Description of problem: DVD install of TC5 Beta x86_64 to HD of Mate with updates block unchecked in software sources doing test and added 2nd user and logged in then got error. Version-Release number of selected component: mate-panel-1.6.1-4.fc20 Additional info: reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.11.5-302.fc20.x86_64 runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #1 container_child_background_set at mate-panel-applet-frame-dbus.c:240 #2 g_simple_async_result_complete at gsimpleasyncresult.c:777 #3 set_applet_property_cb at mate-panel-applet-container.c:556 #4 g_simple_async_result_complete at gsimpleasyncresult.c:777 #5 g_dbus_connection_call_done at gdbusconnection.c:5484 #6 g_simple_async_result_complete at gsimpleasyncresult.c:777 #7 complete_in_idle_cb at gsimpleasyncresult.c:789 #12 gtk_main at gtkmain.c:1257
Created attachment 816286 [details] File: backtrace
Created attachment 816287 [details] File: cgroup
Created attachment 816288 [details] File: core_backtrace
Created attachment 816289 [details] File: dso_list
Created attachment 816290 [details] File: environ
Created attachment 816291 [details] File: exploitable
Created attachment 816292 [details] File: limits
Created attachment 816293 [details] File: maps
Created attachment 816294 [details] File: open_fds
Created attachment 816295 [details] File: proc_pid_status
Created attachment 816296 [details] File: var_log_messages
(In reply to satellit from comment #0) > Description of problem: > DVD install of TC5 Beta x86_64 to HD of Mate with updates block unchecked in > software sources > doing test and added 2nd user and logged in then got error. Did mate-panel crash or is only abrt unhappy?
Mate kept running so I guess abrt saw some problem....
I can't confirm this for the moment after a installation, let us see if this happens with beta or release iso's too, but feel free to post here if the problem occurs more frequently.
I have seen mate-panel crash on login before. I think this is an actual bug in mate-panel, but im not 100% sure.
Altered bottom panel properties to autohide. Was tinkering with cairo-dock setup then logged out and returned to the abrt notification that the panel had crashed. Fedora 20 Mate mate-panel-1.6.1-4.fc20 reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.11.8-300.fc20.x86_64 package: mate-panel-1.6.1-4.fc20 reason: Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
It occurred after login to system. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: mate-panel --sm-client-id 10d4ecfe89e614dee8138552624949120200000011640027 crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.11.9-300.fc20.x86_64 package: mate-panel-1.6.1-4.fc20 reason: Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: close mate seans, login xfce without reboot reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.11.10-301.mo.fc20.R.x86_64 package: mate-panel-1.6.1-4.fc20 reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
(In reply to Dan Mashal from comment #15) > I have seen mate-panel crash on login before. I think this is an actual bug > in mate-panel, but im not 100% sure. Pls forward the issue to upstream, i don't wanna be the asshole who do this everytime in their eyes ;)
*** Bug 1082238 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: Error from first start after update reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.13.8-200.fc20.x86_64 package: mate-panel-1.6.2-1.fc20 reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I use KDE when I'm at my workstation, but I use MATE via VNC when access it remotely. I see this abrt warning pretty much every time that I first log in to KDE after returning home (assuming that I've used MATE remotely while away).
Another user experienced a similar problem: I made an update via yum today and after that i rebooted my system. This error just appeard after login. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.14.4-200.fc20.x86_64 package: mate-panel-1.6.2-1.fc20 reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I just installed Cinnamon desktop via the Mate terminal using yum groupinstall cinnamon. Once it finished the install I logged out of Mate and logged in on Cinnamon. I got the error when I got logged into the Cinnamon desktop when it loaded. Hope this helps. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.11.10-301.fc20.x86_64 package: mate-panel-1.6.2-1.fc20 reason: Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Just started Mate-Session. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.14.7-200.fc20.x86_64 package: mate-panel-1.6.2-1.fc20 reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
forward to upstream https://github.com/mate-desktop/mate-panel/issues/214
Another user experienced a similar problem: I was just booting into fedora 20! (MATE) reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.14.8-200.fc20.x86_64 package: mate-panel-1.6.2-1.fc20 reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
mate-panel-1.6.2-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mate-panel-1.6.2-2.fc20
mate-panel-1.6.2-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mate-panel-1.6.2-2.fc19
Hey Guys, it would be nice if someone could test this update. Here on my system i don't see the issue if i login to a new created account. Thank you
Patch fc20 seems to work fine here, thanks!
Package mate-panel-1.6.2-2.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 mate-panel-1.6.2-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7767/mate-panel-1.6.2-2.fc19 then log in and leave karma (feedback).
Another user experienced a similar problem: Started mate session. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: mate-panel crash_function: container_child_background_set executable: /usr/bin/mate-panel kernel: 3.14.9-200.fc20.x86_64 package: mate-panel-1.6.2-2.fc20 reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
mate-panel-1.6.2-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mate-panel-1.6.2-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Still occurring here randomly just after login in a xinetd VNC session. mate-panel-1.6.2-2.fc20.x86_64 Please reopen. Thanks.
Hi Patrick, shure i can. Can you please report this also at upstream report? https://github.com/mate-desktop/mate-panel/issues/214 Stefano is waiting for a feedback for his fix. Maybe it's an issue with low vnc performance? Note: Mate-1.8 is currently in update-testing. Maybe it doesn't https://admin.fedoraproject.org/updates/FEDORA-2014-8966/atril-1.8.0-5.fc20,pluma-1.8.1-2.fc20,mozo-1.8.0-2.fc20,mate-utils-1.8.0-3.fc20,mate-user-share-1.8.0-2.fc20,mate-terminal-1.8.0-3.fc20,mate-system-monitor-1.8.0-3.fc20,mate-settings-daemon-1.8.1-2.fc20,mate-session-manager-1.8.1-2.fc20,mate-sensors-applet-1.8.0-3.fc20,mate-screensaver-1.8.0-2.fc20,mate-power-manager-1.8.0-3.fc20,mate-polkit-1.8.0-2.fc20,mate-panel-1.8.0-3.fc20,mate-notification-daemon-1.8.0-2.fc20,mate-netspeed-1.8.0-3.fc20,mate-menus-1.8.0-3.fc20,mate-media-1.8.0-2.fc20,mate-icon-theme-faenza-1.8.0-1.fc20,mate-icon-theme-1.8.0-2.fc20,mate-dialogs-1.8.0-3.fc20,mate-desktop-1.8.1-5.fc20,mate-control-center-1.8.2-1.fc20,mate-common-1.8.0-3.fc20,mate-backgrounds-1.8.0-2.fc20,mate-applets-1.8.0-3.fc20,marco-1.8.1-1.fc20,libmateweather-1.8.0-2.fc20,libmatekbd-1.8.0-2.fc20,eom-1.8.0-3.fc20,engrampa-1.8.0-2.fc20,compiz-0.8.8-27.fc20,caja-extensions-1.8.0-3.fc20,caja-actions-1.7.1-3.fc20,caja-1.8.1-5.fc20?_csrf_token=387b749cc5d4a481cf9662aa378f7c53a2a926e9 Please leave karma.
*** Bug 1132298 has been marked as a duplicate of this bug. ***
I logged into Mate this evening and at first the panels didn't load. I thought I might have to recreate them, but then they appeared. There was no network connection. Everything was moving slow, maybe because ABRT was running. ABRT didn't come up until I was logged into another user account (my son's account; he's three, so I try to keep him a confined process). I could not authenticate to submit the report from that account, so I logged back into my account and tried to submit the report from there. ABRT said it had already been reported and directed me to this bug. I'm running mate-panel-1.8.0-4.fc20.x86_64. I don't use vnc.
Still occurring with 1.8.0-4. I left the same comment at https://github.com/mate-desktop/mate-panel/issues/214.
(continued) However I'm not sure it happens at session start time. It is reported (the beacon) at this time, but I think it happened at previous session end time. Not sure, but quite confident in this diagnostic.
mate-panel-1.8.1-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/mate-panel-1.8.1-2.fc21
mate-panel-1.8.1-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mate-panel-1.8.1-2.fc20
mate-panel-1.6.2-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mate-panel-1.6.2-3.fc19
Package mate-panel-1.8.1-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mate-panel-1.8.1-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15959/mate-panel-1.8.1-2.fc21 then log in and leave karma (feedback).
mate-panel-1.8.1-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mate-panel-1.8.1-3.fc20
mate-panel-1.8.1-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mate-panel-1.8.1-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
mate-panel-1.6.2-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
This bug restarted to occur with mate-panel-1.8.1-4.fc20.x86_64 :-(
New attempt from upstream to fix this issue. Scratch build for all branches please test, as upstream and me couldn't reproduce the issue you help is needed. f24 http://koji.fedoraproject.org/koji/taskinfo?taskID=14010315 f23 http://koji.fedoraproject.org/koji/taskinfo?taskID=14010343 f22 http://koji.fedoraproject.org/koji/taskinfo?taskID=14010355 epel7 http://koji.fedoraproject.org/koji/taskinfo?taskID=14010361