Machine on a deadlock
by Paul Smith
Dear All,
I have a machine running Fedora 19, which is experiecning a deadlock.
What can I do to remedy this situation? I have tried
CRTL + ALT + F3
to get a login prompt to issue the reboot command, but the keyboard
seems to be also locked.
Thanks in advance,
Paul
9 years, 6 months
Mplayer failure message
by JD
$ mplayer "Fiona e Lisa - Pastyme with good company-aqYyOAzKOzw.webm"
MPlayer SVN-r37150-4.8.3 (C) 2000-2014 MPlayer Team
....
Playing Fiona e Lisa - Pastyme with good company-aqYyOAzKOzw.webm.
libavformat version 55.19.104 (external)
libavformat file format detected.
[lavf] stream 0: video (vp8), -vid 0
[lavf] stream 1: audio (vorbis), -aid 0
VIDEO: [VP80] 480x360 0bpp 25.000 fps 0.0 kbps ( 0.0 kbyte/s)
Load subtitles in ./
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 55.39.101 (external)
Selected video codec: [ffvp8] vfm: ffmpeg (FFmpeg VP8)
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 0.0 kbit/0.00% (ratio: 0->352800)
Selected audio codec: [ffvorbis] afm: ffmpeg (FFmpeg Vorbis)
==========================================================================
AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample)
Starting playback...
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
VO: [vdpau] 480x360 => 480x360 Planar YV12
A: 0.3 V: 0.0 A-V: 0.224 ct: 0.004 0/ 0 ??% ??% ??,?% 1 0
[VD_FFMPEG] DRI failure.
A: 134.6 V: 135.0 A-V: -0.380 ct: 0.010 0/ 0 3% 1% 1.1% 0 0
So, what's causing VD_FFMPEG failure?
The video/audio plays just fine.
Just curious about the failure message.
9 years, 6 months
Level of discourse: how we can be more effective (and, systemd)
by Matthew Miller
On Tue, Sep 23, 2014 at 05:18:57PM -0500, Dave Ihnat wrote:
> Let's decide that before we argue any more on the merits--or lack
> thereof--of systemd itself. If it's not going to change Red Hat's decision,
> then all we can meaningfully discuss here are discovered issues and any
> resolutions of same with the current implementation of systemd.
I'm breaking this into a new thread because, as you say, it's a separate
topic, and because it deserves a fresh start of its own.
Dave, thank you for your thoughtful response. If every thread about systemd
were at this level of civility, we wouldn't have a problem. But, clearly,
that's not what happens. In fact, these threads continually and quickly
devolve into personal attacks, name calling, and all manner of nastiness.
This is harmful to Fedora. It makes this list a bad place to get help with
real issues. It makes it a scary place for new users. It makes it a
miserable place for active developers and contributors. It doesn't just
increase the noise: over time, it reduces the signal.
And, it's not just by driving away helpful people. When the thread has been
reduced to a mud-fight, it means that I can't use it as meaningful evidence.
That's part of my job inside of Red Hat. I _want_ to be able to say "Fedora
users are really indicating that we're going to have a problem with this
direction. Take a look — we need to put resources into fixing this." But, if
someone does look, they'll see that we're mostly busy calling each other
fascists, proposing outlandish theories about GPL violation, willfully
misunderstanding each other in order to score Internet argument points, and
so on.
That does not carry any weight. In fact, if I were to try that, I would soon
find my own ability to convince anyone to listen to anything in Fedora
vanish. And that's not me just talking to Red Hat — it's the same thing
talking to basically _anyone_ who has any ability to do anything.
Let's help ourselves be heard by keeping the discourse at a constructive
level.
It doesn't have to be all about technical issues. We can talk about more
than just code. But, for code and everything else, let's not go in circles.
Repetition might work for propaganda, but it's not going to change Fedora
decision-making. There's actually very little here that isn't
well-understood all throughout Fedora engineering leadership — and, really,
I don't feel out of line in saying that I'm sure Red Hat leadership
understands the picture very well too. (Nothing's perfect; you make the best
decisions you can.) When there's something important that we can say that
_isn't_ understood or is otherwise urgent, I want that to stand out — not to
be piled under eight tons of muck.
Someone may be about to argue that those tons of muck must indicate that
people are unhappy, and therefore should be listened to. I've heard that
before. Let me ask: is it working? I assure you, it's not — and _more muck_
isn't going to help.
I'm not interested in stopping discussion of systemd. In fact, we'll need to
talk about it a lot more, because it is (and always was) an enabling
technology, not a simple replacement for init. But please, please, please,
let's do it like a community actually working together to make cool stuff.
If we don't, all that will happen is that this list will become completely
irrelevant. I don't want that to happen, and that's why I'm taking a
stronger stance on this.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 6 months
Problem in F20 with vfat filesystem on some sdhc card
by Joachim Backes
Hi all,
1. I created a vfat FS on a 32 GB SD-HC card
mkfs.vfat /dev/sdd1).
No errors
2. mount /dev/sdd1 /mnt
3. copy some huge file (about 17 GB) to /mnt with the cp cmd:
cp bigfile /mnt
This runs for some secs, but then fails with:
FAT-fs (sdd1): error, fat_free_clusters: deleting FAT entry beyond EOF
FAT-fs (sdd1): Filesystem has been set read-only
4. Trying the same with rsync:
rsync bigfile /mnt
runs some time, but then breaks:
rsync: mkstemp "/mnt/.bigfile.fqOS8w" failed: Read-only file system (30)
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1165) [sender=3.1.0]
How can I get rid from this? All help welcome.
Kind regards
Joachim Backes
--
Fedora release 21 (Twenty One)
Kernel-3.16.3-300.fc21.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
9 years, 6 months
color picker
by Mike Wright
Hi all,
Fedora 20 here. Anybody know the name of the color picker? (I think
that's what it's called. Allows clicking on a color and it gives the RGB).
TIA
9 years, 6 months
youtube-dl hangs
by JD
Hi all,
Sometimes, I see playlists that I like to download via youtube-dl (at
hotspots)
and listen to them at home at my leisure.
What's happening is that the download will get stuck at say track number 3
and never proceed. Restarting the download (of course, I always use the
options
-cktli) - that way I do not re-download already downloaded tracks.
I am at a hotspot that ususally downloads at up to 4M bytes/s.
I am only having this hang on youtube.
Is this a youtube policy thing?
9 years, 6 months
youtube-dl hangs
by JD
Hi all,
Sometimes, I see playlists that I like to download via youtube-dl (at
hotspots)
and listen to them at home at my leisure.
What's happening is that the download will get stuck at say track number 3
and never proceed. Restarting the download (of course, I always use the
options
-cktli) - that way I do not re-download already downloaded tracks.
I am at a hotspot that ususally downloads at up to 4M bytes/s.
I am only having this hang on youtube.
Is this a youtube policy thing?
9 years, 6 months
Dual monitors in Xfce4 fedora 20
by jarmo
Struggling with adding another monitor. With Arandr I can set both
monitors working so, that I can drag programs ffrom monitor to another.
BUT, monitors are in wrong order. I have DVI-0 and VGA-0, from same card
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370
[Radeon X300]
xrandr -q
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm
1280x1024 60.02*+ 75.02 72.05
1152x864 75.00
1024x768 75.08 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 60.00
720x400 70.08
DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
1280x1024 60.02*+ 75.02 72.05
1152x864 75.00
1024x768 75.08 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
640x480 75.00 72.81 66.67 60.00
720x400 70.08
S-video disconnected (normal left inverted right x axis y axis)
xrandr --output VGA0 --right-of DVI-0
warning: output VGA0 not found; ignoring
As said, I can make these monitors working with ARANDR, but when opning
xfce4 again, have to configure monitors again.
Tried to configure xorg.conf, no worky...
Xorg :1 -configure
X.Org X Server 1.14.4
Release Date: 2013-10-31
X Protocol Version 11, Revision 0
Build Operating System: 3.14.3-200.fc20.x86_64
Current Operating System: Linux oh1mrr.ampr.org 3.16.2-201.fc20.i686+PAE #1 SMP Mon Sep 15 20:10:13 UTC 2014 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.2-201.fc20.i686+PAE root=UUID=73d8e52e-eabd-485b-a4f9-53b8388ca52d ro LANG=fi_FI.UTF-8 rd.md=0 rd.lvm=0 rd.dm=0 quiet SYSFONT=lat0-16 KEYTABLE=fi-latin1 plymouth.enable=0 rhgb rd.luks=0 SYSFONTACM=iso15
Build Date: 27 June 2014 01:35:49AM
Build ID: xorg-x11-server 1.14.4-11.fc20
Current version of pixman: 0.30.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed Sep 24 21:14:28 2014
setversion 1.4 failed
List of video drivers:
nouveau
r128
sis
v4l
apm
ztv
siliconmotion
glint
geode
i740
amd
tdfx
neomagic
trident
modesetting
s3virge
sisusb
cirrus
mach64
rendition
mga
savage
i128
radeon
openchrome
ati
voodoo
dummy
intel
qxl
vmware
vesa
fbdev
(++) Using config file: "/root/xorg.conf.new"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
Number of created screens does not match number of detected devices.
Configuration failed.
(EE) Server terminated with error (2). Closing log file.
Googled much, but didn't found any help... Many people with different
distros same troubles, no solution.
Anybody experienced with this?
Jarmo
9 years, 6 months
Failed to start Ipmievd Daemon.
by JD
In boot.log:
boot.log:[FAILED] Failed to start Ipmievd Daemon.
It is not a catastrophic failure.
I am not sure what devices I have on the lapop that might be on
the ipmi bus. Could be useful for detecting failed or failing devices.
9 years, 6 months