[Desktop-packages] [Bug 1894881] Re: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card
In the meantime I'm on 5.4.0-51-generic #56, but it's still happening. Google more about the error, there are some indications that it could be a faulty/bad firmware problem: https://www.kernel.org/doc/html/v5.4/sound/hd-audio/notes.html#codec- probing-problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894881 Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: kernel 5.4.0-47-generic #51 upgraded today to this new kernel sound is now totally broken kern.org and syslog are filling with those messages every second, in loop, with no end to it : Sep 8 19:42:34 orion kernel: [ 147.398030] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20970500 Sep 8 19:42:35 orion kernel: [ 148.410043] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20a70500 Sep 8 19:42:36 orion kernel: [ 149.413955] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20b70500 Sep 8 19:42:37 orion kernel: [ 150.421890] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x201f0500 Sep 8 19:42:38 orion kernel: [ 151.453799] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:39 orion kernel: [ 152.461793] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:41 orion kernel: [ 153.473734] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:42 orion kernel: [ 154.477653] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:43 orion kernel: [ 155.481576] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:44 orion kernel: [ 156.489620] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Sep 8 19:42:45 orion kernel: [ 157.497553] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x2043b000 Sep 8 19:42:46 orion kernel: [ 158.509530] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x20470740 Sep 8 19:42:47 orion kernel: [ 159.513471] snd_hda_intel :00:1f.3: No response from codec, resetting bus: last cmd=0x204f0015 Because of this, machine has become very slow and response time is awful Login into the machine, even trying to launch a simple program can take up to 30 seconds of wait before anything happens. Sound was working fine with previous kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gf 1758 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 8 19:42:19 2020 InstallationDate: Installed on 2020-08-29 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9300, Realtek ALC289, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd07/07/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894881/+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 1899889] [NEW] In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the
You have been subscribed to a public bug: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page. https://bugs.launchpad.net/bugs/1899889 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1899889] Re: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the e
** Package changed: dash (Ubuntu) => gnome-shell (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/1899889 Title: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page. Status in gnome-shell package in Ubuntu: New Bug description: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash 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/1899889/+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 1899893] [NEW] [Important] Ubuntu default screen keyboard to be movable, interface morph and more enhancements
Public bug reported: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) 1. Add option for enable screen keyboard movable https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-dock.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-undocked.jpg 2. Add screen keyboard modes (option to morph into several keyboards) Normal(default), Thumb and Standard (standard has all keys has on physical keyboard) https://gitlab.com/cloud.ch/bugs/-/raw/master/modes.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/thumb.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/standard.jpg 3. Add option to enable screen-keyboard icon in dock (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) (Enable it through universal access > screen keyboard then it quite annoying due pop up often) https://gitlab.com/cloud.ch/bugs/-/raw/master/screenkeyboard.png ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1899893 Title: [Important] Ubuntu default screen keyboard to be movable, interface morph and more enhancements Status in gnome-shell package in Ubuntu: New Bug description: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) 1. Add option for enable screen keyboard movable https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-dock.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-undocked.jpg 2. Add screen keyboard modes (option to morph into several keyboards) Normal(default), Thumb and Standard (standard has all keys has on physical keyboard) https://gitlab.com/cloud.ch/bugs/-/raw/master/modes.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/thumb.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/standard.jpg 3. Add option to enable screen-keyboard icon in dock (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) (Enable it through universal access > screen keyboard then it quite annoying due pop up often) https://gitlab.com/cloud.ch/bugs/-/raw/master/screenkeyboard.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899893/+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 1899889] Re: In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the e
I think this is correct. The current design allows you to drag icons and define your own order. Meaning the order of icons should stay unchanged, not sorted, even after installing new apps. But rather than closing this bug I will turn it into an enhancement request for the option to sort the icons. ** Summary changed: - In "show applications" the applications are not sorted alphabetically and does not update when installing new application. New applications are just added at the end of the last page. + Add option to sort icons by name ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Summary changed: - Add option to sort icons by name + Add option to sort app icons by name ** Tags added: 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/1899889 Title: Add option to sort app icons by name Status in gnome-shell package in Ubuntu: Triaged Bug description: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash 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/1899889/+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 1538234] Re: Right-clicking on an application in the Activities Overview list should give you options but also display program information
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Tags added: focal 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/1538234 Title: Right-clicking on an application in the Activities Overview list should give you options but also display program information Status in Ubuntu GNOME: New Status in gnome-shell package in Ubuntu: Triaged Bug description: In Unity when one searches for an application, if they then right- click on the application icon it provides the user with more information and focusses on the program and puts it in a sort of square in the centre of the screen (so basically it looks quit nice and slick). It puts the application icon big next to the title on the right and has a description of the application underneath, it then also provides options such as "Open" and "Uninstall" (I think so anyway, it's been a while since I used Unity). Anyway, I think that when one searches for an application or views the listing of them in the Activities Overview that they should be able to right-click on the icon and get something similar rather than just a menu with a few options. It would probably be good if the same was done for other file types and not just applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1538234/+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 1899893] Re: [Important] Ubuntu default screen keyboard to be movable, interface morph and more enhancements
In future please be careful to only report one issue per bug. Let's start by making this just about a moveable keyboard... ** Tags added: osk ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Summary changed: - [Important] Ubuntu default screen keyboard to be movable, interface morph and more enhancements + Ubuntu default screen keyboard to be movable ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/1899893 Title: Ubuntu default screen keyboard to be movable Status in gnome-shell package in Ubuntu: Triaged Bug description: This enhancement requests for ubuntu default screen keyboard (compared to windows 10 touch keyboard, not on screen keyboard) 1. Add option for enable screen keyboard movable https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-dock.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/win-10-keyboard-undocked.jpg 2. Add screen keyboard modes (option to morph into several keyboards) Normal(default), Thumb and Standard (standard has all keys has on physical keyboard) https://gitlab.com/cloud.ch/bugs/-/raw/master/modes.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/thumb.jpg https://gitlab.com/cloud.ch/bugs/-/raw/master/standard.jpg 3. Add option to enable screen-keyboard icon in dock (it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field) (Enable it through universal access > screen keyboard then it quite annoying due pop up often) https://gitlab.com/cloud.ch/bugs/-/raw/master/screenkeyboard.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899893/+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 1896394] Re: Prevent add to favorite and vise versa when move apps to left or right
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1896394 Title: Prevent add to favorite and vise versa when move apps to left or right Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Gnome dock has serious issue, we cannot move apps to left then it get added to favorite and if move to right then get removed from favorite then as result users cannot move apps in dock as preferred. No one add apps to 'dock favorite' more often then already it's possible to perform by right click on required app icon and click 'add to favorite' Is it possible to address this issue soon, this is most likely erase some codes rather than implement new feature. KDE and Windows 10 don't have such issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896394/+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 1896394] Re: Prevent add to favorite and vise versa when move apps to left or right
The bug is not confirmed until at least one other person understands and confirms it. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => 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/1896394 Title: Prevent add to favorite and vise versa when move apps to left or right Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Gnome dock has serious issue, we cannot move apps to left then it get added to favorite and if move to right then get removed from favorite then as result users cannot move apps in dock as preferred. No one add apps to 'dock favorite' more often then already it's possible to perform by right click on required app icon and click 'add to favorite' Is it possible to address this issue soon, this is most likely erase some codes rather than implement new feature. KDE and Windows 10 don't have such issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896394/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set
I solved the problem changing the gnome theme to Adwaita using gnome tweaks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set Status in Ubuntu: Confirmed Status in im-config package in Ubuntu: Fix Released Status in light-themes package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1760818/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Same for me. Also Alt + F2 and executing "r" resolved it... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1899889] Re: Add option to sort app icons by name
Thanks for the explanation. Just one note. This is affecting my Groovy install not 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/1899889 Title: Add option to sort app icons by name Status in gnome-shell package in Ubuntu: Triaged Bug description: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash 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/1899889/+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 1899909] [NEW] [gdm3] Screen keyboard doesn't work after session locked
Public bug reported: Below explain further details and reproduce instruction to recognize the issue Ubuntu all in one touch screen device with 2 user accounts (eg: root and non-root) [1] Boot the device [2] Ubuntu loads to main login screen (the screen that display all user accounts) then tap on any user account and it brings to next screen to enter the password. Screen keyboard automatically appear then you can enter password and tap enter to login. [3] Lock the session [4] It brings to locked screen that display time [4] Tap on screen once, then brings to existing logged account login screen (not the main login screen that display all accounts list) [5] [Bug] Tap on password input field, screen keyboard doesn't appear. you cannot get it by anyway (Alternative solution) - Tap the user accounts icon located on right side down corner then it bring to locked screen that display time - Tap on screen again, it display main login screen that display all user accounts. Now you can tap on already logged user account icon and it brings to existing logged account login screen, now screen keyboard appear and you can unlock the session (About universal access > enable screen keyboard) If enable that, then it display screen keyboard on 4th step but any key input doesn't appear on password input field. Furthermore that screen keyboard through universal access too annoying because after that, screen keyboard pop up when tap on text field. Ubuntu 20.04.01 3.36.4-1ubuntu1~20.04.2 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked Status in gnome-shell package in Ubuntu: New Bug description: Below explain further details and reproduce instruction to recognize the issue Ubuntu all in one touch screen device with 2 user accounts (eg: root and non-root) [1] Boot the device [2] Ubuntu loads to main login screen (the screen that display all user accounts) then tap on any user account and it brings to next screen to enter the password. Screen keyboard automatically appear then you can enter password and tap enter to login. [3] Lock the session [4] It brings to locked screen that display time [4] Tap on screen once, then brings to existing logged account login screen (not the main login screen that display all accounts list) [5] [Bug] Tap on password input field, screen keyboard doesn't appear. you cannot get it by anyway (Alternative solution) - Tap the user accounts icon located on right side down corner then it bring to locked screen that display time - Tap on screen again, it display main login screen that display all user accounts. Now you can tap on already logged user account icon and it brings to existing logged account login screen, now screen keyboard appear and you can unlock the session (About universal access > enable screen keyboard) If enable that, then it display screen keyboard on 4th step but any key input doesn't appear on password input field. Furthermore that screen keyboard through universal access too annoying because after that, screen keyboard pop up when tap on text field. Ubuntu 20.04.01 3.36.4-1ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+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 1899889] Re: Add option to sort app icons by name
I verified it's a missing feature on both focal and 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/1899889 Title: Add option to sort app icons by name Status in gnome-shell package in Ubuntu: Triaged Bug description: Upon installing a new application the list in "show applications" is not updated and just added at the end (last page). The list is also not sorted. When first installing Ubuntu 20.10, I could get the list updated by logging in and out, but after installing about 10 applications that stopped working. The Dash is version 0.5.10.2-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dash 0.5.10.2-7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 09:29:12 2020 InstallationDate: Installed on 2020-10-01 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923) RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: dash 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/1899889/+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 1899766] Re: Xorg freeze after selecting large cursor
Found the source of the v4l warnings; I was experimenting with v4lloopback to use a camera as webcam. Disabled that and it's gone away. Unfortunately, /var/crash is empty and I didn't see any report from the right time in the errors webpage. After applying the change to add "Crash" to the crashdb.conf, I still don't see a crash dump in /var/crash after repro. However, I did find that the problem only repros in NVIDIA PRIME mode, not Intel. -- 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/1899766 Title: Xorg freeze after selecting large cursor Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/nvidia-graphics-drivers-435/+bug/1899766/+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 1899349] Re: Jack_control in jackd2 1.9.14 will not accept char parameters
This bug was fixed in the package jackd2 - 1.9.14-0ubuntu3.1 --- jackd2 (1.9.14-0ubuntu3.1) groovy; urgency=medium * debian/patches/git_dbus_bytes.patch: - Fix jack_control handling of dbus bytes, thanks Len (lp: #1899349) -- Sebastien Bacher Wed, 14 Oct 2020 09:59:30 +0200 ** Changed in: jackd2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1899349 Title: Jack_control in jackd2 1.9.14 will not accept char parameters Status in jackd2 package in Ubuntu: Fix Released Bug description: trying to set self-connect-mode (for example): $ jack_control eps self-connect-mode e gives: --- engine param set "self-connect-mode" -> "e" Traceback (most recent call last): File "/usr/bin/jack_control", line 400, in main() File "/usr/bin/jack_control", line 283, in main configure_iface.SetParameterValue(['engine', param], python_type_to_jackdbus_type(value, type_char)) File "/usr/bin/jack_control", line 46, in python_type_to_jackdbus_type return dbus.Byte(value); TypeError: Expected a bytes or str of length 1, or an int in the range 0-255 This bug has been fixed upstream in commit ba28ffa @@ -43,7 +43,7 @@ def python_type_to_jackdbus_type(value, type_char): if type_char == "b": return bool_convert(value); elif type_char == "y": -return dbus.Byte(value); +return dbus.Byte(ord(value)); elif type_char == "i": return dbus.Int32(value) elif type_char == "u": To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1899349/+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 1899909] Re: [gdm3] Screen keyboard doesn't work after session locked
Probably distantly related to https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/717 ** Tags added: focal osk ** Tags added: lock ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #717 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/717 -- 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/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked Status in gnome-shell package in Ubuntu: New Bug description: Below explain further details and reproduce instruction to recognize the issue Ubuntu all in one touch screen device with 2 user accounts (eg: root and non-root) [1] Boot the device [2] Ubuntu loads to main login screen (the screen that display all user accounts) then tap on any user account and it brings to next screen to enter the password. Screen keyboard automatically appear then you can enter password and tap enter to login. [3] Lock the session [4] It brings to locked screen that display time [4] Tap on screen once, then brings to existing logged account login screen (not the main login screen that display all accounts list) [5] [Bug] Tap on password input field, screen keyboard doesn't appear. you cannot get it by anyway (Alternative solution) - Tap the user accounts icon located on right side down corner then it bring to locked screen that display time - Tap on screen again, it display main login screen that display all user accounts. Now you can tap on already logged user account icon and it brings to existing logged account login screen, now screen keyboard appear and you can unlock the session (About universal access > enable screen keyboard) If enable that, then it display screen keyboard on 4th step but any key input doesn't appear on password input field. Furthermore that screen keyboard through universal access too annoying because after that, screen keyboard pop up when tap on text field. Ubuntu 20.04.01 3.36.4-1ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Thu, Oct 15, 2020 at 05:37:46AM -, Kai-Heng Feng wrote: >Coiby, can you please work on a DMI based workaround in gpiolib-acpi.c? >It'll have higher chance to get merged. > Thank you for the suggestion! Linus Walleij also suggested introducing a new quirk [1]. Although my main effort is on patching pinctrl-amd.c without affecting other touchpad together with Hans de Goede [1], I have spent some time on understanding gpiolib-acpi.c. For now my conclusion is there is no way to bypass pinctrl-amd by introducing a new quirk. [1] https://www.spinics.net/lists/linux-gpio/msg53641.html [2] https://www.spinics.net/lists/linux-gpio/msg53901.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216
[Desktop-packages] [Bug 1899955] [NEW] New Freeze Exception: Exceptional circumstance
Public bug reported: A description of the proposed changes, with sufficient detail to estimate their potential impact on the distribution: Changing the default wallpaper from the existing Groovy Gorilla illustration to the Raspberry Pi specific one with the Raspberry in his sunglasses. "We'll basically need to revert https://launchpad.net/ubuntu/+source /ubuntu-settings/20.10.2 and https://launchpad.net/ubuntu/+source /ubuntu-wallpapers/20.10.2-0ubuntu1 and update the warty-final- ubuntu.png" A rationale for the exception, explaining the benefit of the change: The benefit is to pay homage to the work various teams have been doing with the Raspberry Pi foundation and to their product. It's a way to signal our commitment to making their platform great and deepen our relationship with the Pi foundation. Any additional information which would be helpful in considering the decision The concerns people have are of product placement and forcing something onto peoples machines. There are several arguments against this, the option to change to the default easily, that there is not direct link to Raspberry Pi anything and its quite subtle. But ultimately the reason is we want to make a splash with the Raspberry Pi and arm in general and this is a very good way to do it. ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1899955 Title: New Freeze Exception: Exceptional circumstance Status in ubuntu-wallpapers package in Ubuntu: New Bug description: A description of the proposed changes, with sufficient detail to estimate their potential impact on the distribution: Changing the default wallpaper from the existing Groovy Gorilla illustration to the Raspberry Pi specific one with the Raspberry in his sunglasses. "We'll basically need to revert https://launchpad.net/ubuntu/+source /ubuntu-settings/20.10.2 and https://launchpad.net/ubuntu/+source /ubuntu-wallpapers/20.10.2-0ubuntu1 and update the warty-final- ubuntu.png" A rationale for the exception, explaining the benefit of the change: The benefit is to pay homage to the work various teams have been doing with the Raspberry Pi foundation and to their product. It's a way to signal our commitment to making their platform great and deepen our relationship with the Pi foundation. Any additional information which would be helpful in considering the decision The concerns people have are of product placement and forcing something onto peoples machines. There are several arguments against this, the option to change to the default easily, that there is not direct link to Raspberry Pi anything and its quite subtle. But ultimately the reason is we want to make a splash with the Raspberry Pi and arm in general and this is a very good way to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1899955/+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 1899953] [NEW] Crackling audio on Raspberry Pi Desktop
Public bug reported: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899953/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Fix on #211 Another header file hid-ids.h is required to build i2c-hid module. Attached is the updated zip file. ** Attachment added: "i2c-hid_standalone.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5422562/+files/i2c-hid_standalone.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
[Desktop-packages] [Bug 1899956] [NEW] Opening the Utilities folder and trying to scroll through it will expand and multiply the pages on the Show all applications panel
Public bug reported: What's expected to happen: Retracting or closing the Utilities folder should not affect the amount of pages displayed on the Show all applications panel. What happens instead: Retracting or closing the Utilities folder increases the amount of dots that represent the pages displayed on the Show all applications panel. A short screencast showcasing the bug is attached to the bug report below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal gnome-shell ** Attachment added: "A short screencast showcasing the bug" https://bugs.launchpad.net/bugs/1899956/+attachment/5422563/+files/show-all-apps.webm ** Description changed: - What's expected to happen: + What's expected to happen: Retracting or closing the Utilities folder should not affect the amount of pages on the Show all applications panel. - What happens instead: + What happens instead: Retracting or closing the Utilities folder increases the amount of dots that represent the pages on the Show all applications panel. + + A short screencast showcasing the bug is attached to the bug report + below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago) ** Description changed: - What's expected to happen: - Retracting or closing the Utilities folder should not affect the amount of pages on the Show all applications panel. + What's expected to happen: + Retracting or closing the Utilities folder should not affect the amount of pages displayed on the Show all applications panel. What happens instead: Retracting or closing the Utilities folder increases the amount of dots that represent the pages on the Show all applications panel. A short screencast showcasing the bug is attached to the bug report below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago) ** Description changed: - What's expected to happen: + What's expected to happen: Retracting or closing the Utilities folder should not affect the amount of pages displayed on the Show all applications panel. What happens instead: - Retracting or closing the Utilities folder increases the amount of dots that represent the pages on the Show all applications panel. + Retracting or closing the Utilities folder increases the amount of dots that represent the pages shown on the Show all applications panel. A short screencast showcasing the bug is attached to the bug report below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago)
[Desktop-packages] [Bug 1517272] Re: Can't import ssh keys
*** This bug is a duplicate of bug 1471965 *** https://bugs.launchpad.net/bugs/1471965 ** This bug has been marked a duplicate of bug 1471965 Import ssh keys don't work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1517272 Title: Can't import ssh keys Status in seahorse package in Ubuntu: Confirmed Bug description: I'm exported my several ssh keys. Now I want to import this. I'm open the seahorse and trying import keys. After entering password and key normally imported. But I can't see this key in list ssh keys of this program. In ~/.ssh I can't find my key too. Description: Ubuntu 14.04.3 LTS Release: 14.04 seahorse 3.10.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: seahorse 3.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-69.112-generic 3.13.11-ckt29 Uname: Linux 3.13.0-69-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 18 03:46:48 2015 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2014-08-08 (467 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1517272/+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 1251176] Re: Can't type accented characters anymore: is undefined
Bus is closed but I came to this issue while observing issues with: GNU Emacs 26.3 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.14) I sorted it out by adding: (require 'iso-transl) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1251176 Title: Can't type accented characters anymore: is undefined Status in Emacs-snapshot: Triaged Status in emacs24 package in Ubuntu: Confirmed Bug description: When you type an accented character through a dead-key, you might get one of: is undefined is undefined is undefined is undefined is undefined is undefined or something similar. On the web, I found several workaround: 1/ launch emacs with "XMODIFIERS='' emacs" 2/ type C-x 8 RET RET once 3/ add "(require 'iso-transl)" to your .emacs.d/init.el or .emacs file Upstream report: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15135 and http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15891 To manage notifications about this bug go to: https://bugs.launchpad.net/emacs-snapshot/+bug/1251176/+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 1471965] Re: Import ssh keys don't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: seahorse (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1471965 Title: Import ssh keys don't work Status in seahorse package in Ubuntu: Confirmed Bug description: I'm tryed import ssh key in seahorse. When I import, the program ask me a tag. After filling the key does not appear in the list of ssh keys. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: seahorse 3.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 6 22:48:47 2015 InstallationDate: Installed on 2014-08-08 (332 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1471965/+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 1899962] [NEW] Wrong audio output device selected on Raspberry Pi Desktop
Public bug reported: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1899971] [NEW] Problematic dependency on python3-apport causes all Python invocations to install apport hook
Public bug reported: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver- xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1899971 Title: Problematic dependency on python3-apport causes all Python invocations to install apport hook Status in xorg package in Ubuntu: New Bug description: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver-xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899971/+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 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: Triaged => Fix Released ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-prime (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-450 (Ubuntu Focal) Importance: Undecided => Wishlist ** No longer affects: nvidia-graphics-drivers-450 (Ubuntu Bionic) ** No longer affects: nvidia-graphics-drivers-450 (Ubuntu Focal) ** No longer affects: nvidia-prime (Ubuntu Bionic) ** No longer affects: nvidia-prime (Ubuntu Focal) ** No longer affects: ubuntu-drivers-common (Ubuntu Bionic) ** No longer affects: ubuntu-drivers-common (Ubuntu Focal) -- 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/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: New Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+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 1899909] Re: [gdm3] Screen keyboard doesn't work after session locked
** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked Status in gnome-shell package in Ubuntu: Confirmed Bug description: Below explain further details and reproduce instruction to recognize the issue Ubuntu all in one touch screen device with 2 user accounts (eg: root and non-root) [1] Boot the device [2] Ubuntu loads to main login screen (the screen that display all user accounts) then tap on any user account and it brings to next screen to enter the password. Screen keyboard automatically appear then you can enter password and tap enter to login. [3] Lock the session [4] It brings to locked screen that display time [4] Tap on screen once, then brings to existing logged account login screen (not the main login screen that display all accounts list) [5] [Bug] Tap on password input field, screen keyboard doesn't appear. you cannot get it by anyway (Alternative solution) - Tap the user accounts icon located on right side down corner then it bring to locked screen that display time - Tap on screen again, it display main login screen that display all user accounts. Now you can tap on already logged user account icon and it brings to existing logged account login screen, now screen keyboard appear and you can unlock the session (About universal access > enable screen keyboard) If enable that, then it display screen keyboard on 4th step but any key input doesn't appear on password input field. Furthermore that screen keyboard through universal access too annoying because after that, screen keyboard pop up when tap on text field. Ubuntu 20.04.01 3.36.4-1ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+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 1899803] Re: Some comments on annotations are not visible
** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #1347 https://gitlab.gnome.org/GNOME/evince/-/issues/1347 ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/-/issues/1347 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1899803 Title: Some comments on annotations are not visible Status in Evince: Unknown Status in evince package in Ubuntu: Triaged Bug description: It is not possible to see some text/comment on annotations in a PDF file. This bug was tracking on: https://gitlab.gnome.org/GNOME/evince/-/issues/1347 I've replicated this bug here to document and add more people to help solve the problem. I've also tested using: - Ubuntu 20.04 with Evince 3.36.7 - Ubuntu 20.10 with Evince 3.38.0 To reproduce this bug, see the post: https://gitlab.gnome.org/GNOME/evince/-/issues/1347#note_745797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:29:28 2020 InstallationDate: Installed on 2020-10-05 (9 days ago) InstallationMedia: Ubuntu 20.04.1 2020.09.19 LTS "Custom Focal Fossa" (20200920) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-09-19T23:53:28 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1899803/+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 1898205] Re: Thunderbird snap should be maintained by Canonical
The owner has been changed to Canonical now! ** Changed in: thunderbird (Ubuntu) Status: New => In Progress ** Changed in: thunderbird (Ubuntu) Status: In Progress => Fix Released -- 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/1898205 Title: Thunderbird snap should be maintained by Canonical Status in thunderbird package in Ubuntu: Fix Released Bug description: At the moment, the Thunderbird snap is maintained by Kev Van Dine. Obviously, nothing personal, and THANKS for packaging! :-) But, as Firefox snap, it would be more logical that Canonical handles the authoring, as this software needs somewhat the Canonical official support if a later defaulting/recommending of the snap version is done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1898205/+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 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm
** Changed in: alsa-utils (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1899745 Title: [SRU] alsa-utils: let alsactl support _boot section defined in ucm Status in HWE Next: New Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: In Progress Bug description: This patchset was backported from mainline alsa-utils 1.2.3, and groovy already integrated alsa-utils 1.2.3, there is no need to SRU this patchset to groovy, so only for focal. [Impact] We enabled 2 Dell soundwire audio machines, these machines depend on ucm to make the audio work, and in the ucm, the _boot section defined some amixers values for the 1st booting, these amixer values should be set to audio driver at the 1st booting, otherwise the whole audio doesn't work. [Fix] Backport some patches from mainline v1.2.3, these patches make the alsactl support _boot section in the ucm, then the systemd will call alsactl init after booting, the alsactl init will setting all amixers defined in the _boot section of ucm. [Test Case] On the Dell soundwire audio machines, After booting up, run 'amixer contents | less' to check all amixer values defined in the _boot section of ucm, all values read from driver are same as the ones in the ucm, test speaker/microphone/headset, all work well. [Regression Risk] This could introduce failure on runing 'alsactl init' for some machines, then the amixers will not be initialized correctly, users will experience all audio can't work like speaker doesn't output sound or microphone can't record sound. But this regression possibility is very low, since We have tested it both on soundwire machines and non-soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899745/+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 1898205] Re: Thunderbird snap should be maintained by Canonical
I confirm I can see that with snap list. Thanks! Will be good for TB snap usage. -- 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/1898205 Title: Thunderbird snap should be maintained by Canonical Status in thunderbird package in Ubuntu: Fix Released Bug description: At the moment, the Thunderbird snap is maintained by Kev Van Dine. Obviously, nothing personal, and THANKS for packaging! :-) But, as Firefox snap, it would be more logical that Canonical handles the authoring, as this software needs somewhat the Canonical official support if a later defaulting/recommending of the snap version is done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1898205/+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 1899989] [NEW] outdated instructions on bookmarking
You have been subscribed to a public bug: This page is wrong: https://help.ubuntu.com/stable/ubuntu-help/nautilus-bookmarks-edit.html.en Under 'Add a bookmark:' it should simply read: Press Ctrl + d The mentioned menu was removed in Ubuntu 20.04, it is available in 18.04. ** Affects: gnome-user-docs (Ubuntu) Importance: Medium Status: Confirmed -- outdated instructions on bookmarking https://bugs.launchpad.net/bugs/1899989 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs 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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected error response fro
[Desktop-packages] [Bug 1899989] Re: outdated instructions on bookmarking
Thanks for your report! Confirmed. (Why on earth did they drop that from the GUI?) It would be great if you could report it upstream too: https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues If you do, please post the URL to the upstream issue in a comment here. ** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu) ** Changed in: gnome-user-docs (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-user-docs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1899989 Title: outdated instructions on bookmarking Status in gnome-user-docs package in Ubuntu: Confirmed Bug description: This page is wrong: https://help.ubuntu.com/stable/ubuntu-help/nautilus-bookmarks-edit.html.en Under 'Add a bookmark:' it should simply read: Press Ctrl + d The mentioned menu was removed in Ubuntu 20.04, it is available in 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1899989/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) We have received feedback in our forum that the touchpad no longer works after a resuming from suspend. I've attached the link - maybe you can take a look at it. https://forum.manjaro.org/t/i2c-touchpad-does-not-function-after- resuming-from-suspend/31987/5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH0
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Hi Daniel, apt list libmutter-6-0 Auflistung... Fertig libmutter-6-0/focal-updates,now 3.36.6-1ubuntu0.20.04.2 amd64 [Installiert,automatisch] Sorry but the bu still occurs. Should I open a new bug? Best regards José -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Just try this morning the #210, it's working well on ubuntu 20.04 ! Thanks @Coiby Xu (coiby) I also confirmed the suspend will break the touchpad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
[Desktop-packages] [Bug 1899673] Re: gdm 3.38 with nvidia drivers breaks Wayland support (once nvidia drivers are disabled)
This bug was fixed in the package gdm3 - 3.38.1-2ubuntu1 --- gdm3 (3.38.1-2ubuntu1) groovy; urgency=medium * Merging with debian, containing a new upstream release, remaining changes: + readme.debian: update for correct paths in ubuntu + control.in: - don't recommend desktop-base - build depend on libgudev-1.0-dev - depend on bash for config_error_dialog.patch - update vcs field - recomends libpam-fprintd (instead of suggests) + rules: - don't override default user/group - -dgdm-xsession=true to install upstream xsession script - override dh_installinit with --no-start to avoid session being killed + rules, readme.debian, gdm3.8.pod: use upstream custom.conf instead of daemon.conf + gdm3.{postinst,postrm}: rename user and group back to gdm + gdm3.postinst, gdm3.prerm: don't kill gdm on upgrade + gdm3.*.pam: make pam_env read ~/.pam_environment + gdm3.install: - stop installing default.desktop. it adds unnecessary clutter ("system default") to the session chooser. - don't install debian/xsession + add run_xsession.d.patch + add xresources_is_a_dir.patch - fix loading from /etc/x11/xresources/* + add nvidia_prime.patch: - add hook to run prime-offload (as root) and prime-switch if nvidia-prime is installed + add revert_override_lang_with_accountservices.patch: - on ubuntu accountservices only stores the language and not the full locale as needed by lang. + add dont_set_language_env.patch: - don't run the set_up_session_language() function, since it overrides variable values set by ~/.pam_environment + add config_error_dialog.patch: - show warning dialog in case of error in ~/.profile etc. and don't let a syntax error make the login fail + add debian/patches/revert_nvidia_wayland_blacklist.patch: - don't blacklist nvidia for wayland + add gdm3.service-wait-for-drm-device-before-trying-to-start-i.patch: - wait for the first valid gdm device on pre-start + add debian/default.pa - disable bluetooth audio devices in pulseaudio from gdm3. + debian/gdm3.install - added details of the default.pa file + debian/gdm3.postinst - added installation of default.pa and creation of dir if it doesn't exist. + debian/greeter.dconf-defaults: don't set debian settings in the greeter's dconf db gdm3 (3.38.1-2) unstable; urgency=medium * debian/gdm3.preinst: Add script to replace possibly wrong .conf file. In gdm3 versions of the 3.38 series a regression was introduced causing the /usr/libexec/gdm-disable-wayland tool to write its supposedly temporary gdm file to the persistent location. This is particularly harmful for users of the NVIDIA drivers as they will get their default config file (/etc/gdm3/daemon.conf in debian and /etc/gdm3/custom.conf in Ubuntu) modified for good, making impossible to login in a Wayland session (once nvidia driver is disabled). As per this, in case of upgrades or install with configuration files left, we replace the gdm's daemon.conf/custom.conf file in case it matches the one that the disable-wayland tool would produce. https://discourse.gnome.org/t/gdm-3-38-0-has-bad-bug-for-nvidia-users/4517 (LP: #1899673) gdm3 (3.38.1-1) unstable; urgency=medium * New upstream release: - Fix bug leading to users /etc/gdm/custom.conf getting overwritten on nvidia systems (LP: #1899673). - Fix typo in comment - Translation updates * debian/rules: Don't override the runtime-conf path anymore. Upstream fixed the root issue for changing this, so the default runtime configuration file will be correctly written in the runtime path again. gdm3 (3.38.0-2) unstable; urgency=medium * Team upload * d/rules: Set runtime configuration path. In Autotools, the default runtime configuration path used to be ${GDM_RUN_DIR}/custom.conf, but in the Meson build system the fallback changed to be the same as the custom.conf path in /etc (set to /etc/gdm3/daemon.conf in Debian for historical reasons). Explicitly set it to the path we used before switching to Meson, so that configuration changes by gdm-disable-wayland are temporary as intended, and do not persist to a subsequent boot. * Revert "debian/watch: Monitor unstable versions" * d/upstream/metadata: Add * Merge packaging from unstable * Release to unstable -- Marco Trevisan (Treviño) Wed, 14 Oct 2020 15:28:44 +0100 ** Changed in: gdm3 (Ubuntu) Status: In Progress => 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/1899673 Title: gdm 3.38 with nvidia drivers breaks Wayland support (once nvidia drivers are disabled) Status in gdm: Unknown Status in gd
[Desktop-packages] [Bug 1899478] Re: Personal Certificate Not Migrated to Snap-Based Chromium
Thanks for the report Gunter. Just to make sure I understand correctly the problem: we're talking about certificates that chromium shows at chrome://settings/certificates ? You had some personal certificates there in Ubuntu 18.04, and after upgrading to 20.04 they are not there any longer? Were your other chromium settings (current browsing session, history, passwords) correctly imported in the upgrade? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Summary changed: - Personal Certificate Not Migrated to Snap-Based Chromium + [snap] Personal Certificate Not Migrated to Snap-Based Chromium -- 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/1899478 Title: [snap] Personal Certificate Not Migrated to Snap-Based Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: After upgrade from Ubuntu 18.04 to Ubuntu 20.04, login to web sites requiring client certificates is not possible any more. The client certificate list in Chromium is empty. ProblemType: Bug DistroRelease: KDE neon 20.04 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Oct 12 14:26:40 2020 Snap: chromium 85.0.4183.121 (stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2020-10-11 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899478/+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 1898447] Re: HDMI sound output disappears after sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1898447 Title: HDMI sound output disappears after sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am using an Nvidia graphics card with HDMI output. The sound output choice for HDMI is missing from either pavucontrol or the GNOME settings sound settings after waking the computer up from sleep. Running `pacmd list-cards` does show the HDMI sound output listed. I can bring the output back as a choice if I run `pulseaudio -k`, but I will lose the choice to select this output if I put the computer to sleep, leaving me only with the S/PDIF output from my motherboard. I didnt see this issue prior to what I suspect was an `apt upgrade`. Description: Ubuntu 20.04.1 LTS Release: 20.04 Kernel: 5.4.0-48-generic Desktop Environment: GNOME 3.36.3 pulseaudio: Installed: 1:13.99.1-1ubuntu3.6 Candidate: 1:13.99.1-1ubuntu3.6 Version table: *** 1:13.99.1-1ubuntu3.6 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages Hardware Info: CPU: AMD Ryzen 9 3950x GPU: Nvidia RTX 2080ti (Driver 450.66 ) Motherboard: Gigabyte X570 AORUS MASTER --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: umayr 4915 F pulseaudio /dev/snd/pcmC0D3p: umayr 4915 F...m pulseaudio /dev/snd/controlC1: umayr 4915 F pulseaudio /dev/snd/controlC2: umayr 4915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-12 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898447/+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 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
Hi Daniel, someone in mint linux support chat, mesaboogie, firmly believes this can be fixed by adding "snd-hda-intel options model=" to the correct value in my /etc/modprobe.d/alsa-config.conf we tried setting to p950-clevo and rebooting but no luck. any other ideas? Any idea why my sound works perfectly in the live CD every single time, yet in the same exact version of the that same kernel the sound is broken now? I have not done anything unusual with my system install -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook 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.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+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 1164317] Re: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
Just upgraded fro 18.04 to 20.04.1 LTS. After upgrade, no sound. In settings no choice for my sound card. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1164317 Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: no audio coming out while using any of the players (both audio and video - rhythm box, banshee, movie player) in use in ubuntu ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavan 1862 F pulseaudio /dev/snd/pcmC0D1p: raghavan 1862 F...m pulseaudio Date: Thu Apr 4 12:03:53 2013 InstallationDate: Installed on 2013-01-15 (78 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavan 1862 F pulseaudio /dev/snd/pcmC0D1p: raghavan 1862 F...m pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1164317/+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 1900009] [NEW] Window tiled to monitor where most of the window is in instead of where the mouse is.
Public bug reported: Release: Ubuntu Groovy Gorilla (development branch) 20.10 Package version: 3.38.1-1ubuntu1 When I tile windows using edge tiling, I want the window to tile on the same edge that I brought it to, however, if the window is mostly in monitor 1 when I try to tile it to the left (or right) edge of monitor 2, the window will tile to the left (or right) edge of monitor 2. This happens on both my computer with an Nvidia GPU on x11 and my laptop using Intel integrated graphics on Wayland. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/199 Title: Window tiled to monitor where most of the window is in instead of where the mouse is. Status in gnome-shell package in Ubuntu: New Bug description: Release: Ubuntu Groovy Gorilla (development branch) 20.10 Package version: 3.38.1-1ubuntu1 When I tile windows using edge tiling, I want the window to tile on the same edge that I brought it to, however, if the window is mostly in monitor 1 when I try to tile it to the left (or right) edge of monitor 2, the window will tile to the left (or right) edge of monitor 2. This happens on both my computer with an Nvidia GPU on x11 and my laptop using Intel integrated graphics on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/199/+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 1899675] Re: Desktop background image is corrupted after suspend
** Attachment added: "lspci -kv" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899675/+attachment/5422671/+files/lspci.txt -- 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/1899675 Title: Desktop background image is corrupted after suspend Status in gnome-shell package in Ubuntu: Incomplete Bug description: Immediately after resuming from suspend, any desktop background image is corrupted. Expected desktop image to be shown as set in Settings > Background. Notes: * Happens since day 0 of installation. * Does not happen after restart; only after suspend mode. Details: Description: Ubuntu 20.04.1 LTS Release: 20.04 possible alternate application: Gnome-control-center nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-19 (24 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899675/+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 1899675] Re: Desktop background image is corrupted after suspend
** Attachment added: "journalctl -b0" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899675/+attachment/5422672/+files/journal.txt -- 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/1899675 Title: Desktop background image is corrupted after suspend Status in gnome-shell package in Ubuntu: Incomplete Bug description: Immediately after resuming from suspend, any desktop background image is corrupted. Expected desktop image to be shown as set in Settings > Background. Notes: * Happens since day 0 of installation. * Does not happen after restart; only after suspend mode. Details: Description: Ubuntu 20.04.1 LTS Release: 20.04 possible alternate application: Gnome-control-center nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-19 (24 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899675/+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 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
FIX IS to add these lines to /etc/modprobe.d/alsa-config.conf options snd-hda-intel model=clevo-p950 options snd-hda-intel probe_mask=0x1 the cause appears to be NVIDIA drivers I am using the same ones https://pov.es/linux/ubuntu-ubuntu-20-4-installing-nvidia-drivers- breaks-built-in-audio-on-laptop/?print=print mesaboogie in the mintlinux official IRC chat found this technical writeup... The problem did appear to happen after I changed to NVIDIA from the default... why NVIDIA breaks sound i have no idea lol -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook 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.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
This Bug is embarrassing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1881780] Re: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address.
*** This bug is a duplicate of bug 1828107 *** https://bugs.launchpad.net/bugs/1828107 I guess this is a duplicate of https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828107 ** This bug has been marked a duplicate of bug 1828107 gvfs can't list shares from smb servers that disabled SMB1 -- 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/1881780 Title: Nautilus requires SMBv1 to work from "Other Locations" without manually typing in the address. Status in gvfs package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Navigate to Other Locations. Your SMB share should show here. Clicking on the share will cause an error "Unable to access location; Invalid Argument" if SMBv1 is disabled on the remote host. Manually connecting by typing in the address still works. SMBv1 is deprecated due to WannaCry and other vulnerabilities. Please fully deprecate SMBv1 by default. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 2 11:41:18 2020 GsettingsChanges: InstallationDate: Installed on 2019-10-13 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-04-24 (39 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1881780/+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 1900017] [NEW] No text output when exporting to PDF and when printing --- Toolbar icons disappearing
Public bug reported: I create a new text document in Libreoffice with some text: ok; Now: If i export it to pdf, the pdf file is full white, no text output, and same if i want to print it, i only got a white page. I tried to change the font and text color of the document without sucess. (The printer works fine with other software just for info). Also It must be a separate bug but i report it here anyway...The toolbars' icons occasionnaly completly disappear... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Thu Oct 15 22:04:20 2020 InstallationDate: Installed on 2020-09-04 (41 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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/1900017 Title: No text output when exporting to PDF and when printing --- Toolbar icons disappearing Status in libreoffice package in Ubuntu: New Bug description: I create a new text document in Libreoffice with some text: ok; Now: If i export it to pdf, the pdf file is full white, no text output, and same if i want to print it, i only got a white page. I tried to change the font and text color of the document without sucess. (The printer works fine with other software just for info). Also It must be a separate bug but i report it here anyway...The toolbars' icons occasionnaly completly disappear... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Thu Oct 15 22:04:20 2020 InstallationDate: Installed on 2020-09-04 (41 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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/1900017/+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 1894604] Re: Enable zeitgeist plugin
Just a FYI. GNOME activity journal port to python3 is complete. For more details please refer: https://discourse.gnome.org/t/zeitgeist-gnome-activity-journal-1-0/4521/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1894604 Title: Enable zeitgeist plugin Status in rhythmbox package in Ubuntu: New Bug description: Rhythmbox zeitgeist plugin is currently not packaged due to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1313914 Rhythmbox zeitgeist plugin has been ported to Python3 via Gobject introspection bindings: https://gitlab.gnome.org/GNOME/rhythmbox/-/commit/efcb4653a13a723b5b99fb5e387f60d5110ae840 More improvements to Rhythmbox zeitgeist plugin pending review: https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/75/commits Upstream zeitgeist is maintained at: https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/commits/master Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969713 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1894604/+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 1900032] [NEW] Update to 81.0.2
Public bug reported: See https://www.mozilla.org/en-US/firefox/81.0.2/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: Fix Released ** Changed in: firefox (Ubuntu) Status: New => 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/1900032 Title: Update to 81.0.2 Status in firefox package in Ubuntu: Fix Released Bug description: See https://www.mozilla.org/en-US/firefox/81.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1900032/+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 1900057] [NEW] booting interrupted
Public bug reported: After pressing power button (and after upgrade to focal), PC starts up normally. After I enter authentication, though, it shuts down, apparently into sleep mode/suspend/hibernate. Pressing powerbutton again brings up normal desktop and normal use right away. Possibly this is a bug against kernel or gdm3. Ubuntu 20.04.1 LTS xorg: Geïnstalleerd: 1:7.7+19ubuntu14 Kandidaat: 1:7.7+19ubuntu14 Versietabel: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status gdm3: Geïnstalleerd: 3.36.3-0ubuntu0.20.04.1 Kandidaat: 3.36.3-0ubuntu0.20.04.1 Versietabel: *** 3.36.3-0ubuntu0.20.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 00:10:04 2020 DistUpgraded: 2020-10-12 20:07:01,643 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (Bestand of map bestaat niet) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-11-30 (320 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=21af2411-3a11-46c1-9554-cb8ffbfdbd89 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-12 (3 days ago) dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET66WW (2.16 ) dmi.board.name: 6474B84 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/1900057 Title: booting interrupted Status in xorg package in Ubuntu: New Bug description: After pressing power button (and after upgrade to focal), PC starts up normally. After I enter authentication, though, it shuts down, apparently into sleep mode/suspend/hibernate. Pressing powerbutton again brings up normal desktop and normal use right away. Possibly this is a bug against kernel or gdm3. Ubuntu 20.04.1 LTS xorg: Geïnstalleerd: 1:7.7+19ubuntu14 Kandidaat: 1:7.7+19ubuntu14 Versietabel: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status gdm3: Geïnstalleerd: 3.36.3-0ubuntu0.20.04.1 Kandidaat: 3.36.3-0ubuntu0.20.04.1 Versietabel: *** 3.36.3-0ubuntu0.20.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packag
[Desktop-packages] [Bug 1650891] Re: nvidia proprietary driver does not output to HDMI screens
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-367 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1650891 Title: nvidia proprietary driver does not output to HDMI screens Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: When attaching an external screen to my Macbook Pro 15" Retina the external screen stays blank. nvidia-settings report the screen correctly. There are three options to attach a screen: - HDMI directly - via Thunderbold port 1 and 2 I use a Moshi adapter. Cable and adapter used to work properly, HDMI direct worked till 16.04. Using Nouveau driver the external screen works fine (except for overlapping screens) from TB port 2 and HDMI port. TB port 1 works fine with VGA. Thus I presume there is an error in the nvidia 367 driver (I haven't tried the latest update 375.20 from NVidias site yet) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nvidia-367 367.57-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 18 14:30:23 2016 InstallationDate: Installed on 2016-10-22 (57 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nvidia-graphics-drivers-367 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-367_hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1650891/+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 1650897] Re: nvidia proprietary driver does not output to HDMI screens
*** This bug is a duplicate of bug 1650891 *** https://bugs.launchpad.net/bugs/1650891 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-367 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1650897 Title: nvidia proprietary driver does not output to HDMI screens Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: When attaching an external screen to my Macbook Pro 15" Retina the external screen stays blank. nvidia-settings report the screen correctly. There are three options to attach a screen: - HDMI directly - via Thunderbold port 1 and 2 I use a Moshi adapter. Cable and adapter used to work properly, HDMI direct worked till 16.04. Using Nouveau driver the external screen works fine (except for overlapping screens) from TB port 2 and HDMI port. TB port 1 works fine with VGA. Thus I presume there is an error in the nvidia 367 driver (I haven't tried the latest update 375.20 from NVidias site yet) I have reported this error under #1650891 (nvidia-367 driver) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Dec 18 15:09:07 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7] NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2016-10-22 (57 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed root=UUID=9a60a19c-458f-4dca-8617-f7c6cacf9658 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sun Dec 18 14:22:56 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1650897/+subscriptions -- Mailing list: h
[Desktop-packages] [Bug 1900063] [NEW] Sync flatpak 1.8.2-3 (universe) from Debian sid (main)
Public bug reported: Please sync flatpak 1.8.2-3 (universe) from Debian sid (main) Changelog entries since current groovy version 1.8.2-2: flatpak (1.8.2-3) unstable; urgency=medium * d/p/Skip-parental-controls-checks-on-ServiceUnknown-or-NameHa.patch: Add proposed patch to skip parental controls if accountsservice is not installed. The malcontent package (which activates parental controls support) depends on accountsservice, but the libmalcontent-0-0 client library does not, so we need to cope gracefully with the case where neither malcontent nor accountsservice is installed. Presumably, in such installations the sysadmin did not want the parental controls feature. Ideally libmalcontent would do this itself (#972145). (Closes: #972138) * Add Depends on dbus, for the well-known system bus service. Now that the parental controls feature is enabled, Flatpak will refuse to run apps if the D-Bus system bus is unavailable. Previously, it would have partially worked (but with severely reduced functionality, in particular only --user installations). * d/control: Canonicalize case of Multi-Arch * Update lintian overrides to silence some false-positives -- Simon McVittie Thu, 15 Oct 2020 09:47:28 +0100 ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1900063 Title: Sync flatpak 1.8.2-3 (universe) from Debian sid (main) Status in flatpak package in Ubuntu: New Bug description: Please sync flatpak 1.8.2-3 (universe) from Debian sid (main) Changelog entries since current groovy version 1.8.2-2: flatpak (1.8.2-3) unstable; urgency=medium * d/p/Skip-parental-controls-checks-on-ServiceUnknown-or-NameHa.patch: Add proposed patch to skip parental controls if accountsservice is not installed. The malcontent package (which activates parental controls support) depends on accountsservice, but the libmalcontent-0-0 client library does not, so we need to cope gracefully with the case where neither malcontent nor accountsservice is installed. Presumably, in such installations the sysadmin did not want the parental controls feature. Ideally libmalcontent would do this itself (#972145). (Closes: #972138) * Add Depends on dbus, for the well-known system bus service. Now that the parental controls feature is enabled, Flatpak will refuse to run apps if the D-Bus system bus is unavailable. Previously, it would have partially worked (but with severely reduced functionality, in particular only --user installations). * d/control: Canonicalize case of Multi-Arch * Update lintian overrides to silence some false-positives -- Simon McVittie Thu, 15 Oct 2020 09:47:28 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1900063/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Why has this STILL not been rolled out to 20.04??? It was fixed for 19.10, but still not for 20.04... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1900068] [NEW] Upgrade to zeitgeist-1.0.3
Public bug reported: Please do upgrade zeitgeist from current 1.0.2 to 1.0.3. It is required for GNOME Activity Journal to work. GNOME Activity Journal has been ported to GTK3. It will be available in GNOME repos shortly. For more details: https://discourse.gnome.org/t/zeitgeist-gnome-activity-journal-1-0/4521 ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Attachment added: "GNOME Activity Journal - new version based on zeitgeist 1.0.3" https://bugs.launchpad.net/bugs/1900068/+attachment/5422747/+files/multi-view-new.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1900068 Title: Upgrade to zeitgeist-1.0.3 Status in zeitgeist package in Ubuntu: New Bug description: Please do upgrade zeitgeist from current 1.0.2 to 1.0.3. It is required for GNOME Activity Journal to work. GNOME Activity Journal has been ported to GTK3. It will be available in GNOME repos shortly. For more details: https://discourse.gnome.org/t/zeitgeist-gnome-activity- journal-1-0/4521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1900068/+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 1899456] Re: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)
This bug was fixed in the package libreoffice - 1:7.0.2-0ubuntu1 --- libreoffice (1:7.0.2-0ubuntu1) groovy; urgency=medium * New upstream release * Update yaru icon style "2010-10-11" (LP: #1899456) -- Rico Tzschichholz Mon, 12 Oct 2020 09:56:14 +0200 ** Changed in: libreoffice (Ubuntu) Status: Fix Committed => Fix Released -- 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/1899456 Title: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu) Status in libreoffice package in Ubuntu: Fix Released Bug description: The yaru icon style is explicitly shipped within the ubuntu source package of libreoffice. libreoffice 7.0.2~rc2-0ubuntu1 includes yaru icon style "2020-09-28" The final libreoffice 7.0.2-0ubuntu1 is meant to include "2020-10-11" Upstream changes: https://github.com/ubuntu/libreoffice-style-yaru- fullcolor/compare/2020-09-28...2020-10-11 Most noticeable visual changes: * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/105 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/121 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/125 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/141 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1899456/+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 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
Same issue, running ubuntu 20.04.1 with 5.4.0-51-generic kernel. I have an ASUS Zephyrus M GU502GW-AH76 -- 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+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 1895821] Re: No voice typing with chromium snap at google docs
I can confirm the exact same behavior. Google docs "Voice typing" constantly opens and closes the access to the microphone while other websites (like `https://www.onlinemictest.com/`) work normally. When looking at the sound settings while activating voice typing, I can see that the entry which flickr is called "Chromium input". Note that activating the mic on `onlinemictest.com` create *two* consistent entries: "Chromium" and "Chromium input". The major difference I've with OP is that I'm having the problem with both: * Chromium 84.0.4147.135 built on Ubuntu focal/20.04, running on Ubuntu focal/20.04 from ungoogled-chromium (opensuse.org) * Chromium 86.0.4240.75 snap directly from Google using Ubuntu apt trust-proxy. So I'd say snap is not at cause here ([r]which does not take anything to the fact that misusing snap concept to provide Google's opaque-binaries instead of a deb built from sourcecode is still insane[/r]) ** Package changed: chromium-browser (Ubuntu) => chromium (Ubuntu) ** Changed in: chromium (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1895821 Title: No voice typing with chromium snap at google docs Status in chromium package in Ubuntu: Confirmed Bug description: The voice typing feature of google docs is a online speech-to-text converter. It can be found on any google docs document under Toosl>Voice Typing and it only runs with Chrome or Chromium. However while I can use this feature using the google chromium.deb build. I cdoesn't work on the chromium snap. Instead the browser constantly opens and closes the access to the microphone, resulting in a flickering microphone icon in the top right of the screen. The fact that this works with the .deb but not with the snap make me think it is a snap related issue. $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $ apt-cache policy chromium-browser chromium-browser: Installed: (none) Candidate: 1:85.0.4183.83-0ubuntu0.20.04.1 Version table: 1:85.0.4183.83-0ubuntu0.20.04.1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 80.0.3987.163-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages $ apt-cache policy google-chrome-stable google-chrome-stable: Installed: 85.0.4183.102-1 Candidate: 85.0.4183.102-1 Version table: *** 85.0.4183.102-1 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1895821/+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 1899675] Re: [nvidia] Desktop background image is corrupted after suspend
*** This bug is a duplicate of bug 1855757 *** https://bugs.launchpad.net/bugs/1855757 Thanks! Bug 1855757 certainly should have fixed that for you. I might check with other people about that fix. ** Summary changed: - Desktop background image is corrupted after suspend + [nvidia] Desktop background image is corrupted after suspend ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- 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/1899675 Title: [nvidia] Desktop background image is corrupted after suspend Status in gnome-shell package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Immediately after resuming from suspend, any desktop background image is corrupted. Expected desktop image to be shown as set in Settings > Background. Notes: * Happens since day 0 of installation. * Does not happen after restart; only after suspend mode. Details: Description: Ubuntu 20.04.1 LTS Release: 20.04 possible alternate application: Gnome-control-center nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-19 (24 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899675/+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 1899675] Re: [nvidia] Desktop background image is corrupted after suspend
*** This bug is a duplicate of bug 1855757 *** https://bugs.launchpad.net/bugs/1855757 Nevermind. We already have someone else saying bug 1855757 is not fixed. Let's use that again... ** This bug has been marked a duplicate of bug 1855757 [nvidia] Background image corrupted after standby or resume from suspend -- 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/1899675 Title: [nvidia] Desktop background image is corrupted after suspend Status in gnome-shell package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Immediately after resuming from suspend, any desktop background image is corrupted. Expected desktop image to be shown as set in Settings > Background. Notes: * Happens since day 0 of installation. * Does not happen after restart; only after suspend mode. Details: Description: Ubuntu 20.04.1 LTS Release: 20.04 possible alternate application: Gnome-control-center nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-19 (24 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899675/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
That's two people who have said the fix doesn't work in Ubuntu 20.04. But actually I would like to hear from more people to be completely sure. ** Changed in: mutter (Ubuntu Focal) Status: Fix Released => Confirmed ** Changed in: mutter (Ubuntu Focal) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Please also try Ubuntu 20.10 when it is formally released next week. We probably need to reopen that one too. ** Changed in: mutter (Ubuntu) Status: Fix Released => 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1899909] Re: [gdm3] Screen keyboard doesn't work after session locked
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => New -- 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/1899909 Title: [gdm3] Screen keyboard doesn't work after session locked Status in gnome-shell package in Ubuntu: New Bug description: Below explain further details and reproduce instruction to recognize the issue Ubuntu all in one touch screen device with 2 user accounts (eg: root and non-root) [1] Boot the device [2] Ubuntu loads to main login screen (the screen that display all user accounts) then tap on any user account and it brings to next screen to enter the password. Screen keyboard automatically appear then you can enter password and tap enter to login. [3] Lock the session [4] It brings to locked screen that display time [4] Tap on screen once, then brings to existing logged account login screen (not the main login screen that display all accounts list) [5] [Bug] Tap on password input field, screen keyboard doesn't appear. you cannot get it by anyway (Alternative solution) - Tap the user accounts icon located on right side down corner then it bring to locked screen that display time - Tap on screen again, it display main login screen that display all user accounts. Now you can tap on already logged user account icon and it brings to existing logged account login screen, now screen keyboard appear and you can unlock the session (About universal access > enable screen keyboard) If enable that, then it display screen keyboard on 4th step but any key input doesn't appear on password input field. Furthermore that screen keyboard through universal access too annoying because after that, screen keyboard pop up when tap on text field. Ubuntu 20.04.01 3.36.4-1ubuntu1~20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899909/+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 1164317] Re: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all
This bug is closed and has been for a few years. Please open a new bug by running: ubuntu-bug pulseaudio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1164317 Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: no audio coming out while using any of the players (both audio and video - rhythm box, banshee, movie player) in use in ubuntu ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavan 1862 F pulseaudio /dev/snd/pcmC0D1p: raghavan 1862 F...m pulseaudio Date: Thu Apr 4 12:03:53 2013 InstallationDate: Installed on 2013-01-15 (78 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghavan 1862 F pulseaudio /dev/snd/pcmC0D1p: raghavan 1862 F...m pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/08/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1164317/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
I will assume this is groovy. ** Tags added: groovy ** Tags added: raspi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899953/+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 1899956] Re: Opening the Utilities folder and trying to scroll through it will expand and multiply the pages on the Show all applications panel
*** 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/1899956 Title: Opening the Utilities folder and trying to scroll through it will expand and multiply the pages on the Show all applications panel Status in gnome-shell package in Ubuntu: New Bug description: What's expected to happen: Retracting or closing the Utilities folder should not affect the amount of pages displayed on the Show all applications panel. What happens instead: Retracting or closing the Utilities folder increases the amount of dots that represent the pages displayed on the Show all applications panel. A short screencast showcasing the bug is attached to the bug report below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899956/+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 1889102] Re: [ubuntu-dock] App grid has too many page dots on right
There's also a great video showing the issue in duplicate bug 1899956. -- 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/1889102 Title: [ubuntu-dock] App grid has too many page dots on right Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have noticed a bug with the applications menu. I am having a weird issue with adding apps into folders on the menu. If I try opening a folder, the entire screen glitches out and the bar on the right-hand size showing how many pages are on the menu show more pages than there actually is. Occasionally if I try adding or removing an app to a folder, the entire system freezes. The only way I am able to get things back to normal is a forced restart by holding down the power button. The only way I have been able to not come across this issue is to have no folders in my menu at all, which took a while as the system kept crashing during the process. However, I am no longer experiencing the issue with no folders, but it returns when I try creating a folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 16:31:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3f1a] InstallationDate: Installed on 2020-07-22 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56b2 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 004: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81VV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1664842e-9af5-44b6-a3c8-f9235f094044 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN21WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32776 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-14IIL dmi.modalias: dmi:bvnLENOVO:bvrCUCN21WW(V1.10):bd05/27/2020:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32776WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL: dmi.product.family: IdeaPad S340-14IIL dmi.product.name: 81VV dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL dmi.product.version: Lenovo IdeaPad S340-14IIL dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/1889102/+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 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop
** Tags added: groovy raspi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+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 1899971] Re: Problematic dependency on python3-apport causes all Python invocations to install apport hook
** Tags added: focal -- 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/1899971 Title: Problematic dependency on python3-apport causes all Python invocations to install apport hook Status in xorg package in Ubuntu: New Bug description: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver-xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899971/+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 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.
Please report the issue to the developers at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues and then tell us the new issue ID. ** Tags added: groovy multimonitor -- 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/199 Title: Window tiled to monitor where most of the window is in instead of where the mouse is. Status in gnome-shell package in Ubuntu: New Bug description: Release: Ubuntu Groovy Gorilla (development branch) 20.10 Package version: 3.38.1-1ubuntu1 When I tile windows using edge tiling, I want the window to tile on the same edge that I brought it to, however, if the window is mostly in monitor 1 when I try to tile it to the left (or right) edge of monitor 2, the window will tile to the left (or right) edge of monitor 2. This happens on both my computer with an Nvidia GPU on x11 and my laptop using Intel integrated graphics on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/199/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
Dave, can you please report the issue to the developers: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues and then tell us the issue ID? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: New Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899953/+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 1900057] Re: ThinkPad T400 sleeps immediately after login
Does the same problem happen if you select 'Ubuntu on Wayland' from the login screen? ** Summary changed: - booting interrupted + ThinkPad T400 sleeps immediately after login ** Package changed: xorg (Ubuntu) => gnome-shell (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/1900057 Title: ThinkPad T400 sleeps immediately after login Status in gnome-shell package in Ubuntu: New Bug description: After pressing power button (and after upgrade to focal), PC starts up normally. After I enter authentication, though, it shuts down, apparently into sleep mode/suspend/hibernate. Pressing powerbutton again brings up normal desktop and normal use right away. Possibly this is a bug against kernel or gdm3. Ubuntu 20.04.1 LTS xorg: Geïnstalleerd: 1:7.7+19ubuntu14 Kandidaat: 1:7.7+19ubuntu14 Versietabel: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status gdm3: Geïnstalleerd: 3.36.3-0ubuntu0.20.04.1 Kandidaat: 3.36.3-0ubuntu0.20.04.1 Versietabel: *** 3.36.3-0ubuntu0.20.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 00:10:04 2020 DistUpgraded: 2020-10-12 20:07:01,643 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (Bestand of map bestaat niet) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-11-30 (320 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic root=UUID=21af2411-3a11-46c1-9554-cb8ffbfdbd89 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-10-12 (3 days ago) dmi.bios.date: 04/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET66WW (2.16 ) dmi.board.name: 6474B84 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET66WW(2.16):bd04/22/2009:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/1900057/+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 1890930] Re: [amdgpu] Xorg freeze
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1890930 Title: [amdgpu] Xorg freeze Status in linux package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: Ubuntu freeze randomly My laptop is AMD ryzen 5 2500U GPU TADEON VEGA GRAPHIC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 9 13:37:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [103c:84ae] InstallationDate: Installed on 2020-04-25 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Laptop 15-db0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8fad8780-5a61-47b5-8c26-63fbc3a59d18 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84AE dmi.board.vendor: HP dmi.board.version: 86.20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/31/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db0xxx dmi.product.sku: 4PC77PA#AKL dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/linux/+bug/1890930/+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 1892973] Re: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107)
Try nvidia-graphics-driver-390. -- 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/1892973 Title: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107) Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily work. Is GNOME just a cute code project intended as a resume line for people looking for real work? What kind of quality control processes are in place that allow ancient failures, extensively reported, to persist? Is anyone at GNOME able and willing to put on their big-boy pants to get a reliable package suitable for production deployments, released? The command cat /var/log/syslog | grep gnome-session reveals fundamental errors in implementing systemd syntax and references/calls to nonexistent binaries. See the gnome-sesion units in /usr/lib/systemd/user. Maybe getting this right would be a first step to helping the developers understand the environment better. Please see man systemd. Source is, astonishingly, a hybrid of C and Javascript, which doubtless presents a QC nightmare. Has anyone given this any thought? What does it take to get this package to work today? - What is the procedure? What commands must be run? - Why doesn't GNOME simply include these commands in a script, just to make it easier? Does anyone there know how? - Why doesn't GNOME simply compile these commands into the package so it works in the first place? - Will a different graphics card matter? - Which one? - Why, if the drivers support the existing hardware, according to the documentation if not the function? Can this package be made to work today? If not, will this package be ready for production use in the next Ubuntu release (i.e., 20.04.02)? If not, what alternatives exist for production use? These are all serious questions. It is astonishing that this package has been released to the public. It getting out the door poses an existential reputational threat to the GNOME project. Any help in getting this package to work would be most gratefully appreciated. What did you expect to happen I expected the screen not to freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892973/+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.la
[Desktop-packages] [Bug 1890930] Re: [amdgpu] Xorg freeze
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1890930 Title: [amdgpu] Xorg freeze Status in linux package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: Ubuntu freeze randomly My laptop is AMD ryzen 5 2500U GPU TADEON VEGA GRAPHIC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 9 13:37:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [103c:84ae] InstallationDate: Installed on 2020-04-25 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Laptop 15-db0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8fad8780-5a61-47b5-8c26-63fbc3a59d18 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84AE dmi.board.vendor: HP dmi.board.version: 86.20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/31/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db0xxx dmi.product.sku: 4PC77PA#AKL dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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/linux/+bug/1890930/+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 1891713] Re: I am unable to resize windows by clicking on the tops of them and dragging after gnome-shell restarted due to low performance.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1891713 Title: I am unable to resize windows by clicking on the tops of them and dragging after gnome-shell restarted due to low performance. Status in gnome-shell package in Ubuntu: Expired Bug description: When I was saving a document, the computer froze, and so did the desktop, and mouse cursor. Eventually, the mouse cursor reset its position, and the screen flashed black but then back to normal. However, I was then unable to move windows around by clicking and dragging them. I had to manually minimize and then maximize the window back. This mostly happened to Visual Studio Code, which was running while I was saving data in another Java application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 16:26:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-06 (39 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-08-12T16:46:41.139091 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1891713/+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 1891725] Re: Cannot log in xorg, wayland works fine
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1891725 Title: Cannot log in xorg, wayland works fine Status in xorg-server package in Ubuntu: Expired Bug description: stuck on login loop on ubuntu xorg ,but wayland works fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 06:50:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:17e1] InstallationDate: Installed on 2020-08-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X412FA_X412FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ec70f2f9-cfb4-4af6-9a61-2573df2b0483 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X412FA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X412FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX412FA.304:bd08/16/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX412FA_X412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X412FA_X412FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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-server/+bug/1891725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Hey Daniel, the update didn't fix the issue on my laptop (HP Omen 15) the webpage distort after I wake up from hibernation On Thu, Oct 15, 2020 at 7:15 PM Daniel van Vugt <1855...@bugs.launchpad.net> wrote: > Please also try Ubuntu 20.10 when it is formally released next week. We > probably need to reopen that one too. > > ** Changed in: mutter (Ubuntu) >Status: Fix Released => Incomplete > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1894627). > https://bugs.launchpad.net/bugs/1855757 > > Title: > [nvidia] Background image corrupted after standby or resume from > suspend > > Status in mutter package in Ubuntu: > Incomplete > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Won't Fix > Status in nvidia-graphics-drivers-390 package in Ubuntu: > Won't Fix > Status in nvidia-graphics-drivers-435 package in Ubuntu: > Won't Fix > Status in mutter source package in Focal: > Confirmed > Status in nvidia-graphics-drivers-340 source package in Focal: > Won't Fix > Status in nvidia-graphics-drivers-390 source package in Focal: > Won't Fix > Status in nvidia-graphics-drivers-435 source package in Focal: > Won't Fix > > Bug description: > Looks similar to > https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 > > When the computer goes to standby, the background image becomes > corrupted. > > I am able to fix by "killall Xorg" , change the background image > (settings > background) and restart. Haven't tried login logout. > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 > Uname: Linux 5.3.0-24-generic x86_64 > NonfreeKernelModules: nvidia > .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 > 21:54:01 PDT 2018 >GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) > ApportVersion: 2.20.11-0ubuntu8.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Dec 9 10:58:35 2019 > DistUpgraded: Fresh install > DistroCodename: eoan > DistroVariant: ubuntu > DkmsStatus: >nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed >nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) > (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] > InstallationDate: Installed on 2019-11-29 (10 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > MachineType: ASUSTek Computer Inc. G60JX > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic > root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 12/25/2009 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 204 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: G60JX > dmi.board.vendor: PEGATRON CORPORATION > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: PEGATRON Computer Inc. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: > dmi.product.family: PEGA Family > dmi.product.name: G60JX > dmi.product.sku: 0 > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTek Computer Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.99-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core > 2:1.20.5+git20191008-0ubuntu1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20190815-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions > -- You receive
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
This bug is about background wallpaper only. If you have problems with webpages then please open a new bug. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Kashad, I will reopen your bug 1894627 and clarify that is about web browsers. This one is about the background wallpaper. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1894627] Re: Screen Distorted After Hibernation/Power Save when idle
Which web browser(s) are you using? ** This bug is no longer a duplicate of bug 1855757 [nvidia] Background image corrupted after standby or resume from suspend ** Summary changed: - Screen Distorted After Hibernation/Power Save when idle + [nvidia] Web browser distorted after hibernation/power save when idle ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia -- 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/1894627 Title: [nvidia] Web browser distorted after hibernation/power save when idle Status in Ubuntu: Incomplete Bug description: my laptop goes to hibernation/power saver mode when my computer is idle. every time I bring my computer back up, the screen distorted. I have to close all my browsers. Sometimes, shut down the computer. Description: Ubuntu 20.04.1 LTS Release: 20.04 N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 03:33:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-42-generic, x86_64: installed nvidia, 440.100, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8466] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8466] InstallationDate: Installed on 2020-06-23 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=98265a4d-5439-415e-b43c-904265a8559a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2019 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8466 dmi.board.vendor: HP dmi.board.version: 68.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.09:bd04/24/2019:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4CC49UA#ABA dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-06-26T00:47:21.524860 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 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/+bug/1894627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-
[Desktop-packages] [Bug 1900098] [NEW] software-properties-gtk fails to open with error
Public bug reported: When trying to open software-properties-gtk via Terminal (via GUI: “Settings & Livepatch”) the following error is returned in the terminal and software-properties-gtk does not open. ERROR:dbus.proxies:Introspect error on :1.121:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.121 was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 08:17:15 2020 InstallationDate: Installed on 2020-10-09 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1900098 Title: software-properties-gtk fails to open with error Status in software-properties package in Ubuntu: New Bug description: When trying to open software-properties-gtk via Terminal (via GUI: “Settings & Livepatch”) the following error is returned in the terminal and software-properties-gtk does not open. ERROR:dbus.proxies:Introspect error on :1.121:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.121 was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 08:17:15 2020 InstallationDate: Installed on 2020-10-09 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1900098/+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 1900095] [NEW] "Restart Firefox" button quits but doesn't restart after Firefox upgrades
Public bug reported: When I upgrade Firefox via apt upgrade (or, more often, Update Manager) and open a new tab, Firefox shows a page telling me that it's been upgraded and I need to restart it before I can continue browsing. There's a "Restart Firefox" button. I press it, Firefox quits, and then fails to restart. I have to start Firefox myself. This is similar to bug 80773, but that one was fixed back in 2012, so I think this is a new one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 81.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mg 3603 F pulseaudio /dev/snd/controlC0: mg 3603 F pulseaudio BuildID: 20201012085804 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 09:13:04 2020 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:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-08 (7 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=81.0/20200917005511 (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET88W (1.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HES2142P 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:bvrN1QET88W(1.63):bd04/22/2020:svnLENOVO:pn20HES2142P:pvrThinkPadT470:rvnLENOVO:rn20HES2142P:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HES2142P dmi.product.sku: LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1900095 Title: "Restart Firefox" button quits but doesn't restart after Firefox upgrades Status in firefox package in Ubuntu: New Bug description: When I upgrade Firefox via apt upgrade (or, more often, Update Manager) and open a new tab, Firefox shows a page telling me that it's been upgraded and I need to restart it before I can continue browsing. There's a "Restart Firefox" button. I press it, Firefox quits, and then fails to restart. I have to start Firefox myself. This is similar to bug 80773, but that one was fixed back in 2012, so I think this is a new one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 81.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mg 3603 F pulseaudio /dev/snd/controlC0: mg 3603 F pulseaudio BuildID: 20201012085804 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 09:13:04 2020 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:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False Installati