Re: Unable to install .iso's in virtualbox, but why?

[didier gaumet]

Le 09/09/2018 à 16:20, Sharon Kimble a écrit :
[...]
> VT-x is disabled in the BIOS for all CPU modes 
> (VERR_VMX_MSR_ALL_VMX_DISABLED).
[...]
> How can I enable 'VT-x' then please so that I can run successfully
> virtual machines on this box please?
[...]

Take a look at your Motherboard manual, page 62, section 2-30:
 
https://dlcdnets.asus.com/pub/ASUS/mb/LGA1151/PRIME_Z270-P/E12008_PRIME_Z270-P_UM_web_only_20170712.pdf

"Intel Virtualization Technology [Disabled]
When set to [Enabled], a VMM can utilize the additional hardware
capabilities provided by Vanderpool Technology. Configuration options:
[Disabled] [Enabled]"

Enter your BIOS setup program by pressing  or  at boot during
POST and change to [Enabled].

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[Brad Rogers]

On Sun, 9 Sep 2018 11:43:39 +0300
Reco  wrote:

Hello Reco,

>Moreover, apulse causes Firefox to crash since Firefox version 58, as

I've not been running apulse long, but so far, no crashes in Ff 62.

>apulse is a kludge, not a solution.

That's as may be (I don't have an opinion either way).

Sadly, however, Mozilla are withdrawing ALSA support completely (slowly,
over time) and I'm disinclined to run an ever ageing version of Ff just
to maintain sound.  In part because that brings problems of its own, what
with sites no longer working because of 'Your web browser is too old'
"error" reports.

Sometimes, you just can't win.   :-(

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
We are the chosen
Changed - Judgement Centre


pgpt42fRL_7F4.pgp
Description: OpenPGP digital signature

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[Reco]

Hi.

On Mon, Sep 10, 2018 at 09:59:03AM +0100, Brad Rogers wrote:
> On Sun, 9 Sep 2018 11:43:39 +0300
> Reco  wrote:
> 
> Hello Reco,
> 
> >Moreover, apulse causes Firefox to crash since Firefox version 58, as
> 
> I've not been running apulse long, but so far, no crashes in Ff 62.

So upstream lies then. To quote apulse's README.md:

Firefox 58 (Nightly) tightened its sandbox a bit more. Now `ioctl()`
calls are forbidden too, but are used by ALSA libraries. That causes
sandbox violation with subsequent process termination. Exception can be
added by setting parameter `security.sandbox.content.syscall_whitelist`
in `about:config`. That field accepts a comma separated list of system
call numbers. Add there `16` for x86-64, or `54` for x86 or ARM.


> >apulse is a kludge, not a solution.
> 
> That's as may be (I don't have an opinion either way).

It's the usual. A compatibility wrapper can never exceed the original.
But - if it works for anyone - more power to them.

Reco

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[Brad Rogers]

On Mon, 10 Sep 2018 12:49:01 +0300
Reco  wrote:

Hello Reco,

>On Mon, Sep 10, 2018 at 09:59:03AM +0100, Brad Rogers wrote:
>> I've not been running apulse long, but so far, no crashes in Ff 62.  
>So upstream lies then. To quote apulse's README.md:

Maybe, maybe not.  It's only been a couple of days and I've yet to
really stress load Ff.  Fear not, if I do get crashes, I'll report here.

>sandbox violation with subsequent process termination. Exception can be
>added by setting parameter `security.sandbox.content.syscall_whitelist`
>in `about:config`. That field accepts a comma separated list of system
>call numbers. Add there `16` for x86-64, or `54` for x86 or ARM.

Which I've added.  After reading various posts/complaints in multiple
places.

>It's the usual. A compatibility wrapper can never exceed the original.

Agreed.  In this case, it doesn't need to.  Well, not yet.

>But - if it works for anyone - more power to them.

I only administer a handful of machines, and this problem affects only
one of them;  All the others had PA installed when they were first set
up (bare metal installations of Debian), so no problems there.

The machine it does affect is the one that I routinely use, which has
been in use for longer than PA has been around.  I /could/ install PA,
but am reluctant to do so, since sound works here ATM and I'm concerned
that installing PA may cause issues for me.

My gut feeling/guess is that installing PA on 'virgin' hardware is fine,
by _may_ result in odd behaviour when installed on a system successfully
running ALSA and, TBH, I don't want to find out and (maybe) have to go
through another PITA session of getting sound working properly again.

Time and life are short, and spending time getting sound working isn't
something I want to waste the two on.

I'm already resigned to the fact that I'm having to use two browsers
anyway, since certain plugins I find /extremely/ useful only work in a
XUL environment, whilst others only work in a WE environment.

As I said last time;  Sometimes, you just can't win.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
This disease is catching
Into The Valley - Skids


pgpsQqWYRRuBJ.pgp
Description: OpenPGP digital signature

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[rhkramer]

On Monday, September 10, 2018 05:49:01 AM Reco wrote:
> It's the usual. A compatibility wrapper can never exceed the original.

Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how 
to say what I want to say, let me try a made-up example.

