Bug 736727
Summary: | [abrt] xfce4-power-manager-1.0.10-1.fc16: handle_error: Process /usr/bin/xfce4-power-manager was killed by signal 5 (SIGTRAP) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Václav Jansa <vaclav.jansa> | ||||||||||
Component: | xfce4-power-manager | Assignee: | Christoph Wickert <christoph.wickert> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 16 | CC: | adanos, andovais, awilliam, canthony, christoph.wickert, contact, cptcool1, derstef, dr.sexx, eblix08, foto, gondarlinux, halinux, hopparz, hrobi88, igor, igor.redhat, jeff, jmoskovc, karmstrong, lcafiero, maciek.borzecki, mario, markwilt, martin.nyhus, maxamillion, me, metalhead2004, mrunge, udtduetl | ||||||||||
Target Milestone: | --- | Keywords: | CommonBugs | ||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | abrt_hash:2ec2060ac9199f9e8207d804a67eee401f4be0e5 AcceptedNTH https://fedoraproject.org/wiki/Common_F16_bugs#xfce-power-crash | ||||||||||||
Fixed In Version: | xfce4-power-manager-1.0.10-2.fc16 | Doc Type: | Bug Fix | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2011-11-12 03:30:40 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: | |||||||||||||
Bug Depends On: | |||||||||||||
Bug Blocks: | 748255 | ||||||||||||
Attachments: |
|
Description
Václav Jansa
2011-09-08 14:21:19 UTC
Created attachment 522131 [details]
File: maps
Created attachment 522132 [details]
File: backtrace
Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Second login to Xfce. Problem persist. Right after this happens all the window decorations disappear and the system switches to focus-follows-mouse. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Just logged into xfce session. Ping? This seems to me like pretty serious problem, it dies every time I log into XFCE and non-working power manager means the laptop just dies without a warninng when the battery is low. I am sorry, unlike you I am not paid by Red Hat but a volunteer, so things can take a little longer when I am busy with my dayjob. Can any of you please provide a better backtrace? The one we have lacks all xfce4-power-manager debug symbols and some others are outdated. So if you can reproduce this but, make sure to update your system incl the debuginfo packages and then run # debuginfo-install xfce4-power-manager Then reproduce the bug and provide the backtrace here. TIA! (In reply to comment #7) > I am sorry, unlike you I am not paid by Red Hat but a volunteer, so things can > take a little longer when I am busy with my dayjob. Sorry, I didn't mean to nag you, I'm just hitting this bug for a month, so I was hoping it's already known and there might be some workaround..will upload a better backtrace in few mins.. Created attachment 523961 [details]
hopefully a better backtrace
This is strange, the backtrace contains *some* debug symbols, but not all of them: #10 xfpm_brightness_setup (brightness=0x23e2ed0 [XfpmBrightness]) at xfpm-brightness.c:521 No locals. #11 0x0000000000411dc6 in xfpm_backlight_init (backlight=0x7faee8007e90 [XfpmBacklight]) at xfpm-backlight.c:381 No locals. I am starting to think there is something wrong with how upstream treats debugging symbols. xfce4-power-manger-debuginfo is installed, right? (In reply to comment #11) > I am starting to think there is something wrong with how upstream treats > debugging symbols. xfce4-power-manger-debuginfo is installed, right? - yes, according to ABRT everything is installed and even gdb is missing only the kernel-debuginfo (which ABRT never installs) - I even tried to use debuginfo-install just to make sure there is not a bug in ABRT and got the same: #10 xfpm_brightness_setup (brightness=0x23e2ed0 [XfpmBrightness]) at xfpm-brightness.c:521 No locals. #11 0x0000000000411dc6 in xfpm_backlight_init (backlight=0x7faee8007e90 [XfpmBacklight]) at xfpm-backlight.c:381 No locals. - I can try to compile it without optimizations to see if it give us a better bt, but later... Let's see if a simple rebuild helps: Rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=3363713 F16: http://koji.fedoraproject.org/koji/taskinfo?taskID=3363771 (In reply to comment #13) > Let's see if a simple rebuild helps: - no, it doesn't :( This is patch which I use to temporary workaround this problem: @@ -66,7 +66,8 @@ xfpm_brightness_xrand_get_limit (XfpmBrightness *brightness, RROutput output, gi XRRPropertyInfo *info; gboolean ret = TRUE; . - info = XRRQueryOutputProperty (GDK_DISPLAY (), output, brightness->priv->backlight); + //info = XRRQueryOutputProperty (GDK_DISPLAY (), output, brightness->priv->backlight); + info = NULL; I have a feeling it happens only with nouveau driver, can someone please confirm this? I'll test the nvidia blob later... Yes, Jiri. I can confirm this bug with nouveau. Scratch build with my workaround integrated (for those who don't like their laptop to run out of battery without warning...). Please note, that this is just a WORKAROUND without any warranty: F16: http://koji.fedoraproject.org/koji/taskinfo?taskID=3373474 rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=3373480 It doesn't crash with nvidia blob, so I believe it's xrandr+nouveau problem. I was about to mark this as a release blocker, because I believe it falls into this release blocker criteria: 8. In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ) - abrt notifies about this crash every time I log into XFCE session 9. All known bugs that can cause corruption of user data must be fixed or documented at Common F16 bugs - when the laptop runs out of battery without warning, it can definitely cause a data corruption or loss - but then I found XFCE doesn't fall into: "release-blocking desktops" Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- See bugs 736964 and 741394 This happens to me as well and I'm on radeon. In the above comment I meant to say that this sounds like exact same problem as in bug 736964 and bug 741394. (In reply to comment #18) > Scratch build with my workaround integrated (for those who don't like their > laptop to run out of battery without warning...). Please note, that this is > just a WORKAROUND without any warranty: I can confirm that this build does indeed help - I'm not seeing any coredumps anymore. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- log into xfce4 Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- I booted my laptop, a ThinkPad T30, and there appeared this message Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- booting up Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- Happens always when I log into xfce session (In reply to comment #26) > Package: xfce4-power-manager-1.0.10-1.fc16 > Architecture: i686 > OS Release: Fedora release 16 (Verne) > > Comment > ----- > Happens always when I log into xfce session Again that's using a radeon driver. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Fresh install of Fedora 16, this happens every time when I log in to XFCE Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- starting xfce Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- initial login of a system with a clean install of f16-beta and the /home directories copied from f15. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- It's reproducable immediatelly on my machine (HP Probook 4515s), on linve mode the app always crashing/reporting theat my battery is full/restarts - and after install simply gets an SIG5 sigtrap. The used Fedora is F16TC2. *** Bug 748343 has been marked as a duplicate of this bug. *** *** Bug 748322 has been marked as a duplicate of this bug. *** Should this become a F16Blocker? NTH? (In reply to comment #34) > Should this become a F16Blocker? NTH? No, XFCE is not a release blocking desktop. That's why it becomes NTH rather than Blocker. I am now adding a blocker on F16Blocker-xfce (which blocks F16-accepted) I can't reproduce the crash. I have an Intel N10 Family GPU here. Same here with an Lenovo x121e, F16 64Bit, AMD Drivers. Signal 5 every time ... Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This happens every time xfce power manager is started on my box. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- This happens every time xfce power manager is started on my box. Discussed at 2011-10-28 NTH review meeting, accepted as NTH as a 'blocker' issue in a non-blocking desktop. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- Happens every time I start up and log in. *** Bug 751859 has been marked as a duplicate of this bug. *** Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Fresh install of Fedora 16 XFCE live, this happens every time when I log in to XFCE. This seems to be a very annoying bug. Anybody analyzed the backtrace already? I think the interesting part is "BadName (named color or font does not exist)". I guess an issue with X or xfs. Found an old bug, maybe it's something similiar. https://bugzilla.redhat.com/show_bug.cgi?id=430416 Proposal to reassign this bug to Xorg. Status updated: Weird... I think that Fedora 16 logo shown during boot is to be expected. Sometimes it shows only a running stripe on the bottom of the screen -if that happens, my screen resolution changes and Xfce4-power-manager starts up without an error. If my memory serves, this happened to me in Fedora 15 xfce spin once. The upstream has the following suggestion to the problem: https://bugzilla.xfce.org/show_bug.cgi?id=7999#c3 which originally came from openSUSE https://bugzilla.novell.com/show_bug.cgi?id=718980 How about applying the fix? (In reply to comment #46) > Status updated: > Weird... I think that Fedora 16 logo shown during boot is to be expected. > Sometimes it shows only a running stripe on the bottom of the screen -if that > happens, my screen resolution changes and Xfce4-power-manager starts up without > an error. If my memory serves, this happened to me in Fedora 15 xfce spin once. Just a thought: It happens with nouveau. Nvidia users can't even use nvidia stable drivers because of Xorg 1.11.x. Is it possible to downgrade Xorg to previous version? I know how to do that only in Debian. (In reply to comment #48) > (In reply to comment #46) > > Status updated: > > Weird... I think that Fedora 16 logo shown during boot is to be expected. > > Sometimes it shows only a running stripe on the bottom of the screen -if that > > happens, my screen resolution changes and Xfce4-power-manager starts up without > > an error. If my memory serves, this happened to me in Fedora 15 xfce spin once. > > Just a thought: > It happens with nouveau. Nvidia users can't even use nvidia stable drivers > because of Xorg 1.11.x. Is it possible to downgrade Xorg to previous version? I > know how to do that only in Debian. Tested. Yum did not find other/older version of Xorg. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Power manager crashed on first login after install of XFCE default spin and crashes on every single login. Possible workaround (without nouveau): Try Nvidia 275.36 "long-lived branch" or 290.06 driver, they should work with Xorg 1.11.X Or log as root and do the following: 1. "init 3" 2. "yum -remove xorg-x11-drv-nouveau" 3. "yum install xorg-x11-drv-nouveau" 4. "init 5" 5. log in ...third restart, nouveau running and no error from xfce4-power-manager... yet I installed kmod-nvidia.x86_64 1:285.05.09-1.fc16.4 from rpmfusion. After rebuilding the initrd to blacklist nouveau, X started up with the nvidia driver and this problem is not happening for me any longer. This was on a Lenovo ThinkPad T510 with NVidia graphics, does seem to be a nouveau-related problem. > This was on a Lenovo ThinkPad T510 with NVidia graphics, does seem to be a
> nouveau-related problem.
This problem affects at least some noveau users, some AMD users, but no intel users, right?
AMD: my X300 is affected, my Radeon HD 3470 not.
I get those warnings, when run via xcfce4-power-manager --no-daemon from other prgrams, too. They seem so work flawless. Those warnings might be related, maybe not.
Reassign to X-bug? +1!
No that is not an NOUVEAU Bug, because on my Thinkpad x121e i have the same problem, and this is an AMD Chipset with an Radeon Graphic. Only on my T410, which is intel Graphic Based it works. Crazy that the bug is still alive all the development Cycle and in the Final F16. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- It happens every time I login (In reply to comment #54) > Crazy that the bug is still alive all the development Cycle and in the Final F16. Well, it seems that the developers or maintainers can't reproduce the behaviour with their own hardware. Otherwise, I would have expected a fast reply. And how can you justify that's the same bug ... :) Debian sid has a similiar problem: http://help.lockergnome.com/linux/Bug-641752-xfpm-change-default-values-backlight-brightness-i--ftopict543319.html "" I cannot change the default values of brightness (80% on AC and 20% on battery) that xfce4-power-manager claims it will set the display to when the computer is inactive for a specified amount of time. They appear to be changed, but as soon as I close it goes back to defaults. This is rather annoying as I want to change it to whatever I want. "" How is that related to this bug report? This looks more like bug 721166. (In reply to comment #55) > Package: xfce4-power-manager-1.0.10-1.fc16 > Architecture: x86_64 > OS Release: Fedora release 16 (Verne) > > Comment > ----- > It happens every time I login This is with Dell Inspiron 101z laptop with Radeon driver. (In reply to comment #53) > > This was on a Lenovo ThinkPad T510 with NVidia graphics, does seem to be a > > nouveau-related problem. > > This problem affects at least some noveau users, some AMD users, but no intel > users, right? > > AMD: my X300 is affected, my Radeon HD 3470 not. > > I get those warnings, when run via xcfce4-power-manager --no-daemon from other > prgrams, too. They seem so work flawless. Those warnings might be related, > maybe not. > > Reassign to X-bug? +1! Intel users are also affected. (tested on Core 2 Duo; Merom) I am an Intel user myself and I cannot reproduce the bug. (In reply to comment #60) > I am an Intel user myself and I cannot reproduce the bug. Christoph, this bug was reproduced for me only first 7-10 boot of system. I.e. on now this bug is not reproduced for me. Maybe this information will help you. I use nouveau driver. I can reproduce this on a Thinkpad T61 every time xfce4-settings-manager is launched. Using free graphics drivers (nvidia card inside). Has anyone tried to revert to an older version of the package? Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- The crash occured right after logging in Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- It crashes on load Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- The power manager of Xfce4 doesn't work. It happens at the startup of the environment. When I try to open the power manager, it appears an alert that says something like "The power manager of Xfce4 is not in execution, start it now?" If I agree, nothing happens. The power manager it's impossibile start it. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Upon first and every successive login, the power settings manager fails. Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- 1. install Fedora 16 from x64 DVD with xfce only desktop 2. reboot after installalation 3. XFCE Power manager crash I've rebuilt the package with a workaround from upstream report, packages can be found here: https://koji.fedoraproject.org/koji/taskinfo?taskID=3506524 - i686 https://koji.fedoraproject.org/koji/taskinfo?taskID=3506523 - x86_64 The crash is gone, with backlight control working through sysfs rather than xrandr. Note, I'm not xfce4-power-manager maintaier, use the packages at your own risk. Hi Maciek, as you write this I am working on an update. You have used the fix suggested in https://bugzilla.xfce.org/show_bug.cgi?id=7999#c3, right? (In reply to comment #69) > Hi Maciek, > > as you write this I am working on an update. You have used the fix suggested in > https://bugzilla.xfce.org/show_bug.cgi?id=7999#c3, right? Yes, that's correct. Alright. Is any of you seeing this crash in F15? xfce4-power-manager-1.0.10-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/xfce4-power-manager-1.0.10-2.fc16 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Package: xfce4-power-manager-1.0.10-1.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- It simply failed at login xfce4-power-manager-1.0.10-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. With this Fix, the problem has gone, xfce4-power-manager is working here on Nvidia and AMD Chipset without the Signal 5 problem ! THANX ! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** Bug 756393 has been marked as a duplicate of this bug. *** Problem still exists. After fresh install xfce power manager was crashing every time when logging to system. Now it's crashing every time when I plug in/out a power cable. My laptop is Dell Inspiron 1501. Did you update your system after the install? Make sure you are running xfce4-power-manager-1.0.10-2.fc16 and not 1.0.10-1.fc16. Try to reinstall some packages. It helped here after I did (accidently) brake the file system permissions. $ yum reinstall xfce4-power-manager upower xfce4-session Maybe there are more packages to consider about, dunno. Yes, I have the recent version and still when I plug a cord I see "process was killed by signal 11" in automatic bug reporting tool. I'm quite new to Fedora and I haven't learned how to use this tool yet. This is packet's description (sorry for russian language): Название: xfce4-power-manager Архитектура: x86_64 Версия: 1.0.10 Выпуск: 2.fc16 Объем: 3.3 M Источник: installed Из источника: updates Аннотация: Power management for the Xfce desktop environment Tried "yum reinstall xfce4-power-manager upower xfce4-session". Still no luck. Plugging power cord in/out causes power manager to crash. I'll try to attach some logs, not sure if this can help. Created attachment 537662 [details]
logs
Thanks for the logs, I will look at them later. Just to be sure: You did restart your computer or log out of the Xfce desktop after updating the package, right? Yes, I have rebooted my laptop and performed a test. I think changing power state (charging, on battery) causes xfce power manager to crash. I can see that icon changes and right after that it shuts down. |