[Desktop-packages] [Bug 1905010] Re: [snap] chromium forgets custom root certificates after each update
We have another case where Chromium "forgets" our internal root CA but
tells me it is already installed.
I can pinpoint this a bit further: we did an upgrade fom 18.04 to 20.04.
Uninstalling and re-installing chromium with snap seems to solve the
problem in most cases.
--
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/1905010
Title:
[snap] chromium forgets custom root certificates after each update
Status in chromium-browser package in Ubuntu:
Expired
Bug description:
Running
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
with
snap list | grep chromium
chromium 87.0.4280.661411 latest/stable
canonical* -
each time the snap container gets an update, our own root CA is
deleted from the certificate storage, leading to all our internal
websites being marked as potentially evil.
It would be nice if either snap migrates all data completely from one version
to another, or saving custom certificates inside the current-symlink (which
does not forget any data stored in there)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAQrDxBTFFGQS0dAQOANx947u6Vo1RMmSYPUFSlSwBxT6lAgYDRwAEBAQEBAQEBVl4AoKCgKVAwIDUAKTchAAAa/wAzQzRZUDlCOUFGUUwK/ABERUxMIFUyNTE4RAog/QA4TB5aGQAKICAgICAgAaYCAyTxT5AFBAMCBxYBBhESFRMUHyMJHweDAQAAZwMMABAAADICOoAYcTgtQFgsRQApNyEAAB5+OQCggDgfQDAgOgApNyEAABoBHQByUdAeIG4oVQApNyEAAB6/FgCggDgTQDAgOgApNyEAABoAxg==
modes: 2560x1440 2048x1080 2048x1080 1920x1080 1920x1080 1920x1080
1920x1080i 1920x1080i 1920x1080 1920x1080i 1600x1200 1280x1024 1280x1024
1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600
720x576 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
720x400
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: disabled
dpms: Off
status: connected
edid-base64:
AP///wANrskUAAgaAQSVHxF4Aihll1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQPGgANa0QAAAY/gBOMTQwSENBLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTQwSENBLUVBQgogAD4=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
tmpfs tmpfs 7,8G 134M 7,6G 2% /dev/shm
/dev/mapper/ubuntu--vg-root ext4 232G 108G 113G 49% /
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-01-17 (675 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20LS001AGE
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Snap.Changes:
ID Status Spawn Ready Summary
186 Done2020-11-23T10:48:28+01:00 2020-11-23T10:48:31+01:00
"chromium" Snap wiederherstellen
187 Done2020-11-23T10:49:18+01:00 2020-11-23T10:49:21+01:00
"chromium" Snap auffrischen
Snap.ChromeDriverVersion: ChromeDriver 87.0.4280.66
(fd98a29dd59b36f71e4741332c9ad5bda42094bf-refs/branch-heads/4280@{#1432})
Snap.ChromiumVersion: Chromium 87.0.4280.66 snap
Tags: focal snap
Uname: Linux 5.4.0-54-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-28 (208 days ago)
UserGroups: dialout lpadmin sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 12/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET60W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS001AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS001AGE
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Desktop crashes and return to login screen
there's no more uploaded file for xorg crash... I'll do what you ask on next crash and reboot. I found the origin of the gnome-shell entries in journalctl, they came from chrome. I try to not use it today and we'll see if I have no more gnome crash. I have no idea if it's related but it's not, I'll have the crash even if I don't use chrome. -- 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/1914573 Title: [DisplayLink] Desktop crashes and return to login screen Status in evdi package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1914573/+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 1914573] Re: [DisplayLink] Desktop crashes and return to login screen
the uploaded file. ** Attachment added: "_opt_displaylink_DisplayLinkManager.0.uploaded" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5460225/+files/_opt_displaylink_DisplayLinkManager.0.uploaded -- 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/1914573 Title: [DisplayLink] Desktop crashes and return to login screen Status in evdi package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1914573/+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 1914573] Re: Gnome desktop crash and return to login screen
Thanks. It sounds like a few different DisplayLink problems. It appears the display-related crashes are all in Xorg, Xwayland and DisplayLinkManager. The last one doesn't seem to be part of Ubuntu so I'll ignore that here. So the remaining two both come from the 'xorg- server' source package. Unfortunately I can't tell exactly how Xorg is crashing. Next time it happens, please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Please also share the contents of the '.uploaded' files. You don't need to share your whoopsie-id (also I can see it on those 'oops' pages). ** Summary changed: - Gnome desktop crash and return to login screen + [DisplayLink] Desktop crashes and return to login screen ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) ** Also affects: evdi (Ubuntu) Importance: Undecided Status: New ** Tags added: displaylink -- 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/1914573 Title: [DisplayLink] Desktop crashes and return to login screen Status in evdi package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1914573/+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 1914733] [NEW] Volume keys not working on Ubuntu 20.10 Groovy Gorilla
Public bug reported: Volume keys not working but sound still coming. Problem is that sound is not decreasing or increasing by using volume keys. sound only increase or decrease through Alsa Mixer. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/1914733 Title: Volume keys not working on Ubuntu 20.10 Groovy Gorilla Status in alsa-driver package in Ubuntu: New Bug description: Volume keys not working but sound still coming. Problem is that sound is not decreasing or increasing by using volume keys. sound only increase or decrease through Alsa Mixer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914733/+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 1914573] Re: Gnome desktop crash and return to login screen
Hello, 1. I have 3 crash files in /var/crash but the ubuntu-bug command fail. Each one has a ".upload" and ".uploaded" file so I think they're already uploaded. Shall I empty the folder to have a clean start point for next time the bug appear? 2. Many files in this page. These are the 3 related with the crashs in my /var/crash, but there're many others : 2021-02-04 07:02 (the day when I opened this bug) - https://errors.ubuntu.com/oops/b95f8166-66b4-11eb-84cc-fa163e102db1 2021-01-27 09:01 : https://errors.ubuntu.com/oops/6b87b264-607b-11eb-83c4-fa163e102db1 2021-02-02 09:02 : https://errors.ubuntu.com/oops/46f3c61a-652e-11eb-90f7-fa163ee63de6 May I link the full url of https://errors.ubuntu.com/user/ID or is it unsafe? -- 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/1914573 Title: Gnome desktop crash and return to login screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914573/+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 1914573] Re: Gnome desktop crash and return to login screen
By the way, my "journalctl" is full of this, maybe related, maybe not... févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: Errors: févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: [4886:4886:0205/073611.340319:ERROR:shared_context_state.cc(74)] Skia shader compilation error févr. 05 07:36:11 PORTABLE-USERNAME gnome-shell[3662]: -- 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/1914573 Title: Gnome desktop crash and return to login screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914573/+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 1914601] Re: GUI apps do not start from the link created
Hi, > Could be that the target is too long when `--gui` flag is used? This is the normal behavior of properties window that they will display to be truncated, but actually not. Editing it will result in actual truncation. --- Also, since 20.04 package is outdated, and the package is currently still waiting for the update here: #1911432, can you try the PPA version before it gets merged, and see if it works? https://launchpad.net/~wslutilities/+archive/ubuntu/wslu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1906995] Re: Gnome suddently crahses after update
[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/1906995 Title: Gnome suddently crahses after update Status in gnome-shell package in Ubuntu: Expired Bug description: After Ubuntu enter sleep mode, Gnome crashes ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 16:25:49 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-21 (15 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-11-30 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906995/+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 1914583] Re: unresponsive gnome de on 20.10
Thanks for the bug report. Please try the workaround from bug 1896164. ** Tags added: raspi raspi-gfx ** 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/1914583 Title: unresponsive gnome de on 20.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz. Even with disabled animation and 1 static workspace, gnome de is still generally not quite responsive: list of apps takes about 5 secs to display, opening a folder in app list takes about 2 secs, almost everywhere lag between click and action is 1 sec+. So just a heads up here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1013.16-raspi 5.8.18 Uname: Linux 5.8.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Feb 4 13:57:21 2021 DisplayManager: gdm3 ImageMediaBuild: 20201022 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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/1914583/+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 1913672] Re: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width
> Maybe old bug reports are incorrectly attached to newer packages. That would certainly explain the weird stack traces and lack of working debug symbols. -- 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/1913672 Title: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width Status in gnome-shell package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1~20.10.1, the problem page at https://errors.ubuntu.com/problem/4f12318421d8c95c357e2db953aa75b2cdcacdfa 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/gnome-shell/+bug/1913672/+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 1914573] Re: Gnome desktop crash and return to login screen
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/1914573 Title: Gnome desktop crash and return to login screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914573/+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 1914147]
I was unable to reproduce the issue by using Firefox 85.0a1 (2020-11-30) after and before updating it, under macOS 10.15.7. It seems that the reporter says the fix is working (see Comment 16 and Comment 17), so I will remove the qa+ flag based on that. If further investigation is needed, please don't hesitate and ni me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914147 Title: [upstream] Firefox 85 hangs at startup Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: In Progress Bug description: Today I have received a security upgrade for kubuntu 20.04 including firefox 85. Unfortunately, this version of firefox appears to hang at start unless it is started passing an url. Namely: firefox hangs, while firefox lwn.net does not hang. I have quickly tried working with a clean profile and firefox 85 seems to start fine with that. Yet, the profile is not broken: if I downgrade to firefox 84 and restore my profile from a backup, then firefox 84 works just fine. So the issue seems to be that firefox 85 has issues in working with profiles that are totally fine with firefox 84. This breaks migration from firefox 84 to firefox 85. Issue is totally reproducible: downgrade to firefox 84 restore profile from firefox 84 from backup work with firefox 84 (OK) upgrade to firefox 85 try to work with firefox 85 (KO) Please consider that having to reset a profile is a form of data loss. In a modern browser, the profile includes extensions, passwords, data from web apps and more. Because this bug makes it impossible to apply a security update (firefox 85 is marked as such and shipped via the security channel), this bug is particularly serious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 84.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 1454 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Tue Feb 2 00:52:23 2021 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-02-16 (351 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.10.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.116 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=84.0.2/20210105180113 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-05-23 (254 days ago) dmi.bios.date: 10/02/2019 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: N141CU dmi.board.vendor: SCHENKER dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: SCHENKER_SLIM14_SSL14L19 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SCHENKER To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1914147/+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 1477489] Re: Content indexing spamming syslog and logging personal information (emails etc) - there should be a way to disable file contents indexing
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tracker (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1477489
Title:
Content indexing spamming syslog and logging personal information
(emails etc) - there should be a way to disable file contents indexing
Status in Tracker:
Invalid
Status in tracker package in Ubuntu:
Confirmed
Bug description:
I recently changed from Ubuntu 15.04, to Ubuntu Gnome 15.04 (I was
using Unity, now Gnome Shell), and since I have changed I have noticed
some problems similar to this bug report in Tracker's logging to
syslog: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754907
So what I am noticing is that it is spamming my syslog with loads and
loads of stuff similar to the bug report I linked to above. But not
only is it spamming contents there, it is also putting the contents
and details of my private emails etc, for instance I have OSSEC HIDS
running and it keeps on reporting to me of these sorts of things:
"
OSSEC HIDS Notification. 2015 Jul 22 21:08:46
Received From: Weaponised-Towel->/var/log/syslog Rule: 1003 fired
(level 13) -> "Non standard syslog message (size too large)." Portion
of the log(s):
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]:
nie:description "Beginning Android Games, Second Edition offers
everything you need to join the ranks of successful Android game
developers, including Android tablet game app development
considerations. You'll start with game design fundamentals and
programming basics, and then progress toward creating your own basic
game engine and playable game apps that work on Android and earlier
version compliant smartphones and now tablets. This will give you
everything you need to branch out and write your own Android games.
The potential user base and the wide array of available high-
performance devices makes Android an attractive target for aspiring
game developers. Do you have an awesome idea for the next break-
through mobile gaming title? Beginning Android Games will help you
kick-start your project. This book will guide you through the process
of making several example game apps using APIs available in new
Android SDK and earlier SDK releases for Android smartphones and
tablets: The fundamentals of game development and design suitable for
Android smartphones and tablets The Android platform basics to apply
those fundamentals in the context of making a game, inc
--END OF NOTIFICATION
"
And then when I checked my syslog for that time period these are the
sorts of things that I saw:
"
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: INSERT {
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: GRAPH
{
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]:
nie:dataSource
.
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]:
a nfo:EBook ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:creator [ a
nco:PersonContact ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:fullname "Zechner,
Mario & Green, Robert" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameFamily
"Zechner" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameGiven "Mario" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameAdditional "&
Green, Robert" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:creator
] ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:creator [ a
nco:PersonContact ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:fullname "Robert
Green" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameFamily "Green" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:nameGiven "Robert" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:creator
] ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nie:title "Beginning
Android Games" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:publisher [ a
nco:Contact ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nco:fullname "Apress"] ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nie:identifier
"URN:ISBN:978-1-4302-4677-0" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nie:identifier
"9781430246770" ;
Jul 22 21:08:44 Weaponised-Towel gnome-session[1509]: nie:description "Beginning Android Games, Second Edition offers everything
you need to join the ranks of successful Android game developers, including
Android tablet game app development considerations. You'll start with game
design fundamentals and programming basics, and then progress toward creating
your own basic game engine and playable game apps that work on
[Desktop-packages] [Bug 1895852] Re: can't access network printer since 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1895852 Title: can't access network printer since 20.04 Status in system-config-printer package in Ubuntu: Confirmed Bug description: I can access my network printer with all previous LTS-ubuntu version, but not since 20.04. Normally, system-config-printer can found it with search functionality. The expected result is: smb://freebox/Brother%20DCP-J752DW But in 20.04 I can't because System-config-printer ask for a password to access workgroup. But there is NO password! The printer is shared without identification needed. I still have ubuntu16.04 on same machine and I am forced to print with it. I give the output of system-config-printer --debug file with 16.04 if you want to compare with 20.04. I have installed python3-smbc (1.0.15.6-2build2) to have the search functionality (software-center proposed to install it but can't!). Then I have allowed samba with sudo ufw allow samba because system-config-printer ask it to try to access printer. :~$ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 :~$ apt-cache policy system-config-printer system-config-printer: Installé : 1.5.12-0ubuntu1 Candidat : 1.5.12-0ubuntu1 Table de version : *** 1.5.12-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://fr.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status Printer: brother DCP-j752DW, cups drivers from brother site. Server: a box, freebox4k-mini (from "free" french ISP) connected via USB to the printer. I found other people having same problem with other hardware (server and/or printer). I can't use ubuntu20.04 with this issue. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: system-config-printer 1.5.12-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [16/Sep/2020:15:25:11 +0200] Unknown directive JobPrivateAccess on line 125 of /etc/cups/cupsd.conf. E [16/Sep/2020:15:25:11 +0200] Unknown directive JobPrivateValues on line 126 of /etc/cups/cupsd.conf. E [16/Sep/2020:15:25:11 +0200] Unknown directive SubscriptionPrivateAccess on line 127 of /etc/cups/cupsd.conf. E [16/Sep/2020:15:25:11 +0200] Unknown directive SubscriptionPrivateValues on line 128 of /etc/cups/cupsd.conf. CurrentDesktop: XFCE Date: Wed Sep 16 15:34:36 2020 Lpstat: device for CUps-USB: cups-brf:/ device for CUPSReseau: lpd://mafreebox.freebox.fr device for DCP-J752DW: lpd://0.0.0.0/binary_p1 device for test: socket://mafreebox.freebox.fr:9100 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader Bus 002 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 8: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all Papersize: a4 PpdFiles: test: Brother DCP-J752DW CUPS CUPSReseau: Brother DCP-J752DW CUPS CUps-USB: Brother DCP-J752DW CUPS DCPJ752DW: Brother DCP-J752DW CUPS DCP-J752DW: Brother DCP-J752DW CUPS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-lowlatency root=UUID=0a780a26-4ab8-45b9-80b7-41f505936637 ro splash quiet SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC 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.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC: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
[Desktop-packages] [Bug 1914583] Re: unresponsive gnome de on 20.10
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Public Security to Public -- 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/1914583 Title: unresponsive gnome de on 20.10 Status in gnome-shell package in Ubuntu: New Bug description: Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz. Even with disabled animation and 1 static workspace, gnome de is still generally not quite responsive: list of apps takes about 5 secs to display, opening a folder in app list takes about 2 secs, almost everywhere lag between click and action is 1 sec+. So just a heads up here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1013.16-raspi 5.8.18 Uname: Linux 5.8.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Feb 4 13:57:21 2021 DisplayManager: gdm3 ImageMediaBuild: 20201022 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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/1914583/+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 1869847] Re: LaTeX: noto font doesn't work with medium weight anymore
This has been fixed on Ubuntu 20.10 (though still not working in 20.04
LTS).
** Changed in: texlive-extra (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1869847
Title:
LaTeX: noto font doesn't work with medium weight anymore
Status in texlive-extra package in Ubuntu:
Fix Released
Bug description:
Trying to use font 'Noto' with medium weight doesn't work anymore in
Ubuntu 20.04 (prerelease, 20200331). It worked fine in Ubuntu 19.10
and earlier.
Defining the following in a LaTeX document:
\usepackage[medium,extrabold]{noto}
causes errors like this when executing 'pdflatex':
"LaTeX Font Warning: Font shape `T1/NotoSerif-TLF/ediu/it'
undefined"
Regular weight works fine.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: texlive-fonts-extra 2019.202000218-1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Mar 31 10:20:28 2020
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: texlive-extra
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1869847/+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 1886161] Re: Unattended upgrades should work on roaming laptops
Just an update, for what it's worth. I solved this problem with a shell script triggered by Network Manager's "up" hook. Because UU does not update the package list, I had to resort to a `apt-get update && apt-get dist-upgrade` with `DEBIAN_FRONTEND=noninteractive` and a whole bunch of options to make sure everything runs reliably in the background. Convoluted and laborious. But now my Ubuntu is *always* up to date. Before, it regularly went *months* without a security update. Putting aside whose fault it is, this absolutely IS a problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1886161] Re: Unattended upgrades should work on roaming laptops
** Summary changed: - UU should work on roaming laptops + Unattended upgrades should work on roaming laptops -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1894833] Re: [Dell XPS 15 7590, Realtek ALC3266, Mic, Internal] Lots of background noise on internal microphone
Update: in my case I took the case with Dell support, they changed some parts, which included obviously the internal microphone, but also the trackpad (they are positioned close to each other physically. That fixed the issue, the sound is good now. In my case the status 'Invalid' is correct, it was a hardware issue. -- 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/1894833 Title: [Dell XPS 15 7590, Realtek ALC3266, Mic, Internal] Lots of background noise on internal microphone Status in alsa-driver package in Ubuntu: Invalid Bug description: Problem: Lots of background noise on the internal microphone. If I record it in Audacity it seems that most of the noise is in the Left- Front channel. The Right-Front channel is still noisy/bad quality, but not as bad. Hardware: Dell XPS 15 7590 laptop (basically 2019 model) OS: Ubuntu 20.04 fresh/plain installation: $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Other tests: - If I use a external/USB headsets+microphone sound is fine - If I boot from Ubuntu 20.04 live USB it still has the problem - Tested with other versions/distributions, but it still has the problem: ubuntu-19.10-desktop-amd64, linuxmint-20-cinnamon-64bit, Fedora-Workstation-Live-x86_64-32-1.6, xubuntu-20.04.1-desktop-amd64, pop-os_20.04_amd64_nvidia_13, ubuntu-18.04.5-desktop-amd64 - I tried many steps involving changing config files e.g. https://wiki.ubuntu.com/Audio/PositionReporting + reboot, none fixed the problem, reverted the config files back after every change ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mircea 1400 F pulseaudio /dev/snd/pcmC0D0c: mircea 1400 F...m pulseaudio /dev/snd/pcmC0D0p: mircea 1400 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 12:33:31 2020 InstallationDate: Installed on 2020-09-06 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: High background noise, or volume is too low Title: [XPS 15 7590, Realtek ALC3266, Mic, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd07/03/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-09-08T11:02:41.506649 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1894833/+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 1914614] Re: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe)
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1914614 Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe) Status in sane-backends package in Ubuntu: New Bug description: After install Ubuntu I update via software updater , but i get error while install update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 4 19:06:49 2021 DuplicateSignature: package:sane-utils:1.0.29-0ubuntu5.2 Setting up sane-utils (1.0.29-0ubuntu5.2) ... dpkg: error processing package sane-utils (--configure): installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2021-02-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sane-backends Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1914614/+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 1914614] Re: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe)
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1914614 Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe) Status in sane-backends package in Ubuntu: New Bug description: After install Ubuntu I update via software updater , but i get error while install update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 4 19:06:49 2021 DuplicateSignature: package:sane-utils:1.0.29-0ubuntu5.2 Setting up sane-utils (1.0.29-0ubuntu5.2) ... dpkg: error processing package sane-utils (--configure): installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2021-02-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: sane-backends Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1914614/+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 1894833] Re: [Dell XPS 15 7590, Realtek ALC3266, Mic, Internal] Lots of background noise on internal microphone
Don't close this bug, please! The input from microphone is terrible :( -- 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/1894833 Title: [Dell XPS 15 7590, Realtek ALC3266, Mic, Internal] Lots of background noise on internal microphone Status in alsa-driver package in Ubuntu: Invalid Bug description: Problem: Lots of background noise on the internal microphone. If I record it in Audacity it seems that most of the noise is in the Left- Front channel. The Right-Front channel is still noisy/bad quality, but not as bad. Hardware: Dell XPS 15 7590 laptop (basically 2019 model) OS: Ubuntu 20.04 fresh/plain installation: $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Other tests: - If I use a external/USB headsets+microphone sound is fine - If I boot from Ubuntu 20.04 live USB it still has the problem - Tested with other versions/distributions, but it still has the problem: ubuntu-19.10-desktop-amd64, linuxmint-20-cinnamon-64bit, Fedora-Workstation-Live-x86_64-32-1.6, xubuntu-20.04.1-desktop-amd64, pop-os_20.04_amd64_nvidia_13, ubuntu-18.04.5-desktop-amd64 - I tried many steps involving changing config files e.g. https://wiki.ubuntu.com/Audio/PositionReporting + reboot, none fixed the problem, reverted the config files back after every change ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mircea 1400 F pulseaudio /dev/snd/pcmC0D0c: mircea 1400 F...m pulseaudio /dev/snd/pcmC0D0p: mircea 1400 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 12:33:31 2020 InstallationDate: Installed on 2020-09-06 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: High background noise, or volume is too low Title: [XPS 15 7590, Realtek ALC3266, Mic, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd07/03/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-09-08T11:02:41.506649 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1894833/+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 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image
** Changed in: ubiquity (Ubuntu) Milestone: ubuntu-20.04.2 => ubuntu-21.04-beta ** Changed in: ubuntu-drivers-common (Ubuntu) Milestone: None => ubuntu-21.04-beta -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Triaged Status in ubuntu-drivers-common source package in Groovy: New Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1913672] Re: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width
Maybe old bug reports are incorrectly attached to newer packages. Focal, Bionic and others also have "zombie updates" : update-notifier on Focal, gnome-calculator and nautilus on Bionic. Those last two have been zombified more than one year ago (moreover at the same time it seems). Have a look here : https://people.canonical.com/~ubuntu-archive/phased- updates.html Considering all those first go through proposed, the phasing system is an ultimate security system in case something slipped through, which should happen rarely. -- 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/1913672 Title: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width Status in gnome-shell package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1~20.10.1, the problem page at https://errors.ubuntu.com/problem/4f12318421d8c95c357e2db953aa75b2cdcacdfa 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/gnome-shell/+bug/1913672/+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 1913672] Re: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width
I wonder if it could be a bug related to the crash reporting software instead. What looks strange (but maybe I'm not reading it correctly) is that the publishing history indicates it was brought back to 0% even before it was put at 10% : https://launchpad.net/ubuntu/groovy/amd64 /gnome-shell It seems to me it should at least collect some data before phasing out, so maybe the bug is somewhere else or it has been blocked manually... The qemu package looks affected too, maybe it's not a coincidence that it has been published only a few days before : https://launchpad.net/ubuntu/groovy/amd64/qemu -- 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/1913672 Title: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width Status in gnome-shell package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1~20.10.1, the problem page at https://errors.ubuntu.com/problem/4f12318421d8c95c357e2db953aa75b2cdcacdfa 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/gnome-shell/+bug/1913672/+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 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
First of all, thanks for your time. > One bug report can track a problem across several packages, so there's no need for multiple reports. Sorry for the noise :-) > If you can reproduce it with Hirsute I can reproduce the problem using linux-image-generic 5.10.0.14.16 from hirsute in a tty. To be sure I did it right, those are the steps I followed: 1. added this repo to the list of repos: deb http://archive.ubuntu.com/ubuntu/ hirsute-proposed restricted main multiverse universe 2. updated apt list and installed those packages: linux-headers-generic/hirsute-proposed linux-modules-5.10.0-14-generic/hirsute-proposed linux-modules-extra-5.10.0-14-generic/hirsute-proposed linux-image-5.10.0-14-generic/hirsute-proposed 3. Rebooted, choose kernel 5.10 from advanced list in grub 4. On gnome login prompt, switched to tty with ctrl+alt+F3 5. Check kernel and packages: $ uname -a Linux bestia3 5.10.0-14-generic #15-Ubuntu SMP Fri Jan 29 15:10:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep 5.10.0 ii linux-headers-5.10.0-145.10.0-14.15 all Header files related to Linux kernel version 5.10.0 ii linux-headers-5.10.0-14-generic5.10.0-14.15 amd64Linux kernel headers for version 5.10.0 on 64 bit x86 SMP ii linux-headers-generic 5.10.0.14.16 amd64Generic Linux kernel headers ii linux-image-5.10.0-14-generic 5.10.0-14.15 amd64Signed kernel image generic ii linux-modules-5.10.0-14-generic5.10.0-14.15 amd64Linux kernel extra modules for version 5.10.0 on 64 bit x86 SMP ii linux-modules-extra-5.10.0-14-generic 5.10.0-14.15 amd64Linux kernel extra modules for version 5.10.0 on 64 bit x86 SMP Now, calling 'sensors' from console still causes the problem, i.e. the output of sensors hangs a couple of seconds just after printing 'amdgpu-pci-0100' and the fans start spinning. The only difference with kernel 5.10 wrt kernel 5.8 is that I don't see the kernel error messages directly into the tty, but they are present in dmesg: [ 25.039603] vboxdrv: TSC mode is Invariant, tentative frequency 2592005345 Hz [ 25.039607] vboxdrv: Successfully loaded version 6.1.18 (interface 0x0030) [ 25.251013] VBoxNetFlt: Successfully started. [ 25.253147] VBoxNetAdp: Successfully started. [ 41.364575] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 41.493122] [drm] UVD and UVD ENC initialized successfully. [ 41.603133] [drm] VCE initialized successfully. [ 41.609182] amdgpu :01:00.0: [drm] Cannot find any crtc or sizes [ 41.680294] rfkill: input handler enabled [ 47.719525] Bluetooth: RFCOMM TTY layer initialized [ 47.719530] Bluetooth: RFCOMM socket layer initialized [ 47.719535] Bluetooth: RFCOMM ver 1.11 * END OF BOOT ** * Called 'sensors' in tty vvv ** [ 96.156579] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 96.285097] [drm] UVD and UVD ENC initialized successfully. [ 96.395079] [drm] VCE initialized successfully. [ 96.401254] amdgpu :01:00.0: [drm] Cannot find any crtc or sizes ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux-signed-hwe-5.8 package in Ubuntu: Incomplete Status in lm-sensors package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate:
[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth
Made a script to split a single OpenVPN file to multiple to avoid the issue due
to XML chunks within the single file breaking network-manager-openvpn when
importing
https://gist.github.com/ThomasG77/5c09eead1244f9d1d2bd7fa70b26fead
--
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/606365
Title:
unable to import config with inlined ca, cert, key or tls-auth
Status in NetworkManager-OpenVPN:
Fix Released
Status in plasma-nm:
New
Status in network-manager-openvpn package in Ubuntu:
Fix Released
Status in plasma-nm package in Ubuntu:
Fix Released
Bug description:
Binary package hint: network-manager-openvpn-gnome
So a client of mine runs an OpenVPN setup. It exported a client.ovpn
file but it fails to completely import this file using the network-
manager (gnome) on Ubuntu 10.04.
When I import the file, it gives me the name ("client") and gateway
("vpn.example.org") on the initial screen. No other fields are
populated even though the client.ovpn file also includes a user
certificate, server certifikate and a private key.
When I go to advanced, some (most) of the settings obviously seem to
import correct, others not at all. E.g. none of the TLS settings (key
and key direction) are imported.
From what I understand I should be able to use this without any
additional settings.
The following software is installed through aptitude:
* openvpn (2.1.0)
* openvpn-blacklist
* network-manager-openvpn
* network-manager-openvpn-gnome
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+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 1914601] Re: GUI apps do not start from the link created
Also, if I open the desktop shortcut properties I see that target is truncated: C:\Windows\System32\wscript.exe C:\\Users\\username\wslu\runHidden.vbs "C:\\Users\\username\\AppData\\Local\\Microsoft\\WindowsApps\\CanonicalGroupLimited.Ubuntu20.04onWindows_79rhkp1fndgsc\\ubuntu2004.exe" run "cd ~; . /usr/share/wslu/wsl-integration.s Could be that the target is too long when `--gui` flag is used? Without `--gui` flag, the target is much shorter: C:\Users\username\AppData\Local\Microsoft\WindowsApps\CanonicalGroupLimited.Ubuntu20.04onWindows_79rhkp1fndgsc\ubuntu2004.exe run "cd ~; terminator" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1914601] Re: GUI apps do not start from the link created
Hi, As you can see from bug description, I also tried --gui flag which also did not produce a working link. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Fix Released Status in clucene-core package in Ubuntu: Fix Released Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+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 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
Hello munbi and thanks for this bug report. I marked the other two bugs you filed as duplicates of this one, and added "tasks" for the packages you filed the other bugs against. One bug report can track a problem across several packages, so there's no need for multiple reports. I don't think xserver-xorg-video-amdgpu is really involved here. If you can reproduce this issue without logging it to the graphical console, i.e. by calling `sensors` from tty, and you agree that this proves that Xorg is not involved, then please change the status of the xserver-xorg- video-amdgpu task to Invalid. My feeling is that we're seeing a kernel issue here. If you can reproduce it with Hirsute (the current Ubuntu devel version) then I think we can add a "regular" kernel task, as the problem is not HWE- specific. Currently linux-image-generic 5.10.0.14.16 is in the Hirsute -proposed pocket. Could you try to test that newer kernel and report how it behaves? I'm setting the status of this bug to Incomplete for the moment, waiting for the results of your testing. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Incomplete ** Changed in: lm-sensors (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux-signed-hwe-5.8 package in Ubuntu: Incomplete Status in lm-sensors package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+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 1914226] Re: Add option to enable screen-keyboard icon for panel
** Description changed: Add option to enable screen-keyboard icon for panel - (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) - (Currently if enable it through universal access > screen keyboard then it makes quite annoying due pop up often) + - it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field. + - furthermore sometimes we tap on certain areas for drag, move windows etc that may related to input fields and screen keyboard appear such times + - Even if user mistake touch on certain areas and some third-party application then that gives trouble + + (Currently if enable it through universal access > screen keyboard then it makes quite annoying once again due pop up often) https://gitee.com/mHatsune/chaya/raw/master/disk/screenkeyboard.png -- 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/1914226 Title: Add option to enable screen-keyboard icon for panel Status in gnome-shell package in Ubuntu: Triaged Bug description: Add option to enable screen-keyboard icon for panel - it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field. - furthermore sometimes we tap on certain areas for drag, move windows etc that may related to input fields and screen keyboard appear such times - Even if user mistake touch on certain areas and some third-party application then that gives trouble (Currently if enable it through universal access > screen keyboard then it makes quite annoying once again due pop up often) https://gitee.com/mHatsune/chaya/raw/master/disk/screenkeyboard.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914226/+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 1914226] Re: Add option to enable screen-keyboard icon for panel
** Description changed: - Add option to enable screen-keyboard icon in dock + Add option to enable screen-keyboard icon for panel (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) (Currently if enable it through universal access > screen keyboard then it makes quite annoying due pop up often) https://gitee.com/mHatsune/chaya/raw/master/disk/screenkeyboard.png -- 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/1914226 Title: Add option to enable screen-keyboard icon for panel Status in gnome-shell package in Ubuntu: Triaged Bug description: Add option to enable screen-keyboard icon for panel - it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field. - furthermore sometimes we tap on certain areas for drag, move windows etc that may related to input fields and screen keyboard appear such times - Even if user mistake touch on certain areas and some third-party application then that gives trouble (Currently if enable it through universal access > screen keyboard then it makes quite annoying once again due pop up often) https://gitee.com/mHatsune/chaya/raw/master/disk/screenkeyboard.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914226/+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 1914601] Re: GUI apps do not start from the link created
Hi, For GUI apps, -g should be passed when creating shortcuts. Can you run `wslusc -g terminator` and check it again? Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Also affects: lm-sensors (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux-signed-hwe-5.8 package in Ubuntu: New Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+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 1914601] [NEW] GUI apps do not start from the link created
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Summary changed: - GUI apps do not work + GUI apps do not work from the link created ** Summary changed: - GUI apps do not work from the link created + GUI apps do not start from the link created -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1914601 Title: GUI apps do not start from the link created Status in wslu package in Ubuntu: New Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 wslu: Installed: 2.3.6-0ubuntu2~20.04.0 Candidate: 2.3.6-0ubuntu2~20.04.0 Version table: *** 2.3.6-0ubuntu2~20.04.0 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.3.6-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages C:\Users\username\Desktop>wsl -l -v NAME STATE VERSION * Ubuntu-20.04 Running 2 $ wslusc --version wslu v2.3.6; wslusc v37 $ wslusc terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused You need to run terminator in an X environment. Make sure $DISPLAY is properly set $ wslusc --gui terminator [info] Create shortcut terminator.lnk successful C:\Users\username\Desktop>terminator.lnk Looks like DISPLAY propery is not set correctly by the underlying script: $ pwd /usr/share/wslu $ export DISPLAY=SHOULD_BE_SET $ . wsl-integration.sh $ echo $DISPLAY SHOULD_BE_SET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1914601/+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 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
clucene-core (2.3.3.4+dfsg-1ubuntu1) hirsute; urgency=medium * Fix float_t abi to double ahead of glibc change. -- Dimitri John Ledkov Mon, 01 Feb 2021 10:22:06 + ** Changed in: clucene-core (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: In Progress Status in clucene-core package in Ubuntu: Fix Released Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+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 1914413] Re: amdgpu driver interaciton with lm-sensor causes fans to spin up in kernel 5.8
*** This bug is a duplicate of bug 1910562 *** https://bugs.launchpad.net/bugs/1910562 ** This bug has been marked a duplicate of bug 1910562 Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1914413 Title: amdgpu driver interaciton with lm-sensor causes fans to spin up in kernel 5.8 Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Previously reported here as a kernel bug ( https://bugs.launchpad.net/ubuntu/+source/linux-signed- hwe-5.8/+bug/1910562 ), now after finding root cause reporting here also. After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. So, after testing several different kernels and live distros to pinpoint this bug, I finally found out the problem: it's an interaction between lm-sensors and amdgpu driver with kernel > 5.4.0. I found out by chance because I noticed the problem happened only after logging in with a graphical session. This is what is happening: - a gnome extension to monitor sensors/temps calls the 'sensors' utility from package lm-sensors every 10 senconds - sensors 'hangs' for a couple of seconds when poking something related to the amdgpu driver - amdgpu driver spits some warning/errors on vt console and dmesg - fans starts spinning for one sec - then sensors continue normally displaying the readouts from other sensor This is the output of 'sensors', taken in a non-graphical console (ctr+alt+F3) with kernel 5.8.0-41: [UNRELATED OUTPUT] amdgpu-pci-0100 Adapter: PCI adapter [ 112.780951] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 113.380939] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! vddgfx: 1.05 V edge: +44.0°C (crit = +94.0°C, hyst = -273.1°C) power1: 7.12 W (cap = 35.00 W) [UNRELATED OUTPUT] This is the complete kernel log from amgpu when this happens: [ 111.572873] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 112.780951] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 113.380939] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 113.411556] [drm] UVD and UVD ENC initialized successfully. [ 113.521534] [drm] VCE initialized successfully. It seems that lm-sensors poking the amdgpu thermal sensor i triggering some sort of reset and/or causing the thermal infrastructure to spin up the fans Note that this is not happening with kernel 5.4, with which sensor reports this: amdgpu-pci-0100 Adapter: PCI adapter vddgfx: N/A edge: N/A (crit = +94.0°C, hyst = -273.1°C) power1: N/A (cap = 35.00 W) [UNRELATED OUTPUT] Note the missing data about amdgpu and no console kernel warning messages. Disabling the gnome sensor check extension solves the problem for now, but there is definitely something going on here. Please feel free to ask me for anything I can do/test to help solve this problem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-amdgpu 19.1.0-1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 3 14:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0926] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 3200] [1002:6981] (prog-if 00 [VGA controller]) Subsystem: Dell Lexa XT [Radeon PRO WX 3200] [1028:0926] InstallationDate: Installed on 2020-05-06 (273 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-amdgpu
[Desktop-packages] [Bug 1914583] Re: unresponsive gnome de on 20.10
** Information type changed from Public to Public Security -- 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/1914583 Title: unresponsive gnome de on 20.10 Status in gnome-shell package in Ubuntu: New Bug description: Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz. Even with disabled animation and 1 static workspace, gnome de is still generally not quite responsive: list of apps takes about 5 secs to display, opening a folder in app list takes about 2 secs, almost everywhere lag between click and action is 1 sec+. So just a heads up here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1013.16-raspi 5.8.18 Uname: Linux 5.8.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Feb 4 13:57:21 2021 DisplayManager: gdm3 ImageMediaBuild: 20201022 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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/1914583/+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 1914583] Re: unresponsive gnome de on 20.10
** Description changed: - Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz. - Even with disabled animation and 1 static workspace, gnome de is still generally not quite responsive: list of apps takes about 5 secs to display, opening a folder in app list takes about 2 secs, almost everywhere lag between click and action is 1 sec+. In general, it works and I wanted gnome de to stay as I trust ubuntu devs with their choices but after few months I can't force myself to tolerate constant lags. So just a heads up here. + Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz. + Even with disabled animation and 1 static workspace, gnome de is still generally not quite responsive: list of apps takes about 5 secs to display, opening a folder in app list takes about 2 secs, almost everywhere lag between click and action is 1 sec+. + So just a heads up here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1013.16-raspi 5.8.18 Uname: Linux 5.8.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Feb 4 13:57:21 2021 DisplayManager: gdm3 ImageMediaBuild: 20201022 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1914583 Title: unresponsive gnome de on 20.10 Status in gnome-shell package in Ubuntu: New Bug description: Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz. Even with disabled animation and 1 static workspace, gnome de is still generally not quite responsive: list of apps takes about 5 secs to display, opening a folder in app list takes about 2 secs, almost everywhere lag between click and action is 1 sec+. So just a heads up here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1013.16-raspi 5.8.18 Uname: Linux 5.8.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Feb 4 13:57:21 2021 DisplayManager: gdm3 ImageMediaBuild: 20201022 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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/1914583/+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 1914583] [NEW] unresponsive gnome de on 20.10
Public bug reported: Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz. Even with disabled animation and 1 static workspace, gnome de is still generally not quite responsive: list of apps takes about 5 secs to display, opening a folder in app list takes about 2 secs, almost everywhere lag between click and action is 1 sec+. So just a heads up here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1013.16-raspi 5.8.18 Uname: Linux 5.8.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Feb 4 13:57:21 2021 DisplayManager: gdm3 ImageMediaBuild: 20201022 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy -- 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/1914583 Title: unresponsive gnome de on 20.10 Status in gnome-shell package in Ubuntu: New Bug description: Just one more user of latest raspberry pi 4 8gb overclocked to 2 ghz. Even with disabled animation and 1 static workspace, gnome de is still generally not quite responsive: list of apps takes about 5 secs to display, opening a folder in app list takes about 2 secs, almost everywhere lag between click and action is 1 sec+. So just a heads up here. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1013.16-raspi 5.8.18 Uname: Linux 5.8.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Feb 4 13:57:21 2021 DisplayManager: gdm3 ImageMediaBuild: 20201022 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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/1914583/+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 1766230] Re: Strange window matching behaviour between Slack and Chrome
I am also seeing this behaviour on 20.04.1 - it is confusing. I also see it when I open Cypress from within a terminal inside JetBrains PhpStorm - the chrome windows opened by that are co-located with the PhpStorm 'pips'. This makes ctrl-tabbing between open applications difficult. -- 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/1766230 Title: Strange window matching behaviour between Slack and Chrome Status in gnome-shell package in Ubuntu: Confirmed Bug description: There seems to be a window matching bug between the Slack snap and Chrome. If you open a URL from within Slack without Chrome open, then the launcher shows the extra pip next to Slack and doesn't add a Chrome icon to the launcher. If you open Chrome first, then things work as expected. Steps to reproduce 1. Install Slack snap and Chrome deb. 2. Join a Slack channel and open a hyperlink. Notice the extra pip next to Slack in the launcher. 3. Close Chrome and reopen it. 4. Open a URL from Slack again and notice the Chrome icon get added to the launcher. I'm not sure if this is an Ubuntu Dock or GNOME Shell issue. EDIT: Spoke to didrocks, he says that matching is done by Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+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 1914573] [NEW] Gnome desktop crash and return to login screen
Public bug reported: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1914573 Title: Gnome desktop crash and return to login screen Status in gnome-shell package in Ubuntu: New Bug description: The bug is that all at a sudden gnome reset to login screen. When i log again, the only "sound output" allowed is simulation, my devices are not displayed. I'm using - Ubuntu 20.04 (I upgraded from 18 some months ago, I don't think this bug was present at that moment but i used less my ubuntu station). - Portable PC The bug happen - When I use my PC with screen pluged directly : some times - When I use my docking station with 144Hz display in DVI (https://i-tec.pro/fr/produkt/u3hdmidvidock-4/) : quite frequently - When à Use my docking station and watch some full screen video : very frequently It seems to be linked to displayLink use, but not only because it happen too when i don't use the docking station. It seems to be frequently when i "Stress" the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 4 10:17:54 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-08 (1183 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-07-01 (217 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914573/+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 1857891] Re: Authentication code required for keyboardless device
** Changed in: gnome-bluetooth Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1857891 Title: Authentication code required for keyboardless device Status in GNOME Bluetooth: Fix Released Status in gnome-bluetooth package in Ubuntu: Triaged Bug description: Hi, I'm trying to connect a turn page pedal which acts partly as a two- button mouse (provides left- and right-click depending on the pedal you press) and partly as a keyboard (can send keycodes as enter, space, left, right, PgUp or PgDn...). It only has two pedals and no keyboard (see it on manufacturer's site: https://www.donnerdeal.com/products/donner-bluetooth-page-turner- pedal-for-tablets-ipad-rechargeable- black?_pos=4&_sid=b8e2efbcf&_ss=r). Whenever I try to connect it to bluez, it asks me for an authentication code which is impossible to provide, of course. I've search deeply but couldn't find any means to automatically "trust" my pedal. I've tried it on Windows and Android: it functions smoothly... Thank you in advance Some information: hciconfig -a hci0: Type: Primary Bus: USB BD Address: 00:16:38:CA:9D:64 ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN RX bytes:6435 acl:95 sco:0 events:271 errors:0 TX bytes:3151 acl:76 sco:0 commands:126 errors:0 Features: 0xff 0xff 0x8d 0xfe 0x9b 0xfd 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'HP-t520-Flexible-Series-TC' Class: 0x0c0104 Service Classes: Rendering, Capturing Device Class: Computer, Desktop workstation HCI Version: 2.0 (0x3) Revision: 0x2000 LMP Version: 2.0 (0x3) Subversion: 0x415c Manufacturer: Broadcom Corporation (15) bluetoothctl --version bluetoothctl: 5.48 bluetoothctl [NEW] Controller 00:16:38:CA:9D:64 HP-t520-Flexible-Series-TC [default] [NEW] Device 08:29:17:24:83:49 ZX1679 [NEW] Device 50:E6:66:03:72:8C Bluetooth Music Pedal Agent registered [Bluetooth Music Pedal]# show Controller 00:16:38:CA:9D:64 (public) Name: HP-t520-Flexible-Series-TC Alias: HP-t520-Flexible-Series-TC Class: 0x000c0104 Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: no [Bluetooth Music Pedal]# devices Device 08:29:17:24:83:49 ZX1679 Device 50:E6:66:03:72:8C Bluetooth Music Pedal [Bluetooth Music Pedal]# info 50:E6:66:03:72:8C Device 50:E6:66:03:72:8C (public) Name: Bluetooth Music Pedal Alias: Bluetooth Music Pedal Class: 0x0540 Icon: input-keyboard Paired: no Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v04E8p7021d0102 rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-25 (308 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Package: gnome-bluetooth 3.28.0-2ubuntu0.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-72-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-02-25 (308 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1857891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1913672] Re: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width
Is there anyone here who is experiencing this bug, or can reproduce it? -- 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/1913672 Title: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width Status in gnome-shell package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1~20.10.1, the problem page at https://errors.ubuntu.com/problem/4f12318421d8c95c357e2db953aa75b2cdcacdfa 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/gnome-shell/+bug/1913672/+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
