Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upower local libusb revert #942

Closed

Conversation

sergei-mironov
Copy link
Contributor

That workarounds the coldplug problem

$ sudo ./libexec/upowerd -v
TI:18:38:27 Starting upowerd version 0.9.19
...
TI:18:38:27 registering subsystem : usb
TI:18:38:27 failed to coldplug /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/usb1

That workarounds the coldplug problem

$ sudo ./libexec/upowerd -v
TI:18:38:27     Starting upowerd version 0.9.19
...
TI:18:38:27     registering subsystem : usb
TI:18:38:27     failed to coldplug /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/usb1
<upowerd EXITS>
@vcunat
Copy link
Member

vcunat commented Sep 7, 2013

And what about updating upower and patching xfce?

https://bugzilla.xfce.org/show_bug.cgi?id=9952

@vcunat
Copy link
Member

vcunat commented Sep 7, 2013

Oh, better take directly their patch from master (probably the same as the last bug attachment).

http://git.xfce.org/xfce/xfce4-session/commit/?id=ae28aef315a7a6b90f1649ce6d1f30b842791cbf

@sergei-mironov
Copy link
Contributor Author

This patch (I hope) fixes the original shutdown problem, but it does nothing to cure upower from crashing (early exiting). Others may be using it as well, so I'd suggest to keep the topic libusb hack.

@vcunat
Copy link
Member

vcunat commented Sep 7, 2013

I thought someone suggested an update should solve that.

@vcunat
Copy link
Member

vcunat commented Sep 7, 2013

Oh, this is a patch for something else, already solved. I'm sorry, probably too tired now.

@sergei-mironov
Copy link
Contributor Author

Yes, seems like that. And they don't ship files like configure.in.in with the tarball, so the patch couldn't be applied as is.

@offlinehacker
Copy link
Contributor

So what about applying this pull request and reverting it when new release
comes?

On Sat, Sep 7, 2013 at 10:21 PM, Sergey Mironov [email protected]:

Yes, seems like that. And they don't ship files like configure.in.in with
the tarball, so the patch couldn't be applied as is.


Reply to this email directly or view it on GitHubhttps://github.com//pull/942#issuecomment-24008916
.

@vcunat
Copy link
Member

vcunat commented Sep 7, 2013

I was a bit confused. The bugzilla patch isn't upstreamed yet. It does apply against git trees, as they run autoreconf before every release (as is usual). However, during compilation I run into some problem... probably let's apply this fix until upstream settles a bit :-)

@vcunat
Copy link
Member

vcunat commented Sep 8, 2013

Pushed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants