Bug 963599
Summary: | [abrt] cinnamon-1.8.2-4.fc19: object_instance_finalize: Process /usr/bin/cinnamon was killed by signal 5 (SIGTRAP) | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomas Dolezal <todoleza> | ||||||||||||||||||||||
Component: | cinnamon | Assignee: | leigh scott <leigh123linux> | ||||||||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||
Version: | 19 | CC: | ansubram, antoine, brwillia, dan.mashal, dtimms, irathore, joshua, joshua, js, kengert, leigh123linux, lukas.marek, mahmud, marbolangos, m.oliver, peter.p.waskiewicz.jr, plambri, self | ||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||
Whiteboard: | abrt_hash:69481444af4e83c73330ef2b742f918aaf775f66 | ||||||||||||||||||||||||
Fixed In Version: | cinnamon-1.9.1-16.fc19 | Doc Type: | Bug Fix | ||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||
Last Closed: | 2013-07-14 03:31:59 UTC | Type: | --- | ||||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||||
Attachments: |
|
Description
Tomas Dolezal
2013-05-16 08:27:50 UTC
Created attachment 748650 [details]
File: backtrace
Created attachment 748651 [details]
File: cgroup
Created attachment 748652 [details]
File: core_backtrace
Created attachment 748653 [details]
File: dso_list
Created attachment 748654 [details]
File: environ
Created attachment 748655 [details]
File: limits
Created attachment 748656 [details]
File: maps
Created attachment 748657 [details]
File: open_fds
Created attachment 748658 [details]
File: proc_pid_status
Created attachment 748659 [details]
File: var_log_messages
the vpn disconnected. then cinnamon crashed. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: cinnamon --replace crash_function: object_instance_finalize executable: /usr/bin/cinnamon kernel: 3.9.4-300.fc19.x86_64 package: cinnamon-1.8.3-1.fc19 reason: Process /usr/bin/cinnamon was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 1000 I think it's connected to the display of a notification in the top right corner of the screen. I am getting this several times a day now, thankfully all windows are automatically restarted... I got this right after resume. I'm getting this every time I connect to a wifi and then disable it using networ-manager applet. cinnamon-1.9.1-12.fc19.x86_64 Same as Lukas: happens reliably if I disconnect from the wifi using nm (or rather, disconnect from whatever connection was running when I first logged in?) Same here, after a NM disconnect of wireless Probably related: http://github.com/linuxmint/Cinnamon/issues/2125 What makes this bug much worse than it sounds is that half the time I get the screen saying "oh no" covering all of my display(s) then I have to find a way to kill that to be able to say yes to "restart cinnamon", or I lose what I was doing. Feel free to skip this rant: who came up with this "oh no" screen anyway? How does it help anyone? It hides the real cause (not to be found in xsession-errors, or anywhere that I could find) and it only offers a single choice: "OK", and in fact it is anything but OK at this point: it will kill the X11 server and tear down all your applications! Terrible, terrible UI and choice of action. I've seen this "oh no" screen far too many times, and to me it usually means: install a DE environment that works, this one won't and won't tell you why either. (In reply to Antoine Martin from comment #18) > What makes this bug much worse than it sounds is that half the time I get > the screen saying "oh no" covering all of my display(s) then I have to find > a way to kill that to be able to say yes to "restart cinnamon", or I lose > what I was doing. Indeed. Very annoying. There should be an easy way to kill the forced-foreground oh-no-forced-logoug dialog, if one is certain that continuing is acceptable and life-saving. It is the same for me on a "MacBook Pro" with ATI Radeon and on a Lenovo W530 with NVidia Quatro. It happens with or without proprietary drivers. One othe thing to mention is that they were both upgraded from FC-18. This issue only happens with VPN notification, othet notification even from NM (wireless connected, disconnected) do not cause the crash. A new version of NetworkManager was just pushed and it did not make any difference, it is till crashing. recent changes: - upgrade fedora 18 to fedora 19 via fedup (iso only, now doingremaining updates). - new mouse: usb logitech g600 with 12 shortcut buttons on side. These are by default set for digits. Notice that sometimes I accidently press one of the side buttons. usually a digital it types into firefox or terminal. But sometimes, the mouse cursor disappears. If the location that the mouse is over has some visual feeback, then as you move the mouse, oyou can sort of work out where the pointer currently is. This can be resolved by switch user, loggin in as another user, logout, ssitch back to original user. Updates may have been running/installing while this crash occured. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: cinnamon --replace crash_function: object_instance_finalize executable: /usr/bin/cinnamon kernel: 3.9.5-301.fc19.x86_64 package: cinnamon-1.9.1-12.fc19 reason: Process /usr/bin/cinnamon was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 1000 xsession_errors: Window manager warning: Log level 16: cinnamon: Fatal IO error 0 (Success) on X server :0. I see this with Fedora 19: cinnamon.x86_64 1.9.1-12.fc19 There is a consistent crash every time I disconnect my VPN (vpnc). It throws up a cinnamon crash error and I need to logout and login again, my entire state wiped out... VPN connect using vpnc proceeds smoothly (though that seems to have a different issue of not managing to save the Group password consistently) but disconnect always crashes cinnamon. Any update from the devs on this? Between this bug and the inability to shut down a VM without a host panic, Fedora 19 is very difficult to use on a daily basis. Any updates would be much appreciated. I'm not sure exactly what caused the crash. I was reconfiguring some port settings on my router, which caused a momentary WiFi drop out. Whilse trying to get Cinnamon to refresh the networks in the area, I accidetally RMB on another network... boom. I have no idea if this can be reproduced - or even if this is what caused the drop. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: cinnamon --replace crash_function: object_instance_finalize executable: /usr/bin/cinnamon kernel: 3.9.5-301.fc19.x86_64 package: cinnamon-1.9.1-12.fc19 reason: Process /usr/bin/cinnamon was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 1000 This is rather easy to trigger by either toggling Wifi on/off or a suspend/resume cycle. Very annoying. :( It is very easily seen on Fedora19. As reported several times, earlier in this thread, its very easily triggered by wi-fi or VPN (ON/OFF button) - at least for me. I did try to do yum update to move to Fedora 19-GA to check if it resolved the issue. Unfortunately that did not help. So finally moved to Mate, to finally breathe again :-) Not sure if this is related, but some of my colleagues don't seem to hit the issue after yum update on Fedora19 and/or Fedora19-GA but the difference between their cases and mine is that I am on Lenovo X230 while their model happens to be X220. Thanks! I believe I've located the cause of the issue, please test https://koji.fedoraproject.org/koji/buildinfo?buildID=433011 and report here if it fixes the issue. The fix works for me. Thanks Leigh. cinnamon-1.9.1-16.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/cinnamon-1.9.1-16.fc19 Package cinnamon-1.9.1-16.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing cinnamon-1.9.1-16.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12882/cinnamon-1.9.1-16.fc19 then log in and leave karma (feedback). cinnamon-1.9.1-16.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |