Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#39792 - [mate] upower-0.99.0-1 is causing startx to crash

Attached to Project: Community Packages
Opened by Erick Will (erickwill) - Wednesday, 09 April 2014, 17:46 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 15 April 2014, 15:22 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After update from testing repository I found that last update of package upower-0.99.0-1 is causing startx (X server) to crash.


Additional info:
upower-0.99.0-1 * package version(s)
* config and/or log files etc.


Steps to reproduce:
After update from testing repository and replace upower for version 0.99.0-1, it will crash startx.
   Xorg.0.log (9.4 KiB)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 15 April 2014, 15:22 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Wednesday, 09 April 2014, 18:21 GMT
Your bug is an error coming from the nvidia binary drivers. I also see you're still using acpid which is highly deprecated.
Comment by Erick Will (erickwill) - Wednesday, 09 April 2014, 18:34 GMT
What do you recommend to replace acpid? About nvidia binary causing X to crash, I fear that it's not only since I have an laptop that uses intel graphics and has the same problem. Any thought?
Comment by Doug Newgard (Scimmia) - Thursday, 10 April 2014, 01:16 GMT
I doubt it's the same log...
Comment by Doug Newgard (Scimmia) - Friday, 11 April 2014, 15:32 GMT
Hello? Need more information before I can assign this since we really have no idea where the bug is at this point.
Comment by Erick Will (erickwill) - Friday, 11 April 2014, 16:44 GMT
Ok, I tried to reinstall upower, from testing, and I did attach the log for your convenience. Please, let me know if you need something else and what exactly you need.
   Xorg.1.log (9.4 KiB)
Comment by Erick Will (erickwill) - Friday, 11 April 2014, 16:45 GMT
FYI, to keep X working with testing sources, I always update from testing sources and skip upower in order to have startx working without error.
Comment by Doug Newgard (Scimmia) - Saturday, 12 April 2014, 02:24 GMT
This log shows the problem being nvidia as well, did you attach the right log? If so, the problem definitely seems to be with nvidia.
Comment by Erick Will (erickwill) - Saturday, 12 April 2014, 11:22 GMT
Yes, Doug I attached the log that is created after the error message. At the end of the error there is an error address. This is the log attached here.
Is there any reason for another laptop that uses ATI and another laptop mine that uses Intel Graphics is showing the very same problem? I mean, is there any other log I may attach here? Because, this upower issue is not affecting only Nvidia under Testing Sources.
Comment by Doug Newgard (Scimmia) - Saturday, 12 April 2014, 14:45 GMT
Wow, what did you think I was asking for in comments three and four? We had already seen that log, so you posted it a second time? WTF?

The log posted shows a problem with nvidia. If you have a log showing something different, post it!
Comment by Erick Will (erickwill) - Saturday, 12 April 2014, 17:01 GMT
WOW... did you really read my entire last comment?! I did ask you about which log file should I attach as I don't know what log I should provide you. Very polite from your side, thought.
Here is a log from a laptop that uses INTEL Graphics.
   Xorg.1.log (8 KiB)
Comment by Doug Newgard (Scimmia) - Sunday, 13 April 2014, 16:13 GMT
The thing is, upower makes no sense here. It has nothing to do with DRM, which is where your errors are. We also don't have a bunch of people commenting here, voting on it, or threads in the forum or mailing list, so it can't be a wide spread problem, but it happens on three of your systems. It has to be something in one of your config files. I found a bug report on Ubuntu that points to ~/.profile throwing the same error. Can you try this with a different user with no custom configs?
Comment by Erick Will (erickwill) - Sunday, 13 April 2014, 16:55 GMT
Ok Doug, I gonna do that and feed ur back.
Comment by Doug Newgard (Scimmia) - Tuesday, 15 April 2014, 06:09 GMT
Another question, what WM/DE? https://www.archlinux.org/todo/upower-099-rebuild/

Shouldn't cause the DRM errors you're seeing, just a thought.
Comment by Erick Will (erickwill) - Tuesday, 15 April 2014, 13:45 GMT
DE is Mate. BTW after the upower-099-rebuild many Mate packages was updated and fixed the problem. Probably upower was in conflict with mate. Thanks

Loading...