Re: Can't get sound to work

[Joel Roth]

Charlie wrote:
> On Fri, 16 Jan 2015 19:56:31 -1000 Joel Roth sent:
> 
> > For now, you do have have a working audio system sitting
> > atop your Intel soundcard(s).
> 
> Yes thank you.
> 
> I have purged pulseaudio again. Never having used it found Alsa was
> always fine till recently when alsa didn't do it for me when using VLC.
> But then pulseaudio didn't either.
> 
> However alsaplayer in the GUI only plays half the song and chokes.
> 
> Aplay plays the songs fine in full, no glitch when invoked on the
> command line.
> 
> VLC doesn't produce any sound. But then I can live without it.
> Especially since I have discovered how to add several songs to aplay on
> the commandline, takes a bit more typing the way I do it, but then
> that's also fine.

try vlc with the 
--alsa-audio-device default
--alsa-audio-device hw:0,0

It looks like can specify the channel count 
(although using '6' to get stereo seems weird.)
>From vlc --longhelp:

  --alsa-audio-channels {1 (Mono), 6 (Stereo), 102
(Surround 4.0), 4198 (Surround 4.1), 103 (Surround 5.0),
4199 (Surround 5.1), 4967 (Surround 7.1)}

cheers,

 
> It's never so bad if you know how to do something, it's just a pain
> when you don't and you need to scrounge through all manner of websites
> to discover how it might work, often wasted because you've looked in
> the wrong place and it doesn't.

Man pages and mailing lists are helpful. There is no way to 
configure your system without some knowledge, or willingness
to get experience.

> I recall reading a Linux user/developer once writing that he was almost
> sick of Linux because whenever you tried to do something you had to
> learn how to do it. That in Windows it just worked.

I did a Windows 7 system restore for a friend's notebook
that took forever. Many times more difficult than what
I can do with unix tools like rsync.
 
> It was interesting, and I know that when I want to do something and
> have to troll the net to find a way to do it because it needed a tweak,
> it could be frustrating. But I always blamed myself because I made the
> choice to use Debian "testing" instead of stable where I assume
> everything just works?

No, you will always have issues configuring your system to
suit your hardware, networking environment and personal
needs. You cannot escape some overhead in administering
a system. 

cheers,

joel
 
> Anyway thank you,
> Charlie
> 
> -- 
>   Registered Linux User:- 329524
>   ***
> 
>   If I seem to boast more than is becoming, my excuse is that I
>   brag for humanity rather than for myself. Henry David
>   Thoreau
> 
>   ***
> 
>   Debian GNU/Linux - just the best way to create magic
> 
>   -
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/20150117171626.75cf67bd@taogypsy
> 

-- 
Joel Roth
  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150117065129.GB26400@sprite

Re: Can't get sound to work

[Charlie]

On Fri, 16 Jan 2015 19:56:31 -1000 Joel Roth sent:

> For now, you do have have a working audio system sitting
> atop your Intel soundcard(s).

Yes thank you.

I have purged pulseaudio again. Never having used it found Alsa was
always fine till recently when alsa didn't do it for me when using VLC.
But then pulseaudio didn't either.

However alsaplayer in the GUI only plays half the song and chokes.

Aplay plays the songs fine in full, no glitch when invoked on the
command line.

VLC doesn't produce any sound. But then I can live without it.
Especially since I have discovered how to add several songs to aplay on
the commandline, takes a bit more typing the way I do it, but then
that's also fine.

It's never so bad if you know how to do something, it's just a pain
when you don't and you need to scrounge through all manner of websites
to discover how it might work, often wasted because you've looked in
the wrong place and it doesn't.

I recall reading a Linux user/developer once writing that he was almost
sick of Linux because whenever you tried to do something you had to
learn how to do it. That in Windows it just worked.

It was interesting, and I know that when I want to do something and
have to troll the net to find a way to do it because it needed a tweak,
it could be frustrating. But I always blamed myself because I made the
choice to use Debian "testing" instead of stable where I assume
everything just works?

Anyway thank you,
Charlie

-- 
Registered Linux User:- 329524
***

If I seem to boast more than is becoming, my excuse is that I
brag for humanity rather than for myself. Henry David
Thoreau

***

Debian GNU/Linux - just the best way to create magic

-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150117171626.75cf67bd@taogypsy

Re: Can't get sound to work

[Joel Roth]

On Sat, Jan 17, 2015 at 01:27:31PM +1100, Charlie wrote:
> On Fri, 16 Jan 2015 15:11:24 -1000 Joel Roth sent:
> 
> > Robert Latest wrote:
> > > With aplay -D hw:0,0 it still works.  
> > 
> > You're 99% to the destination.
> > 
> > IIRC, directly addressing the sound device
> > as hw:0,0 takes the whole device, will not
> > allow software mixing of audio streams from
> > other applications.
> > 
> > It may be worth trying the 
> > 
> > aplay -D default testfile.wav &
> > aplay -D default testfile.wav
> > 
> > And you should hear two streams playing together.
> > 
> > At least, it works on my system without asoundrc.
> > 
> > Regards,
> > 
> > Joel
> 
> Thanks Joel,
> 
> Using: aplay -D default testfile.wav &
> 
> Without pulse audio installed, I get sound.

Yay.
 
> Using: aplay -D default testfile.wav &
> 
> With pulseaudio, there is no sound but pavucontrol shows that there is
> some sound being relayed to the earphones?

> So sound is still a wraith in Debian. [laughing]

The ALSA project has a Linux kernel driver for your
soundcard.  Many programs, libraries, applications, plugins,
frameworks and APIs target ALSA.[1]  If you're involved in
music or audio production and need to combine audio
applications, there is JACK.

So, have a coffee and doughnut, or beer and pizza!

Now maybe you want pulse audio. Why? Because maybe some app
(Skype?) or Desktop Environment demands it.

Okay, that's a lot of bloat. But you're choosing to pull
that bloat into your software stack. Or maybe it is just
your DE packager's choice.

In any case, you can probably debug it given enough
attention. Any list responsive to pulse audio issues should
be a help. 

For many audio issues, you can go to the Linux Audio Users
mailing list, but even the geniuses and gurus who frequent
that list are mostly ignorant of the dark ways of PA. 

A few have found and published ways to use both JACK and
PA.[2]

For now, you do have have a working audio system sitting
atop your Intel soundcard(s).

cheers,

Joel


1. http://wiki.linuxaudio.org/apps/start
2. http://jackaudio.org/faq/pulseaudio_and_jack.html

> Be well,
> Charlie
> -- 
>   Registered Linux User:- 329524
>   ***
> 
>   If anything in nature strikes you as ugly, you are not
>   appreciating its diversity. ...anon
> 
>   ***
> 
>   Debian GNU/Linux - just the best way to create magic
> 
>   -
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/20150117132731.4e4e4d61@taogypsy
> 

-- 
Joel Roth
  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150117055631.GA26400@sprite

Re: An experiment in backup

