Re: Bug report help

2021-11-30 Thread Andrew M.A. Cater
On Mon, Nov 29, 2021 at 11:14:20PM -0500, Steven Sostrom wrote:
> I am having audio problems in Debian GNU/Linux bookworm/sid running on a
> Raspberry Pi 4.
> Kernel: Linux 5.15.0-1-arm64
> 

Hi Steven,

Any particular reason to be using Sid? 

Where did you source your download from?

It sounds like a kernel/audio subsystem interaction problem but we'd need 
more details, I think.

> I don't know that it is an issue with a package unless it is a firmware
> package.
> 
> Some of the audio devices cause applications to freeze or will play at a
> slower than normal speed. The Default (pulseaudio) device usually works.
> ALSA devices are more likely to fail.
> 
> Often, after a reboot, pulseaudio will not start. I have to keep rebooting
> until it works.
> 
> Steve



Bug report help

2021-11-29 Thread Steven Sostrom
I am having audio problems in Debian GNU/Linux bookworm/sid running on a
Raspberry Pi 4.
Kernel: Linux 5.15.0-1-arm64

I don't know that it is an issue with a package unless it is a firmware
package.

Some of the audio devices cause applications to freeze or will play at a
slower than normal speed. The Default (pulseaudio) device usually works.
ALSA devices are more likely to fail.

Often, after a reboot, pulseaudio will not start. I have to keep rebooting
until it works.

Steve


Re: bug-report help : whole user input events freeze: doubts about the right package to submit against

2019-04-22 Thread bw
In-Reply-To: <3685896c-ded1-395b-6312-cef63a9d2...@pouzenc.fr>

>Ludovic Pouzenc 

>I have doubts about the right package to submit against (gnome-shell, 
>pulseaudio, wayland, udev, kernel)

>Poor work-around :
>
>- enable accessibility feature "visual-bell". The problem vanishes,


Since the workaround is changing an a11y feature, you could try one or 
more of the suggestions here to eliminate some of your list of possible 
pkgs for the bug report?

https://wiki.debian.org/accessibility
https://wiki.archlinux.org/index.php/GNOME/Troubleshooting



bug-report help : whole user input events freeze: doubts about the right package to submit against

2019-04-21 Thread Ludovic Pouzenc

Hi,

I'm a french sysadmin in a school with ~250 computers (labs) running 
Debian 9 + Wayland.


I am testing Debian 10 and I hit an annoying problem that persists 
(present in D9+ Wayland, and D10 default config), I can't find an 
already open bug for it, I have doubts about the right package to submit 
against (gnome-shell, pulseaudio, wayland, udev, kernel) and 
https://www.debian.org/Bugs/Reporting indicate to ask here.


What : in a wayland gnome session, the keyboard and mouse event loop 
could be frozen during a little more than 1 second in all situations 
that fire a sound (if there isn't sound already in progress or very 
recently played). The mouse can't move, the keyboard can't do anything, 
not even VT-switch to console with Ctrl+Alt+F3.


Bonus : If a key press event is processed, then the freeze occur, then a 
key release is queued but delayed, and the focus what in a text field, 
then the letter corresponding to the key is repeated many times.


I didn't add fancy gnome-shell extensions. I've enabled Alternate-tab, 
nothing else different from fresh install defaults.


Reproducer 1 :

In a default Debian buster installation (testing 2019-04-21, gnome-shell 
3.30.2-7, pulseaudio 12.2-4, libwayland-client0 1.16.0-1, udev 241-3, 
linux-image-4.19.0-4-amd64 4.19.28-2) with a first system user named 
testuser with a working sound configuration :

- log in as testuser
- start gnome-terminal
- type some letters that are not a valid shell command prefix (lets says 
type "qwert"), see no lags for now
- press tab and right after try to move mouse or typing anything else, 
everything is frozen for more than 1 second



Reproducer 2 :

In a default Debian buster installation (testing 2019-04-21, gnome-shell 
3.30.2-7, pulseaudio 12.2-4, libwayland-client0 1.16.0-1, udev 241-3, 
linux-image-4.19.0-4-amd64 4.19.28-2) with a first system user named 
testuser with a working sound configuration :

- log in as testuser
- start firefox
- browse https://www.debian.org
- hit Ctrl+F to have focus in a search field, to to seek a word that in 
NOT in the page (but have some first letters that match some words in 
the page), lets say "windows" (wi matches "wiki", and I've got a nasty 
mood :)
- you will observe the lag when firefox trigger "no match" sound after 
typing n, and the search box will contain around 71 or 72 "n" : 
"winnndows"



Poor work-around :

- enable accessibility feature "visual-bell". The problem vanishes, but 
the epileptic guys will go very disapointed.


Severity :

- technically : the right is usually done after a delay (~ low)
- perception from users : make the system very annoying to use 
(important !) : my users reboot to get Windows to not have this problem :-/


On debian 9, I manage to see with strace the whole gnome-session and 
I've seen a open() on sound card device that blocks more than 400ms. On 
debian 10, I didn't manage to strace gnome-shell without entire lock-up. 
(suggestions are very welcome).


I think that system sound triggering should not freeze all input event 
processing, in any case. It seems true with gnome session over Xorg, it 
seems false to me with gnome session over Wayland.



Debian is very very great, hoping I can help a little bit to 
troubleshoot things here.


Regards,
Ludovic



Re: Bug report help: debian testing lvm boot

