how to enable audio as root ?
by sean darcy
I want to have sound when logged in as root. I don't care if it's a good
idea or not.
And I don't care if it's pulseaudio or alsa, or whatever.
I've tried pulseaudio -D, but the volume control never can connect to
the daemon. It just spams syslog with:
pulseaudio[6288]: Denied access to client with invalid authentication data.
I've added system-instance = yes to /etc/pulse/daemon.conf.
I've read
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Sy...
.
I've set up the users and groups as described.
.esd_auth exists in /var/run/puls
Does anyone have audio working as root?
sean
9 years, 1 month
Most likely OT: rsync to cifs mount
by Ranjan Maitra
Hi,
I am at my wits end with this, so I thought I would post here to see if anyone had any thoughts. The only connection with F21 (updated in all installed components) is that everything is on a F21 machine.
So, I have a cifs share mounted onto /mnt/space using the usual mount.cifs option with sec=ntlmv2.
I wanted to copy the following directory (kmeans) onto /mnt/space -- because I wanted to preserve permissions and structure, I tried rsync:
rsync -avSz --delete --progress kmeans/. /mnt/space/kmnsinit
So here is the problem:
The original directory has size:
% du -sh kmeans
156G kmeans
But the copying has continued on and on with no sign of ending (and we are at 378GB).
% du -sh kmnsinit
378G kmnsinit
I also tried without the . after the kmeans/ in the rsync command (though not sure why it would matter) but to no avail. (Same story, and note that it is not ending at 378G but going on, and chances are will go on for some more.)
Is it possible that since all things Windoze are bad, the cifs puts stuff all over the place and represents large files differently. Is it possible to however make it behave?
Does anyone have an explanation and solution for the above? I apologize again for the largely OT nature of this post.
Many thanks and best wishes,
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.
____________________________________________________________
FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
Check it out at http://www.inbox.com/earth
9 years, 1 month
Are md0_raid1 and md0_resync doing vast I/O normal?
by Tom Horsley
I setup a software raid on a couple of 4TB sata drives
not too long ago, and this morning I find md0_raid1
using about 10% of the CPU and having accumulated
about an hour of CPU time and md0_resync at about
half that, and gkrellm shows disks reads going at
about 180M (whatever units that happens to be :-).
Is this normal stuff for a software raid, or should
I be trying to find out what the heck is going on?
9 years, 1 month
question about burning and then reading (dd) to confirm sha256sum
by JD
After burning 3 DVD's, and reading them back to compute sha256sum.
all three of them generated these error messages during readback,
and all 3 messages show the error was past the 4gb offset.
Is this a media issue or is it the burner?
A side question: why does the block io layer assume that all media
have 512 byte sectors?
[ 977.862167] sr 1:0:0:0: [sr0] FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 977.862175] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 977.862179] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error
[ 977.862182] sr 1:0:0:0: [sr0] CDB:
[ 977.862186] Read(10): 28 00 00 22 33 38 00 00 40 00
[ 977.862197] blk_update_request: I/O error, dev sr0, sector 8965376
[ 981.369440] sr 1:0:0:0: [sr0] FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 981.369448] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 981.369452] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error
[ 981.369455] sr 1:0:0:0: [sr0] CDB:
[ 981.369458] Read(10): 28 00 00 22 33 78 00 00 40 00
[ 981.369471] blk_update_request: I/O error, dev sr0, sector 8965600
[ 986.544988] sr 1:0:0:0: [sr0] FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 986.544996] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
[ 986.545000] sr 1:0:0:0: [sr0] Add. Sense: Unrecovered read error
[ 986.545024] sr 1:0:0:0: [sr0] CDB:
[ 986.545027] Read(10): 28 00 00 22 33 70 00 00 02 00
[ 986.545043] blk_update_request: I/O error, dev sr0, sector 8965568
[ 986.545051] Buffer I/O error on dev sr0, logical block 1120696, async
page read
9 years, 1 month
cdrecord (schilling's) and wodim : Warning: Cannot read drive buffer.
by JD
How do I fix this?
The drive is:
$ dmesg | egrep -i 'cdrom|dvd|optical|optiarc'
[ 1.614989] ata2.00: ATAPI: Optiarc DVD+/-RW AD-7930H, 100A, max UDMA/100
[ 1.637908] scsi 1:0:0:0: CD-ROM Optiarc DVD+-RW AD-7930H
100A PQ: 0 ANSI: 5
[ 1.669987] sr 1:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram
cd/rw xa/form2 cdda tray
[ 1.670229] cdrom: Uniform CD-ROM driver Revision: 3.20
Thanx!
9 years, 1 month
radeon video +Fedora21 +steam games
by Paul Cartwright
I downloaded some steam games and I keep getting openGLX errors trying
to play them. Does it work with FLGRX video driver, or am I missing
something?
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
9 years, 1 month
kernel-3.19.3-200.fc21.x86_64 fails to boot
by Patrick O'Callaghan
kernel-3.19.3-200.fc21.x86_64
kmod-nvidia-3.19.3-200.fc21.x86_64-346.47-2.fc21.4.x86_64
The failure happens immediately after selecting the kernel from the boot
menu. A stack trace appears which I'll post if someone tells me how to
capture it.
poc
9 years, 1 month
One of the configured repositories failed (Fedora 21 - x86_64) when running "docker build" on F21:
by Kevin Wilson
Hi,
I have the follwing problem, running on Fedora 21, with
docker-io-1.5.0-2.fc21.x86_64:
I have this Dockerfile:
cat Dockerfile
FROM fedora
MAINTAINER tester
RUN yum -y update && yum clean all
RUN yum -y install httpd
When I am running
docker build -t test .
I get:
Sending build context to Docker daemon 3.072 kB
Sending build context to Docker daemon
Step 0 : FROM fedora
---> 834629358fe2
Step 1 : MAINTAINER tester
---> Using cache
---> 16e9f95d5ab0
Step 2 : RUN yum -y update && yum clean all
---> Running in 88b98222885a
One of the configured repositories failed (Fedora 21 - x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable fedora
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=fedora.skip_if_unavailable=true
Cannot retrieve metalink for repository: fedora/21/x86_64. Please
verify its path and try again
INFO[0042] The command [/bin/sh -c yum -y update && yum clean all]
returned a non-zero code: 1
Any ideas what can be the reason for this?
Regards,
Kevin
9 years, 1 month
sticky keys
by Stuart McGraw
And yet another problem with Fedora-21...
When I press my Shift keys quickly a few times (which I often
do unconsciously while thinking about what to type), I get a
notification that "sticky keys have been enabled". I then
get a lot of odd keyboard effects such as every word typed
being capitalized or the keyboard acting like the control key
is permanently pressed.
Googling seems to indicate this is an old problem going back
to the mid-2000's.
I tried one of the solutions I found: install xkbset and run
"xkbset -a" at login time via Application Autostart tab in
the Settings and Startup dialog (this is Xfce).
That seemed to work for a while but the problem's come back.
The auto-startup setting is still there, still enabled.
While I was typing this, something called "slow keys became
enabled making it impossible to continue typing this message
until I logged out and back in again.
None of the options in the accessibility applet are enabled
(I'm pretty sure, having worked around the problem of dialogs
not showing checkmarks).
What do I need to do to permanently put a stake in the throat
of this nasty little Sticky Keys virus?
<rant>
I seldom rant in public but I've got to say that installing
Fedotra-21 was the worst experience I have ever had installing
Linux (in terms of the endless amount of brokeness) -- and I
have been using Redhat going back to the 3.x days (that's *Redhat*,
not Redhat Enterprise; not Fedora). I don't think it is me. I
did a pretty plain vanilla install and except for some of the
usual audio/video stuff from rpmfusion, am using packages straight
out of the Fedora-21 repo. Plain vanilla hardware that ran
Fedora-15 fine for several years. Has Fedora become too focused
on release schedules and lost interest in quality control?
Or are all these problems coming from xfce?
9 years, 1 month