[Kevin O'Gorman]

On Fri, Jan 16, 2015 at 8:14 AM, Rob Owens  wrote:

> On Thu, Jan 15, 2015 at 08:47:01PM -0800, Kevin O'Gorman wrote:
> > On Thu, Jan 15, 2015 at 8:41 PM, David Christensen <
> > > There are two basic kinds of "backups":
> > >
> > > 1.  File system -- e.g. a copy of the files and directories on an
> mounted
> > > and operating drive.
> > >
> > > 2.  Raw binary image -- e.g. a copy of the bytes on a drive taken when
> the
> > > drive is powered, but the partitions, volumes, file systems, etc., are
> not
> > > mounted.
> > >
> > >
> > > For system drives, the former won't work; you need the later.  I
> connect a
> > > large hard drive (to hold the images), boot Debian installation media
> into
> > > rescue mode, and use 'dd' to backup/ restore system drive raw binary
> images.
> > >
> > > I was hoping for some details on why this won't work on system drives,
> or
> > conditions under which it just might.  Another user has suggested I read
> > https://help.ubuntu.com/community/BackupYourSystem/TAR which suggests
> that
> > it actually should work.
>
> Image backups are definitely easier for doing disaster recovery of an
> entire machine.  And when you have that kind of problem, you may really
> appreciate having to do less work / make fewer decisions.
>
> But filesystems backups can be used for disaster recovery.  I've done
> it.  One potential problem is that on a running system, things change.
> So at the start of your backup, you backup file A.  At the end of the
> backup, you backup file Z.  But in the middle of the backup, both file A
> and file Z have changed.  And some software requires that file A and
> file Z be in sync.  When you restore, those files are not in sync and
> you could have a problem.
>
> In practice, I haven't seen this be a problem much on home desktop
> machines.  But that's not to say it couldn't be a problem.
>
> Another thing to consider is hardware changes.  This can make certain
> devices be named differently when you restore.  eth0 becomes eth1, and
> /etc/network/interfaces doesn't have a stanza for eth1.  /dev/dvd
> becomes /dev/dvd1, and your cd burner was set to look for /dev/dvd which
> no longer exists.  These things can be fixed in the /etc/udev/rules.d
> directory.
>
> UIDs of disk partitions will change.  If /etc/fstab references UIDs, you
> need to update it.  Same for /boot/grub/grub.cfg, although for that you
> run update-grub2 from the restored system (you'll need to boot with a
> live cd and chroot, or you'll need to boot with Super Grub Disk or
> similar).  You will also need to install the bootloader on the new hard
> disk.  'grub-install /dev/sda'
>
> The UUID and Grub issues don't show up when restoring from an image
> backup, but the network card and cd burner issues can.
>
> There are a lot of free software backup solutions available.  I would
> recommend using one of those, unless this endevour is more for learning
> experience than anything else.
>
> Backuppc may be overkill for your case, but it's pretty good.  It will
> do file pooling and compression, so keeping multiple backups of one or
> more machines doesn't take up much disk space.
>
> This is partly a learning experience, and partly to take control of what's
happening.
I have plenty of backup capacity.  Aside from using compression I see no
need
to worry about optimizing storage.  Instead, I like having each backup be
self-contained
and easily identifiable.

I have roughly 32TB of 2-TB disks dedicated to backups (!) plus smaller
older ones.
My three machines are quite modest in size.  Except for one with a huge
stripe array
for temporary stuff related to a hobby of mine, not subject to backups.  I
have
backups running back for years, covering machines I recycled as much as a
decade ago.
All my drives are such that I have a USB drive dock for them, or they come
with a
USB interface.  USB seems likely to stick around for a while.

My hardware is stable enough I'm not worried about naming confusions.
Almost
everything is GPT partitions.  Everything is identified by UUIDs -- those
have no
need to change and I know how to set them on an existing partition to match
anything
in /etc/fstab.

I back up the GPT itself (both copies) and every partition other than
swap.  Just in
case I want it later.

I've not tried other solutions.  I worry that the ones folks seem to like
most do more
than I need or want in terms of management.  I want my stuff where I can
see it, so
to speak, and where I can use the ancient tools (tar, dd, gzip and so on)
to work with it.

I have already spent too much of my life dealing with incompatibilites,
problems with
software and format changes and a whole raft of other stuff.  I want it
simple, and I
want it to be obvious.  I use directory and file names to help make it so,
and every
backup includes the scripts that were used to make it.  It's all bash
script and tools
that were known at the time I started using Linux -- roughly 1993.

I'm a bit ashamed I've never tried (or needed)

Re: An experiment in backup

[Kevin O'Gorman]

On Fri, Jan 16, 2015 at 3:54 AM, Tom H  wrote:

> On Thu, Jan 15, 2015 at 10:19 PM, Kevin O'Gorman 
> wrote:
> >
> > I have a tar backup of the entire system, excluding /sys, /proc and /dev.
> > I have a tar backup of a bind-mount of /dev.
> > These were taken while the system was running, but quiet. I did it this
> > way because I cannot get the system to boot into single user mode.
> Putting
> > "single" on the end of the "linux" like results in a black screen.
> >
> > I restored these, created /sys and /proc, and tried to boot the resulting
> > partition. It boots, but X does not come up, or even seem to try. I can
> do
> > a console login to my usual account, and stuff is there.
>
> What commands did you run to back up and restore the system?
>
> For the Linux part (there's also Windows on some of my machines) it's all
tar.


> Is '/tmp' a tmpfs filesystem? If not, did you back up and restore it?
>

It's a subdirectory of /, not a mount point on the machine in question.

>
> Did you exclude '/run'? If not, did you restore it?
>
I exclude /var/run and /var/lock

>
> Did you create '/proc' and '/sys' with the right ownership and mode?
>
> Hmm.  They appear right. 755 owned by root.


> If this is a Debian system, is it a non-standard install that doesn't
> use udev (AFAIK this is still possible)? If not, there's no point in
> backing up and restoring '/dev'.
>
> It's vanilla Xubuntu.  I back up and restore what's on the hard drive via
a bind mount.
I wasn't convinced there wasn't something in the boot process that needed
it.


> If this is an Ubuntu system, the default '(recovery)' grub entry will
> have 'nomodeset' appended. Try that when you add 'single'.
>
> Are you using a DM?

 A what? Xubuntu uses xfce4 if that answers the question.

Are you using a WM or a DE?
>
A what?

>
> Have you looked at the logs? Especially Xorg.0.log and xsessions-errors.
>
Xorg logs seem normal
I don't see any xsessions-errors file


> Can you launch X after logging in to the console?
>

I don't know how.

>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> https://lists.debian.org/CAOdo=swjn5qggmjo7qta_2otefqgzihwpn35hykxshk4_oa...@mail.gmail.com
>
>


-- 
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.

Ric Moore

[Gene Heskett]

Greetings, back on the old 10.04.4  LTS LUCID drive.

Ric, installing that mesa library for firefox made firefox work better, & 
no squawking about the missing file.

But, it pulled in 19 other packages either for additional deps, or 
whatever, then finished up on a rescan, wanting to update about 100 other 
packages.  Which I didn't let it do.

However, when I went to reply to the mail, I fond that in addition to 
wanting to remove kmail without replacing it with an even newer version, 
whatever it pulled rather instantly removed kmails ability to send mail, 
claiming the address was bogus.  But it never had time to ping the mail 
server, it was an instant rejection.


So now I am back on the old LUCID based install.  Where hopefully I can 
send an email.  With kmail.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201501162146.19054.ghesk...@wdtv.com

Re: Can't get sound to work

[Charlie]

On Fri, 16 Jan 2015 15:11:24 -1000 Joel Roth sent:

> Robert Latest wrote:
> > With aplay -D hw:0,0 it still works.  
> 
> You're 99% to the destination.
> 
> IIRC, directly addressing the sound device
> as hw:0,0 takes the whole device, will not
> allow software mixing of audio streams from
> other applications.
> 
> It may be worth trying the 
> 
> aplay -D default testfile.wav &
> aplay -D default testfile.wav
> 
> And you should hear two streams playing together.
> 
> At least, it works on my system without asoundrc.
> 
> Regards,
> 
> Joel

Thanks Joel,

Using: aplay -D default testfile.wav &

Without pulse audio installed, I get sound.

Using: aplay -D default testfile.wav &

With pulseaudio, there is no sound but pavucontrol shows that there is
some sound being relayed to the earphones?

So sound is still a wraith in Debian. [laughing]

Be well,
Charlie
-- 
Registered Linux User:- 329524
***

If anything in nature strikes you as ugly, you are not
appreciating its diversity. ...anon

***

Debian GNU/Linux - just the best way to create magic

-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150117132731.4e4e4d61@taogypsy

Re: Can't get sound to work

[Joel Roth]

Robert Latest wrote:
> With aplay -D hw:0,0 it still works.

You're 99% to the destination.

IIRC, directly addressing the sound device
as hw:0,0 takes the whole device, will not
allow software mixing of audio streams from
other applications.

It may be worth trying the 

aplay -D default testfile.wav &
aplay -D default testfile.wav

And you should hear two streams playing together.

At least, it works on my system without asoundrc.

Regards,

Joel
 
> OK, now trying to remove all pulse-related stuff.
> 
> Thanks
> robert
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/20150116205622.3f0fc1af@dotcom.mfs32
> 

-- 
Joel Roth
  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150117011124.GB7790@sprite

Re: firefox compaining about missing library

[Sven Joachim]

On 2015-01-16 20:56 +0100, Gene Heskett wrote:

> On Friday, January 16, 2015 12:07:14 PM Liam O'Toole did opine
> And Gene did reply:
>> On 2015-01-16, Gene Heskett  wrote:
>> > Greetings;
>> > 
>> > Does anyone know where to find, for Wheezy, this library?
>> > VDPAU backend libvdpau_nouveau.so?
>> 
>> The library belongs to the mesa-vdpau-drivers package[1], which is not
>> available in wheezy, nor in wheezy-backports. It's used for
>> hardware-accerated video playback.

Not that nouveau does not provide video decoding unless you extract
proprietary and not readily available firmware from the NVIDIA blob[1].

> Humm, how incompatible would it be with the rest of wheezy?

Badly.  It needs libllvm3.5 which is not available in wheezy, plus newer
versions of libc6 and libstdc++6.

Cheers,
   Sven


1. http://nouveau.freedesktop.org/wiki/VideoAcceleration/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87iog6l73n@turtle.gmx.de

Re: An experiment in backup

[Ric Moore]

On 01/16/2015 12:32 AM, Kevin O'Gorman wrote:

On Thu, Jan 15, 2015 at 9:03 PM, David Christensen
mailto:dpchr...@holgerdanske.com>> wrote:

On 01/15/2015 08:47 PM, Kevin O'Gorman wrote:

I was hoping for some details on why this won't work on system
drives, or
conditions under which it just might.  Another user has
suggested I read
https://help.ubuntu.com/__community/BackupYourSystem/TAR
 which
suggests that
it actually should work.


That would require an in-depth understanding of the Linux kernel,
which I don't have.  (My answer was geared towards practical system
administration; it works reliably for me.)

If you want to learn everything required to explain why a file
system level self-backup of an operational system drive won't work,
or how to make it work (and how to restore it), more power to you.
If you would care to post what you find, I'd like to read it.


No promises, but I might just take you upon that.  I don't think it will
take any kernel knowledge, but some of the daemons may be an issue.  As
a first step, I may take a self-dump then do a fast reboot to another OS
or partition, restore the dump to a new place and do a compare.  If the
list of suspects (outside of /tmp and such) is huge, I may give up.  If
not, I may learn something.

I care because I like to have a lot of free space in my partitions, but
I hate to use backup time and space on the holes.


Maybe just back up files? Backing up and restoring /proc might be 
problmatic as it is such a moving target that depends on what you were 
doing system wide at the time. Restoring it (IMHO) would be akin to time 
travel. :) Ric




--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54b98185.6080...@gmail.com

Re: Can't get sound to work

[Ric Moore]

On 01/16/2015 03:51 PM, berenger.mo...@neutralite.org wrote:

Le 16.01.2015 19:24, Robert Latest a écrit :

On Thu, 15 Jan 2015 19:43:23 -0500
Ric Moore  wrote:


On 01/15/2015 03:54 PM, Hans wrote:
> First questions:
>
> Are you running pulseaudio or alsa?


I don't know. I seem to have both on my system. I don't know what the
difference is, or if one is running on top of the other, or if they are
fighting over my soundcard. How would an application that wants to play
sound figure out which system to use?


There are several people more knowledgeable than me around here, but,
AFAIK, alsa is the lowest level sound manager.
If I am not wrong, pulse audio is built on it. Note that I never tried
PA: alsa always worked just fine for me, so why should I try it?
I understand the linux Audio stack like this:

Alsa ==> OSS
   ^
   |
   ^
/  \
PA  J

Alsa is better (why? No idea, just what people says...) than OSS, and
then you have 2 frameworks which works over Alsa. PulseAudio (PA, which
seems to be POSIX and windows compatible), and Jack (J, which seems to
be used by professional applications, for real-time stuff and other.

If you simply want sound from flash-player, iceweasel and mplayer...
well, removing PA may help you, and it will remove something you do not
necessarily need. And, in my opinion, less code running on my computer
means less surprises (on my computer), so it's the way I choose. But, I
am a minimalist lover (well, at least in computing... for beers per
example I have different tastes ;) ).

Note that I have no opinion about the quality of pulse audio and jack.
Plus, in some cases, I had problems with microphones with Alsa. Maybe in
those situations PA or jack would have helped me. Never tried, it was
not important enough for me.


Maybe if the OP mv;d that file to another name,
rebooted and ran alsamixer first, then add pavucontrol along with
pulse, he might have a better experience, IMHO.


I'll try that (have to install first). If it works, can I then purge all
ALSA-related stuff from my system? Or could I also remove all
pulse-related stuff and keep ALSA?


If you purge alsa-related stuff, you will end with no sound at all.
Alsa means "Advanced Linux Sound Architecture". It seems to be a driver
replacement for OSS.
In short, it would be like removing your nouveau/nvidia/intel/whatever
driver and trying to run Xorg or weston... Xorg and weston would be PA
and Jack, the driver would be alsa. That's what I understand, at least.


Jack confuses the heck out of me, and I think it relies on a realtime 
kernel. I leave that to the true audiophiles who need that degree of 
response for mostly sound only applications. You are right, alsa is a 
must have installed. Pulse will only work with a working alsa setup.




--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54b97e68.8040...@gmail.com

Re: Can't get sound to work

[Ric Moore]

On 01/16/2015 02:56 PM, Robert Latest wrote:

On Thu, 15 Jan 2015 19:43:23 -0500
Ric Moore  wrote:


On 01/15/2015 03:54 PM, Hans wrote:

First questions:

Are you running pulseaudio or alsa?

Did you try alsamixer?

Often it is possible, to choose different hardware in the GUI. Did
you try other ones, too?

Best


He's got an asoundrc file in /etc. I thought that use was deprecated
some years ago. Maybe if the OP mv;d that file to another name,
rebooted and ran alsamixer first, then add pavucontrol along with
pulse, he might have a better experience, IMHO.


Hi Ric,

it's getting weirder: I installed pavucontrol, started it, and started
mplayer in some other window. No sound on my headphones, but the
little VU bar flashing. Unplugged headphones, sound came from the built
in speaker. Plugged headphones back in, pavucontrol sees it and changes
from "unplugged" tp "plugged in", still no sound on headphones.

With aplay -D hw:0,0 it still works.

OK, now trying to remove all pulse-related stuff.


You're shooting yourself in the foot. IF alsa won't work, pulse will not 
either. IF you used pavucontrol, set up your sound sources, then 
selected playback while the file was playing, you should have seen the 
volume bar twitching. If it was, did you check to see if the volume was 
scrolled up to 100%, unmuted, and that the headphone was selected??


Or, is this some headphone plugged into the soundcard audio-out jack? 
Maybe you're plugged into audio-out (which is non-amplified) instead of 
the headphone jack, which is? OR if there is just one output jack, which 
relies on some sort of hardware magic to determine if it should act like 
audio-out/headphone out, there in lies the problem. PLugging in the 
headphone, removing it and pugging it in, multiple times might get it to 
switch correctly. They don't always work right. Get a cheap set of USB 
headphones and suffer no more. Leave the sound card to drive speakers, 
which worked, as you mention. That must be the problem as I had that 
happen trying to plug in some earbuds. The audio-out expects the plugged 
in device to have it's own amplifier. Headphone out uses the sound card 
amplifier to drive a non-amplified device, like old headphones. No sound 
indicates you're in the wrong jack or it fails to auto-select/switch 
between the two states if there is only one out jack. I bet this is the 
problem. Refer to your manual if you have it. Ric





--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54b97d8f.2030...@gmail.com

Re: firefox compaining about missing library

[Gene Heskett]

On Friday, January 16, 2015 12:07:14 PM Liam O'Toole did opine
And Gene did reply:
> On 2015-01-16, Gene Heskett  wrote:
> > Greetings;
> > 
> > Does anyone know where to find, for Wheezy, this library?
> > VDPAU backend libvdpau_nouveau.so?
> > 
> > Or alternatively, how to install to iceweasal, the missing pluggins
> > that make it work with the real world?  Fresh Wheezy install here.
> > 
> > Thank you.
> > 
> > Cheers, Gene Heskett
> 
> The library belongs to the mesa-vdpau-drivers package[1], which is not
> available in wheezy, nor in wheezy-backports. It's used for
> hardware-accerated video playback.
> 
> 1. https://packages.debian.org/jessie/mesa-vdpau-drivers

Humm, how incompatible would it be with the rest of wheezy?


Thanks.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201501161456.57210.ghesk...@wdtv.com

Re: Can't get sound to work

[berenger . morel]

Le 16.01.2015 19:24, Robert Latest a écrit :

On Thu, 15 Jan 2015 19:43:23 -0500
Ric Moore  wrote:


On 01/15/2015 03:54 PM, Hans wrote:
> First questions:
>
> Are you running pulseaudio or alsa?


I don't know. I seem to have both on my system. I don't know what the
difference is, or if one is running on top of the other, or if they 
are
fighting over my soundcard. How would an application that wants to 
play

sound figure out which system to use?


There are several people more knowledgeable than me around here, but, 
AFAIK, alsa is the lowest level sound manager.
If I am not wrong, pulse audio is built on it. Note that I never tried 
PA: alsa always worked just fine for me, so why should I try it?

I understand the linux Audio stack like this:

Alsa ==> OSS
  ^
  |
  ^
/  \
PA  J

Alsa is better (why? No idea, just what people says...) than OSS, and 
then you have 2 frameworks which works over Alsa. PulseAudio (PA, which 
seems to be POSIX and windows compatible), and Jack (J, which seems to 
be used by professional applications, for real-time stuff and other.


If you simply want sound from flash-player, iceweasel and mplayer... 
well, removing PA may help you, and it will remove something you do not 
necessarily need. And, in my opinion, less code running on my computer 
means less surprises (on my computer), so it's the way I choose. But, I 
am a minimalist lover (well, at least in computing... for beers per 
example I have different tastes ;) ).


Note that I have no opinion about the quality of pulse audio and jack. 
Plus, in some cases, I had problems with microphones with Alsa. Maybe in 
those situations PA or jack would have helped me. Never tried, it was 
not important enough for me.



Maybe if the OP mv;d that file to another name,
rebooted and ran alsamixer first, then add pavucontrol along with
pulse, he might have a better experience, IMHO.


I'll try that (have to install first). If it works, can I then purge 
all

ALSA-related stuff from my system? Or could I also remove all
pulse-related stuff and keep ALSA?


If you purge alsa-related stuff, you will end with no sound at all.
Alsa means "Advanced Linux Sound Architecture". It seems to be a driver 
replacement for OSS.
In short, it would be like removing your nouveau/nvidia/intel/whatever 
driver and trying to run Xorg or weston... Xorg and weston would be PA 
and Jack, the driver would be alsa. That's what I understand, at least.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/7336596ddab655b8d37400e9c49a9...@neutralite.org

Re: Can't get sound to work

[Ric Moore]

On 01/16/2015 04:33 AM, Lisi Reisz wrote:



The symptoms are not the same as yours. aplay doesn't play sound when I
select the PCM device on the command line. But, with audacity, if I
explicitly select ALSA as output and device hw:1,0, sound comes out. So, I
may have another problem that prevents aplay from running when the PCM
device is specified and the above solution may still help you.

BTW, I have pulseaudio installed in case it matters.


So the advice is to have alsa and pulseaudio?


You have to have alsa. That is the sound system. Pulse sits on top of it 
to direct your sound sources where you want them to be, as in multiple 
sound devices, speakers and microphones. You can do this on the fly, as 
in switching between 7.1 to USB head phones for quiet listening. :) Ric



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54b97700.2020...@gmail.com

