abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: gnome-power-manager comment: I was already loggued locally and was logging in another NX session component: gnome-power-manager crash_function: handle_error executable: /usr/bin/gnome-power-manager kernel: 2.6.35.6-48.fc14.x86_64 package: gnome-power-manager-2.32.0-3.fc14 rating: 4 reason: Process /usr/bin/gnome-power-manager was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1290605384 uid: 500 How to reproduce ----- 1. login as usual 2. abrt then tells me than gnome-power-manager has crashed 3.
Created attachment 462639 [details] File: backtrace
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.log in system using nxclient 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.i booted the first time after an upgrade from 13 to 14 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. install freenx and nx rpms configure for login under Fedora 14. 2. login with no machine nx client 3. get error about gnome-power-manager crashing on login. Comment ----- Might be related to bug https://bugzilla.redhat.com/show_bug.cgi?id=573933
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Not sure, just noticed the Gnome "ABRT" icon, with a crash count of 4 2. 3. Comment ----- The system of interest is a server, on which I installed F14 a few days ago (Nov 29). I access it via NX from my F14 desktop, and just noticed that this problem has occurred 4 times so far.
Here are the entries in /var/log/messages bracketing the abort. Note that there is an entry in the middle of this for pulseaudio, for which there is a also newly exposed bug (see https://bugzilla.redhat.com/show_bug.cgi?id=659072). I mention this on the small chance that there is some causal relation between the two. Dec 2 14:37:20 vh3 setroubleshoot: SELinux is preventing /usr/bin/xauth "unlink" access on .Xauthority-c. For complete SELinux messages. run sealert -l 7e17b194-2e7d-477b-b748-df96414765cc Dec 2 14:37:20 vh3 dbus: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.189" (uid=1432881289 pid=2839 comm="/usr/bin/seapplet) interface="org.fedoraproject.SetroubleshootdIface" member="check_for_new" error name="(unset)" requested_reply=0 destination="org.fedoraproject.Setroubleshootd" (uid=0 pid=1345 comm="/usr/bin/python)) Dec 2 14:37:20 vh3 abrt[2966]: saved core dump of pid 2817 (/usr/bin/gnome-power-manager) to /var/spool/abrt/ccpp-1291318640-2817.new/coredump (11051008 bytes) Dec 2 14:37:20 vh3 abrtd: Directory 'ccpp-1291318640-2817' creation detected Dec 2 14:37:20 vh3 pulseaudio[2838]: pid.c: Daemon already running. Dec 2 14:37:20 vh3 abrtd: Crash is in database already (dup of /var/spool/abrt/ccpp-1291172721-22614) and is reported
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Logged in with nxclient 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Startin up Gnome 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. started gnome sesssion via nomachine nx Comment ----- start a gnome sesssion via nomachine nx
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. loged onto a text console. Then did a startx 2. Worked for a while on the system, then switched away (using a KVM swicth to share keyboard / video / mouse) 3.Whe I returned to the server - had a blank screen - no response from the mouse or keyboard. 4. Other tasks (eg httpd and ssh) were working OK. Comment ----- This is not the 1st time this has happened. The 1st time (similar steps as above) happened on a fedora12 installation. This installtion has now been updated to fedora 14 x64 - with all updates installed to date.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start gnome on a second session. Comment ----- This happens every time I log in remotely via nx and start up gnome.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I logged in using nx, the error was there 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I was remoting into my desktop on port 22 us NX client 2.The Program i used was NX client for windows 3.It can be downloaded from :www.nomachine.com/download, i run the client, node and software NX versions on my fedora desktop.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Log into desktop using freenx, abrt immedeately announces that the gnome-power-manager process has crashed. Happens every time. Local logins does not have this problem.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Starting up the system 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Logged in to NX 2.Received crash message 3.Was still able to work
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.just as get connected by NOMACHINE, through freeNX. 2. Boom gnome-power-management bang 3. crash
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Remote desktop with Nx 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Don't know, just saw the error indicator 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.login with NX client 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. connect with NX client from Windows 2. While starting gnome, the error report appeared
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. freenx server 64bit running 2. freenx client from windows trying to remote dekstop 3. gnome-power-manager crash
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.reboot the computer 2.login 3.crash
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. boot into Fedora 14 2. uptime is 2 days, 6:49 hours 3. AFAIK, it was an asynchronous occurrence
This was with nxserver running and happened on nxclient login to resume a session.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I have a APC BR1200 UPS connected via USB to the Fedora 14 x86_64 PC 2. I created a 2nd session to the computer as the same user (clinton) using freenx 3. Comment ----- I believe this bug was triggered by creating a 2nd gnome session to the same computer.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. This bug was occured when etablishing a new session connexion by freenx-server (with nomachine client). 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.This error occur when i logon to freenx server with nomachine client. 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- The error occurs when a user creates a gnome remote session via FreeNX. Comment ----- It happens while the gnome panel is built up
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. log in using nx 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I logged in to the machine using the Nomachine NX client for Mac OS. As soon as i logged in the crash occurred. 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I don't know 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Log into this computer with freenx client 2. 3.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Connect to machine remotely using NX Client for Windows 2. Log in 3. Crash reporter fires up
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Clicking on System -> Preferences -> Power Management Crash report immediatley happens. Some options are greyed out.
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Power Manager crashes each time the system boots/I log in
Package: gnome-power-manager-2.32.0-3.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.did not see what the problem is 2. 3.
(In reply to comment #42) > Package: gnome-power-manager-2.32.0-3.fc14 > Architecture: x86_64 > OS Release: Fedora release 14 (Laughlin) > > > How to reproduce > ----- > Power Manager crashes each time the system boots/I log in Reading through the other reports, I wanted to also make note that I am using the NeatX NX server on my system, and connecting with the nomachines client and java applet. I'm running the same software on a different host running Fedora 15 and have not seen the ABRT warning.
This is fixed and tested in F16.
*** Bug 656063 has been marked as a duplicate of this bug. ***
*** Bug 652126 has been marked as a duplicate of this bug. ***
*** Bug 643946 has been marked as a duplicate of this bug. ***
*** Bug 700539 has been marked as a duplicate of this bug. ***