[Desktop-packages] [Bug 1915121] Re: /usr/bin/gnome-shell:11:on_stage_stage_views_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3323 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3323 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3323 Importance: Unknown Status: Unknown ** Summary changed: - /usr/bin/gnome-shell:11:on_stage_stage_views_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit + gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Committed ** Tags added: fixed-upstream ** Tags added: fixed-in-3.38.4 ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/1915121 Title: gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed 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/bc3566d950d42340582580239b618869c4c1d038 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/gnome-shell/+bug/1915121/+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 1915121] [NEW] gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signa
Public bug reported: 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/bc3566d950d42340582580239b618869c4c1d038 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/. ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: Fix Committed ** Tags: fixed-in-3.38.4 fixed-upstream 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/1915121 Title: gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed 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/bc3566d950d42340582580239b618869c4c1d038 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/gnome-shell/+bug/1915121/+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 1905010] Re: [snap] chromium forgets custom root certificates after each update
One workaround seems to be saving the chromium profile, deleting the
profile, restarting chromium and then move the saved profile back into
place.
I could now add our internal root CA without a problem. Will have a look
how chromium behaves with the next snap update.
--
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] Xorg crashes and return to login screen
I opened my session in Xorg this morgning. I only want one of Wayland or Xorg to work, which one you think we have a better chance? You already see some logs and probably have some idea about Xorg. My suggest is to continue for this day with Xorg, I'll send you logs each time I get the crash (I used to send you only one or two) for you to get as much as information I can. After that, maybe you'll have a better idea if continue with Xorg is a better solution, or switch to Wayland. Many thanks for help, -- 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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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] Xorg crashes and return to login screen
We should probably open a new bug about those problems in Wayland sessions. If you wanted to just focus on Wayland then we can close this bug about Xorg crashes. If you like? Or we can keep two bugs open, I don't mind. -- 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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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] Xorg crashes and return to login screen
Hello, You're true, I changed to Wayland because it seems to be the next default of ubuntu, and it's recommended to use with Displaylink (even if in the past it had some troubles). Whatever, I'll use Xorg as you ask and I'll send you next crash information. -- 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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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 1901391] Re: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement)
** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1901391 Title: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: I'm using gnome-shell with wayland (don't know if that matters), and, when I press CTRL-ALT-SHIFT-R, nothing happens. I checked my keyboard shortcuts, and this shortcut is supposed to trigger screencasting. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Oct 25 10:39:48 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-07 (260 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1901391/+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 1915096] Re: clock/calendar displays outdated information
I'm not completely sure what you mean. Are you talking about the notification from 10:10 still being displayed at 12:36? ** Summary changed: - clock/calendar does not have a refresh option + clock/calendar displays outdated information ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915096 Title: clock/calendar displays outdated information Status in gnome-shell package in Ubuntu: Incomplete Bug description: The drop-down calendar from the clock (in the middle of the top bar) does not offer a refresh option and consequently displays out-dated information (see attached). It needs a refresh-button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 13:25:24 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821CU, 5.4.1, 5.8.0-40-generic, x86_64: installed rtl8821CU, 5.4.1, 5.8.0-41-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-40-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] InstallationDate: Installed on 2021-01-14 (26 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=9dd289f2-eb84-4c73-92fb-e6050acc143d ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 2.48 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.48 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.ec.firmware.release: 5.57 dmi.modalias: dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: L1G76AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915096/+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 1914992] Re: gnome-calendar crashes after a few clicks when creating event or un/toggling which calendar to show
** Description changed: I am using gnome-calendar (3.36.2) on Linux Mint 20 (Ulyana), Cinnamon 4.6.7. I am able to replicate the crash by opening gnome-calendar, then clicking on "Manage your calendars" and toggling / untoggling different calendars at random. Here's a log from journalctl if it's of use: -- The job identifier is 27260. - Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.386][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:1041][info] BYTECOUNT: 3311031560, 118663140 - Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.387][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:942][info] peer: handshake at 1612777449 - "3 sec" ago Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: ** Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn systemd[1]: Started Process Core Dump (PID 249641/UID 0). -- Subject: A start job for unit systemd-coredump@41-249641-0.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support - -- + -- -- A start job for unit systemd-coredump@41-249641-0.service has finished successfully. - -- + -- -- The job identifier is 27350. Feb 08 01:44:16 saturn systemd-coredump[249642]: Process 249540 (gnome-calendar) of user 1000 dumped core. - - Stack trace of thread 249540: - #0 0x7f1ff002018b __GI_raise (libc.so.6 + 0x4618b) - #1 0x7f1fe859 __GI_abort (libc.so.6 + 0x25859) - #2 0x7f1ff0523b43 n/a (libglib-2.0.so.0 + 0x1db43) - #3 0x7f1ff0580b2f g_assertion_message_expr (libglib-2.0.so.0 + 0x7ab2f) - #4 0x5562ad7685a7 n/a (gnome-calendar + 0x455a7) - #5 0x7f1ff0645a56 n/a (libgobject-2.0.so.0 + 0x14a56) - #6 0x7f1ff0664b28 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33b28) - #7 0x7f1ff06650d3 g_signal_emit (libgobject-2.0.so.0 + 0x340d3) - #8 0x5562ad7825ec n/a (gnome-calendar + 0x5f5ec) - #9 0x7f1ff0557e6e g_main_context_dispatch (libglib-2.0.so.0 + 0x51e6e) - #10 0x7f1ff0558220 n/a (libglib-2.0.so.0 + 0x52220) - #11 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) - #12 0x7f1ff0773fd5 g_application_run (libgio-2.0.so.0 + 0xe2fd5) - #13 0x5562ad747532 main (gnome-calendar + 0x24532) - #14 0x7f1ff00010b3 __libc_start_main (libc.so.6 + 0x270b3) - #15 0x5562ad74757e _start (gnome-calendar + 0x2457e) - - Stack trace of thread 249544: - #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) - #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) - #2 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) - #3 0x7f1ff155799d n/a (libdconfsettings.so + 0xa99d) - #4 0x7f1ff0581911 n/a (libglib-2.0.so.0 + 0x7b911) - #5 0x7f1fef452609 start_thread (libpthread.so.0 + 0x9609) - #6 0x7f1ff00fc293 __clone (libc.so.6 + 0x122293) - - Stack trace of thread 249543: - #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) - #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) -
[Desktop-packages] [Bug 1915096] Re: clock/calendar does not have a refresh option
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915096 Title: clock/calendar does not have a refresh option Status in xorg package in Ubuntu: New Bug description: The drop-down calendar from the clock (in the middle of the top bar) does not offer a refresh option and consequently displays out-dated information (see attached). It needs a refresh-button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 13:25:24 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821CU, 5.4.1, 5.8.0-40-generic, x86_64: installed rtl8821CU, 5.4.1, 5.8.0-41-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-40-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] InstallationDate: Installed on 2021-01-14 (26 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=9dd289f2-eb84-4c73-92fb-e6050acc143d ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 2.48 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.48 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.ec.firmware.release: 5.57 dmi.modalias: dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: L1G76AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1915096/+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 1915003] Re: Always update the initramfs when changing power profile
IMHO, shall we have a kernel boot parameter so that the script in the initrd check and decide what to load and/or parameter to added. If that's too much work, maybe put that as a long-term goal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-prime source package in Focal: In Progress Status in nvidia-settings source package in Focal: In Progress Status in nvidia-prime source package in Groovy: In Progress Status in nvidia-settings source package in Groovy: In Progress Bug description: The different power profiles require loading the nvidia drivers with different options (or blacklisting them, in case of intel mode). We need to call update-initramfs whenever we switch to a different profile, or things may fall out sync, resulting in a failure. The update-initramfs command takes a few seconds, therefore we also need to provide feedback, so that users know that they have to wait for the operation to complete. For this reason, prime-select will provide a spinner on the command line, and nvidia-settings will show a progress dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1915096] [NEW] clock/calendar does not have a refresh option
You have been subscribed to a public bug: The drop-down calendar from the clock (in the middle of the top bar) does not offer a refresh option and consequently displays out-dated information (see attached). It needs a refresh-button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 13:25:24 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821CU, 5.4.1, 5.8.0-40-generic, x86_64: installed rtl8821CU, 5.4.1, 5.8.0-41-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-40-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] InstallationDate: Installed on 2021-01-14 (26 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=9dd289f2-eb84-4c73-92fb-e6050acc143d ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 2.48 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.48 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.ec.firmware.release: 5.57 dmi.modalias: dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: L1G76AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- clock/calendar does not have a refresh option https://bugs.launchpad.net/bugs/1915096 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915014] Re: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot
Please: 1. Open a Terminal window. 2. Reproduce the bug again. 3. After the problem has started run this in the Terminal window: journalctl -b0 > journal.txt 4. Attach the resulting text file here. Separately, please try some other kernel versions like: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.14/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.18/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.96/ and tell us if any of those exhibit the same bug. ** Tags added: 5.8-gfx ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1915014 Title: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot Status in mutter package in Ubuntu: Incomplete Bug description: Weird issue which has come to my system via updates - possibly the Linux kernel 5.8? Steps to repro: - Take a screenshot (prt scr) - Continue using the computer After I have taken a screenshot, my display gets quick black flashes when using other applications. Manipulating the screenshot with Pinta, opening web browser, etc.. Screen goes black for a second and then resumes normal operation. This does not happen before taking the screenshot, so it obviously triggers something. The system works and is usable, but the black flashes are pretty odd and distracting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:39:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1025:1367] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:1366] InstallationDate: Installed on 2020-05-16 (268 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Nitro AN515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=675bb42c-4c3c-461b-bce1-53e34e786eaa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 1.8 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd12/24/2019:br1.8:efr1.5:svnAcer:pnNitroAN515-43:pvrV1.08:rvnPK:rnOctavia_PKS:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915014/+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 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
** Summary changed: - Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 + Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 -- 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/1880405 Title: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+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 1915040] Re: gnome-shell is so laggy after waking up
*** This bug is a duplicate of bug 1880405 *** https://bugs.launchpad.net/bugs/1880405 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1880405, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1880405 Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 -- 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/1915040 Title: gnome-shell is so laggy after waking up Status in gnome-shell package in Ubuntu: New Bug description: Gnome-shell is so laggy and when I am loging in after automatic suspend it takes 5-20 mins to respond for just logging in, After logged it so laggy and freezes for sometime and sometimes it will say sorry the program gnome-shell crashed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: hostname 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: Mon Feb 8 21:54:00 2021 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.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/1915040/+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 1915089] Re: Update to 3.38.3 and SRU it
Marco, Maybe also cherry pick the fix for bug 1880405? It's a doozy. -- 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/1915089 Title: Update to 3.38.3 and SRU it Status in gnome-shell package in Ubuntu: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Icon grid behavior has some changes reverted which may lead to slight difference in look. Workspace switch fixes have been included, so workspace behavior should be checked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+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 1915061] Re: Applications - Wrong pagination when exiting from a folder
*** This bug is a duplicate of bug 1889102 *** https://bugs.launchpad.net/bugs/1889102 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1889102, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1889102 [ubuntu-dock] App grid has too many page dots on right -- 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/1915061 Title: Applications - Wrong pagination when exiting from a folder Status in gnome-shell package in Ubuntu: New Bug description: Whenever I click to see the contents of a folder (like the Utilities one) in the applications view and not launch any of the contained applications, the pagination gets messed up until I reboot the machine. I have 2 pages, but when it happens those 2 white dots in the right-hand side get replaced by 9, the first 8 (from top to bottom) of which if clicked go to the first page, and the last of which goes to the second/last page. However if I scroll down from the first page, the second one gets highlighted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:05:19 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-10 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.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/1915061/+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 1915026] Re: Souris inactive et écran figé
Thanks for the bug report. It appears gnome-shell has frozen or crashed but Xorg is still working. Next time the problem happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Open a Terminal and run: journalctl -b-1 > prevboot.txt 4. Attach the file 'prevboot.txt' here. Please also follow these steps to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Tags added: 5.8-gfx ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915026 Title: Souris inactive et écran figé Status in gnome-shell package in Ubuntu: Incomplete Bug description: Bug constaté lorsque firefox est ouvert. Une partie de l'écran sautille, la souris est mobile mais ne contrôle plus rien, plus aucun clic actif. Le clavier reste opérationnel et me permet d'ouvrir une console pour fermer firefox. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:55:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller [1043:81ea] InstallationDate: Installed on 2021-02-06 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2007 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0510 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915026/+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 1915025] Re: Update to 3.38.3 and SRU it
** Tags added: fixed-in-3.38.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1915025 Title: Update to 3.38.3 and SRU it Status in mutter package in Ubuntu: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on monitors handling during hotplug and updates, should not cause issues nor changes when using xrandr fractional scaling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915025/+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 1915089] Re: Update to 3.38.3 and SRU it
** Tags added: groovy hirsute ** Tags added: fixed-in-3.38.3 -- 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/1915089 Title: Update to 3.38.3 and SRU it Status in gnome-shell package in Ubuntu: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Icon grid behavior has some changes reverted which may lead to slight difference in look. Workspace switch fixes have been included, so workspace behavior should be checked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+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 1915023] Re: Fix an extension spamming gnome logs?
** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome- shell-extension-gamemode (Ubuntu) ** Summary changed: - Fix an extension spamming gnome logs? + Object .Gjs_gamemode_christian_kellner_me_extension_GameModeIndicator (0x5565b80a8c60), has been already deallocated — impossible to set any property on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1915023 Title: Object .Gjs_gamemode_christian_kellner_me_extension_GameModeIndicator (0x5565b80a8c60), has been already deallocated — impossible to set any property on it. Status in gnome-shell-extension-gamemode package in Ubuntu: New Bug description: So I have this issue were I downloaded the gamemode extension a long time ago and hade no issue. But in the past month I have been getting these errors in Gnome Logs being spammed hundreds of times https://github.com/gicmo/gamemode-extension/issues/35 Object .Gjs_gamemode_christian_kellner_me_extension_GameModeIndicator (0x5565b80a8c60), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Object St.Icon (0x5565b7d04800), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. So I have tried uninstalling and reinstalling the extension, errors still happen. I then just decided to leave it uninstalled but the errors still come. Unfortunately the creator Christian seems to have given up on updating the extension and last update was for Gnome 3.34 and has not been responsive. What can I do to fix this issue? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-gamemode/+bug/1915023/+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 1915014] Re: Screen goes occasionally black after taking a screenshot
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: amdgpu ** Summary changed: - Screen goes occasionally black after taking a screenshot + [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1915014 Title: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot Status in mutter package in Ubuntu: New Bug description: Weird issue which has come to my system via updates - possibly the Linux kernel 5.8? Steps to repro: - Take a screenshot (prt scr) - Continue using the computer After I have taken a screenshot, my display gets quick black flashes when using other applications. Manipulating the screenshot with Pinta, opening web browser, etc.. Screen goes black for a second and then resumes normal operation. This does not happen before taking the screenshot, so it obviously triggers something. The system works and is usable, but the black flashes are pretty odd and distracting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:39:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1025:1367] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:1366] InstallationDate: Installed on 2020-05-16 (268 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Nitro AN515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=675bb42c-4c3c-461b-bce1-53e34e786eaa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 1.8 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd12/24/2019:br1.8:efr1.5:svnAcer:pnNitroAN515-43:pvrV1.08:rvnPK:rnOctavia_PKS:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915014/+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] Xorg crashes and return to login screen
Thanks for all that. Confusingly you now seem to be getting hangs in the Intel kernel driver followed by gnome-shell crashes. This seems to be a different bug to what we were looking at before, probably caused by using Wayland instead of Xorg... févr. 08 10:51:19 PORTABLE-PPAQUIN kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 févr. 08 10:51:19 PORTABLE-PPAQUIN gnome-shell[3042]: GNOME Shell crashed with signal 6 févr. 08 10:51:19 PORTABLE-PPAQUIN gnome-shell[3042]: == Stack trace for context 0x55e1400292a0 == févr. 08 12:58:22 PORTABLE-PPAQUIN kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 févr. 08 12:58:22 PORTABLE-PPAQUIN gnome-shell[2676]: GNOME Shell crashed with signal 6 févr. 08 12:58:22 PORTABLE-PPAQUIN gnome-shell[2676]: == Stack trace for context 0x5618d81e35d0 == Please change back to 'Ubuntu' instead of 'Ubuntu on Wayland', and then follow the steps in comment #16. -- 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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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 1915025] Re: Update to 3.38.3 and SRU it
** Tags added: groovy hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1915025 Title: Update to 3.38.3 and SRU it Status in mutter package in Ubuntu: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on monitors handling during hotplug and updates, should not cause issues nor changes when using xrandr fractional scaling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915025/+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 1164016] Re: restore type-ahead find
** Bug watch removed: gitlab.gnome.org/GNOME/nautilus/-/issues #1154 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1154 ** Bug watch removed: gitlab.gnome.org/GNOME/nautilus/-/issues #1157 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1157 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1730612] Re: Enable Remote desktop feature during build
** Changed in: mutter (Ubuntu) Importance: Wishlist => Medium ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1730612 Title: Enable Remote desktop feature during build Status in Default settings and artwork for Baltix OS: New Status in mutter package in Ubuntu: In Progress Bug description: Currently there are no way to use Remote Desktop (Desktop sharing) and Screen Recording in Ubuntu 17.10 Wayland (default) session because Remote desktop feature isn't enabled during build :( Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Currently in mutter 3.26.1 and 3.26.2 (Artful and Bionic) build log I see this: mutter-3.26.1 [..] Wayland: yes Native (KMS) backend: yes EGLDevice:yes Remote desktop: no To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+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 1915092] [NEW] lib-gtk-3 / lib-gtk-3-dev NOT compatible
Public bug reported: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1915092 Title: lib-gtk-3 / lib-gtk-3-dev NOT compatible Status in gtk+3.0 package in Ubuntu: New Bug description: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1915092/+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 1915091] [NEW] Nautilus shows LXD storage pool in sidebar
Public bug reported: I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs storage pool called "default". Now Nautilus shows a "default" device in the sidebar despite the loop device not being intended for users to directly interact with. System: Ubuntu 20.04.2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Description changed: - I recently set up LXD on Ubuntu 20.04 with a file-backed btrfs storage - pool called "default". Now Nautilus shows a "default" device in the - sidebar despite the loop device not being intended for users to directly - interact with. + I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs + storage pool called "default". Now Nautilus shows a "default" device in + the sidebar despite the loop device not being intended for users to + directly interact with. + + System: Ubuntu 20.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1915091 Title: Nautilus shows LXD storage pool in sidebar Status in nautilus package in Ubuntu: New Bug description: I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs storage pool called "default". Now Nautilus shows a "default" device in the sidebar despite the loop device not being intended for users to directly interact with. System: Ubuntu 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915091/+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 1915089] [NEW] Update to 3.38.3 and SRU it
Public bug reported: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Icon grid behavior has some changes reverted which may lead to slight difference in look. Workspace switch fixes have been included, so workspace behavior should be checked. ** Affects: gnome-shell (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- 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/1915089 Title: Update to 3.38.3 and SRU it Status in gnome-shell package in Ubuntu: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Icon grid behavior has some changes reverted which may lead to slight difference in look. Workspace switch fixes have been included, so workspace behavior should be checked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+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 1865838] Re: no error displayed on failed fingerprint authentication
** Description changed: + [ Impact ] + + No fingerprint errors are exposed on fingerprint login failures. + from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. - Steps to reproduce issue: + + [ Test case ] + 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger - 4. after 5 times retry. There's no error popup, then re-try index finger still no any message remind users they can not try fingerprint anymore. + 4. Each time the wrong finger is used an error is shown + 5. After 3 times retries, an authentication error is shown, suggesting +to use another method. - It will confuse user. + [ Regression potential] - Suggest behavior: - 1. Each time user try fingerprint failed, show error message to remind user. - 2. When user exceed 5 time errors, show error message to remind user input password instead. + Wrong errors are shown during both fingerprint auth and other kinds of authentications. + Password failures aren't properly exposed. Verification can't restart on error. - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + --- + + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) - InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) - SourcePackage: gdm3 + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gdm3 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/1865838 Title: no error displayed on failed fingerprint authentication Status in gdm: New Status in OEM Priority Project: New Status in fprintd package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: In Progress Status in fprintd source package in Focal: Triaged Status in gnome-shell source package in Focal: In Progress Bug description: [ Impact ] No fingerprint errors are exposed on fingerprint login failures. from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. [ Test case ] 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger 4. Each time the wrong finger is used an error is shown 5. After 3 times retries, an authentication error is shown, suggesting to use another method. [ Regression potential] Wrong errors are shown during both fingerprint auth and other kinds of authentications. Password failures aren't properly exposed. Verification can't restart on error. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+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 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working
** Description changed: + [ Test case ] + In the user session lockscreen (gdm login screen is fine): - Lock the screen - Hit Enter - Hit Escape - Repeat - You'll see by checking watch -n1 "ps aux |grep gdm-session-worker" (or - just ps'ing after unlocked) that many gdm workers are left around and - never terminated. + Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing + after unlocked) gdm workers should not be running (a part the one used + for logging in). Fingerprint unlocking is particularly hit by this as the service may prevent further authentication to happen until the PAM module times out. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 + + [ Regression potential ] + + Authenticating at login screen or at unlock screen stops working after + wrong credentials have been used once or the request has been cancelled + via escape key. -- 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/1915066 Title: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: [ Test case ] In the user session lockscreen (gdm login screen is fine): - Lock the screen - Hit Enter - Hit Escape - Repeat Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing after unlocked) gdm workers should not be running (a part the one used for logging in). Fingerprint unlocking is particularly hit by this as the service may prevent further authentication to happen until the PAM module times out. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 [ Regression potential ] Authenticating at login screen or at unlock screen stops working after wrong credentials have been used once or the request has been cancelled via escape key. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915066/+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] Re: [upstream] Firefox 85 hangs at startup
This bug was fixed in the package firefox - 85.0.1+build1-0ubuntu0.20.04.1 --- firefox (85.0.1+build1-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (85.0.1+build1) -- Olivier Tilloy Fri, 05 Feb 2021 12:54:22 +0100 ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Released -- 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: Fix Released 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 1914147] Re: [upstream] Firefox 85 hangs at startup
This bug was fixed in the package firefox - 85.0.1+build1-0ubuntu0.18.04.1 --- firefox (85.0.1+build1-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (85.0.1+build1) -- Olivier Tilloy Fri, 05 Feb 2021 12:50:03 +0100 -- 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: Fix Released 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 1914147] Re: [upstream] Firefox 85 hangs at startup
This bug was fixed in the package firefox - 85.0.1+build1-0ubuntu0.20.10.1 --- firefox (85.0.1+build1-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (85.0.1+build1) -- Olivier Tilloy Fri, 05 Feb 2021 12:56:13 +0100 ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Released ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Released -- 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: Fix Released 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 1914450] Re: Autopkgtests started failing on xenial
This bug was fixed in the package firefox - 85.0.1+build1-0ubuntu0.16.04.1 --- firefox (85.0.1+build1-0ubuntu0.16.04.1) xenial; urgency=medium * New upstream release (85.0.1+build1) -- Olivier Tilloy Fri, 05 Feb 2021 12:49:06 +0100 ** Changed in: firefox (Ubuntu) Status: Fix Committed => Fix Released -- 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/1914450 Title: Autopkgtests started failing on xenial Status in firefox package in Ubuntu: Fix Released Bug description: This is caused by the virtualenv wrapper script that by default installs the latest version of pip. Since version 21.0 (released on 2021-01-23), pip dropped support for Python 3.5, which is what we have in xenial. So the script needs to be modified to pin the version of pip to 20.x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914450/+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 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3654 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 Importance: Unknown Status: Unknown -- 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/1915066 Title: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: In the user session lockscreen (gdm login screen is fine): - Lock the screen - Hit Enter - Hit Escape - Repeat You'll see by checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing after unlocked) that many gdm workers are left around and never terminated. Fingerprint unlocking is particularly hit by this as the service may prevent further authentication to happen until the PAM module times out. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915066/+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 1915066] [NEW] Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working
Public bug reported: In the user session lockscreen (gdm login screen is fine): - Lock the screen - Hit Enter - Hit Escape - Repeat You'll see by checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing after unlocked) that many gdm workers are left around and never terminated. Fingerprint unlocking is particularly hit by this as the service may prevent further authentication to happen until the PAM module times out. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 ** Affects: gnome-shell (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: fingerprint -- 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/1915066 Title: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working Status in gnome-shell package in Ubuntu: In Progress Bug description: In the user session lockscreen (gdm login screen is fine): - Lock the screen - Hit Enter - Hit Escape - Repeat You'll see by checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing after unlocked) that many gdm workers are left around and never terminated. Fingerprint unlocking is particularly hit by this as the service may prevent further authentication to happen until the PAM module times out. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915066/+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 1877277] Re: Mounting USB drive spins up unrelated drive(s)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1877277 Title: Mounting USB drive spins up unrelated drive(s) Status in udisks2 package in Ubuntu: Confirmed Bug description: When mounting or unmounting a USB drive (USB pendrive, USB HDD, whatever) via file manager, udiskd wakes my sleeping, completely unrelated internal data HD. This is possibly related to https://github.com/storaged-project/udisks/pull/656 Not sure in which release this will be fixed, currently installed version is: libudisks2-0:amd642.8.4-1ubuntu1 udisks2 2.8.4-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.snapd.rules Date: Thu May 7 11:48:49 2020 InstallationDate: Installed on 2020-05-01 (6 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 2351BH6 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2351BH6 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn2351BH6:pvrThinkPadT430:rvnLENOVO:rn2351BH6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2351BH6 dmi.product.sku: LENOVO_MT_2351 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1877277/+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 1915061] [NEW] Applications - Wrong pagination when exiting from a folder
Public bug reported: Whenever I click to see the contents of a folder (like the Utilities one) in the applications view and not launch any of the contained applications, the pagination gets messed up until I reboot the machine. I have 2 pages, but when it happens those 2 white dots in the right-hand side get replaced by 9, the first 8 (from top to bottom) of which if clicked go to the first page, and the last of which goes to the second/last page. However if I scroll down from the first page, the second one gets highlighted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:05:19 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-10 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1915061 Title: Applications - Wrong pagination when exiting from a folder Status in gnome-shell package in Ubuntu: New Bug description: Whenever I click to see the contents of a folder (like the Utilities one) in the applications view and not launch any of the contained applications, the pagination gets messed up until I reboot the machine. I have 2 pages, but when it happens those 2 white dots in the right-hand side get replaced by 9, the first 8 (from top to bottom) of which if clicked go to the first page, and the last of which goes to the second/last page. However if I scroll down from the first page, the second one gets highlighted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:05:19 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-10 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.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/1915061/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
This bug was fixed in the package software-properties - 0.99.6
---
software-properties (0.99.6) hirsute; urgency=medium
[ William 'jawn-smith' Wilson ]
* Fixing an incorrect variable being passed to GTK message dialog creation
function (LP: #1829401)
[ Shivaram Lingamneni ]
* Update livepatch code to remove use of python-requests-unixsocket;
the usage is trivial and we can remove the dependency
-- Brian Murray Mon, 01 Feb 2021 16:08:37 -0800
** Changed in: software-properties (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in software-properties package in Ubuntu:
Fix Released
Status in software-properties source package in Eoan:
Won't Fix
Status in software-properties source package in Focal:
Fix Committed
Status in software-properties source package in Groovy:
Fix Committed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
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/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
[Impact]
* If selected mirrors are not reachable or have
expired GPG keys, software-properties-gtk
would crash
[Test Case]
* Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
* Find your locale in this file and add a non-existent URL
to the list
* Run software-properties-gtk and choose your newly added
URL from the "Download From" dropdown menu
* Press "Close" in the bottom right, and when
prompted press "Reload"
* You should be presented with an error window rather than
the program crashing
[Where problems could occur]
* The new error window binds to the parent window. If the
parent window has gotten into a bad state this could
cause problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
You can close VLC or just jump to another time location in the video then the log-spam will stop too. Workaround: https://unix.stackexchange.com/a/633378/20661 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Indeed, once focal is updated, bionic is next in line. The status of the corresponding bug task will be updated accordingly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1915003] Re: Always update the initramfs when changing power profile
** Changed in: nvidia-settings (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-prime source package in Focal: In Progress Status in nvidia-settings source package in Focal: In Progress Status in nvidia-prime source package in Groovy: In Progress Status in nvidia-settings source package in Groovy: In Progress Bug description: The different power profiles require loading the nvidia drivers with different options (or blacklisting them, in case of intel mode). We need to call update-initramfs whenever we switch to a different profile, or things may fall out sync, resulting in a failure. The update-initramfs command takes a few seconds, therefore we also need to provide feedback, so that users know that they have to wait for the operation to complete. For this reason, prime-select will provide a spinner on the command line, and nvidia-settings will show a progress dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1164016] Re: restore type-ahead find
** Changed in: nautilus Importance: Wishlist => Unknown ** Changed in: nautilus Status: Expired => Unknown ** Changed in: nautilus Remote watch: GNOME Bug Tracker #681871 => bugzilla.gnome.org/ #681871 ** Bug watch removed: GNOME Bug Tracker #681871 https://gitlab.gnome.org/681871 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1915040] [NEW] gnome-shell is so laggy after waking up
Public bug reported: Gnome-shell is so laggy and when I am loging in after automatic suspend it takes 5-20 mins to respond for just logging in, After logged it so laggy and freezes for sometime and sometimes it will say sorry the program gnome-shell crashed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: hostname 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: Mon Feb 8 21:54:00 2021 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1915040 Title: gnome-shell is so laggy after waking up Status in gnome-shell package in Ubuntu: New Bug description: Gnome-shell is so laggy and when I am loging in after automatic suspend it takes 5-20 mins to respond for just logging in, After logged it so laggy and freezes for sometime and sometimes it will say sorry the program gnome-shell crashed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: hostname 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: Mon Feb 8 21:54:00 2021 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.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/1915040/+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 1915039] [NEW] Firefox is so laggy after wake up sleep
Public bug reported: When my device is idle, it just lock itself and wait. When I am logging in and switching tabs between firefox, it is so laggy that it takes upto 4-10 minutes to respond. And also sometimes it crashes and I have to restart my sytsem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 85.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: hostname 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.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balashanmugam 1437 F pulseaudio /dev/snd/pcmC0D0p: balashanmugam 1437 F...m pulseaudio /dev/snd/timer: balashanmugam 1437 f pulseaudio BuildID: 20210118153634 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 21:47:55 2021 ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.0.1 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.0.0/24 dev ens33 proto kernel scope link src 192.168.0.118 metric 100 NoProfiles: True ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16722896.B64.2008100651 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1915039 Title: Firefox is so laggy after wake up sleep Status in firefox package in Ubuntu: New Bug description: When my device is idle, it just lock itself and wait. When I am logging in and switching tabs between firefox, it is so laggy that it takes upto 4-10 minutes to respond. And also sometimes it crashes and I have to restart my sytsem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 85.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: hostname 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.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balashanmugam 1437 F pulseaudio /dev/snd/pcmC0D0p: balashanmugam 1437 F...m pulseaudio /dev/snd/timer: balashanmugam 1437 f pulseaudio BuildID: 20210118153634 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 21:47:55 2021 ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.0.1 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.0.0/24 dev ens33 proto kernel scope link src 192.168.0.118 metric 100 NoProfiles: True ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16722896.B64.2008100651 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name:
Re: [Desktop-packages] [Bug 1802039]
Yeah I've been having trouble with it still in Ubuntu MATE 20.10. Also appears to be an issue in Vivaldi. On Mon, Feb 8, 2021 at 3:00 AM Alexander Browne <1802...@bugs.launchpad.net> wrote: > I haven't used MATE for a couple years now, so I'm not sure myself. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1802039 > > Title: > Firefox without titlebar has visual glitches when > maximizing/unmaximizing > > Status in Mozilla Firefox: > New > Status in firefox package in Ubuntu: > Confirmed > > Bug description: > There is a relatively new feature in Firefox that allows you to hide > the title bar (I'm running Firefox 63.0), which is very helpful when > you have a low resolution screen. However, when changing the > maximization state, some visual gitches occur. I didn't notice this > glitching when running Kubuntu or Ubuntu Budgie on two separate > systems. > > To try this, go to your Firefox Menu, click Customize, and uncheck > "Title Bar" at the bottom left. Then unmaximize the window and then > remaximize it. > > What it's supposed to look like: https://pasteboard.co/HM0h8oB.png > Unmaximized (note the large transparent section): > https://pasteboard.co/HM0hpud.png > Remaximized (note the duplicate set of close buttons): > https://pasteboard.co/HM0hCf5.png > > Also another interesting bug I noticed...if you try to use Firefox in > the no titlebar state with the global menu enabled (e.g. Contemporary, > Cupertino, or Mutiny panel layouts), the window buttons are not placed > correctly, being on the window border. > > Systems tried on: > > Laptop, Dell Latitude E5430 - Intel Core i3-3120M dual core with > hyperthreading, 12 GB DDR3 Memory, Intel 4000 Graphics, Built-in LCD at > 1366x768 (screenshots from this system) > Desktop, Lenovo ThinkCentre M79 - AMD A4-6300B 3.7 GHz dual core, 8 GB > DDR3 Memory, AMD 8370D Graphics, HP 2009f Monitor at 1600x900 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/firefox/+bug/1802039/+subscriptions > -- 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/1802039 Title: Firefox without titlebar has visual glitches when maximizing/unmaximizing Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: There is a relatively new feature in Firefox that allows you to hide the title bar (I'm running Firefox 63.0), which is very helpful when you have a low resolution screen. However, when changing the maximization state, some visual gitches occur. I didn't notice this glitching when running Kubuntu or Ubuntu Budgie on two separate systems. To try this, go to your Firefox Menu, click Customize, and uncheck "Title Bar" at the bottom left. Then unmaximize the window and then remaximize it. What it's supposed to look like: https://pasteboard.co/HM0h8oB.png Unmaximized (note the large transparent section): https://pasteboard.co/HM0hpud.png Remaximized (note the duplicate set of close buttons): https://pasteboard.co/HM0hCf5.png Also another interesting bug I noticed...if you try to use Firefox in the no titlebar state with the global menu enabled (e.g. Contemporary, Cupertino, or Mutiny panel layouts), the window buttons are not placed correctly, being on the window border. Systems tried on: Laptop, Dell Latitude E5430 - Intel Core i3-3120M dual core with hyperthreading, 12 GB DDR3 Memory, Intel 4000 Graphics, Built-in LCD at 1366x768 (screenshots from this system) Desktop, Lenovo ThinkCentre M79 - AMD A4-6300B 3.7 GHz dual core, 8 GB DDR3 Memory, AMD 8370D Graphics, HP 2009f Monitor at 1600x900 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1802039/+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 1865838] Re: no error displayed on failed fingerprint authentication
** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-shell (Ubuntu Focal) Status: Triaged => In Progress -- 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/1865838 Title: no error displayed on failed fingerprint authentication Status in gdm: New Status in OEM Priority Project: New Status in fprintd package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: In Progress Status in fprintd source package in Focal: Triaged Status in gnome-shell source package in Focal: In Progress Bug description: from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. Steps to reproduce issue: 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger 4. after 5 times retry. There's no error popup, then re-try index finger still no any message remind users they can not try fingerprint anymore. It will confuse user. Suggest behavior: 1. Each time user try fingerprint failed, show error message to remind user. 2. When user exceed 5 time errors, show error message to remind user input password instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Hi @osomon,
happy to see there is progress with TB and 20.04 ("We’ve decided to
update Thunderbird in Ubuntu 20.04 from 68.x to 78.x. This is a major
version update. [1]). And as the title of the discourse states it's
about the LTS version, does this mean the 78.x version tree is also
coming to Ubuntu 18.04 (which by definition [2] is also a LTS version) ?
Thanks
[1] https://discourse.ubuntu.com/t/thunderbird-lts-update/20819
[2] https://wiki.ubuntu.com/Releases
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1895643
Title:
Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Status in thunderbird package in Ubuntu:
Fix Released
Status in thunderbird source package in Bionic:
Triaged
Status in thunderbird source package in Focal:
Fix Committed
Status in thunderbird source package in Groovy:
Fix Released
Bug description:
Upstream Thunderbird version 78.2.2 should be a candidate for
backporting to stable Ubuntu releases.
I've successfully built 78.2.1 against both with forcing nodejs
version (20.04, 18.04) and disabling AV1 support due to too old nasm
(18.04). Attaching debdiffs here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1915030] [NEW] ubuntu-desktop is slow and resolution in booting is incorrect
Public bug reported: ubuntu-desktop is slow at starting and also when I click show applications (That 9 dots on the Dock) it shows slowly and also animating incorrectly. It is so slow that barely I can select activites and click show applications. And also ubuntu-desktop is taking up system resources highly. sometimes when I open and close show applications it opens and before closing it shows wallpaper for few seconds and then closes. I am a windows user and curious to know linux works. Windows 8.1 is way faster than ubuntu booting on a virtual machine with just 2 gig of memory. Both are same specs 2 gigs of ram and 1 core and 2 processors. I don't know what causes this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.2 ProcVersionSignature: hostname 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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 20:50:59 2021 InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1915030 Title: ubuntu-desktop is slow and resolution in booting is incorrect Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-desktop is slow at starting and also when I click show applications (That 9 dots on the Dock) it shows slowly and also animating incorrectly. It is so slow that barely I can select activites and click show applications. And also ubuntu-desktop is taking up system resources highly. sometimes when I open and close show applications it opens and before closing it shows wallpaper for few seconds and then closes. I am a windows user and curious to know linux works. Windows 8.1 is way faster than ubuntu booting on a virtual machine with just 2 gig of memory. Both are same specs 2 gigs of ram and 1 core and 2 processors. I don't know what causes this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.2 ProcVersionSignature: hostname 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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 20:50:59 2021 InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1915030/+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 1914868] Re: gnome-software-dev doesn't contain all the header files in /usr/include/gnome-software
** Changed in: gnome-software (Ubuntu) Status: New => Confirmed ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1914868 Title: gnome-software-dev doesn't contain all the header files in /usr/include/gnome-software Status in gnome-software package in Ubuntu: Confirmed Bug description: I have tried to compile example plugin mentioned here: https://gitlab.gnome.org/GNOME/gnome-software/-/blob/master/contrib/gs-plugin-example.c and here: https://developer.gnome.org/gnome-software/stable/plugins.html I have installed package gnome-software-dev (required for compilation) But I am not able to compile it: $ gcc -shared -o libgs_plugin_example.so gs-plugin-example.c -fPIC `pkg-config --libs --cflags gnome-software` -DI_KNOW_THE_GNOME_SOFTWARE_API_IS_SUBJECT_TO_CHANGE In file included from gs-plugin-example.c:5: /usr/include/gnome-software/gnome-software.h:16:10: fatal error: gs-app-collation.h: No such file or directory 16 | #include | ^~~~ compilation terminated. It appears package gnome-software-dev lacks some headers. This issue was already reported here: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1119#note_1002516 My system: Description: Ubuntu 20.04.2 LTS Release: 20.04 Package version: apt-cache policy gnome-software-dev gnome-software-dev: Zainstalowana: 3.36.1-0ubuntu0.20.04.0 Kandydująca: 3.36.1-0ubuntu0.20.04.0 Tabela wersji: *** 3.36.1-0ubuntu0.20.04.0 500 500 http://pl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.0-0ubuntu3 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1914868/+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 1903632]
*** Bug 140243 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1903632/+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 1915026] [NEW] Souris inactive et écran figé
Public bug reported: Bug constaté lorsque firefox est ouvert. Une partie de l'écran sautille, la souris est mobile mais ne contrôle plus rien, plus aucun clic actif. Le clavier reste opérationnel et me permet d'ouvrir une console pour fermer firefox. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:55:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller [1043:81ea] InstallationDate: Installed on 2021-02-06 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2007 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0510 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0510:bd05/22/2007:br8.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915026 Title: Souris inactive et écran figé Status in xorg package in Ubuntu: New Bug description: Bug constaté lorsque firefox est ouvert. Une partie de l'écran sautille, la souris est mobile mais ne contrôle plus rien, plus aucun clic actif. Le clavier reste opérationnel et me permet d'ouvrir une console pour fermer firefox. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 15:55:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G965 Integrated Graphics Controller [8086:29a2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82G965 Integrated Graphics Controller [1043:81ea] InstallationDate: Installed on 2021-02-06 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=7fc41ded-4d1e-43f9-924a-2e58d834e881 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2007 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0510 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-VM
[Desktop-packages] [Bug 1914178] Re: package firefox 84.0.2+build1-0ubuntu0.20.10.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/firefox/omni.ja » vers « /usr
>From DpkgTerminalLog.txt: Dépaquetage de firefox (85.0+build1-0ubuntu0.20.10.1) sur (84.0.2+build1-0ubuntu0.20.10.1) ... dpkg-deb (sous-processus) : décompression du membre de l'archive : erreur LZMA : les données compressées sont corrompues This means that somehow the update that was downloaded was corrupted. I suggest re-installing: sudo apt reinstall firefox ** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1914178 Title: package firefox 84.0.2+build1-0ubuntu0.20.10.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/firefox/omni.ja » vers « /usr/lib/firefox/omni.ja.dpkg-new » : fin de fichier ou de flux inattendue Status in firefox package in Ubuntu: Invalid Bug description: No further information available ProblemType: Package DistroRelease: Ubuntu 20.10 Package: firefox 84.0.2+build1-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.3 AptOrdering: firefox:amd64: Install firefox-locale-en:amd64: Install firefox-locale-fr:amd64: Install libmysqlclient21:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yvan 3192 F pulseaudio /dev/snd/controlC0: yvan 3192 F pulseaudio /dev/snd/controlC1: yvan 3192 F pulseaudio BuildID: 20210105180113 CasperMD5CheckResult: skip Channel: Unavailable Date: Mon Feb 1 23:09:11 2021 DpkgHistoryLog: Start-Date: 2021-02-01 23:09:03 Commandline: apt-get upgrade Requested-By: yvan (1000) Upgrade: firefox-locale-en:amd64 (84.0.2+build1-0ubuntu0.20.10.1, 85.0+build1-0ubuntu0.20.10.1), firefox-locale-fr:amd64 (84.0.2+build1-0ubuntu0.20.10.1, 85.0+build1-0ubuntu0.20.10.1), libmysqlclient21:amd64 (8.0.22-0ubuntu0.20.10.2, 8.0.23-0ubuntu0.20.10.1), firefox:amd64 (84.0.2+build1-0ubuntu0.20.10.1, 85.0+build1-0ubuntu0.20.10.1) ErrorMessage: impossible de copier les données extraites pour « ./usr/lib/firefox/omni.ja » vers « /usr/lib/firefox/omni.ja.dpkg-new » : fin de fichier ou de flux inattendue ForcedLayersAccel: False IpRoute: default via 192.168.0.254 dev enp4s0 proto dhcp metric 100 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.30 metric 100 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 84.0.2+build1-0ubuntu0.20.10.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/firefox/omni.ja » vers « /usr/lib/firefox/omni.ja.dpkg-new » : fin de fichier ou de flux inattendue UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1914178/+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 1915025] [NEW] Update to 3.38.3 and SRU it
Public bug reported: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on monitors handling during hotplug and updates, should not cause issues nor changes when using xrandr fractional scaling. ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1915025 Title: Update to 3.38.3 and SRU it Status in mutter package in Ubuntu: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on monitors handling during hotplug and updates, should not cause issues nor changes when using xrandr fractional scaling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915025/+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 1914821] Re: Disks won't execute
** Project changed: canonical-identity-provider => gnome-disk-utility (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1914821 Title: Disks won't execute Status in gnome-disk-utility package in Ubuntu: New Bug description: a@a-desktop:~$ gnome-disks (gnome-disks:11342): GNOME-Disks-ERROR **: 14:09:11.170: Error getting udisks client: Timeout was reached Trace/breakpoint trap (core dumped) a@a-desktop:~$ a@a-desktop:~$ uname -a Linux a-desktop 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux a@a-desktop:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1914821/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
The update is now sitting in the focal-proposed unapproved queue, and is being carefully reviewed by the SRU team. Please bear with us while we work to ensure the upgrade goes smoothly for everyone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
For future reference, a rationale and summary have been shared on Ubuntu's discourse: https://discourse.ubuntu.com/t/thunderbird-lts- update/20819. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+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 1914821] [NEW] Disks won't execute
You have been subscribed to a public bug: a@a-desktop:~$ gnome-disks (gnome-disks:11342): GNOME-Disks-ERROR **: 14:09:11.170: Error getting udisks client: Timeout was reached Trace/breakpoint trap (core dumped) a@a-desktop:~$ a@a-desktop:~$ uname -a Linux a-desktop 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux a@a-desktop:~$ ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- Disks won't execute https://bugs.launchpad.net/bugs/1914821 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
wizard@hp:~$ cat /proc/asound/card*/codec* | grep Codec Codec: Realtek ALC3227 Codec: Intel Braswell HDMI wizard@hp:~$ sudo lspci -vvv | grep -A 40 -i audio [sudo] пароль для wizard: 00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 35) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s (downgraded), Width x0 (downgraded) TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ wizard@hp:~$ -- 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/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I have a new laptop HP-15-BS576TX which has this Intel Corporation Sunrise Point-LP HD Audio. 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) The laptop sound works perfectly fine in Windows 10 with realtek drivers. However, in Ubuntu 17.10, the volume is significantly low, that I've to scroll the volume slider above 100% mark in pulseaudio to the maximum to get acceptable level of sound. I suspect the sound quality also is low (mono-like), may be not coming from all speakers (perhaps subwoofer exist for this model). Also alsamixer shows the speaker volume at the maximum. Details about the audio hardware are below: :~$ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company Device 832b Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- /proc/asound/card0/codec#0 <== Codec: Realtek ALC3227 ==> /proc/asound/card0/codec#2 <== Codec: Intel Kabylake HDMI :~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I have gone through Linux kernel sources ALSA and Snd-HDA lists and unable to find any optimizations for this laptop. Here is the relevant dmesg details: [ 15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 16.310510] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 16.310512] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 16.451397] input: HDA Intel PCH
[Desktop-packages] [Bug 1915023] [NEW] Fix an extension spamming gnome logs?
Public bug reported: So I have this issue were I downloaded the gamemode extension a long time ago and hade no issue. But in the past month I have been getting these errors in Gnome Logs being spammed hundreds of times https://github.com/gicmo/gamemode-extension/issues/35 Object .Gjs_gamemode_christian_kellner_me_extension_GameModeIndicator (0x5565b80a8c60), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Object St.Icon (0x5565b7d04800), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. So I have tried uninstalling and reinstalling the extension, errors still happen. I then just decided to leave it uninstalled but the errors still come. Unfortunately the creator Christian seems to have given up on updating the extension and last update was for Gnome 3.34 and has not been responsive. What can I do to fix this issue? ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1915023 Title: Fix an extension spamming gnome logs? Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: So I have this issue were I downloaded the gamemode extension a long time ago and hade no issue. But in the past month I have been getting these errors in Gnome Logs being spammed hundreds of times https://github.com/gicmo/gamemode-extension/issues/35 Object .Gjs_gamemode_christian_kellner_me_extension_GameModeIndicator (0x5565b80a8c60), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Object St.Icon (0x5565b7d04800), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. So I have tried uninstalling and reinstalling the extension, errors still happen. I then just decided to leave it uninstalled but the errors still come. Unfortunately the creator Christian seems to have given up on updating the extension and last update was for Gnome 3.34 and has not been responsive. What can I do to fix this issue? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1915023/+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 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Won't Fix => In Progress ** Tags added: fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1841774 Title: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js) Status in mutter package in Ubuntu: In Progress Bug description: I was closing the dialog of the "software and updates" tools (I was checking the repositories and ppa), but the entire desktop went into freeze, no mouse movement, at the click no action, I pressed the keys "ctrl + alt + f3 "and I went into a tty session, from there I recorded the logs via:" journalctl -f> log ", and I restarted. This is one part of the log, but it seems to repeat itself, I have attached a file with a longer log. -- Logs begin at Tue 2019-02-19 00:29:40 CET. -- ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:51:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (190 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841774/+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 745299] Fix included in openstack/tripleo-validations 11.4.0
This issue was fixed in the openstack/tripleo-validations 11.4.0 release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/745299 Title: Desktop Audio CD context menu compress option defaults to tar.gz Status in nautilus package in Ubuntu: Invalid Bug description: Binary package hint: nautilus Ubuntu 11.04 Alpha 3 (Natty Narwhal) i386 Audio CD mounted in drive shows icon on desktop. Right-click > Compress defaults to tar.gz which isn't going to work in any media player. Is FLAC too much to ask? Nice to see it mount as a directory full of WAV files which isn't a F/OSS standard: http://en.wikipedia.org/wiki/WAV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/745299/+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 1915003] Re: Always update the initramfs when changing power profile
** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-prime source package in Focal: In Progress Status in nvidia-settings source package in Focal: New Status in nvidia-prime source package in Groovy: In Progress Status in nvidia-settings source package in Groovy: In Progress Bug description: The different power profiles require loading the nvidia drivers with different options (or blacklisting them, in case of intel mode). We need to call update-initramfs whenever we switch to a different profile, or things may fall out sync, resulting in a failure. The update-initramfs command takes a few seconds, therefore we also need to provide feedback, so that users know that they have to wait for the operation to complete. For this reason, prime-select will provide a spinner on the command line, and nvidia-settings will show a progress dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+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 1915014] [NEW] Screen goes occasionally black after taking a screenshot
Public bug reported: Weird issue which has come to my system via updates - possibly the Linux kernel 5.8? Steps to repro: - Take a screenshot (prt scr) - Continue using the computer After I have taken a screenshot, my display gets quick black flashes when using other applications. Manipulating the screenshot with Pinta, opening web browser, etc.. Screen goes black for a second and then resumes normal operation. This does not happen before taking the screenshot, so it obviously triggers something. The system works and is usable, but the black flashes are pretty odd and distracting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:39:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1025:1367] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:1366] InstallationDate: Installed on 2020-05-16 (268 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Nitro AN515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=675bb42c-4c3c-461b-bce1-53e34e786eaa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 1.8 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd12/24/2019:br1.8:efr1.5:svnAcer:pnNitroAN515-43:pvrV1.08:rvnPK:rnOctavia_PKS:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915014 Title: Screen goes occasionally black after taking a screenshot Status in xorg package in Ubuntu: New Bug description: Weird issue which has come to my system via updates - possibly the Linux kernel 5.8? Steps to repro: - Take a screenshot (prt scr) - Continue using the computer After I have taken a screenshot, my display gets quick black flashes when using other applications. Manipulating the screenshot with Pinta, opening web browser, etc.. Screen goes black for a second and then resumes normal operation. This does not happen before taking the screenshot, so it obviously triggers something. The system works and is usable, but the black flashes are pretty odd and distracting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:39:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1025:1367] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:1366] InstallationDate: Installed on 2020-05-16 (268 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen
Another time, another log :). Thanks for help. ** Attachment added: "curboot2.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461238/+files/curboot2.txt -- 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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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 1908469] Re: Cannot install .deb packages opened from Firefox
tmp will not work for some applications; any link explaining exactly why/when/how? is it just because of snap - or other things too? -- 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/1908469 Title: Cannot install .deb packages opened from Firefox Status in firefox package in Ubuntu: Confirmed Bug description: Suppose in Firefox you click a link to a .deb package. A dialog named "Opening [filename].deb" opens. If you select "Open with", then the .deb file is downloaded, placed in /tmp/mozilla_[username]0/ directory, then Software Install (as named in the Firefox dialog) is started on that .deb file. Next, Software Install loads and fails with "Failed to install file: not supported". If on the other hand, in Firefox's "Opening [filename].deb" dialog, if I select "Save File" instead, the .deb file ends up in the user's Downloads directory. Software Install works fine with the package there. I don't want to get too much into solutioning or "why". The main point of this bug is that I should not get a weird error just because I selected "Open with" instead of "Save File". This happens with a vanilla install of Ubuntu, with nothing else installed, so the product isn't working in an intuitive way. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 19:54:01 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-12-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1908469/+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 1096363] Re: Add '--help' to hybrid-detect
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Triaged => Won't Fix
--
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/1096363
Title:
Add '--help' to hybrid-detect
Status in ubuntu-drivers-common package in Ubuntu:
Won't Fix
Bug description:
When looking at /etc/init/hybrid-gfx.conf or hybrid-detect one could
maybe guess its use, but there is no description in the upstart job,
no manpage, no 'hybrid-detect --help' or similar.
I propose adding an '--help' option to hybrid-detect with an output
like this:
printf("Usage: %s\n", argv[0]);
printf("Detect if the available GPUs were changed (e.g. by BIOS settings)
since the last run using %s.\n", FILENAME);
printf("In this case detect which GPU in a hybrid graphics configuration
should be used.\n");
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1096363/+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 1472109] Re: gpu-manager crashes
** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Incomplete -- 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/1472109 Title: gpu-manager crashes Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug description: gpu-manager has no man page and when running with -h it crashes: $ gpu-manager -h Segmentation fault (core dumped) $ gpu-manager --help gpu-manager: unrecognized option '--help' If this is really something that should not be run, better hide it away from $PATH... But the command line option handling should be fixed anyway. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-drivers-common 1:0.2.91.9 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 7 08:55:08 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-08 (89 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1472109/+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 1492873] Re: nvidiadetector.py: neglects to match on class code 0302 3D Controller
nvidia-detector was never meant to be used with ubuntu-drivers. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Triaged => Invalid -- 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/1492873 Title: nvidiadetector.py: neglects to match on class code 0302 3D Controller Status in ubuntu-drivers-common package in Ubuntu: Invalid Bug description: Helping a user on IRC where ubuntu-drivers failed to detect 0a:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 850M] [10de:1391] (rev a2) Looking at the source-code I noticed that /usr/lib/python3/dist- packages/NvidiaDetector/nvidiadetector.py::detection() is not matching on class 0302 (despite the associated fake entry comment for debugging suggesting it) The work-around is to amend the code thus: sudo sed -i 's/0300/(0300|0302)/' /usr/lib/python3/dist- packages/NvidiaDetector/nvidiadetector.py Running ubuntu-drivers now matches the 3D Controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1492873/+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 1878245] Re: Cannot use PRIME render offloading on AMD CPUs
This is fixed in Focal. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Fix Released -- 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/1878245 Title: Cannot use PRIME render offloading on AMD CPUs Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: Release: Ubuntu 20.04 Package version: 1:0.8.1 gpu-manager will only configure X for PRIME render offloading when using an Intel CPU with integrated graphics. AMD CPUs also have integrated graphics that can support GPU offloading. Upstream report: https://github.com/tseliot/ubuntu-drivers- common/issues/39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1878245/+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]
Do we know when/why this started? Any idea how many users may have been affected, and why? -- 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 1914147]
(In reply to Kershaw Chang [:kershaw] from comment #22) > (In reply to Julien Cristau [:jcristau] from comment #21) > > Do we know when/why this started? Any idea how many users may have been > > affected, and why? > I think the code that triggers this deadlock was in bug 1325341 (since the lock is `mRCWNLock`), so it has been there for years. I think it's probably some recent changes that affect the thread timings and make this deadlock happen more often. Unfortunately, I can't tell how many users are affected, since it's all about timing to hit this. -- 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 1914147]
In reply to "when", I never experienced this problem up to and including 84.0.2. I first got this problem in 85.0, and still get it in 85.0.1. -- 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 1914147]
(In reply to Julien Cristau [:jcristau] from comment #21) > Do we know when/why this started? Any idea how many users may have been > affected, and why? I think the code that triggers this deadlock was in bug 1325341 (since the lock is `mRCWNLock`), so it has been there for years. I think it's probably some recent changes that change the thread timings and make this deadlock happen more often. Unfortunately, I can't tell how many users are affected, since it's all about timing to hit this. -- 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 1914147]
Comment on attachment 9197123 Bug 1679933 - Call EnsureNSSInitializedChromeOrContent() during nsHttpHandler initialization ### Beta/Release Uplift Approval Request * **User impact if declined**: Firefox could freeze on start up. See bug 1689032. It seems we have some users reported the same issue. * **Is this code covered by automated tests?**: Yes * **Has the fix been verified in Nightly?**: Yes * **Needs manual test from QE?**: No * **If yes, steps to reproduce**: * **List of other uplifts needed**: None * **Risk to taking this patch**: Low * **Why is the change risky/not risky? (and alternatives if risky)**: This patch is quite straightforward and this patch is already on beta and nightly for a while. * **String changes made/needed**: N/A -- 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 1915003] Re: Always update the initramfs when changing power profile
** Changed in: nvidia-prime (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-settings (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-prime (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-prime (Ubuntu Focal) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-prime (Ubuntu Groovy) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu Groovy) Status: New => In Progress ** Changed in: nvidia-prime (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu Groovy) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu Groovy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: Always update the initramfs when changing power profile Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-prime source package in Focal: In Progress Status in nvidia-settings source package in Focal: New Status in nvidia-prime source package in Groovy: In Progress Status in nvidia-settings source package in Groovy: In Progress Bug description: The different power profiles require loading the nvidia drivers with different options (or blacklisting them, in case of intel mode). We need to call update-initramfs whenever we switch to a different profile, or things may fall out sync, resulting in a failure. The update-initramfs command takes a few seconds, therefore we also need to provide feedback, so that users know that they have to wait for the operation to complete. For this reason, prime-select will provide a spinner on the command line, and nvidia-settings will show a progress dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1915003/+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 1901391] Re: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement)
** Summary changed: - Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 + Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement) -- 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/1901391 Title: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: I'm using gnome-shell with wayland (don't know if that matters), and, when I press CTRL-ALT-SHIFT-R, nothing happens. I checked my keyboard shortcuts, and this shortcut is supposed to trigger screencasting. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Oct 25 10:39:48 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-07 (260 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1901391/+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 1915003] [NEW] Always update the initramfs when changing power profile
Public bug reported: The different power profiles require loading the nvidia drivers with different options (or blacklisting them, in case of intel mode). We need to call update-initramfs whenever we switch to a different profile, or things may fall out sync, resulting in a failure. The update-initramfs command takes a few seconds, therefore we also need to provide feedback, so that users know that they have to wait for the operation to complete. For this reason, prime-select will provide a spinner on the command line, and nvidia-settings will show a progress dialog. ** Affects: nvidia-prime (Ubuntu) Importance: High Assignee: Alberto Milone (albertomilone) Status: Fix Released ** Affects: nvidia-settings (Ubuntu) Importance: High Assignee: Alberto Milone (albertomilone) Status: Fix Released ** Affects: nvidia-prime (Ubuntu Bionic) Importance: High Status: In Progress ** Affects: nvidia-settings (Ubuntu Bionic) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: nvidia-prime (Ubuntu Focal) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: nvidia-settings (Ubuntu Focal) Importance: High Assignee: Alberto Milone (albertomilone) Status: New ** Affects: nvidia-prime (Ubuntu Groovy) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: nvidia-settings (Ubuntu Groovy) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Also affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-settings (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-settings (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: nvidia-settings (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nvidia-prime (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-prime (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-prime (Ubuntu Groovy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu Groovy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: Always update the initramfs when changing power profile Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: In Progress Status in nvidia-prime source package in Focal: In Progress Status in nvidia-settings source package in Focal: New Status in nvidia-prime source package in Groovy: In Progress Status in nvidia-settings source package in Groovy: In Progress Bug description: The different power profiles require loading the nvidia drivers with different options (or blacklisting them, in case of intel mode). We need to call update-initramfs whenever we switch to a different profile, or things may fall out sync, resulting in a failure. The update-initramfs command takes a few seconds, therefore we also need to provide feedback, so that users know that they have to wait for the operation to complete. For this reason, prime-select will provide a spinner on the command line, and nvidia-settings will show a progress dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1915003/+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 1915001] [NEW] I can't present my powerpoint presentation.
Public bug reported: I created a powerpoint presentation with Microsoft 365 PowerPoint And in Another device when I am open the presentation with Libreoffice impress it opens When I am presenting it at first it's ok but when the 3rd slide comes and it crashed. It says due to some errors Libreoffice Impress crashed and it will recover when I close the message. And then it will say again and crashes and it will reopen. This will go infinite loop. I can't present my presentation on Libreoffice Impress on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-impress 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: hostname 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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 16:20:27 2021 InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1915001 Title: I can't present my powerpoint presentation. Status in libreoffice package in Ubuntu: New Bug description: I created a powerpoint presentation with Microsoft 365 PowerPoint And in Another device when I am open the presentation with Libreoffice impress it opens When I am presenting it at first it's ok but when the 3rd slide comes and it crashed. It says due to some errors Libreoffice Impress crashed and it will recover when I close the message. And then it will say again and crashes and it will reopen. This will go infinite loop. I can't present my presentation on Libreoffice Impress on Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-impress 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: hostname 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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 16:20:27 2021 InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915001/+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 1912211] Re: Can't scroll pages in "Show Applications" when Ubuntu Dock is loaded
** Changed in: dash-to-dock Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1912211 Title: Can't scroll pages in "Show Applications" when Ubuntu Dock is loaded Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Go to show Application bottom left corner of the windows 2. try to scroll down to check all of the apps. whenever i try to do the same it doesnt allow me to scroll or check all the apps i have installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 18 18:57:54 2021 InstallationDate: Installed on 2021-01-12 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1912211/+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 1914997] [NEW] Can't able to view downloads
Public bug reported: When I download a pdf file from a website an when I try to open the download icon, its not opening. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 85.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: hostname 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.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balashanmugam 1457 F pulseaudio BuildID: 20210118153634 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 16:04:46 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:353 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.0.1 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.0.0/24 dev ens33 proto kernel scope link src 192.168.0.118 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:353 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=85.0/20210118153634 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2020 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.16722896.B64.2008100651 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.16722896.B64.2008100651:bd08/10/2020:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1914997 Title: Can't able to view downloads Status in firefox package in Ubuntu: New Bug description: When I download a pdf file from a website an when I try to open the download icon, its not opening. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 85.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: hostname 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.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balashanmugam 1457 F pulseaudio BuildID: 20210118153634 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 16:04:46 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:353 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.0.1 dev ens33 proto dhcp metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.0.0/24 dev ens33 proto kernel scope link src 192.168.0.118 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:353 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1
[Desktop-packages] [Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen
Error tracker entry : https://errors.ubuntu.com/oops/3d57ee6e-69f3-11eb-8529-fa163e102db1 -- 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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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] Xorg crashes and return to login screen
There's something new in /var/crash, I have a gnome-shell entry, with uploaded file. Here is file ** Attachment added: "_usr_bin_gnome-shell.1000.uploaded" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461215/+files/_usr_bin_gnome-shell.1000.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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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 1861769] Re: gdm3 crashed with SIGSEGV in g_type_check_instance_cast() from gdm_manager_handle_register_session() from ffi_call_unix64() from ffi_call() from g_cclosure_marshal
This bug was fixed in the package gdm3 - 3.36.3-0ubuntu0.20.04.3 --- gdm3 (3.36.3-0ubuntu0.20.04.3) focal; urgency=medium * debian/patches/git_display_segfault.patch: - Backport crash fix when using Xvfb in some situations (lp: #1861769) -- Sebastien Bacher Tue, 10 Nov 2020 13:27:10 +0100 ** Changed in: gdm3 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1861769 Title: gdm3 crashed with SIGSEGV in g_type_check_instance_cast() from gdm_manager_handle_register_session() from ffi_call_unix64() from ffi_call() from g_cclosure_marshal_generic() Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Focal: Fix Released Bug description: * Impact The desktop session can close in some cases when using xvfb * Test case $ Xvfb -ac :100 2> Xvfb.log & $ export DISPLAY=:100 $ gnome-session --session=ubuntu * Regression potential The change is a simple variable init in the display code, check that the greeter stills load correctly in normal and remote cases The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/75937873ed2a64ec63a908fe2b52c193e7371d78 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/gdm/+bug/1861769/+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 1914989] Re: Not Scrolling down
*** This bug is a duplicate of bug 1912211 *** https://bugs.launchpad.net/bugs/1912211 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1912211, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1912211 Can't scroll pages in "Show Applications" when Ubuntu Dock is loaded -- 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/1914989 Title: Not Scrolling down Status in gnome-shell package in Ubuntu: New Bug description: when I click show applications and swipe down it didn't scroll down and when I am navigating with my arrow keys it didn't work. I dont know what caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: hostname 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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:32:29 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.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/1914989/+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 1905740] Re: SRU the current 3.36.5 stable update
This bug was fixed in the package gnome-control-center - 1:3.36.5-0ubuntu1 --- gnome-control-center (1:3.36.5-0ubuntu1) focal; urgency=medium * New upstream release (lp: #1905740) * debian/patches/git_useraccount_segfault.patch, debian/patches/git_row_collide.patch, debian/patches/0033-sound-update-the-profile-list-after-getting-the-sign.patch: - removed, included in the new version * debian/patches/revert_vino_deprecated.patch: - revert the upstream change to remove the vino control option, it's still working in Ubuntu because we reverted the g-s-d commit which deprecated the backend handling -- Sebastien Bacher Thu, 26 Nov 2020 13:47:43 +0100 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1905740 Title: SRU the current 3.36.5 stable update Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential Review the fixes in the update the things to try should include - replacing a keybinding - checking that connectivy changes are correctly reflected in settings and that informations are correctly displayed in the details screen - opening the printer panel to verify that ink levels are still correctly displayed - using the privacy screen to enable or disable screen sharing - going to the sound panel and change devices configurations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905740/+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 1905740] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1905740 Title: SRU the current 3.36.5 stable update Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential Review the fixes in the update the things to try should include - replacing a keybinding - checking that connectivy changes are correctly reflected in settings and that informations are correctly displayed in the details screen - opening the printer panel to verify that ink levels are still correctly displayed - using the privacy screen to enable or disable screen sharing - going to the sound panel and change devices configurations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905740/+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 1912211] Re: Can't scroll pages in "Show Applications" when Ubuntu Dock is loaded
Maybe related (from duplicate bug 1914989): [ 9574.735022] Ubuntu gnome-shell[1681]: Object St.ScrollView (0x5558e598c4c0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [ 9574.743757] Ubuntu gnome-shell[1681]: == Stack trace for context 0x5558e2b27710 == [ 9574.799543] Ubuntu gnome-shell[1681]: #0 5558e37610b0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:965 (141015fe76a0 @ 132) [ 9574.801651] Ubuntu gnome-shell[1681]: #1 5558e3761018 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:494 (141015fec880 @ 30) [ 9574.801968] Ubuntu gnome-shell[1681]: st_scroll_view_get_vscroll_bar: assertion 'ST_IS_SCROLL_VIEW (scroll)' failed [ 9574.838268] Ubuntu gnome-shell[1681]: JS ERROR: TypeError: scrollView.get_vscroll_bar(...) is null ensureActorVisibleInScrollView@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:965:34 _createAppItem/https://github.com/micheleg/dash-to-dock/issues/1273 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1273 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1912211 Title: Can't scroll pages in "Show Applications" when Ubuntu Dock is loaded Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Go to show Application bottom left corner of the windows 2. try to scroll down to check all of the apps. whenever i try to do the same it doesnt allow me to scroll or check all the apps i have installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 18 18:57:54 2021 InstallationDate: Installed on 2021-01-12 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1912211/+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] Xorg crashes and return to login screen
same file, after reboot. ** Attachment added: "prevboot3.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461212/+files/prevboot3.txt -- 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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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] Xorg crashes and return to login screen
Hello, I had the bug just now. It was a bit different, the screen freeze in a strange way before "gnome reboot", so maybe it's different... Here are the 2 files, before and after reboot just in case you need both. They may be the same file or nearly. ** Attachment added: "curboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914573/+attachment/5461211/+files/curboot.txt -- 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] Xorg crashes and return to login screen Status in evdi package in Ubuntu: Incomplete 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 1914992] [NEW] gnome-calendar crashes after a few clicks when creating event or un/toggling which calendar to show
Public bug reported: I am using gnome-calendar (3.36.2) on Linux Mint 20 (Ulyana), Cinnamon 4.6.7. I am able to replicate the crash by opening gnome-calendar, then clicking on "Manage your calendars" and toggling / untoggling different calendars at random. Here's a log from journalctl if it's of use: -- The job identifier is 27260. Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.386][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:1041][info] BYTECOUNT: 3311031560, 118663140 Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.387][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:942][info] peer: handshake at 1612777449 - "3 sec" ago Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: ** Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn systemd[1]: Started Process Core Dump (PID 249641/UID 0). -- Subject: A start job for unit systemd-coredump@41-249641-0.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit systemd-coredump@41-249641-0.service has finished successfully. -- -- The job identifier is 27350. Feb 08 01:44:16 saturn systemd-coredump[249642]: Process 249540 (gnome-calendar) of user 1000 dumped core. Stack trace of thread 249540: #0 0x7f1ff002018b __GI_raise (libc.so.6 + 0x4618b) #1 0x7f1fe859 __GI_abort (libc.so.6 + 0x25859) #2 0x7f1ff0523b43 n/a (libglib-2.0.so.0 + 0x1db43) #3 0x7f1ff0580b2f g_assertion_message_expr (libglib-2.0.so.0 + 0x7ab2f) #4 0x5562ad7685a7 n/a (gnome-calendar + 0x455a7) #5 0x7f1ff0645a56 n/a (libgobject-2.0.so.0 + 0x14a56) #6 0x7f1ff0664b28 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33b28) #7 0x7f1ff06650d3 g_signal_emit (libgobject-2.0.so.0 + 0x340d3) #8 0x5562ad7825ec n/a (gnome-calendar + 0x5f5ec) #9 0x7f1ff0557e6e g_main_context_dispatch (libglib-2.0.so.0 + 0x51e6e) #10 0x7f1ff0558220 n/a (libglib-2.0.so.0 + 0x52220) #11 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) #12 0x7f1ff0773fd5 g_application_run (libgio-2.0.so.0 + 0xe2fd5) #13 0x5562ad747532 main (gnome-calendar + 0x24532) #14 0x7f1ff00010b3 __libc_start_main (libc.so.6 + 0x270b3) #15 0x5562ad74757e _start (gnome-calendar + 0x2457e) Stack trace of thread 249544: #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) #2 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) #3 0x7f1ff155799d n/a (libdconfsettings.so + 0xa99d) #4 0x7f1ff0581911 n/a (libglib-2.0.so.0 + 0x7b911) #5 0x7f1fef452609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f1ff00fc293 __clone (libc.so.6 + 0x122293) Stack trace of thread 249543: #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) #2 0x7f1ff0558513 g_main_loop_run (libglib-2.0.so.0 + 0x52513)
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
> bug 1751069: restore type-ahead find in nautilus itself You have linked to the wrong issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1914989] [NEW] Not Scrolling down
Public bug reported: when I click show applications and swipe down it didn't scroll down and when I am navigating with my arrow keys it didn't work. I dont know what caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: hostname 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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:32:29 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1914989 Title: Not Scrolling down Status in gnome-shell package in Ubuntu: New Bug description: when I click show applications and swipe down it didn't scroll down and when I am navigating with my arrow keys it didn't work. I dont know what caused it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: hostname 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 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:32:29 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-05 (2 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.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/1914989/+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 1802039]
I haven't used MATE for a couple years now, so I'm not sure myself. -- 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/1802039 Title: Firefox without titlebar has visual glitches when maximizing/unmaximizing Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: There is a relatively new feature in Firefox that allows you to hide the title bar (I'm running Firefox 63.0), which is very helpful when you have a low resolution screen. However, when changing the maximization state, some visual gitches occur. I didn't notice this glitching when running Kubuntu or Ubuntu Budgie on two separate systems. To try this, go to your Firefox Menu, click Customize, and uncheck "Title Bar" at the bottom left. Then unmaximize the window and then remaximize it. What it's supposed to look like: https://pasteboard.co/HM0h8oB.png Unmaximized (note the large transparent section): https://pasteboard.co/HM0hpud.png Remaximized (note the duplicate set of close buttons): https://pasteboard.co/HM0hCf5.png Also another interesting bug I noticed...if you try to use Firefox in the no titlebar state with the global menu enabled (e.g. Contemporary, Cupertino, or Mutiny panel layouts), the window buttons are not placed correctly, being on the window border. Systems tried on: Laptop, Dell Latitude E5430 - Intel Core i3-3120M dual core with hyperthreading, 12 GB DDR3 Memory, Intel 4000 Graphics, Built-in LCD at 1366x768 (screenshots from this system) Desktop, Lenovo ThinkCentre M79 - AMD A4-6300B 3.7 GHz dual core, 8 GB DDR3 Memory, AMD 8370D Graphics, HP 2009f Monitor at 1600x900 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1802039/+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 1802039]
This is still happening in Ubuntu Mate 20.04 with Firefox 85.0. Any updates? -- 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/1802039 Title: Firefox without titlebar has visual glitches when maximizing/unmaximizing Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: There is a relatively new feature in Firefox that allows you to hide the title bar (I'm running Firefox 63.0), which is very helpful when you have a low resolution screen. However, when changing the maximization state, some visual gitches occur. I didn't notice this glitching when running Kubuntu or Ubuntu Budgie on two separate systems. To try this, go to your Firefox Menu, click Customize, and uncheck "Title Bar" at the bottom left. Then unmaximize the window and then remaximize it. What it's supposed to look like: https://pasteboard.co/HM0h8oB.png Unmaximized (note the large transparent section): https://pasteboard.co/HM0hpud.png Remaximized (note the duplicate set of close buttons): https://pasteboard.co/HM0hCf5.png Also another interesting bug I noticed...if you try to use Firefox in the no titlebar state with the global menu enabled (e.g. Contemporary, Cupertino, or Mutiny panel layouts), the window buttons are not placed correctly, being on the window border. Systems tried on: Laptop, Dell Latitude E5430 - Intel Core i3-3120M dual core with hyperthreading, 12 GB DDR3 Memory, Intel 4000 Graphics, Built-in LCD at 1366x768 (screenshots from this system) Desktop, Lenovo ThinkCentre M79 - AMD A4-6300B 3.7 GHz dual core, 8 GB DDR3 Memory, AMD 8370D Graphics, HP 2009f Monitor at 1600x900 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1802039/+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