Fwd: Re: Can't get sound to work

[Ric Moore]

I hit the wrong send to: button.


 Forwarded Message 
Subject: Re: Can't get sound to work
Date: Fri, 16 Jan 2015 15:29:50 -0500
From: Ric Moore 
To: Robert Latest 

On 01/16/2015 01:24 PM, Robert Latest wrote:

On Thu, 15 Jan 2015 19:43:23 -0500
Ric Moore  wrote:



I happen to love
using pulse, although years ago I was spitting mad at it. Works a
charm for me now, especially when using different sound
inputs/outputs on the fly. Ric


I'm not that picky. All I want is hear sound from mplayer or webpages
with video content.



In a nut shell, alsa is the basement for sound. Pulse sits on top and
directs input/output to multiple sound decices. It seems you have
several. I've got a sound card plugged in, so I disabled the onboard
sound card, that won't work at all, in the bios. Now alsa has one less
headache to deal with. Then install pauvucontrol. That is the graphical
interface to pulse. Running that I can define my outputs, like USB
headphonne + mono-mike, 6.1 sound card. Now I can select playback and
direct the sound between my suround speakers and stereo headphones, ON
THE FLY!!

Again, if alsa is not happy, pulse will not work at all either. If you
have a sound card in your junk box, install that to the motherboard and
disable the onboard intel setup in the bios. My onboard audio refused to
work, and that fixed it nicely. Or, just get a cheap usb audio device,
with all the bells and whistles, like 7.1 sound. I love blasting the
neighborhood with my setup. When I need quiet, I just use pavucontrol to
direct the output to the usb headphones. That beats the dickens out of
messing with ancient alsa scripts and edits.