2013-06-12 Thread Bob Proulx
Brian wrote:
> Michael Anckaeart wrote:
> > I was going to provide all necessary info in the bug report, but here
> > goes: 

It is quite reasonable to make descriptions here and then repeat all
of the refined information again when making the bug report.

> > I downloaded the latest Debian testing image
> > (debian-testing-amd64-netinst.iso), installed in a new VirtualBox VM:
> > all options default except LVM on the entire disk (not encrypted). 
> > When rebooting after the installation I get dropped into a busybox
> > shell with the message that my vg_root partition wasn't found. 
> > 
> > So basically a vanilla installation with LVM on VirtualBox that's
> > missing the lvm2 package.

Hmm...  That definitely works in Wheezy 7.  I use it all of the time.
But it could be broken in Jessie Testing.

Could you try the exact same test that you are currently doing but
using Wheezy 7 instead of Jessie?  If it works then you have a good
solid report that something is broken between Wheezy 7 and Jessie
Testing.  If not then it would be good to look at things here a little
more first.  Because external influences such as preseed files may
affect the behavior too.

  debian-7.0.0-amd64-netinst.iso

> An lvm2 package is listed as being available in
>
> http://cdimage.debian.org/cdimage/weekly-builds/amd64/list-cd/debian-testing-amd64-netinst.list.gz
> If you report a bug then debian-installer looks like the place for it.

Agreed.  I would report it there.  Then it can get triaged as appropriate.

Bob


signature.asc
Description: Digital signature


Re: Bug report help: debian testing lvm boot

2013-06-12 Thread Brian
On Wed 12 Jun 2013 at 15:41:12 +0200, Michael Anckaeart wrote:

> I was going to provide all necessary info in the bug report, but here
> goes: 
> 
> I downloaded the latest Debian testing image
> (debian-testing-amd64-netinst.iso), installed in a new VirtualBox VM:
> all options default except LVM on the entire disk (not encrypted). 
> When rebooting after the installation I get dropped into a busybox
> shell with the message that my vg_root partition wasn't found. 
> 
> So basically a vanilla installation with LVM on VirtualBox that's
> missing the lvm2 package.

An lvm2 package is listed as being available in

   
http://cdimage.debian.org/cdimage/weekly-builds/amd64/list-cd/debian-testing-amd64-netinst.list.gz

If you report a bug then debian-installer looks like the place for it.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130612141616.GF11739@desktop



Re: Bug report help: debian testing lvm boot

2013-06-12 Thread Michael Anckaeart
On Thu, 13 Jun 2013 01:35:32 +1200
Chris Bannister  wrote:

> On Wed, Jun 12, 2013 at 02:28:08PM +0200, Michael Anckaeart wrote:
> > Hello everyone
> > 
> > I got redirected to the Debian users list from the Bug reporting
> > page. I wanted to file a bug report but can't seem to find what
> > package it belongs to and thus can't find for an existing bug or
> > create a new report. 
> > 
> > When installing Debian Testing (in a vm) using an LVM setup the lvm2
> > package is missing from the new system, resulting in a failed boot.
> > Booting into rescue mode and installing lvm2 fixes this.
> > 
> > Could someone point me to the correct package to report this bug?
> 
> You are going to have to provide a bit more info.
> What vm?
> Steps you took to install.
> 
> I think that if there was an actual bug then more people would be
> noticing this? 
> 
> IOW, how does a tester reproduce the bug, easily.
> 

I was going to provide all necessary info in the bug report, but here
goes: 

I downloaded the latest Debian testing image
(debian-testing-amd64-netinst.iso), installed in a new VirtualBox VM:
all options default except LVM on the entire disk (not encrypted). 
When rebooting after the installation I get dropped into a busybox
shell with the message that my vg_root partition wasn't found. 

So basically a vanilla installation with LVM on VirtualBox that's
missing the lvm2 package. 



signature.asc
Description: PGP signature


Re: Bug report help: debian testing lvm boot

2013-06-12 Thread Chris Bannister
On Wed, Jun 12, 2013 at 02:28:08PM +0200, Michael Anckaeart wrote:
> Hello everyone
> 
> I got redirected to the Debian users list from the Bug reporting page.
> I wanted to file a bug report but can't seem to find what package it
> belongs to and thus can't find for an existing bug or create a new
> report. 
> 
> When installing Debian Testing (in a vm) using an LVM setup the lvm2
> package is missing from the new system, resulting in a failed boot.
> Booting into rescue mode and installing lvm2 fixes this.
> 
> Could someone point me to the correct package to report this bug?

You are going to have to provide a bit more info.
What vm?
Steps you took to install.

I think that if there was an actual bug then more people would be
noticing this? 

IOW, how does a tester reproduce the bug, easily.

-- 
"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: http://lists.debian.org/20130612133532.GA24146@tal



Bug report help: debian testing lvm boot

2013-06-12 Thread Michael Anckaeart
Hello everyone

I got redirected to the Debian users list from the Bug reporting page.
I wanted to file a bug report but can't seem to find what package it
belongs to and thus can't find for an existing bug or create a new
report. 

When installing Debian Testing (in a vm) using an LVM setup the lvm2
package is missing from the new system, resulting in a failed boot.
Booting into rescue mode and installing lvm2 fixes this.

Could someone point me to the correct package to report this bug?

Kind regards
Michael


signature.asc
Description: PGP signature