Re: How to override fuse args to ntfs-3g to set permissions?

2014-11-27 Thread Scott Ferguson

>>
>> Quick comment (I will get back to this later today or early tomorrow):-
>> grep ntfs /lib/udev/rules.d/*.rules
>> /lib/udev/rules.d/80-udisks.rules:ENV{ID_FS_TYPE}=="ntfs|vfat", \
>>
>> If this does control the effect you note, (which is easy to determine),
>> then it's simple to create a rule based on it
>> (/etc/udev.d/$something.rule) that will treat your WinBackup disk
>> differently
>
>
> I grabbed the src for udisks, but didn't get very far. It has code that
> checks fstab and uses its entries if found, but that code isn't used. It
> always makes a call to udev_glib instead.

The default settings for external drives is in /lib, offhand I can't
remember where filetypes is taken from (somewhere in /etc ?).  Take a
look at "udisks-doc" if you're interested. Most of udisks, as you've
discovered, is binary.

Another very quick comment as I haven't had a chance to do much Debian
User stuff lately (will get back to this and an Apple udev rule this
evening).

The udisk rule I pointed out above - is fine as it is, it hides
disk/slices that would normally need to be hidden.

I need to finish testing a custom udisks rule for you that changes the
default naming of new devices that have an ntfs file system to
/dev/$Label and a udev rule that runs fuser to automount the drive (to
/media/$Label. It can be done with just udev, but it's a crude hack
(doesn't cleanly umount, creates incrementing /media/usbN). Then you
should get the Thunar support you want for Plex.
>
> Regards,
> Rick
>
>
Thanks for your patience.

Kind regards


-- 
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/camt2cqoss9jklek5ifvkvgbcmrrjt7zthwtk8hbj70fegyk...@mail.gmail.com



Re: How to override fuse args to ntfs-3g to set permissions?

2014-11-27 Thread Rick Macdonald

On 26/11/14 04:20 PM, Scott Ferguson wrote:

On 27/11/14 06:32, Rick Macdonald wrote:

On 26/11/14 08:24 AM, Rick Macdonald wrote:

On 26/11/14 12:23 AM, Scott Ferguson wrote:

On 26/11/14 16:14, Rick Macdonald wrote:

On 25/11/14 08:46 PM, Scott Ferguson wrote:



Sorry for replying to my own post...

I see now that it's the XFCE's volume management that is initiating the
(hotplug) mount. Some digging found that "udisks" is involved, so I
attached strace to the udisks-daemon and found this:

[pid 29472] 10:58:32 execve("/sbin/mount.ntfs", ["/sbin/mount.ntfs",
"/dev/sdg2", "/media/WinBackup_", "-o",
"rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,dmask=0077,fmask=0177"],
[/* 3 vars */]) = 0

So the mode that I'd like to change is coming from the udisks-daemon (or
its parent). Strace on udevd shows that it's involved but I don't see
any file modes.

That's were I'm at now. I played with udev rules a bit but I've never
worked with them before.