"Works For Me!" Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54b975ed.50...@gmail.com

Re: Can't get sound to work

[Ric Moore]

On 01/16/2015 03:41 AM, Frédéric Marchal wrote:


BTW, I have pulseaudio installed in case it matters.

Frederic


Once you start with the edits, pulse most likely will not work since you 
defeated it's purpose to define things after alsa is doing it's job. I 
remember the bad old days when you had to do that and even then it 
didn't work half the time. Ric



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
Linux user# 44256


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54b975ab.4060...@gmail.com

Sleep but no resume

[edjabr]

Running stable 64bit with the 3.2.65-1+deb7u1 kernel.  This macbook 
will go to sleep but will not resume, requiring a hard reboot.  When 
s2ram is run, the acivity light blinks- a sign that the machine is 
really asleep.  However, when I hit a key, the light goes out and no 
resume.  

I booted into OSX and sleep/resume was flawless, so it’s not hardware.  
Resume worked before the recently updated proprietary nvidia driver. 
So, uninstalled it and ran with nouveau, but still nogo.  I then 
installed a newer proprietary from backports.  No resume still, so it 
doesn’t seem to be a driver problem.  I've googled a lot and looked 
through files I never heard of before but couldn't find anything 
helpful. Bug #774461 refers to a fix for a similar but really 
different problem, and says that sleep/resume is fixed with the kernel 
I’m already running.  I’ve run s2ram wth different parameters but got 
nowhere.  Finally, s2ram --test returns 

 Machine unknown
This machine can be identified by:
sys_vendor   = "Apple Inc."
sys_product  = "MacBook5,1"
sys_version  = "1.0"
bios_version = "MB51.88Z.007D.B03.0904271443"

I’m at a loss here.  If anyone has any hints, something else to try or 
a pointer to a good rundown on this, greatly appreciated.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201501161519.36736.edj...@gmail.com

