[Desktop-packages] [Bug 1862843] Re: chromium crashes when it starts
After a reboot, there is no problem: chromium starts normally. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid ** Information type changed from Public to Private -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1862843 Title: chromium crashes when it starts Status in chromium-browser package in Ubuntu: Invalid Bug description: Ubuntu Eoan with KDE desktop, full updated. Since today, when I start chromium, doesn't appear any window. If I start it on terminal, I read this: $ chromium-browser internal error, please report: running "chromium" failed: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml I reinstalled snap packages but no changes. Infact, in chromium's snap folder there is nothing: $ ll /snap/chromium/current/ totale 0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAQrHugUzZVNDAXAQSlNCB4Ou6Vo1RMmSYPUFShCACBQIGAqUCzANHAAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wAwRkZYRDNCUzRVNlMK/ABERUxMIFUyNDEyTQog/QAyPR5TEQAKICAgICAgAHk= modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x960 1024x768 800x600 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAVwzEYAQEBARkSAQOAJh546uQVo1RKmyUTUFShCACBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/wBWNzk0NzA2OAogICAg/QA7PR9ACwAKICAgICAg/ABTMTkyMQogICAgICAgAOg= modes: 1280x1024 1024x768 800x600 640x480 720x400 Date: Tue Feb 11 22:44:13 2020 DiskUsage: File systemTipo Dim. Usati Dispon. Uso% Montato su /dev/nvme0n1p3 ext4 177G 87G 82G 52% /home tmpfs tmpfs 7,8G 140M7,7G 2% /dev/shm /dev/nvme0n1p3 ext4 177G 87G 82G 52% /home InstallationDate: Installed on 2019-01-30 (377 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=7164fc7a-333a-4530-8355-d7af8a4933a3 ro quiet splash vt.handoff=7 Snap.Changes: ID Status Spawn Ready Summary 7Done2020-02-11T21:23:03+01:00 2020-02-11T21:23:03+01:00 Connect chromium:password-manager-service to snapd:password-manager-service Snap.ChromeDriverVersion: Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed with exit code 1: error: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 1: error: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2020-02-05 (6 days ago) dmi.bios.date: 09/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd09/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862843/+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 1862895] [NEW] [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM
Public bug reported: I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Remmina: Feb 12 10:15:22 blade gnome-shell[13670]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a7 Feb 12 10:15:29 blade org.remmina.Remmina.desktop[14229]: [10:15:29:144] [14229:14825] [ERROR][com.winpr.timezone] - Unable to get current timezone rule Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Backtrace: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55685152bd2c] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f482176559f] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0x317) [0x55685144a347] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5ab5) [0x5568514a90d5] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 4: /usr/lib/xorg/Xorg (ResizeVisualArray+0x25d) [0x5568513be1dd] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 5: /usr/lib/xorg/Xorg (AllocARGBCursor+0x198) [0x5568513be478] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 6: /usr/lib/xorg/Xorg (AddTraps+0x2303) [0x5568514a1d23] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5568513caf44] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5568513cefd4] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f48215841e3] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x5568513b8a3e] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Segmentation fault at address 0x0 Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Fatal server error: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Caught signal 11 (Segmentation fault). Server aborting Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Please consult the The X.Org Foundation support Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: #011 at http://wiki.x.org Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: for help. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Please also check the log file at "/home/dima/.local/share/xorg/Xorg.1.log" for additional information. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:30 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Server terminated with error (1). Closing log file. Feb 12 10:15:30 blade remmina[14229]: org.remmina.Remmina: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:15:30 blade gnome-calendar[14118]: gnome-calendar: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. virt-viewer: Feb 12 10:02:09 blade systemd[4463]: Started /usr/bin/virt-viewer -c qemu:///system. Feb 12 10:02:09 blade systemd[1]: Starting Daily apt download activities... Feb 12 10:02:10 blade systemd-resolved[1782]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 12 10:02:10 blade systemd-resolved[1782]: message repeated 3 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 12 10:02:11 blade apt-get: Libgcrypt warning: missing initialization - please fix the application Feb 12 10:02:12 blade /unattended-upgrade: Not running on this development release before 2020-04-01 Feb 12 10:02:12 blade systemd[1]: apt-daily.service: Succeeded. Feb 12 10:02:12 blade systemd[1]: Started Daily apt download activities. Feb 12 10:02:12 blade evolution-alarm[7943]: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:02:12 blade pulseaudio[7212]: X connection to :1 broken (explicit kill or server shutdown). Feb 12 10:02:12 blade at-spi-bus-launcher[7657]: X connection to :1 broken (explicit kill or server shutdown). Feb 12 10:02:12 blade kdeconnectd[7947]:
[Desktop-packages] [Bug 1862843] Re: chromium crashes when it starts
After a reboot, there is no problem: chromium starts normally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1862843 Title: chromium crashes when it starts Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu Eoan with KDE desktop, full updated. Since today, when I start chromium, doesn't appear any window. If I start it on terminal, I read this: $ chromium-browser internal error, please report: running "chromium" failed: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml I reinstalled snap packages but no changes. Infact, in chromium's snap folder there is nothing: $ ll /snap/chromium/current/ totale 0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAQrHugUzZVNDAXAQSlNCB4Ou6Vo1RMmSYPUFShCACBQIGAqUCzANHAAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wAwRkZYRDNCUzRVNlMK/ABERUxMIFUyNDEyTQog/QAyPR5TEQAKICAgICAgAHk= modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x960 1024x768 800x600 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAVwzEYAQEBARkSAQOAJh546uQVo1RKmyUTUFShCACBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/wBWNzk0NzA2OAogICAg/QA7PR9ACwAKICAgICAg/ABTMTkyMQogICAgICAgAOg= modes: 1280x1024 1024x768 800x600 640x480 720x400 Date: Tue Feb 11 22:44:13 2020 DiskUsage: File systemTipo Dim. Usati Dispon. Uso% Montato su /dev/nvme0n1p3 ext4 177G 87G 82G 52% /home tmpfs tmpfs 7,8G 140M7,7G 2% /dev/shm /dev/nvme0n1p3 ext4 177G 87G 82G 52% /home InstallationDate: Installed on 2019-01-30 (377 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=7164fc7a-333a-4530-8355-d7af8a4933a3 ro quiet splash vt.handoff=7 Snap.Changes: ID Status Spawn Ready Summary 7Done2020-02-11T21:23:03+01:00 2020-02-11T21:23:03+01:00 Connect chromium:password-manager-service to snapd:password-manager-service Snap.ChromeDriverVersion: Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed with exit code 1: error: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 1: error: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2020-02-05 (6 days ago) dmi.bios.date: 09/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd09/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862843/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Edwin, let me know if you can get in touch with me via the contact email on my Launchpad page. Thanks for all the help! -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting information on this link to try determine the problem:
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
** Attachment added: "ethtool -S for inactive interface enp94s0f0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853638/+attachment/5327556/+files/ethtool-S-enp94s0f0 -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting information on this link to try determine the
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
ethtool-enp94s0f0 -- Settings for enp94s0f0: Supported ports: [ FIBRE ] Supported link modes: 1baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 1Mb/s Duplex: Full Port: FIBRE PHYAD: 1 Transceiver: internal Auto-negotiation: off Supports Wake-on: g Wake-on: d Current message level: 0x (0) Link detected: yes ethtool-i-enp94s0f0 -- driver: bnxt_en version: 1.10.0 firmware-version: 214.0.253.1/pkg 21.40.25.31 expansion-rom-version: bus-info: :5e:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: no supports-priv-flags: no ethtool-c-enp94s0f0 - Coalesce parameters for enp94s0f0: Adaptive RX: off TX: off stats-block-usecs: 100 sample-interval: 0 pkt-rate-low: 0 pkt-rate-high: 0 rx-usecs: 10 rx-frames: 15 rx-usecs-irq: 1 rx-frames-irq: 1 tx-usecs: 28 tx-frames: 30 tx-usecs-irq: 2 tx-frames-irq: 2 rx-usecs-low: 0 rx-frame-low: 0 tx-usecs-low: 0 tx-frame-low: 0 rx-usecs-high: 0 rx-frame-high: 0 tx-usecs-high: 0 tx-frame-high: 0 ethtool-g-enp94s0f0 Ring parameters for enp94s0f0: Pre-set maximums: RX: 2047 RX Mini:0 RX Jumbo: 8191 TX: 2047 Current hardware settings: RX: 511 RX Mini:0 RX Jumbo: 2044 TX: 511 ethtool-k-enp94s0f0 - Features for enp94s0f0: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: on tx-checksum-ip-generic: off [fixed] tx-checksum-ipv6: on tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] scatter-gather: on tx-scatter-gather: on tx-scatter-gather-fraglist: off [fixed] tcp-segmentation-offload: on tx-tcp-segmentation: on tx-tcp-ecn-segmentation: off [fixed] tx-tcp-mangleid-segmentation: off tx-tcp6-segmentation: on udp-fragmentation-offload: off generic-segmentation-offload: on generic-receive-offload: on large-receive-offload: off rx-vlan-offload: on tx-vlan-offload: on ntuple-filters: on receive-hashing: on highdma: on [fixed] rx-vlan-filter: off [fixed] vlan-challenged: off [fixed] tx-lockless: off [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: on tx-gre-csum-segmentation: on tx-ipxip4-segmentation: on tx-ipxip6-segmentation: off [fixed] tx-udp_tnl-segmentation: on tx-udp_tnl-csum-segmentation: on tx-gso-partial: on tx-sctp-segmentation: off [fixed] tx-esp-segmentation: off [fixed] tx-udp-segmentation: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: off loopback: off [fixed] rx-fcs: off [fixed] rx-all: off [fixed] tx-vlan-stag-hw-insert: on rx-vlan-stag-hw-parse: on rx-vlan-stag-filter: off [fixed] l2-fwd-offload: off [fixed] hw-tc-offload: on esp-hw-offload: off [fixed] esp-tx-csum-hw-offload: off [fixed] rx-udp_tunnel-port-offload: on tls-hw-tx-offload: off [fixed] tls-hw-rx-offload: off [fixed] rx-gro-hw: on tls-hw-record: off [fixed] -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control
[Desktop-packages] [Bug 1861882] Re: Shift key cancels accented IME input with fcitx
I also experienced the same problem but on Google Chrome v80 on Archlinux. So maybe this bug is not only restricted to Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1861882 Title: Shift key cancels accented IME input with fcitx Status in chromium-browser package in Ubuntu: Confirmed Bug description: Prerequisites: * Ubuntu Bionic or Zorin OS 15 * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 * fcitx=1:4.2.9.6-1 * fcitx-unikey=0.2.4-1.1 Steps: * Launch fcitx and chromium-browser. * Focus input to a text box (e.g. omnibox, F12 console). * Trigger fcitx IME with UniKey. * Type a character sequence that produces a Vietnamese character (e.g. "aws" (without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl or Spacebar, which will commit the word. * Press either Shift key. Expected result: * Nothing happens, or the typed character should not change, to the very least. Actual result: * Typed word reverts back to "aws". The underline on the word still retains, meaning that the word is not yet committed. This issue is a real nuisance when typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark right after the word). Remarks: * This issue does not happen on any other programs, only happens on Chromium and Google Chrome, version 79. * Using fcitx-mozc, after typing a Japanese word, the Shift key does not change the character. * This issue, more or less, is similar to bug #1859294, although not a strict duplicate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1861882/+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 1861882] Re: Shift key cancels accented IME input with fcitx
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1861882 Title: Shift key cancels accented IME input with fcitx Status in chromium-browser package in Ubuntu: Confirmed Bug description: Prerequisites: * Ubuntu Bionic or Zorin OS 15 * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 * fcitx=1:4.2.9.6-1 * fcitx-unikey=0.2.4-1.1 Steps: * Launch fcitx and chromium-browser. * Focus input to a text box (e.g. omnibox, F12 console). * Trigger fcitx IME with UniKey. * Type a character sequence that produces a Vietnamese character (e.g. "aws" (without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl or Spacebar, which will commit the word. * Press either Shift key. Expected result: * Nothing happens, or the typed character should not change, to the very least. Actual result: * Typed word reverts back to "aws". The underline on the word still retains, meaning that the word is not yet committed. This issue is a real nuisance when typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark right after the word). Remarks: * This issue does not happen on any other programs, only happens on Chromium and Google Chrome, version 79. * Using fcitx-mozc, after typing a Japanese word, the Shift key does not change the character. * This issue, more or less, is similar to bug #1859294, although not a strict duplicate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1861882/+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 1563110]
Our vision for every child, life in all its fullness. Our prayer for every heart, the will to make it so.We work toward a nation and a world where every child experiences life in all its fullness. Where they are protected, cared for how to sponsor a child in another country and given the opportunities to become everything they’re meant to be. https://www.hopetoshine.in -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Fix Released Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1854085] Re: Totem segfaults on launch
*** This bug is a duplicate of bug 1856927 *** https://bugs.launchpad.net/bugs/1856927 ** This bug has been marked a duplicate of bug 1856927 totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1854085 Title: Totem segfaults on launch Status in totem package in Ubuntu: Invalid Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date at 26/11/2019 Totem crashes with a segfault on launching the icon SIGSEGV in grl_tracker_setup_key_mappings() ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 26 18:45:59 2019 InstallationDate: Installed on 2019-10-25 (32 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1854085/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
"Bad" System/NIC: NIC: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller System: Dell Kernel: 5.3.0-28-generic #30~18.04.1-Ubuntu (Note, this issue has been seen on prior kernels as well, upgraded to latest to see if various problems were resolved) Attaching stats/config files from nics from this system (seeing issue). -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver???
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Good System/Good NIC (all configurations work) Comparison NIC: NetXtreme II BCM57000 10 Gigabit Ethernet QLogic 57000 System: Dell Kernel: 5.0.0-25-generic #26~18.04.1-Ubuntu /proc/net/bonding/bond0 --- Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: enp5s0f1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: enp5s0f1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:00:00:00:73:e2 Slave queue ID: 0 Slave Interface: enp5s0f0 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 00:00:00:00:73:e0 Slave queue ID: 0 /etc/netplan/50-cloud-init.yaml network: bonds: bond0: addresses: - 00.00.235.182/25 gateway4: 00.00.235.129 interfaces: - enp5s0f0 - enp5s0f1 macaddress: 00:00:00:00:73:e0 mtu: 9000 nameservers: addresses: - 00.00.235.172 - 00.00.235.171 search: - maas parameters: down-delay: 0 gratuitious-arp: 1 mii-monitor-interval: 100 mode: active-backup transmit-hash-policy: layer2 up-delay: 0 ethernets: ...(snip).. enp5s0f0: match: macaddress: 00:00:00:00:73:e0 mtu: 9000 set-name: enp5s0f0 enp5s0f1: match: macaddress: 00:00:00:00:73:e2 mtu: 9000 set-name: enp5s0f1 version: 2 -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978]
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
"Bad" Configuration for active-backup mode: $ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: enp94s0f1d1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 Slave Interface: enp94s0f1d1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 2 Permanent HW addr: 4c:d9:8f:48:08:da Slave queue ID: 0 Slave Interface: enp94s0f0 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 2 Permanent HW addr: 4c:d9:8f:48:08:d9 Slave queue ID: 0 --- $ cat uname-rv 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 --- Scrubbed /etc/netplan/50-cloud-init.yaml: network: bonds: bond0: addresses: - 0.0.235.177/25 gateway4: 0.0.235.129 interfaces: - enp94s0f0 - enp94s0f1d1 macaddress: 00:00:00:48:08:00 mtu: 9000 nameservers: addresses: - 0.0.235.171 - 0.0.235.172 search: - maas parameters: down-delay: 0 gratuitious-arp: 1 mii-monitor-interval: 100 mode: active-backup transmit-hash-policy: layer2 up-delay: 0 ethernets: eno1: match: macaddress: 00:00:00:76:6e:ca mtu: 1500 set-name: eno1 eno2: match: macaddress: 00:00:00:76:6e:cb mtu: 1500 set-name: eno2 enp94s0f0: match: macaddress: 00:00:00:48:08:00 mtu: 9000 set-name: enp94s0f0 enp94s0f1d1: match: macaddress: 00:00:00:48:08:da mtu: 9000 set-name: enp94s0f1d1 version: 2 -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in
[Desktop-packages] [Bug 1854085] Re: Totem segfaults on launch
** Attachment removed: "_usr_bin_totem.1000.crash" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1854085/+attachment/5308002/+files/_usr_bin_totem.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1854085 Title: Totem segfaults on launch Status in totem package in Ubuntu: Invalid Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date at 26/11/2019 Totem crashes with a segfault on launching the icon SIGSEGV in grl_tracker_setup_key_mappings() ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 26 18:45:59 2019 InstallationDate: Installed on 2019-10-25 (32 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1854085/+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 1855546] Re: Desktop freezes a while than logs out
Still not resolved ** Changed in: gnome-shell (Ubuntu) Status: Expired => Incomplete -- 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/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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 1855546] Re: Desktop freezes a while than logs out
Please remember to follow the steps in comment #4. -- 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/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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 1855546] Re: Desktop freezes a while than logs out
Still not resolved ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- 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/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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 1862835] Re: Unable to change laptop screen brightness or keyboard backlighting
First a small warning: You seem to be using the 'oibaf' graphics PPA which is not supported and is known to cause bugs. However I think it's unlikely that's relevant here. Second, other people are already reporting that having the Nvidia driver installed has broken their brightness control. See bug 1861532 and bug 1857764. Please try uninstalling the Nvidia driver, and try uninstalling that PPA. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1862835 Title: Unable to change laptop screen brightness or keyboard backlighting Status in Ubuntu: Incomplete Bug description: I am running a Dell XPS 15. Updating to 20.04 means that the keyboard bindings for changing the brightness and keypad backlighting don't work. The icons appear on the screen, but the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:23:22 2020 DistUpgraded: 2020-02-08 14:25:17,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.2, 5.3.0-29-generic, x86_64: installed virtualbox, 6.1.2, 5.4.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2018-11-21 (447 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=78400725-c498-408a-af83-69891ddf09e4 ro quiet splash nouveau.modeset=0 acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-02-08 (3 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd11/08/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002030730.a4e627~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002030730.a4e627~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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/+bug/1862835/+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 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work
[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/1470730 Title: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work Status in alsa-driver package in Ubuntu: Expired Bug description: When I plug in external speakers to line in/line out combo on the laptop the internal speakers are turned off but when I plug the speakers into the docking station (HP UltraSlim Dock 2013 EURO, D9Y32AA) music keeps playing in the internal speakers. Similar behaviour (nothing happens) is experienced with microphone connected to line in on docking station. ### Expected behaviour Plugging in external speakers to docking station should turn off sound from laptop internal speakers. Plugging in microphone to line in on docking station should switch from "internal microphone" to "microphone" in Ubuntu sound settings. ### Current behaviour Sound keeps playing in internal speakers when plugging in external speakers to docking station. Plugging in microphone to line in on docking station, nothing happens. ### Hardware Laptop: HP EliteBook 840 G2 Product number: H9W19EA#AK8 Docking station: HP UltraSlim Dock 2013 EURO Product number: D9Y32AA ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chol 2001 F pulseaudio /dev/snd/controlC0: chol 2001 F pulseaudio /dev/snd/controlC1: chol 2001 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 2 08:16:15 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-05 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 2216 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5093YZ7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G2 dmi.product.version: A3009D410303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1470730/+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 1855546] Re: Desktop freezes a while than logs out
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (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/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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 1855546] Re: Desktop freezes a while than logs out
[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/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+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 1862835] Re: Unable to change laptop screen brightness or keyboard backlighting
** Package changed: ubuntu => xorg (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/1862835 Title: Unable to change laptop screen brightness or keyboard backlighting Status in xorg package in Ubuntu: New Bug description: I am running a Dell XPS 15. Updating to 20.04 means that the keyboard bindings for changing the brightness and keypad backlighting don't work. The icons appear on the screen, but the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:23:22 2020 DistUpgraded: 2020-02-08 14:25:17,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.2, 5.3.0-29-generic, x86_64: installed virtualbox, 6.1.2, 5.4.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2018-11-21 (447 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=78400725-c498-408a-af83-69891ddf09e4 ro quiet splash nouveau.modeset=0 acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-02-08 (3 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd11/08/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002030730.a4e627~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002030730.a4e627~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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/xorg/+bug/1862835/+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 1862835] [NEW] Unable to change laptop screen brightness or keyboard backlighting
You have been subscribed to a public bug: I am running a Dell XPS 15. Updating to 20.04 means that the keyboard bindings for changing the brightness and keypad backlighting don't work. The icons appear on the screen, but the brightness does not change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 09:23:22 2020 DistUpgraded: 2020-02-08 14:25:17,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.2, 5.3.0-29-generic, x86_64: installed virtualbox, 6.1.2, 5.4.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2018-11-21 (447 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=78400725-c498-408a-af83-69891ddf09e4 ro quiet splash nouveau.modeset=0 acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-02-08 (3 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd11/08/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2002030730.a4e627~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2002030730.a4e627~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression single-occurrence third-party-packages ubuntu -- Unable to change laptop screen brightness or keyboard backlighting https://bugs.launchpad.net/bugs/1862835 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1852691] Re: Disable touchscreen gesture
** Also affects: oem-priority/bionic Importance: Undecided Status: New ** No longer affects: oem-priority/bionic ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** No longer affects: oem-priority ** No longer affects: oem-priority/bionic ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1852691 Title: Disable touchscreen gesture Status in OEM Priority Project: Confirmed Status in xf86-input-wacom package in Ubuntu: New Bug description: [Impact] Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 1774242), the issue can be fixed by disabling in-driver gestures for touchscreens. Config file that instructs driver to disable in-driver gestures for touchscreens: # Prevent the Wacom driver from providing its own gestures for # touchscreen devices. # Section "InputClass" Identifier "Wacom touchscreen gestures" MatchDriver "wacom" MatchIsTouchscreen "true" Option "Gesture" "off" EndSection [Test Case] 1) Enable the bionic-proposed repository, and install the xf86-input-wacom package 2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger zoom/rotate and 3+ finger gestures) work as desired. Also check /var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead libinput driver. [Regression Potential] Low To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1852691/+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 1852691] Re: Disable touchscreen gesture
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Tags added: oem-priority originate-from-1814058 somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1852691 Title: Disable touchscreen gesture Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in xf86-input-wacom package in Ubuntu: New Bug description: [Impact] Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 1774242), the issue can be fixed by disabling in-driver gestures for touchscreens. Config file that instructs driver to disable in-driver gestures for touchscreens: # Prevent the Wacom driver from providing its own gestures for # touchscreen devices. # Section "InputClass" Identifier "Wacom touchscreen gestures" MatchDriver "wacom" MatchIsTouchscreen "true" Option "Gesture" "off" EndSection [Test Case] 1) Enable the bionic-proposed repository, and install the xf86-input-wacom package 2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger zoom/rotate and 3+ finger gestures) work as desired. Also check /var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead libinput driver. [Regression Potential] Low To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1852691/+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 1862753] Re: Backport GPU hotplug RandR fix
** Changed in: xorg-server Status: Unknown => Fix Released -- 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/1862753 Title: Backport GPU hotplug RandR fix Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: In order for the first DisplayLink device hotplug after reboot to be correctly acted on in GNOME, the following fix should be backported to all Xorg-server downstream branches that already apply the patch "xf86: autobind GPUs to the screen" (upstream 078277e4d92f05a90c4715d61b89b9d9d38d68ea): https://gitlab.freedesktop.org/xorg/xserver/merge_requests/326 The related upstream bug report fixed by this is https://gitlab.freedesktop.org/xorg/xserver/issues/909 I originally diagnosed the issue on Ubuntu 19.04 with Xorg based on the 1.20.4 upstream release. Upstream will not backport this patch into the stable 1.20 branch, because that branch does not carry "xf86: autobind GPUs to the screen". To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1862753/+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 1862852] Re: lubuntu loads slow and browser cannot handle multiple windows
Thanks for the bug report. 1. You seem to be using the 'oibaf' PPA which is unsupported and is known to cause bugs. But also... 2. Ubuntu 19.04 "disco" is no longer supported at all as it reached end- of-life on 23 January 2020 (https://wiki.ubuntu.com/Releases). Please upgrade to Ubuntu 19.10 before logging any more bugs. And be sure to not use any PPAs if you intend to log bugs. ** Tags added: performance ** Summary changed: - lubuntu loads slow and browser cannot handle multiple windows + [Intel Merom] lubuntu loads slow and browser cannot handle multiple windows ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1862852 Title: [Intel Merom] lubuntu loads slow and browser cannot handle multiple windows Status in Ubuntu: Invalid Bug description: lubuntu loads slow and browser cannot handle multiple windows ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Tue Feb 11 17:57:15 2020 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:01fe] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01fe] InstallationDate: Installed on 2019-10-11 (123 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude D830 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=58532c64-b8c3-4274-99db-6d3cc2aa0f7d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0HN341 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/19/2013:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/+bug/1862852/+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 1862865] [NEW] i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
Public bug reported:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault at
0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 e8
31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef
be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01
80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 e8
31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef
be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 01
80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:17 dharkan kernel: [71072.575930] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:19 dharkan kernel: [71074.591922] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:21 dharkan kernel: [71076.575911] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:23 dharkan kernel: [71078.591901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:25 dharkan kernel: [71080.575883] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:27 dharkan
[Desktop-packages] [Bug 1862792] Re: gnome-shell always crash after boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1862792 Title: gnome-shell always crash after boot Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell always crash after boot with an UnreportableReason. This is in a Wayland session. There are no stability issues after boot. I get this information in the terminal after the command ubuntu-bug p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell p-i@pi-asus-b450f-gaming:~$ [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! ERROR:gl goes from 1 to 19. In Settings the Display is named Microstep 27" The problem might be hardware related: Mobo: ASUSTeK model: ROG STRIX B450-F GAMING GPU: AMD Navi 10 Radeon RX 5700 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 16:43:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-08 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/1862792/+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 1862792] Re: gnome-shell always crash after boot
It sounds like the main issue is that Xwayland has crashed first: [ 31.095070] pi-asus-b450f-gaming gnome-shell[1400]: Connection to xwayland lost Please follow the steps in comment #2 to help us diagnose the problem further. -- 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/1862792 Title: gnome-shell always crash after boot Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell always crash after boot with an UnreportableReason. This is in a Wayland session. There are no stability issues after boot. I get this information in the terminal after the command ubuntu-bug p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell p-i@pi-asus-b450f-gaming:~$ [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! ERROR:gl goes from 1 to 19. In Settings the Display is named Microstep 27" The problem might be hardware related: Mobo: ASUSTeK model: ROG STRIX B450-F GAMING GPU: AMD Navi 10 Radeon RX 5700 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 16:43:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-08 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/1862792/+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 1862753] Re: Backport GPU hotplug RandR fix
Bug 1853357 shares the same upstream link. Should we use bug 1853357 instead? ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #909 https://gitlab.freedesktop.org/xorg/xserver/issues/909 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/issues/909 Importance: Unknown Status: Unknown ** Tags added: focal -- 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/1862753 Title: Backport GPU hotplug RandR fix Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: In order for the first DisplayLink device hotplug after reboot to be correctly acted on in GNOME, the following fix should be backported to all Xorg-server downstream branches that already apply the patch "xf86: autobind GPUs to the screen" (upstream 078277e4d92f05a90c4715d61b89b9d9d38d68ea): https://gitlab.freedesktop.org/xorg/xserver/merge_requests/326 The related upstream bug report fixed by this is https://gitlab.freedesktop.org/xorg/xserver/issues/909 I originally diagnosed the issue on Ubuntu 19.04 with Xorg based on the 1.20.4 upstream release. Upstream will not backport this patch into the stable 1.20 branch, because that branch does not carry "xf86: autobind GPUs to the screen". To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1862753/+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 1862281] Re: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse
Thanks. Please also test "Ubuntu on Wayland" to be sure. It sounds like
the problem is specific to Xorg but we need to be sure it's not the
kernel.
--
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/1862281
Title:
Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
If I run a thermal transition test script (30 seconds stress-ng, 30
seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably
crashes, usually in the first couple of runs and almost 100% of the
time by run 6.
This appears to be hardware-linked, but not due to a specific piece of
bad hardware: I have swapped literally every piece of hardware in the
system.
It shows up (while running the script at the end):
- On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard.
- On both an AMD Ryzen 5 3600 and 3600X CPU.
- With one or two sticks of RAM. I've tested both sticks individually, in
more than one mainboard slot.
- Regardless of whether the mainboard is in/attached to a case.
- Regardless of whether there is an m.2 SSD installed or I'm running off a
live Kubuntu 19.10 USB stick with no hard disk attached.
- Regardless of which of two mice I use (an old Logitech one, or a GTX 133
Gaming mouse).
- Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU.
- Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia
Gigabyte GeForce RTX 2700 Super (with open source drivers in both cases).
- Regardless of whether I'm using KDE or XFCE.
- Regardless of whether I'm using the default KDE DM or switch to GDM3 and
set WaylandEnable=false.
- Regardless of whether I use the default 5.3.0-29-generic kernel or
5.4.17-050417-generic.
- Regardless of whether I go directly into the graphical environment or start
in runlevel 3 and then manually run startx.
- Regardless of whether it's on the rising or falling edge of the
stress-script's temperature changes.
- Regardless of bios version on the X570 mainboard (the one it shipped with,
or the newest one released in January 2020).
- Regardless of whether XMP is on or off in the bios.
- Regardless of whether I use the default or set global c-state to "control =
disabled" in the bios.
- Regardless of whether I add processor.max_cstate=5 idle=halt in grub.
- Regardless of whether or not speakers are plugged in.
- Regardless of whether I'm using a USB port that is directly on the
motherboard or is on the front of the case.
- Regardless of which monitor it is attached to.
It doesn't show up:
- On an old i7-4771 machine I have, also running Kubuntu 19.10, while running
the test script.
- When I use a mouse remotely with ssh -Y [ip of the machine I am reporting
this from] xeyes, while running the test script.
- When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle,
including under saturated network load, while running the test script.
- During stress tests of the GPU, CPU, etc. Tools like memtest, mprime,
Unigine Superposition, repeated kernel compiles, etc run stably overnight.
- When the system is entirely idle aside from mouse movement.
- When I start in runlevel 3 and run the same test script, using the mouse
with gpm.
- Running the same test script without mouse movement: this was stable
overnight, then crashed within a couple of minutes of moving the mouse.
It shows up with load other than the stress-ng+sleep script too, but
much less reliably - I'm writing this bug report on the relevant
machine, with firefox open. Crashes occur at least once a week under
these conditions, but not frequently.
Crashes occur with sensor-reported CPU temperatures of 32 to 41
degrees Celsius. Nothing is overheating, and the system is stable at
much higher temperatures under sustained stress tests.
The symptoms of the crash: the display stops updating and the system
does not respond to any further input, including via the network or
magic sysrq key. There is nothing related to it in syslog or
journalctl, including when I'm running journalctl -f at the time of
the crash.
The test script:
#!/bin/bash
for x in {1..1}
do
echo "Run $x at `date`"
stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief
sleep 30
done
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
Uname: Linux 5.4.17-050417-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Fri Feb 7 00:02:22 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
NVIDIA Corporation
[Desktop-packages] [Bug 1724098] Re: Panel menu icons are briefly way too big (when opened the first time)
I think this should be fixed in Gnome Shell 3.35 as the offending icons are no longer used. ** Tags added: fixed-in-3.35 fixed-upstream -- 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/1724098 Title: Panel menu icons are briefly way too big (when opened the first time) Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: On every fresh boot, the first time when you click the drop down menu for SOUND/WIRELESS/SHUT-DOWN, the sound icon jumps out very big in size...BUT ONLY THE FIRST TIME WHEN YOU RESTART the machine!! --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: org.gnome.shell enabled-extensions ['ubuntu-appindicat...@ubuntu.com'] org.gnome.shell app-picker-view uint32 1 org.gnome.shell favorite-apps ['chromium-browser.desktop', 'firefox.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop'] org.gnome.desktop.interface enable-animations false org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' InstallationDate: Installed on 2017-08-31 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) Package: gnome-shell 3.26.1-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1724098/+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 1799073] Re: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10
I think there is upstream work coming in Gnome Shell 3.36 related to this, but it doesn't seem to work in 20.04 right now. Which are you referring to? -- 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/1799073 Title: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi all. I noticed this problem when I upgraded from 18.04 to 18.04.1 (Worked perfectly in stock 18.04) and then I was testing the 18.10 beta and hoped it would be fixed there but it's not. To reproduce: login to the regular Ubuntu desktop, hit Super+Alt+= (You can validate that your keyboard shortcut is set to the default in Settings->Keyboard.) I also tried changing the keyboard mapping for this action in case there was a conflict, and no matter what I set it to I couldn't zoom from the keyboard. As a partially blind user, this is a show stopper for me - I require screen zoom to be able to use Ubuntu at all for any serious work. Thanks for everything you do! -Chris (Happy to try any work-arounds or testing people can think up to help fix this problem) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2018-10-07 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Package: gnome-shell 3.30.1-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799073/+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 1862772] Re: failed
Please explain in more detail what kind of problem you are experiencing. I can't see anything immediately going wrong in the attached logs. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1862772 Title: failed Status in Ubuntu: Incomplete Bug description: do not understand / it is my fault cheers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 11 11:55:28 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-01-04 (37 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2P ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=ae2a0258-72f7-48c3-a597-3bc06c85e35a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Feb 11 11:40:11 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft Basic Optical Mouse MOUSE, id 8 inputLITEON Technology USB Keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1862772/+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 1862855] [NEW] "file does not exist" for existing files
Public bug reported: libreoffice reports files are missing when trying to open them from anywhere but $HOME/Documents/ May be related to Ubuntu moving libreoffice to be a snap package. How to reproduce: $ echo "anything at all" >/tmp/testfile.txt $ libreoffice /tmp/testfile.txt Expected: LibreOffice Writer starts, or I'm prompted for whether I wanted to use --writer or --calc Seen: error message "/tmp/testfile.txt does not exist" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice (not installed) 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 CurrentDesktop: KDE Date: Tue Feb 11 18:14:58 2020 InstallationDate: Installed on 2018-10-30 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libreoffice UpgradeStatus: Upgraded to eoan on 2019-11-14 (89 days ago) mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1862855 Title: "file does not exist" for existing files Status in libreoffice package in Ubuntu: New Bug description: libreoffice reports files are missing when trying to open them from anywhere but $HOME/Documents/ May be related to Ubuntu moving libreoffice to be a snap package. How to reproduce: $ echo "anything at all" >/tmp/testfile.txt $ libreoffice /tmp/testfile.txt Expected: LibreOffice Writer starts, or I'm prompted for whether I wanted to use --writer or --calc Seen: error message "/tmp/testfile.txt does not exist" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice (not installed) 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 CurrentDesktop: KDE Date: Tue Feb 11 18:14:58 2020 InstallationDate: Installed on 2018-10-30 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libreoffice UpgradeStatus: Upgraded to eoan on 2019-11-14 (89 days ago) mtime.conffile..etc.logrotate.d.apport: 2018-12-13T12:13:33.355709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862855/+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 1858092] Re: Network Manager not saving OpenVPN password
This bug was fixed in the package network-manager - 1.20.4-2ubuntu2.2 --- network-manager (1.20.4-2ubuntu2.2) eoan; urgency=medium [ José Manuel Santamaría Lema ] * d/p/lp1858092-fix_updating_agent_vpn_secrets.patch: - fix VPN password storing (LP: #1858092) network-manager (1.20.4-2ubuntu2.1) eoan; urgency=medium * d/t/killswitches-no-urfkill, d/t/urfkill-integration, d/t/wpa-dhclient, d/t/nm.py, d/t/control: - skip tests on s390 due to missing wireless kernel support (LP: #1855009) - skip tests on i386 since there is no i386 kernel anymore, so we can't build our custom rfkill test module (LP: #1855183) -- Dan Streetman Wed, 08 Jan 2020 08:45:30 -0500 ** Changed in: network-manager (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1855009] Re: autopkgtests all fail on s390x
This bug was fixed in the package network-manager - 1.20.4-2ubuntu2.2 --- network-manager (1.20.4-2ubuntu2.2) eoan; urgency=medium [ José Manuel Santamaría Lema ] * d/p/lp1858092-fix_updating_agent_vpn_secrets.patch: - fix VPN password storing (LP: #1858092) network-manager (1.20.4-2ubuntu2.1) eoan; urgency=medium * d/t/killswitches-no-urfkill, d/t/urfkill-integration, d/t/wpa-dhclient, d/t/nm.py, d/t/control: - skip tests on s390 due to missing wireless kernel support (LP: #1855009) - skip tests on i386 since there is no i386 kernel anymore, so we can't build our custom rfkill test module (LP: #1855183) -- Dan Streetman Wed, 08 Jan 2020 08:45:30 -0500 ** Changed in: network-manager (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386
This bug was fixed in the package network-manager - 1.20.4-2ubuntu2.2 --- network-manager (1.20.4-2ubuntu2.2) eoan; urgency=medium [ José Manuel Santamaría Lema ] * d/p/lp1858092-fix_updating_agent_vpn_secrets.patch: - fix VPN password storing (LP: #1858092) network-manager (1.20.4-2ubuntu2.1) eoan; urgency=medium * d/t/killswitches-no-urfkill, d/t/urfkill-integration, d/t/wpa-dhclient, d/t/nm.py, d/t/control: - skip tests on s390 due to missing wireless kernel support (LP: #1855009) - skip tests on i386 since there is no i386 kernel anymore, so we can't build our custom rfkill test module (LP: #1855183) -- Dan Streetman Wed, 08 Jan 2020 08:45:30 -0500 ** Changed in: network-manager (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+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 1862852] [NEW] lubuntu loads slow and browser cannot handle multiple windows
Public bug reported: lubuntu loads slow and browser cannot handle multiple windows ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Tue Feb 11 17:57:15 2020 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:01fe] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01fe] InstallationDate: Installed on 2019-10-11 (123 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude D830 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=58532c64-b8c3-4274-99db-6d3cc2aa0f7d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0HN341 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/19/2013:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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 disco third-party-packages 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/1862852 Title: lubuntu loads slow and browser cannot handle multiple windows Status in xorg package in Ubuntu: New Bug description: lubuntu loads slow and browser cannot handle multiple windows ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Tue Feb 11 17:57:15 2020 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:01fe] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01fe] InstallationDate: Installed on 2019-10-11 (123 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Latitude D830 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=58532c64-b8c3-4274-99db-6d3cc2aa0f7d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0HN341 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/19/2013:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git2002011830.5c8ff5~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1855183] Update Released
The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+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 1855009] Update Released
The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+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 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
This bug is not duplicate, or the 'duplicate' is private. Please address. ** This bug is no longer a duplicate of private bug 1671487 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1838948 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. Status in eog package in Ubuntu: Confirmed Bug description: I opened an image. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AssertionMessage: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. CurrentDesktop: ubuntu:GNOME Date: Mon Jul 29 16:22:00 2019 ExecutablePath: /usr/bin/eog ExecutableTimestamp: 1523677004 InstallationDate: Installed on 2017-03-13 (874 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: eog /home/mircea/Downloads/IMG_20190410_143513.jpg ProcCwd: /home/mircea Signal: 6 SourcePackage: eog StacktraceTop: __assert_fail_base (fmt=0x7fac8c9d47d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fac8c0ce9a9 "*ptr != NULL", file=file@entry=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=line@entry=619, function=function@entry=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:92 __GI___assert_fail (assertion=0x7fac8c0ce9a9 "*ptr != NULL", file=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=619, function=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. UpgradeStatus: Upgraded to bionic on 2018-08-24 (345 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1838948/+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 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: eog (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1838948 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. Status in eog package in Ubuntu: Confirmed Bug description: I opened an image. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AssertionMessage: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. CurrentDesktop: ubuntu:GNOME Date: Mon Jul 29 16:22:00 2019 ExecutablePath: /usr/bin/eog ExecutableTimestamp: 1523677004 InstallationDate: Installed on 2017-03-13 (874 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: eog /home/mircea/Downloads/IMG_20190410_143513.jpg ProcCwd: /home/mircea Signal: 6 SourcePackage: eog StacktraceTop: __assert_fail_base (fmt=0x7fac8c9d47d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fac8c0ce9a9 "*ptr != NULL", file=file@entry=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=line@entry=619, function=function@entry=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:92 __GI___assert_fail (assertion=0x7fac8c0ce9a9 "*ptr != NULL", file=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=619, function=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. UpgradeStatus: Upgraded to bionic on 2018-08-24 (345 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1838948/+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 1858092] Update Released
The verification of the Stable Release Update for network-manager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1851807] Re: xdg-desktop-portal-gtk spams logs
This bug was fixed in the package xdg-desktop-portal - 1.4.2-2ubuntu1 --- xdg-desktop-portal (1.4.2-2ubuntu1) eoan; urgency=medium * d/p/background-Don-t-spam-the-logs.patch - Only warn once if we don't find the shell api (LP: #1851807) -- Ken VanDine Wed, 08 Jan 2020 09:26:04 -0500 ** Changed in: xdg-desktop-portal (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1851807 Title: xdg-desktop-portal-gtk spams logs Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Eoan: Fix Released Bug description: Every minute I get a log entry that looks like > xdg-desktop-por[ ]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error: org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Upstream bug-report: https://github.com/flatpak/xdg-desktop-portal- gtk/issues/222 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xdg-desktop-portal-gtk 1.4.0-2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 10:51:30 2019 InstallationDate: Installed on 2019-11-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: xdg-desktop-portal-gtk UpgradeStatus: No upgrade log present (probably fresh install) [Impact] * Continual spamming of the syslog [Test Case] * Reboot after installing the update * grep org.freedesktop.portal.Error.Failed /var/log/syslog - You should only see the error logged once since your most recent login [Regression Potential] * Regressions are very unlikely for this change, it just suppresses the logging of this one error condition more than once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1851807/+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 1851807] Update Released
The verification of the Stable Release Update for xdg-desktop-portal has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1851807 Title: xdg-desktop-portal-gtk spams logs Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Eoan: Fix Released Bug description: Every minute I get a log entry that looks like > xdg-desktop-por[ ]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error: org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Upstream bug-report: https://github.com/flatpak/xdg-desktop-portal- gtk/issues/222 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xdg-desktop-portal-gtk 1.4.0-2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 10:51:30 2019 InstallationDate: Installed on 2019-11-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: xdg-desktop-portal-gtk UpgradeStatus: No upgrade log present (probably fresh install) [Impact] * Continual spamming of the syslog [Test Case] * Reboot after installing the update * grep org.freedesktop.portal.Error.Failed /var/log/syslog - You should only see the error logged once since your most recent login [Regression Potential] * Regressions are very unlikely for this change, it just suppresses the logging of this one error condition more than once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1851807/+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 1849773] Update Released
The verification of the Stable Release Update for poppler has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Eoan: Fix Released Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+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 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
This bug was fixed in the package poppler - 0.80.0-0ubuntu1.1 --- poppler (0.80.0-0ubuntu1.1) eoan; urgency=medium * Fix null pointer dereference when checking for glyphless font, thanks to Enrik Berkhan (LP: #1849773) -- Julian Andres Klode Mon, 16 Dec 2019 21:41:17 +0100 ** Changed in: poppler (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection Status in poppler package in Ubuntu: Fix Released Status in poppler source package in Eoan: Fix Released Bug description: [Impact] Selecting text in evince crashes for some files in eoan [Test case] Open the pdf in bug 1855596 and select some text. [Regression potential] This adds a check for a null pointer before using the pointer; it's limited to a small function checking if a font is glyphless so there is basically no risk for regressio [Error tracker] The Ubuntu Error Tracker has been receiving reports about a problem regarding evince. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+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 1859643] Re: [snap] cannot use shared NSS db
OTOH, I think it makes sense to allow for the ability to share ~/.pki/nssdb (and yes, a personal-files addition along with a snap change (perhaps just a symlink from $SNAP_USER_DATA/.pki/nssdb to ~/.pki/nssdb would be enough rather than patching?). For read access, I have no problem with using personal-files to read the nssdb into $SNAP_USER_DATA, with auto-connection. For write, chromium is not the clear owner of this directory, so I would be hesitant to recommend it as a default since IMO, chromium shouldn't be writing out to these files even in non-snap situations (again, perfectly reasonable to merge in changes if the user desires). I for one would be rather surprised to install a certificate via chromium and have it reflected in my session-wide nssdb for another application (eg, libvirt). Furthermore, there is nothing saying that nssdb might not change format incompatibly with nss in the chromium snap and software installed on the system. This is not theoretical: rather than using a single nssdb in the user's global ~/.pki/nssdb dir, firefox, for example, instead stores per-profile certN.db files in ~/.mozilla/firefox//* and in my profile dirs I have a mixture of cert8.db and cert9.db. I do see that chromium only has cert9.db, so perhaps this is handled by the library itself (again, someone would need to verify), but then there is nssdb skew if some applications are writing to certN-1.db, some to certN.db and others to certN+1.db. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1859643 Title: [snap] cannot use shared NSS db Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://askubuntu.com/questions/1202861 /chromium-does-not-show-certificates-from-pki-nssdb) Chromium can theoretically use the shared NSS db at ~/.pki/nssdb, but the snap confinement prevents it from actually using the shared db (it reads and writes to $SNAP/.pki/nssdb instead). Shared certificates can be inspected by browsing to chrome://settings/certificates. Really accessing the shared db would require an additional read/write personal-files plug on $HOME/.pki/nssdb, and patching GetDefaultConfigDirectory() in crypto/nss_util.cc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1859643/+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 1835644] Re: CRL files are not accessible for the Verify CRL options
the problem persists on Ubuntu 19.10: nm-openvpn[2459]: Options error: --crl-verify fails with '/var/lib/openvpn/chroot//etc/openvpn/crl.pem': No such file or directory (errno=2) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1835644 Title: CRL files are not accessible for the Verify CRL options Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Hello, The Network Manager GUI options 'Verify CRL from file' and 'Verify CRL from directory' won't work because the openvpn process cannot access the files since being run with chroot, so the connection fails: nm-openvpn[5069]: chroot to '/var/lib/openvpn/chroot' and cd to '/' succeeded nm-openvpn[6135]: Options error: --crl-verify fails with '/var/lib/openvpn/chroot//home/steve/VPN/config/crl.rsa.4096.pem': No such file or directory (errno=2) Thanks. Ubuntu 19.04 network-manager-openvpn, network-manager-openvpn-gnome 1.8.10-1 openvpn 2.4.6-1ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1835644/+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 1862843] [NEW] chromium crashes when it starts
Public bug reported: Ubuntu Eoan with KDE desktop, full updated. Since today, when I start chromium, doesn't appear any window. If I start it on terminal, I read this: $ chromium-browser internal error, please report: running "chromium" failed: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml I reinstalled snap packages but no changes. Infact, in chromium's snap folder there is nothing: $ ll /snap/chromium/current/ totale 0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAQrHugUzZVNDAXAQSlNCB4Ou6Vo1RMmSYPUFShCACBQIGAqUCzANHAAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wAwRkZYRDNCUzRVNlMK/ABERUxMIFUyNDEyTQog/QAyPR5TEQAKICAgICAgAHk= modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x960 1024x768 800x600 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAVwzEYAQEBARkSAQOAJh546uQVo1RKmyUTUFShCACBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/wBWNzk0NzA2OAogICAg/QA7PR9ACwAKICAgICAg/ABTMTkyMQogICAgICAgAOg= modes: 1280x1024 1024x768 800x600 640x480 720x400 Date: Tue Feb 11 22:44:13 2020 DiskUsage: File systemTipo Dim. Usati Dispon. Uso% Montato su /dev/nvme0n1p3 ext4 177G 87G 82G 52% /home tmpfs tmpfs 7,8G 140M7,7G 2% /dev/shm /dev/nvme0n1p3 ext4 177G 87G 82G 52% /home InstallationDate: Installed on 2019-01-30 (377 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=7164fc7a-333a-4530-8355-d7af8a4933a3 ro quiet splash vt.handoff=7 Snap.Changes: ID Status Spawn Ready Summary 7Done2020-02-11T21:23:03+01:00 2020-02-11T21:23:03+01:00 Connect chromium:password-manager-service to snapd:password-manager-service Snap.ChromeDriverVersion: Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed with exit code 1: error: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 1: error: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2020-02-05 (6 days ago) dmi.bios.date: 09/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd09/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1862843 Title: chromium crashes when it starts Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu Eoan with KDE desktop, full updated. Since today, when I start chromium, doesn't appear any window. If I start it on terminal, I read this: $ chromium-browser internal error, please report: running "chromium" failed: cannot find installed snap "chromium" at revision 1016: missing file /snap/chromium/1016/meta/snap.yaml I reinstalled snap packages but no changes. Infact, in chromium's snap folder there is nothing: $ ll /snap/chromium/current/ totale 0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64:
[Desktop-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
BT device is in the wrong mode / on the wrong profile. Solution is here: https://askubuntu.com/questions/889737/video-not- playing-in-web-browser-with-bluetooth-headphones-connected-how-can-i wget https://gist.github.com/pylover/d68be364adac5f946887b85e6ed6e7ae/archive/d698974910bbb7d016ec0ad08c1bf41b4b524364.zip unzip d698974910bbb7d016ec0ad08c1bf41b4b524364.zip in there is a a2dp.py chmod +x a2dp.py Run the file (modify python3.5 to python3 if needed in the first line) when you have the device connected. Choose it from the list. It changes the profile, now everything works, the video is also running. What the reason is, I cant tell, but I can tell you that this solves it -- 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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2
This is why it is important to upstream the bugs and find the root cause. -- 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/1032456 Title: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2 Status in cups package in Ubuntu: Fix Released Status in cups source package in Precise: Fix Released Bug description: My Canon i560 was working fine until the update two days ago. Now it fails every single job, printing half a page and then ejecting the page when a USB reset is issued. Same printer works fine when printing through Windows in Virtualbox with USB passthrough. Summary: the USB backend "improvements" have rendered my printer useless with CUPS. Unloading the usblp module makes no difference - the USB reset is what aborts the print job. [ 224.008042] usb 3-1: reset full-speed USB device number 3 using uhci_hcd [ 224.161701] usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04A9 pid 0x108 Kubuntu 12.04 [IMPACT] Everyone with a Canon inkjet connected to USB and also users of some other printer models on USB get printouts with the last page being incomplete. This happens for every job. For everyone with a Samsung printer the problem of bug 995111 shows up again. [TESTCASE] Unfortunately, for reproducing this bug one needs the actual hardware. Connect a Canon inkjet (or other models mentioned in this bug report) to the USB and print from a completely updated Precise system. The last page of each job will come out incomplete. Connect a Samsung printer to the USB and print from a completely updated Precise system. You will get printouts with weird characters (at least from the second job on) as described in bug 995111. After installing the proposed package all these problems should disappear. [Regression Potential] Regression risk is very low. The fix is not doing the USB device reset on the printer after the job for most printers. The fix contains an exception rule for Samsung printers and Prolific Technology USB->Parallel adapters, to avoid reoccurring of bug 987485 and bug 997040. It is still possible that some printers are treated incorrectly in terms of whether they need a reset after the job or not. As most printers work both with and without reset this risk is very low. All reported problems are solved with the proposed fix. *** dpkg -l "*cups*"|grep ii ii bluez-cups 4.98-2ubuntu7 Bluetooth printer driver for CUPS ii cups 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - server ii cups-bsd 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - BSD commands ii cups-client 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - client programs (SysV) ii cups-common 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - common files ii cups-filters 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters ii cups-ppdc 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - PPD manipulation utilities ii ghostscript-cups 9.05~dfsg-0ubuntu4.1 interpreter for the PostScript language and for PDF - CUPS filters ii libcups2 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Core library ii libcupscgi1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - CGI library ii libcupsdriver1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Driver library ii libcupsfilters1 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters - Shared library ii libcupsimage2 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Raster image library ii libcupsmime1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - MIME library ii libcupsppdc1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - PPD manipulation library
[Desktop-packages] [Bug 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2
I can confirm that the bug is still present in the Ubuntu 18.04.4 LTS for my Canon MX300 An yes, the command sudo lpadmin -p MX300 -o usb-unidir-default=true seolves the problem. -- 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/1032456 Title: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2 Status in cups package in Ubuntu: Fix Released Status in cups source package in Precise: Fix Released Bug description: My Canon i560 was working fine until the update two days ago. Now it fails every single job, printing half a page and then ejecting the page when a USB reset is issued. Same printer works fine when printing through Windows in Virtualbox with USB passthrough. Summary: the USB backend "improvements" have rendered my printer useless with CUPS. Unloading the usblp module makes no difference - the USB reset is what aborts the print job. [ 224.008042] usb 3-1: reset full-speed USB device number 3 using uhci_hcd [ 224.161701] usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04A9 pid 0x108 Kubuntu 12.04 [IMPACT] Everyone with a Canon inkjet connected to USB and also users of some other printer models on USB get printouts with the last page being incomplete. This happens for every job. For everyone with a Samsung printer the problem of bug 995111 shows up again. [TESTCASE] Unfortunately, for reproducing this bug one needs the actual hardware. Connect a Canon inkjet (or other models mentioned in this bug report) to the USB and print from a completely updated Precise system. The last page of each job will come out incomplete. Connect a Samsung printer to the USB and print from a completely updated Precise system. You will get printouts with weird characters (at least from the second job on) as described in bug 995111. After installing the proposed package all these problems should disappear. [Regression Potential] Regression risk is very low. The fix is not doing the USB device reset on the printer after the job for most printers. The fix contains an exception rule for Samsung printers and Prolific Technology USB->Parallel adapters, to avoid reoccurring of bug 987485 and bug 997040. It is still possible that some printers are treated incorrectly in terms of whether they need a reset after the job or not. As most printers work both with and without reset this risk is very low. All reported problems are solved with the proposed fix. *** dpkg -l "*cups*"|grep ii ii bluez-cups 4.98-2ubuntu7 Bluetooth printer driver for CUPS ii cups 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - server ii cups-bsd 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - BSD commands ii cups-client 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - client programs (SysV) ii cups-common 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - common files ii cups-filters 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters ii cups-ppdc 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - PPD manipulation utilities ii ghostscript-cups 9.05~dfsg-0ubuntu4.1 interpreter for the PostScript language and for PDF - CUPS filters ii libcups2 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Core library ii libcupscgi1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - CGI library ii libcupsdriver1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Driver library ii libcupsfilters1 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters - Shared library ii libcupsimage2 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Raster image library ii libcupsmime1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - MIME library ii libcupsppdc1
[Desktop-packages] [Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
Hello,
in view of the above-mentioned post, it seems to me that the problem is not
fully solved and therefore I will describe my findings. Today I tried to set up
my small server backup to a second using duplicity package. I used some example
for writing tiny script.
#!/bin/bash
export PASSPHRASE=some_pwd
export FTP_PASSWORD=some_ftp_pwd
duplicity ~/SQLBACKUP ftp://some_user@10.0.0.250/SQLBACKUP
unset PASSPHRASE
unset FTP_PASSWORD
When I ran the script, I got the errors listed above, but a directory
SQLBACKUP was created on the target server. The permissions of this
directory were okay (some similar bug), so I tried to run the script a
second time and the backup went without errors. Other backups were
already running without errors too. In my opinion, the problem may be
that it fails to create a backup directory on the target server fast
enough. As a target server I used ftp server on Windows once and second
ftp server on Ubuntu 18.04 and the result was always the same
(physically three machines on network: one with duplicity and two ftp
servers). When I prepared SQLBACKUP directory on the target server
manually, the backup went without errors too.
machine with duplicity:
---
Ubuntu 18.04.4 LTS
Python 2.7.17
duplicity 0.7.17 (from Ubuntu repository)
lftp version 4.8.1
Perhaps a small loop in the depths of duplicity package, that tests whether a
directory has already been created, would help :-).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
Fix Released
Bug description:
backup worked under Ubuntu 17.10
It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
my drive is encrypted
this is the error message in the error frame
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 09:55:00 2018
InstallationDate: Installed on 2018-05-01 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
Same problem on Ubuntu 18.04 - thankfully edelans posted a fix in #19 for removing the message! -- 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/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) Status in HPLIP: Confirmed Status in hplip package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Install hplip-gui 3. Launch GNOME session. 4. Get error message window with header "HPLIP Status Service" and text "No system tray detected on this system. Unable to start, exiting." Expected results: hp-systray is compatible with modern GNOME Actual results: hp-systray is not compatible with modern GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 (dbus://) went away, retrying! CurrentDesktop: GNOME Date: Sat Sep 2 14:10:19 2017 InstallationDate: Installed on 2017-08-26 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. UX32A PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+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 1862281] Re: Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse
I've installed weston, run telinit 3, and from the terminal run weston-
launch. 20 minutes of moving the mouse later, this appears to be stable
(just as gpm in a console after booting into runlevel 3 is).
--
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/1862281
Title:
Repeatable hang within 5 minutes using stress-ng + sleep + usb mouse
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
If I run a thermal transition test script (30 seconds stress-ng, 30
seconds sleep, in a loop) and move a local USB mouse, Kubuntu reliably
crashes, usually in the first couple of runs and almost 100% of the
time by run 6.
This appears to be hardware-linked, but not due to a specific piece of
bad hardware: I have swapped literally every piece of hardware in the
system.
It shows up (while running the script at the end):
- On both an MSI B450 Gaming plus max and MSI MPG X570 Gaming plus mainboard.
- On both an AMD Ryzen 5 3600 and 3600X CPU.
- With one or two sticks of RAM. I've tested both sticks individually, in
more than one mainboard slot.
- Regardless of whether the mainboard is in/attached to a case.
- Regardless of whether there is an m.2 SSD installed or I'm running off a
live Kubuntu 19.10 USB stick with no hard disk attached.
- Regardless of which of two mice I use (an old Logitech one, or a GTX 133
Gaming mouse).
- Regardless of whether I'm using a Corsair VS650 or Corsair AX850 PSU.
- Regardless of whether I'm using an AMD RX 5700 XT or using an Nvidia
Gigabyte GeForce RTX 2700 Super (with open source drivers in both cases).
- Regardless of whether I'm using KDE or XFCE.
- Regardless of whether I'm using the default KDE DM or switch to GDM3 and
set WaylandEnable=false.
- Regardless of whether I use the default 5.3.0-29-generic kernel or
5.4.17-050417-generic.
- Regardless of whether I go directly into the graphical environment or start
in runlevel 3 and then manually run startx.
- Regardless of whether it's on the rising or falling edge of the
stress-script's temperature changes.
- Regardless of bios version on the X570 mainboard (the one it shipped with,
or the newest one released in January 2020).
- Regardless of whether XMP is on or off in the bios.
- Regardless of whether I use the default or set global c-state to "control =
disabled" in the bios.
- Regardless of whether I add processor.max_cstate=5 idle=halt in grub.
- Regardless of whether or not speakers are plugged in.
- Regardless of whether I'm using a USB port that is directly on the
motherboard or is on the front of the case.
- Regardless of which monitor it is attached to.
It doesn't show up:
- On an old i7-4771 machine I have, also running Kubuntu 19.10, while running
the test script.
- When I use a mouse remotely with ssh -Y [ip of the machine I am reporting
this from] xeyes, while running the test script.
- When I do non-mouse USB input, ie via a USB keyboard or USB wifi dongle,
including under saturated network load, while running the test script.
- During stress tests of the GPU, CPU, etc. Tools like memtest, mprime,
Unigine Superposition, repeated kernel compiles, etc run stably overnight.
- When the system is entirely idle aside from mouse movement.
- When I start in runlevel 3 and run the same test script, using the mouse
with gpm.
- Running the same test script without mouse movement: this was stable
overnight, then crashed within a couple of minutes of moving the mouse.
It shows up with load other than the stress-ng+sleep script too, but
much less reliably - I'm writing this bug report on the relevant
machine, with firefox open. Crashes occur at least once a week under
these conditions, but not frequently.
Crashes occur with sensor-reported CPU temperatures of 32 to 41
degrees Celsius. Nothing is overheating, and the system is stable at
much higher temperatures under sustained stress tests.
The symptoms of the crash: the display stops updating and the system
does not respond to any further input, including via the network or
magic sysrq key. There is nothing related to it in syslog or
journalctl, including when I'm running journalctl -f at the time of
the crash.
The test script:
#!/bin/bash
for x in {1..1}
do
echo "Run $x at `date`"
stress-ng --cpu 12 --cpu-method all --verify -t 30s --metrics-brief
sleep 30
done
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
Uname: Linux 5.4.17-050417-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Fri Feb 7 00:02:22 2020
DistUpgraded: Fresh install
DistroCodename: eoan
[Desktop-packages] [Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
nonetheless I do not experience the core issue (screensaver activating, and the unability to temporarily disable it while an mpv playback is running) alias mpv='mpv--no-audio-display --volume-max=132 --cache-secs=120 --alang=hu' No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan up-to-date -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: New Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Hi Nivedita, I have been away on PTO the last week and am picking this up again now. Please could you post the full bonding configuration? Regards, Edwin Peer -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting information on this link to try determine the problem:
[Desktop-packages] [Bug 1862135] Re: [snap] Chromium 80 window border artifacts while using chromium's title bar and borders
Chromium in Ubuntu session (Xorg) is also affected. Screenshot attached. ** Attachment added: "Screenshot from 2020-02-11 19-26-22.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862135/+attachment/5327396/+files/Screenshot%20from%202020-02-11%2019-26-22.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1862135 Title: [snap] Chromium 80 window border artifacts while using chromium's title bar and borders Status in chromium-browser package in Ubuntu: New Bug description: FIX: It can be fixed by switching to system title bar and borders and back to chromium's. I'm using Wayland, Ubuntu 19.10, Chromium 80.0.3987.87 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862135/+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 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
List of some mpv issues with gnome wayland, the window deco is somewhat mitigated by the new osc overlay that will, by default show in the absence of window deco. https://github.com/mpv-player/mpv/wiki/FAQ#i-use-gnome-wayland-and-i-have-xyz-problem -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: New Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+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 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
On 2/11/20 11:16 AM, Imre Péntek wrote: > as far as I can tell this bug is not present in 19.10 (fixed) > No, clearly never fixed and still an issue in 20.04. Only way around is for user from cli to use gnome-session-inhibit mpv /path/to/file -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: New Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+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 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el
This bug was fixed in the package ghostscript - 9.50~dfsg-5ubuntu1 --- ghostscript (9.50~dfsg-5ubuntu1) focal; urgency=medium * Re-introduced exception rule for building with only -O2 instead of -O3 on ppc64el (see also LP: #1862053). -- Till Kamppeter Fri, 7 Feb 2020 19:09:58 +0100 ** Changed in: ghostscript (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1862053 Title: Compiler gets stuck (or extremely slow) on ppc64el Status in gcc: New Status in gcc package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Fix Released Bug description: I have uploaded Ghostscript 9.50 to focal and it built without any problem on all architectures but ppc64el. On ppc64el the compiler seems to get stuck (or extremely slow) on one of the files of Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to the build process being killed after 150 minutes. See https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407 and https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal- ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1862053/+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 1860830] Re: Geolocation not working − the Google maps API always returns error codes
73.0b12 (64-bit) Has the same bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1860830 Title: Geolocation not working − the Google maps API always returns error codes Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Happened as soon as Firefox was updated to 72.0.1. I noticed sites could not determine my location. Troubleshooting page shows "missing" under Location service key. I have another computer running Lubuntu 18.04LTS, which I rarely use. Just for fun, I booted it up and as soon as the software updater updated Firefox to 72.0.1, location stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 72.0.1+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 2125 F pulseaudio /dev/snd/controlC1: frank 2125 F pulseaudio BuildID: 20200107212822 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 19:58:30 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-82fc5472-37b3-46d6-a6fa-f47e11180406 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=72.0.1/20200107212822 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2019-07-05 (203 days ago) dmi.bios.date: 03/24/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.27 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1442 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.27:bd03/24/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr048D10242B202:rvnHewlett-Packard:rn1442:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 048D10242B202 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860830/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)
Please test kernel parameter "snd_hda_intel.model=inv-dmic". -- 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/1850702 Title: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows) Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P02REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version:
[Desktop-packages] [Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
note to self: check my home ubuntu if I have any alias set for mpv -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: New Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+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 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
as far as I can tell this bug is not present in 19.10 (fixed) -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: New Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+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 1799073] Re: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10
This is fixed in Ubuntu 20.04 -- 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/1799073 Title: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi all. I noticed this problem when I upgraded from 18.04 to 18.04.1 (Worked perfectly in stock 18.04) and then I was testing the 18.10 beta and hoped it would be fixed there but it's not. To reproduce: login to the regular Ubuntu desktop, hit Super+Alt+= (You can validate that your keyboard shortcut is set to the default in Settings->Keyboard.) I also tried changing the keyboard mapping for this action in case there was a conflict, and no matter what I set it to I couldn't zoom from the keyboard. As a partially blind user, this is a show stopper for me - I require screen zoom to be able to use Ubuntu at all for any serious work. Thanks for everything you do! -Chris (Happy to try any work-arounds or testing people can think up to help fix this problem) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2018-10-07 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Package: gnome-shell 3.30.1-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799073/+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 1862707] Re: LibreOffice Snap (6.4.0.3; 2/10/2020) can't open documents from ".hidden" directories
Thanks for reporting your issue with the libreoffice snap. Unfortunately, snaps are restricted from accessing files in hidden folders because this is often where other applications keep their configuration files. If you still need to access these files with libreoffice, you should use the libreoffice installed from apt, rather than the snap, as this should work just fine. ** Changed in: libreoffice (Ubuntu) Status: New => Won't Fix -- 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/1862707 Title: LibreOffice Snap (6.4.0.3; 2/10/2020) can't open documents from ".hidden" directories Status in libreoffice package in Ubuntu: Won't Fix Bug description: When in Nautilus, trying to open (double-clicking) any file associated with LibreOffice generates this error: "Access to /home/MyName/.LevelOne/Reports/2020-01-01_Report.xls File .xls was denied." The same behavior happens if you already have a Libre app (Calc, Writer, etc.) running, and try to use the Open file dialog. This occurs even though Tools-> Options-> General-> "Use Libre Dialogs" is unchecked. (Also, of course, Nautilus Show Hidden Files option on.) All file/dir owner:group permissions were checked and are user level (not owned by root:root). Renaming all directories in the file path to remove the leading dot (.) allows the files to open normally and Libre works as expected. (Unfortunately, there about 175 files/directories I'm working on.) LibreOffice was installed through official Ubuntu Software Store - Canonical (LibreOffice Snap Store (6.4.0.3; 2/10/2020). = System Info: $ lsb_release -rd Description: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92) Release: 18.04 - $ apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:6.0.7-0ubuntu0.18.04.10 Version table: 1:6.0.7-0ubuntu0.18.04.10 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 1:6.0.3-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862707/+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 1862772] Re: failed
** Package changed: ubuntu => xorg (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/1862772 Title: failed Status in xorg package in Ubuntu: New Bug description: do not understand / it is my fault cheers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 11 11:55:28 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-01-04 (37 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2P ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=ae2a0258-72f7-48c3-a597-3bc06c85e35a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Feb 11 11:40:11 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft Basic Optical Mouse MOUSE, id 8 inputLITEON Technology USB Keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862772/+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 1862792] [NEW] gnome-shell always crash after boot
Public bug reported: gnome-shell always crash after boot with an UnreportableReason. This is in a Wayland session. There are no stability issues after boot. I get this information in the terminal after the command ubuntu-bug p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell p-i@pi-asus-b450f-gaming:~$ [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! ERROR:gl goes from 1 to 19. In Settings the Display is named Microstep 27" The problem might be hardware related: Mobo: ASUSTeK model: ROG STRIX B450-F GAMING GPU: AMD Navi 10 Radeon RX 5700 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 16:43:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-08 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1862792 Title: gnome-shell always crash after boot Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell always crash after boot with an UnreportableReason. This is in a Wayland session. There are no stability issues after boot. I get this information in the terminal after the command ubuntu-bug p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell p-i@pi-asus-b450f-gaming:~$ [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! ERROR:gl goes from 1 to 19. In Settings the Display is named Microstep 27" The problem might be hardware related: Mobo: ASUSTeK model: ROG STRIX B450-F GAMING GPU: AMD Navi 10 Radeon RX 5700 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 16:43:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-08 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/1862792/+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 1563110]
World Vision India is focused on exclusive expectations of responsibility and straightforwardness which is a statement of our guiding principle on ''how to sponsor a child in another country”. This is on the grounds that we intensely accept that we work successfully for the prosperity of kids. World Vision India ceaselessly endeavors to keep up high national and global models of expert capability and is responsible through proper structures for accomplishing these norms. https://www.worldvision.in -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Fix Released Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1862772] [NEW] failed
You have been subscribed to a public bug: do not understand / it is my fault cheers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 11 11:55:28 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-01-04 (37 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2P ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=ae2a0258-72f7-48c3-a597-3bc06c85e35a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Feb 11 11:40:11 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft Basic Optical Mouse MOUSE, id 8 inputLITEON Technology USB Keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 ubuntu -- failed https://bugs.launchpad.net/bugs/1862772 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1781597] Re: [SRU] WoWLAN settings are not supported
It looks like the VPN related SRU that was previous to this one was reverted. Could we land this into bionic? -- 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/1781597 Title: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Triaged Status in network-manager source package in Cosmic: Fix Released Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+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 1862048] Re: [MIR] fonts-urw-base35
@didrocks, this upload already happened, it is 9.50~dfsg-5ubuntu1. ** Changed in: ghostscript (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-urw-base35 in Ubuntu. https://bugs.launchpad.net/bugs/1862048 Title: [MIR] fonts-urw-base35 Status in fonts-urw-base35 package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Fix Released Bug description: Availability: The package is in Universe and it has no known build issues in the curremt version. It is a pure data package without any executable code inside and so nothing to compile. Therefore it is architecture independent. Rationale: This package is needed by the current Debian package of Ghostscript (9.50) which I have synced into Ubuntu. Security: As this package does not contain executable code (it contains only fonts and therefore only data) there should be no security risk being introduced by it. Quality assurance: There is no user interaction required to use this package. It will get pulled in by Ghostscript via dependency and provide the 35 PostScript standard fonts needed by Ghostscript. It comes with all needed metadata and configuration files so that Ghostscript actually finds the fonts. As this is only a font collection there is no user interface. The package also does not contain any debconf questions. The upstream package comes from Artifex, the upstream maintainers Ghostscript. Therefore it should be as well maintained as Ghostscript itself. There are regularly happening updates at Debian and Ubuntu simply auto-syncs. The package has no test suite, but it is nothing more than a collection of fonts. debian/watch is present. This package does not depend on any other package, so it cannot pull in anything deprecated or from Universe. Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain. Maintenance: The Ubuntu Printing Team is subscribed to bug reports on this package. As mentioned earlier this package is auto-synced from Debian and there well maintained. Currently there are no open bugs. Background information: The package is well described in its description. Security checks No known CVE entries, but as this package contains only fonts we do not expect any vulnerabilities. No executables, so also no SUID/GUID, daemons, startup scripts, port bindings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1862048/+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 1862048] Re: [MIR] fonts-urw-base35
Override component to main fonts-urw-base35 20170801.1-3 in focal: universe/misc -> main fonts-urw-base35 20170801.1-3 in focal amd64: universe/fonts/optional/100% -> main fonts-urw-base35 20170801.1-3 in focal arm64: universe/fonts/optional/100% -> main fonts-urw-base35 20170801.1-3 in focal armhf: universe/fonts/optional/100% -> main fonts-urw-base35 20170801.1-3 in focal i386: universe/fonts/optional/100% -> main fonts-urw-base35 20170801.1-3 in focal ppc64el: universe/fonts/optional/100% -> main fonts-urw-base35 20170801.1-3 in focal s390x: universe/fonts/optional/100% -> main 7 publications overridden. ** Changed in: fonts-urw-base35 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1862048 Title: [MIR] fonts-urw-base35 Status in fonts-urw-base35 package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Fix Committed Bug description: Availability: The package is in Universe and it has no known build issues in the curremt version. It is a pure data package without any executable code inside and so nothing to compile. Therefore it is architecture independent. Rationale: This package is needed by the current Debian package of Ghostscript (9.50) which I have synced into Ubuntu. Security: As this package does not contain executable code (it contains only fonts and therefore only data) there should be no security risk being introduced by it. Quality assurance: There is no user interaction required to use this package. It will get pulled in by Ghostscript via dependency and provide the 35 PostScript standard fonts needed by Ghostscript. It comes with all needed metadata and configuration files so that Ghostscript actually finds the fonts. As this is only a font collection there is no user interface. The package also does not contain any debconf questions. The upstream package comes from Artifex, the upstream maintainers Ghostscript. Therefore it should be as well maintained as Ghostscript itself. There are regularly happening updates at Debian and Ubuntu simply auto-syncs. The package has no test suite, but it is nothing more than a collection of fonts. debian/watch is present. This package does not depend on any other package, so it cannot pull in anything deprecated or from Universe. Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain. Maintenance: The Ubuntu Printing Team is subscribed to bug reports on this package. As mentioned earlier this package is auto-synced from Debian and there well maintained. Currently there are no open bugs. Background information: The package is well described in its description. Security checks No known CVE entries, but as this package contains only fonts we do not expect any vulnerabilities. No executables, so also no SUID/GUID, daemons, startup scripts, port bindings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1862048/+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 1862048] Re: [MIR] fonts-urw-base35
Promotion done. Till, as ghostscript doesn’t need any promotion if I‘m correct, I let you close the bug in the changelog for your corresponding ghostscript upload. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1862048 Title: [MIR] fonts-urw-base35 Status in fonts-urw-base35 package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Fix Committed Bug description: Availability: The package is in Universe and it has no known build issues in the curremt version. It is a pure data package without any executable code inside and so nothing to compile. Therefore it is architecture independent. Rationale: This package is needed by the current Debian package of Ghostscript (9.50) which I have synced into Ubuntu. Security: As this package does not contain executable code (it contains only fonts and therefore only data) there should be no security risk being introduced by it. Quality assurance: There is no user interaction required to use this package. It will get pulled in by Ghostscript via dependency and provide the 35 PostScript standard fonts needed by Ghostscript. It comes with all needed metadata and configuration files so that Ghostscript actually finds the fonts. As this is only a font collection there is no user interface. The package also does not contain any debconf questions. The upstream package comes from Artifex, the upstream maintainers Ghostscript. Therefore it should be as well maintained as Ghostscript itself. There are regularly happening updates at Debian and Ubuntu simply auto-syncs. The package has no test suite, but it is nothing more than a collection of fonts. debian/watch is present. This package does not depend on any other package, so it cannot pull in anything deprecated or from Universe. Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain. Maintenance: The Ubuntu Printing Team is subscribed to bug reports on this package. As mentioned earlier this package is auto-synced from Debian and there well maintained. Currently there are no open bugs. Background information: The package is well described in its description. Security checks No known CVE entries, but as this package contains only fonts we do not expect any vulnerabilities. No executables, so also no SUID/GUID, daemons, startup scripts, port bindings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1862048/+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 1851936] Re: User profile won't load after upgrade - prompt to create new profile
hornetster, this is a bug specifically for Ubuntu, so it's unlikely
anyone reading it will be able to help you. I would suggest filing a
bug upstream, or perhaps asking a question in Stack Overflow (or
similar). Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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 1856014] Re: Extension enable/disable slider switch missing
** Changed in: gnome-software Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856014 Title: Extension enable/disable slider switch missing Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Triaged Bug description: 1) Ubuntu 19.10 2) 3.30.6-2ubuntu10.19.10.0 3) If I remember correctly, there was a slider switch in the top right corner of the extension settings window. 4) Extensions are not appearing on the top bar. Extensions appeared before and now they do not appear. I tried removing and reinstalling the extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1856014/+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 1862048] Re: [MIR] fonts-urw-base35
Subscription by Dektop team done, ready for promotion ** Changed in: fonts-urw-base35 (Ubuntu) Status: New => Fix Committed ** Changed in: fonts-urw-base35 (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => (unassigned) ** Changed in: ghostscript (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1862048 Title: [MIR] fonts-urw-base35 Status in fonts-urw-base35 package in Ubuntu: Fix Committed Status in ghostscript package in Ubuntu: Fix Committed Bug description: Availability: The package is in Universe and it has no known build issues in the curremt version. It is a pure data package without any executable code inside and so nothing to compile. Therefore it is architecture independent. Rationale: This package is needed by the current Debian package of Ghostscript (9.50) which I have synced into Ubuntu. Security: As this package does not contain executable code (it contains only fonts and therefore only data) there should be no security risk being introduced by it. Quality assurance: There is no user interaction required to use this package. It will get pulled in by Ghostscript via dependency and provide the 35 PostScript standard fonts needed by Ghostscript. It comes with all needed metadata and configuration files so that Ghostscript actually finds the fonts. As this is only a font collection there is no user interface. The package also does not contain any debconf questions. The upstream package comes from Artifex, the upstream maintainers Ghostscript. Therefore it should be as well maintained as Ghostscript itself. There are regularly happening updates at Debian and Ubuntu simply auto-syncs. The package has no test suite, but it is nothing more than a collection of fonts. debian/watch is present. This package does not depend on any other package, so it cannot pull in anything deprecated or from Universe. Standards compliance: The package should meet the FHS and Debian Policy standards. Major violations should be documented and justified. Also, the source packaging should be reasonably easy to understand and maintain. Maintenance: The Ubuntu Printing Team is subscribed to bug reports on this package. As mentioned earlier this package is auto-synced from Debian and there well maintained. Currently there are no open bugs. Background information: The package is well described in its description. Security checks No known CVE entries, but as this package contains only fonts we do not expect any vulnerabilities. No executables, so also no SUID/GUID, daemons, startup scripts, port bindings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-urw-base35/+bug/1862048/+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 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
I see this bug is still open. One work-around exists where ~/.ssh/config is used. Make an entry there for the host (or range of hosts using a pattern) and assign the right key using IdentityFile while also setting IdentitiesOnly to "yes". Both parts are needed for the work-around. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for Status in GNOME Keyring: Confirmed Status in gnome-keyring package in Ubuntu: Triaged Bug description: When trying to connect using ssh, I get this error: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for It appears that for some reason Lubuntu's agent somehow arbitrarily pulls in some keys and, despite not being asked to, tries to use them for authentication and won't let me try the password. If I list the keys in the agent (ssh-add -L) then it lists a bunch of public keys, none of which I put there, none of which should be there. If anything there should be private keys in the agent. If I remove the keys (ssh-add -D) then they are still there when I check again. Looking at the output for the server, it looks like it keeps trying keys until the max limit for failed logins is reached. The problem can be made to go away by uninstalling gnome-keyring and rebooting or by clearing ~/.ssh/ of keys. The problem can be created by adding 6 or more keys to ~/.ssh/ and then trying to connect with ssh, say to localhost. cd ~/.ssh/ ssh 127.0.0.1 ssh-keygen -P '' -f test_key_1 ssh-keygen -P '' -f test_key_2 ssh-keygen -P '' -f test_key_3 ssh-keygen -P '' -f test_key_4 ssh-keygen -P '' -f test_key_5 ssh 127.0.0.1 ssh-keygen -P '' -f test_key_6 ssh 127.0.0.1 rm test_key_6 ssh 127.0.0.1 I'm not sure if this is a security vulnerability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Sat Jun 29 00:52:05 2013 InstallationDate: Installed on 2013-06-21 (7 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64+mac (20130620) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1195911/+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 1862753] Re: Backport GPU hotplug RandR fix
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Triaged ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1862753 Title: Backport GPU hotplug RandR fix Status in xorg-server package in Ubuntu: Triaged Bug description: In order for the first DisplayLink device hotplug after reboot to be correctly acted on in GNOME, the following fix should be backported to all Xorg-server downstream branches that already apply the patch "xf86: autobind GPUs to the screen" (upstream 078277e4d92f05a90c4715d61b89b9d9d38d68ea): https://gitlab.freedesktop.org/xorg/xserver/merge_requests/326 The related upstream bug report fixed by this is https://gitlab.freedesktop.org/xorg/xserver/issues/909 I originally diagnosed the issue on Ubuntu 19.04 with Xorg based on the 1.20.4 upstream release. Upstream will not backport this patch into the stable 1.20 branch, because that branch does not carry "xf86: autobind GPUs to the screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862753/+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 1862767] Re: gnome-control-center crashes when try to open it
Strangely, purging nvidia drivers seems to fix the issue (following advice from https://askubuntu.com/a/1183137/44054). However, I had a different error as noted in the original bug description. However, now I can't have nvidia working with the settings. -- 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/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+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 1862767] [NEW] gnome-control-center crashes when try to open it
Public bug reported: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- 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/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+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 1754125] Re: Rhythmbox stays running in the background after quit
Paul, the "Stop & Quit" action is certainly a plus, but it doesn't solve this precise bug report, as there still is a case where "Rhythmbox stays running in the background after quit" (if you just close the window). I'm not the one to decide whether or not this is the desired behaviour, but I just think that the "Stop & Quit" action is only a workaround for this bug. -- 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/1754125 Title: Rhythmbox stays running in the background after quit Status in rhythmbox package in Ubuntu: Triaged Bug description: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
In KDE Neon 5.17.5 this bug exist as well... -- 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (2 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 1ea7:0066 Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.13 StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+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 1862753] [NEW] Backport GPU hotplug RandR fix
Public bug reported: In order for the first DisplayLink device hotplug after reboot to be correctly acted on in GNOME, the following fix should be backported to all Xorg-server downstream branches that already apply the patch "xf86: autobind GPUs to the screen" (upstream 078277e4d92f05a90c4715d61b89b9d9d38d68ea): https://gitlab.freedesktop.org/xorg/xserver/merge_requests/326 The related upstream bug report fixed by this is https://gitlab.freedesktop.org/xorg/xserver/issues/909 I originally diagnosed the issue on Ubuntu 19.04 with Xorg based on the 1.20.4 upstream release. Upstream will not backport this patch into the stable 1.20 branch, because that branch does not carry "xf86: autobind GPUs to the screen". ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1862753 Title: Backport GPU hotplug RandR fix Status in xorg package in Ubuntu: New Bug description: In order for the first DisplayLink device hotplug after reboot to be correctly acted on in GNOME, the following fix should be backported to all Xorg-server downstream branches that already apply the patch "xf86: autobind GPUs to the screen" (upstream 078277e4d92f05a90c4715d61b89b9d9d38d68ea): https://gitlab.freedesktop.org/xorg/xserver/merge_requests/326 The related upstream bug report fixed by this is https://gitlab.freedesktop.org/xorg/xserver/issues/909 I originally diagnosed the issue on Ubuntu 19.04 with Xorg based on the 1.20.4 upstream release. Upstream will not backport this patch into the stable 1.20 branch, because that branch does not carry "xf86: autobind GPUs to the screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862753/+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 1851936] Re: User profile won't load after upgrade - prompt to create new profile
Have upgraded both to 68.4.2.
Still get the message occasionally if trying to run from existing link. If I
break and remake (ie Pin) link, still get the error??
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
I'm having this problem -- printing duplex on short edge instead of long edg -- with a Brother HL-L2375DW. I'm running Ubuntu 19.10. It was working in Ubuntu 19.04. But, I thought it had also been printing correctly previously in 19.10, until it stopped working more recently. But I'm not 100% sure when it stopped working, since I don't print duplex very often. -- 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/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge Status in cups package in Ubuntu: Confirmed Bug description: Dell E310dw printer which worked well on 19.04 has problems in 19.10: First, I went through the CUPS web interface to add the printer. The interface gave me a choice of two entries with the same name plus one with "driverless" added. I chose the first entry (not driverless) and completed adding the printer. On the Printers page, the Dell was now listed. When I tried "Print Test Page", I got many pages each containing a single line of symbols. I deleted the printer in the web interface, intending to start again and choose the second option. But after I did Delete Printer, CUPS took me back to the Printers page which now listed: Dell_Printer_E310dw@DELL316BAA.local Dell Printer E310dw, driverless, cups-filters 1.25.11 So I clicked on that printer and tried Print Test Page, which worked. So then I tried a duplex print (which is really what I need this morning): lp -o sides=two-sided-long-edge -o collate=true -d Dell_Printer_E310dw@DELL316BAA.local filename.pdf It printed the PDF 2-sided, but with the sides flipped around the short edge, as if it was a landscape print. I tried the same command with sides=two-sided-short-edge and it flipped the same way. So sides is handling duplex but ignoring which edge is supposed to be used, and defaulting to landscape which I'd guess is less commonly what people want. This is all using what's built into Ubuntu. I haven't yet downloaded any extra drivers from Dell's site since Ubuntu claims to have a driver for the printer, and I'm pretty sure it was working in 19.04 (I may still have a working 19.04 to check that, if it would help). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Nov 25 09:58:21 2019 InstallationDate: Installed on 2019-10-10 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lpstat: device for Brother_HL-3170CDW_series: dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee device for Dell_Printer_E310dw@DELL316BAA.local: implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/ MachineType: LENOVO 20QDCTO1WW Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', '/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1754125] Re: Rhythmbox stays running in the background after quit
Julien, you are right in that the icon disappears if the program is simply closed with 'Quit'. However, I have added added rhythmbox to Ubuntu's dock so the icon is always visible. Right-clicking the icon displays "Stop & Quit". However, while the program is running, rather than just 'Quit' you can now 'Stop and Quit' from either the program icon or the icon that appears in the top bar while the program has focus. The new option in my view fixes the bug that was originally raised in that you can now quit and stop rhythmbox while music is playing, something that couldn't be done in previous releases. -- 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/1754125 Title: Rhythmbox stays running in the background after quit Status in rhythmbox package in Ubuntu: Triaged Bug description: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1790098] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-02-11 04:54 EDT--- IBM Bugzilla status -> closed, Fix Released with bionic -- 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/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now,
[Desktop-packages] [Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10
Unfortunately when I run ubuntu-bug gnome-shell it collects the information but then when I tell it to send it just returns to the command line immediately rather than sending me to launchpad, so I will have to get that sorted first. -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1856516/+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 1858105] Re: chromium-browser hangs on startup without gnome-keyring
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1858105 Title: chromium-browser hangs on startup without gnome-keyring Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.6 LTS chromium-browser 79.0.3945.79-0ubuntu0.16.04. (and some older ones) amd64 Ive used chromium-browser since a while but in the recent months it sometimes after exiting cannot be started again, it just hangs with no window opened and no meaningful error message. First I thought some corrupt profile was the cause as a restore of the profile from backup resolves this. But as it kept happening on a 100% stable system which runs 24/7 this is unlikely. Debugging this was a bit delayed as the -dbg package is outdated the -dbgsym package does not work with the gdb version i have from xenial and rebuilding chromium-browser strips debug symbols even when is_debug is enabled and it takes over 12h for a build. Either way, backtraces of the relevant threads are below. A workaround of this issue is to install gnome-keyring, start chromium-browser, cancel the gazillion of password requests and uninstall gnome-keyring and gcr, after that chromium-browser launches normal again. Another workaround is to use --single-process (which is a dumb idea security wise) I do not know why its doing that, i did not investigate further, but this is not normal or acceptable behavior of a browser even if I did something stupid which no doubt is possible. What i expect is well the browser should not hang and not do funny things with packages it doesnt have any dependancy/recommand/suggests on. And it should not grow tentacles that grab into keyrings without explanation to the user. info threads Id Target Id Frame * 1Thread 0x77f1dac0 (LWP 23428) "chromium-browse" __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 2Thread 0x7fffe85bd700 (LWP 23433) "sandbox_ipc_thr" 0x7144074d in poll () at ../sysdeps/unix/syscall-template.S:84 3Thread 0x7fffe7dbc700 (LWP 23438) "chromium-browse" 0x772d7f7b in __waitpid (pid=23435, stat_loc=0x7fffe7dbbb04, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 4Thread 0x7fffe6207700 (LWP 23439) "ThreadPoolServi" 0x7144ca13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 6Thread 0x7fffe5205700 (LWP 23441) "Chrome_IOThread" 0x7144ca13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 8Thread 0x7fffc700 (LWP 23443) "inotify_reader" 0x714425d3 in select () at ../sysdeps/unix/syscall-template.S:84 9Thread 0x7fffcf38f700 (LWP 23444) "gmain" 0x7144074d in poll () at ../sysdeps/unix/syscall-template.S:84 10 Thread 0x7fffceb8e700 (LWP 23445) "gdbus" 0x7144074d in poll () at ../sysdeps/unix/syscall-template.S:84 11 Thread 0x7fffce38d700 (LWP 23446) "Bluez D-Bus thr" 0x7144ca13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 12 Thread 0x7fffe413d700 (LWP 23447) "CrShutdownDetec" 0x772d751d in read () at ../sysdeps/unix/syscall-template.S:84 15 Thread 0x7fffccb8a700 (LWP 23450) "ThreadPoolForeg" pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 17 Thread 0x7fffabfff700 (LWP 23451) "ThreadPoolForeg" __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 18 Thread 0x7fffaaffd700 (LWP 23453) "CompositorTileW" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 19 Thread 0x7fffaa7fc700 (LWP 23454) "ThreadPoolSingl" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 20 Thread 0x7fffa9ffb700 (LWP 23455) "VideoCaptureThr" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 21 Thread 0x7fffa8ff9700 (LWP 23457) "gpu-process_cra" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 22 Thread 0x7fffa97fa700 (LWP 23456) "CacheThread_Blo" 0x7144ca13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 23 Thread 0x7fff87fff700 (LWP 23459) "utility_crash_u" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 24 Thread 0x7fff877fe700 (LWP 23461) "ThreadPoolSingl" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 25 Thread 0x7fff86ffd700 (LWP 23463) "Chrome_HistoryT" pthread_cond_timedwait@@GLIBC_2.3.2 () at
[Desktop-packages] [Bug 1754125] Re: Rhythmbox stays running in the background after quit
@Paul White The problem is that, in gnome-shell, if you close Rhythmbox while music is playing, Rhythmbox's icon simply disappears. So, there is no way to reach this "Stop & Quit" quickmenu option. Unless I'm missing something, of course... -- 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/1754125 Title: Rhythmbox stays running in the background after quit Status in rhythmbox package in Ubuntu: Triaged Bug description: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1754125] Re: Rhythmbox stays running in the background after quit
In rhythmbox 3.4.4 there is an additional quickmenu option of 'Stop & Quit'. This version will be in Ubuntu 20.04. Does that addition fix this bug? It works for me but others may disagree. -- 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/1754125 Title: Rhythmbox stays running in the background after quit Status in rhythmbox package in Ubuntu: Triaged Bug description: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1862056] Re: Theme: use other exported colors
Here is the MR: https://gitlab.gnome.org/GNOME/gnome-
software/merge_requests/421
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1862056
Title:
Theme: use other exported colors
Status in gnome-software package in Ubuntu:
Fix Released
Bug description:
Adwaita and Yaru both export colors at the top of their CSS file from within
this source files:
https://gitlab.gnome.org/GNOME/gtk/blob/master/gtk/theme/Adwaita/_colors-public.scss#L84
https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/gtk/theme/Adwaita/_colors-public.scss
gnome-software uses some of those colors in their in-app CSS that overwrites
the global gtk theme:
https://gitlab.gnome.org/GNOME/gnome-software/blob/master/src/gtk-style.css
Most likely those are the correct colors. In three cases sadly not and
it is too late to get an upstream change for 20.04 now because gnome
is already in UI freeze for this cycle:
1) The round checkmarks inside the App boxes that show that the app is
installed are orange instead of green, which is semantically wrong
since they are not selected and should instead show that you
successfully installed that app:
https://gitlab.gnome.org/GNOME/gnome-software/blob/master/src/gtk-style.css#L12
Change
.installed-icon {
color: @theme_selected_bg_color;
}
to
.installed-icon {
color: @success_color;
}
https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/gtk/theme/Adwaita/_colors-public.scss#L84
-> exported to:
https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/gtk/theme/Adwaita/gtk-contained.css#L2021
2) The little [1] boxes inside the "stackswitcher" in the headerbar (it's
actually a buttonbox in this case, but this is offtopic) that show up if you
are either installing X apps or have X updates would be orange, if we would not
"hack" a bg box-shadow over them to make them green. This is first of all a
dirty hack and secondly there are little orange pixels showing up at the
rounding
Change
.counter-label {
...
...
background-color: mix(@theme_selected_bg_color,
@theme_selected_fg_color, 0.3);
...
...
...
}
To
.counter-label {
...
...
background-color: @success_color;
...
...
...
}
https://gitlab.gnome.org/GNOME/gnome-software/blob/master/src/gtk-style.css#L422
3) The "given" stars are not visible in both Adwaita and Yaru dark. For some
reason, upstream transparentizes them into oblivion with the "shade-function".
The enabled stars should just use the theme's fg color:
Change
.star-enabled,
.star-enabled:disabled {
color: shade(@theme_fg_color, 0.8);
}
to
.star-enabled,
.star-enabled:disabled {
color: @theme_fg_color;
}
https://gitlab.gnome.org/GNOME/gnome-software/blob/master/src/gtk-style.css#L412
Thank you very much in advance! I try to get this into gnome-shell's
upstream repo in the next cycle
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862056/+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 1754125] Re: Rhythmbox stays running in the background after quit
This behaviour might me perfect in the default Ubuntu desktop (gnome- shell + Unity plugins), but it's broken if you use upstream gnome-shell because there is no tray to control Rhythmbox from once closed. I understand that Ubuntu's focus is on the default experience, but I guess it's also important to make it easy to use alternatives (especially when the "alternative" is actually upstream's default). So, wouldn't it be possible to detect whether the desktop has a "tray" (or "indicator" or whatever it's called in Unity), and really quit Rhythmbox on close if it doesn't? -- 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/1754125 Title: Rhythmbox stays running in the background after quit Status in rhythmbox package in Ubuntu: Triaged Bug description: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1851936] Re: User profile won't load after upgrade - prompt to create new profile
I am trying to run both Opensuse Leap 15.1, and Feren OS on the same PC as dual
boot.
Am getting this exact issue with Thunderbird - Version is 68.4.1 on both
Solution?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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