Suppose some piece of software is running (or trying to run) on a piece of 
hardware where some function does not work because the software was written to 
depend on a certain set of (let's say machine) instructions which don't exist 
on that particular machine.  But, on a Turing complete machine, I'd expect 
other instructions to exist which, perhaps by substituting a long series of 
such other instructions, the missing machine instructions could be emulated.

As a(n almost) real world example, at least once (and I'm pretty sure more 
than once) Intel built a chip that had some hardware errors (I'm remembering 
what I think is the first one, maybe as many as 20 years ago) when the floating 
point operations gave incorrect results for at least some inputs.

Intel created a fix (a compatibility layer, in my choice of words) that fixed 
the problem.

If the problem is that Firefox can't produce sound in some or all 
circumstances because it doesn't support ALSA, yet ALSA is the sound system 
running on the machine, a compatibility layer could be created that (without 
getting the details correct) translated the sound instructions that Firefox 
issues into ALSA instructions.

Hmm, did I react too much to that simple statement -- maybe, I just think it 
is an un-necessarily limiting statement to "our" thinking.

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[Curt]

On 2018-09-10, Brad Rogers  wrote:
>
> The machine it does affect is the one that I routinely use, which has
> been in use for longer than PA has been around.  I /could/ install PA,
> but am reluctant to do so, since sound works here ATM and I'm concerned
> that installing PA may cause issues for me.
>

So uninstall it then in that unfortunate case--with extreme prejudice (you
know, like, purgerino time).

Or are we dealing with the supernatural here (software from Hell)?

Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[Brad Rogers]

On Mon, 10 Sep 2018 11:53:01 + (UTC)
Curt  wrote:

Hello Curt,

>So uninstall it then in that unfortunate case--with extreme prejudice

Time.

Oh, and I can't be arsed to try PA in the first place.   :-)

>Or are we dealing with the supernatural here (software from Hell)?

I'm wary because of all the tales of woe I've read.  Obviously, there
are plenty of ppl for whom PA causes no problems at all.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Only the wounded remain, the generals have all left the game
Generals - The Damned


pgpgVfhukSSpy.pgp
Description: OpenPGP digital signature

[Solved!] Re: Getting rid of Wilber

[Siard]

10 days ago, Brad Rogers wrote:
> We still don't appear to be able to remove Wilber from the main window,
> however.

Meanwhile, I've made considerable progress though. In Gimp 2.10 in buster
there are four styles in /usr/share/gimp/2.0/themes: Dark, Gray, Light,
System.  In Light/gtkrc you'll find this code:

style "kde_hack_2"
{
  bg[NORMAL] = "#DD" #Sets canvas BG
}

Changing DD to 3C3C3C makes the background color equal to the color of
the logo, so you don't see it any more.
The same goes for Gray/gtkrc, where you can change 77 into 00.
I did not find such options for the 'Dark' and the 'System' theme though.

However, I found another great solution that works for both Gimp 2.8 in
stretch and 2.10 in buster.  It's the themes of the Gimp Theme Project:
https://www.gnome-look.org/p/1106530/
There are 6 themes, ranging from dark to light, inspired by the Adobe CS
Suite. Taken from the description: "Turn off Wilber Logo - small and big
logo turned off by default".

The download button does not seem to work nowadays, but in the comment
that starts with 'I think I've tracked it down' a download link is
mentioned, so put wget in front of it:

$ wget 
https://web.archive.org/web/20160213025658/http://rgb4u.com/share/gimp-theme-project.zip

Note, however, that gimp-theme-project.zip is a .tar.gz file, not a .zip
file. So, rename .zip to .tar.gz and unpack:

$ tar xfz gimp-theme-project.tar.gz

In the 01_Themes folder you'll find 12 themes, that is, 6 different shades
of gray, each one of them with or without some blue added.
The creator has Gimp 2.8 for Windows in mind, so the themes folder
mentioned here is C:\Users\your-user-name\.gimp-2.8\themes\ .
For Linux, this easily translates into /usr/share/gimp/2.0/themes,
or ~/.gimp-2.8/themes in stretch, or ~/.config/GIMP/2.10/themes in buster.

In Gimp, in Edit > Preferences > Interface > Theme, you can set the new
theme.
I find it's a great professional look. And most important of all, that
annoying creature has finally gone. From several places in the internet
I find that I am not the only one that would like to get rid of it.

[beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[Thomas Schmitt]

Hi,

Reco wrote:
> > It's the usual. A compatibility wrapper can never exceed the original.

rhkra...@gmail.com wrote:
> Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how
> to say what I want to say, let me try a made-up example.

I could offer my program cdrskin as real example.
It is a cdrecord/wodim compatibility wrapper but exceeds both when it
comes to DVD and BD media.


> Suppose some piece of software is running (or trying to run) on a piece of 
> hardware where some function does not work because the software was written 
> to 
> depend on a certain set of (let's say machine) instructions which don't exist 
> on that particular machine.

Or suppose a program which insists to treat every optical medium like
a CD, regardless what the specs say ...


Have a nice day :)

Thomas

Buster: Firefox-esr: can't get spell checker to work

[local10]

Hi, 

Does the spell checker works in Firefox-esr in testing? It does not work for me 
in Buster but  was working fine in Firefox-esr 52.8.0esr-1~deb7u1 in Wheezy.

Any ideas? Thanks

Preferences > Advanced > [X] Check my spelling as I type (checked)

layout.spellcheckDefault=2

sslh and libwrap0 (tcp-wrappers)

[Håkon Alstadheim]

I have an openvpn server on stretch (with some backports stuff) in
combination with sslh so that I can multiplex https and openvpn on port
443. This is needed so clients can get through a firewall.

Simplistic setup of sslh&openvpn means that openvpn and apache see all
connects as coming from localhost, so I wanted to enable tcp-wrappers
with geoip, but I can not get it to work.

When I enable hosts.{allow,deny} I have, Starting with the symptoms and
working down to my config:

- firefox showing connection failed to httpps://

- log showing:

Sep 10 15:38:10 garbo sslh[10550]: sslh-fork 1.18-1 started
Sep 10 15:38:30 garbo geofilter: [10555] Mon, 10 Sep 2018 15:38:30 +0200
uid:115 /usr/local/sbin/https-geofilter 192.168.2.201
Sep 10 15:38:30 garbo geofilter: [10555] allow: ALLOW connection from
192.168.2.201 (IP Address not found)Sep 10 16:14:17 garbo geofilter:
[16004] Mon, 10 Sep 2018 16:14:17 +0200 uid:115
/usr/local/sbin/https-geofilter 192.168.2.201

Sep 10 16:14:17 garbo geofilter: [16004] allow: ALLOW connection from
192.168.2.201 (IP Address not found)
Sep 10 16:14:17 garbo sslh[10550]: warning: /etc/hosts.allow, line 5:
process 16003 exited with signal 126
Sep 10 16:14:17 garbo sslh[10550]: aclexec returned 1
Sep 10 16:14:17 garbo sslh[10550]: connection from
gt.alstadheim.priv.no.2.168.192.in-addr.arpa(192.168.2.201): access denied

Re: Buster: Firefox-esr: can't get spell checker to work

[local10]

Sep 10, 2018, 9:40 AM by loca...@tutanota.com:

> Hi, 
>
> Does the spell checker works in Firefox-esr in testing? It does not work for 
> me in Buster but  was working fine in Firefox-esr 52.8.0esr-1~deb7u1 in 
> Wheezy.
>
> Any ideas? Thanks
>
> Preferences > Advanced > [X] Check my spelling as I type (checked)
>
> layout.spellcheckDefault=2
>

More info: Did all the steps suggested in this page ( 
http://kb.mozillazine.org/Spell_checking#Setting_up_the_spell_checker 
 ) but 
it just doesn't work for me. 

sslh and libwrap0 (tcp-wrappers and aclexec) -- [Complete version, earlier send by mistake :-/]

[Håkon Alstadheim]

(please discard the earlier misfire, I was trying to wrap the log-lines)

I have an openvpn server on stretch (with some backports stuff) in
combination with sslh so that I can multiplex https and openvpn on port
443. This is needed so clients can get through a firewall.

Simplistic setup of sslh&openvpn means that openvpn and apache see all
connects as coming from localhost, so I wanted to enable tcp-wrappers
with geoip, but I can not get it to work.

When I enable hosts.{allow,deny} I have, Starting with the symptoms and
working down to my config:

- firefox showing connection failed to httpps://

- log showing:

Sep 10 15:38:10 garbo sslh[10550]: sslh-fork 1.18-1 started
Sep 10 15:38:30 garbo geofilter: [10555] Mon, 10 Sep 2018 15:38:30\
 +0200 uid:115 /usr/local/sbin/https-geofilter 192.168.2.201
Sep 10 15:38:30 garbo geofilter: [10555] allow: ALLOW connection\
 from 192.168.2.201 (IP Address not found)
Sep 10 16:14:17 garbo geofilter: [16004] Mon, 10 Sep 2018 16:14:17\
 +0200 uid:115 /usr/local/sbin/https-geofilter 192.168.2.201
Sep 10 16:14:17 garbo geofilter: [16004] allow: ALLOW connection\
 from 192.168.2.201 (IP Address not found)
Sep 10 16:14:17 garbo sslh[10550]: warning: /etc/hosts.allow,\
 line 5: process 16003 exited with signal 126
Sep 10 16:14:17 garbo sslh[10550]: aclexec returned 1
Sep 10 16:14:17 garbo sslh[10550]: connection from\
 gt.alstadheim.priv.no.2.168.192.in-addr.arpa(192.168.2.201):\
 access denied

- Standard output where sslh is launched showing:
 /etc/init.d/sslh restart
Restarting ssl/ssh multiplexer: sslh
tls addr: localhost:https. libwrap service: https log_level: 5 family 2 2 []
openvpn addr: localhost:. libwrap service: openvpn log_level: 5
family 2 2 []
listening on:
garbo.alstadheim.priv.no:https  []
148-252-110.153.3p.ntebredband.no:https []
timeout: 3
on-timeout: openvpn
listening to 2 addresses
.
turning into sslh
capabilities: =

accepted fd 6
 writing deferred on fd -1
probing for tls
access denied

 my config: ==
---/etc/sslh/sslh.cfg:---
foreground: false;
inetd: false;
numeric: false
transparent: false;
timeout: 3;
user: "sslh";
pidfile: "/var/run/sslh/sslh.pid";
syslog_facility: "auth";

protocols:
(
 { name: "tls";service: "https"; host: "localhost"; port: "443";
log_level: 5;},
  { name: "openvpn"; service: "openvpn" ; host: "localhost"; port:
""; log_level: 5; }

);
---/etc/default/sslh---
RUN=yes
DAEMON=/usr/sbin/sslh
DAEMON_OPTS="-vv --user sslh --listen 192.168.2.2:443 --listen\
 148.252.110.153:443 --pidfile /var/run/sslh/sslh.pid --on-timeout\
 openvpn -F/etc/sslh/sslh.cfg"

---/etc/hosts.deny---
rpc.ugidd: ALL
#openvpn: ALL
https: ALL
#ssl: ALL
#anyprot: ALL
swat: ALL
#sslh: ALL
---/etc/hosts.allow---
#
rpc.ugidd: 192.168.2.0/24
#
# next line is line 5
https: ALL:aclexec /usr/local/sbin/https-geofilter %a:\
 severity auth.warning
---/usr/local/sbin/https-geofilter---
#!/bin/bash
exec>/dev/null &1

# Ansible Managed: GeoIP aclexec script for Linux TCP wrappers.
## Source: http://www.axllent.org/docs/view/ssh-geoip

# UPPERCASE space-separated country codes to ACCEPT
/usr/bin/logger -t geofilter -p authpriv.warning "[$$] `/bin/date -R`
uid:$UID $0 $*"
ALLOW_COUNTRIES="NO SE"

if [ $# -ne 1 ]; then
  echo "Usage:  `basename $0` ip" 1>&2
  exit 0 # return true in case of config issue
fi

COUNTRY=`/usr/bin/geoiplookup $1 | /usr/bin/awk -F ": " '{ print $2 }' |
/usr/bin/awk -F "," '{ print $1 }' | /usr/bin/head -n 1`

[[ $COUNTRY = "IP Address not found" || $ALLOW_COUNTRIES =~ $COUNTRY ]]
&& RESPONSE="ALLOW" || RESPONSE="DENY"
if [ $RESPONSE = "ALLOW" ]
then
/usr/bin/logger -t geofilter -p authpriv.warning "[$$] allow:
$RESPONSE connection from $1 ($COUNTRY)" || true
true
exit 0
else
  /usr/bin/logger -t geofilter -p authpriv.warning "[$$]deny: $RESPONSE
connection from $1 ($COUNTRY)" || true
  false
  exit 1
fi

--

My reading of this is that my aclexec-script gets called, and when
192.168.2.201 is not found, it logs ALLOW and returns with 'exit 0'.
Then the parent-process (as seen by the PID) then erroneously complains
that my script was terminated by a signal 126, and returns 1 (i.e.
false) to sslh.

I tried looking at the source-packages for sslh and tcp-wrappers, both
for the versions in stretch, and for tcp-wrappers also the one in
unstable, but I can not make sense of them.

Re: [beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[Reco]

Hi.

On Mon, Sep 10, 2018 at 03:37:28PM +0200, Thomas Schmitt wrote:
> Hi,
> 
> Reco wrote:
> > > It's the usual. A compatibility wrapper can never exceed the original.
> 
> rhkra...@gmail.com wrote:
> > Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how
> > to say what I want to say, let me try a made-up example.
> 
> I could offer my program cdrskin as real example.
> It is a cdrecord/wodim compatibility wrapper but exceeds both when it
> comes to DVD and BD media.

Wait. You're *the* Thomas Schmitt who wrote xorriso?
I have to take it back then. A compatibility wrapper can exceed the
original indeed.

Reco

[OT] Re: Wrappers and emulation (was Bug#908349)

[Thomas Schmitt]

Hi,

Reco wrote:
> Wait. You're *the* Thomas Schmitt who wrote xorriso?

Yep. I am the current developer of libburn, libisofs, libisoburn, cdrskin,
xorriso.

There were others involved, though.
libburn was forked from a half-dead project in 2006. Not more than 25
percent of the code is still from there. libisofs was founded by Vreixo
Formoso. I took over in 2008. Now i'd say 50 percent are by me.
Vreixo was involved in libisoburn, too. But that was only a short time.


> I have to take it back then. A compatibility wrapper can exceed the
> original indeed.

Well, xorriso _has_ two compatibility wrappers built in, but other than
cdrskin it _is_ a project without direct paragon. One can look at it as
the next step beyond growisofs by Andy Polyakov.

To be clear:
All my emulators or wrappers have their shortcommings towards the
originals (no exotic CD modes except data and audio, no UDF, no HFS).
But they also make use of capabilities of libburn or xorriso, which
are not present in cdrecord or mkisofs.

So trying to be compatible on user interface level does not tell much
about the pros and cons of original and emulator.


Have a nice day :)

Thomas

Re: [beginning OT] Re: Bug#908349: firefox-esr: no sound after upgrading from 52.9 to 60.2

[rhkramer]

On Monday, September 10, 2018 09:37:28 AM Thomas Schmitt wrote:
> I could offer my program cdrskin as real example.
> It is a cdrecord/wodim compatibility wrapper but exceeds both when it
> comes to DVD and BD media.


Thanks, for:

   * the useful example, and
   * changing the Subject: line appropriately! (for this and your later post)

Re: Encrypted e-mails?

[pjw]

On Thu, Sep 6, 2018, at 7:44 AM, Torben Schou Jensen wrote:
> With https://protonmail.com/ we have webmail with focus on encrypted
> e-mails, but it require your friends also have account there to make full
> use of it.

Since July ProtonMail is now fully interoperable with other PGP mail clients.

You can export your ProtonMail public key to non-ProtonMail contacts, so they 
can send you encrypted mail using their client of choice.  You can import their 
public PGP key, so you can send them encrypted mail.

Once that's done, email encryption can be automatic between the two of you with 
only the one party using ProtonMail.

https://protonmail.com/blog/address-verification-pgp-support/
https://protonmail.com/support/knowledge-base/how-to-use-pgp/

-pjw

Sound in Stretch

[Joe]

There's no alsa-base in Stretch. 

Should there be some other way of producing sounds?

-- 
Joe

Re: Sound in Stretch

[Greg Wooledge]

On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:
> 
> There's no alsa-base in Stretch. 
> 
> Should there be some other way of producing sounds?

If you're looking for alsamixer, it's in alsa-utils.  ALSA should just
work out of the box for most users who skip the Desktop Environment
during the installation (and therefore do not have to circumvent pulse).

The only steps required for most people are to install alsa-utils,
run alsamixer, unmute the master channels, and raise the volume of the
master channels above zero.

PGP & Protonmail (Was: Encrypted e-mails?)

[Bob Bernstein]

On Mon, 10 Sep 2018, pjw wrote:

Since July ProtonMail is now fully interoperable with 
other PGP mail clients.


Now that is a nice piece of news.

--
Fraught with portent

Re: Sound in Stretch

[Joe]

On Mon, 10 Sep 2018 16:22:38 -0400
Greg Wooledge  wrote:

> On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:
> > 
> > There's no alsa-base in Stretch. 
> > 
> > Should there be some other way of producing sounds?  
> 
> If you're looking for alsamixer, it's in alsa-utils.  ALSA should just
> work out of the box for most users who skip the Desktop Environment
> during the installation (and therefore do not have to circumvent
> pulse).
> 
> The only steps required for most people are to install alsa-utils,
> run alsamixer, unmute the master channels, and raise the volume of the
> master channels above zero.
> 

Thank you for an extremely prompt reply, but I've been there and done
that:

alsa-utils is already installed at the requested version (1.1.3-1)

alsamixer

cannot open mixer: No such file or directory

I always used to start sound troubleshooting by looking in /proc/asound
to find out what the system thought my sound cards were, but that
directory no longer exists.

This, by the way, is a clean no-X installation of Stretch, running in
hardware that previously ran Wheezy, with working sound. The sound
'card' is a cheap generic USB thing, which the kernel is seeing.
Various sound modules are loaded. I presume I've got to install or
configure something else, but I can't find the slightest clue on the
Net. One Debian sound page refers to Sarge...

-- 
Joe

-- 
Joe

Re: Sound in Stretch

[deloptes]

Joe wrote:

> alsamixer
> 
> cannot open mixer: No such file or directory
> 
> I always used to start sound troubleshooting by looking in /proc/asound
> to find out what the system thought my sound cards were, but that
> directory no longer exists.

you sure you have the driver loaded?

ls -al /proc/asound/
total 0
dr-xr-xr-x   6 root root 0 Sep 10 19:50 .
dr-xr-xr-x 253 root root 0 Sep 10 21:49 ..
dr-xr-xr-x   8 root root 0 Sep 10 19:50 card0
dr-xr-xr-x   3 root root 0 Sep 10 19:50 card1
-r--r--r--   1 root root 0 Sep 10 19:50 cards
-r--r--r--   1 root root 0 Sep 10 22:48 devices
-r--r--r--   1 root root 0 Sep 10 22:48 hwdep
-r--r--r--   1 root root 0 Sep 10 22:48 modules
dr-xr-xr-x   2 root root 0 Sep 10 22:48 oss
lrwxrwxrwx   1 root root 5 Sep 10 22:48 PCH -> card0
-r--r--r--   1 root root 0 Sep 10 22:48 pcm
dr-xr-xr-x   2 root root 0 Sep 10 22:48 seq
-r--r--r--   1 root root 0 Sep 10 22:48 timers
-r--r--r--   1 root root 0 Sep 10 22:48 version
lrwxrwxrwx   1 root root 5 Sep 10 22:48 Webcam -> card1

stretch

regards

Re: Sound in Stretch

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Sep 10, 2018 at 09:33:30PM +0100, Joe wrote:
> On Mon, 10 Sep 2018 16:22:38 -0400
> Greg Wooledge  wrote:
> 
> > On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:
> > > 
> > > There's no alsa-base in Stretch. 
> > > 
> > > Should there be some other way of producing sounds?  
> > 
> > If you're looking for alsamixer, it's in alsa-utils.  ALSA should just
> > work out of the box for most users who skip the Desktop Environment
> > during the installation (and therefore do not have to circumvent
> > pulse).
> > 
> > The only steps required for most people are to install alsa-utils,
> > run alsamixer, unmute the master channels, and raise the volume of the
> > master channels above zero.
> > 
> 
> Thank you for an extremely prompt reply, but I've been there and done
> that:
> 
> alsa-utils is already installed at the requested version (1.1.3-1)
> 
> alsamixer
> 
> cannot open mixer: No such file or directory

You could try to list your cards and devices with aplay -l

Cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluW2gIACgkQBcgs9XrR2kb4nQCfX7n92ERILwZehpOfSPeBCQe2
9wcAnAjGPYoWMLBpyI9uu2OjVImBxICg
=4GJO
-END PGP SIGNATURE-

Re: Sound in Stretch

[arne]

On Mon, 10 Sep 2018 22:49:34 +0200
deloptes  wrote:

> Joe wrote:
> 
> > alsamixer
> > 
> > cannot open mixer: No such file or directory
> > 
> > I always used to start sound troubleshooting by looking
> > in /proc/asound to find out what the system thought my sound cards
> > were, but that directory no longer exists.  
> 
> you sure you have the driver loaded?
> 
> ls -al /proc/asound/
> total 0
> dr-xr-xr-x   6 root root 0 Sep 10 19:50 .
> dr-xr-xr-x 253 root root 0 Sep 10 21:49 ..
> dr-xr-xr-x   8 root root 0 Sep 10 19:50 card0
> dr-xr-xr-x   3 root root 0 Sep 10 19:50 card1
> -r--r--r--   1 root root 0 Sep 10 19:50 cards
> -r--r--r--   1 root root 0 Sep 10 22:48 devices
> -r--r--r--   1 root root 0 Sep 10 22:48 hwdep
> -r--r--r--   1 root root 0 Sep 10 22:48 modules
> dr-xr-xr-x   2 root root 0 Sep 10 22:48 oss
> lrwxrwxrwx   1 root root 5 Sep 10 22:48 PCH -> card0
> -r--r--r--   1 root root 0 Sep 10 22:48 pcm
> dr-xr-xr-x   2 root root 0 Sep 10 22:48 seq
> -r--r--r--   1 root root 0 Sep 10 22:48 timers
> -r--r--r--   1 root root 0 Sep 10 22:48 version
> lrwxrwxrwx   1 root root 5 Sep 10 22:48 Webcam -> card1
> 
> stretch
> 
> regards
> 

does the command alsa-info give a clue?

Re: Sound in Stretch

[Brian]

On Mon 10 Sep 2018 at 21:19:09 +0100, Joe wrote:

> 
> There's no alsa-base in Stretch. 
> 
> Should there be some other way of producing sounds?

In jessie alsa-base has precisely two files:

 /usr/share/doc/alsa-base/changelog.gz
 /usr/share/doc/alsa-base/copyright

It is doubtful either of these is invovloved in the production of sound.

Also:

 
https://metadata.ftp-master.debian.org/changelogs/main/a/alsa-base/alsa-base_1.0.27+1_changelog

  * The still-useful bits of alsa-base (kmod configuration files) have moved
to kmod itself in version 17-1. There is nothing of use left in
alsa-base, so for jessie, it'll just become a dummy package that helps
cleaning up its old conffiles. It will be dropped after the jessie
release.

You obviously have some issue with sound but it is impossible to discover
what it is.

-- 
Brian.

Re: Sound in Stretch

[Joe]

On Mon, 10 Sep 2018 23:26:56 +0200
arne  wrote:

> On Mon, 10 Sep 2018 22:49:34 +0200
> deloptes  wrote:
> 
> > Joe wrote:
> >   
> > > alsamixer
> > > 
> > > cannot open mixer: No such file or directory
> > > 
> > > I always used to start sound troubleshooting by looking
> > > in /proc/asound to find out what the system thought my sound cards
> > > were, but that directory no longer exists.
> > 
> > you sure you have the driver loaded?


I have sound modules loaded, which I thought meant the driver must have
been found.

> > 
> > ls -al /proc/asound/
> > total 0
> > dr-xr-xr-x   6 root root 0 Sep 10 19:50 .
> > dr-xr-xr-x 253 root root 0 Sep 10 21:49 ..
> > dr-xr-xr-x   8 root root 0 Sep 10 19:50 card0
> > dr-xr-xr-x   3 root root 0 Sep 10 19:50 card1
> > -r--r--r--   1 root root 0 Sep 10 19:50 cards
> > -r--r--r--   1 root root 0 Sep 10 22:48 devices
> > -r--r--r--   1 root root 0 Sep 10 22:48 hwdep
> > -r--r--r--   1 root root 0 Sep 10 22:48 modules
> > dr-xr-xr-x   2 root root 0 Sep 10 22:48 oss
> > lrwxrwxrwx   1 root root 5 Sep 10 22:48 PCH -> card0
> > -r--r--r--   1 root root 0 Sep 10 22:48 pcm
> > dr-xr-xr-x   2 root root 0 Sep 10 22:48 seq
> > -r--r--r--   1 root root 0 Sep 10 22:48 timers
> > -r--r--r--   1 root root 0 Sep 10 22:48 version
> > lrwxrwxrwx   1 root root 5 Sep 10 22:48 Webcam -> card1
> > 
> > stretch
> > 
> > regards
> >   
> 
> does the command alsa-info give a clue?
> 

I didn't know about that one. It gives pages of stuff that look like
what I used to find in /proc/asound, it certainly knows all about the
USB device. No error messages, no suggestion as to what might be
missing.

-- 
Joe

Re: Sound in Stretch

[Joe]

On Mon, 10 Sep 2018 22:54:26 +0200
 wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Mon, Sep 10, 2018 at 09:33:30PM +0100, Joe wrote:
> > On Mon, 10 Sep 2018 16:22:38 -0400
> > Greg Wooledge  wrote:
> >   
> > > On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:  
> > > > 
> > > > There's no alsa-base in Stretch. 
> > > > 
> > > > Should there be some other way of producing sounds?
> > > 
> > > If you're looking for alsamixer, it's in alsa-utils.  ALSA should
> > > just work out of the box for most users who skip the Desktop
> > > Environment during the installation (and therefore do not have to
> > > circumvent pulse).
> > > 
> > > The only steps required for most people are to install alsa-utils,
> > > run alsamixer, unmute the master channels, and raise the volume
> > > of the master channels above zero.
> > >   
> > 
> > Thank you for an extremely prompt reply, but I've been there and
> > done that:
> > 
> > alsa-utils is already installed at the requested version (1.1.3-1)
> > 
> > alsamixer
> > 
> > cannot open mixer: No such file or directory  
> 
> You could try to list your cards and devices with aplay -l
> 
>

OK, aplay -l as root sees my USB device as card 1. 

I have various sound modules loaded, including snd, soundcore and
snd_usb_audio. I assume from this that my device driver has been found.

Speaker-test is unable to find any sound cards.

-- 
Joe

Re: Sound in Stretch

[Joe]

On Mon, 10 Sep 2018 22:50:30 +0100
Joe  wrote:

> On Mon, 10 Sep 2018 23:26:56 +0200
> arne  wrote:
> 
> > On Mon, 10 Sep 2018 22:49:34 +0200
> > deloptes  wrote:
> >   
> > > Joe wrote:
> > > 
> > > > alsamixer
> > > > 
> > > > cannot open mixer: No such file or directory
> > > > 
> > > > I always used to start sound troubleshooting by looking
> > > > in /proc/asound to find out what the system thought my sound
> > > > cards were, but that directory no longer exists.  
> > > 
> > > you sure you have the driver loaded?  
> 
> 
> I have sound modules loaded, which I thought meant the driver must
> have been found.
> 

It occurs to me that there are no snd_xxx_codec modules loaded. Is that
significant?

-- 
Joe

Re: update problem

[Default User]

On Sun, Sep 9, 2018, 20:09 Patrick Bartek  wrote:

> On Sun, 9 Sep 2018 10:52:39 -0400
> Default User  wrote:
>
> > UPDATE:
> >
> > Problem still occurring as of 2018-09-09 14.50 UT.
> > No indication of whether anyone else is experiencing this condition.
> >
>
> I don't run Sid/Unstable, but "updates" on both Wheezy which I ran
> for 5+ years and now Stretch on occasion stall, but very rarely like 4
> or 5 times a year. I've traced this particular "problem" to a repo that
> is not available for whatever reason. My guesses why are its files are
> being updated and access is locked out, the server is very busy and too
> overloaded to respond or is down for maintenance, its Internet access
> is off line, or my ISP is having problems.  I usually just CTRL-C out
> of it and try later which usually works.
>
> As to your "bug reports" download.  This could be the crux of your
> problem since that file is being updated to its most current status
> BEFORE it's downloaded.  My take a lot of time.
>
> And a third reason: You're using Sid.  It's called Unstable for
> multiple reasons.
>
> Have you tried using apt-get or apt instead of aptitude?  I haven't
> used aptitude since I first installed Sarge a dozen+ years ago using
> floppies.
>
> Also, besides checking your sources.list, check what's in
> sources.list.d, too.
>
> B
>
> > On Sat, Sep 8, 2018 at 3:38 PM Default User
> >  wrote:
> >
> > > Hello . . .
> > > Running Sid (amd-64) on standard x86-64 hardware, conventional
> > > software setup, nothing unusual.
> > >
> > > For several days now, after I do:
> > >
> > > sudo aptitude -Pvv update
> > >
> > > If there is anything to upgrade, if I do:
> > >
> > > sudo aptitude -Pvv safe-upgrade
> > >
> > > (or)
> > >
> > > sudo aptitude -Pvv full-upgrade
> > >
> > > it will "Get: " the new and/or update package(s), then it will
> > > STALL FOR UP TO 5 MINUTES at:
> > >
> > > Retrieving bug reports... 0%
> > >
> > > then followed by:
> > >
> > > Retrieving bug reports... Done
> > > Parsing Found/Fixed information... Done
> > > Reading changelogs... Done
> > >
> > > before finally "Unpacking, Preparing and Setting up" the packages to
> > > complete the upgrade.
> > >
> > > [See example fragment:
> > >
> > > . . .
> > >
> > > Get: 15 http://ftp.us.debian.org/debian unstable/main amd64
> > > libspice-client-glib-2.0-8 amd64 0.35-2 [528 kB]
> > > Get: 16 http://ftp.us.debian.org/debian unstable/main amd64
> > > libspice-client-gtk-3.0-5 amd64 0.35-2 [274 kB]
> > > Get: 17 http://ftp.us.debian.org/debian unstable/main amd64 redshift
> > > amd64 1.12-1 [108 kB]
> > > Fetched 5,625 kB in 5s (1,134 kB/s)
> > > Retrieving bug reports... Done
> > > Parsing Found/Fixed information... Done
> > > Reading changelogs... Done
> > > (Reading database ... 208745 files and directories currently
> > > installed.) Preparing to
> > > unpack .../00-aptitude_0.8.11-3_amd64.deb ... Unpacking aptitude
> > > (0.8.11-3) over (0.8.10-9) ... Preparing to
> > > unpack .../01-aptitude-common_0.8.11-3_all.deb ... Unpacking
> > > aptitude-common (0.8.11-3) over (0.8.10-9) ...
> > >
> > > . . . ]
> > >
> > > Note: sources list is okay:
> > >
> > > cat /etc/apt/sources.list
> > > # deb cdrom:[Debian GNU/Linux 9.4.0 _Stretch_ - Official amd64
> > > NETINST 20180310-11:21]/ buster contrib main non-free
> > >
> > > debhttp://ftp.us.debian.org/debian/unstable
> > > main  contrib  non-free
> > > deb-srchttp://ftp.us.debian.org/debian/unstable
> > > main  contrib  non-free
> > >
> > > # deb  http://security.debian.org/debian-security
> > > buster/updates main  contrib  non-free
> > > # deb-src  http://security.debian.org/debian-security
> > > buster/updates main  contrib  non-free
> > >
> > > # buster-updates, previously known as 'volatile'
> > > # deb  http://ftp.us.debian.org/debian/
> > > buster-updates main  contrib  non-free
> > > # deb-src  http://ftp.us.debian.org/debian/
> > > buster-updates main  contrib  non-free
> > >
> > > and I have run netselect-apt to find the fastest mirror:
> > >
> > > sudo netselect-apt -s -n sid
> > >
> > > (trimmed for result only:)
> > >
> > > The fastest 10 servers seem to be:
> > >
> > > http://ftp.us.debian.org/debian/
> > > http://mirror.us.leaseweb.net/debian/
> > > http://debian.ec.as6453.net/debian/
> > > http://mirror.us.oneandone.net/debian/
> > > http://ftp.us.debian.org/debian/
> > > http://mirrors.advancedhosters.com/debian/
> > > http://mirror.cogentco.com/debian/
> > > http://mirrors.gigenet.com/debian/
> > > http://mirror.steadfast.net/debian/
> > > http://ftp.utexas.edu/debian/
> > >
> > > Of the hosts tested we choose the fastest valid for HTTP:
> > > http://ftp.us.debian.org/debian/
> > >
> > > Writing sources.list.
> > > sources.list exists, moving to sources.list.1536427463
> > > Done.
> > >
> > > (As expected.)
> > >
> > > So . . .
> > > 1 - Has anyone else seen this "stall" during updating.
> > > 2 - any clue as to the cause? Maybe just a problem with

Re: Sound in Stretch

[Ric Moore]

On 09/10/2018 04:22 PM, Greg Wooledge wrote:

On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:


There's no alsa-base in Stretch.

Should there be some other way of producing sounds?


If you're looking for alsamixer, it's in alsa-utils.  ALSA should just
work out of the box for most users who skip the Desktop Environment
during the installation (and therefore do not have to circumvent pulse).

The only steps required for most people are to install alsa-utils,
run alsamixer, unmute the master channels, and raise the volume of the
master channels above zero.



You have to do that even with pulse up and running. 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.
http://linuxcounter.net/user/44256.html

Previously Bootable: Stretch using Grub with GPT, LUKS, & BTRFS

[Joel Brunetti]

Hey Team,

I'm having trouble booting a previously bootable system.
This system has been in use since very shortly before the Stretch release
and has always been Stretch.
I'm using Grub to boot a fully encrypted system. Each drive is partitioned
with GPT and encrypted using LUKS. The drives are then used together with
BTRFS.

This system has worked with some minor boot problems (Which I thought were
fixed by adding the bios_grub flag to my partition and the pmbr_boot flag
to my disk) for at least a year.
Today I can not boot the system.  I suspect I've made it worse for trying
to repair it so I will jump to where I am now.

When I boot I get on either device:
error: no such device: (UUID of my decrypted luks volume / btrfs pool)
error: unknown filesystem

I've chrooted onto the system using a usb key.
I can open my encrypted drives and mount the btrfs filesystem.
I suspected a bad kernel or grub update so I:
update initramfs -u -k all
update-grub
grub-install /dev/sda
grub-install /dev/sdb

This gives the above errors when I boot.

When I inspected /boot/grub/grub.cfg I noted it is missing "insmod
cryptodisk" and other encryption related modules. This is despite
/etc/default/grub containing "GRUB_ENABLE_CRYPTODISK=y".  I tried restoring
/boot/grub/grub.cfg from a snapshot that does include those modules and
then grub-install to both drives again but to no avail.

I'm really at a loss and could really use some help in restoring my system.

Thanks,
Joel

Re: update problem

[Jimmy Johnson]

On 09/10/2018 05:14 PM, Default User wrote:

On Sun, Sep 9, 2018, 20:09 Patrick Bartek  wrote:


On Sun, 9 Sep 2018 10:52:39 -0400
Default User  wrote:


UPDATE:

Problem still occurring as of 2018-09-09 14.50 UT.
No indication of whether anyone else is experiencing this condition.



I don't run Sid/Unstable, but "updates" on both Wheezy which I ran
for 5+ years and now Stretch on occasion stall, but very rarely like 4
or 5 times a year. I've traced this particular "problem" to a repo that
is not available for whatever reason. My guesses why are its files are
being updated and access is locked out, the server is very busy and too
overloaded to respond or is down for maintenance, its Internet access
is off line, or my ISP is having problems.  I usually just CTRL-C out
of it and try later which usually works.

As to your "bug reports" download.  This could be the crux of your
problem since that file is being updated to its most current status
BEFORE it's downloaded.  My take a lot of time.

And a third reason: You're using Sid.  It's called Unstable for
multiple reasons.

Have you tried using apt-get or apt instead of aptitude?  I haven't
used aptitude since I first installed Sarge a dozen+ years ago using
floppies.

Also, besides checking your sources.list, check what's in
sources.list.d, too.

B


On Sat, Sep 8, 2018 at 3:38 PM Default User
 wrote:


Hello . . .
Running Sid (amd-64) on standard x86-64 hardware, conventional
software setup, nothing unusual.

For several days now, after I do:

sudo aptitude -Pvv update

If there is anything to upgrade, if I do:

sudo aptitude -Pvv safe-upgrade

(or)

sudo aptitude -Pvv full-upgrade

it will "Get: " the new and/or update package(s), then it will
STALL FOR UP TO 5 MINUTES at:

Retrieving bug reports... 0%

then followed by:

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done

before finally "Unpacking, Preparing and Setting up" the packages to
complete the upgrade.

[See example fragment:

. . .

Get: 15 http://ftp.us.debian.org/debian unstable/main amd64
libspice-client-glib-2.0-8 amd64 0.35-2 [528 kB]
Get: 16 http://ftp.us.debian.org/debian unstable/main amd64
libspice-client-gtk-3.0-5 amd64 0.35-2 [274 kB]
Get: 17 http://ftp.us.debian.org/debian unstable/main amd64 redshift
amd64 1.12-1 [108 kB]
Fetched 5,625 kB in 5s (1,134 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
(Reading database ... 208745 files and directories currently
installed.) Preparing to
unpack .../00-aptitude_0.8.11-3_amd64.deb ... Unpacking aptitude
(0.8.11-3) over (0.8.10-9) ... Preparing to
unpack .../01-aptitude-common_0.8.11-3_all.deb ... Unpacking
aptitude-common (0.8.11-3) over (0.8.10-9) ...

. . . ]

Note: sources list is okay:

cat /etc/apt/sources.list
# deb cdrom:[Debian GNU/Linux 9.4.0 _Stretch_ - Official amd64
NETINST 20180310-11:21]/ buster contrib main non-free

debhttp://ftp.us.debian.org/debian/unstable
main  contrib  non-free
deb-srchttp://ftp.us.debian.org/debian/unstable
main  contrib  non-free

# deb  http://security.debian.org/debian-security
buster/updates main  contrib  non-free
# deb-src  http://security.debian.org/debian-security
buster/updates main  contrib  non-free

# buster-updates, previously known as 'volatile'
# deb  http://ftp.us.debian.org/debian/
buster-updates main  contrib  non-free
# deb-src  http://ftp.us.debian.org/debian/
buster-updates main  contrib  non-free

and I have run netselect-apt to find the fastest mirror:

sudo netselect-apt -s -n sid

(trimmed for result only:)

The fastest 10 servers seem to be:

http://ftp.us.debian.org/debian/
http://mirror.us.leaseweb.net/debian/
http://debian.ec.as6453.net/debian/
http://mirror.us.oneandone.net/debian/
http://ftp.us.debian.org/debian/
http://mirrors.advancedhosters.com/debian/
http://mirror.cogentco.com/debian/
http://mirrors.gigenet.com/debian/
http://mirror.steadfast.net/debian/
http://ftp.utexas.edu/debian/

Of the hosts tested we choose the fastest valid for HTTP:
 http://ftp.us.debian.org/debian/

Writing sources.list.
sources.list exists, moving to sources.list.1536427463
Done.

(As expected.)

So . . .
1 - Has anyone else seen this "stall" during updating.
2 - any clue as to the cause? Maybe just a problem with whatever
site provides "bug reports" information to the aptitude updating
mechanism?







Hi, Patrick.
Thanks for the reply.

I have tried updating with:
- aptitude
- apt
- apt-get

No difference.

I checked /etc/apt/sources.list, it is unchanged and has worked ever since
I first upgraded to unstable, quite a while ago.

I even tried changing repository mirrors. Again no change.



Hi,

#--#
#   OFFICIAL DEBIAN REPOS
#--#

## Debian Main Repos
deb http://

Re: update problem

[Default User]

On Mon, Sep 10, 2018, 22:59 Jimmy Johnson  wrote:

> On 09/10/2018 05:14 PM, Default User wrote:
> > On Sun, Sep 9, 2018, 20:09 Patrick Bartek  wrote:
> >
> >> On Sun, 9 Sep 2018 10:52:39 -0400
> >> Default User  wrote:
> >>
> >>> UPDATE:
> >>>
> >>> Problem still occurring as of 2018-09-09 14.50 UT.
> >>> No indication of whether anyone else is experiencing this condition.
> >>>
> >>
> >> I don't run Sid/Unstable, but "updates" on both Wheezy which I ran
> >> for 5+ years and now Stretch on occasion stall, but very rarely like 4
> >> or 5 times a year. I've traced this particular "problem" to a repo that
> >> is not available for whatever reason. My guesses why are its files are
> >> being updated and access is locked out, the server is very busy and too
> >> overloaded to respond or is down for maintenance, its Internet access
> >> is off line, or my ISP is having problems.  I usually just CTRL-C out
> >> of it and try later which usually works.
> >>
> >> As to your "bug reports" download.  This could be the crux of your
> >> problem since that file is being updated to its most current status
> >> BEFORE it's downloaded.  My take a lot of time.
> >>
> >> And a third reason: You're using Sid.  It's called Unstable for
> >> multiple reasons.
> >>
> >> Have you tried using apt-get or apt instead of aptitude?  I haven't
> >> used aptitude since I first installed Sarge a dozen+ years ago using
> >> floppies.
> >>
> >> Also, besides checking your sources.list, check what's in
> >> sources.list.d, too.
> >>
> >> B
> >>
> >>> On Sat, Sep 8, 2018 at 3:38 PM Default User
> >>>  wrote:
> >>>
>  Hello . . .
>  Running Sid (amd-64) on standard x86-64 hardware, conventional
>  software setup, nothing unusual.
> 
>  For several days now, after I do:
> 
>  sudo aptitude -Pvv update
> 
>  If there is anything to upgrade, if I do:
> 
>  sudo aptitude -Pvv safe-upgrade
> 
>  (or)
> 
>  sudo aptitude -Pvv full-upgrade
> 
>  it will "Get: " the new and/or update package(s), then it will
>  STALL FOR UP TO 5 MINUTES at:
> 
>  Retrieving bug reports... 0%
> 
>  then followed by:
> 
>  Retrieving bug reports... Done
>  Parsing Found/Fixed information... Done
>  Reading changelogs... Done
> 
>  before finally "Unpacking, Preparing and Setting up" the packages to
>  complete the upgrade.
> 
>  [See example fragment:
> 
>  . . .
> 
>  Get: 15 http://ftp.us.debian.org/debian unstable/main amd64
>  libspice-client-glib-2.0-8 amd64 0.35-2 [528 kB]
>  Get: 16 http://ftp.us.debian.org/debian unstable/main amd64
>  libspice-client-gtk-3.0-5 amd64 0.35-2 [274 kB]
>  Get: 17 http://ftp.us.debian.org/debian unstable/main amd64 redshift
>  amd64 1.12-1 [108 kB]
>  Fetched 5,625 kB in 5s (1,134 kB/s)
>  Retrieving bug reports... Done
>  Parsing Found/Fixed information... Done
>  Reading changelogs... Done
>  (Reading database ... 208745 files and directories currently
>  installed.) Preparing to
>  unpack .../00-aptitude_0.8.11-3_amd64.deb ... Unpacking aptitude
>  (0.8.11-3) over (0.8.10-9) ... Preparing to
>  unpack .../01-aptitude-common_0.8.11-3_all.deb ... Unpacking
>  aptitude-common (0.8.11-3) over (0.8.10-9) ...
> 
>  . . . ]
> 
>  Note: sources list is okay:
> 
>  cat /etc/apt/sources.list
>  # deb cdrom:[Debian GNU/Linux 9.4.0 _Stretch_ - Official amd64
>  NETINST 20180310-11:21]/ buster contrib main non-free
> 
>  debhttp://ftp.us.debian.org/debian/unstable
>  main  contrib  non-free
>  deb-srchttp://ftp.us.debian.org/debian/unstable
>  main  contrib  non-free
> 
>  # deb  http://security.debian.org/debian-security
>  buster/updates main  contrib  non-free
>  # deb-src  http://security.debian.org/debian-security
>  buster/updates main  contrib  non-free
> 
>  # buster-updates, previously known as 'volatile'
>  # deb  http://ftp.us.debian.org/debian/
>  buster-updates main  contrib  non-free
>  # deb-src  http://ftp.us.debian.org/debian/
>  buster-updates main  contrib  non-free
> 
>  and I have run netselect-apt to find the fastest mirror:
> 
>  sudo netselect-apt -s -n sid
> 
>  (trimmed for result only:)
> 
>  The fastest 10 servers seem to be:
> 
>  http://ftp.us.debian.org/debian/
>  http://mirror.us.leaseweb.net/debian/
>  http://debian.ec.as6453.net/debian/
>  http://mirror.us.oneandone.net/debian/
>  http://ftp.us.debian.org/debian/
>  http://mirrors.advancedhosters.com/debian/
>  http://mirror.cogentco.com/debian/
>  http://mirrors.gigenet.com/debian/
>  http://mirror.steadfast.net/debian/
>  http://ftp.utexas.edu/debian/
> 
>  Of the hosts tested we choose the fastest valid for HTTP:
>   http:/

Re: update problem

[Patrick Bartek]

On Mon, 10 Sep 2018 20:14:05 -0400
Default User  wrote:

> On Sun, Sep 9, 2018, 20:09 Patrick Bartek  wrote:
> 
> > On Sun, 9 Sep 2018 10:52:39 -0400
> > Default User  wrote:
> >  
> > > UPDATE:
> > >
> > > Problem still occurring as of 2018-09-09 14.50 UT.
> > > No indication of whether anyone else is experiencing this
> > > condition. 
> >
> > I don't run Sid/Unstable, but "updates" on both Wheezy which I ran
> > for 5+ years and now Stretch on occasion stall, but very rarely
> > like 4 or 5 times a year. I've traced this particular "problem" to
> > a repo that is not available for whatever reason. My guesses why
> > are its files are being updated and access is locked out, the
> > server is very busy and too overloaded to respond or is down for
> > maintenance, its Internet access is off line, or my ISP is having
> > problems.  I usually just CTRL-C out of it and try later which
> > usually works.
> >
> > As to your "bug reports" download.  This could be the crux of your
> > problem since that file is being updated to its most current status
> > BEFORE it's downloaded.  My take a lot of time.
> >
> > And a third reason: You're using Sid.  It's called Unstable for
> > multiple reasons.
> >
> > Have you tried using apt-get or apt instead of aptitude?  I haven't
> > used aptitude since I first installed Sarge a dozen+ years ago using
> > floppies.
> >
> > Also, besides checking your sources.list, check what's in
> > sources.list.d, too.
> >
> > B
> >  
> > > On Sat, Sep 8, 2018 at 3:38 PM Default User
> > >  wrote:
> > >  
> > > > Hello . . .
> > > > Running Sid (amd-64) on standard x86-64 hardware, conventional
> > > > software setup, nothing unusual.
> > > >
> > > > For several days now, after I do:
> > > >
> > > > sudo aptitude -Pvv update
> > > >
> > > > If there is anything to upgrade, if I do:
> > > >
> > > > sudo aptitude -Pvv safe-upgrade
> > > >
> > > > (or)
> > > >
> > > > sudo aptitude -Pvv full-upgrade
> > > >
> > > > it will "Get: " the new and/or update package(s), then it will
> > > > STALL FOR UP TO 5 MINUTES at:
> > > >
> > > > Retrieving bug reports... 0%
> > > >
> > > > then followed by:
> > > >
> > > > Retrieving bug reports... Done
> > > > Parsing Found/Fixed information... Done
> > > > Reading changelogs... Done
> > > >
> > > > before finally "Unpacking, Preparing and Setting up" the
> > > > packages to complete the upgrade.
> > > >
> > > > [See example fragment:
> > > >
> > > > . . .
> > > >
> > > > Get: 15 http://ftp.us.debian.org/debian unstable/main amd64
> > > > libspice-client-glib-2.0-8 amd64 0.35-2 [528 kB]
> > > > Get: 16 http://ftp.us.debian.org/debian unstable/main amd64
> > > > libspice-client-gtk-3.0-5 amd64 0.35-2 [274 kB]
> > > > Get: 17 http://ftp.us.debian.org/debian unstable/main amd64
> > > > redshift amd64 1.12-1 [108 kB]
> > > > Fetched 5,625 kB in 5s (1,134 kB/s)
> > > > Retrieving bug reports... Done
> > > > Parsing Found/Fixed information... Done
> > > > Reading changelogs... Done
> > > > (Reading database ... 208745 files and directories currently
> > > > installed.) Preparing to
> > > > unpack .../00-aptitude_0.8.11-3_amd64.deb ... Unpacking aptitude
> > > > (0.8.11-3) over (0.8.10-9) ... Preparing to
> > > > unpack .../01-aptitude-common_0.8.11-3_all.deb ... Unpacking
> > > > aptitude-common (0.8.11-3) over (0.8.10-9) ...
> > > >
> > > > . . . ]
> > > >
> > > > Note: sources list is okay:
> > > >
> > > > cat /etc/apt/sources.list
> > > > # deb cdrom:[Debian GNU/Linux 9.4.0 _Stretch_ - Official amd64
> > > > NETINST 20180310-11:21]/ buster contrib main non-free
> > > >
> > > > debhttp://ftp.us.debian.org/debian/unstable
> > > > main  contrib  non-free
> > > > deb-srchttp://ftp.us.debian.org/debian/unstable
> > > > main  contrib  non-free
> > > >
> > > > # deb  http://security.debian.org/debian-security
> > > > buster/updates main  contrib  non-free
> > > > # deb-src  http://security.debian.org/debian-security
> > > > buster/updates main  contrib  non-free
> > > >
> > > > # buster-updates, previously known as 'volatile'
> > > > # deb  http://ftp.us.debian.org/debian/
> > > > buster-updates main  contrib  non-free
> > > > # deb-src  http://ftp.us.debian.org/debian/
> > > > buster-updates main  contrib  non-free
> > > >
> > > > and I have run netselect-apt to find the fastest mirror:
> > > >
> > > > sudo netselect-apt -s -n sid
> > > >
> > > > (trimmed for result only:)
> > > >
> > > > The fastest 10 servers seem to be:
> > > >
> > > > http://ftp.us.debian.org/debian/
> > > > http://mirror.us.leaseweb.net/debian/
> > > > http://debian.ec.as6453.net/debian/
> > > > http://mirror.us.oneandone.net/debian/
> > > > http://ftp.us.debian.org/debian/
> > > > http://mirrors.advancedhosters.com/debian/
> > > > http://mirror.cogentco.com/debian/
> > > > http://mirrors.gigenet.com/debian/
> > > > http://mirror.steadfast.net/debian/
> > > > http://ftp.utexas.edu/debian/
> > > >
> > > > Of the hosts tested we choose the fastest vali

Re: update problem

[Default User]

On Mon, Sep 10, 2018, 23:42 Patrick Bartek  wrote:

> On Mon, 10 Sep 2018 20:14:05 -0400
> Default User  wrote:
>
> > On Sun, Sep 9, 2018, 20:09 Patrick Bartek  wrote:
> >
> > > On Sun, 9 Sep 2018 10:52:39 -0400
> > > Default User  wrote:
> > >
> > > > UPDATE:
> > > >
> > > > Problem still occurring as of 2018-09-09 14.50 UT.
> > > > No indication of whether anyone else is experiencing this
> > > > condition.
> > >
> > > I don't run Sid/Unstable, but "updates" on both Wheezy which I ran
> > > for 5+ years and now Stretch on occasion stall, but very rarely
> > > like 4 or 5 times a year. I've traced this particular "problem" to
> > > a repo that is not available for whatever reason. My guesses why
> > > are its files are being updated and access is locked out, the
> > > server is very busy and too overloaded to respond or is down for
> > > maintenance, its Internet access is off line, or my ISP is having
> > > problems.  I usually just CTRL-C out of it and try later which
> > > usually works.
> > >
> > > As to your "bug reports" download.  This could be the crux of your
> > > problem since that file is being updated to its most current status
> > > BEFORE it's downloaded.  My take a lot of time.
> > >
> > > And a third reason: You're using Sid.  It's called Unstable for
> > > multiple reasons.
> > >
> > > Have you tried using apt-get or apt instead of aptitude?  I haven't
> > > used aptitude since I first installed Sarge a dozen+ years ago using
> > > floppies.
> > >
> > > Also, besides checking your sources.list, check what's in
> > > sources.list.d, too.
> > >
> > > B
> > >
> > > > On Sat, Sep 8, 2018 at 3:38 PM Default User
> > > >  wrote:
> > > >
> > > > > Hello . . .
> > > > > Running Sid (amd-64) on standard x86-64 hardware, conventional
> > > > > software setup, nothing unusual.
> > > > >
> > > > > For several days now, after I do:
> > > > >
> > > > > sudo aptitude -Pvv update
> > > > >
> > > > > If there is anything to upgrade, if I do:
> > > > >
> > > > > sudo aptitude -Pvv safe-upgrade
> > > > >
> > > > > (or)
> > > > >
> > > > > sudo aptitude -Pvv full-upgrade
> > > > >
> > > > > it will "Get: " the new and/or update package(s), then it will
> > > > > STALL FOR UP TO 5 MINUTES at:
> > > > >
> > > > > Retrieving bug reports... 0%
> > > > >
> > > > > then followed by:
> > > > >
> > > > > Retrieving bug reports... Done
> > > > > Parsing Found/Fixed information... Done
> > > > > Reading changelogs... Done
> > > > >
> > > > > before finally "Unpacking, Preparing and Setting up" the
> > > > > packages to complete the upgrade.
> > > > >
> > > > > [See example fragment:
> > > > >
> > > > > . . .
> > > > >
> > > > > Get: 15 http://ftp.us.debian.org/debian unstable/main amd64
> > > > > libspice-client-glib-2.0-8 amd64 0.35-2 [528 kB]
> > > > > Get: 16 http://ftp.us.debian.org/debian unstable/main amd64
> > > > > libspice-client-gtk-3.0-5 amd64 0.35-2 [274 kB]
> > > > > Get: 17 http://ftp.us.debian.org/debian unstable/main amd64
> > > > > redshift amd64 1.12-1 [108 kB]
> > > > > Fetched 5,625 kB in 5s (1,134 kB/s)
> > > > > Retrieving bug reports... Done
> > > > > Parsing Found/Fixed information... Done
> > > > > Reading changelogs... Done
> > > > > (Reading database ... 208745 files and directories currently
> > > > > installed.) Preparing to
> > > > > unpack .../00-aptitude_0.8.11-3_amd64.deb ... Unpacking aptitude
> > > > > (0.8.11-3) over (0.8.10-9) ... Preparing to
> > > > > unpack .../01-aptitude-common_0.8.11-3_all.deb ... Unpacking
> > > > > aptitude-common (0.8.11-3) over (0.8.10-9) ...
> > > > >
> > > > > . . . ]
> > > > >
> > > > > Note: sources list is okay:
> > > > >
> > > > > cat /etc/apt/sources.list
> > > > > # deb cdrom:[Debian GNU/Linux 9.4.0 _Stretch_ - Official amd64
> > > > > NETINST 20180310-11:21]/ buster contrib main non-free
> > > > >
> > > > > debhttp://ftp.us.debian.org/debian/unstable
> > > > > main  contrib  non-free
> > > > > deb-srchttp://ftp.us.debian.org/debian/unstable
> > > > > main  contrib  non-free
> > > > >
> > > > > # deb  http://security.debian.org/debian-security
> > > > > buster/updates main  contrib  non-free
> > > > > # deb-src  http://security.debian.org/debian-security
> > > > > buster/updates main  contrib  non-free
> > > > >
> > > > > # buster-updates, previously known as 'volatile'
> > > > > # deb  http://ftp.us.debian.org/debian/
> > > > > buster-updates main  contrib  non-free
> > > > > # deb-src  http://ftp.us.debian.org/debian/
> > > > > buster-updates main  contrib  non-free
> > > > >
> > > > > and I have run netselect-apt to find the fastest mirror:
> > > > >
> > > > > sudo netselect-apt -s -n sid
> > > > >
> > > > > (trimmed for result only:)
> > > > >
> > > > > The fastest 10 servers seem to be:
> > > > >
> > > > > http://ftp.us.debian.org/debian/
> > > > > http://mirror.us.leaseweb.net/debian/
> > > > > http://debian.ec.as6453.net/debian/
> > > > > http://mirror.us.oneandone.net/debian/
> > > > > http://ft

