Bug#852398: Issue still present in 57.0.2987.98-1
Just upgraded to 57.0.2987.98-1 on stretch, the bug is still present. Can confirm that CHROMIUM_FLAGS='--enable-remote-extensions' workaround is effective.
Bug#827636: libasound2: ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse
Dear Elimar, Thank you for clarifying. The command without '-d pulse' indeed works as expected. apt-listchanges didn't mention anything so I wasn't expecting any change to the config. Best wishes, Lev On Sun, 19 Jun 2016 at 12:59 Elimar Riesebieter wrote: > Control: reassign -1 libasound2-plugins > Control: severity -1 minor > > * Lev Livnev [2016-06-18 23:45 +0100]: > > > Package: libasound2 > > Version: 1.1.1-1 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > > > After the update to libasound2 version 1.1.1-1 from 1.1.0-1, it is no > longer > > possible to control audio, the below command, which should adjust the > audio > > levels, fails with the following error: > > > > ~/ amixer -D pulse sset Master 5%+ > > ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse > > amixer: Mixer attach pulse error: No such file or directory > > Since libasound2-plugins 1.1.1 we don't install 50-pulseaudio.conf > anymore. So the device pulse isn't available anymore by Debian's > default config. See also > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739329. > > $ amixer sset Master 5%+ > should adjust the default advice as wanted. > > Elimar > -- > On the keyboard of life you have always > to keep a finger at the escape key;-) >
Bug#827636: libasound2: ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse
Elimar, My sound works, the problem I'm having is that after the latest upgrade (from 1.1.0-1 to 1.1.1-1), I can't control the volume from the command line using $ amixer -D pulse sset Master 5%+, getting the error that was the subject of the original bug report. It is still possible to control the levels from # alsamixer. Before the upgrade the above command ran fine (and was used by Xbindkeys to control levels using keyboard keys), but it seems like a change in one of the ALSA libraries broke it. On Sun, 19 Jun 2016 at 11:08 Elimar Riesebieter wrote: > * Lev Livnev [2016-06-19 09:36 +]: > > > Elimar, thank you for your help: > > > > I am unable to adjust the sound, so I felt like the package is unusable > in > > my configuration. Here are the outputs: > > > > $ dpkg -l | egrep '(alsa|libasound)' > > [...] > Output looks fine. > > > $ aplay -l > > List of PLAYBACK Hardware Devices > > card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] > > Subdevices: 1/1 > > Subdevice #0: subdevice #0 > > card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] > > Subdevices: 1/1 > > Subdevice #0: subdevice #0 > > card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] > > Subdevices: 1/1 > > Subdevice #0: subdevice #0 > > card 1: PCH [HDA Intel PCH], device 0: ALC3263 Analog [ALC3263 Analog] > > Subdevices: 1/1 > > Subdevice #0: subdevice #0 > > So your default card is HDMI device 3 or do you want to run the > analog output (card 1)? > > > # alsactl init > > [sudo] password for lev: > > alsactl: sysfs_init:48: sysfs path '/sys' is invalid > > > > Found hardware: "HDA-Intel" "Intel Broadwell HDMI" > > "HDA:80862808,80860101,0010" "0x1028" "0x0665" > > Hardware is initialized using a generic method > > Your soundcard is recognized and should work if configured > correctly. > > Elimar > -- > 355/113: Not the famous irrational number pi, >but an incredible simulation! > -unknown >
Bug#827636: [Pkg-alsa-devel] Bug#827636: libasound2: ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse
Elimar, thank you for your help: I am unable to adjust the sound, so I felt like the package is unusable in my configuration. Here are the outputs: $ dpkg -l | egrep '(alsa|libasound)' ii alsa-base 1.0.27+1 all dummy package to ease purging of obsolete conffiles ii alsa-utils1.1.1-1 amd64Utilities for configuring and using ALSA ii gstreamer1.0-alsa:amd64 1.8.2-1 amd64GStreamer plugin for ALSA ii libasound2:amd64 1.1.1-1 amd64shared library for ALSA applications ii libasound2:i386 1.1.1-1 i386 shared library for ALSA applications ii libasound2-data 1.1.1-1 all Configuration files and profiles for ALSA drivers ii libasound2-plugins:amd64 1.1.1-1 amd64ALSA library additional plugins ii libasound2-plugins:i386 1.1.1-1 i386 ALSA library additional plugins $ aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: ALC3263 Analog [ALC3263 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 # alsactl init [sudo] password for lev: alsactl: sysfs_init:48: sysfs path '/sys' is invalid Found hardware: "HDA-Intel" "Intel Broadwell HDMI" "HDA:80862808,80860101,0010" "0x1028" "0x0665" Hardware is initialized using a generic method # sudo alsactl restore (last command gives no output) Lev On Sun, 19 Jun 2016 at 09:54 Elimar Riesebieter wrote: > * Lev Livnev [2016-06-18 23:45 +0100]: > > > Package: libasound2 > > Version: 1.1.1-1 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > > > > > After the update to libasound2 version 1.1.1-1 from 1.1.0-1, it is no > longer > > possible to control audio, the below command, which should adjust the > audio > > levels, fails with the following error: > > > > ~/ amixer -D pulse sset Master 5%+ > > ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse > > amixer: Mixer attach pulse error: No such file or directory > > > > I can't be sure if this is related to the package libasound2, > > libasound2-plugins, or alsa-utils, or even something else, so please > reclassify > > if necessary. > > But you're sure to set severity to grave? > > Is sound working? Anyway, what tells: > > $ dpkg -l | egrep '(alsa|libasound)' > > $ aplay -l > > # alsactl init > > # alsactl restore > > Elimar > -- > You cannot propel yourself forward by > patting yourself on the back. >
Bug#827636: libasound2: ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse
Package: libasound2 Version: 1.1.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, After the update to libasound2 version 1.1.1-1 from 1.1.0-1, it is no longer possible to control audio, the below command, which should adjust the audio levels, fails with the following error: ~/ amixer -D pulse sset Master 5%+ ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL pulse amixer: Mixer attach pulse error: No such file or directory I can't be sure if this is related to the package libasound2, libasound2-plugins, or alsa-utils, or even something else, so please reclassify if necessary. Please instruct me on what else to try to get to the bottom of this. Thank you, -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#802890: backintime-qt4: can't launch with gksu/gksudo, blank grey window appears
Package: backintime-qt4 Version: 1.1.6-1 Severity: grave Justification: renders package unusable Dear Maintainer, Trying to start the QT interface for backintime-qt4 using: $ gksu backintime-qt4 results in a blank grey window appearing, along with the output: Back In Time Version: 1.1.6 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime-qt4 --license' for details. X Error: BadAccess (attempt to access private resource denied) 10 Extension:130 (MIT-SHM) Minor opcode: 1 (X_ShmAttach) Resource id: 0x18b X Error: BadShmSeg (invalid shared segment parameter) 128 Extension:130 (MIT-SHM) Minor opcode: 5 (X_ShmCreatePixmap) Resource id: 0xf4 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x3800013 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x3800013 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x3800013 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x3800013 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x3800013 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea) Resource id: 0x3800013 (using gksudo leads to the same behaviour but without the above Error messages in the output.) This appears to be a common problem for some qt4 programs, and is fixed by running instead: $ gksu QT_X11_NO_MITSHM=1 backintime-qt4 in which case the program runs as normal. This problem has only recently started to affect my system, no idea why. Googling QT_X11_NO_MITSHM=1 shows that this affects a lot of QT apps that need gksu/gksudo. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages backintime-qt4 depends on: ii backintime-common 1.1.6-1 ii libnotify-bin 0.7.6-2 ii policykit-1 0.105-12 ii python3-dbus.mainloop.qt 4.11.4+dfsg-1+b2 ii python3-pyqt4 4.11.4+dfsg-1+b2 pn python3:any ii x11-utils 7.7+3 Versions of packages backintime-qt4 recommends: ii python3-secretstorage 2.1.2-3 Versions of packages backintime-qt4 suggests: pn meld | kompare -- no debconf information