Re: Can't get sound to work

[Robert Latest]

On Thu, 15 Jan 2015 19:43:23 -0500
Ric Moore  wrote:

> On 01/15/2015 03:54 PM, Hans wrote:
> > First questions:
> >
> > Are you running pulseaudio or alsa?
> >
> > Did you try alsamixer?
> >
> > Often it is possible, to choose different hardware in the GUI. Did
> > you try other ones, too?
> >
> > Best
> 
> He's got an asoundrc file in /etc. I thought that use was deprecated 
> some years ago. Maybe if the OP mv;d that file to another name,
> rebooted and ran alsamixer first, then add pavucontrol along with
> pulse, he might have a better experience, IMHO.

Hi Ric,

it's getting weirder: I installed pavucontrol, started it, and started
mplayer in some other window. No sound on my headphones, but the
little VU bar flashing. Unplugged headphones, sound came from the built
in speaker. Plugged headphones back in, pavucontrol sees it and changes
from "unplugged" tp "plugged in", still no sound on headphones.

With aplay -D hw:0,0 it still works.

OK, now trying to remove all pulse-related stuff.

Thanks
robert


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150116205622.3f0fc1af@dotcom.mfs32

Re: Can't get sound to work

[Mike McGinn]

On Friday, January 16, 2015 14:23:21 Doug wrote:
> On 01/16/2015 01:24 PM, Robert Latest wrote:

When I had a new install I found that the mixer levels were all at zero. Found 
it after an hour of troubleshooting.


-- 
Mike McGinn KD2CNU
Be happy that brainfarts don't smell.
No electrons were harmed in sending this message, some were inconvenienced.
** Registered Linux User 377849


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201501161433.29846.mikemcg...@mcginnweb.net

Re: Can't get sound to work

[Doug]

On 01/16/2015 01:24 PM, Robert Latest wrote:


pulse, he might have a better experience, IMHO.


I'll try that (have to install first). If it works, can I then purge all
ALSA-related stuff from my system? Or could I also remove all
pulse-related stuff and keep ALSA?


I happen to love
using pulse, although years ago I was spitting mad at it. Works a
charm for me now, especially when using different sound
inputs/outputs on the fly. Ric


I'm not that picky. All I want is hear sound from mplayer or webpages
with video content.

Thanks,
robert



I won't swear to it, but I think PA runs on top of Alsa, so don't remove it.
Even if that is not the case, they are compatible--i.e., Alsa will not
interfere with PA.

For years I swore at PA and always removed it, but in the last year or so,
it is working, and has some features you can't get anywhere else, like being
able to output sound from two sound cards at once, so as to send sound along
with video to your TV, while still hearing it locally at your computer.

If all else fails, you can remove pulse and keep Alsa, but I wouldn't try it
the other way round.

--doug


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54b96529.3060...@optonline.net

Re: Have I been hacked?

[Chris Bannister]

On Thu, Jan 15, 2015 at 12:35:00PM +0100, mrr wrote:
> On 14/01/2015 06:00, Bob Proulx wrote:
> >Trying to hide in an unusual username is obscurity not security.  You
> >may have heard the term that obscurity is not security.
> 
> Well obscurity may help, think about the man who loose his car key somewhere
> in an obscure place but will begin looking for it where there is some light
> because it's easier to see around!

And looking in the wrong place means you'll *NEVER* find the keys no matter
how good the light is.

> Said otherwise, the "black hat" may try to hack easy targets (with known
> username) before hacking you (with weird username), no?

In this case the "black hat" *MAY* crack the password.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150116184146.GA30837@tal

Re: Can't get sound to work

[Robert Latest]

On Thu, 15 Jan 2015 19:43:23 -0500
Ric Moore  wrote:

> On 01/15/2015 03:54 PM, Hans wrote:
> > First questions:
> >
> > Are you running pulseaudio or alsa?

I don't know. I seem to have both on my system. I don't know what the
difference is, or if one is running on top of the other, or if they are
fighting over my soundcard. How would an application that wants to play
sound figure out which system to use?

> >
> > Did you try alsamixer?

When I just run alsamixer, I see one big vertical adjustment. When I
run alsamixer -c 0 I see a lot of controls (Master, Headphone, PCM...).
Still I can't hear anything unless running aplay -D hw:0,0.

> > Often it is possible, to choose different hardware in the GUI. Did
> > you try other ones, too?

F6 lets me select different cards in alsamixer, but it doesn't change
anything if I run anything but aplay -D hw:0,0 in another window.

> 
> He's got an asoundrc file in /etc. I thought that use was deprecated 
> some years ago.

I put it there hoping to make the "-D hw:0,0" thingy the default for
all sound-playing software.

> Maybe if the OP mv;d that file to another name,
> rebooted and ran alsamixer first, then add pavucontrol along with
> pulse, he might have a better experience, IMHO.

I'll try that (have to install first). If it works, can I then purge all
ALSA-related stuff from my system? Or could I also remove all
pulse-related stuff and keep ALSA?

> I happen to love
> using pulse, although years ago I was spitting mad at it. Works a
> charm for me now, especially when using different sound
> inputs/outputs on the fly. Ric

I'm not that picky. All I want is hear sound from mplayer or webpages
with video content.

Thanks,
robert


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150116192420.25211d69@dotcom.mfs32

Re: firefox compaining about missing library

