After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 351704 - Crash on gtk_recent_info_get_short_name
Crash on gtk_recent_info_get_short_name
Status: RESOLVED DUPLICATE of bug 363437
Product: gtk+
Classification: Platform
Component: Class: GtkRecent
2.10.x
Other All
: High critical
: ---
Assigned To: gtk-bugs
Emmanuele Bassi (:ebassi)
: 360674 375011 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-08-16 23:33 UTC by meir
Modified: 2007-01-10 11:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
gnome-panel bug (6.26 KB, text/plain)
2006-10-08 19:11 UTC, david.latreyte
Details
gnome-panel startup log and backtrace, and .recently-used.xbel (10.42 KB, application/x-compressed-tar)
2006-11-03 18:53 UTC, Stu Hood
Details

Description meir 2006-08-16 23:33:13 UTC
What were you doing when the application crashed?
Tried to view source from epiphany


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.91 2006-08-08 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 33763328 vsize: 0 resident: 33763328 share: 0 rss: 8634368 rss_rlim: 0
CPU usage: start_time: 1155771164 rtime: 0 utime: 21 stime: 0 cutime:18 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gedit'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208186688 (LWP 25379)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1208186688 (LWP 25379))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 *__GI_raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 *__GI_abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_recent_info_get_short_name
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_recent_info_get_display_name
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 _gedit_window_move_tab_to_new_window
  • #13 _gedit_window_move_tab_to_new_window
  • #14 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #19 bacon_message_connection_new
  • #20 gedit_app_create_window
  • #21 main
  • #0 __kernel_vsyscall

Comment 1 Paolo Borelli 2006-08-17 09:55:54 UTC
> What were you doing when the application crashed?
> Tried to view source from epiphany
>
> #9  0x4da37480 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
> #10 0x4dd7814d in gtk_recent_info_get_short_name ()

Emmanuele, is this another case of GtkRecent not dealing properly with remote file uris? If yes, can we get it fixed in gtk? It's silly to add workarounds all over the place...


Comment 2 Emmanuele Bassi (:ebassi) 2006-08-17 10:27:10 UTC
the stack trace is not useful to narrow it down.  gtk_recent_info_get_short_name() calls get_uri_shortname_for_display() which is basically the same code used by gnome-vfs (and egg-recent) to get the last fraction of the URI and make sure that it's UTF-8 encoded; if the URI is not local (file:/) it'll try to get the URI scheme and add it to the string.

I need the full backtrace, otherwise I don't know where it hit an assert().
Comment 3 Paolo Borelli 2006-08-17 11:06:33 UTC
apart from the backtrace I useful info to know it's the url of the page of which you were trying to view the source, so that we can try to repro.
Comment 4 Steve Frécinaux 2006-08-17 13:23:51 UTC
(In reply to comment #1)
> > Tried to view source from epiphany
> 
> Emmanuele, is this another case of GtkRecent not dealing properly with remote
> file uris? If yes, can we get it fixed in gtk?

AFAIK Epiphany opens the local cached file in gedit, not the remote one.
Comment 5 Paolo Maggi 2006-08-18 15:33:38 UTC
Can we move this to gtk+?
Comment 6 Paolo Maggi 2006-08-21 10:55:43 UTC
<paolo> Can we move bug #351704 to gtk+?
<bugsbot> paolo: Bug http://bugzilla.gnome.org/show_bug.cgi?id=351704 cri, High, ---, gedit-maint@gnome.bugs, NEED, Crash on gtk_recent_info_get_short_name
<pbor> paolo: mmm... not sure
<pbor> paolo: nud's comment is true
<pbor> so I am not sure anymore that it's the same issue
Comment 7 Emmanuele Bassi (:ebassi) 2006-08-21 11:03:40 UTC
if someone experiencing this crasher can get me a complete stack trace I'll more than gladly move this to gtk+; until then, I'd say it can stay as NEEDINFO because I can't see whether this is a bug in GtkRecentInfo creating or being passed wrong data.
Comment 8 Elijah Newren 2006-10-08 15:53:43 UTC
*** Bug 360674 has been marked as a duplicate of this bug. ***
Comment 9 david.latreyte 2006-10-08 19:10:24 UTC
I'm not sure that the bug 360674 is directly a gedit bug. It seems to me that this is a gnome-panel bug at first.

See the backtrace below
Comment 10 david.latreyte 2006-10-08 19:11:36 UTC
Created attachment 74308 [details]
gnome-panel bug
Comment 11 Paolo Maggi 2006-10-29 16:11:43 UTC
It seems this crash also affects gnome-panel (see comment #10).

Moving to gtk+.
Comment 12 Stu Hood 2006-11-03 18:52:16 UTC
I'm experiencing this one as well with Gnome, Gedit and gnome-panel all at version 2.16.1, and it is especially nasty. It started the same way mentioned above: I viewed source on a file in Epiphany, and then gedit and gnome-panel both crashed.

On all subsequent startups, gnome-panel and gedit will crash.

Here is the important update: if I remove "~/.recently-used.xbel", gnome-panel and gedit will start just fine and a fresh recently-used.xbel will be generated. I've attached the offending file, and a hopefully enlightening trace. I checked it quickly for anything incriminating, but luckily I do my dirty work on my desktop =)

Thanks!

Comment 13 Stu Hood 2006-11-03 18:53:56 UTC
Created attachment 75953 [details]
gnome-panel startup log and backtrace, and .recently-used.xbel
Comment 14 Emmanuele Bassi (:ebassi) 2006-11-16 10:24:44 UTC
this feels like a duplicate of bug #363437.

I'll dupe this, as the other bug has a meaningful stack trace.

*** This bug has been marked as a duplicate of 363437 ***
Comment 15 Paolo Maggi 2007-01-10 11:23:37 UTC
*** Bug 375011 has been marked as a duplicate of this bug. ***