Bug#927173: Adding details

2019-04-18 Thread JB
Thanks for your input, and sorry for reporting a bug on the wrong package. How should I report this bug then? I am not sure what to say to demonstrate it is a kernel issue. ‐‐‐ Original Message ‐‐‐ On Friday, April 19, 2019 2:17 AM, Felipe Sateler wrote: > On Thu, Apr 18, 2019 at 8:05

Bug#927173: Adding details

2019-04-18 Thread Felipe Sateler
On Thu, Apr 18, 2019 at 8:05 PM JB wrote: > My bad, I thought it was the case but I mixed up the numbers. > > Please find enclosed the details you've asked for. > This confirms that ID_MODEL_ID changes and that ID_VENDOR changes although ID_VENDOR_ID does not. I think this is a kernel bug. --

Bug#927173: Adding details

2019-04-18 Thread JB
My bad, I thought it was the case but I mixed up the numbers. Please find enclosed the details you've asked for. ‐‐‐ Original Message ‐‐‐ On Friday, April 19, 2019 1:47 AM, Felipe Sateler wrote: > On Thu, Apr 18, 2019 at 5:32 PM Michael Biebl wrote: > >> Am 18.04.19 um 19:35 schrieb JB

Bug#927173: Adding details

2019-04-18 Thread Felipe Sateler
On Thu, Apr 18, 2019 at 5:32 PM Michael Biebl wrote: > Am 18.04.19 um 19:35 schrieb JB: > > If it can help, it happened to other people, e.g. here with Arch : > https://bbs.archlinux.org/viewtopic.php?id=222301 > > > > Felipe, with your PA hat on, can you take a look at this? > PA simply reads i

Bug#927173: Adding details

2019-04-18 Thread JB
If that helps, please find enclosed the output of `pacmd list-sinks` when in bad state and in good state. Best regards, JB ‐‐‐ Original Message ‐‐‐ On Thursday, April 18, 2019 11:32 PM, Michael Biebl wrote: > Am 18.04.19 um 19:35 schrieb JB: > > > If it can help, it happened to other

Bug#927173: Adding details

2019-04-18 Thread Michael Biebl
Am 18.04.19 um 19:35 schrieb JB: > If it can help, it happened to other people, e.g. here with Arch : > https://bbs.archlinux.org/viewtopic.php?id=222301 > Felipe, with your PA hat on, can you take a look at this? To me this looks like a kernel/driver issue, but would welcome your input on this

Processed: [bts-link] source package systemd

2019-04-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

[bts-link] source package systemd

2019-04-18 Thread debian-bts-link
# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #927008 (http://bugs.debian.org/927008)

Bug#927173: Adding details

2019-04-18 Thread JB
If it can help, it happened to other people, e.g. here with Arch : https://bbs.archlinux.org/viewtopic.php?id=222301 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman

Bug#927173: udev: wrong device name when booting

2019-04-18 Thread JB
Long story short, my USB DAC was listed at index 0 within the list of pulseaudio sinks. -> when in good state: $ pacmd list-sinks 2 sink(s) available. index: 0 name: So, I usually set it as the default output sink: $ pacmd set-default-sink 0 I thought it might worked as work

Bug#927173: udev: wrong device name when booting

2019-04-18 Thread Michael Biebl
Am 18.04.19 um 17:03 schrieb JB: > I managed to track this bug down to udev, How? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature __

Bug#927173: udev: wrong device name when booting

2019-04-18 Thread JB
I managed to track this bug down to udev, but I am no expert when it comes to it, so I might be wrong. I also thought it could be the kernel when I saw the dmesg output but first I had to be sure it was not a udev issue. At this point, I suspect it might even be a hardware issue (device which co

Bug#926603: marked as done (Debian fails to start after installation into Virtualbox)

2019-04-18 Thread Debian Bug Tracking System
Your message dated Thu, 18 Apr 2019 16:23:56 +0200 with message-id and subject line Re: Bug#926603: Debian fails to start after installation into Virtualbox has caused the Debian Bug report #926603, regarding Debian fails to start after installation into Virtualbox to be marked as done. This mea

Bug#926603: Debian fails to start after installation into Virtualbox

2019-04-18 Thread Andy Ruddock
Michael Biebl wrote: > On Mon, 8 Apr 2019 01:10:28 +0200 Michael Biebl wrote: >> Control: tags -1 moreinfo >> >> Am 07.04.19 um 18:51 schrieb Andy Ruddock: >>> Package: systemd >>> Severity: critical >>> >>> I'm running Windows 10 (Home edition - up to date) on the desktop, with >>> Virtualbox (

Bug#927173: udev: wrong device name when booting

2019-04-18 Thread Michael Biebl
Am 18.04.19 um 01:43 schrieb Jul': > Sorry for the lack of details. > > 1) how udev assigns this name? > > Since I have no custom udev rule, AFAIK, udev assigns it with the standards > rules (in "/lib/udev/rules.d/60-persistent-alsa.rules" since it is a sound > device). > This rules file just