[Liam O'Toole]

On 2015-01-16, Gene Heskett  wrote:
> Greetings;
>
> Does anyone know where to find, for Wheezy, this library?
> VDPAU backend libvdpau_nouveau.so?
>
> Or alternatively, how to install to iceweasal, the missing pluggins that 
> make it work with the real world?  Fresh Wheezy install here.
>
> Thank you.
>
> Cheers, Gene Heskett

The library belongs to the mesa-vdpau-drivers package[1], which is not
available in wheezy, nor in wheezy-backports. It's used for
hardware-accerated video playback.

1. https://packages.debian.org/jessie/mesa-vdpau-drivers

-- 

Liam



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmbiha1.faa.liam.p.otoole@dipsy.tubbynet

Re: Have I been hacked?

[Curt]

On 2015-01-16, Joel Rees  wrote:
>
> The argument, SSH keys versus passwords is kind of missing the point,
> unless the argument itself helps people listening in think a bit more
> carefully about their security.
>

The success of the offline cracking of seemingly "good" hashed passcodes
got me to thinking, an activity to which I have reluctantly grown
accustomed over the years.

-- 
“There’s no money in poetry, but then there’s no poetry in money,
either.” —Robert Graves


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmbigfd.223.cu...@einstein.electron.org

Re: upgrade kernel

[Marc Auslander]

Pol Hallen  writes:
> Hi folks!
>
> a security updates of kernel is available (from apt-get upgrade), so:
> must I reboot my pc (after upgrade) to avoid security problems? Is
> there another way?
>
> thanks for help!
>
> Pol
>
>

I always reboot after a kernel related upgrade on the grounds that if
something goes wrong, I want to know about it right now.

The alternative is that sometime in the future, a scheduled or
unscheduled reboot leads to trouble and you have no idea what caused it!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/877fwmbrx3@aptiva.optonline.net

Re: An experiment in backup

[Rob Owens]

On Thu, Jan 15, 2015 at 08:47:01PM -0800, Kevin O'Gorman wrote:
> On Thu, Jan 15, 2015 at 8:41 PM, David Christensen <
> > There are two basic kinds of "backups":
> >
> > 1.  File system -- e.g. a copy of the files and directories on an mounted
> > and operating drive.
> >
> > 2.  Raw binary image -- e.g. a copy of the bytes on a drive taken when the
> > drive is powered, but the partitions, volumes, file systems, etc., are not
> > mounted.
> >
> >
> > For system drives, the former won't work; you need the later.  I connect a
> > large hard drive (to hold the images), boot Debian installation media into
> > rescue mode, and use 'dd' to backup/ restore system drive raw binary images.
> >
> > I was hoping for some details on why this won't work on system drives, or
> conditions under which it just might.  Another user has suggested I read
> https://help.ubuntu.com/community/BackupYourSystem/TAR which suggests that
> it actually should work.

Image backups are definitely easier for doing disaster recovery of an
entire machine.  And when you have that kind of problem, you may really
appreciate having to do less work / make fewer decisions.

But filesystems backups can be used for disaster recovery.  I've done
it.  One potential problem is that on a running system, things change.
So at the start of your backup, you backup file A.  At the end of the
backup, you backup file Z.  But in the middle of the backup, both file A
and file Z have changed.  And some software requires that file A and
file Z be in sync.  When you restore, those files are not in sync and
you could have a problem.

In practice, I haven't seen this be a problem much on home desktop
machines.  But that's not to say it couldn't be a problem.

Another thing to consider is hardware changes.  This can make certain
devices be named differently when you restore.  eth0 becomes eth1, and
/etc/network/interfaces doesn't have a stanza for eth1.  /dev/dvd
becomes /dev/dvd1, and your cd burner was set to look for /dev/dvd which
no longer exists.  These things can be fixed in the /etc/udev/rules.d
directory.

UIDs of disk partitions will change.  If /etc/fstab references UIDs, you
need to update it.  Same for /boot/grub/grub.cfg, although for that you
run update-grub2 from the restored system (you'll need to boot with a
live cd and chroot, or you'll need to boot with Super Grub Disk or
similar).  You will also need to install the bootloader on the new hard
disk.  'grub-install /dev/sda' 

The UUID and Grub issues don't show up when restoring from an image
backup, but the network card and cd burner issues can.

There are a lot of free software backup solutions available.  I would
recommend using one of those, unless this endevour is more for learning
experience than anything else.

Backuppc may be overkill for your case, but it's pretty good.  It will
do file pooling and compression, so keeping multiple backups of one or
more machines doesn't take up much disk space.

-Rob


signature.asc
Description: Digital signature

firefox compaining about missing library

[Gene Heskett]

Greetings;

Does anyone know where to find, for Wheezy, this library?
VDPAU backend libvdpau_nouveau.so?

Or alternatively, how to install to iceweasal, the missing pluggins that 
make it work with the real world?  Fresh Wheezy install here.

Thank you.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201501161114.23261.ghesk...@wdtv.com

Re: An experiment in backup

[Rob Owens]

On Thu, Jan 15, 2015 at 07:19:52PM -0800, Kevin O'Gorman wrote:
> I'm trying to develop a reliable backup method that does not use
> proprietary tools or formats, and is free as in beer.  I thought I had it,
> but i just tried a restore, and it's a miserable failure.  I wonder if
> anyone here can point out the error of my ways.
> 
> I have a tar backup of the entire system, excluding /sys, /proc and /dev.
> I have a tar backup of a bind-mount of /dev.
> These were taken while the system was running, but quiet.  I did it this
> way because I cannot get the system to boot into single user mode.  Putting
> "single" on the end of the "linux" like results in a black screen.
> 
> I restored these, created /sys and /proc, and tried to boot the resulting
> partition.  It boots, but X does not come up, or even seem to try.  I can
> do a console login to my usual account, and stuff is there.
> 
Check the permissions on /tmp.  It should be drwxrwxrwt.  Without the
't' at the end, stuff like X logins won't work (in my experience).


signature.asc
Description: Digital signature

Re: Have I been hacked?

[Frédéric Marchal]

On Friday 16 January 2015 14:38:09, Joel Rees wrote :
> > I can remember "TwasBrilligAndTheSlithyToves" and associate it with an
> > account.
> > 
> > Before signing up I do
> > 
> > echo TwasBrilligAndTheSlithyToves | sha1sum | base64 | cut -c -30
> > 
> > The output is what I give to a site as a password.
> 
> Now you're talking sense. Maybe I don't need to answer your questions
> about IP spoofing and using strategy instead of pure brute force after
> all.
> 
> Although, when you don't have access to a command line that gives you
> sha1sum, you're back to having to work hard to remember what you gave
> that site for a password.
> 
> Frankly, rot13 or rot42 would get pretty close. But I would prefer a
> tool of my own making that I can use to exclusive-or the site name
> with my chosen pass-phrase before I pass it to the predictable
> shuffle.

That looks like https://www.passwordmaker.org/passwordmaker.html which is 
available as a firefox/iceweasel plugin and a chrome plugin (if I'm not 
mistaken).

That tool takes one master password (you only have to remember that one) and 
use it to derive a site specific password based on that password, the url and 
possibly the user name used on the site.

The generated password can be computed at any time and on any computer with 
those informations and various other options (such as the hash algorithm, the 
characters included in the password, the password length and so on).

Due to the hash algorithm, it is impossible to find the master password from 
one or even many generated passwords. Nor is it possible to compute the 
password for another site from passwords harvested on compromised sites.

If one site is compromised and the owner ask you to change your existing 
password, simply change one option in PasswordMaker to generate a new 
password.

Frederic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/201501161551.08129.frederic.marc...@wowtechnology.com

Re: Have I been hacked?

[Joel Rees]

On Thu, Jan 15, 2015 at 6:56 AM, Brian  wrote:
> [...]
> We are still on off-line cracking? How does this sound?

Hmm. I guess I should respond to your questions about IP spoofing and
using strategy rather than pure brute force after all.

> Memorable passwords are good. Long, complex passwords are also good. One
> needn't exclude the other.

To a certain degree, they do. However,

> I can remember "TwasBrilligAndTheSlithyToves" and associate it with an
> account.
>
> Before signing up I do
>
> echo TwasBrilligAndTheSlithyToves | sha1sum | base64 | cut -c -30
>
> The output is what I give to a site as a password.

Now you're talking sense. Maybe I don't need to answer your questions
about IP spoofing and using strategy instead of pure brute force after
all.

Although, when you don't have access to a command line that gives you
sha1sum, you're back to having to work hard to remember what you gave
that site for a password.

Frankly, rot13 or rot42 would get pretty close. But I would prefer a
tool of my own making that I can use to exclusive-or the site name
with my chosen pass-phrase before I pass it to the predictable
shuffle.

But, as John Hasler points out, we're just sort of re-inventing (half
of) ssh keys.

> Furthermore, before any future logins I can run the command again to get
> the same password. Isn't this on-line and off-line cracking taken care
> of?

Depends on whether the targetting attacker is aware that you use
sha1sum on all your passwords.

Or has a copy of the source code for my rot42xor tool.

This is the part that SSH keys gets right, of course.

The argument, SSH keys versus passwords is kind of missing the point,
unless the argument itself helps people listening in think a bit more
carefully about their security.

-- 
Joel Rees

Be careful when you look at conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Arm yourself with knowledge of yourself, as well.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caar43ioj_vklxzni4os_0hzjfghgl9m2hhcmpmm7h5hdmfv...@mail.gmail.com

Re: An experiment in backup

[Tom H]

On Thu, Jan 15, 2015 at 10:19 PM, Kevin O'Gorman  wrote:
>
> I have a tar backup of the entire system, excluding /sys, /proc and /dev.
> I have a tar backup of a bind-mount of /dev.
> These were taken while the system was running, but quiet. I did it this
> way because I cannot get the system to boot into single user mode. Putting
> "single" on the end of the "linux" like results in a black screen.
>
> I restored these, created /sys and /proc, and tried to boot the resulting
> partition. It boots, but X does not come up, or even seem to try. I can do
> a console login to my usual account, and stuff is there.

What commands did you run to back up and restore the system?

Is '/tmp' a tmpfs filesystem? If not, did you back up and restore it?

Did you exclude '/run'? If not, did you restore it?

Did you create '/proc' and '/sys' with the right ownership and mode?

If this is a Debian system, is it a non-standard install that doesn't
use udev (AFAIK this is still possible)? If not, there's no point in
backing up and restoring '/dev'.

