Bug#970760: Problem still exists in 0.3.14
This is on the GNOME wayland session. I think I did encounter this bug in 0.3.13 as on initial login, sound was not available. Fooling around with the output sound devices in gnome-settings usually fixed the problem. In 0.3.14-1 however, the sound tab on gnome-settings is attached. >From journalctl: Nov 05 18:35:08 mobius pipewire[2021]: [W][00734.381510][module-protocol-native.c:386 client_new()] server 0x555b767b9d00: no peersec: Protocol not available Nov 05 18:34:51 mobius pipewire[2021]: [W][00717.544047][module-protocol-native.c:386 client_new()] server 0x555b767b9d00: no peersec: Protocol not available Nov 05 18:29:41 mobius pipewire[2021]: [W][00407.837975][module-protocol-native.c:386 client_new()] server 0x555b767b9d00: no peersec: Protocol not available Nov 05 18:24:43 mobius pipewire[2021]: [W][00109.463230][module-protocol-native.c:386 client_new()] server 0x555b767b9d00: no peersec: Protocol not available Nov 05 18:24:33 mobius pipewire[2021]: [W][00100.093323][module-protocol-native.c:386 client_new()] server 0x555b767b9d00: no peersec: Protocol not available Nov 05 18:24:33 mobius pipewire[2021]: [W][00099.404585][module-protocol-native.c:386 client_new()] server 0x555b767b9d00: no peersec: Protocol not available Nov 05 18:24:31 mobius pipewire[2021]: [E][00098.220657][module-adapter.c:229 create_object()] can't create node: Device or resource busy Nov 05 18:24:31 mobius pipewire[2021]: [W][00098.220654][adapter.c:175 find_format()] adapter 0x555b768a3ac0: can't get format: Device or resource busy Nov 05 18:24:31 mobius pipewire[2021]: [E][00098.220651][alsa-pcm.c:33 spa_alsa_open()] 'front:2': capture open failed: Device or resource busy Nov 05 18:24:31 mobius pipewire[2021]: [E][00098.220531][module-adapter.c:229 create_object()] can't create node: Device or resource busy Nov 05 18:24:31 mobius pipewire[2021]: [W][00098.220528][adapter.c:175 find_format()] adapter 0x555b768a05a0: can't get format: Device or resource busy Nov 05 18:24:31 mobius pipewire[2021]: [E][00098.220525][alsa-pcm.c:33 spa_alsa_open()] 'front:2': playback open failed: Device or resource busy Nov 05 18:24:31 mobius pipewire[2021]: [E][00098.220395][module-adapter.c:229 create_object()] can't create node: Device or resource busy Nov 05 18:24:31 mobius pipewire[2021]: [W][00098.220393][adapter.c:175 find_format()] adapter 0x555b7685fee0: can't get format: Device or resource busy Nov 05 18:24:31 mobius pipewire[2021]: [E][00098.220388][alsa-pcm.c:33 spa_alsa_open()] 'front:1': capture open failed: Device or resource busy Nov 05 18:24:30 mobius pipewire[2021]: [W][00097.285816][module-protocol-native.c:386 client_new()] server 0x555b767b9d00: no peersec: Protocol not available Nov 05 18:24:30 mobius pipewire[2021]: [W][00097.285782][module-protocol-native.c:386 client_new()] server 0x555b767b9d00: no peersec: Protocol not available Nov 05 18:24:25 mobius pipewire[1093]: [E][00091.409082][alsa-pcm.c:33 spa_alsa_open()] 'hdmi:0,2': playback open failed: Device or resource busy Nov 05 18:24:25 mobius pipewire[1093]: [E][00091.408989][alsa-pcm.c:33 spa_alsa_open()] 'front:2': capture open failed: Device or resource busy Nov 05 18:24:25 mobius pipewire[1093]: [E][00091.408912][alsa-pcm.c:33 spa_alsa_open()] 'front:2': playback open failed: Device or resource busy Nov 05 18:24:25 mobius pipewire[1093]: [E][00091.408822][alsa-pcm.c:33 spa_alsa_open()] 'front:1': capture open failed: Device or resource busy Nov 05 18:24:25 mobius pipewire[1093]: [W][00091.407867][module-protocol-native.c:386 client_new()] server 0x55f7440aed00: no peersec: Protocol not available Nov 05 18:24:24 mobius pipewire[1093]: [E][00091.233053][alsa-pcm.c:33 spa_alsa_open()] 'hdmi:0,2': playback open failed: Device or resource busy Nov 05 18:24:24 mobius pipewire[1093]: [E][00091.232908][alsa-pcm.c:33 spa_alsa_open()] 'front:2': capture open failed: Device or resource busy Nov 05 18:24:24 mobius pipewire[1093]: [E][00091.232768][alsa-pcm.c:33 spa_alsa_open()] 'front:2': playback open failed: Device or resource busy Nov 05 18:24:24 mobius pipewire[1093]: [E][00091.232618][alsa-pcm.c:33 spa_alsa_open()] 'front:1': capture open failed: Device or resource busy Nov 05 18:24:24 mobius pipewire[1093]: [W][00091.231562][module-protocol-native.c:386 client_new()] server 0x55f7440aed00: no peersec: Protocol not available Nov 05 18:24:24 mobius pipewire[1093]: [E][00090.369118][alsa-pcm.c:33 spa_alsa_open()] 'front:1': capture open failed: Device or resource busy Nov 05 18:24:23 mobius pipewire[1093]: [W][00089.447566][module-protocol-native.c:386 client_new()] server 0x55f7440aed00: no peersec: Protocol not available Nov 05 18:24:23 mobius pipewire[1093]: [W][00089.447530][module-protocol-native.c:386 client_new()] server 0x55f7440aed00: no peersec: Protocol not available -- System Information: Debian Release: bullseye/sid APT prefers
Bug#940929: quassel-client: support wayland
Package: quassel-client Version: 1:0.13.1-1 Severity: wishlist Dear Maintainer, QT5 does have some wayland support. Since quassel-core already brings in a bunch of dependencies, would you consider adding wayland to the mix? Currently, adding -platform wayland to the command line causes a segfault. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages quassel-client depends on: ii dbus-x11 [dbus-session-bus] 1.12.16-1 ii libc62.29-2 ii libdbusmenu-qt5-20.9.3+16.04.20160218-2 ii libgcc1 1:9.2.1-8 ii libkf5configwidgets5 5.62.0-1 ii libkf5coreaddons55.62.0-1 ii libkf5notifications5 5.62.0-1 ii libkf5notifyconfig5 5.62.0-1 ii libkf5sonnetui5 5.62.0-1 ii libkf5textwidgets5 5.62.0-1 ii libkf5widgetsaddons5 5.62.0-1 ii libkf5xmlgui55.62.0-1 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5dbus5 5.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5multimedia55.11.3-2 ii libqt5network5 5.11.3+dfsg1-4 ii libqt5webenginewidgets5 5.11.3+dfsg-2+b1 ii libqt5widgets5 5.11.3+dfsg1-4 ii libstdc++6 9.2.1-8 ii quassel-data 1:0.13.1-1 ii zlib1g 1:1.2.11.dfsg-1+b1 quassel-client recommends no packages. quassel-client suggests no packages. -- no debconf information
Bug#894172: python-virtualenv-clone: Conflicts with virtualenv-clone
Package: python-virtualenv-clone Version: 0.3.0-1.1 Severity: normal Dear Maintainer, While dist-upgrading, virtualenv-clone pulled in python-virtualenv-clone and the following happened: Preparing to unpack .../39-python-virtualenv-clone_0.3.0-1.1_all.deb ... Unpacking python-virtualenv-clone (0.3.0-1.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-YAqdAR/39-python-virtualenv-clone_0.3.0-1.1_all.deb (--unpack): trying to overwrite '/usr/bin/virtualenv-clone', which is also in package virtualenv-clone 0.2.5-1 Purging virtualenv-clone (and virtualenvwrapper which depends on it) allowed me to continue. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-virtualenv-clone depends on: ii python 2.7.14-4 python-virtualenv-clone recommends no packages. python-virtualenv-clone suggests no packages. -- no debconf information -- Alok
Bug#872794: i3blocks: [cpu_usage] Handle mpstat output change
On Sat, 26 Aug 2017 at 10:51 Jason Pleau <ja...@jpleau.ca> wrote: > Hi again. > > On 08/21/2017 06:41 AM, Alok Singh wrote: > > Package: i3blocks > > Version: 1.4-3+b1 > > Severity: normal > > > > Dear Maintainer, > > > > Not sure when this happened but the regexp in cpu_usage cannot parse the > > output of mpstat anymore. Patch attached. > > > > I investigated, and this is strange, I cannot reproduce your exact issue. > My issue was exactly what is described in https://github.com/vivien/i3blocks/pull/252 After looking at mpstat, I figured the "Average" line was the one I'd like to be shown in the widget while the regexp as written would pick the first CPU. This is something that the github issue above is silent on. http://sources.debian.net/src/i3blocks/1.4-3/scripts/cpu_usage/#L34 Yes, this is indeed the version I had before I created the patch. I have inverted the original file and my patched file. So applying the patch would not change the file. I have attached the fixed patch below. My apologies for the mistake. > I will however add a patch that was recently added as a PR upstream (the > script does not work with newer kernel/mpstat): > https://github.com/vivien/i3blocks/pull/252 Thank you, that should fix the problem. There is a difference between what I have done and what upstream has done and I leave it to your judgement if you'd like to change the regexp to use the "Average" line. Ideally, upstream should accept this patch. Thanks muchly for maintaining this package which I am sure has a loyal if small following :) -- Alok cpu_usage.patch Description: Binary data
Bug#872794: i3blocks: [cpu_usage] Handle mpstat output change
Package: i3blocks
Version: 1.4-3+b1
Severity: normal
Dear Maintainer,
Not sure when this happened but the regexp in cpu_usage cannot parse the
output of mpstat anymore. Patch attached.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_IN:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages i3blocks depends on:
ii libc6 2.24-15
ii perl 5.26.0-5
Versions of packages i3blocks recommends:
ii acpi1.7-1+b1
pn alsa-utils
pn gawk
ii i3-wm 4.13-1
ii sysstat 11.5.7-1
i3blocks suggests no packages.
-- no debconf information
--
Alok
--- cpu_usage 2017-08-21 17:36:30.375729312 +0700
+++ cpu_usage.orig 2017-08-21 15:27:23.603195839 +0700
@@ -31,7 +31,7 @@
$ENV{LC_ALL}="en_US"; # if mpstat is not run under en_US locale, things may break, so make sure it is
open (MPSTAT, 'mpstat 1 1 |') or die;
while () {
-if (/^Average.*\s+(\d+\.\d+)/) {
+if (/^.*\s+(\d+\.\d+)\s+$/) {
$cpu_usage = 100 - $1; # 100% - %idle
last;
}
Bug#852398: To load extensions
Copying this over from #851692. A method of enabling extensions without re-compiling Chromium. Not saying it is ideal 1. Find your extensions: They are in $XDG_CONFIG_DIR/chromium//Extensions// For example, uBlock is at /home/alok/.config/chromium/Default/Extensions/cjpalhdlnbpafiamejdnhcphjbkeiagm/1.9.4_0 2. Create a file in /etc/chromium.d/enable-extensions with the content export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --load-extension=" 3. You have to create multiple lines of the form above for each profile. Note that you will have to update this file when the extension version changes. If you have the same extension in multiple profiles, you will have make explicit entries for it as per step 2. -- — Alok
Bug#851692: To load your extensions
Here's what you need to do to enable the extensions that you installed via the Web Store and are in your profile. 1. Find your extensions: They are in $XDG_CONFIG_DIR/chromium//Extensions// For example, uBlock is at /home/alok/.config/chromium/Default/Extensions/cjpalhdlnbpafiamejdnhcphjbkeiagm/1.9.4_0 2. Create a file in /etc/chromium.d/enable-extensions with the content export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --load-extension " 3. You have to create multiple lines of the form for each profile. Note that you will have to update this file when the extension version changes. If you have the same extension in multiple profiles, you will have make explicit entries for it as per step 2. HTH until the CHROMIUM_FLAGS patch above is accepted. -- — Alok
