name of bluray drive
by JD
/var/log/messages-20151116:Nov 9 09:21:35 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 9 09:45:59 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 9 10:00:16 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 9 15:07:52 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 9 18:37:10 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 10 09:25:59 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 10 11:44:02 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 10 17:13:40 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 11 08:50:12 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 11 11:32:21 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 11 08:50:12 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151116:Nov 11 11:32:21 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
/var/log/messages-20151207:Dec 3 19:57:34 localhost
org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path
provided!
However, since the update to latest kernel, these messages stopped.
But, /dev still has no device named blueray or br or br0. Ditto with dvd.
I have had to manually create dvd link to sr0.
Interestingly, cdrom is there.
since what user creates disappears at reboot, I have added the creation of
/dev/dvd in rc.local.
So, what should the blueray device be called in /dev? bd? br? bdr?
8 years, 3 months
F23 problem with mercurial and SSL
by Lester M Petrie
Hi
Since I have upgraded to Fedora 23, I am unable to communicate with the remote
mercurial repo that I work from. All the local commands I have tried work fine,
and I am even able to clone my local repo to another machine, but everytime I
try to communicate with the base repo, I get the following error message:
abort: error: [SSL: PARSE_TLSEXT] parse tlsext (_ssl.c:590)
I can still communicate with the base repo from a RHEL 6 machine, so it is
possible to get work done, but it is very clumsy. Does anyone have any
suggestions of how to correct the error?
--
Lester M Petrie
Bldg 5700, Room O305
Oak Ridge National Laboratory
Phone 865-574-5259, Email petrielmjr(a)ornl.gov
8 years, 3 months
looking for effective way to activate hugepages for libvirt
by thibaut noah
hello, i'm currently using libvirt for my win10 gaming vm and i wanted to
activate hugepages for it to improve performances.
It seems that my system will allow 1G hugepages however i failed to
activate it for libvirt, anyone here add the same issue and could point me
to a tutorial or something? I followed some documentation but it didn't fix
my issue.
I'm using last version of fedora
8 years, 3 months
systemd-tty-ask-password-agent: Invalid password file
by Frank White
Hi,
an other error I have is the following:
Dec 3 13:27:21 localhost kernel: Switched to clocksource tsc
Dec 3 13:27:30 localhost systemd-tty-ask-password-agent: Invalid
password file /run/systemd/ask-password/ask.x3yhfv
Dec 3 13:27:30 localhost systemd-tty-ask-password-agent: Failed to
show password: Bad message
Dec 3 13:27:30 localhost systemd-cryptsetup: Set cipher aes, mode
xts-plain64, key size 512 bits for device
/dev/disk/by-uuid/be252f25-e188-40e6-af85-cefb5722ceed.
Dec 3 13:27:31 localhost systemd-cryptsetup: Set cipher aes, mode
xts-plain64, key size 512 bits for device
/dev/disk/by-uuid/584d0452-78ac-4e8f-8ed2-b882b2165a82.
Dec 3 13:27:32 localhost systemd: Found device
/dev/mapper/luks-be252f25-e188-40e6-af85-cefb5722ceed.
Thank u very much for any help.
8 years, 3 months
F23 Server: unexpected network problem
by Cristian Sava
I Installed F23 Server with static address but after updating that it
got an automatic one. Why that? I consider that extremely dangerous.
That was verified and happened on different hardware boxes.
Do I miss something? Does anyone else saw that?
This is what I have (eno1 wired, eth1 not connected):
[root@s217 network-scripts]# ls ifcfg-*
ifcfg-eno1 ifcfg-eth1 ifcfg-lo
[root@s217 network-scripts]# cat ifcfg-eno1
HWADDR=00:1E:67:8B:B9:31
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eno1
UUID=8daf047d-e944-4305-b47f-6f2104edf9a2
ONBOOT=yes
IPADDR=111.222.333.217
PREFIX=27
GATEWAY=111.222.333.193
DNS1=111.222.333.254
DOMAIN=domain.me
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_PRIVACY=no
[root@s217 network-scripts]# cat ifcfg-eth1
cat: cat: No such file or directory
HWADDR=00:1E:67:8B:B9:30
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=eth1
UUID=0d9c850a-1545-481c-897f-84d4475e0377
ONBOOT=yes
[root@s217 network-scripts]# ip route
default via 172.18.0.1 dev eno1 proto static metric 100
172.18.0.0/16 dev eno1 proto kernel scope link src
172.18.172.146 metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src
192.168.122.1
111.222.333.193 via 172.18.0.1 dev eno1 proto dhcp metric 100
[root@s217 network-scripts]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel
state DOWN group default qlen 1000
link/ether 00:1e:67:8b:b9:31 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
link/ether 00:1e:67:8b:b9:30 brd ff:ff:ff:ff:ff:ff
inet 172.18.172.146/16 brd 172.18.255.255 scope global dynamic eno1
valid_lft 949sec preferred_lft 949sec
inet6 fe80::21e:67ff:fe8b:b930/64 scope link
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default
link/ether 52:54:00:62:c8:4a brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master
virbr0 state DOWN group default qlen 500
link/ether 52:54:00:62:c8:4a brd ff:ff:ff:ff:ff:ff
[root@s217 network-scripts]#
C.S.
8 years, 3 months
opening xxx.pat files
by Angelo Moreschini
Hi,
I got a file with suffix .pat (the extension is a Pattern Image file) and,
for what I could know, this kinde of files are used with photoshop...
II haven't photshp, so I looked for knowing how to open this file, and the
only suggestion that I found was to try (in Linux environment) with GIMP.
I hadn't success in this way, (using GIMP) so I would ask what other I can
try ...
Regards
Thank you
Angelo
8 years, 3 months
Why was YUM removed
by Junayeed Ahnaf
Hello,
I haven't been using Fedora for a while (2+ years) and yesterday I installed
fedora on dad's computer and see that they replaced yum with dnf. Now the
question is why was this done ? And who names their package manager as "DNF"
? The name seems pretty weird to be honest.
Thanks for any input on this one. Have fun
Junayeed Ahnaf Nirjhor
Twitter - @Nirjhor <https://twitter.com/Nirjhor>
8 years, 3 months
MP4 video on F23
by Patrick O'Callaghan
Since updating to F23 I've been unable to view MP4 videos (mostly H264
encoded). I know this is a proprietary format but it's what's out there
and what people tend to send when sharing in emails (from non-Linux
machines as a rule). The message from vlc (for example) is:
Codec not supported:
VLC could not decode the format "h264" (H264 - MPEG-4 AVC (part 10))
Usually the audio track is supported and plays, but no picture.
No doubt the answer is going to be "install gstreamer-ugly-whatever"
from RPMfusion, but I've done all that and still nothing. I didn't have
this problem under F22 (or earlier) so I have to wonder if something
hasn't been updated, but anyone with a solution is welcome to comment.
This is what I currently have installed:
gstreamer1-vaapi-0.6.1-1.fc23.x86_64
gstreamer-plugins-base-0.10.36-13.fc23.i686
gstreamer1-plugins-bad-free-1.6.1-2.fc23.x86_64
gstreamer1-1.6.1-1.fc23.x86_64
gstreamer-plugins-bad-free-0.10.23-28.fc23.x86_64
gstreamer-plugins-bad-nonfree-0.10.23-3.fc22.x86_64
gstreamer-plugins-ugly-0.10.19-18.fc23.x86_64
gstreamer1-plugins-base-1.6.1-1.fc23.i686
gstreamer-plugins-bad-0.10.23-7.fc22.x86_64
gstreamer1-plugins-bad-freeworld-1.6.1-1.fc23.x86_64
gstreamer-plugins-good-0.10.31-15.fc23.x86_64
gstreamer-plugins-espeak-0.4.0-7.fc23.x86_64
gstreamer1-plugins-base-1.6.1-1.fc23.x86_64
gstreamer-ffmpeg-0.10.13-15.fc22.x86_64
gstreamer-plugins-base-0.10.36-13.fc23.x86_64
gstreamer-plugins-bad-free-extras-0.10.23-28.fc23.x86_64
gstreamermm-0.10.11-8.fc23.x86_64
gstreamer1-plugins-ugly-1.6.1-1.fc23.x86_64
gstreamer-0.10.36-13.fc23.i686
gstreamer1-libav-1.6.1-2.fc23.x86_64
gstreamer-0.10.36-13.fc23.x86_64
gstreamer1-plugins-good-1.6.1-1.fc23.x86_64
gstreamer-tools-0.10.36-13.fc23.x86_64
gstreamer1-1.6.1-1.fc23.i686
poc
8 years, 3 months
xfce without a mouse
by Chris Murphy
Hi,
So I have only a bluetooth mouse, and GNOME lets me navigate by
keyboard only to get to Settings well enough I can then pair with the
mouse. I can't figure out how to do this at all on xfce (granted this
is Fedora 20 because that's the build Intel is using for their CPU
diagnostic tool).
Any suggestions?
--
Chris Murphy
8 years, 3 months