Re: F28 beta: Flawless dnf update (almost!) + Bluetooth keyboard doesnt work + systemd-udev/upower eating CPU and continuously logging to journalctl + inaccessible man pages

2018-04-04 Thread Michal Jaegermann
On Wed, Apr 04, 2018 at 08:42:21AM +0100, Ankur Sinha wrote: > > Thanks. I've dropped a comment there. I'm seeing it with openmpi, while > you've filed it for mpich. Ah, yes, the same issue with a different package. You better file a separate bug report possibly with a reference to the earlier o

Re: F28 beta: Flawless dnf update (almost!) + Bluetooth keyboard doesnt work + systemd-udev/upower eating CPU and continuously logging to journalctl + inaccessible man pages

2018-04-04 Thread Ankur Sinha
> > This is https://bugzilla.redhat.com/show_bug.cgi?id=1533717 > originally filed on 2018-01-11. Additional comments that this breaks > not only rawhide are clearly appriopriate. > > The bug description also includes suggested fix which does not require > a deactivation of an offending module.

Re: F28 beta: Flawless dnf update (almost!) + Bluetooth keyboard doesnt work + systemd-udev/upower eating CPU and continuously logging to journalctl + inaccessible man pages

2018-04-04 Thread Ankur Sinha
On Wed, Apr 04, 2018 01:36:05 +0100, Ankur Sinha wrote: > Issue 1 > > > systemd-udev has been running continuously, hogging up a CPU, and > keeping my laptop at 75C. I'm not sure what it's doing. journalctl has > *many* lines like this, and from the looks of it, it's still logging > them:

Re: F28 beta: Flawless dnf update (almost!) + Bluetooth keyboard doesnt work + systemd-udev/upower eating CPU and continuously logging to journalctl + inaccessible man pages

2018-04-03 Thread Michal Jaegermann
On Tue, Apr 03, 2018 at 07:13:32PM -0700, Adam Williamson wrote: > On Wed, 2018-04-04 at 01:36 +0100, Ankur Sinha wrote: > > Turns out, this is set by the mpi/openmpi-x86_64 module, which should > > probably be appending to MANPATH instead of overwriting it? > > > > $ echo $MANPATH > > /usr/share/

Re: F28 beta: Flawless dnf update (almost!) + Bluetooth keyboard doesnt work + systemd-udev/upower eating CPU and continuously logging to journalctl + inaccessible man pages

2018-04-03 Thread Adam Williamson
On Wed, 2018-04-04 at 01:36 +0100, Ankur Sinha wrote: > Turns out, this is set by the mpi/openmpi-x86_64 module, which should > probably be appending to MANPATH instead of overwriting it? > > $ echo $MANPATH > /usr/share/man/openmpi-x86_64 > > Deactivating the module (module unload mpi/openmpi-x8

F28 beta: Flawless dnf update (almost!) + Bluetooth keyboard doesnt work + systemd-udev/upower eating CPU and continuously logging to journalctl + inaccessible man pages

2018-04-03 Thread Ankur Sinha
Hi! Just updated to F28 via DNF. Thanks for all the work. F28 looks like another solid release! The upgrade went off almost perfectly. I only ran into an issue with Pokerth, but that's already been reported[1]. I've run into a few issues after rebooting, though. Any help would be appreciated. I'm

Upower

2013-01-05 Thread Lawrence Graves
How to use the upower package. It sees myapc, keyboard and mouse but on the keyboard and mouse it does not register anything and shows a trouble sign. -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscri

Re: upower question?

2011-11-16 Thread Peter Gueckel
Adam Williamson wrote: > No, that sounds like exactly the bug discussed above, and I would bet > dollars to donuts you got an update to 'at' at the same time as you got > an update to the kernel. The 'at' update fixes the bug. Yes, that is correct. Along with the kernal was at-3.1.13-5.fc16. Tha

Re: upower question?

2011-11-16 Thread Adam Williamson
work just fine. Ok. So I download > >> > the xfce4-session source and start looking. Then I write a simple DBus > >> > utility to call upower directly, first to check I am allowed to suspend > >> > (which I am), then to call Suspend directly. Same behavior. Someth

Re: upower question?

2011-11-16 Thread Peter Gueckel
;suspend", my network drops...it looks >> > hopeful, then I see the network come back up. Of course, a simple cat >> > into sysfs >> > does suspend the system, so it can work just fine. Ok. So I download >> > the xfce4-session source and start looking. Then I write a s

Re: upower question?

2011-11-16 Thread Adam Williamson
; > then I see the network come back up. Of course, a simple cat into sysfs > > does suspend the system, so it can work just fine. Ok. So I download > > the xfce4-session source and start looking. Then I write a simple DBus > > utility to call upower directly, first to check I

Re: upower question?

2011-11-16 Thread Jon Masters
On Wed, 2011-11-16 at 14:21 +, Richard Hughes wrote: > On 16 November 2011 11:33, Jon Masters wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=754252 > > atd really shouldn't be restarting on resume anyway It's ok, like most things, it's being replaced by the init process so we don

Re: upower question?

2011-11-16 Thread Richard Hughes
On 16 November 2011 11:33, Jon Masters wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=754252 atd really shouldn't be restarting on resume anyway Richard. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test

Re: upower question?

2011-11-16 Thread Jon Masters
On Wed, 2011-11-16 at 06:25 -0500, Jon Masters wrote: > Ah well, I guess I was overdue for digging through that anyway. I'll > file or hunt down whatever bug is already reported. https://bugzilla.redhat.com/show_bug.cgi?id=754252 -- test mailing list test@lists.fedoraproject.org To unsubscribe

Re: upower question?

2011-11-16 Thread Jon Masters
> does suspend the system, so it can work just fine. Ok. So I download > the xfce4-session source and start looking. Then I write a simple DBus > utility to call upower directly, first to check I am allowed to suspend > (which I am), then to call Suspend directly. Same behavior. Somethi

upower question?

2011-11-16 Thread Jon Masters
Folks, These days xfce4-session-logout will call UPower over DBUS to request that the system Suspend when the user chooses to do so. upower will then determine whether the user is authorized to perform this amazing feat, and then a simple kernel interface is called to do the heavy lifting. On a