[Desktop-packages] [Bug 1884410] [NEW] I was watching a live video on YouTube..Soon after the programme is over, I'm seeing volume icon popping up on the screen
Public bug reported: I'm using Ubuntu 19.10 installed yesterday... ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884410 Title: I was watching a live video on YouTube..Soon after the programme is over, I'm seeing volume icon popping up on the screen Status in pulseaudio package in Ubuntu: New Bug description: I'm using Ubuntu 19.10 installed yesterday... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 597056] Re: HP Touchsmart 600-1005xt No sound from Internal Speakers
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/597056 Title: HP Touchsmart 600-1005xt No sound from Internal Speakers Status in alsa-driver package in Ubuntu: Expired Bug description: Found there is no internal speaker output from hp touchsmart 600-1005xt in all releases of Ubuntu 8.04 to 10.04LTS (64bit) with updated alsa-base (on 1.0.22.1 in Lucid now). All outputs & inputs work except the Internal speakers. I Checked all alsamixer levels, I have also noticed the nodeid's it seem to be mapped 0x15 - 0x0d - 0x03 (21 - 13 - 3) for internal speakers which gives same results (no audio) in osx Applehda.kext. The Headphone nodeid's of 0x14 - 0x0c - 0x02 (20 - 12 - 2) seem to work in all Ubuntu Dists & OSx as well. Windows 7 Driver everything works of course. Is Bios sending wrong pin configs for internal audio? if so what would the resolution be? here is my alsa-information from alsa-info.sh attached, My only guess is the pin configs how do you change them in alsa driver & how could I get the correct ones if the bios was sending wrong pathmaps? I should also note I've tried most of the model flags in alsa-base.conf in the alc888 documentation & rebooted countless times, model=auto shows the internal speaker but sound comes out headphones plug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/597056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778317] Re: Owncloud always ask for password at startup
[Expired for gnome-shell-extension-appindicator (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1778317 Title: Owncloud always ask for password at startup Status in gnome-shell-extension-appindicator package in Ubuntu: Expired Bug description: At startup, ownCloud client always ask for password with the following message: Please enter ownCloud password: User: Account: x...@xxx.xx Click here to request an app password from the web interface. Reading from keychain failed with error: 'No keychain service available' I think ownCloud can't get password from gnome-keyring or something like this... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1778317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780709] Re: Boot duration is very long
[Expired for gnome-shell-extension-appindicator (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1780709 Title: Boot duration is very long Status in gnome-shell-extension-appindicator package in Ubuntu: Expired Bug description: When my laptop starts, it took a very long time. I CTRL-F2, and I discovered the following message: "a start job is running for snappy daemon" Boot sequence seems to be stuck up a long time with this deamon. I'm using Ubuntu 18.04 LTS always up to date. My laptop is a HP Elitebook 8470p To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1780709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870278] Re: Shell is unresponsive at the lock screen for ~10s after unlocking
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870278 Title: Shell is unresponsive at the lock screen for ~10s after unlocking Status in gnome-shell package in Ubuntu: Expired Bug description: When unlocking the session GNOME Shell now appears to be entirely unresponsive (still showing the lock screen) for ~10s after entering a correct password. This occurs on both an X11 and a Wayland session; on the Wayland session the mouse cursor is frozen, while on X11 it is responsive (and still changes the cursor image appropriately when moving over windows) This only started recently (maybe a couple of days ago?); it's now 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 16:49:34 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871011] Re: USB scanning broken on focal --> hpmud and ippusbxd conflict
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1871011 Title: USB scanning broken on focal --> hpmud and ippusbxd conflict Status in HPLIP: Invalid Status in hplip package in Ubuntu: Expired Bug description: On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Printer/scanner is an Officejet 4635. Scanning previously worked just fine a few months ago. Regression? To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874003] Re: cant log into network
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1874003 Title: cant log into network Status in network-manager package in Ubuntu: Expired Bug description: Running Ubuntu Mate 20.04 2020-04-20 ISO live session, sometimes i'm not able to log into detected wireless networks. See screenshot for error message. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: MATE Date: Tue Apr 21 05:29:48 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200420) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 c072d14c-3f17-3a1d-9679-9929ecc4d6cb ethernet 0 never yes -999 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- ---- enp4s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872917] Re: Laptop does not recognize it's charging
[Expired for upower (Ubuntu) because there has been no activity for 60 days.] ** Changed in: upower (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1872917 Title: Laptop does not recognize it's charging Status in upower package in Ubuntu: Expired Bug description: I'm using a pretty new Lenovo Thinkpad X1 Extreme G2. Since a few days, the laptop does not recognize that its charging all the time. It's showing the battery icon and a percent number. This must be broken a couple of days or weeks ago, this was working when I installed Ubuntu 19.10. It does not depend from dock or directly connecting the AC adapter. Incredibly long battery life time is shown, see screenshot. (laptop was connected to AC during this) This is a problem because for example firmware upgrades does not work because they require "AC-connected state". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1872917/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
[Expired for gtk+2.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+2.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: Expired Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
Maybe different machines have different root cause for this issue, for
my case:
I have 3 laptops: 1 dell laptop with intel BT 8087:0aaa, 1 dell laptop
with Atheros BT 0cf3:e007 and 1 lenovo laptop with intel BT 8087:0029. I
have 4 BT headsets: 1 QC35 II, 1 harman kardon soho wireless, 1 sony wl-
1000x and 1 plantronics Go2.
After freshly installing the ubuntu 20.04, those 4 headsets work well on
both Dell laptops, in the hsp/hfp mode, both playback and recording work
well.
But on the Lenovo machine, I reproduced the issue, all headsets could
work in A2DP mode, couldn't output and record in hsp/hfp mode.
I ran $sudo btmon, found after switch to Synchronous connection
successfully (HCI Event: Synchronous Connect Complete), the dell
machines could receive the sco packets from headsets, while the lenovo
machine couldn't. The difference between Lenovo and Dell machines is
they have different BT host controllers. Then I debugged the bt kernel
driver, found on that lenovo machine, the btusb driver could not receive
the usb_isoc packets from headsets (length always equals 0).
So on my LENOVO laptop, it is highly possible this is a kernel driver or
BT firmware/WiFi firmware's bug.
So if possible, you could plug in an external USB BT dongle to redo the
test, let headsets connect to that dongle instead of BT hci on your
laptop. Or you could run sudo btmon to check the log, if it is a
synchronous connection failure or TX/RX on SCO packets failure.
This is a example log captured on my Dell machine (without hsp/hfp
issue), starting capture when manually switch to hsp/hfp mode:
Bluetooth monitor ver 5.48
= Note: Linux version 5.3.0-56-generic (x86_64)
0.694655
= Note: Bluetooth subsystem version 2.22
0.694662
= New Index: 18:1D:EA:86:BE:E6 (Primary,USB,hci0)
[hci0] 0.694666
= Open Index: 18:1D:EA:86:BE:E6
[hci0] 0.694667
= Index Info: 18:1D:EA:86:BE:E6 (Intel Corp.)
[hci0] 0.694668
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0002} 0.694673
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.694674
@ MGMT Open: btmon (privileged) version 1.14
{0x0003} 0.694731
< HCI Command: Exit Sniff Mode (0x02|0x0004) plen 2
#1 [hci0] 6.574419
Handle: 256
> HCI Event: Command Status (0x0f) plen 4
>
>#2 [hci0] 6.688939
Exit Sniff Mode (0x02|0x0004) ncmd 1
Status: Success (0x00)
> HCI Event: Mode Change (0x14) plen 6
>
>#3 [hci0] 6.829008
Status: Success (0x00)
Handle: 256
Mode: Active (0x00)
Interval: 0.000 msec (0x)
< HCI Command: Setup Synchronous Connection (0x01|0x0028) plen 17
#4 [hci0] 6.829108
Handle: 256
Transmit bandwidth: 8000
Receive bandwidth: 8000
Max latency: 10
Setting: 0x0060
Input Coding: Linear
Input Data Format: 2's complement
Input Sample Size: 16-bit
# of bits padding at MSB: 0
Air Coding Format: CVSD
Retransmission effort: Optimize for power consumption (0x01)
Packet type: 0x0380
3-EV3 may not be used
2-EV5 may not be used
3-EV5 may not be used
> HCI Event: Command Status (0x0f) plen 4
>
[Desktop-packages] [Bug 1884405] Re: package mutter 3.34.3-1ubuntu1~19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1884405 Title: package mutter 3.34.3-1ubuntu1~19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mutter package in Ubuntu: New Bug description: installation/ unninstalation ProblemType: Package DistroRelease: Ubuntu 19.10 Package: mutter 3.34.3-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-59.53-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 AptOrdering: gnome-shell:amd64: Install gnome-shell-common:amd64: Install rygel:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 21 05:29:20 2020 DpkgHistoryLog: Start-Date: 2020-06-21 05:29:16 Requested-By: fredrik (1000) Upgrade: gnome-shell-common:amd64 (3.34.1-1ubuntu1, 3.34.3-1ubuntu1~19.10.1), rygel:amd64 (0.38.1-2ubuntu3, 0.38.1-2ubuntu3.3), gnome-shell:amd64 (3.34.1-1ubuntu1, 3.34.3-1ubuntu1~19.10.1) DuplicateSignature: package:mutter:3.34.3-1ubuntu1~19.10.1 Setting up rygel (0.38.1-2ubuntu3.3) ... Disable user unit that shouldn't have been auto enabled dpkg: error processing package mutter (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-06-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: mutter Title: package mutter 3.34.3-1ubuntu1~19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884405] [NEW] package mutter 3.34.3-1ubuntu1~19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: installation/ unninstalation ProblemType: Package DistroRelease: Ubuntu 19.10 Package: mutter 3.34.3-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-59.53-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 AptOrdering: gnome-shell:amd64: Install gnome-shell-common:amd64: Install rygel:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 21 05:29:20 2020 DpkgHistoryLog: Start-Date: 2020-06-21 05:29:16 Requested-By: fredrik (1000) Upgrade: gnome-shell-common:amd64 (3.34.1-1ubuntu1, 3.34.3-1ubuntu1~19.10.1), rygel:amd64 (0.38.1-2ubuntu3, 0.38.1-2ubuntu3.3), gnome-shell:amd64 (3.34.1-1ubuntu1, 3.34.3-1ubuntu1~19.10.1) DuplicateSignature: package:mutter:3.34.3-1ubuntu1~19.10.1 Setting up rygel (0.38.1-2ubuntu3.3) ... Disable user unit that shouldn't have been auto enabled dpkg: error processing package mutter (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-06-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: mutter Title: package mutter 3.34.3-1ubuntu1~19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1884405 Title: package mutter 3.34.3-1ubuntu1~19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mutter package in Ubuntu: New Bug description: installation/ unninstalation ProblemType: Package DistroRelease: Ubuntu 19.10 Package: mutter 3.34.3-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-59.53-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 AptOrdering: gnome-shell:amd64: Install gnome-shell-common:amd64: Install rygel:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 21 05:29:20 2020 DpkgHistoryLog: Start-Date: 2020-06-21 05:29:16 Requested-By: fredrik (1000) Upgrade: gnome-shell-common:amd64 (3.34.1-1ubuntu1, 3.34.3-1ubuntu1~19.10.1), rygel:amd64 (0.38.1-2ubuntu3, 0.38.1-2ubuntu3.3), gnome-shell:amd64 (3.34.1-1ubuntu1, 3.34.3-1ubuntu1~19.10.1) DuplicateSignature: package:mutter:3.34.3-1ubuntu1~19.10.1 Setting up rygel (0.38.1-2ubuntu3.3) ... Disable user unit that shouldn't have been auto enabled dpkg: error processing package mutter (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-06-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: mutter Title: package mutter 3.34.3-1ubuntu1~19.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884404] [NEW] package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kerne
Public bug reported: startx don't came up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 20 23:36:09 2020 ErrorMessage: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-06-21 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1884404 Title: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: startx don't came up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 20 23:36:09 2020 ErrorMessage: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-06-21 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1884404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Same as jacj and Edwin. With 440.64 Nvidia driver with Ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884101] Re: jackdbus produces high cpu load
Did that already, got rid of the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1884101 Title: jackdbus produces high cpu load Status in jackd2 package in Ubuntu: Incomplete Bug description: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1884101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
Try the following in Ubuntu LTS 20.04, to clear things out. 1. Create a new gnome user and log in. 2. Build Rhythmbox 3.4.3 from source. This should take 15 mins + 200 MB disk space $ sudo apt-get build-dep rhythmbox $ sudo apt-get install git $ git clone https://gitlab.gnome.org/GNOME/rhythmbox.git $ cd rhythmbox/ $ git checkout tags/v3.4.3 -b v3.4.3 $ ./autogen.sh $ make $ shell/rhythmbox --version $ shell/rhythmbox Note: Here were just building and starting Rhythmbox from source tree. It runs 100% from the tree. We don't do any installation. So, this will not interfere with existing Rhythmbox installed by the system. Just always do this experiment as a new user, so config / data of both git and system Rhythmbox versions remain separate in separate user home dirs. 3. Check if the random sink issue shows up ( It SHOULD in my opinion ) 4. Do step [1] / [2] in Ubuntu 19.10 replacing "3.4.3" with "3.4.4". 5. Check if the random sink issue shows up ( It SHOULD NOT in my opinion ). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Correction: Applying following patch does not solve this assertion
failure:
diff --git a/src/engine-eds.cpp b/src/engine-eds.cpp
index 153a9ea..8e2674f 100644
--- a/src/engine-eds.cpp
+++ b/src/engine-eds.cpp
@@ -879,6 +879,11 @@ private:
if (tzid == nullptr)
return nullptr;
+// Workaround: Etc/Utc is not known to
i_cal_timezone_get_builtin_timezone_from_tzid/i_cal_timezone_get_builtin_timezone
+if (strcmp("Etc/Utc", tzid) == 0) {
+return g_time_zone_new("Z");
+}
+
auto itz = i_cal_timezone_get_builtin_timezone_from_tzid(tzid); //
usually works
if (itz == nullptr) // fallback
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libical3 in Ubuntu.
https://bugs.launchpad.net/bugs/1848969
Title:
src/date-time.cpp:171:GDateTime*
unity::indicator::datetime::DateTime::get() const: assertion failed:
(m_dt)
Status in indicator-datetime package in Ubuntu:
Confirmed
Status in libical3 package in Ubuntu:
New
Bug description:
After upgrading to Ubuntu 19.10, indicator-datetime
15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:
$ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized
TZID: 'Etc/Utc'
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized
TZID: 'Etc/Utc'
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized
TZID: 'Etc/Utc'
(process:17641): libecal-CRITICAL **: 01:46:35.457:
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libecal-CRITICAL **: 01:46:35.457:
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
[...]
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libecal-CRITICAL **: 01:46:35.458:
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libecal-CRITICAL **: 01:46:35.458:
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
**
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Bail out!
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
The underlying issue is that i_cal_timezone_get_builtin_timezone_from_tzid and i_cal_timezone_get_builtin_timezone included from /usr/include/libical- glib/i-cal-timezone.h (libical-dev) fail to determine the timezone for "Etc/Utc" or "Etc/UTC". ** Also affects: libical3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libical3 in Ubuntu. https://bugs.launchpad.net/bugs/1848969 Title: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Status in indicator-datetime package in Ubuntu: Confirmed Status in libical3 package in Ubuntu: New Bug description: After upgrading to Ubuntu 19.10, indicator-datetime 15.10+19.10.20190819.1-0ubuntu1 crashes right from the start: $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized TZID: 'Etc/Utc' (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed [...] (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed ** Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Bail out! Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Finally, i have the same problem on Vivobook S15 and Headset QC35 II that worked perfectly before upgrade to 20.04. It's very annoying issue in this period of containment and remote calls. Don't push me to switch on Windows -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Finally , i h -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884396] [NEW] Ubuntu freezing intermittently
Public bug reported: I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] InstallationDate: Installed on 2020-05-12 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M13 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M13 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M13 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884396 Title: Ubuntu freezing intermittently Status in xorg package in Ubuntu: New Bug description: I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh in
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I had the same issue with my BOSE QC35 II on Ubuntu 20.04 recently updated from 19 . My config: Asus VivoBook S15 . To correct this issue i only had to enable this line in /etc/pulse/daemon.conf flat-volumes = no then restart pulseaudio as user : systemctl --user restart pulseaudio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884395] [NEW] GIMP crashes X-Server when mouse is first used after program launch
Public bug reported: As of 5 days ago (6/15/20) and after several recent Mint 19.3 software updates, GIMP 2.10.20 started crashing. I can open GIMP OK and even open an image file. But as soon as I use the mouse, even to click on the opened image, or click a menu item, GIMP crashes and I end up at the login screen. I’ve also tried earlier versions of GIMP, namely 2.10.18 and 2.10.14 but same problem. I found the cause to be my Logitech MX Master wireless mouse unifying USB wireless receiver. GIMP works OK when using the laptop track pad. Log excerpt: lightdm PAM adding faulty module: pam_kwallet5.so PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory systemd-coredum Process 1451 (Xorg) of user 0 dumped core. Stack trace of thread 1554: #0 0x559b66bcdde5 n/a (Xorg) #1 0x559b66bce572 n/a (Xorg) #2 0x559b66c9424b n/a (Xorg) #3 0x559b66c95019 miPointerSetPosition (Xorg) #4 0x559b66b64c6e n/a (Xorg) #5 0x559b66b65410 n/a (Xorg) #6 0x559b66b66b74 GetPointerEvents (Xorg) #7 0x559b66b67150 QueuePointerEvents (Xorg) #8 0x7f62bf07bfb5 n/a (libinput_drv.so) #9 0x7f62bf07cb40 n/a (libinput_drv.so) #10 0x559b66ca9e83 n/a (Xorg) #11 0x559b66cac561 n/a (Xorg) #12 0x559b66ca9cce n/a (Xorg) #13 0x7f62c2e9c6db start_thread (libpthread.so.0) #14 0x7f62c2bc588f __clone (libc.so.6) Stack trace of thread 1451: #0 0x7f62c2bc5bb7 epoll_wait (libc.so.6) #1 0x559b66cac517 n/a (Xorg) #2 0x559b66ca5533 WaitForSomething (Xorg) #3 0x559b66b4e463 n/a (Xorg) #4 0x559b66b526a8 n/a (Xorg) #5 0x7f62c2ac5b97 __libc_start_main (libc.so.6) #6 0x559b66b3c32a _start (Xorg) Stack trace of thread 1547: #0 0x7f62c2ea29f3 futex_wait_cancelable (libpthread.so.0) #1 0x7f62ba1f2ecb n/a (i965_dri.so) #2 0x7f62ba1f2ac7 n/a (i965_dri.so) #3 0x7f62c2e9c6db start_thread (libpthread.so.0) #4 0x7f62c2bc588f __clone (libc.so.6) ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1884395 Title: GIMP crashes X-Server when mouse is first used after program launch Status in xorg-server package in Ubuntu: New Bug description: As of 5 days ago (6/15/20) and after several recent Mint 19.3 software updates, GIMP 2.10.20 started crashing. I can open GIMP OK and even open an image file. But as soon as I use the mouse, even to click on the opened image, or click a menu item, GIMP crashes and I end up at the login screen. I’ve also tried earlier versions of GIMP, namely 2.10.18 and 2.10.14 but same problem. I found the cause to be my Logitech MX Master wireless mouse unifying USB wireless receiver. GIMP works OK when using the laptop track pad. Log excerpt: lightdm PAM adding faulty module: pam_kwallet5.so PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory systemd-coredum Process 1451 (Xorg) of user 0 dumped core. Stack trace of thread 1554: #0 0x559b66bcdde5 n/a (Xorg) #1 0x559b66bce572 n/a (Xorg) #2 0x559b66c9424b n/a (Xorg) #3 0x559b66c95019 miPointerSetPosition (Xorg) #4 0x559b66b64c6e n/a (Xorg) #5 0x559b66b65410 n/a (Xorg) #6 0x559b66b66b74 GetPointerEvents (Xorg) #7 0x559b66b67150 QueuePointerEvents (Xorg) #8 0x7f62bf07bfb5 n/a (libinput_drv.so) #9 0x7f62bf07cb40 n/a (libinput_drv.so) #10 0x559b66ca9e83 n/a (Xorg) #11 0x559b66cac561 n/a (Xorg) #12 0x559b66ca9cce n/a (Xorg) #13 0x7f62c2e9c6db start_thread (libpthread.so.0) #14 0x7f62c2bc588f __clone (libc.so.6) Stack trace of thread 1451: #0 0x7f62c2bc5bb7 epoll_wait (libc.so.6) #1 0x559b66cac517 n/a (Xorg) #2 0x559b66ca5533 WaitForSomething (Xorg) #3 0x559b66b4e463 n/a (Xorg) #4 0x559b66b526a8 n/a (Xorg) #5 0x7f62c2ac5b97 __libc_start_main (libc.so.6) #6 0x559b66b3c32a _start (Xorg) Stack trace of thread 1547: #0 0x7f62c2ea29f3 futex_wait_cancelable (libpthread.so.0) #1 0x7f62ba1f2ecb n/a (i965_dri.so) #2 0x7f62ba1f2ac7 n/a (i965_dri.so) #3 0x7f62c2e9c6db start_thread (libpthread.so.0) #4 0x7f62c2bc588f __clone (libc.so.6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1884395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884393] [NEW] With Auto-hide dock enabled, icons get hidden behind dock & dock does not hide untill there's an app near it
Public bug reported: Gnome Settings>Appearance> auto hide dock //enable it automatically you might see icons getting hidden behind dock (keep windows away from dock). Not only desktop getting hidden under dock looks unaesthetic, But don't you think dock should remain hidden till the user points mouse at it? Other wise we won't be able to use left side of the desktop to keep icons. Dock never hides till an app is near it, so desktop icons may get under it. So that we can use the entire left side of desktop to keep icons, with the auto hide dock option enabled, don't you think dock should remain hidden until user points mouse near it? //probably a logical error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 02:14:32 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 0880CR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: NN_PC_NB0 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0880CR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "icon getting hidden under dock & dock not hiding as no window near it" https://bugs.launchpad.net/bugs/1884393/+attachment/5385694/+files/Screenshot%20from%202020-06-21%2002-26-26.png ** Description changed: Gnome Settings>Appearance> auto hide dock //enable it automatically you might see icons getting hidden behind dock (keep windows away from dock). Not only desktop getting hidden under dock looks unaesthetic, But don't you think dock should remain hidden till the user points mouse at it? Other wise we won't be able to use left side of the desktop to keep icons. Dock never hides till an app is near it, so desktop icons may get under it. So that we can use the entire left side of desktop to keep icons, with the auto hide dock option enabled, don't you think dock should remain hidden until user points mouse near it? + //probably a logical error + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 02:14:32 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028
[Desktop-packages] [Bug 1884391] Re: PCI/internal sound card not detected
Here's what I've tried (that I can remember): - Reinstalling all the ALSA packages - Rebooting, turning off the sound devices in the BIOS, letting it boot, then reboot, turn the sound devices back on, and let it boot - rm -rf ~/.config/pulseaudio && pulseaudio -k - sudo alsa force-reload - Remove and reinstall pulseaudio packages - sudo apt purge alsa-base pulseaudio && sudo apt install ubuntu-gnome-desktop && sudo alsa force-reload -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1884391 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: My sound card stopped being recognized suddenly today. lspci shows the card, but alsa and pulseaudio don't see it. I verified that the kernel modules are installed. I noticed this today when I logged on and the only audio device was the dummy device. I tried the various fixes I found online for this, but nothing worked. I haven't made any changes to any audio packages manually, but I have had automatic updates over the last few days which may have caused this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 15:29:04 2020 InstallationDate: Installed on 2020-03-14 (98 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1884391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884392] Re: Clock does not remain in center when auto-hide the dock setting is disabled from gnome settings
** Description changed: BUG condition: Gnome Settings>Appearance> disable "auto hide the dock" You will see clock gets displaced to a bit right from the center from the screen & this looks bad. WORKAROUND: Enable "auto hide the dock" from gnome settings + + //this is probably a logical error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 01:56:40 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:0794] + Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: - LANGUAGE=en_IN:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + LANGUAGE=en_IN:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 0880CR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: NN_PC_NB0 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0880CR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884392 Title: Clock does not remain in center when auto-hide the dock setting is disabled from gnome settings Status in xorg package in Ubuntu: New Bug description: BUG condition: Gnome Settings>Appearance> disable "auto hide the dock" You will see clock gets displaced to a bit right from the center from the screen & this looks bad. WORKAROUND: Enable "auto hide the dock" from gnome settings //this is probably a logical error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 01:56:40 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg
[Desktop-packages] [Bug 1884391] [NEW] PCI/internal sound card not detected
Public bug reported: My sound card stopped being recognized suddenly today. lspci shows the card, but alsa and pulseaudio don't see it. I verified that the kernel modules are installed. I noticed this today when I logged on and the only audio device was the dummy device. I tried the various fixes I found online for this, but nothing worked. I haven't made any changes to any audio packages manually, but I have had automatic updates over the last few days which may have caused this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 15:29:04 2020 InstallationDate: Installed on 2020-03-14 (98 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1884391 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: My sound card stopped being recognized suddenly today. lspci shows the card, but alsa and pulseaudio don't see it. I verified that the kernel modules are installed. I noticed this today when I logged on and the only audio device was the dummy device. I tried the various fixes I found online for this, but nothing worked. I haven't made any changes to any audio packages manually, but I have had automatic updates over the last few days which may have caused this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 15:29:04 2020 InstallationDate: Installed on 2020-03-14 (98 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1884391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884392] [NEW] Clock does not remain in center when auto-hide the dock setting is disabled from gnome settings
Public bug reported: BUG condition: Gnome Settings>Appearance> disable "auto hide the dock" You will see clock gets displaced to a bit right from the center from the screen & this looks bad. WORKAROUND: Enable "auto hide the dock" from gnome settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 01:56:40 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 0880CR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: NN_PC_NB0 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0880CR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "displaced" https://bugs.launchpad.net/bugs/1884392/+attachment/5385675/+files/Screenshot%20from%202020-06-21%2002-02-24.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884392 Title: Clock does not remain in center when auto-hide the dock setting is disabled from gnome settings Status in xorg package in Ubuntu: New Bug description: BUG condition: Gnome Settings>Appearance> disable "auto hide the dock" You will see clock gets displaced to a bit right from the center from the screen & this looks bad. WORKAROUND: Enable "auto hide the dock" from gnome settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 01:56:40 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.
[Desktop-packages] [Bug 1538615] Re: Cat causes login screen to hang
** Attachment added: "demonstration.jpg" https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1538615/+attachment/5385654/+files/demonstration.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1538615 Title: Cat causes login screen to hang Status in unity-greeter package in Ubuntu: Fix Released Status in unity-greeter source package in Trusty: Triaged Bug description: Steps to reproduce: 1. Leave laptop unattended in a cold room with a warm cat. 2. Cat will sit on laptop keyboard. 3. Wait 1 hour. 4. Lightdm will become unresponsive. Symptoms: Due to excessive password input by cat, lightdm acts oddly. I try to hit enter to try the invalid password and then type in the correct password, but enter has no affect. The cursor is not blinking, and hitting backspace has no effect. Using Ctrl+a or using shift+Ctrl+left arrow doesn't select the whole password to delete it. Hitting capslock causes the warning symbol to appear or disappear. The mouse moves, but clicking on the settings icon, date, sound icon, or language icon has no effect. One person suggested seeing if the cat had triggered scroll lock, but toggling between ctrl+q and ctrl+s had no effect. Logging in on a virtual terminal still works. Alternative steps to reproduce if cat is unavailable or uncooperative about being placed on keyboard (see attached pictures): 0. Glare at cat. 1. Restart lightdm. 2. Log in as a normal user. 3. Lock screen with ctrl+alt+l (I'm running Ubuntu 15.10). 4. Weigh self. Weigh self + cat. Find books approximately equal to 10 lbs, and various household items to simulate cat paws (I used two large nail clippers, a fat key, and a bottle opener). 5. Put items on keyboard, avoiding function keys, backspace, and enter. Place books on top of household items. 6. Wait 1 hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1538615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
What's new : I can reproduce the problem on Ubuntu 20.04 live USB, so I'm sure the root cause is not a broken config on my side. To summarize : Ubuntu 20.04 / Fedora 32.1 are affected. (Ubuntu 19.10 is not) - Rhythmbox 3.4.4 fully affected (wrong sink at start + output is switched to a RAOP sink with each new song) - Spotify is mildly affected : wrong sink at start, but after that you can play new song normally - Rhytmbox 3.4.3 (in Ubuntu 19.10) is lightly affected : wrong sink on 1st launched, but the last sink used is saved for next launch - VLC, Totem, Firefox, Chromium are unaffected Requirements to trigger the bug : 1 (maybe 2) RAOP (aka Airplay / AirTunes) sinks available on local network in addition to local soundcard. Steps to reproduce : $ sudo apt install pulseaudio-module-raop $ sudo apt install paprefs If needed, fix paprefs (which is broken in 20.04) $ sudo ln -s /usr/lib/pulse-13.99.1/ /usr/lib/pulse-13.99 optional, to monitor sinks used by rhythmbox : $ sudo apt install pavucontrol && pavucontrol Launch paprefs and check "Make discoverable Apple AirTunes soud devices available locally" Launch Rhythmbox, play a track, correct the sink, play another track (next button or direct choice), correct the sink, etc. As the issue has been abruptly dismissed upstream : https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1797#note_844963 (I assume the guy knows his job), you are my only hope here ! I know it's my fault, I should have stayed in Ubuntu 19.10 and wait 20.04.1, but I felt harassed by the updater popup reminder :) No, seriously I needed rhythmbox 3.4.4, to support my new phone. So what should I do now ? I understand there is some kind of middleware between pulseaudio and rhythmbox : gstreamer ? Could it be the "culprit" ? If yes, should I report a bug here https://gstreamer.freedesktop.org/bugs/ or downstream ? Is it possible to downgrade gstreamer ? ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #1797 https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1797 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873026] Re: File manager grabs favorites folders on left
I just did an update and "Files" was updated with it, so I checked, and for me at least, it appears this behavior is fixed. Here is what was updated with this update: Upgrade: libgirepository-1.0-1:amd64 (1.64.0-2, 1.64.1-1~ubuntu20.04.1), gir1.2-freedesktop:amd64 (1.64.0-2, 1.64.1-1~ubuntu20.04.1), gir1.2-nautilus-3.0:amd64 (1:3.36.2-0ubuntu1, 1:3.36.3-0ubuntu1), apport:amd64 (2.20.11-0ubuntu27.2, 2.20.11-0ubuntu27.3), nautilus:amd64 (1:3.36.2-0ubuntu1, 1:3.36.3-0ubuntu1), libnautilus-extension1a:amd64 (1:3.36.2-0ubuntu1, 1:3.36.3-0ubuntu1), gir1.2-glib-2.0:amd64 (1.64.0-2, 1.64.1-1~ubuntu20.04.1), python3-apport:amd64 (2.20.11-0ubuntu27.2, 2.20.11-0ubuntu27.3), apport-gtk:amd64 (2.20.11-0ubuntu27.2, 2.20.11-0ubuntu27.3), grub-efi-amd64-signed:amd64 (1.142+2.04-1ubuntu26, 1.142.1+2.04-1ubuntu26), nautilus-data:amd64 (1:3.36.2-0ubuntu1, 1:3.36.3-0ubuntu1), python3-problem-report:amd64 (2.20.11-0ubuntu27.2, 2.20.11-0ubuntu27.3) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873026 Title: File manager grabs favorites folders on left Status in nautilus package in Ubuntu: Confirmed Bug description: Upgraded to beta release of 20.4 and Nautilus file manager now is exhibiting a problem reported in older versions. When clicking on folders in the left side window the folder will be dragged to where ever the mouse is moved. The work around is to click once move slightly then click again to release in the same spot. The other work around is to reboot and sometimes the problem goes away. I believe all this information has be sent when I did the ubuntu-bug command, but here is is again: Release: Ubuntu Focal Fossa (development branch) nautilus:Installed: 1:3.36.1.1-1ubuntu2 Expected behavior: Expected to click on "favorite" folder and be taken to the folder in the right side of screen. Actual behavior: Clicking on "favorite" folder grabbed the folder to drag where ever the cursor went. Need to click again in same place on left screen to release the folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 10:28:53 2020 InstallationDate: Installed on 2017-03-19 (1123 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884384] [NEW] in high contrast mode the calendar display uncomfortable
Public bug reported: in high contrast mode the calendar display uncomfortable i.e. the weekends and the column with the number of week are very hard to comprehend :( ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 21:33:05 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek EasyCamera Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=5c5e4d9a-db2e-49a9-8392-07091e531b13 ro quiet splash resume=UUID=f15ed6b9-9e79-4114-af6b-1797d024ff44 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-17ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:svnLENOVO:pn81FL:pvrLenovoideapad330-17ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-17ICH: dmi.product.family: ideapad 330-17ICH dmi.product.name: 81FL dmi.product.sku: LENOVO_MT_81FL_BU_idea_FM_ideapad 330-17ICH dmi.product.version: Lenovo ideapad 330-17ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884384 Title: in high contrast mode the calendar display uncomfortable Status in xorg package in Ubuntu: New Bug description: in high contrast mode the calendar display uncomfortable i.e. the weekends and the column with the number of week are very hard to comprehend :( ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 21:33:05 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek EasyCamera Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=5c5e4d9a-db2e-49a9-8392-07091e531b13 ro quiet splash resume=UUID=f15ed6b9-9e79-4114-af6b-1797d024ff44 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-17ICH dmi.modalias: d
Re: [Desktop-packages] [Bug 1869561] Re: Libreoffice Help does not work
The package that is installed in the stock version of ubuntu (20.04) is 1:6.4.3-0 As I said, still getting the same error. On Sat, Jun 20, 2020 at 11:45 AM Marc Bruell wrote: > I updated both ubuntu 20.04 and mate 20.04, and I continue to get the > error that the object can't be opened. > > On Sat, Jun 20, 2020 at 1:35 AM Tim Passingham <1869...@bugs.launchpad.net> > wrote: > >> I am now using version Version: 6.4.4.2 >> Build ID: 1:6.4.4-0ubuntu0.20.04.1 >> CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; >> Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB >> Calc: threaded >> >> The Help now works as expected. >> >> Thanks. >> >> I changed the tag - I hooe I got that right. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1869561 >> >> Title: >> Libreoffice Help does not work >> >> Status in libreoffice package in Ubuntu: >> Fix Released >> Status in libreoffice source package in Focal: >> Fix Committed >> >> Bug description: >> In the latest PPA release of Libreoffice, the Help does not work. IN >> version 6.3.5.2 it is OK. I the version below it returns an error. >> >> Version: 6.4.2.2 >> Build ID: 1:6.4.2-0ubuntu0.19.10.3 >> CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; >> Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB >> Calc: threaded >> >> >> The Error is: >> >> Object not accessible. >> The object cannot be accessed >> due to insufficient user rights. >> >> >> The Help used to open the help in a browser window. This latest >> version seems to try to open the old type of local help (rather than using >> a browser). >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions >> > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873562] Re: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before instal
To proceed with upgrade, for every error dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_19.2.8-0ubuntu0~18.04.3_i386.deb (--unpack): unable to make backup link of './usr/lib/i386-linux-gnu/dri/vmwgfx_dri.so' before installing new version: Input/output error Reinstalling /etc/drirc that was moved away Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_19.2.8-0ubuntu0~18.04.3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) remove the referenced file, i.e., $ sudo rm -rf /usr/lib/i386-linux-gnu/dri/vmwgfx_dri.so -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1873562 Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux- gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error Status in mesa package in Ubuntu: New Bug description: After running $ sudo apt full-upgrade Could be contributing factor to Chromium crashing tabs randomly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 NonfreeKernelModules: overlay ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CompositorRunning: None Date: Sat Apr 18 03:59:22 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1873562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1869561] Re: Libreoffice Help does not work
I updated both ubuntu 20.04 and mate 20.04, and I continue to get the error that the object can't be opened. On Sat, Jun 20, 2020 at 1:35 AM Tim Passingham <1869...@bugs.launchpad.net> wrote: > I am now using version Version: 6.4.4.2 > Build ID: 1:6.4.4-0ubuntu0.20.04.1 > CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; > Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB > Calc: threaded > > The Help now works as expected. > > Thanks. > > I changed the tag - I hooe I got that right. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1869561 > > Title: > Libreoffice Help does not work > > Status in libreoffice package in Ubuntu: > Fix Released > Status in libreoffice source package in Focal: > Fix Committed > > Bug description: > In the latest PPA release of Libreoffice, the Help does not work. IN > version 6.3.5.2 it is OK. I the version below it returns an error. > > Version: 6.4.2.2 > Build ID: 1:6.4.2-0ubuntu0.19.10.3 > CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; > Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB > Calc: threaded > > > The Error is: > > Object not accessible. > The object cannot be accessed > due to insufficient user rights. > > > The Help used to open the help in a browser window. This latest version > seems to try to open the old type of local help (rather than using a > browser). > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884378] [NEW] Text doesn't get clipped when too long
Public bug reported: Text labels should be clipped (like with text-overflow: ellipsis). See first param on the screenshot. Ubuntu 20.04 gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2020-06-20 20-26-20.png" https://bugs.launchpad.net/bugs/1884378/+attachment/5385617/+files/Screenshot%20from%202020-06-20%2020-26-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1884378 Title: Text doesn't get clipped when too long Status in gnome-control-center package in Ubuntu: New Bug description: Text labels should be clipped (like with text-overflow: ellipsis). See first param on the screenshot. Ubuntu 20.04 gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1884378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873638] Re: Titlebar buttons incorrectly placed when set to appear on the left
This bug is ubuntu-specific. Fedora's 3.36.3 gnonme-control-center does not have this issue, see this report & closure upstream https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1034#note_844891 In my case Tweaks does NOT exhibit this bug. This weird behavior only happens in gnome-control-center ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1034 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1034 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873638 Title: Titlebar buttons incorrectly placed when set to appear on the left Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Unexpected button location on settings. Check image as screenshot attachment. Gnome Tweaks -> move the Titlebar buttons from Right to Left. Buttons should be paced on the extreme left -> for gnome-control- center they are centrally placed. OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question how be how to reproduce? To switch button on the left side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
I'm having the same issue - dead cursor appears after machine has gone to sleep when I have multiple monitors connected. I'm on Ubuntu 20.04 and use Wayland, on an AMD GPU. I have updated everything with apt to the most recent version and the issue is still occurring for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Expected: After my computer had gone to sleep and I log in I should see only a single active mouse cursor. What happened instead: After my computer had gone to sleep and I logged in I noticed a second frozen/stuck mouse cursor was on screen and was rendered in one place over any active application windows. I recently upgraded to 20.04 from 19.10 but the same issue was occurring in 19.10 as well. Logging out completely then logging back in again removed the extra frozen cursor. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy mutter mutter: Installed: 3.36.1-3ubuntu3 Candidate: 3.36.1-3ubuntu3 Version table: *** 3.36.1-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 19:53:03 2020 InstallationDate: Installed on 2019-03-09 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1880728] Re: [amdgpu] Gnome Shell freeze
another crash yesterday no new error links, ran another prevboot. On Thu, Jun 18, 2020 at 7:57 AM DavidJr. wrote: > Crashed again overnight. No response from mouse, keyboard, or power > button. Hard rebooted. Dont see any new error links. I have reinstalled > TeamViewer and disabled dash to dock to see if that does anything > different. > > On Wed, Jun 17, 2020 at 9:50 PM Daniel van Vugt < > 1880...@bugs.launchpad.net> wrote: > >> Oh those are much better links, thanks. There you have: >> >> Bug 1877075: A fix for 20.04 is on the way (you will need libmutter >> version 3.36.3). >> >> Bug 1843982: A fix for 20.04 was released to updates yesterday. >> >> Bug 1878775: Not sure but maybe fixed with bug 1843982 yesterday? >> >> But that doesn't help us to choose a single issue for this bug to be >> about. I guess this bug doesn't need to stay open unless we can identify >> some new issue that doesn't already have a bug ID. Please continue >> reporting your crashes here so we can find some pattern. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1880728 >> >> Title: >> [amdgpu] Gnome Shell freeze >> >> Status in gnome-shell package in Ubuntu: >> Incomplete >> >> Bug description: >> was logged in through team viewer and got kicked out. when i was able >> to physically access the machine the screens were on, but was not able >> to move the mouse or interact with the computer. performed hard >> reboot to get it back on. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 20.04 >> Package: xorg 1:7.7+19ubuntu14 >> ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 >> Uname: Linux 5.4.0-31-generic x86_64 >> ApportVersion: 2.20.11-0ubuntu27 >> Architecture: amd64 >> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >> CasperMD5CheckResult: skip >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Tue May 26 11:24:02 2020 >> DistUpgraded: Fresh install >> DistroCodename: focal >> DistroVariant: ubuntu >> ExtraDebuggingInterest: Yes >> GpuHangFrequency: Several times a week >> GpuHangReproducibility: Seems to happen randomly >> GpuHangStarted: Immediately after installing this version of Ubuntu >> GraphicsCard: >>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX >> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA >> controller]) >> Subsystem: PC Partner Limited / Sapphire Technology Radeon RX >> 470/480 [174b:e347] >> InstallationDate: Installed on 2020-05-09 (16 days ago) >> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 >> (20200423) >> MachineType: Micro-Star International Co., Ltd. MS-7A34 >> ProcEnviron: >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic >> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7 >> SourcePackage: xorg >> Symptom: display >> Title: Xorg freeze >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 07/08/2019 >> dmi.bios.vendor: American Megatrends Inc. >> dmi.bios.version: A.LM >> dmi.board.asset.tag: To be filled by O.E.M. >> dmi.board.name: B350 PC MATE(MS-7A34) >> dmi.board.vendor: Micro-Star International Co., Ltd >> dmi.board.version: 2.0 >> dmi.chassis.asset.tag: To be filled by O.E.M. >> dmi.chassis.type: 3 >> dmi.chassis.vendor: Micro-Star International Co., Ltd. >> dmi.chassis.version: 2.0 >> dmi.modalias: >> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: >> dmi.product.family: To be filled by O.E.M. >> dmi.product.name: MS-7A34 >> dmi.product.sku: To be filled by O.E.M. >> dmi.product.version: 2.0 >> dmi.sys.vendor: Micro-Star International Co., Ltd. >> version.compiz: compiz N/A >> version.libdrm2: libdrm2 2.4.101-2 >> version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 >> version.libgl1-mesa-glx: libgl1-mesa-glx N/A >> version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 >> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A >> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 >> version.xserver-xorg-video-intel: xserver-xorg-video-intel >> 2:2.99.917+git20200226-1 >> version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau >> 1:1.0.16-1 >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+subscriptions >> > ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1880728/+attachment/5385615/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to
[Desktop-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Hello, i'm back to this issue. I reinstalled Ubuntu 20.04 on the same laptop and i'm still having sound related issues, as other seems to also feedback. Main issue is the stability of the computer with default settings. It happens on a random (but high ratio) basis that the computer gets completely frozen at the login page. Only way to pass throught this is to force a poweroff with a long press on power button. When this issue does not accur, the system is pretty stable, but those random freeze still do occur and are seems related to sound system because for example the fact that I receive a call on some instant messaging app do cause the freeze ! Stability gets even worse when the laptop is hooked to the HP G2 thunderbolt dock. Under those condition, the login page freeze is systematic (but it's possible to boot without the dock and to hook the dock after which get the system back to usable mic but unstable system) If I add the options snd-hda-intel dmic_detect=0 (either in the modprobe.d rules or with the kernel command line version) then I have a perfectly stable computer, but without microphone. System is running kernel Linux ZBook15G6 5.4.0-38-lowlatency #42-Ubuntu SMP PREEMPT Mon Jun 8 17:28:37 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux but behaviour has been the same with generic version of the kernel, and also with previous versions. If there are any tests or logs I can provide to try getting this sorted out, please let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1871573] Re: [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found
Hi Thierry, >From memory I did set "on demand" mode and it worked correctly. Now it is a strange situation, kernel 5.4.0-28 is the latest that boots correctly in my setup if only built in screen (on later versions, it hangs shortly after Linux boot started, Lenovo sign still there and progress circle not shown anymore) Latest kernels boots correctly if there is external screen plugged by HDMI (so, maybe "hung" from 1st case it is just that still somehow expects external screen...) Regards, Igor čet, 18. lip 2020. u 13:45 Thierry Bossy <1871...@bugs.launchpad.net> napisao je: > Hi, > > I have a very similar problem and noticed the following: > My external display is working with Nvidia "Performance Mode" only. In > "On-demand" mode, I have a black screen that it is not detected in Ubuntu > system settings, although it is detected by Nvidia X Server Settings. > As if we needed a parameter in On-demand to force HDMI interface to start > with Nvidia card and not Intel. > > Any hints about this? > > @Igor, are you sure that you are in "On Demand" mode? I realized that it > automatically switches to "Performance Mode" when we change the driver. > > Thanks, > Thierry > --- > My config: > - Lenovo Thinkpad P1 Gen2 with Nvidia Quadro T2000 > - Secure Boot Disabled > - Nvidia driver 440 activated > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1871573 > > Title: > [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found > > Status in nvidia-prime package in Ubuntu: > Won't Fix > > Bug description: > Hi, > > I know that you have certified version 18.04 and that 20.04 is not out > yet. > So this is more heads up. > > I am testing Ubuntu 20.04 on new Lenovo P1 2nd gen. > Currently HDMI does not work. > > How do I know that problem is not in cable or monitor ? > If I boot to windows, HDMI port works as expected. > > Thank you, > Igor RACIC > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > ApportVersion: 2.20.11-0ubuntu24 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Apr 8 10:00:57 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: >acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed >nvidia, 440.64, 5.4.0-21-generic, x86_64: installed > GraphicsCard: >Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 > [VGA controller]) > Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] > InstallationDate: Installed on 2020-04-01 (6 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) > MachineType: LENOVO 20QTCTO1WW > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic > root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/20/2020 > dmi.bios.vendor: LENOVO > dmi.bios.version: N2OET42W (1.29 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20QTCTO1WW > dmi.board.vendor: LENOVO > dmi.board.version: SDK0R32862 WIN > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: None > dmi.modalias: > dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: > dmi.product.family: ThinkPad P1 Gen 2 > dmi.product.name: 20QTCTO1WW > dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 > dmi.product.version: ThinkPad P1 Gen 2 > dmi.sys.vendor: LENOVO > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.100-4 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20190815-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1871573/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1871573 Title: [Lenovo ThinkPad P1 Gen 2] HDMI port can't be found Status in nvidia-prime package in Ubuntu: Won't Fix Bug description: Hi,
[Desktop-packages] [Bug 1881943] Re: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg
I have the same problem with mainline 5.7 kernel. ** Summary changed: - [Inspiron 5391, Realtek ALC3204] Sound stopped to work, errors in dmesg + [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg ** Description changed: Sound worked, but accidentally stopped to work at all. Just before it I had plugged and unplugged HDMI display (but without sound via HDMI). Only restart helped. Here is dmesg output while the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND - /dev/snd/controlC0: tenikeev 4612 F pulseaudio - /dev/snd/pcmC0D0p: tenikeev 4612 F...m pulseaudio - /dev/snd/pcmC0D6c: tenikeev 4612 F...m pulseaudio + /dev/snd/controlC0: username 4612 F pulseaudio + /dev/snd/pcmC0D0p: username 4612 F...m pulseaudio + /dev/snd/pcmC0D6c: username 4612 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 3 20:42:33 2020 InstallationDate: Installed on 2020-05-28 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: - июн 03 20:04:56 tenikeev-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") - июн 03 20:04:59 tenikeev-5391 systemd[4295]: pulseaudio.service: Succeeded. - июн 03 20:05:09 tenikeev-5391 systemd[4295]: pulseaudio.socket: Succeeded. + июн 03 20:04:56 username-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") + июн 03 20:04:59 username-5391 systemd[4295]: pulseaudio.service: Succeeded. + июн 03 20:05:09 username-5391 systemd[4295]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5391, Realtek ALC3204, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07DM2C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5391 dmi.product.sku: 096E dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881943 Title: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg Status in alsa-driver package in Ubuntu: New Bug description: Sound worked, but accidentally stopped to work at all. Just before it I had plugged and unplugged HDMI display (but without sound via HDMI). Only restart helped. Here is dmesg output while the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 4612 F pulseaudio /dev/snd/pcmC0D0p: username 4612 F...m pulseaudio /dev/snd/pcmC0D6c: username 4612 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 3 20:42:33 2020 InstallationDate: Installed on 2020-05-28 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: июн 03 20:04:56 username-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") июн 03 20:04:59 username-5391 systemd[4295]: pulseaudio.service: Succeeded. июн 03 20:05:09 username-5391 systemd[4295]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5391, Realtek ALC3204, Spea
[Desktop-packages] [Bug 1884367] [NEW] The display is flickering
Public bug reported: For flickering display, I tried to update intel display drivers, and this bug report came during the process ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 18:39:54 2020 DistUpgraded: 2020-06-10 01:24:34,201 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2018-01-23 (878 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LAB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=5b2de4e2-596a-412f-b22c-5aa72fb9234a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-06-09 (10 days ago) dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.503 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Aug 16 15:18:06 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1249 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884367 Title: The display is flickering Status in xorg package in Ubuntu: New Bug description: For flickering display, I tried to update intel display drivers, and this bug report came during the process ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 18:39:54 2020 DistUpgraded: 2020-06-10 01:24:34,201 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2018-01-23 (878 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera Bus 001 Device 001: ID 1
[Desktop-packages] [Bug 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
I am experiencing the same problem with a RODECaster Pro and (in my case) Arch Linux. The following log output is generated when I connect the RODECaster via USB: kernel: usb 2-9.4.2: new high-speed USB device number 20 using xhci_hcd kernel: usb 2-9.4.2: New USB device found, idVendor=19f7, idProduct=0011, bcdDevice= 2.10 kernel: usb 2-9.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: usb 2-9.4.2: Product: RODECaster Pro kernel: usb 2-9.4.2: Manufacturer: RODE Microphones kernel: usb 2-9.4.2: SerialNumber: 001A kernel: hid-generic 0003:19F7:0011.0009: hiddev1,hidraw7: USB HID v1.10 Device [RODE Microphones RODECaster Pro] on usb-:00:14.0-9.4.2/input0 kernel: usb 2-9.4.2: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 1) kernel: usb 2-9.4.2: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 1) mtp-probe[4037]: checking bus 2, device 20: "/sys/devices/pci:00/:00:14.0/usb2/2-9/2-9.4/2-9.4.2" mtp-probe[4037]: bus: 2, device: 20 was not an MTP device systemd-udevd[4043]: controlC4: Process '/usr/bin/alsactl restore 4' failed with exit code 99. mtp-probe[4050]: checking bus 2, device 20: "/sys/devices/pci:00/:00:14.0/usb2/2-9/2-9.4/2-9.4.2" mtp-probe[4050]: bus: 2, device: 20 was not an MTP device pulseaudio[1460]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. pulseaudio[1460]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="4" name="usb-RODE_Microphones_RODECaster_Pro_001A-01" card_name="alsa_card.usb-RODE_Microphones_RODECaster_Pro_001A-01" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. The RODECaster shows up in the list of cards that ALSA knows about, but PulseAudio can't find a working profile and gives up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1877726 Title: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Please see https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb-soundcard/1236257#1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 nils@blackbox:~/tmp/soundtest$ arecord --list-devices List of CAPTURE Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog [ALC887-VD Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:45:20 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (1354 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AudioUsers: pulse Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Contro
[Desktop-packages] [Bug 1884364] [NEW] package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: Processing triggers for tex-common (6.13) ... Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in /tmp/updmap.hALzKUDl Please include this file if you report a bug. Sometimes, not accepting conffile updates in /etc/texmf/updmap.d causes updmap-sys to fail. Please check for files with extension .dpkg-dist or .ucf-dist in this directory dpkg: error processing package tex-common (--configure): installed tex-common package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: tex-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 20 21:11:32 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-19 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1884364 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Processing triggers for tex-common (6.13) ... Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in /tmp/updmap.hALzKUDl Please include this file if you report a bug. Sometimes, not accepting conffile updates in /etc/texmf/updmap.d causes updmap-sys to fail. Please check for files with extension .dpkg-dist or .ucf-dist in this directory dpkg: error processing package tex-common (--configure): installed tex-common package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: tex-common E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 20 21:11:32 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-19 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1884364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
** Changed in: hplip (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3947d85c-2c09-420b-802f-edf59648248a ro quiet splash SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install)
[Desktop-packages] [Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
@Chris York (1-0hris-x) If by fix you mean the new downloadable hplip-3.20.6, it has the same issue as 3.20.5 - can't install required dependency python-pyqt5. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1881401 Title: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base Status in HPLIP: In Progress Status in hplip package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3947d85c-2c09-420b-802f-edf59648248a ro quiet s
[Desktop-packages] [Bug 1884361] [NEW] User icon not updated in login screen
Public bug reported: I created 2 users. The first and the second user have their own user pictures. When start the laptop and see the login dialog I see the first user picture, but the second user picture is the standard icon (women head profile), but not the picture I assigned to the second user. So, the seond user picture does not get updated in the login screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 20 13:34:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-05-17 (34 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=ed4f23e0-6712-4e26-a125-0da798c01065 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884361 Title: User icon not updated in login screen Status in xorg package in Ubuntu: New Bug description: I created 2 users. The first and the second user have their own user pictures. When start the laptop and see the login dialog I see the first user picture, but the second user picture is the standard icon (women head profile), but not the picture I assigned to the second user. So, the seond user picture does not get updated in the login screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 20 13:34:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-05-17 (34 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=ed4f23e0-6712-4e26-a125-0da798c01065 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS0
[Desktop-packages] [Bug 1869561] Re: Libreoffice Help does not work
I am now using version Version: 6.4.4.2 Build ID: 1:6.4.4-0ubuntu0.20.04.1 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Help now works as expected. Thanks. I changed the tag - I hooe I got that right. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869561] Re: Libreoffice Help does not work
Olivier - thanks - I understand now. I've done the update. It turned out that there were three modules that were't selected using this method (nlpsolver, wiki-publisher and fonts-opensymbol) so I installed them as well. ** Tags removed: focal verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884345] [NEW] printer HP laserjet P2035 prints ASCI characters and tremendously lots of pages by itself
Public bug reported: ubuntu 18.04.4 LTS release 18.04, unable to get pkgname, CUPS problem probably, printer was installed in ubuntu 16 after upgrade to 18 version was working fine for 2 years ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CupsErrorLog: E [20/Jun/2020:09:25:53 +0300] [Job 493] Stopping unresponsive job. CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 10:01:58 2020 InstallationDate: Installed on 2016-11-09 (1318 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for HP-LaserJet-P2035: hp:/usb/HP_LaserJet_P2035?serial=RZ4JQ79 MachineType: Dell Inc. Inspiron 3537 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-LaserJet-P2035.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-LaserJet-P2035.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=a09951af-688e-41b0-9891-0529420ff209 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-09-10 (648 days ago) dmi.bios.date: 08/30/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PHTY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/30/2013:svnDellInc.:pnInspiron3537:pvrA05:rvnDellInc.:rn0PHTY0:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.family: 00 dmi.product.name: Inspiron 3537 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1884345 Title: printer HP laserjet P2035 prints ASCI characters and tremendously lots of pages by itself Status in cups package in Ubuntu: New Bug description: ubuntu 18.04.4 LTS release 18.04, unable to get pkgname, CUPS problem probably, printer was installed in ubuntu 16 after upgrade to 18 version was working fine for 2 years ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CupsErrorLog: E [20/Jun/2020:09:25:53 +0300] [Job 493] Stopping unresponsive job. CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 10:01:58 2020 InstallationDate: Installed on 2016-11-09 (1318 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for HP-LaserJet-P2035: hp:/usb/HP_LaserJet_P2035?serial=RZ4JQ79 MachineType: Dell Inc. Inspiron 3537 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-LaserJet-P2035.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-LaserJet-P2035.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=a09951af-688e-41b0-9891-0529420ff209 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-09-10 (648 days ago) dmi.bios.date: 08/30/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PHTY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/30/2013:svnDellInc.:pnInspiron3537:pvrA05:rvnDellInc.:rn0PHTY0:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.family: 00 dmi.product.name: Inspiron 3537 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1884345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
