odd ball in the yum updates
by Tim
In my recent yum update on F20, I noticed a file being added for
dependencies that I knew nothing about: clucene09-core
rpm -i reveals: This package contains an old and deprecated version of
clucene-core. You need it only if the software you are using has not
been updated to work with the newer version and the newer API.
rpm -e reveals: error: Failed dependencies:
libclucene.so.3 is needed by (installed) qt-x11-1:4.8.6-18.fc20.i686
This, that a new update dredges in a deprecated file, doesn't seem like
a good idea to me.
--
tim@localhost ~]$ uname -rsvp
Linux 3.17.4-200.fc20.i686 #1 SMP Fri Nov 21 23:59:46 UTC 2014 i686
All mail to my mailbox is automatically deleted, there is no point trying
to privately email me, I will only read messages posted to the public lists.
George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.
9 years, 5 months
A first in bug reporting
by Bill Davidsen
I was reporting a bug in fc21-x86 (polkitd hung 100% busy) and in the process
discovered that the last upgrade caused eog to generate warnings about the
"accessibility bus" which are not in the original install, at least from the
fc21-Live-MATE-x86_64 ISO I used.
Never found one bug while reporting another before, and I go back to Redhat
desktop 6 or so. Just a fun thing for me, trying fc21 on a weekend instead of
having time off.
--
bill davidsen <davidsen(a)tmr.com>
CTO TMR Associates, Inc
Unsigned numbers may not be negative. However, unsigned numbers may be
less than zero for suffiently large values of zero.
9 years, 5 months
Fedora 21: How do I get to the Software Selection screen as shown in the Install Guide?
by Jim Lewis
Hello all,
I am a bit embarrassed asking this, as it must be something simple I
overlooked. I have had no trouble installing the previous 20 versions of
Fedora, but 21 has me stumped. I am using the Fedora 21 server DVD
image, want the Mate base environment, and want to pick several add-ons.
In general I want the screen shown in section 5.4.7 of the Installation
Guide. When I attempt this the only base option is Fedora Server, and
there aren't nearly enough add-ons to pick from.
Thanks in advance for any help on this. I would really like to start
using 21.
Jim Lewis
RHCSA
Senior Software Engineer (retired)
9 years, 5 months
pdftk
by Ranjan Maitra
What is the story with pdftk?
$ sudo yum list pdftk
.....
Installed Packages
pdftk.x86_64 1.44-11.fc19 @fedora
Is it orphaned? That would be a bummer! I depend on it a lot.
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
____________________________________________________________
Receive Notifications of Incoming Messages
Easily monitor multiple email accounts & access them with a click.
Visit http://www.inbox.com/notifier and check it out!
9 years, 5 months
Re: Broken IR remote setup on Fedora 20
by Justin Moore
Thanks for all your replies. I didn't get a chance to test again until the
weekend. Stupid work week.
Responses inline.
> Assuming you are trying to use LIRC to process the remote signals: what
> does "cat /sys/class/rc/rc0/protocols" show? If more than one item is
> enclosed in square brackets, then something other than LIRC is getting
> those signals. There is now an in-kernel IR driver, this started sometime
> around F18. In order to get my remote to work with my MythTV system, I have
> to execute
>
> # echo lirc > /sys/class/rc/rc0/protocols
>
> After that, the above "cat" command shows only lirc bracketed, and then
> LIRC works fine.
>
I've tried using just LIRC and I've tried going through the native route --
the IR driver for MCEUSB appears to be in-kernel now -- and neither worked.
I tried your approach just now:
cat /sys/class/rc/rc0/protocols
rc-5 nec rc-6 jvc sony sanyo sharp mce_kbd [lirc]
ir-keytable shows:
=== start ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Enabled protocols: LIRC
Name: Media Center Ed. eHome Infrared
bus: 3, vendor/product: 0471:0815, version: 0x0000
Repeat delay = 500 ms, repeat period = 125 ms
=== end ir-keytable
My /etc/lirc/lircd.conf:
===
include "/usr/share/lirc-remotes/hauppauge/lircd.conf.hauppauge"
===
The LIRCD logs when I start LIRCD and then run IRW
=== start lirc logs
sh[2217]: lircd-0.9.0[2217]: lircd(devinput) ready, using
/var/run/lirc/lircd
lircd-0.9.0[2217]: lircd(devinput) ready, using /var/run/lirc/lircd
sh[2217]: lircd-0.9.0[2217]: accepted new client on /var/run/lirc/lircd
sh[2217]: lircd-0.9.0[2217]: initializing '/dev/input/event5'
lircd-0.9.0[2217]: accepted new client on /var/run/lirc/lircd
lircd-0.9.0[2217]: initializing '/dev/input/event5'
sh[2217]: lircd-0.9.0[2217]: removed client
sh[2217]: lircd-0.9.0[2217]: closing '/dev/input/event5'
lircd-0.9.0[2217]: removed client
lircd-0.9.0[2217]: closing '/dev/input/event5'
=== end lirc logs
But when I run IRW and click a bunch of buttons on the remote, nothing
shows up.
Total speculation: Have you checked to see if some "helpful" new
> feature is grabbing control of the remote? (Though I'm not sure
> how to check for such a thing). Maybe look through release notes
> for something about wonderful new and improved remote support?
>
I checked, and it's possible that X is actually grabbing the remote and
using it as a keyboard. I added a file
/etc/X11/xorg.conf.d/90-disable_mce.conf:
=== start 90-disable_mce.conf
Section "InputClass"
Identifier "Ignore MCE IR Keyboard/Mouse"
MatchProduct "MCE IR Keyboard/Mouse (mceusb)"
MatchIsKeyboard "true"
Option "Ignore" "true"
EndSection
Section "InputClass"
Identifier "Remote"
MatchProduct "Media Center Ed. eHome Infrared Remote Transceiver
(0471:0815)"
Option "Ignore" "true"
EndSection
=== end 90-disable_mce.conf:
When I start X I see this in the logs:
=== start Xorg.0.log snippets
[1366421.127] (II) config/udev: Adding input device Media Center Ed. eHome
Infrared Remote Transceiver (0471:0815) (/dev/input/event5)
[1366421.127] (**) Media Center Ed. eHome Infrared Remote Transceiver
(0471:0815): Ignoring device from InputClass "Remote"
[...]
[1366421.127] (II) config/udev: Adding input device MCE IR Keyboard/Mouse
(mceusb) (/dev/input/event16)
[1366421.127] (**) MCE IR Keyboard/Mouse (mceusb): Ignoring device from
InputClass "Ignore MCE IR Keyboard/Mouse"
[1366421.127] (II) config/udev: Adding input device MCE IR Keyboard/Mouse
(mceusb) (/dev/input/mouse2)
[1366421.127] (**) MCE IR Keyboard/Mouse (mceusb): Ignoring device from
InputClass "Ignore MCE IR Keyboard/Mouse"
=== end Xorg.0.log snippets
To me this says that X is ignoring this device and all its interfaces in
/dev/input.
So as far as I can tell, nothing is grabbing the IR receiver as input, lirc
recognizes the device and is able to attach clients to it, but neither
'irw' nor 'ir-keytable -t' sees anything from the remote.
More info:
ir-keytable says that it's using keytable 'table rc-rc6-mce', and my
/etc/rc_maps.cfg file has this:
=== start /etc/rc_maps.cfg
#driver table file
* rc-rc6-mce rc6_mce
=== end /etc/rc_maps.cfg
I copied /usr/lib/udev/rc_keymaps/rc6_mce to /etc/rc_keymaps/ and then
unplugged and re-plugged in my IR receiver. dmesg shows this:
=== start dmesg snippet
[1784677.192171] Registered IR keymap rc-rc6-mce
[1784677.192354] input: Media Center Ed. eHome Infrared Remote Transceiver
(0471:0815) as
/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/rc/rc0/input38
[1784677.192601] rc0: Media Center Ed. eHome Infrared Remote Transceiver
(0471:0815) as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/rc/rc0
[1784677.192775] input: MCE IR Keyboard/Mouse (mceusb) as
/devices/virtual/input/input39
[1784677.194120] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered
at minor = 0
=== end dmesg snippet
According to this the lirc_dev driver noticed it getting plugged in and
loaded the ir-lirc-codec module to expose button presses to userspace. BUT
here are all the kernel modules which are currently related to MCE:
=== start lsmod snippets
mceusb 28026 0
ir_mce_kbd_decoder 13214 0
rc_rc6_mce 12502 0
rc_core 27490 13
ir_sharp_decoder,lirc_dev,ir_lirc_codec,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,mceusb,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder,rc_rc6_mce
=== end lsmod snippets
In there I see kernel modules for plain old mceusb, the new in-kernel
keyboard decoder (ir_mce_kbd_decoder) the old lirc drivers (lirc_dev,
irc_lirc_codec) and rc_rc6_mce (whatever that is).
Which kernel module is grabbing the input? Are there multiple modules
trying to grab the input? If so, which one SHOULD be grabbing the input and
how do I disable the other ones? It feels like there are at least two
different systems trying to handle the IR input and all of them are failing
miserably.
Here are some other pages with LIRC-related configurations I've tried to
follow, none of which have worked for me:
http://atterer.org/mythtv-xmbc-remote-control-without-lirc
http://www.mythtv.org/wiki/MCE_Remote
This is all so frustrating. It just feels like IR configuration is being
shoved into the same bin as sound and printing: theoretically perfect but
practically a pain in the ass. Between this and continued PulseAudio
wonkiness I'm getting to the point where I feel it would be easier just to
get MythTV running on Ubuntu or Windows or a pre-Fedora-18 system.
Thanks,
-jdm
9 years, 5 months
lots of systemd warnings logged
by Neal Becker
I get a lot of these log messages:
Dec 13 08:22:26 nbecker1 systemd-sysv-generator[17437]: Could not find init
script for ebtables.service
Dec 13 08:22:26 nbecker1 systemd-sysv-generator[17437]: Could not find init
script for ebtables.service
Dec 13 08:22:26 nbecker1 systemd-sysv-generator[17437]: Could not find init
script for ebtables.service
Dec 13 08:22:26 nbecker1 systemd-sysv-generator[17437]: Could not find init
script for ebtables.service
Dec 13 08:22:26 nbecker1 systemd-sysv-generator[17437]: Could not find init
script for ebtables.service
Dec 13 08:22:26 nbecker1 systemd-sysv-generator[17437]: Could not find init
script for ebtables.service
Dec 13 08:22:26 nbecker1 systemd-sysv-generator[17437]: Could not find init
script for ebtables.service
How do I fix this?
--
-- Those who don't understand recursion are doomed to repeat it
9 years, 5 months
fedora 20, on my system, actually works only to line command.
by Angelo Moreschini
Hi,
currently my system (Fedora 20) start with the "command line interface",
and though I try to change the "target units" using <cntr-alt- F1, F3, F5
..> I never get the GUI (Gnome) .
But always (in each of the above cases), the command "systemctl
get-default", provides as output "grafical.target".
I tried the command: "systemctl isoltate graphical.target", but, after a
short time when it flashed the graphic symbol of Fedora (stylized letter
F), everything is back to the initial situation.
My question is :
how I can change Fedora to use the graphical mode (ie gnome)?
Thank you
Angelo
9 years, 5 months
Xfce and the windows key
by Robert Moskowitz
On F21
I have not found anything in the Xfce keyboard shortcut on using the
windows keys.
The menu button seems to be working ok.
The windows start button does not seem to do anything. I would think it
would bring down the applications menu, but it doesn't.
The start button + P does bring up the monitor switcher (better than
GNOME just rolling through the modes).
Start + L does not lock the screen.
Don't know of any others, but this is my experience so far. Start+L
would be nicer than ctl-alt-del.
9 years, 5 months
Re: (fedora) Re: after upgrade 20->21 gnome crashes when using rpmfusion's kmod-nvidia
by Jouk Jansen
linuxnutster at videotron.ca wrote on 12-DEC-2014 14:26:15.06
>On 12/12/2014 02:21 AM, Jouk Jansen wrote:
>> Joe Zeff wrote at 11-DEC-2014 18:34:39.83
>>
>>> On 12/11/2014 06:45 AM, Jouk Jansen wrote:
>>>> Does anybody know or point me in the direction of a solution?
>>>
>>> Follow the instructions here:
>>> http://forums.fedoraforum.org/showthread.php?t=204752 Don't worry about
>>> the way it refers only to old versions of Fedora; it's been kept
>>> up-to-date and works just as well now as it did then. As you'll see,
>>> it's a tad more complicated than simply installing one package and
>>> rebooting.
>>
>> Bassically this suggest avoid collisions with nouveau. However, even
>> removing nouveau and doing the dracut as suggested on the webpage, still
>> hangs when starting gdm
>>
>
>Hello, I have the same problem, but I'm a novice at troubleshooting.
>What is the precise location of the logfile I need?
What I listed came from :
/var/log/messages
Regards
Jouk
Pax, vel iniusta, utilior est quam iustissimum bellum.
(free after Marcus Tullius Cicero (106 b.Chr.-46 b.Chr.)
Epistularum ad Atticum 7.1.4.3)
Touch not the cat bot a glove
>------------------------------------------------------------------------------<
Jouk Jansen
joukj(a)hrem.nano.tudelft.nl
Technische Universiteit Delft tttttttttt uu uu ddddddd
Kavli Institute of Nanoscience tttttttttt uu uu dd dd
Nationaal centrum voor HREM tt uu uu dd dd
Lorentzweg 1 tt uu uu dd dd
2628 CJ Delft tt uu uu dd dd
Nederland tt uu uu dd dd
tel. 31-15-2782272 tt uuuuuuu ddddddd
>------------------------------------------------------------------------------<
9 years, 5 months