Re: Sound in Stretch

[deloptes]

arne wrote:

> does the command alsa-info give a clue?

what is alsa-info?

$ alsa
alsabatalsa_inalsaloop   alsamixer  alsa_out   alsatplg   alsaucm

regards

Re: Sound in Stretch

[deloptes]

Joe wrote:

> It occurs to me that there are no snd_xxx_codec modules loaded. Is that
> significant?

yes - seems like - what is your sound card - manufacturer?

Re: Sound in Stretch

[deloptes]

Joe wrote:

> On Mon, 10 Sep 2018 22:54:26 +0200

> 
> OK, aplay -l as root sees my USB device as card 1.

why as root - are you in the audio group?

$ grep audio /etc/group
audio:x:29:abcdef,pulse,timidity

> 
> I have various sound modules loaded, including snd, soundcore and
> snd_usb_audio. I assume from this that my device driver has been found.
> 
> Speaker-test is unable to find any sound cards.

what is the sound card, mainboard etc.?

For example here I have intel HD based card on the board and a web cam
attached (the usb) and HDMI display link. You can ignore the midi. So good
modules loaded look like this

$ lsmod | grep snd
snd_usb_audio 184320  2
snd_usbmidi_lib28672  1 snd_usb_audio
snd_rawmidi32768  1 snd_usbmidi_lib
snd_seq_device 16384  1 snd_rawmidi
snd_hda_codec_hdmi 57344  1
snd_hda_codec_conexant20480  1
snd_hda_codec_generic77824  1 snd_hda_codec_conexant
snd_hda_intel  32768  4
snd_hda_codec 118784  4
snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep  16384  2 snd_usb_audio,snd_hda_codec
snd_hda_core   65536  5
snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_pcm   102400  5
snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
snd_timer  32768  1 snd_pcm
snd81920  24
snd_hda_codec_generic,snd_hda_codec_conexant,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_timer,snd_pcm,snd_rawmidi
soundcore  16384  1 snd
usbcore   221184  10
xhci_hcd,ehci_pci,snd_usb_audio,usbhid,snd_usbmidi_lib,uvcvideo,ehci_hcd,btusb,xhci_pci,uhci_hcd

Re: Sound in Stretch

[deloptes]

Brian wrote:

> alsa-base

in stretch there is no alsa-base

$ dpkg -l | grep alsa
ii  alsa-utils  1.1.3-1 
   
amd64Utilities for configuring and using ALSA
ii  gstreamer1.0-alsa:amd64 1.10.4-1
   
amd64GStreamer plugin for ALSA
ii  libsox-fmt-alsa:amd64   14.4.1-5+b2 
   
amd64SoX alsa format I/O library
ii  libzita-alsa-pcmi0:amd640.2.0-4 
   
amd64C++ wrapper around the ALSA API