If this is an Ubuntu system, the default '(recovery)' grub entry will
have 'nomodeset' appended. Try that when you add 'single'.

Are you using a DM?

Are you using a WM or a DE?

Have you looked at the logs? Especially Xorg.0.log and xsessions-errors.

Can you launch X after logging in to the console?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAOdo=swjn5qggmjo7qta_2otefqgzihwpn35hykxshk4_oa...@mail.gmail.com

Re: An experiment in backup

[Thom Miller]

On 01/16/2015 01:28 AM, Joel Roth wrote:
> On Thu, Jan 15, 2015 at 09:32:24PM -0800, Kevin O'Gorman wrote:
>> I care because I like to have a lot of free space in my partitions, but I
>> hate to use backup time and space on the holes.
> 
> Hi Kevin,
> 
> If you copy the whole partition, byte-for-byte, as with the
> 'dd' command, you copy everything, including the free space.
> 
> If you copy via the filesystem, e.g. using rsync, you just
> pay for what you use, and all the files are immediately
> available. Restoring a file is a matter of 
> copying.
> 
> ...
> 
> #!/bin/sh
> RSYNC="rsync -avx "
> CMD="$RSYNC \
>   --exclude /dev \
>   --exclude /proc \
>   --exclude /sys  \
>   --exclude /home \
>   --exclude /tmp \
>   --exclude /var/cache/apt/archives \
>   --exclude /var/run \
> / /mnt/$1/root" 
> echo $CMD >> /var/log/backup.log
> 
I can confirm that the above works. I recently used rsync to copy my
live system to another partition, excluding /dev /proc /sys /tmp and /home.

After setting grub to boot the new partition, it works fine. I'm using
it now.

-Thom


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54b8edd7.40...@cagroups.com

Re: Can't get sound to work

[Frédéric Marchal]

On Friday 16 January 2015 10:33:23, Lisi Reisz wrote :
> On Friday 16 January 2015 08:41:29 Frédéric Marchal wrote:
> > But sound started to work fine after I edited $HOME/.asoundrc like this:
> > 
> > pcm.!default {
> >   type plug
> >   slave {
> > pcm "hw:1,0"
> >   }
> > }
> > ctl.!default {
> >   type hw
> >   card 1
> > }
> > 
> > The symptoms are not the same as yours. aplay doesn't play sound when I
> > select the PCM device on the command line. But, with audacity, if I
> > explicitly select ALSA as output and device hw:1,0, sound comes out. So,
> > I may have another problem that prevents aplay from running when the PCM
> > device is specified and the above solution may still help you.
> > 
> > BTW, I have pulseaudio installed in case it matters.
> 
> So the advice is to have alsa and pulseaudio?

I haven't investigated that far. I'm just stating a fact.

I don't know what's the purpose of pulseaudio nor what are the benefits of 
having installed it. I don't know if it would break something to remove it.

I believe it was installed at some point as part of a routine system update 
and may have been the cause of the sound failure in the first place.

Frederic


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/201501161153.37226.frederic.marc...@wowtechnology.com

Re: An experiment in backup

[Darac Marjal]

On Thu, Jan 15, 2015 at 07:19:52PM -0800, Kevin O'Gorman wrote:
>I'm trying to develop a reliable backup method that does not use
>proprietary tools or formats, and is free as in beer.  I thought I had it,
>but i just tried a restore, and it's a miserable failure.  I wonder if
>anyone here can point out the error of my ways.
> 
>I have a tar backup of the entire system, excluding /sys, /proc and /dev.
>I have a tar backup of a bind-mount of /dev.

Skip these.

/sys and /proc are "pseudo-filesystems" in that they are representations
of kernel settings in a file system format. Some of these "files" are
read only (for example the contents of /proc/net/dev are statistics on
all your network devices; in this case, it makes no sense for userspace
to be telling the kernel how many packets have been recieved, so you
can't write to the file), some of the files are write only (for example
/proc/sysrq-trigger which can be used to simulate pressing
SysRq+). And besides, neither of these filesystems is
persistent (the contents are lost at shutdown and recreated when the
filesystem is mounted).

/dev, similarly, is (since the days of devfs) a dymanic filesystem
containing only communication end-points to your devices. You could back
up the device nodes, but because the kernel autodiscovers hardware and
creates the devices nodes at boot, you'll either have exactly the same
thing (if the autodetection happened in exactly the same manner) or the
WRONG device nodes.


>These were taken while the system was running, but quiet.  I did it this
>way because I cannot get the system to boot into single user mode. 
>Putting "single" on the end of the "linux" like results in a black screen.
> 
>I restored these, created /sys and /proc, and tried to boot the resulting
>partition.  It boots, but X does not come up, or even seem to try.  I can
>do a console login to my usual account, and stuff is there.
> 
>I'm quite clueless as to why this is happening.  I could sure use some
>help.
>--
>Kevin O'Gorman
>#define QUESTION ((bb) || (!bb))   /* Shakespeare */
> 
>Please consider the environment before printing this email.




signature.asc
Description: Digital signature

Latest update was bad news for me!

[Bruce Ward]

I've got an ASRock motherboard with AMD AM3 CPU and "Giga PHY RTL8211CL"
ethernet, running Wheezy. Had no joy getting the network port running
(forcedeth module would kill the whole system as soon as tried to use or
even unload it!), so I used an old (faithful) DEC Tulip card (de2104x
module). And so it ran for months (or a year or more, through a number of
linux updates) without problems.
Last week I happened to find a reference in an Ubuntu forum to
successfully getting the RTL8211 working - after consultation with ASRock.
It involved removing the forcedeth module and reinstalling it with certain
parameters. So I tried it, and it worked (without killing the system!); I
put the necessary fix in a file in /etc/modprobe.d, and that I used until
this morning. I presumably had rebooted in that time to test the fix.
This morning the latest Linux security update (DSA3128) arrived and I
installed that. It involved a restart, after which I had no network
connection - not even with the Tulip card. In fact I was back to rmmod
forcedeth killing the system (with a familiar pattern on screen - but
locked SOLID).
No, I have not been able to get the Tulip working in Wheezy, but I know it
is not dead - Puppy Linux (tahr) gets it going just fine (but has other
problems apparently from the RTL8211 which it can't connect to the
network). After some hours of frustration, I have got the RTL8211 working
in Wheezy, but it seems to involve manual loading of the forcedeth driver
after every restart.

One thing to take from this - ASRock, AMD AM3, and Linux don't play well
together.
Another is that today's de2104x module doesn't work my card.

/vent

Bruce Ward



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/22678.60.234.158.211.1421400550.squir...@mail.orcon.net.nz

Re: Can't get sound to work

[Lisi Reisz]