Quick comment (I will get back to this later today or early tomorrow):-
grep ntfs /lib/udev/rules.d/*.rules
/lib/udev/rules.d/80-udisks.rules:ENV{ID_FS_TYPE}=="ntfs|vfat", \

If this does control the effect you note, (which is easy to determine),
then it's simple to create a rule based on it
(/etc/udev.d/$something.rule) that will treat your WinBackup disk
differently


I grabbed the src for udisks, but didn't get very far. It has code that 
checks fstab and uses its entries if found, but that code isn't used. It 
always makes a call to udev_glib instead.


Regards,
Rick


--
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/54780346.7000...@shaw.ca



Re: Replacing systemd in Jessie

2014-11-27 Thread Don Armstrong
On Thu, 27 Nov 2014, Patrick Bartek wrote:
> Now the strange thing: I've done some research, and it seems that all
> the init replacement procedures start with first replacing systemd
> with sysvinit, then proceeding with replacing sysvinit with the
> desired init. Anyone have info or instructions to the contrary?

If you want upstart, you can just install upstart instead of
sysvinit-core.

> I'm concerned specifically with runit.

Runit is not configured to be directly replaced without manual
intervention. Install sysvinit-core or whatever, then run the manual
configuration to run runit as /sbin/init.

-- 
Don Armstrong  http://www.donarmstrong.com

In all matters of government, the correct answer is usually: "Do
nothing"
 -- Robert Heinlein _Time Enough For Love_ p428


-- 
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/20141128043300.gq25...@teltox.donarmstrong.com



Re: Replacing systemd in Jessie

2014-11-27 Thread Chris Bannister
On Thu, Nov 27, 2014 at 10:10:23PM -0500, The Wanderer wrote:
> On 11/27/2014 at 09:33 PM, John Hasler wrote:
> 
> > Patrick Bartek writes:
> > 
> >> It seems systemd cannot not be installed in Jessie.
> > 
> > You mean Testing.  Jessie has not been released.
> 
> My understanding of the way the Debian release codenames work / are used
> is that current testing (AKA "the current testing release") is codenamed
> jessie, and when it changes from being a testing release to being the
> latest stable release it will still be codenamed jessie, and the new
> testing will be - or, as the case happens to be, has been - given a new
> codename.

Yes, of course. But read a bit deeper.

-- 
"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/20141128040832.GA26258@tal



shutdown hangs 4+ minutes at "Stopping enhanced syslogd: rsyslog."

2014-11-27 Thread Scott David Sutton

Hello,

I found your thread and I wanted to add something I found on my system.
If I add additional drives (either network or internal) into the fstab 
file the system hangs for the 4+ minutes stated.

If I do not add the drives the system acts normally during shutdown/restart.

I also noted that if I mount these drives I cannot unmount them.
The system states that only the root can unmount them.
Hope this helps

fstab below:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#   
# / was on /dev/sda1 during installation
UUID=dbe17944-35f1-4c6e-bad2-8ff642a90703 /   ext4 
errors=remount-ro 0   1

# swap was on /dev/sda5 during installation
UUID=3b967a80-d527-4e3e-a239-e216f70ea78f noneswap 
sw  0   0

/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0

#ADDITIONAL DRIVES



#UUID=16CA1C95CA1C736B /mnt/MultiMedia  ntfs-3g 
defaults,locale=en_US.utf8 0 0


# NETWORK DiskStation

#//10.0.1.125/software /media/Software cifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0


#//10.0.1.125/photo  /media/Photos cifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0


#//10.0.1.125/video  /media/Movies cifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0


#//10.0.1.125/music  /media/Musiccifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0


#//10.0.1.125/documents  /media/NAS-Documentscifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0


--


ありがとうございます

Arigatou Gozaimasu.

Scott David Sutton

LINUX
JOINT THE REVOLUTION!

Every facet  every compartment of your mind
needs to be programmed by you.
Unless you assume your rightful responsibility
and begin to program your own mind
The world will program it for you.

The Crystal Method

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=dbe17944-35f1-4c6e-bad2-8ff642a90703 /   ext4
errors=remount-ro 0   1
# swap was on /dev/sda5 during installation
UUID=3b967a80-d527-4e3e-a239-e216f70ea78f noneswapsw
  0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0

#additional Drive
#/dev/sdc1  /media/MultiMedia ntfs-3g defaults,locale=en_US.utf8 0 0
#UUID=16CA1C95CA1C736B /mnt/MultiMedia  ntfs-3g defaults,locale=en_US.utf8 0 0

# DiskStation

#//10.0.1.125/software  /media/Software cifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0

#//10.0.1.125/photo /media/Photos   cifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0

#//10.0.1.125/video /media/Movies   cifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0

#//10.0.1.125/music /media/Musiccifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0

#//10.0.1.125/documents  /media/NAS-Documents   cifs 
username=HTPC,password=tp3gR.17,uid=1000,umask=000,exec   0 0


Re: Replacing systemd in Jessie

2014-11-27 Thread Patrick Bartek
On Thu, 27 Nov 2014, John Hasler wrote:

> Patrick Bartek writes:
> > It seems systemd cannot not be installed in Jessie.
> 
> You mean Testing.  Jessie has not been released.

Semantics.

B



-- 
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/20141127200235.46040...@debian7.boseck208.net



Re: Replacing systemd in Jessie

2014-11-27 Thread The Wanderer
On 11/27/2014 at 09:33 PM, John Hasler wrote:

> Patrick Bartek writes:
> 
>> It seems systemd cannot not be installed in Jessie.
> 
> You mean Testing.  Jessie has not been released.

My understanding of the way the Debian release codenames work / are used
is that current testing (AKA "the current testing release") is codenamed
jessie, and when it changes from being a testing release to being the
latest stable release it will still be codenamed jessie, and the new
testing will be - or, as the case happens to be, has been - given a new
codename.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature


Re: Replacing systemd in Jessie

2014-11-27 Thread John Hasler
Patrick Bartek writes:
> It seems systemd cannot not be installed in Jessie.

You mean Testing.  Jessie has not been released.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA


-- 
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/87h9xk3vh1@thumper.dhh.gt.org



Replacing systemd in Jessie

2014-11-27 Thread Patrick Bartek

It seems systemd cannot not be installed in Jessie.  It can only be replaced 
once first installed unless one wishes to create a custom CD with another init. 
 I don't.  Even preseeding won't accomplish this.  Recommended preseeding 
procedures I've seen just automate the replacement process.

Now the strange thing:  I've done some research, and it seems that all the init 
replacement procedures start with first replacing systemd with sysvinit, then 
proceeding with replacing sysvinit with the desired init.  Anyone have info or 
instructions to the contrary? I'd like to be able to just install the desired 
init without an intermediate step.

I'm concerned specifically with runit.

Thanks.

B


-- 
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/20141127173157.06852...@debian7.boseck208.net



Re: Systemd debugging

2014-11-27 Thread Haines Brown
On Thu, Nov 27, 2014 at 05:22:55PM -0500, Haines Brown wrote:
> On Thu, Nov 27, 2014 at 06:23:06PM +0100, Sven Joachim wrote:
> > > If .../kernel/drivers/block/loop.ko was loaded, why not it87.ko?
> > >
> > >   Nov 26 17:15:16 engels systemd-fsck[195]: /dev/sda1: clean,
> > > 15827/61056 files, 120381/243968 blocks
> > >   Nov 26 17:15:16 engels systemd-modules-load[201]: Inserted module 'loop'
> > >   Nov 26 17:15:16 engels kernel: loop: module loaded
> > >   Nov 26 17:15:16 engels systemd-modules-load[201]: Inserted module
> > > 'coretemp'
> > >   Nov 26 17:15:16 engels systemd-modules-load[201]: Failed to insert
> > > 'it87': No such device
> > 
> > I'm not familiar with the it87 module, but do you actually have the
> > hardware which it controls?  If not, then it's not too surprising that
> > trying to load it fails with ENODEV.
> 
> The module supports the lm-sensors application that monitors hardware
> state such as CPU temperatures and fans. In fact, with the # sensors
> command I do get readings for the Jessie box, even though lm-sensors is 
> not using the it87 module.  

I thought I'd append a bit more and specifically the reason why it87
could not be loaded. In lm-sensors configuration for Wheezy, it said to
put two modules into /etc/modules: coretemp and it87. When lm-sensors
run under my current hardware with Jessie, it only says to add the
coretemp module. When I comment the it87, I no longer the the FAILURE
message during boot. 

My # sensors command no longer provides fan speeds and ALARM, which I'll
have to investigate some other time, but it seems it87 module not
relevant to this.

Haines


-- 
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/20141127235325.go5...@historicalmaterialism.info



Re: ntpd confusion

2014-11-27 Thread Bob Proulx
mad wrote:
> I found it. It was DHCP. The NTP init scripts checks if there is a file
> /var/lib/ntp/ntp.conf.dhcp in which the local router is configured as
> only ntp source.

Thank you for posting the resolution of the problem!

Bob


signature.asc
Description: Digital signature


Linux entropy pool / random number benchmark

2014-11-27 Thread David Christensen

debian-user:

I found some informative articles about Linux and the Intel Secure Key 
processor feature:



https://software.intel.com/en-us/articles/performance-impact-of-intel-secure-key-on-openssl


http://blog.cloudflare.com/ensuring-randomness-with-linuxs-random-number-generator/


It appears that openssl gives you direct access to Secure Key, while the 
Linux kernel uses Secure Key to stir an entropy pool that is fed into 
SHA-1 to produce random numbers.  So, openssl and /dev/random should 
show speed improvements on a processor with Secure Key, and /dev/urandom 
should have better entropy.



Below please find a Perl script for benchmarking the Linux entropy pool 
and random numbers, and two sample runs on a Wheezy 7.7 i386 machine 
with a Pentium 4 3.4E GHz HT processor (does not have Secure Key):


1.  The first run was with an idling machine and a low entropy pool to 
begin with.


2.  The second run was started after rapidly typing random garbage into 
another terminal and continuing to type during the run.



Could somebody with a Secure Key processor please run the script and 
post the results?



David


$ cat `which entropy-random-bench `
#!/usr/bin/perl

eval 'exec /usr/bin/perl  -S $0 ${1+"$@"}'
if 0; # not running under some shell
# $Id: entropy-random-bench,v 1.7 2014/11/27 21:58:22 dpchrist Exp $
###
# Argument defaults -- edit to suit:

my $entropy = '/proc/sys/kernel/random/entropy_avail';
my $random  = '/dev/urandom';
my $duration=   60.0;   # seconds
my $entropy_upper   = 4095; # bits
my $entropy_lower   =0; # bits
my $nap_upper   =   10.0;   # seconds
my $nap_lower   =1.0E-06;   # seconds
my $gain=   10.0;   # seconds / bit

###
# The rest of the script should not be edited:

use strict;
use warnings;

use Getopt::Longqw(
:config
auto_help
auto_version
);
use Pod::Usage;
use Time::HiRes qw( sleep time );

$| = 1;

our $VERSION= sprintf("%d.%03d", q$Revision: 1.7 $ =~ /(\d+)/g);
my $man;

GetOptions(
"entropy=s"   => \$entropy,
"random=s"=> \$random,
"duration=f"  => \$duration,
"entropy-upper=f" => \$entropy_upper,
"entropy-lower=f" => \$entropy_lower,
"nap-upper=f" => \$nap_upper,
"nap-lower=f" => \$nap_lower,
"gain=f"  => \$gain,
"man" => \$man,
) or pod2usage(2);
pod2usage(-exitstatus => 0, -verbose => 2) if $man;

my $entropy_span= $entropy_upper - $entropy_lower;
my $entropy_setpoint= $entropy_upper / 2;
my $nap_span= $nap_upper - $nap_lower;
my $nap_offset  = $nap_upper / 2;

my $err;
my $buf;
my $e1;
my $e2;
my $t1;
my $t2;
my $rate;
my $dt;
my $signal;
my $nap = $nap_lower;
my $lastprint;

open(my $random_fh, $random) or die "error opening $random: $!";
$err = sysread($random_fh, $buf, 1);
die "error reading $random: $!" unless defined $err && $err;

### /proc/sys/kernel/random/entropy_avail is not world-readable, but
### 'cat' can read it (?)
$e1 = `cat $entropy`;
chomp $e1;

print "time (seconds)  entropy (bits)  random (bytes/second)\n",
  "==  ==  ==\n";
my $begin = $lastprint = $t1 = time();
my $end = $begin + $duration;
do {
sleep($nap);

$err = sysread($random_fh, $buf, 1);
die "error reading $random: $!" unless defined $err;

$e2 = `cat $entropy`;
chomp $e2;

$t2 = time();
$dt = $t2 - $t1;
$rate = 1.0 / $dt;
if ($dt && ($lastprint + 1 < $t2)) {
$lastprint = $t2;
printf "%14.06f  %14i  %22.6f\n",
$t2 - $begin,
$e2,
$rate;
}
$signal = ($e2 - $entropy_setpoint) / $entropy_span;
$nap = -1.0 * $gain * $signal * $nap_span + $nap_offset;
$nap = $nap_lower if $nap   < $nap_lower;
$nap = $nap_upper if $nap_upper < $nap;
$e1 = $e2;
$t1 = $t2;
} while ($t2 < $end);
DONE:

__END__

=head1 NAME

entropy-random-bench - Linux entropy pool / random number benchmark

=head1 SYNOPSIS

 entropy-random-bench.pl [options]

  Options:
   --entropypath to entropy availble file
   --random path to random number file
   --duration   duration of benchmark
   --entropy-upper  upper range value of entropy available
   --entropy-lower  lower range value of entropy available
   --nap-upper  upper range value for sleep() calls
   --nap-lower  upper range value for sleep() calls
   --gain   timing loop proportional gain
   --man

Re: Systemd debugging

2014-11-27 Thread Haines Brown
On Thu, Nov 27, 2014 at 06:23:06PM +0100, Sven Joachim wrote:
> > If .../kernel/drivers/block/loop.ko was loaded, why not it87.ko?
> >
> >   Nov 26 17:15:16 engels systemd-fsck[195]: /dev/sda1: clean,
> > 15827/61056 files, 120381/243968 blocks
> >   Nov 26 17:15:16 engels systemd-modules-load[201]: Inserted module 'loop'
> >   Nov 26 17:15:16 engels kernel: loop: module loaded
> >   Nov 26 17:15:16 engels systemd-modules-load[201]: Inserted module
> > 'coretemp'
> >   Nov 26 17:15:16 engels systemd-modules-load[201]: Failed to insert
> > 'it87': No such device
> 
> I'm not familiar with the it87 module, but do you actually have the
> hardware which it controls?  If not, then it's not too surprising that
> trying to load it fails with ENODEV.

The module supports the lm-sensors application that monitors hardware
state such as CPU temperatures and fans. In fact, with the # sensors
command I do get readings for the Jessie box, even though lm-sensors is 
not using the it87 module.  

> > Then there's something wrong when Console Kit and Policy Kit loaded.
> > Both were ultimately activated, but something about page size failed:
> >
> >   Nov 26 17:17:36 engels dbus[723]: [system] Activating via systemd: 
> > service name='org.freedesktop.ConsoleKit' 
> > unit='console-kit-daemon.service'
> >   Nov 26 17:17:36 engels console-kit-daemon[1310]: (process:1373): 
> > GLib-CRITICAL **: g_slice_set_config: assertion 
> > 'sys_page_size == 0' failed
> 
> This seems to be https://bugs.debian.org/718843.  Maybe you should just
> remove consolekit, it's deprecated and replaced by systemd-logind.

I did so and rebooted successfully.

> > This immediately followed by a problem getting IP address from my
> > router's DHCP. The box has wifi card, but no ethernet cable. Before
> > Jessie, wlan0 was assigned an address automatically, but with Jessie
> > there's no assress and wlan-avahi instead gets a bogus address. I can
> > do ifdown/ifup and get an IP address, but should not have to. Is DBus
> > blocking the connection?
> 
> No, this does not have anything to to with dbus AFAICS.
> 
> >   Nov 26 17:17:52 engels ntpd[896]: Deferring DNS for 
> > 1.debian.pool.ntp.org 1
> >   Nov 26 17:17:53 engels console-kit-daemon[1310]: (process:1540): 
> > GLib-CRITICAL **: g_slice_set_config: assertion 
> > 'sys_page_size == 0' failed
> >   Nov 26 17:17:55 engels dhclient[585]: DHCPDISCOVER on 
> > eth0 to 255.255.255.255 port 67 interval 15
> >   Nov 26 17:17:55 engels ifup[573]: DHCPDISCOVER on 
> > eth0 to 255.255.255.255 port 67 interval 15
> >   Nov 26 17:18:06 engels org.gtk.vfs.Daemon[1545]: A connection to 
> > the bus can't be made
> >   Nov 26 17:18:06 engels org.gtk.vfs.Daemon[1545]: 
> > g_dbus_connection_real_closed: Remote peer vanished with error: 
> > Underlying GIOStream returned 0 bytes on an async read 
> > (g-io-error-quark, 0). Exiting.
> >   Nov 26 17:18:06 engels console-kit-daemon[1310]: (process:1597): 
> > GLib-CRITICAL **: g_slice_set_config: assertion 
> > 'sys_page_size == 0' failed
> >   Nov 26 17:18:07 engels console-kit-daemon[1310]: (process:1599): 
> > GLib-CRITICAL **: g_slice_set_config: assertion 
> > 'sys_page_size == 0' failed
> >   Nov 26 17:18:10 engels dhclient[585]: No DHCPOFFERS received.
> 
> That's the problem, but without knowing how you connect to your router
> (network-manager, ifupdown…) it's hard to tell why you don't get any
> DHCPOFFERS from it.

I find that on the reboot that I now connect to wlan0 automatically as
I would expect. Is it possible that removal of consolekit allowed the 
network interface to get the IP address from DHCP?

Thanks for the clarifications,

Haines


-- 
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/2014112755.gn5...@historicalmaterialism.info



Re: ALSA - Multiple Sources...? / Thanks

2014-11-27 Thread hobie
Just a note of thanks to Joel, Andrei and Florent. :)  I'll carry my
situation to the Audio users list and see what happens.  Thanks for the
time and the courteous comments.

--hobie

> On Thu, Nov 27, 2014 at 04:56:12AM -0500, ho...@rumormillnews.com wrote:
>> > On Jo, 27 nov 14, 03:03:33, ho...@rumormillnews.com wrote:
>> >> > On Wed, Nov 26, 2014 at 05:55:24PM -0500, ho...@rumormillnews.com
>> >> wrote:
>> >> >
>> >> > Do you know if pulseaudio is installed?
>> >> >
>> >> > dpkg -l | grep pulseaudio
>> >>
>> >> Hi, Joel - Thanks. :)  Synaptic says "no" but running the dpkg -l
>> >> command
>> >> indicates pulseaudio 2.0.3 is present. (!)  It isn't, but there's a
>> fair
>> >> number of residual files around from some earlier install, including
>> >> things like the gstreamer1.0-pulseaudio plugin and PulseAudio client
>> >> libraries.  I don't _think_ there's anything there that would cause
>> ALSA
>> >> to block...?
>> >
>> > Would you mind just copy-pasting the output of above command?
>> >
>> > BTW, interpreting the output of 'dpkg -l' would be easier if one would
>> > not use grep to strip the header with explanations and use only dpkg's
>> > built-in pattern support, in this particular case:
>> >
>> > dpkg -l '*pulseaudio*'
>> >
>> > Thanks,
>> > Andrei
>> > --
>>
>> Thanks, Andrei - here 'tis:
>>
>> Desired=Unknown/Install/Remove/Purge/Hold
>> |
>> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
>> ||/ Name   Version  Architecture Description
>> +++-==---=
>> ii  gstreamer0.10- 0.10.31-3+nm amd64GStreamer plugin for
>> PulseAudio
>> ii  gstreamer1.0-p 1.4.4-2  amd64GStreamer plugin for
>> PulseAudio
>> un  libsdl1.2debia   (no description available)
>> rc  pulseaudio 2.0-3amd64PulseAudio sound server
>> un  pulseaudio-eso   (no description available)
>> un  pulseaudio-mod   (no description available)
>> un  pulseaudio-uti   (no description available)
>
>
> Okay, no pulseaudio.
>
> This reference says you get dmix by default
> for ALSA, version above 1.0.9rc2. So several
> years.
>
> http://alsa.opensrc.org/Dmix
>
> You also want to make sure there is no asoundrc.
>
> Probably you will get better help if you post
> to Linux Audio Users mailing list.
>
> It may help to know the output of
>
> lspci
>
> cat /proc/asound/cards
>
> lsmod | grep snd
>
>
> Hope this helps
>
>
> --
> 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/20141127103501.GA359@sprite
>
>


-- 
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/65689244064ef478e9046cefc3819056.squir...@dragon.rumormillnews.com



Re: Haven't seen this ssh output before

2014-11-27 Thread Jochen Spieker
Harry Putnam:
> Harry Putnam  writes:
> 
> …
>KexAlgorithms   
> curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1
> 
> That also works.  

Thanks for posting your solution and what you tried.

> Now, since debian chose to follow the new upstream sshd defaults and
> limits due to `UNSAFE' alg.  I'm wondering if by adding one of those
> discarded algs back in there... I may be creating a security hole.

I am not qualified to give an answer to that, I usually trust upstream's
or the maintainer's defaults. You will probably receive the best answers
on OpenSSH related mailing lists. Maybe it is even already explained
there.

But, as far as I understand, if the key exchange algorithm is really
unsafe, the risk is probably that someone might eavesdrop on your
connection. This is especially problematic since you are using password
authentication because the password can be read as well (if the key
exchange is unsafe).

J.
-- 
I have been manipulated and permanently distorted.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature


Re: Purging a package............... (and apt-config processing order)

2014-11-27 Thread Nemeth Gyorgy
2014-11-25 05:14 keltezéssel, The Wanderer írta:
>> I don't know whether /etc/apt/apt.conf is processed before fragments
>> in /etc/apt/apt.conf.d  - but I'd be interested in learning.
>> Anyone??
> 
> Now that you bring it up, I'd be interested in that myself. Fortunately,
> it's trivially discoverable:
> 
> $ strace apt-get --dry-run autoremove &> /tmp/apt-dryrun-autoremove.strace
> $ grep apt.conf /tmp/apt-dryrun-autoremove.strace
> 
> I'm not going to paste the output here, but apparently the fragment
> files are processed first.
> 
Perhaps 'apt-config dump' command helps to find out the proper order.

-- 
--- Friczy ---
'Death is not a bug, it's a feature'


-- 
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/54778e24.9080...@freemail.hu



_netdev with wpa_supplicant dependency doesn't work at shutdown

2014-11-27 Thread Javier Barroso
Hello,

I'm trying to solve my own reported bug [1]

When I add a curlfs fstab entry via wifi (wpa_supplicant), it get
mount at boot, but it does not umount when system is halting / at
shutdown. Wpa_supplicant stop before than curlftpfs umount the mount
point (xx.mount).

I have been playing with "After  / Before /Requires" parameters both,
but I'm getting tired .. I'm not able to make it work :(

What I have tried:

1. Modify fstab-generator , so xx.mount depends on :
1.1 network-online.target
1.2 wpa_supplicant.service

2. Modify wpa_supplicant.service, so depends on:
2.1 xx.mount
2.2 remote-fs.target

Do you have any hint about this issue ? How can I get it working ?

How can I say to systemd about not stop wpa_supplicant until xx.mount
is umounted ??

Thank you very much
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769186


-- 
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/cal5ymzrs5kzb_fz5gedjptdcj8+mmumuzq9f32up79aqx35...@mail.gmail.com



Re: ALSA - Multiple Sources...?

2014-11-27 Thread Florent Peterschmitt
On 11/27/2014 10:53 AM, ho...@rumormillnews.com wrote:
[snip]
> Agreed. :)  dpkg -l says:
> 
>  dpkg -l |grep pulseaudio
> ii  gstreamer0.10-pulseaudio:amd64 
> 0.10.31-3+nmu4+b1  amd64GStreamer plugin for
> PulseAudio
> ii  gstreamer1.0-pulseaudio:amd64   1.4.4-2   
> amd64GStreamer plugin for PulseAudio
> rc  pulseaudio  2.0-3 
> amd64PulseAudio sound server
> 
> Maybe the 'rc' at the start of that line has a meaning I don't know? 
> Anyway - it looks like pulseaudio is not actually present.  I agree, too,
> that ALSA should allow mixing without extra configuration.  That's what it
> had been doing for years, until a recent update apparently changed
> something.
> 
> --hobie
> 
> 


"rc" means you have some configuration files lying around your system.

apt-get purge pulseaudio will remove them.



signature.asc
Description: OpenPGP digital signature


Re: ALSA - Multiple Sources...?

2014-11-27 Thread Andrei POPESCU
On Jo, 27 nov 14, 04:56:12, ho...@rumormillnews.com wrote:
> 
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name   Version  Architecture Description
> +++-==---=
...
> rc  pulseaudio 2.0-3amd64PulseAudio sound server

If you follow the lines you will notice that 'r' means "Desired=Remove" 
and 'c' means "Status=Conf-files". In other words "removed but not 
purged".

You might want to 'apt-get purge pulseaudio' to eliminate the 
possibility that it's conffiles somehow interfere (though I doubt it).

On the other hand, your use-case is exactly what pulseaudio was designed 
to do, so you might want to try installing it instead.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature


Re: ntpd confusion

2014-11-27 Thread mad
I found it. It was DHCP. The NTP init scripts checks if there is a file
/var/lib/ntp/ntp.conf.dhcp in which the local router is configured as
only ntp source.

Am 11/24/14 16:11, schrieb Chen Wei:
> On Mon, Nov 24, 2014 at 10:58:29AM +0100, mad wrote:
>> mentioned, other Debian installations not on my home network, with the
>> same configuration show as expected four clock sources. Even starting
>> ntpd on the command line doesn't show any more data and ntpd is compiled
>> without debugging. Probably that is what I will do, recompile ntpd with
>> debug enabled and then see what ntpd is actually doing.
>>
> 
> Besides recompile with debug level option, I would also suggest try the
> NTP mailing list.
> 
>> Could it have something to do with upnp, zeroconf or something like that?
>>
> 
> No idea.
> 
> 


-- 
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/547774ca.8070...@sharktooth.de



aa-logprof/aa-genprof not working after jessie upgrade

2014-11-27 Thread Simon Brandmair
Hi everyone,

I recently upgrade to jessie. I noticed now that aa-logprof/aa-genprof
(for apparmor) stopped working. When I try to create a new profile with
aa-genprof it doesn't add any rules while I see them in the logs. Same
with aa-logprof (both worked just fine in wheezy) . I don't know how to
debug this further. Is this a bug in the jessie packages or did I miss
something in the upgrade progress?

Cheers,
Simon


-- 
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/m57rlt$eie$1...@news.albasani.net



Re: Systemd debugging

2014-11-27 Thread Sven Joachim
On 2014-11-27 14:59 +0100, Haines Brown wrote:

> On Thu, Nov 27, 2014 at 12:06:20AM +0200, Andrei POPESCU wrote:
>
>> You can use this instead
>> 
>> journalctl -alb
>
> Andrei, I did as you suggested, but I'm not sure if the result really
> adds anything substantive.

It is actually quite useful.

> Then the failed to insert module problem. I find that in fact I do have 
> /lib/modules/3.12.0-4-686-pae/kernel/drivers/hwmon/it87.ko on this box.
> When it87 not inserted, were all further module insertions terminated?

I don't think so.

> If .../kernel/drivers/block/loop.ko was loaded, why not it87.ko?
>
>   Nov 26 17:15:16 engels systemd-fsck[195]: /dev/sda1: clean,
> 15827/61056 files, 120381/243968 blocks
>   Nov 26 17:15:16 engels systemd-modules-load[201]: Inserted module 'loop'
>   Nov 26 17:15:16 engels kernel: loop: module loaded
>   Nov 26 17:15:16 engels systemd-modules-load[201]: Inserted module
> 'coretemp'
>   Nov 26 17:15:16 engels systemd-modules-load[201]: Failed to insert
> 'it87': No such device

I'm not familiar with the it87 module, but do you actually have the
hardware which it controls?  If not, then it's not too surprising that
trying to load it fails with ENODEV.

> Then there's the report about not being able to mount /usb although in
> fact it is mounted and accessible. Was it initially seen as ro? Does
> this mean that the remount command succeeded to mount /usr on second
> try without ro?

No, it probably means that /usr was not mounted in the first place;
systemd-remount-fs expects that /usr is mounted by the initramfs which
is not the case for initramfs-tools in jessie.  This is rather harmless,
though.

> Then there's something wrong when Console Kit and Policy Kit loaded.
> Both were ultimately activated, but something about page size failed:
>
>   Nov 26 17:17:36 engels dbus[723]: [system] Activating via systemd: 
> service name='org.freedesktop.ConsoleKit' 
> unit='console-kit-daemon.service'
>   Nov 26 17:17:36 engels console-kit-daemon[1310]: (process:1373): 
> GLib-CRITICAL **: g_slice_set_config: assertion 
> 'sys_page_size == 0' failed

This seems to be https://bugs.debian.org/718843.  Maybe you should just
remove consolekit, it's deprecated and replaced by systemd-logind.

> This immediately followed by a problem getting IP address from my
> router's DHCP. The box has wifi card, but no ethernet cable. Before
> Jessie, wlan0 was assigned an address automatically, but with Jessie
> there's no assress and wlan-avahi instead gets a bogus address. I can
> do ifdown/ifup and get an IP address, but should not have to. Is DBus
> blocking the connection?

No, this does not have anything to to with dbus AFAICS.

>   Nov 26 17:17:52 engels ntpd[896]: Deferring DNS for 
> 1.debian.pool.ntp.org 1
>   Nov 26 17:17:53 engels console-kit-daemon[1310]: (process:1540): 
> GLib-CRITICAL **: g_slice_set_config: assertion 
> 'sys_page_size == 0' failed
>   Nov 26 17:17:55 engels dhclient[585]: DHCPDISCOVER on 
> eth0 to 255.255.255.255 port 67 interval 15
>   Nov 26 17:17:55 engels ifup[573]: DHCPDISCOVER on 
> eth0 to 255.255.255.255 port 67 interval 15
>   Nov 26 17:18:06 engels org.gtk.vfs.Daemon[1545]: A connection to 
> the bus can't be made
>   Nov 26 17:18:06 engels org.gtk.vfs.Daemon[1545]: 
> g_dbus_connection_real_closed: Remote peer vanished with error: 
> Underlying GIOStream returned 0 bytes on an async read 
> (g-io-error-quark, 0). Exiting.
>   Nov 26 17:18:06 engels console-kit-daemon[1310]: (process:1597): 
> GLib-CRITICAL **: g_slice_set_config: assertion 
> 'sys_page_size == 0' failed
>   Nov 26 17:18:07 engels console-kit-daemon[1310]: (process:1599): 
> GLib-CRITICAL **: g_slice_set_config: assertion 
> 'sys_page_size == 0' failed
>   Nov 26 17:18:10 engels dhclient[585]: No DHCPOFFERS received.

That's the problem, but without knowing how you connect to your router
(network-manager, ifupdown…) it's hard to tell why you don't get any
DHCPOFFERS from it.

Cheers,
   Sven


--
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/87d2881rt1@turtle.gmx.de



Re: Systemd debugging

2014-11-27 Thread Haines Brown
On Thu, Nov 27, 2014 at 12:06:20AM +0200, Andrei POPESCU wrote:
> On Mi, 26 nov 14, 12:27:00, Haines Brown wrote:
> > I intalled Jessie and ran into troubles. One of them was an error mesage
> > during boot: Failed to Start Load Kernel Modules. Neverthess, I could
> > boot successfully. I do have /lib/modules/3.16.0-4-686-pae. 
> > 
> > In pursuing this issue, the first thing I found out was that bootlogd is
> > not used with systemd. 
> 
> You can use this instead
> 
> journalctl -alb

Andrei, I did as you suggested, but I'm not sure if the result really
adds anything substantive.

I start the command:

  -- Logs begin at Wed 2014-11-26 17:15:15 EST, end at Thu 2014-11-27
 07:37:20 EST. --
  Nov 26 17:15:15 engels systemd-journal[202]: Runtime journal is using 
8.0M (max allowed 322.3M, trying to leave 483.5M free of 3.1G 
available current limit 322.3M).

Then the failed to insert module problem. I find that in fact I do have 
/lib/modules/3.12.0-4-686-pae/kernel/drivers/hwmon/it87.ko on this box.
When it87 not inserted, were all further module insertions terminated?
If .../kernel/drivers/block/loop.ko was loaded, why not it87.ko?

  Nov 26 17:15:16 engels systemd-fsck[195]: /dev/sda1: clean,
15827/61056 files, 120381/243968 blocks
  Nov 26 17:15:16 engels systemd-modules-load[201]: Inserted module 'loop'
  Nov 26 17:15:16 engels kernel: loop: module loaded
  Nov 26 17:15:16 engels systemd-modules-load[201]: Inserted module
'coretemp'
  Nov 26 17:15:16 engels systemd-modules-load[201]: Failed to insert
'it87': No such device
  Nov 26 17:15:16 engels systemd[1]: systemd-modules-load.service: main 
process exited, code=exited, status=1/FAILURE
  Nov 26 17:15:16 engels systemd[1]: Failed to start Load Kernel Modules.
  Nov 26 17:15:16 engels systemd[1]: Unit systemd-modules-load.service 
entered failed state.

Then there's the report about not being able to mount /usb although in
fact it is mounted and accessible. Was it initially seen as ro? Does
this mean that the remount command succeeded to mount /usr on second
try without ro?

  Nov 26 17:15:17 engels hdparm[357]: Setting parameters of disc: (none).
  Nov 26 17:15:17 engels systemd-fsck[350]: /dev/sda5: recovering journal
  Nov 26 17:15:17 engels systemd-remount-fs[356]: mount: /usr not
mounted or bad option
  Nov 26 17:15:17 engels systemd-remount-fs[356]: In some cases useful 
info is found in syslog - try
  Nov 26 17:15:17 engels systemd-remount-fs[356]: dmesg | tail or so.
  Nov 26 17:15:17 engels systemd-remount-fs[356]: /bin/mount for /usr 
exited with exit status 32.
  Nov 26 17:15:17 engels systemd[1]: systemd-remount-fs.service: main 
process exited, code=exited, status=1/FAILURE
  Nov 26 17:15:17 engels systemd[1]: Failed to start Remount Root and 
Kernel File Systems.
  Nov 26 17:15:17 engels systemd[1]: Unit systemd-remount-fs.service 
entered failed state.
  Nov 26 17:15:17 engels kernel: EXT4-fs (sda1): re-mounted. Opts: 
errors=remount-ro

Then there's something wrong when Console Kit and Policy Kit loaded.
Both were ultimately activated, but something about page size failed:

  Nov 26 17:17:36 engels dbus[723]: [system] Activating via systemd: 
service name='org.freedesktop.ConsoleKit' 
unit='console-kit-daemon.service'
  Nov 26 17:17:36 engels console-kit-daemon[1310]: (process:1373): 
GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Nov 26 17:17:36 engels console-kit-daemon[1310]: missing action
  Nov 26 17:17:36 engels dbus[723]: [system] Activating via systemd: 
service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
  Nov 26 17:17:36 engels polkitd[1376]: started daemon version 0.105 
using authority implementation `local' version `0.105'
  Nov 26 17:17:36 engels dbus[723]: [system] Successfully activated 
service 'org.freedesktop.PolicyKit1'
  Nov 26 17:17:36 engels dbus[723]: [system] Successfully activated 
service 'org.freedesktop.ConsoleKit'
  Nov 26 17:17:36 engels console-kit-daemon[1310]: (process:1386): 
GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Nov 26 17:17:51 engels console-kit-daemon[1310]: (process:1499): 
GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed

This immediately followed by a problem getting IP address from my
router's DHCP. The box has wifi card, but no ethernet cable. Before
Jessie, wlan0 was assigned an address automatically, but with Jessie
there's no assress and wlan-avahi instead gets a bogus address. I can
do ifdown/ifup and get an IP address, but should not have to. Is DBus
blocking the connection? Why ping 192.168.1.254? That's non-existent.
The router is 192.168.1.255.

  Nov 26 17:17:52 engels ntpd[896]: Deferring DNS for 
1.debian.pool.ntp.org 1
  Nov 26 17:17:53 engels console-kit-daemon[1310]: (process:1540): 
GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_siz

Re: Fwd: Gnome/X/Display device issues since before Testing freeze

2014-11-27 Thread Floris

Op Tue, 25 Nov 2014 19:10:37 +0100 schreef Floris :

Op Tue, 25 Nov 2014 02:09:10 +0100 schreef Peter Miller  
:



I've had the "Oh no! Something went wrong" screen for a couple of
weeks now, since just before Testing went into freeze.

I've looked everywhere I can and tried all sorts of things, but
nothing solves the problem. I recently upgraded to sid to see if that
helped, but still no luck.

In the included journal file below, it seems the problem lies in the
"cannot determine display-device" entry, but I can't tell what is
causing that.

I have a lot more diagnostic output, but I can't have attachments,  
apparently.


I would file a bug report, but I am not sure which package to report  
under.


One thing I have not been able to work out if is whether the memory
conflict message is an issue, and, if it is, how to solve it...

Thanks for any assistance...




Can you tell us what kind of VGA card, and which module you use?
And the output of:
journalctl -e /usr/bin/Xorg
(after a crash)

Success,

floris




The only weird thing I can found in your log is:
...

Kernel driver in use: i915

an Intel module
...

Nov 25 07:39:58 pete gdm-Xorg-:0[795]: (II) LoadModule: "glx"
Nov 25 07:39:58 pete gdm-Xorg-:0[795]: (II) Loading  
/usr/lib/xorg/modules/linux/libglx.so
Nov 25 07:39:58 pete gdm-Xorg-:0[795]: (II) Module glx: vendor="NVIDIA  
Corporation"
Nov 25 07:39:58 pete gdm-Xorg-:0[795]: compiled for 4.0.2, module  
version = 1.0.0
Nov 25 07:39:58 pete gdm-Xorg-:0[795]: Module class: X.Org Server  
Extension

Nov 25 07:39:58 pete gdm-Xorg-:0[795]: (II) NVIDIA GLX Module  340.46


Xorg is loading a Nividia module

Maybe you can use:
update-alternatives --config glx
and select the mesa option.
Or if you have a Nvidia Optimus configuration, try to use the Bumblelee  
drivers:

http://bumblebee-project.org

Success,

floris


--
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/op.xpzlr2b15k9...@jessica.jkfloris.demon.nl



Re: Why focus on systemd?

2014-11-27 Thread Joel Rees
On Thu, Nov 27, 2014 at 7:13 PM, Jonathan Dowland  wrote:
> On Wed, Nov 26, 2014 at 02:55:49PM -0700, Buntunub wrote:
>> Is this what the Debian community has devolved to?
>
> Sadly, debian-user has long failed to represent the Debian community at-large,
> and things are only getting worse.

Statistically speaking, we can't help but have a biased sample unless
the ordinary user decides to take an interest in the problems others
have. Without that interest, they don't participate here, and that's
the reason the sample is biased.

But it would even help reduce the arguing if the ordinary user would
just take an interest in writing code.

Historically speaking, though, I don't think it's getting worse.

-- 
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/caar43ioqhhryzekd64rjmqs6vmhc2_znnatdvbhae6mx3-d...@mail.gmail.com



Re: Help understanding error: skb rides the rocket

2014-11-27 Thread Henrique de Moraes Holschuh
On Thu, 27 Nov 2014, Henrique de Moraes Holschuh wrote:
> The xennet kernel driver is broken.

BTW, look here:
https://bugs.archlinux.org/task/40244

Might offer you hints of a real fix.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
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/20141127103536.gc11...@khazad-dum.debian.net



Re: ALSA - Multiple Sources...?

2014-11-27 Thread Joel Roth
On Thu, Nov 27, 2014 at 04:56:12AM -0500, ho...@rumormillnews.com wrote:
> > On Jo, 27 nov 14, 03:03:33, ho...@rumormillnews.com wrote:
> >> > On Wed, Nov 26, 2014 at 05:55:24PM -0500, ho...@rumormillnews.com
> >> wrote:
> >> >
> >> > Do you know if pulseaudio is installed?
> >> >
> >> > dpkg -l | grep pulseaudio
> >>
> >> Hi, Joel - Thanks. :)  Synaptic says "no" but running the dpkg -l
> >> command
> >> indicates pulseaudio 2.0.3 is present. (!)  It isn't, but there's a fair
> >> number of residual files around from some earlier install, including
> >> things like the gstreamer1.0-pulseaudio plugin and PulseAudio client
> >> libraries.  I don't _think_ there's anything there that would cause ALSA
> >> to block...?
> >
> > Would you mind just copy-pasting the output of above command?
> >
> > BTW, interpreting the output of 'dpkg -l' would be easier if one would
> > not use grep to strip the header with explanations and use only dpkg's
> > built-in pattern support, in this particular case:
> >
> > dpkg -l '*pulseaudio*'
> >
> > Thanks,
> > Andrei
> > --
> 
> Thanks, Andrei - here 'tis:
> 
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name   Version  Architecture Description
> +++-==---=
> ii  gstreamer0.10- 0.10.31-3+nm amd64GStreamer plugin for PulseAudio
> ii  gstreamer1.0-p 1.4.4-2  amd64GStreamer plugin for PulseAudio
> un  libsdl1.2debia   (no description available)
> rc  pulseaudio 2.0-3amd64PulseAudio sound server
> un  pulseaudio-eso   (no description available)
> un  pulseaudio-mod   (no description available)
> un  pulseaudio-uti   (no description available)
 

Okay, no pulseaudio.

This reference says you get dmix by default
for ALSA, version above 1.0.9rc2. So several
years.

http://alsa.opensrc.org/Dmix

You also want to make sure there is no asoundrc.

Probably you will get better help if you post
to Linux Audio Users mailing list.

It may help to know the output of

lspci

cat /proc/asound/cards

lsmod | grep snd


Hope this helps


-- 
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/20141127103501.GA359@sprite



Re: Why focus on systemd?

2014-11-27 Thread Jonathan Dowland
On Wed, Nov 26, 2014 at 02:55:49PM -0700, Buntunub wrote:
> Is this what the Debian community has devolved to?

Sadly, debian-user has long failed to represent the Debian community at-large,
and things are only getting worse.


-- 
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/20141127101333.ga5...@chew.redmars.org



Re: Help understanding error: skb rides the rocket

2014-11-27 Thread Henrique de Moraes Holschuh
On Thu, 27 Nov 2014, SL wrote:
> kernel: xen_netfront: xennet: skb rides the rocket: 19 slots

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317811
http://www.brendangregg.com/blog/2014-09-11/perf-kernel-line-tracing.html

Try disabling TSO in xennet:
ethtool -K eth0 sg off

> - What might be causing this issue?

The xennet kernel driver is broken.

> - Could this be a problem with the virtual host? (and why is Xen mentioned
> here)

It is the client, but yes.

> - What can I do to stop this happening?

Kill your net performance by disabling sg acceleration.  This is going to
bite you hard if you use jumbo frames (MTU > 1500).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
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/20141127102732.gb11...@khazad-dum.debian.net



Re: ALSA - Multiple Sources...?

2014-11-27 Thread hobie
> On Jo, 27 nov 14, 03:03:33, ho...@rumormillnews.com wrote:
>> > On Wed, Nov 26, 2014 at 05:55:24PM -0500, ho...@rumormillnews.com
>> wrote:
>> >
>> > Do you know if pulseaudio is installed?
>> >
>> > dpkg -l | grep pulseaudio
>>
>> Hi, Joel - Thanks. :)  Synaptic says "no" but running the dpkg -l
>> command
>> indicates pulseaudio 2.0.3 is present. (!)  It isn't, but there's a fair
>> number of residual files around from some earlier install, including
>> things like the gstreamer1.0-pulseaudio plugin and PulseAudio client
>> libraries.  I don't _think_ there's anything there that would cause ALSA
>> to block...?
>
> Would you mind just copy-pasting the output of above command?
>
> BTW, interpreting the output of 'dpkg -l' would be easier if one would
> not use grep to strip the header with explanations and use only dpkg's
> built-in pattern support, in this particular case:
>
> dpkg -l '*pulseaudio*'
>
> Thanks,
> Andrei
> --

Thanks, Andrei - here 'tis:

Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  gstreamer0.10- 0.10.31-3+nm amd64GStreamer plugin for PulseAudio
ii  gstreamer1.0-p 1.4.4-2  amd64GStreamer plugin for PulseAudio
un  libsdl1.2debia   (no description available)
rc  pulseaudio 2.0-3amd64PulseAudio sound server
un  pulseaudio-eso   (no description available)
un  pulseaudio-mod   (no description available)
un  pulseaudio-uti   (no description available)

--hobie


-- 
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/e2bf01927e665ed49ef5f16f8d7a89ed.squir...@dragon.rumormillnews.com



Re: ALSA - Multiple Sources...?

2014-11-27 Thread hobie
> On Thu, Nov 27, 2014 at 03:03:33AM -0500, ho...@rumormillnews.com wrote:
>> > On Wed, Nov 26, 2014 at 05:55:24PM -0500, ho...@rumormillnews.com
>> wrote:
>> >> For years, ALSA has allowed me to have two apps open at one time -
>> for
>> >> example, a YouTube video could be playing in my browser while vlc was
>> >> also
>> >> open, paused on playback of a 3-hour mp3.
>> >>
>> >> That's changed with a recent Debian update.  Now, if a YouTube video
>> is
>> >> playing and I try to start vlc, I get an error message:
>> >>
>> >> The audio device "dmix:CARD=CK804,DEV=0" could not be used:
>> >> Device or resource busy.
>> >>
>> >> What changed with that recent update?  I have no idea.  After lots of
>> >> Internet searching, I put this into an .asoundrc file:
>> >>
>> >> -
>> >>
>> >> pcm.!default {
>> >> type plug
>> >> slave.pcm "dmixer"
>> >> }
>> >>
>> >> pcm.dmixer {
>> >> type dmix
>> >> ipc_key 1024
>> >> slave {
>> >> pcm "hw:0,0"
>> >> period_time 0
>> >> period_size 1024
>> >> buffer_size 4096
>> >> rate 44100
>> >> }
>> >> bindings {
>> >> 0 0
>> >> 1 1
>> >> }
>> >> }
>> >>
>> >> ctl.dmixer {
>> >> type hw
>> >> card 0
>> >>
>> >> -
>> >>
>> >> That made no meaningful change to the situation that I can see.  How
>> can
>> >> I
>> >> bring back the original ALSA behavior that served me so well for
>> years?
>> >
>> > Do you know if pulseaudio is installed?
>> >
>> > dpkg -l | grep pulseaudio
>> >
>> >
>> >> Thanks in advance.
>> >>
>> >> --hobie
>> >
>> > --
>> > Joel Roth
>>
>> Hi, Joel - Thanks. :)  Synaptic says "no" but running the dpkg -l
>> command
>> indicates pulseaudio 2.0.3 is present. (!)  It isn't, but there's a fair
>> number of residual files around from some earlier install, including
>> things like the gstreamer1.0-pulseaudio plugin and PulseAudio client
>> libraries.  I don't _think_ there's anything there that would cause ALSA
>> to block...?
>
> AIUI, that if pulseaudio is running, your programs are
> not getting direct access to ALSA. There is an additional
> layer.
>
> My expertise doesn't extend to pulse audio. I recall it adds
> some convenience, like being able to provide a separate
> volume control for each app, which can help in a GUI
> environment. Nothing I need.
>
> ALSA should default to mixing. You shouldn't need any
> special asoundrc to get that.
>
> I would be surprised if aptitude and dpkg reported
> different status for the same package!
>
> cheers,
>
> Joel
>

Agreed. :)  dpkg -l says:

 dpkg -l |grep pulseaudio
ii  gstreamer0.10-pulseaudio:amd64 
0.10.31-3+nmu4+b1  amd64GStreamer plugin for
PulseAudio
ii  gstreamer1.0-pulseaudio:amd64   1.4.4-2   
amd64GStreamer plugin for PulseAudio
rc  pulseaudio  2.0-3 
amd64PulseAudio sound server

Maybe the 'rc' at the start of that line has a meaning I don't know? 
Anyway - it looks like pulseaudio is not actually present.  I agree, too,
that ALSA should allow mixing without extra configuration.  That's what it
had been doing for years, until a recent update apparently changed
something.

--hobie


-- 
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/206f13c3de9ce1fe7e3f802ba4b5a1b0.squir...@dragon.rumormillnews.com



Re: ALSA - Multiple Sources...?

2014-11-27 Thread Andrei POPESCU
On Jo, 27 nov 14, 03:03:33, ho...@rumormillnews.com wrote:
> > On Wed, Nov 26, 2014 at 05:55:24PM -0500, ho...@rumormillnews.com wrote:
> >
> > Do you know if pulseaudio is installed?
> >
> > dpkg -l | grep pulseaudio
> 
> Hi, Joel - Thanks. :)  Synaptic says "no" but running the dpkg -l command
> indicates pulseaudio 2.0.3 is present. (!)  It isn't, but there's a fair
> number of residual files around from some earlier install, including
> things like the gstreamer1.0-pulseaudio plugin and PulseAudio client
> libraries.  I don't _think_ there's anything there that would cause ALSA
> to block...?

Would you mind just copy-pasting the output of above command?

BTW, interpreting the output of 'dpkg -l' would be easier if one would 
not use grep to strip the header with explanations and use only dpkg's 
built-in pattern support, in this particular case:

dpkg -l '*pulseaudio*'

Thanks,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature


Re: ALSA - Multiple Sources...?

2014-11-27 Thread Joel Roth
On Thu, Nov 27, 2014 at 03:03:33AM -0500, ho...@rumormillnews.com wrote:
> > On Wed, Nov 26, 2014 at 05:55:24PM -0500, ho...@rumormillnews.com wrote:
> >> For years, ALSA has allowed me to have two apps open at one time - for
> >> example, a YouTube video could be playing in my browser while vlc was
> >> also
> >> open, paused on playback of a 3-hour mp3.
> >>
> >> That's changed with a recent Debian update.  Now, if a YouTube video is
> >> playing and I try to start vlc, I get an error message:
> >>
> >> The audio device "dmix:CARD=CK804,DEV=0" could not be used:
> >> Device or resource busy.
> >>
> >> What changed with that recent update?  I have no idea.  After lots of
> >> Internet searching, I put this into an .asoundrc file:
> >>
> >> -
> >>
> >> pcm.!default {
> >> type plug
> >> slave.pcm "dmixer"
> >> }
> >>
> >> pcm.dmixer {
> >> type dmix
> >> ipc_key 1024
> >> slave {
> >> pcm "hw:0,0"
> >> period_time 0
> >> period_size 1024
> >> buffer_size 4096
> >> rate 44100
> >> }
> >> bindings {
> >> 0 0
> >> 1 1
> >> }
> >> }
> >>
> >> ctl.dmixer {
> >> type hw
> >> card 0
> >>
> >> -
> >>
> >> That made no meaningful change to the situation that I can see.  How can
> >> I
> >> bring back the original ALSA behavior that served me so well for years?
> >
> > Do you know if pulseaudio is installed?
> >
> > dpkg -l | grep pulseaudio
> >
> >
> >> Thanks in advance.
> >>
> >> --hobie
> >
> > --
> > Joel Roth
> 
> Hi, Joel - Thanks. :)  Synaptic says "no" but running the dpkg -l command
> indicates pulseaudio 2.0.3 is present. (!)  It isn't, but there's a fair
> number of residual files around from some earlier install, including
> things like the gstreamer1.0-pulseaudio plugin and PulseAudio client
> libraries.  I don't _think_ there's anything there that would cause ALSA
> to block...?

AIUI, that if pulseaudio is running, your programs are
not getting direct access to ALSA. There is an additional
layer.

My expertise doesn't extend to pulse audio. I recall it adds
some convenience, like being able to provide a separate
volume control for each app, which can help in a GUI
environment. Nothing I need.

ALSA should default to mixing. You shouldn't need any
special asoundrc to get that.

I would be surprised if aptitude and dpkg reported
different status for the same package!

cheers,

Joel

 
> --hobie
> 
> 
> -- 
> 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/8742c1c487c002195804001716ae43e0.squir...@dragon.rumormillnews.com
> 

-- 
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/20141127093732.GA30830@sprite



Help understanding error: skb rides the rocket

2014-11-27 Thread SL
On one of our quite busy (virtual) Debian 6 servers we are seeing a lot of
messages in the syslog like this:

kernel: xen_netfront: xennet: skb rides the rocket: 19 slots

We are seeing some connectivity problems, and I believe it's possibly
related to this. I've tried researching the issue, but can find very little
information (but have confirmed that it can cause packet loss).

Since this is on a virtual machine and we don't have access to the physical
host, one problem is knowing at what level this problem lies.  I've tried
raising this issue with the hosting company in the past, but was basically
told that it wasn't their problem.  So now I don't really know how to move
forward with diagnosis of this issue.

OS: Debian 6, Kernel:  3.15.4-x86_64-linode45

- What might be causing this issue?
- Could this be a problem with the virtual host? (and why is Xen mentioned
here)
- What can I do to stop this happening?

Thank you for any help!


Re: Why focus on systemd?

2014-11-27 Thread Mart van de Wege
Buntunub  writes:

> Wow, its Lawyer time!  Or so one would think reading through this thread.
>
> Is this what the Debian community has devolved to? Quibbling over
> technicalities of the Debian Constitution? Sure gives a lot of weight to Mr.
> Hess's departing words. That document has turned into a poison pill for this
> Distro.
>
> If we want to talk about Systemd, then talk about Systemd - its technical
> merits vs. it's cons, etc.. Leave the Lawyering to the Lawyers.
>
>
Sorry, no can do. Whenever a resolution by a project is taken with less
than consensus, and the losing party is determined to make an ass out of
themselves by being a very vocal obstructive minority, you will get
lawyering if you have *any* rules at all.

The problem is that some persons decided to use the Constitution in a
toxic manner, not the Constitution itself. This is not a unique problem
to Debian, and short of just shooting all opposition essentially
unsolvable.

Mart

-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.


-- 
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/8661e111mg@gaheris.avalon.lan



Linking to the list archives via Message-ID: [was: Re: Headless server just got suspended by updating systemd]

2014-11-27 Thread Andrei POPESCU
On Jo, 27 nov 14, 09:56:37, Scott Ferguson wrote:
> On 27/11/14 01:30, Patrick Wiseman wrote:
> > On Tue, Nov 25, 2014 at 11:50 PM, Scott Ferguson
> >> ().
> > 
> > Not sure what that's supposed to be a link to,
> 
> It's the id of your original post. I 'should' have searched the mail
> archives to find a reference that is easier for the majority to find.
> https://lists.debian.org/debian-user/2014/11/msg01613.html

It is enough to prepend http://lists.debian.org/ to the Message-ID.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature


Re: ALSA - Multiple Sources...?

2014-11-27 Thread hobie
> On Wed, Nov 26, 2014 at 05:55:24PM -0500, ho...@rumormillnews.com wrote:
>> For years, ALSA has allowed me to have two apps open at one time - for
>> example, a YouTube video could be playing in my browser while vlc was
>> also
>> open, paused on playback of a 3-hour mp3.
>>
>> That's changed with a recent Debian update.  Now, if a YouTube video is
>> playing and I try to start vlc, I get an error message:
>>
>> The audio device "dmix:CARD=CK804,DEV=0" could not be used:
>> Device or resource busy.
>>
>> What changed with that recent update?  I have no idea.  After lots of
>> Internet searching, I put this into an .asoundrc file:
>>
>> -
>>
>> pcm.!default {
>> type plug
>> slave.pcm "dmixer"
>> }
>>
>> pcm.dmixer {
>> type dmix
>> ipc_key 1024
>> slave {
>> pcm "hw:0,0"
>> period_time 0
>> period_size 1024
>> buffer_size 4096
>> rate 44100
>> }
>> bindings {
>> 0 0
>> 1 1
>> }
>> }
>>
>> ctl.dmixer {
>> type hw
>> card 0
>>
>> -
>>
>> That made no meaningful change to the situation that I can see.  How can
>> I
>> bring back the original ALSA behavior that served me so well for years?
>
> Do you know if pulseaudio is installed?
>
> dpkg -l | grep pulseaudio
>
>
>> Thanks in advance.
>>
>> --hobie
>
> --
> Joel Roth

Hi, Joel - Thanks. :)  Synaptic says "no" but running the dpkg -l command
indicates pulseaudio 2.0.3 is present. (!)  It isn't, but there's a fair
number of residual files around from some earlier install, including
things like the gstreamer1.0-pulseaudio plugin and PulseAudio client
libraries.  I don't _think_ there's anything there that would cause ALSA
to block...?

--hobie


-- 
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/8742c1c487c002195804001716ae43e0.squir...@dragon.rumormillnews.com