[Desktop-packages] [Bug 1797734] Re: slow calculator startup
This problem persists on Ubuntu 20.04. See this proposal to remove the snap version of the package: https://discourse.ubuntu.com/t/proposal- for-ubuntu-20-04lts/12969/92 Moreover, the apt package cannot currently be found on Ubuntu 20.04. Diagnosis: sudo snap remove gnome-calculator sudo apt-get install gnome-calculator Expected output: apt gnome-calculator successfully installed. Actual output: No apt package "gnome-calculator", but there is a snap with that name. Try "snap install gnome-calculator" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Confirmed Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 408583] Re: thunderbird-gnome-support contains only docs?
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- 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/408583 Title: thunderbird-gnome-support contains only docs? Status in thunderbird package in Ubuntu: Expired Bug description: Binary package hint: thunderbird-gnome-support The package thunderbird-gnome-support should provide GNOME integration for Thunderbird. However, this package does not deliver the desired software as it contains only documentation files: root@portux:~# dpkg -L thunderbird-gnome-support /. /usr /usr/share /usr/share/doc /usr/share/doc/thunderbird-gnome-support /usr/share/doc/thunderbird-gnome-support/copyright /usr/share/doc/thunderbird-gnome-support/changelog.Debian.gz = ProblemType: Bug Architecture: amd64 Date: Mon Aug 3 23:01:29 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: thunderbird-gnome-support 2.0.0.22+build1+nobinonly-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-4.23-generic SourcePackage: thunderbird Uname: Linux 2.6.31-4-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/408583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966428] Re: IMAP: Draft message composed offline is deleted when thunderbird is closed
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- 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/966428 Title: IMAP: Draft message composed offline is deleted when thunderbird is closed Status in thunderbird package in Ubuntu: Expired Bug description: Draft message composed offline is deleted when thunderbird is closed. There is no warning given to the user. Steps to reproduce: 1. Setup IMAP account in Thunderbird 2. Compose message 3. File > Offline > Work Offiline (No Sync) 4. Write message 5. Save message 6. Close Thunderbird 7. Open Thunderbird Result: Message lost. Expected: One of the following two scenarios: 1) Save it to a local (On this PC) Drafts folder while offline. 2) Warn the user that teh data will be lost unless they save the file while online. By searching I found that this affects other thunderbird users, therefore affects all platforms: http://forums.mozillazine.org/viewtopic.php?f=39=702585=9542765 http://jonoscript.wordpress.com/2011/12/07/dear-thunderbird-i-know-you-cant-save-my-draft-please-stop-complaining-about-it/ ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 11.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: komputes 1951 F pulseaudio BuildID: 20120313202109 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x9042 irq 49' Mixer name : 'SigmaTel STAC9271D' Components : 'HDA:83847627,80862501,00100201' Controls : 45 Simple ctrls : 25 Channel: release Date: Tue Mar 27 13:25:10 2012 ForcedLayersAccel: False InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120222) IpRoute: default via 10.153.108.1 dev eth6 proto static 10.153.108.0/24 dev eth6 proto kernel scope link src 10.153.108.150 metric 1 169.254.0.0/16 dev eth6 scope link metric 1000 IwConfig: lono wireless extensions. eth6 no wireless extensions. eth1 no wireless extensions. ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=11.0/20120313202109 (Running) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to precise on 2012-03-23 (4 days ago) WifiSyslog: dmi.bios.date: 06/05/2006 dmi.bios.vendor: Intel Corp. dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG965MQ dmi.board.vendor: Intel Corporation dmi.board.version: AAD37419-102 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/966428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849996] Re: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installati│···········································································
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lirc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1849996 Title: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post- installati│·· Status in lirc package in Ubuntu: Confirmed Bug description: Standard do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 19.10 Package: lirc 0.10.1-6 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 15:12:22 2019 ErrorMessage: installed lirc package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: lirc Title: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1849996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864317] Re: CapsLock toggles group on keyrelease instead of keypress
Found a workaround: install xserver-xorg-hwe, it has a newer version with normal behavior. -- 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/1864317 Title: CapsLock toggles group on keyrelease instead of keypress Status in xorg package in Ubuntu: New Bug description: The behavior is odd and is a reason of a lot of errors due the typing. Moreover it is not possible to switch rapidly between the layouts, particularly, when typing something in both idioms. O working with vim. How to restore the old behavior to change the layout on Keypress? I'm using Ubuntu Xenial, X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-97-generic x86_64 Ubuntu Current Operating System: Linux rosh 4.15.0-72-generic #81~16.04.1-Ubuntu SMP Tue Nov 26 16:34:21 UTC 2019 x86_64 Build Date: 13 October 2017 01:57:05PM xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
It is not a bug, its a feature. To speed up the typing. Set the layout change on CapsLock. (In a case you need old caps behavior, you get it with shift + Caoslock) -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
I confirm Xwrapper root rights worked for me too. Ubuntu 18.04 kernel: 5.3.x and 4.15.x Nvidia driver: 435.21 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864325] [NEW] On press of space key, lock screen got into a loop of trying to show the password field
Public bug reported: I woke the laptop from sleep and pressed "space" key to unlock. Computer went crazy and started a loop of trying to display the password field. Also, there were multiple dropdowns on top of each other for the system tray menu. I use variety, but i am not sure if this is the cause or it is some gnome-shell bug or both. Links to video: https://photos.app.goo.gl/3PxSPsDC5pSkK4P16 Also attaching a journalctl prevboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 21:51:10 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-08 (14 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1864325/+attachment/5330332/+files/prevboot.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/1864325 Title: On press of space key, lock screen got into a loop of trying to show the password field Status in gnome-shell package in Ubuntu: New Bug description: I woke the laptop from sleep and pressed "space" key to unlock. Computer went crazy and started a loop of trying to display the password field. Also, there were multiple dropdowns on top of each other for the system tray menu. I use variety, but i am not sure if this is the cause or it is some gnome-shell bug or both. Links to video: https://photos.app.goo.gl/3PxSPsDC5pSkK4P16 Also attaching a journalctl prevboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 21:51:10 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-08 (14 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
I have an Ubuntu 16.04, how I can restore the normal behavior? I mean change on Keypress -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
I would say, that change on Keypress _must_ be the default behavior, because in an opposite case, there are problems of typing, if toogle in on CapsLock, and you are typing rapidly. -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864317] [NEW] CapsLock toggles group on keyrelease instead of keypress
Public bug reported: The behavior is odd and is a reason of a lot of errors due the typing. Moreover it is not possible to switch rapidly between the layouts, particularly, when typing something in both idioms. O working with vim. How to restore the old behavior to change the layout on Keypress? I'm using Ubuntu Xenial, X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-97-generic x86_64 Ubuntu Current Operating System: Linux rosh 4.15.0-72-generic #81~16.04.1-Ubuntu SMP Tue Nov 26 16:34:21 UTC 2019 x86_64 Build Date: 13 October 2017 01:57:05PM xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. ** 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/1864317 Title: CapsLock toggles group on keyrelease instead of keypress Status in xorg package in Ubuntu: New Bug description: The behavior is odd and is a reason of a lot of errors due the typing. Moreover it is not possible to switch rapidly between the layouts, particularly, when typing something in both idioms. O working with vim. How to restore the old behavior to change the layout on Keypress? I'm using Ubuntu Xenial, X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-97-generic x86_64 Ubuntu Current Operating System: Linux rosh 4.15.0-72-generic #81~16.04.1-Ubuntu SMP Tue Nov 26 16:34:21 UTC 2019 x86_64 Build Date: 13 October 2017 01:57:05PM xorg-server 2:1.18.4-0ubuntu0.7 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
The fix will also be coming with Ubuntu 20.04, is that right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) Status in mutter package in Ubuntu: Triaged Status in xserver-xorg-video-vmware package in Ubuntu: Invalid Bug description: As soon as I set my display to scaled (any percentage) via Settings -> Displays -> Scale, the background image disappears and become all white. When I choose a different background image via Settings -> Background initially nothing happens. As soon as I switch back to 100% scaling, the image I choose before now appears. This problem started right after updating to 19.04. No such issues with either 18.04 or 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:35:49 2019 DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-03-01 (51 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: VMware, Inc. VMware Virtual Platform 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.0.0-13-generic root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864315] [NEW] applet crashes on execution, needs brutal choke to end
Public bug reported: Simple Scan worked perfectly for me today, but only once. The second use and consequent tests resulted in a fail. The printer/scanner is turned on, the applet start is inconspicuous but when I push "scan" the circle of dots keeps on running eternally. I can only stop it by brutally choking the process. Up to now I tried: Update, system restart, complete removal and fresh installation - to no avail. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 18:50:32 2020 InstallationDate: Installed on 2017-10-10 (865 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: FUJITSU ESPRIMO P400 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=d37e1b61-b5cc-4c42-8857-ce7e969fdf24 ro SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2011 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.4.0 R1.7.0 for D2990-A1x dmi.board.name: D2990-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D2990-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$PHW3 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.4.0R1.7.0forD2990-A1x:bd05/03/2011:svnFUJITSU:pnESPRIMOP400:pvr:rvnFUJITSU:rnD2990-A1:rvrS26361-D2990-A1:cvnFUJITSU:ct6:cvrC$PHW3: dmi.product.name: ESPRIMO P400 dmi.sys.vendor: FUJITSU ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1864315 Title: applet crashes on execution, needs brutal choke to end Status in simple-scan package in Ubuntu: New Bug description: Simple Scan worked perfectly for me today, but only once. The second use and consequent tests resulted in a fail. The printer/scanner is turned on, the applet start is inconspicuous but when I push "scan" the circle of dots keeps on running eternally. I can only stop it by brutally choking the process. Up to now I tried: Update, system restart, complete removal and fresh installation - to no avail. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: simple-scan 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 18:50:32 2020 InstallationDate: Installed on 2017-10-10 (865 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: FUJITSU ESPRIMO P400 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=d37e1b61-b5cc-4c42-8857-ce7e969fdf24 ro SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2011 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.4.0 R1.7.0 for D2990-A1x dmi.board.name: D2990-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D2990-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$PHW3 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.4.0R1.7.0forD2990-A1x:bd05/03/2011:svnFUJITSU:pnESPRIMOP400:pvr:rvnFUJITSU:rnD2990-A1:rvrS26361-D2990-A1:cvnFUJITSU:ct6:cvrC$PHW3: dmi.product.name: ESPRIMO P400 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1864315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860425] Re: Manually installed deb package cannot be uninstalled
Same issue on latest Ubuntu Focal with GNOME Software 3.35.91. I have tried multiple different deb packages (Skype, Visual Studio Code, BlueJeans etc.) and there was exactly the same problem with all of them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1860425 Title: Manually installed deb package cannot be uninstalled Status in gnome-software package in Ubuntu: New Bug description: This happens on the latest GNOME Software 3.34.2 on Ubuntu Focal. Manually installed deb package (that does not contain any AppData), for example Steam from Valve (https://store.steampowered.com/about/), cannot be uninstalled using Ubuntu Software. The manually installed package appears under Add-ons section on the Installed tab, but it is gone after Ubuntu Software is restarted. When right clicking the Steam icon in GNOME Shell Overview mode and selecting "Show Details", details page with Ubuntu repository version of steam-launcher is displayed instead. The only way to remove the deb package using GUI is downloading it again, clicking "Install", then clicking "Remove" before closing the app details page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I had the same issue and I had to reinstall 19.04, but anyway I want to use the latest Ubuntu, so I afraid to install it again. Question: How can I check compatibility before updating? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1776044] Re: nvidia-340 crashes display in 18.04 Bionic when no Nvidia GPU present
I have a similar issue. Installed Ubuntu 18.04 on a Ryzen 7 2700x with an old Geforce 8600 GTS. Using the built-in drivers, the video card stalls (took me a long time to figure out it was the video card, after going through all the Ryzen issues). I installed the nvidia-340 as recommended, and the system hangs on boot before the graphic login. I removed the nvidia drivers, and reinstall the default, and it works again, but stalls. I know this is the video stalling, as I can ssh into the machine, and all is working fine on the computer, just the video on the hardware is stalling. -- 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/1776044 Title: nvidia-340 crashes display in 18.04 Bionic when no Nvidia GPU present Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Upgrading to 18.04 (Bionic) desktop on a machine running 17.10 (Artful) and originally installed with Xenial 16.04. Previous release (and other) upgrades had gone without issue. Run the installer, upgrades to 18.04, and reboots. Instead of returning to graphical Ubuntu login prompt, booting starts but gets stuck in a state where the screen is flashing every few seconds between light grey and black. After various experimentation, discovered that the graphical login prompt would return as wanted if I did: sudo apt-get remove nvidia-340 Note - the machine has Intel graphics, HD Graphics 630 (rev 04). Why was nvidia-340 ever installed? I believe I setup this machine by exporting a package list from another machine that DID have nvidia graphics and then importing it (via synaptics package manager) to the machine in question. I believe that nvidia drivers have been installed for all the earlier Ubuntu releases, but only in 18.04 did they cause an issue. I tested this theory on another machine with Intel graphics running 18.04, and sure enough installing nvidia-340 broke the graphical login prompt on reboot - and removing nvidia-340 fixed it again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Jun 9 18:47:58 2018 InstallationDate: Installed on 2017-06-30 (345 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to bionic on 2018-05-31 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1776044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864308] [NEW] c-down-mouse-1 does not work
Public bug reported: For some reason c-down-mouse-1 does not work. I tried to start emacs without init file: "/usr/bin/emacs-gtk -q", but the problem did not disappear. I built my own package from emacs-26.3 sources (emacs-26.3.tar.xz from ftp.gnu.org, build server ubuntu 18.04.3). If I install this package into ubuntu 20.04, then c-down-mouse-1 works ok. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: emacs-gtk 1:26.3+1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 18:51:28 2020 InstallationDate: Installed on 2020-02-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200214) SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs (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 emacs in Ubuntu. https://bugs.launchpad.net/bugs/1864308 Title: c-down-mouse-1 does not work Status in emacs package in Ubuntu: New Bug description: For some reason c-down-mouse-1 does not work. I tried to start emacs without init file: "/usr/bin/emacs-gtk -q", but the problem did not disappear. I built my own package from emacs-26.3 sources (emacs-26.3.tar.xz from ftp.gnu.org, build server ubuntu 18.04.3). If I install this package into ubuntu 20.04, then c-down-mouse-1 works ok. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: emacs-gtk 1:26.3+1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 22 18:51:28 2020 InstallationDate: Installed on 2020-02-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200214) SourcePackage: emacs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1864308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864307] [NEW] Many apps have no icon in Software on Focal
Public bug reported: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Attachment added: "apps.png" https://bugs.launchpad.net/bugs/1864307/+attachment/5330310/+files/apps.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal Status in gnome-software package in Ubuntu: New Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1864307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864301] [NEW] Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
Public bug reported: When I open LibreOffce Writer and decides to resize the Style window on the right of the screen (press F11 to toggle this window), Gnome-Shell completely freezes for a few seconds. I already rebooted and it's 100% reproducible. I initially reported this bug on Gnome-Shell Gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411 You can find more info there (journalctl logs) ** 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/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds Status in gnome-shell package in Ubuntu: New Bug description: When I open LibreOffce Writer and decides to resize the Style window on the right of the screen (press F11 to toggle this window), Gnome- Shell completely freezes for a few seconds. I already rebooted and it's 100% reproducible. I initially reported this bug on Gnome-Shell Gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411 You can find more info there (journalctl logs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
System info: Ubuntu 19.10 gnome-shell: 3.34.1+git20191024-1ubuntu1~19.10.1 -- 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/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds Status in gnome-shell package in Ubuntu: New Bug description: When I open LibreOffce Writer and decides to resize the Style window on the right of the screen (press F11 to toggle this window), Gnome- Shell completely freezes for a few seconds. I already rebooted and it's 100% reproducible. I initially reported this bug on Gnome-Shell Gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411 You can find more info there (journalctl logs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1188569] Re: [SRU]Some keyboard shortcuts randomly stop working
Hello together, I am running Ubuntu 18.04 with the Unity DE. In my case only the keyboard shortcut for changing the input-language is affected. Changing input-method to "none" solves the problem only until waking from the next suspend. The keyboard shortcut stops working after that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1188569 Title: [SRU]Some keyboard shortcuts randomly stop working Status in GNOME Shell: New Status in Unity: Confirmed Status in unity package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: *Impact Hi, Certain shortcuts randomly stops working in my computer. They are Super+s (workspace switcher), Super+Up (switch to workspace above) and Super+Down (switch to workspace below). Other shortcuts work fine. *Test Case A few notes that might help: 1- Reassigning shortcuts make them work again except for Super+s. 2- Rebooting make shortcuts work. 3- I have been using these shortcuts with many previous ubuntu versions and my preferences are old. 4- I am not sure of certain steps that produces the problem. The shortcuts sometimes stop working but once they stop, they do not work unless I reassign them or reboot. I am using Ubuntu 13.04. Thank you * Regression potential None ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell] Date: Fri Jun 7 13:40:06 2013 InstallationDate: Installed on 2013-05-27 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1188569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
I was able to solve the control volume thing but the root problem still there. If someone gets to this point I will show you my solution. I realized (in alsamixer) that I was able to change the speakers volume controlling PCM device instead of Master one. So I searched about that and found that you can make pulseaudio to control another device. All the information is in here: https://askubuntu.com/questions/15069/how- do-i-change-the-way-ubuntu-adjusts-my-volume-mixer-levels However, I think this should be fixed. Thank you for your help ^^ -- 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/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA 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/1596381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864178] Re: Rhythmbox crashes when trying to connect to iPhone
upstream bug https://gitlab.gnome.org/GNOME/rhythmbox/issues/1760 ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #1760 https://gitlab.gnome.org/GNOME/rhythmbox/issues/1760 -- 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/1864178 Title: Rhythmbox crashes when trying to connect to iPhone Status in rhythmbox package in Ubuntu: New Bug description: I connected my iPhone to my laptop running Ubuntu 19.10. Nautilus and Shotwell loaded the device fine. But when I open Rhythmbox, it crashes. I opened Rhythmbox from the terminal to see the error and I got this ``` (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action app.play-repeat can't be activated due to parameter type mismatch (parameter type NULL, target type b) (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action app.play-shuffle can't be activated due to parameter type mismatch (parameter type NULL, target type b) ** Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion failed: (strlen (uri) >= 46) Bail out! Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion failed: (strlen (uri) >= 46) [1]15045 abort (core dumped) rhythmbox ``` Details of the current system: ``` lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ``` ``` apt-cache policy rhythmbox rhythmbox: Installed: 3.4.3-2ubuntu1 Candidate: 3.4.3-2ubuntu1 Version table: *** 3.4.3-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ``` What I expected to happen: I was expected Rhythmbox to show my iPhone under "devices" What actually happned: Rhythmbox just crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1864178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
In my case, the bug apparead when I mounted an encfs volume andf began to navigate on it Linux Mint 19.3 (based on Ubuntu) -- 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/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Confirmed Bug description: I have no idea about the package to blame: gvfs/udev/kernel ? This is now logged: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 27 14:21:10 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el
reverted the work-around in ghostscript ** Changed in: ghostscript (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1862053 Title: Compiler gets stuck (or extremely slow) on ppc64el Status in gcc: In Progress Status in gcc-9 package in Ubuntu: Fix Released Status in ghostscript package in Ubuntu: Fix Released Bug description: I have uploaded Ghostscript 9.50 to focal and it built without any problem on all architectures but ppc64el. On ppc64el the compiler seems to get stuck (or extremely slow) on one of the files of Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to the build process being killed after 150 minutes. See https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407 and https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal- ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1862053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864287] [NEW] pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected
Public bug reported: Yesterday I was using the HDMI cable to duplicate the monitor in the tv and play sound with the tv by selecting HDMI exit sound in ubuntu settings. With the pc turned off I removed the HDMI from the tv but ubuntu doesn't automatically set the exit sound to the default till in the settings there is only that option and till I selected it, ubuntu was still trying to reproduce the audio via HDMI... Also rebooting the system the problem persists. Also by reloading pulseaudio the problem persists. The only solution was installing a third-party program to switch correctly to the default audio exit... lsb_release -rd: Description:Ubuntu 18.04.3 LTS Release:18.04 apt-cache policy pulseaudio: pulseaudio: Installato: 1:11.1-1ubuntu7.2 Candidato: 1:11.1-1ubuntu7.4 Tabella versione: 1:11.1-1ubuntu7.4 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 1:11.1-1ubuntu7.2 100 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** 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/1864287 Title: pulseaudio still trying to reproduce audio to HDMI without the HDMI cable connected Status in pulseaudio package in Ubuntu: New Bug description: Yesterday I was using the HDMI cable to duplicate the monitor in the tv and play sound with the tv by selecting HDMI exit sound in ubuntu settings. With the pc turned off I removed the HDMI from the tv but ubuntu doesn't automatically set the exit sound to the default till in the settings there is only that option and till I selected it, ubuntu was still trying to reproduce the audio via HDMI... Also rebooting the system the problem persists. Also by reloading pulseaudio the problem persists. The only solution was installing a third-party program to switch correctly to the default audio exit... lsb_release -rd: Description: Ubuntu 18.04.3 LTS Release: 18.04 apt-cache policy pulseaudio: pulseaudio: Installato: 1:11.1-1ubuntu7.2 Candidato: 1:11.1-1ubuntu7.4 Tabella versione: 1:11.1-1ubuntu7.4 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 1:11.1-1ubuntu7.2 100 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
I have the same problem on Asus Zenbook UX430UA (Realtek ALC295) in Ubuntu 18.04 with 5.3.0-40-generic linux kernel version. Comment #8 fix's worked for me but now I get the same volume level from my laptop speakers with 1% volume level, than the one I get with 100% volume level. The only thing that I can change from volume controls is that with 0% volume level, the speakers are muted. I have tried with "options snd-hda-intel model=auto,laptop-dmic" but I get the expected behaviour with model=auto (speakers works great but no audio recording from laptop microphone). With "options snd-hda-intel model=laptop-dmic,auto" I get the same behaviour that the one I get with "model=laptop-dmic" only (microphone working but volume control doing nothing). I thought this was fixed, but maybe I'm doing something wrong. -- 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/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA 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/1596381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