On Friday 16 January 2015 08:41:29 Frédéric Marchal wrote:
> On Thursday 15 January 2015 21:28:30, Robert Latest wrote :
> > Hi all,
> >
> > this is my umptieth Debian installation I've done on various PCs over
> > the years, but this time the sound setup really has me stumped. I can't
> > hear anything unless I use aplay with -D hw:0,0 but setting that in the
> > configuration file doesn't help. No other sound-outputting program
> > works. Here's a shell excerpt:
> >
> > bl@dotcom:~$ aplay test.wav   # can't hear nothing
> > bl@dotcom:~$ aplay -D hw:0,0 test.wav # this plays sound
> > bl@dotcom:~$ cat .asoundrc
> > cat: .asoundrc: No such file or directory
> > bl@dotcom:~$ cat /etc/asound.conf
> > pcm.!default {
> > type hw
> > card 0
> > device 0
> > }
> > bl@dotcom:~$ aplay -l
> >  List of PLAYBACK Hardware Devices 
> > card 0: Intel [HDA Intel], device 0: AD1984 Analog [AD1984 Analog]
> >   Subdevices: 1/1
> >   Subdevice #0: subdevice #0
> > card 0: Intel [HDA Intel], device 2: AD1984 Alt Analog [AD1984 Alt
> > Analog]
> >   Subdevices: 1/1
> >   Subdevice #0: subdevice #0
> > bl@dotcom:~$ cat /proc/asound/cards
> >  0 [Intel  ]: HDA-Intel - HDA Intel
> >   HDA Intel at 0xfe9dc000 irq 45
> > bl@dotcom:~$
>
> Sound has been missing on my wheezy for some time until your mail prompted
> me to investigate it.
>
> Running aplay test.wav produces no sound.
>
> The output of aplay -l is:
>
>  List of PLAYBACK Hardware Devices 
> card 0: HDMI_1 [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: HDMI_1 [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: HDMI_1 [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 1: PCH [HDA Intel PCH], device 0: 92HD91BXX Analog [92HD91BXX Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
>
> Running aplay -D hw:1,0 test.wav reports an error and produces no sound:
>
> Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 11025 Hz, Mono
> aplay: set_params:1087: Channels count non available
>
> But sound started to work fine after I edited $HOME/.asoundrc like this:
>
> pcm.!default {
>   type plug
>   slave {
> pcm "hw:1,0"
>   }
> }
> ctl.!default {
>   type hw
>   card 1
> }
>
> The symptoms are not the same as yours. aplay doesn't play sound when I
> select the PCM device on the command line. But, with audacity, if I
> explicitly select ALSA as output and device hw:1,0, sound comes out. So, I
> may have another problem that prevents aplay from running when the PCM
> device is specified and the above solution may still help you.
>
> BTW, I have pulseaudio installed in case it matters.

So the advice is to have alsa and pulseaudio?

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201501160933.23468.lisi.re...@gmail.com

Re: An experiment in backup

[Gerald]

On Thu, 15 Jan 2015 19:19:52 Kevin O'Gorman wrote:
> I'm trying to develop a reliable backup method that does not use
> proprietary tools or formats, and is free as in beer.  I thought I had it,
> but i just tried a restore, and it's a miserable failure.  I wonder if
> anyone here can point out the error of my ways.
> 
> I have a tar backup of the entire system, excluding /sys, /proc and /dev.
> I have a tar backup of a bind-mount of /dev.
> These were taken while the system was running, but quiet.  I did it this
> way because I cannot get the system to boot into single user mode.  Putting
> "single" on the end of the "linux" like results in a black screen.
> 
> I restored these, created /sys and /proc, and tried to boot the resulting
> partition.  It boots, but X does not come up, or even seem to try.  I can
> do a console login to my usual account, and stuff is there.
> 
> I'm quite clueless as to why this is happening.  I could sure use some help.
I have had problems creating backups of the entire system, but I have switched 
to ‘REDO’ to give me a raw disk type of backup. This works very well so long 
as you have disks of the same size or larger for the reinstall.
REDO backup up Linux and Windoze..Very good.
Just Google for redo and  you should get it.
Gerald


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/14077027.2dfaypo...@ws4.sol.home

Re: Can't get sound to work

[Frédéric Marchal]

On Thursday 15 January 2015 21:28:30, Robert Latest wrote :
> Hi all,
> 
> this is my umptieth Debian installation I've done on various PCs over
> the years, but this time the sound setup really has me stumped. I can't
> hear anything unless I use aplay with -D hw:0,0 but setting that in the
> configuration file doesn't help. No other sound-outputting program
> works. Here's a shell excerpt:
> 
> bl@dotcom:~$ aplay test.wav   # can't hear nothing
> bl@dotcom:~$ aplay -D hw:0,0 test.wav # this plays sound
> bl@dotcom:~$ cat .asoundrc
> cat: .asoundrc: No such file or directory
> bl@dotcom:~$ cat /etc/asound.conf
> pcm.!default {
> type hw
> card 0
> device 0
> }
> bl@dotcom:~$ aplay -l
>  List of PLAYBACK Hardware Devices 
> card 0: Intel [HDA Intel], device 0: AD1984 Analog [AD1984 Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: Intel [HDA Intel], device 2: AD1984 Alt Analog [AD1984 Alt
> Analog]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> bl@dotcom:~$ cat /proc/asound/cards
>  0 [Intel  ]: HDA-Intel - HDA Intel
>   HDA Intel at 0xfe9dc000 irq 45
> bl@dotcom:~$

Sound has been missing on my wheezy for some time until your mail prompted me 
to investigate it.

Running aplay test.wav produces no sound.

The output of aplay -l is:

 List of PLAYBACK Hardware Devices 
card 0: HDMI_1 [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI_1 [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI_1 [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: 92HD91BXX Analog [92HD91BXX Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Running aplay -D hw:1,0 test.wav reports an error and produces no sound:

Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 11025 Hz, Mono
aplay: set_params:1087: Channels count non available

But sound started to work fine after I edited $HOME/.asoundrc like this:

pcm.!default {
  type plug
  slave {
pcm "hw:1,0"
  }
}
ctl.!default {
  type hw
  card 1
} 

The symptoms are not the same as yours. aplay doesn't play sound when I select 
the PCM device on the command line. But, with audacity, if I explicitly select 
ALSA as output and device hw:1,0, sound comes out. So, I may have another 
problem that prevents aplay from running when the PCM device is specified and 
the above solution may still help you.

BTW, I have pulseaudio installed in case it matters.

Frederic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/201501160941.29640.frederic.marc...@wowtechnology.com

Re: An experiment in backup

[Joel Roth]

On Thu, Jan 15, 2015 at 09:32:24PM -0800, Kevin O'Gorman wrote:
> I care because I like to have a lot of free space in my partitions, but I
> hate to use backup time and space on the holes.

Hi Kevin,

If you copy the whole partition, byte-for-byte, as with the
'dd' command, you copy everything, including the free space.

If you copy via the filesystem, e.g. using rsync, you just
pay for what you use, and all the files are immediately
available. Restoring a file is a matter of 
copying.

My big files are video, which don't compress well, and I
backup to disk, not tape, so I see no benefit from using
tar. 

btw, like many others, I've written various backup scripts
over the years. Lately, I've just done full backups, one for
/home, one for everything else.  My case is simple, because
everything is in one partition. I exclude some directories,
and after making the backup, create them in the backup
directory.

#!/bin/sh
RSYNC="rsync -avx "
CMD="$RSYNC \
--exclude /dev \
--exclude /proc \
--exclude /sys  \
--exclude /home \
--exclude /tmp \
--exclude /var/cache/apt/archives \
--exclude /var/run \
/ /mnt/$1/root" 
echo $CMD >> /var/log/backup.log

for dir in dev proc sys home tmp var/run var/cache/apt/archives ; do mkdir 
/mnt/$1/root/$dir; done

This script doesn't address permissions. (/tmp usually gets
1777.) 

I haven't tested it lately. However you can see to work if
/dev /proc and /sys get populated on boot, you should have
everything you need.  The most likely booting issues for me are
usually something in /etc/fstab.

However, I'm thinking to move over to a Time Machine style
rsync backup based on hardlinks.

have fun,


-- 
Joel Roth
  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150116082846.GB13450@sprite

Re: Can't get sound to work

[August Karlstrom]

On 2015-01-15 21:40, Daniel Haude wrote:

Hi all,

this is my umptieth Debian installation I've done on various PCs over
the years, but this time the sound setup really has me stumped. I can't
hear anything unless I use aplay with -D hw:0,0 but setting that in the
configuration file doesn't help. No other sound-outputting program
works. Here's a shell excerpt:

bl@dotcom:~$ aplay test.wav   # can't hear nothing
bl@dotcom:~$ aplay -D hw:0,0 test.wav # this plays sound
bl@dotcom:~$ cat .asoundrc
cat: .asoundrc: No such file or directory
bl@dotcom:~$ cat /etc/asound.conf
pcm.!default {
 type hw
 card 0
 device 0
}


What happens if you remove /etc/asound.conf?

-- August


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/m9agfi$bnc$1...@dont-email.me