| Summary: | media-gfx/shotwell-0.13.1-r2: opening preferences window causes segfault in gnome-shell-3.6.2-r1 + mutter-3.6.2 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Clemente Aguiar <clemente.aguiar> |
| Component: | Current packages | Assignee: | Markos Chandras (RETIRED) <hwoarang> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | gnome, graphics+disabled, jlec |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Shotwell crach 20130212 11:43 - abrt log
Shotwell crash 20130212 17:56 - abrt log output of glxinfo -l |
||
|
Description
Clemente Aguiar
2013-02-10 18:28:19 UTC
Can I see your /var/log/Xorg.0.log that contains the crash please? You might need to look in one of the older logs, numbered 1 to 5. It would give some lines starting with (EE) near the end, giving you a backtrace of why it crashed. shotwell crashes every time I try to go to preferences, so I can easily reproduce. Actualy there is no error (EE) messages in Xorg.0.log The last message is: [ 197.815] Server terminated successfully (0). Closing log file. However I looked at the /vat/log/messages and there seems to have some error messages related to the crash. ...... Feb 10 21:10:33 caguiar-home kernel: gnome-shell[18313]: segfault at 0 ip 00007f5b6fd9a8a0 sp 00007fff7fd4bfc8 error 4 in libcogl.so.9.1.2[7f5b6fd76000+84000] Feb 10 21:10:33 caguiar-home polkitd[17679]: Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.40, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_PT.utf8) (disconnected from bus) Feb 10 21:10:33 caguiar-home gnome-session[18190]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 Feb 10 21:10:34 caguiar-home dbus[17576]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.47" (uid=1000 pid=18724 comm="/usr/bin/gnome-shell ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=17591 comm="/usr/sbin/console-kit-daemon ") Feb 10 21:10:34 caguiar-home polkitd[17679]: Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.47 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_PT.utf8) Feb 10 21:10:34 caguiar-home dbus[17576]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.47" (uid=1000 pid=18724 comm="/usr/bin/gnome-shell ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=17591 comm="/usr/sbin/console-kit-daemon ") Feb 10 21:10:34 caguiar-home kernel: gnome-shell[18724]: segfault at 0 ip 00007f9a6d3b38a0 sp 00007fff42b24268 error 4 in libcogl.so.9.1.2[7f9a6d38f000+84000] Feb 10 21:10:34 caguiar-home polkitd[17679]: Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (system bus name :1.47, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale pt_PT.utf8) (disconnected from bus) Feb 10 21:10:34 caguiar-home gnome-session[18190]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 Feb 10 21:10:34 caguiar-home gnome-session[18190]: WARNING: App 'gnome-shell.desktop' respawning too quickly Feb 10 21:10:47 caguiar-home gnome-session[18190]: CRITICAL: gsm_manager_set_phase: assertion `GSM_IS_MANAGER (manager)' failed Feb 10 21:10:47 caguiar-home gnome-session[18190]: Gtk-CRITICAL: gtk_main_quit: assertion `main_loops != NULL' failed ....... Thank you, I was checking if you were experiencing bug #456682, it appears you don't. Therefore, I have assigned this bug to the maintainers of shotwell. Please start SHOTWELL_LOG=1 SHOTWELL_INFO=1 SHOTWELL_DEBUG=1 SHOTWELL_MESSAGE=1 shotwell from a console and attach ~/.cache/shotwell/shotwell.log and if something is in .xsession-errors, also the bits from there. Since I updated the system in early Jan. that I no longer have .xsession-errors file (???). I started SHOTWELL_LOG=1 SHOTWELL_INFO=1 SHOTWELL_DEBUG=1 SHOTWELL_MESSAGE=1 shotwell from a console, and here are the contents of: ~/.cache/shotwell/shotwell.log ---- L 19442 2013-02-11 19:54:09 [MSG] main.vala:372: Shotwell Gestor de fotos 0.13.1 L 19442 2013-02-11 19:54:09 [DBG] Plugins.vala:316: Searching /home/clemente/.gnome2/shotwell/plugins for plugins ... L 19442 2013-02-11 19:54:09 [DBG] Plugins.vala:135: Unable to search directory /home/clemente/.gnome2/shotwell/plugins for plugins: No such file or directory L 19442 2013-02-11 19:54:09 [DBG] Plugins.vala:316: Searching /usr/lib64/shotwell/plugins for plugins ... L 19442 2013-02-11 19:54:09 [DBG] Plugins.vala:316: Searching /usr/lib64/shotwell/plugins/builtin for plugins ... L 19442 2013-02-11 19:54:09 [DBG] Plugins.vala:424: Loaded SPIT module "Transições principais 0.13.1" (org.yorba.shotwell.transitions) [/usr/lib64/shotwell/plugins/builtin/shotwell-transitions.so] L 19442 2013-02-11 19:54:09 [WRN] Resources.vala:42: couldn't load icon set from /usr/lib64/shotwell/plugins/builtin/tumblr.png. L 19442 2013-02-11 19:54:09 [DBG] Plugins.vala:424: Loaded SPIT module "Shotwell Extra Publishing Services 0.13.1" (org.yorba.shotwell.publishing.extras) [/usr/lib64/shotwell/plugins/builtin/shotwell-publishing-extras.so] L 19442 2013-02-11 19:54:09 [DBG] Plugins.vala:424: Loaded SPIT module "Serviços principais de publicação 0.13.1" (org.yorba.shotwell.publishing.core_services) [/usr/lib64/shotwell/plugins/builtin/shotwell-publishing.so] L 19442 2013-02-11 19:54:10 [DBG] Plugins.vala:424: Loaded SPIT module "Serviços de importação de dados 0.13.1" (org.yorba.shotwell.data_imports.core_services) [/usr/lib64/shotwell/plugins/builtin/shotwell-data-imports.so] L 19442 2013-02-11 19:54:10 [MSG] main.vala:43: Verifying database ... L 19442 2013-02-11 19:54:10 [DBG] Db.vala:40: Database schema version 16 created by app version 0.13.1 L 19442 2013-02-11 19:54:10 [DBG] util.vala:162: next step: LibraryPhoto.init (0/6013) L 19442 2013-02-11 19:54:10 [DBG] util.vala:162: next step: Video.init (2837/6013) L 19442 2013-02-11 19:54:10 [DBG] util.vala:162: next step: Upgrades.execute (2860/6013) L 19442 2013-02-11 19:54:10 [DBG] Upgrades.vala:82: Could not delete mimics: /home/clemente/.local/share/shotwell/mimics is not a directory L 19442 2013-02-11 19:54:10 [DBG] util.vala:162: next step: Event.init (2860/6013) L 19442 2013-02-11 19:54:10 [DBG] util.vala:162: next step: Tag.init (3172/6013) L 19442 2013-02-11 19:54:10 [DBG] util.vala:162: next step: LibraryWindow (3172/6013) L 19442 2013-02-11 19:54:11 [DBG] ConfigurationInterfaces.vala:303: ConfigurationFacade: engine reports property 'DISPLAY_BASIC_PROPERTIES' changed. L 19442 2013-02-11 19:54:11 [DBG] ConfigurationInterfaces.vala:303: ConfigurationFacade: engine reports property 'EVENTS_SORT_ASCENDING' changed. L 19442 2013-02-11 19:54:11 [DBG] LibraryWindow.vala:268: on_library_monitor_installed: /home/clemente/Imagens L 19442 2013-02-11 19:54:11 [DBG] util.vala:162: next step: done (3172/6013) L 19442 2013-02-11 19:54:11 [DBG] ConfigurationInterfaces.vala:303: ConfigurationFacade: engine reports property 'SHOW_WELCOME_DIALOG' changed. L 19442 2013-02-11 19:54:11 [DBG] main.vala:187: 1,711850 seconds to Gtk.main() ---- As per instructions in http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#I-found-a-bug-in-Shotwell-How-can-I-report-it I "installed" debug symbols for GLib, GTK+ and Shotwell. I the run $ SHOTWELL_LOG=1 gdb shotwell 2>&1 | tee shotwell.gdb from within a terminal inside gnome. Here is the contents of $ cat shotwell.gdb GNU gdb (Gentoo 7.5 p1) 7.5 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/shotwell...Reading symbols from /usr/lib64/debug/usr/bin/shotwell.debug...done. done. (gdb) run Starting program: /usr/bin/shotwell warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffea371700 (LWP 10170)] [New Thread 0x7fffcf3c1700 (LWP 10171)] [New Thread 0x7fffcebc0700 (LWP 10172)] [New Thread 0x7fffce3bf700 (LWP 10173)] [New Thread 0x7fffcdbbe700 (LWP 10174)] [New Thread 0x7fffcd3bd700 (LWP 10175)] The problem is that the whole gnome session crashes, so even the information of gdb does not get logged, and I cannot backtrace. Any ideas? (In reply to comment #6) > As per instructions in > > http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#I-found-a-bug-in- > Shotwell-How-can-I-report-it > > I "installed" debug symbols for GLib, GTK+ and Shotwell. > > I the run > > $ SHOTWELL_LOG=1 gdb shotwell 2>&1 | tee shotwell.gdb > > from within a terminal inside gnome. Here is the contents of > > $ cat shotwell.gdb > GNU gdb (Gentoo 7.5 p1) 7.5 > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-pc-linux-gnu". > For bug reporting instructions, please see: > <http://bugs.gentoo.org/>... > Reading symbols from /usr/bin/shotwell...Reading symbols from > /usr/lib64/debug/usr/bin/shotwell.debug...done. > done. > (gdb) run > Starting program: /usr/bin/shotwell > warning: Could not load shared library symbols for linux-vdso.so.1. > Do you need "set solib-search-path" or "set sysroot"? > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib64/libthread_db.so.1". > [New Thread 0x7fffea371700 (LWP 10170)] > [New Thread 0x7fffcf3c1700 (LWP 10171)] > [New Thread 0x7fffcebc0700 (LWP 10172)] > [New Thread 0x7fffce3bf700 (LWP 10173)] > [New Thread 0x7fffcdbbe700 (LWP 10174)] > [New Thread 0x7fffcd3bd700 (LWP 10175)] > > The problem is that the whole gnome session crashes, so even the information > of gdb does not get logged, and I cannot backtrace. > > Any ideas? please install abrt. with that you can catch segf even when the complete session crashes. Another try would be, move away all files from your picture folder and restart shottwell. Created attachment 338682 [details]
Shotwell crach 20130212 11:43 - abrt log
I installed abrt (lateste version: 2.0.12-r1
This is the log created after a shotwell crash.
(In reply to comment #7) > Another try would be, move away all files from your picture folder and > restart shottwell. Deleted .local/share/shotwell directory (deletes shotwell data base). No files in Photos and Images directories. Started Shotwell, and is blank, go to preferences still crashes. @gnome the shell crashes. Any idea why? (In reply to comment #10) > @gnome > the shell crashes. Any idea why? No. This is what I have mentioned since my first report. All I do is: 1. From a terminal run startx 2. Open Shotwell 3. Go to Edit -> Preferences And I the whole gnome session crashes and I am back at the terminal. At the office, I have a similar configured PC (i.e. Gentoo AMD64 with Gnome 3.6) and this does not happen. It only happens on my home PC. And that is what is weird. For the record, to try to solve this mystery, I recently emerged -e world, with minimum CFLAGS, i.e. CFLAGS="-O2 -pipe". Made no difference. I am still keeping these CFLAGS until problem solved. (In reply to comment #11) > No. This is what I have mentioned since my first report. it does, look at your abrt.log. It's about a gnome-shell crash. (In reply to comment #12) > (In reply to comment #11) > > No. This is what I have mentioned since my first report. > > it does, look at your abrt.log. It's about a gnome-shell crash. There seem to be a misunderstanding, I was saying no to your question "Any idea why?" in comment 10, which only later that I figure out that the question was not intended for me. Sorry for the confusion. (In reply to comment #8) > Created attachment 338682 [details] > Shotwell crach 20130212 11:43 - abrt log > > I installed abrt (lateste version: 2.0.12-r1 > This is the log created after a shotwell crash. Thanks for the log. Unfortunately, it looks like you didn't have some of the debugging information that abrt needed to generate a complete backtrace for the crash. Please re-emerge the following packages with -ggdb in CFLAGS and splitdebug in FEATURES (see http://www.gentoo.org/proj/en/qa/backtraces.xml for more information): media-libs/cogl, media-libs/clutter, x11-wm/mutter and then please crash gnome-shell with shotwell again, and attach the resulting abrt log. In addition, please say what versions (and with what USE flags) of media-libs/cogl, media-libs/clutter, x11-wm/mutter, gnome-base/gnome-shell, x11-libs/libwnck, and media-libs/mesa you are using. Created attachment 338714 [details]
Shotwell crash 20130212 17:56 - abrt log
Here is the abrt log as requested, after building media-libs/cogl, media-libs/clutter, x11-wm/mutter with debug symbols.
And here is the versions and USE flags of the different packages as requested.
$ emerge -pv media-libs/cogl media-libs/clutter x11-wm/mutter gnome-base/gnome-shell x11-libs/libwnck
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ~] media-libs/cogl-1.10.4:1.0/9 USE="introspection opengl pango -debug -doc -examples -gles2 {-test}" 0 kB
[ebuild R ~] x11-libs/libwnck-3.4.4:3 USE="introspection startup-notification -tools" 0 kB
[ebuild R ~] media-libs/clutter-1.12.2:1.0 USE="gtk introspection -debug -doc {-test}" 0 kB
[ebuild R ~] x11-wm/mutter-3.6.2 USE="introspection -debug {-test}" 0 kB
[ebuild R ~] gnome-base/gnome-shell-3.6.2-r1 USE="bluetooth i18n networkmanager -systemd" PYTHON_TARGETS="python2_7 -python2_6" 0 kB
(In reply to comment #15) > Created attachment 338714 [details] > Shotwell crash 20130212 17:56 - abrt log Thanks. It's possible that mutter is for some reason creating textures that are too large for your video card. Please attach the output of "glxinfo -l" (if you don't have glxinfo, you will need to emerge x11-apps/mesa-progs first). Created attachment 338724 [details]
output of glxinfo -l
(In reply to comment #17) Thanks. > GL_MAX_TEXTURE_SIZE = 2048 seems quite low; I am guessing this is an old video card? When I open the preferences window in shotwell-0.13.1, I notice the screen blink a bit. This is only a guess, but maybe shotwell is initially creating a very large window, over 2048 pixels on one side, and then immediately resizing it down? Mutter would try to allocate a GL texture large enough for the window's initial size, which would fail, and the fallout might be the crash that you are seeing. This is definitively a really low value. Even my old PCI Radeon 9000 (r200) had 4096 here. It couldn't run gnome-shell because of the dual monitor setup exceeding that limit (1280x1024 x 2). What is the size of your monitor ? Yes, its not a new card, its a Radeon X800 GTO. Here is what "lspci -v" says 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI R480 [Radeon X800 GTO (PCIE)] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device 2046 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at f0000000 (64-bit, prefetchable) [size=128M] Memory at fe630000 (64-bit, non-prefetchable) [size=64K] I/O ports at e000 [size=256] Expansion ROM at fe600000 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Capabilities: [58] Express Endpoint, MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Advanced Error Reporting Kernel driver in use: radeon Kernel modules: radeon My display is a LG 20" (Wide) with a resolution of 1650x1050. I installed the latest version (0.14.0-r1), and with this version I am now able to open the Preferences window. So for me the problem is resolved. |
