Ticket #186 (closed defect: fixed)
upgrade libglib-2.0-0 (causes midori crash)
| Reported by: | GNUtoo | Owned by: | spaetz |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Package requests | Version: | SHR-unstable |
| Keywords: | crash midori | Cc: |
Description
hello,
I have the following backtrace with midori:
Starting program: /usr/bin/midori
warning: Lowest section in /usr/lib/libicudata.so.36 is .gnu.hash at 00000094
[Thread debugging using libthread_db enabled]
[New Thread 0x424e8230 (LWP 1575)]
(midori:1575): Gtk-WARNING : Could not find the icon 'process-working'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
(midori:1575): WARNING : Icon 'process-working' couldn't be loaded
[New Thread 0x436e1490 (LWP 1578)]
[Thread 0x436e1490 (LWP 1578) exited]
[New Thread 0x436e1490 (LWP 1579)]
[Thread 0x436e1490 (LWP 1579) exited]
[New Thread 0x436e1490 (LWP 1580)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x436e1490 (LWP 1580)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x4003d368 in open_read_async_thread () from /usr/lib/libgio-2.0.so.0
#2 0x4004c9e8 in run_in_thread () from /usr/lib/libgio-2.0.so.0
#3 0x400482c0 in io_job_thread () from /usr/lib/libgio-2.0.so.0
#4 0x42144c28 in g_thread_pool_thread_proxy () from /usr/lib/libglib-2.0.so.0
#5 0x421429e0 in g_thread_create_proxy () from /usr/lib/libglib-2.0.so.0
#6 0x422d48ac in start_thread () from /lib/libpthread.so.0
#7 0x424735b8 in clone () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
I was told in irc that it was because of glib:
see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495501#15 for more details
Change History
comment:2 Changed 4 years ago by spaetz
- Keywords crash midori added
- Summary changed from libglib-2.0-0 is broken to upgrade libglib-2.0-0 (causes midori crash)
The bug might be in midori, but the corresponding midori bug has been closed as upgrading glib "fixed" the issue, so this is not going to be fixed in midori for the time being. The only way to get rid of this crash for now seems to be upgrading
to glib2.0-2.16.5-1 (debian numbering)
I adapted the summary to reflect this.
comment:3 Changed 4 years ago by spaetz
- Owner changed from ainulindale to spaetz
- Version set to SHR-unstable
- Component changed from SHR Image to package requests
- Milestone set to MS2
The "fix" mentioned in upgrading glib is that is catches the NULL pointer and survives this. The bug itself in midori trying to load a non-existing file is still there.