Finally found out that I was using the wrong syntax for the set-log-level
command. (Why did it say 'access denied' instead of 'bad syntax???)
Changing the log level all the way to emerg still had no effect. And in my
logs during reboot, I'm seeing this message:
systemd: [/etc/systemd/system.conf:11] Invalid log level'warn':
Operation not permitted
even though /etc/systemd/system.conf doesn't contain LogLevel=warn
(anymore) - it has LogLevel=emerg!
Why isn't systemd reading the CURRENT /etc/systemd/system.conf file? Why
does the command line setting seem to have no effect? Is systemd this
A little problem : When I click on the network applet (application in
terminal) it does not functionate and I get the following message :
nm-applet 2407 warning could not register with accessibility bus did
not receive a reply possible causes :
the remote application did not send a reply
the message bus security policy blocked the reply
network connection broken
nm-applet 2407 warning failed to register as an agent (32) an
agent with this ID already registered for this user.
Is there a way to solve this problem ?
Kind regards ,
Ger van Dijck.
New lenovo X1 carbon. Sometimes boots, sometimes hangs.
Today tried to boot and repeatly hung, saying
waitjob for /sysroot
Sounds pretty scary.
After repeated attempts, now it is booted OK.
Tried on latest kernel and also previous 1 or 2.
-- Those who don't understand recursion are doomed to repeat it
Every time I start firefox I'm getting the following message in the log
2015-03-26T08:43:05.397185+01:00 machine-name dbus: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.5658" (uid=1234 pid=27250 comm="/usr/lib64/firefox/firefox ") interface="org.freedesktop.NetworkManager" member="state" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=782 comm="/usr/sbin/NetworkManager --no-daemon ")
Does firefox really depend on NetworkManager? I don't have NetworkManager
installed, my network is started statically via /etc/rc.d/init.d/network,
so the message makes kind of sense. But really, firefox depending on
NetworkManager? That can't be right, can it?
Either way, is there a way to get rid of this log message other than
When I try to connect my ER9XPro USB device to my Fedora 21 server, it fails
to connect with:
[1024110.158374] usb 1-7: new full-speed USB device number 15 using xhci_hcd
[1024110.312216] usb 1-7: device descriptor read/64, error -71
[1024110.565928] usb 1-7: device descriptor read/64, error -71
[1024110.819660] usb 1-7: new full-speed USB device number 16 using xhci_hcd
[1024110.973497] usb 1-7: device descriptor read/64, error -71
[1024111.227212] usb 1-7: device descriptor read/64, error -71
[1024111.480928] usb 1-7: new full-speed USB device number 17 using xhci_hcd
[1024111.482576] usb 1-7: Device not responding to setup address.
[1024111.693836] usb 1-7: Device not responding to setup address.
[1024111.894473] usb 1-7: device not accepting address 17, error -71
[1024112.047316] usb 1-7: new full-speed USB device number 18 using xhci_hcd
[1024112.047415] usb 1-7: Device not responding to setup address.
[1024112.298755] usb 1-7: Device not responding to setup address.
[1024112.498815] usb 1-7: device not accepting address 18, error -71
[1024112.498836] usb usb1-port7: unable to enumerate USB device
It is a direct connection (no hub).
Cheers and thanks,
I was apparently missing something like the raid1 kernel
module in the initramfs in my fedora 21 partition, but
I disabled the mdmonitor service and removed the raid
filesystem from the /etc/fstab, yet the system still
could not boot. It spent several minutes trying to recognize
the raided disks then went into the dracut shell.
Should it really be utterly impossible to boot a system
that merely has raided disks connected to it which no
one is trying to reference? Should I make a kernel bug
I currently locally mirror Fedora release trees, as well as updates
and testing trees, and are all nfs mounted. I would like to do the 2
1 - What to issue at boot to include updates and testing trees? I
already use nfs parameter for the release tree.
2 - What do I do to use a newer anaconda package from the testing tree
instead of the one in the main tree? I guess I want to include a new
image to use from the newer anaconda? I already use the boot.iso from
the release tree and guess I need to create a new/custom image?
Thanks ahead of time,
"Best lil town on Earth!"
What is the best way in Fedora to handle the following situation?
- Package X depends on package Y
- Package Y is actually installed through custom compiling it (in $HOME/bin)
yum install X
will want to install Y
Specifically in my case X is kdenlive and Y is ffmpeg.
I compiled ffmpeg manually to have jack audio  support by following
the guide on the ffmpeg website . This means ffmpeg is in
~/bin/ffmpeg (also in my PATH). Before doing this I removed (with yum)
ffmpeg. Now if I try to:
yum install kdenlive
it will want to install ffmpeg.
Any suggestions, ideas, pointers are welcome.
 http://www.jackaudio.org/ (ffmpeg will add jack support if it finds
the jack development files)