[Desktop-packages] [Bug 1768753] Re: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()
*** This bug is a duplicate of bug 1726145 *** https://bugs.launchpad.net/bugs/1726145 Since the bug this is a duplicate of is marked private, there is no way for us to "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". I found a hint for a workaround here: https://askubuntu.com/questions/927859/libreoffice-writer-crashes-on-start That works for me, too. -- 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/1768753 Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM() Status in libreoffice package in Ubuntu: Confirmed Bug description: libreoffice is crashed ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic i686 ApportVersion: 2.20.9-0ubuntu4 Architecture: i386 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 09:25:08 2018 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-10-18 (561 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=5 SegvAnalysis: Segfault happened at: 0xa2b81c15:movb $0x0,(%eax) PC (0xa2b81c15) ok source "$0x0" ok destination "(%eax)" (0xbf14dfe0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so JNI_CreateJavaVM () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM() UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1768753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768753] Re: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()
*** This bug is a duplicate of bug 1726145 *** https://bugs.launchpad.net/bugs/1726145 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1768753 Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM() Status in libreoffice package in Ubuntu: Confirmed Bug description: libreoffice is crashed ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic i686 ApportVersion: 2.20.9-0ubuntu4 Architecture: i386 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 09:25:08 2018 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-10-18 (561 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=5 SegvAnalysis: Segfault happened at: 0xa2b81c15:movb $0x0,(%eax) PC (0xa2b81c15) ok source "$0x0" ok destination "(%eax)" (0xbf14dfe0) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so JNI_CreateJavaVM () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM() UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1768753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798011] Re: HDD thrashing. System locks all input devices. Hard boot required to regain control.
Solved: On lower spec systems (4GB RAM) the default swap file in /dev/dm-1 of 1GB is insufficient. Addition of new swap file has resolved the stated issues. FilenameTypeSizeUsedPriority /swapfile file4194300 2828-2 /dev/dm-1 partition 999420 0 -3 digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-18-04 -- 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/1798011 Title: HDD thrashing. System locks all input devices. Hard boot required to regain control. Status in firefox package in Ubuntu: New Bug description: When Firefox (default package) is open the HDD will begin thrashing and system become unresponsive. Hard boot only way to stop this as I have left it few hours and thrashing does not stop. Internet activity appears to stop. No specific action required to reproduce this except leave Firefox open. Issue occurs daily. I have seen this issue reported in several versions but I have only seen this occur in 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 62.0.3+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: woombah1501 F pulseaudio BuildID: 20181002130007 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 14:56:29 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-08-14 (62 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.7 metric 100 IwConfig: enp0s25 no wireless extensions. lono wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=62.0.3/20181002130007 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT77AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NONE dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT77AUS:bd05/07/2012:svnLENOVO:pn7360PU5:pvrThinkCentre:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.family: NONE dmi.product.name: 7360PU5 dmi.product.version: ThinkCentre dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792403] Re: Nautilus 3.30 in Gnome Staging PP does not start without tracker package
** Changed in: nautilus Status: Fix Committed => Fix Released -- 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/1792403 Title: Nautilus 3.30 in Gnome Staging PP does not start without tracker package Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus 3.30.0-0ubuntu1~cosmic1 in Gnome Staging PP does not start without tracker package. However the tracker package is now in the universe. The official nautilus version 3.26.4-0ubuntu3 works fine without tracker which is a suggested package anyway. Trying to start nautilus from the terminal I get this error message: Tracker-ERROR **: 20:33:14.659: Unable to find default domain ontology rule /usr/share/tracker/domain-ontologies/default.rule So the nautilus 3.30 seems to need the default.rule file. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1792403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 970431] Re: FF in various Ubuntu and Win installations seems to hang up, when I try to open (url in bug description)
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/970431 Title: FF in various Ubuntu and Win installations seems to hang up, when I try to open (url in bug description) Status in firefox package in Ubuntu: Expired Bug description: *** WARNING - browsing to following URL may cause intense disk activity *** http://mwiacek.com/www/sites/default/files/x9.htm seems to hang up FF in Ubuntu (details attached) and some win7/win xp machines ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: firefox 11.0+build1-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsdsdsdffsdfsdf 1241 F pulseaudio BuildID: 20120310010446 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf0804000 irq 5' Mixer name : 'SigmaTel STAC9221 A1' Components : 'HDA:83847680,83847680,00103401' Controls : 20 Simple ctrls : 12 Channel: release Date: Sun Apr 1 00:17:09 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) IpRoute: default via 10.0.2.2 dev eth0 proto static 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: lono wireless extensions. eth0 no wireless extensions. Plugins: Shockwave Flash - Lib=libflashplayer.so, Location=/usr/lib/flashplugin-installer Windows Media Player Plug-in 10 (compatible; Totem) - Lib=libtotem-gmp-plugin.so, Location=/usr/lib/mozilla/plugins QuickTime Plug-in 7.6.6 - Lib=libtotem-narrowspace-plugin.so, Location=/usr/lib/mozilla/plugins DivX® Web Player - Lib=libtotem-mully-plugin.so, Location=/usr/lib/mozilla/plugins VLC Multimedia Plugin (compatible Totem 3.0.1) - Lib=libtotem-cone-plugin.so, Location=/usr/lib/mozilla/plugins ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=11.0/20120310010446 (Running) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to oneiric on 2012-02-09 (51 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/970431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758178] Re: Firefox has a very delicate goofup on another website
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1758178 Title: Firefox has a very delicate goofup on another website Status in firefox package in Ubuntu: Expired Bug description: On airbnb.com, after filling in your city and other pertinent data, when you go to the Price tab, and slide the marker, for example, to reduce maximum price, airbnb returns with some error message after a long wait, "It seems we are having a problem here. Please try again" or something similar. This always happens, however, on Ubuntu Firefox. It does not happen at all on airbnb.com when using Firefox under Windows 7 with identical settings. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 22 17:31:21 2018 InstallationDate: Installed on 2016-08-09 (590 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) KernLog: SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758169] Re: Firefox has very delicate freezes on a few websites
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1758169 Title: Firefox has very delicate freezes on a few websites Status in firefox package in Ubuntu: Expired Bug description: on www.fifa.com, after selecting the Ticketing tab, Firefox does not display the consequent information, but leaves a large white space on the screen. This tab works perfectly in Windows 7 or 8. on www.vayama.com, Firefox fails when trying to type in an airport name, and will not permit user to select any airports. This feature works perfectly in Windows 7 and 8. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 22 17:02:28 2018 InstallationDate: Installed on 2016-08-09 (590 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) KernLog: SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773535] Re: Delicate failure with Ubuntu when using Firebox email
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1773535 Title: Delicate failure with Ubuntu when using Firebox email Status in firefox package in Ubuntu: Expired Bug description: I received an email from my healthcare provider, Aetna, requesting that I click on a link to take me to my login screen for a list of claims - they wanted some information. Using Ubuntu, the link does create a new Firefox window, but that stays white and never progresses to anything at all. Using Windows and Firefox, this new window immediately fills up with my login information and claims information, exactly as Aetna intended it to do. I have tried the link with Ubuntu multiple times with identical results. I have rebooted and there was no change. I am up-to-date on updates. --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D7p: s 1818 F...m pulseaudio /dev/snd/controlC2: s 1818 F pulseaudio /dev/snd/controlC0: s 1818 F pulseaudio /dev/snd/controlC1: s 1818 F pulseaudio BuildID: 20180704194937 Channel: Unavailable CurrentDesktop: Unity DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) DefaultProfilePrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 16.04 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-09 (706 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.254 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.93 metric 600 Package: firefox 61.0.1+build1-0ubuntu0.16.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile0PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile2PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profile3Extensions: extensions.sqlite corrupt or missing Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile3Locales: extensions.sqlite corrupt or missing Profile3Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile3PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 Profile3PrefSources: prefs.js Profile3Themes: extensions.sqlite corrupt or missing Profile4Extensions: extensions.sqlite corrupt or missing Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile4Locales: extensions.sqlite corrupt or missing Profile4Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile4PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 Profile4PrefSources: prefs.js Profile4Themes: extensions.sqlite corrupt or missing Profile5Extensions: extensions.sqlite corrupt or missing Profile5IncompatibleExtensions: Unavailable (corrupt or
[Desktop-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
I want to add an observation. I upgraded from 16.04 to 18.04 and the first boot already was sluggish and the mouse pointer is slow. First I suspected a baloo_file process to be the cause. It's not. I noticed the fans of my thinkpad spin up. I saw no load on the cpu (as normal user). Also the disk io is low. So what is causing this? Then the sensors still show high temps and it got hot. I noticed also the gpu temp is hot. Then i disabled wayland and rebooted. Still it is slow. Then i booted only into recovery root shell and noticed only as root is a kworker/u16:0 process visible, which produces high load. So now I suspect some other kernel level process is out of control, but I don't know what this kworker process belongs to.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011
[Desktop-packages] [Bug 1802622] [NEW] Ubuntu Cosmic nvidia-340 needs patch for "Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t'
Public bug reported: Since upgrading from Ubuntu 18.04 Bionic to Ubuntu 18.10 Cosmic, I've started seeing issues with getting into Xorg. My config: 01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd G92 [GeForce GTS 250] System Information Manufacturer: Gigabyte Technology Co., Ltd. Product Name: P55A-UD4 Ubuntu 18.04 Cosmic w/nvidia-340 proprietary drivers. This appears to be, in part, due to a newer kernel with stricter permissions around kernel access. This seems to have been fixed in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88 ... by backporting the fix from nvidia-390: https://bugzilla.redhat.com/show_bug.cgi?id=1570493 https://bugzilla.redhat.com/attachment.cgi?id=1425704 Could this patch also be applied to nvidia-340 for Ubuntu? Error I'm seeing on my own system (from dmesg): [ 74.596816] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 74.596945] caller os_map_kernel_space+0x9f/0xb0 [nvidia] mapping multiple BARs [ 75.351656] [ cut here ] [ 75.351661] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)! [ 75.351675] WARNING: CPU: 7 PID: 4310 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 75.351676] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ipmi_devintf ipmi_msghandler ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt snd_hda_codec_realtek nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 input_leds nf_log_ipv4 nf_log_common nvidia_uvm(POE) xt_LOG snd_hda_codec_generic snd_hda_intel snd_hda_codec intel_powerclamp mxm_wmi snd_hda_core kvm_intel snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event kvm nvidia(POE) snd_rawmidi snd_seq snd_seq_device irqbypass drm snd_timer intel_cstate snd xt_limit i7core_edac serio_raw soundcore xt_tcpudp mac_hid wmi xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack sch_fq_codel ip6table_filter it87 hwmon_vid coretemp ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat [ 75.351718] parport_pc nf_conntrack_ftp nf_conntrack libcrc32c ppdev iptable_filter bpfilter sunrpc lp parport ip_tables x_tables autofs4 pata_acpi hid_generic usbhid hid gpio_ich firewire_ohci firewire_core crc_itu_t pata_it8213 r8169 lpc_ich i2c_i801 mii ahci libahci [ 75.351737] CPU: 7 PID: 4310 Comm: Xorg Tainted: P OE 4.18.0-11-generic #12-Ubuntu [ 75.351738] Hardware name: Gigabyte Technology Co., Ltd. P55A-UD4/P55A-UD4, BIOS F15 09/16/2010 [ 75.351741] RIP: 0010:usercopy_warn+0x81/0xa0 [ 75.351742] Code: 50 ac 41 51 4d 89 d8 48 c7 c0 89 8d 4f ac 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 f0 a1 50 ac 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 83 c4 18 c9 c3 48 c7 c6 b2 8a 52 ac 49 89 f1 49 89 f3 eb [ 75.351773] RSP: 0018:bcc5414f3b58 EFLAGS: 00010282 [ 75.351775] RAX: RBX: 9eb29383ae58 RCX: 0006 [ 75.351776] RDX: 0007 RSI: 0092 RDI: 9eb29fdd64b0 [ 75.351777] RBP: bcc5414f3b70 R08: 0001 R09: 03e1 [ 75.351778] R10: 0004 R11: R12: 0003 [ 75.351779] R13: 0001 R14: 9eb29383ae5b R15: 9eb29383aea0 [ 75.351781] FS: 7ff9251eca80() GS:9eb29fdc() knlGS: [ 75.351782] CS: 0010 DS: ES: CR0: 80050033 [ 75.351783] CR2: 7ff9207ca000 CR3: 00020f3f2000 CR4: 06e0 [ 75.351785] Call Trace: [ 75.351791] __check_heap_object+0xc2/0x110 [ 75.351793] __check_object_size+0x14c/0x178 [ 75.351936] os_memcpy_to_user+0x26/0x50 [nvidia] [ 75.352047] _nv001372rm+0xa5/0x260 [nvidia] [ 75.352050] WARNING: kernel stack frame pointer at 8342e4ff in Xorg:4310 has bad value 5ccb4a79 [ 75.352051] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0 [ 75.352053] 84c91694: bcc5414f3b80 (0xbcc5414f3b80) [ 75.352055] 4d93127f: ab669a82 (__check_heap_object+0xc2/0x110) [ 75.352057] d50b634d: bcc5414f3bb0 (0xbcc5414f3bb0) [ 75.352058] f98be371: ab691abc (__check_object_size+0x14c/0x178) [ 75.352059] 6d7335b1: 0003 (0x3) [ 75.352061] 7172f7f5: 9eb29383ae58 (0x9eb29383ae58) [ 75.352062] 7033d970: 55fd55403d80 (0x55fd55403d80) [ 75.352063] f8f0fbc8: 9eb29383ae58 (0x9eb29383ae58) [ 75.352064] 65ef0ef6: bcc5414f3bd8 (0xbcc5414f3bd8) [ 75.352158] 3941ec9f: c0af6d26 (os_memcpy_to_user+0x26/0x50 [nvidia]) [ 75.352159] 4318d8e4: 0003 (0x3) [ 75.352160] ea74c503:
[Desktop-packages] [Bug 1792360] Re: Update to 0.18.0
** Changed in: spice-vdagent (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1792360 Title: Update to 0.18.0 Status in spice-vdagent package in Ubuntu: Fix Released Status in spice-vdagent package in Debian: Fix Released Bug description: The new version is not in Debian yet and includes features (new gtk backend, systemd socket activation, ...), marked as blocked by feature-freeze Update request in Debian https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=905771 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1792360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724572] Re: vino-server crashed with SIGSEGV in _XSend()
** Changed in: vino (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1724572 Title: vino-server crashed with SIGSEGV in _XSend() Status in vino: Fix Released Status in vino package in Ubuntu: Incomplete Status in vino package in Debian: Fix Released Bug description: Following upgrade from 17.04 (Gnome) to 17.10. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: vino 3.8.1-0ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Oct 18 12:59:52 2017 ExecutablePath: /usr/lib/vino/vino-server InstallationDate: Installed on 2017-04-17 (183 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/lib/vino/vino-server ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f2a587b63ce <_XSend+126>: mov(%rax),%rdx PC (0x7f2a587b63ce) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: vino StacktraceTop: _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libXtst.so.6 XTestQueryExtension () from /usr/lib/x86_64-linux-gnu/libXtst.so.6 ?? () Title: vino-server crashed with SIGSEGV in _XSend() UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago) UserGroups: sudo To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/1724572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802610] [NEW] FIle View Windows Don't Snap To Screen Sides On Second Monitor
Public bug reported: When I have a folder open and try to snap the window to the sides of my second monitor nothing happens. Bringing the window to the top of the screen will make it go full screen as expected. Snapping works perfectly on my primary monitor (left, top, right). Other applications like terminal, gedit, and Firefox snap correctly on my second monitor. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1802610 Title: FIle View Windows Don't Snap To Screen Sides On Second Monitor Status in nautilus package in Ubuntu: New Bug description: When I have a folder open and try to snap the window to the sides of my second monitor nothing happens. Bringing the window to the top of the screen will make it go full screen as expected. Snapping works perfectly on my primary monitor (left, top, right). Other applications like terminal, gedit, and Firefox snap correctly on my second monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1802610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802609] [NEW] alot of freezing
Public bug reported: Ubuntu worked perfectly with me twice only i don't know why its freezing when i open any app cant even access ctrl alt f1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 10 02:14:25 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:39d1] Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39d1] InstallationDate: Installed on 2018-11-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80WK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=d82157c0-ebe8-41dc-a55d-30ee1b736357 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4KCN40WW 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 Y520-15IKBN dmi.modalias: dmi:bvnLENOVO:bvr4KCN40WW:bd10/17/2017:svnLENOVO:pn80WK:pvrLenovoY520-15IKBN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBN: dmi.product.family: Y520-15IKBN dmi.product.name: 80WK dmi.product.version: Lenovo Y520-15IKBN dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1802609 Title: alot of freezing Status in xorg package in Ubuntu: New Bug description: Ubuntu worked perfectly with me twice only i don't know why its freezing when i open any app cant even access ctrl alt f1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 10 02:14:25 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:39d1] Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39d1] InstallationDate: Installed on 2018-11-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
[Desktop-packages] [Bug 1802582] Re: Inconsistency in xfce4-mime-settings
There is no attachment. ** Package changed: xorg-server (Ubuntu) => xfce4-settings (Ubuntu) ** Changed in: xfce4-settings (Ubuntu) Status: New => Incomplete -- 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/1802582 Title: Inconsistency in xfce4-mime-settings Status in xfce4-settings package in Ubuntu: Incomplete Bug description: This bug report pertains to Xubuntu 16.04.3 LTS. My current kernel is 4.4.0-116-generic x86_64. Mime types can not be changed consistently. My attached bug report shows the details with screenshots for which I did not find out how to post them here. So look at the attachment, please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1802582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734960] Re: Bluetooth headset profile HSP/HFP doesn't work
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 ** This bug has been marked a duplicate of bug 1576559 Refused to switch profile to headset_head_unit: Not connected -- 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/1734960 Title: Bluetooth headset profile HSP/HFP doesn't work Status in blueman package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP profile, but when i try change sound profile in blueman-manager to HSP/HFP - then i get error "Failed to change profile to headset_head_unit". With profile a2dp headphones work good(clementine, chromium etc..), but I could not get work output headphones in steam games, i listen only silence(i think it's problem of pulseaudio) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pl7ofit3040 F pulseaudio /dev/snd/controlC1: pl7ofit3040 F pulseaudio CurrentDesktop: MATE Date: Tue Nov 28 19:51:59 2017 InstallationDate: Installed on 2016-06-22 (524 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: Bluedio Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pl7ofit3040 F pulseaudio /dev/snd/controlC1: pl7ofit3040 F pulseaudio Symptom_Type: No sound at all Title: [Bluedio, recording] No sound at all UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago) dmi.bios.date: 07/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.38 dmi.board.name: AM2NF6G-VSTA dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1734960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770773] Re: HSP/HFP not working
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 ** This bug is no longer a duplicate of bug 1768625 Bluetooth headset HSP/HFP mode not working in Bionic ** This bug has been marked a duplicate of bug 1576559 Refused to switch profile to headset_head_unit: Not connected -- 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/1770773 Title: HSP/HFP not working Status in pulseaudio package in Ubuntu: Confirmed Bug description: Using the 18.04 release, paired bluetooth headsets' do not work in HSP/HFP mode. [Steps to reproduce] 1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build 2. Go to sound settings > output tab > try switching mode to HSP/HFP mode 3. Press the "test sound" button and try playing sound 4. Go to the input tab and check if bluetooth headset mic is listed [Expected result] After step 3, a window for mono audio test should pop up After step 4, the input tab should list a bluetooth headset mic device [Actual result] After step 3, the window that pops up is for stereo (A2DP) audio test After step 4, the input tab does not list any bluetooth headset mic Logitech H800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1770773/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 ** This bug has been marked a duplicate of bug 1576559 Refused to switch profile to headset_head_unit: Not connected -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
I add this extra information in case it works: I have some "Bluedio F2" brand headphones that do not activate the microphone, however, my Philips SHB4000 hearing aids detect them without any problem (the input). Where in Windows and Android the Bluedio & Philips Microphone works for me without problems. Ubuntu 18.10 nasatome at nasatome-pc in ~ $ uname -r 4.18.0-10-generic nasatome at nasatome-pc in ~ $ bluetoothctl Agent registered [Bluedio F]# devices Device 18:07:21:27:08:11 Bluedio F Device 00:1E:7C:37:EF:22 Philips SHB4000 [Bluedio F]# info 18:07:21:27:08:11 Device 18:07:21:27:08:11 (public) Name: Bluedio F Alias: Bluedio F Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) [Bluedio F]# info 00:1E:7C:37:EF:22 Device 00:1E:7C:37:EF:22 (public) Name: Philips SHB4000 Alias: Philips SHB4000 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: bluetooth:v0039p13A4d0115 ManufacturerData Key: 0x5349 ManufacturerData Value: 53 43SC [Bluedio F]# https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625 -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802576] Re: Syslog filling up
*** This bug is a duplicate of bug 1792702 *** https://bugs.launchpad.net/bugs/1792702 ** This bug has been marked a duplicate of bug 1792702 gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to 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/1802576 Title: Syslog filling up Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The Syslog keeps filling up with Gnome shell errors. bellow is an example of it: org.gnome.Shell.desktop[2475]: #8 0x7fffe34dade0 I resource:///org/gnome/shell/ui/layout.js:209 (0x7f8382b01780 @ 62) Nov 9 14:14:50 org.gnome.Shell.desktop[2475]: == Stack trace for context 0x5618fa9e8330 == Nov 9 14:14:50 --- org.gnome.Shell.desktop[2475]: #0 0x7fffe34d56a0 b /home/notmyname/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:881 (0x7f8266cb6560 @ 2363) Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: #1 0x7fffe34d5710 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8382eb5de0 @ 71) Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: #2 0x7fffe34d57f0 b self-hosted:920 (0x7f8382ef12b8 @ 428) Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: #3 0x7fffe34d70b0 b resource:///org/gnome/shell/ui/overviewControls.js:76 (0x7f8382bcfe68 @ 521) Nov 9 14:14:50 -- org.gnome.Shell.desktop[2475]: #4 0x7fffe34d7120 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8382eb5de0 @ 71) Nov 9 14:14:50 org.gnome.Shell.desktop[2475]: #5 0x7fffe34d9250 b resource:///org/gnome/gjs/modules/_legacy.js:39 (0x7f8382eb5b38 @ 215) Nov 9 14:14:50 --- org.gnome.Shell.desktop[2475]: #6 0x7fffe34d9320 b resource:///org/gnome/shell/ui/overviewControls.js:394 (0x7f8382bd52b8 @ 26) Nov 9 14:14:50 --- org.gnome.Shell.desktop[2475]: #7 0x7fffe34d9390 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8382eb5de0 @ 71) Nov 9 14:14:50 org.gnome.Shell.desktop[2475]: #8 0x7fffe34dade0 I resource:///org/gnome/shell/ui/layout.js:209 (0x7f8382b01780 @ 62) Nov 9 14:14:50 gnome-shell[2475]: Object St.Bin (0x5618fc15f3a0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Nov 9 14:14:50 gnome-shell[2475]: JS ERROR: TypeError: this._porthole is null#012ThumbnailsBox<._getPreferredHeight@//home/notmyname/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:680:1#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/layout.js:209:17#012_updateRegions@resource:///org/gnome/shell/ui/layout.js:982:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 Nov 9 14:14:50 - gnome-shell[2475]: Object St.Bin (0x5618fc160610), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: == Stack trace for context 0x5618fa9e8330 == Nov 9 14:14:50--org.gnome.Shell.desktop[2475]: #0 0x5618fae89fa0 i /home/notmyname/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:802 (0x7f8266cb65e8 @ 22) Nov 9 14:14:50 -- org.gnome.Shell.desktop[2475]: #1 0x7fffe34db3f0 b self-hosted:914 (0x7f8382ef12b8 @ 346) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1802576/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802589] [NEW] No image preview when adding a custom wallpaper
Public bug reported: How to reproduce, 1) Go to unity-control-center->appearance 2) Click on + icon, select a valid image 3) (Expected) GtkFileChooser dialog shows a small preview of the image, 4) (Actual) No, preview. Instead a icon (dialog-question) is shown. This is same for user accounts panel when user tries to add a custom avatar. This reason is in https://bazaar.launchpad.net/~unity-control-center- team/unity-control-center/trunk/view/head:/panels/appearance/cc- appearance-panel.c#L1303 it uses g_file_info_get_content_type which returns an internal string and hence mime_type is always NULL. See: https://bugzilla.gnome.org/show_bug.cgi?id=778424 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Assignee: Khurshid Alam (khurshid-alam) Status: Confirmed ** Tags: disco ** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) ** Changed in: unity-control-center (Ubuntu) Status: New => Confirmed ** Description changed: How to reproduce, 1) Go to unity-control-center->appearance 2) Click on + icon, select a valid image 3) (Expected) GtkFileChooser dialog shows a small preview of the image, 4) (Actual) No, preview. Instead a icon (dialog-question) is shown. This is same for user accounts panel when user tries to add a custom avatar. This reason is in https://bazaar.launchpad.net/~unity-control-center- team/unity-control-center/trunk/view/head:/panels/appearance/cc- appearance-panel.c#L1303 it uses g_file_info_get_content_type which returns an internal string - and hence mime_type was always NULL. + and hence mime_type is always NULL. See: https://bugzilla.gnome.org/show_bug.cgi?id=778424 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1802589 Title: No image preview when adding a custom wallpaper Status in unity-control-center package in Ubuntu: Confirmed Bug description: How to reproduce, 1) Go to unity-control-center->appearance 2) Click on + icon, select a valid image 3) (Expected) GtkFileChooser dialog shows a small preview of the image, 4) (Actual) No, preview. Instead a icon (dialog-question) is shown. This is same for user accounts panel when user tries to add a custom avatar. This reason is in https://bazaar.launchpad.net/~unity-control-center- team/unity-control-center/trunk/view/head:/panels/appearance/cc- appearance-panel.c#L1303 it uses g_file_info_get_content_type which returns an internal string and hence mime_type is always NULL. See: https://bugzilla.gnome.org/show_bug.cgi?id=778424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1802589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off
Locking and sleeping is very buggy for me on a fresh 18.04. It rarely works, other times gnome restarts, and I get in without a login prompt (HUGE security issue), sometimes I can't log in after resume, or I can, but my apps get closed (probably I get fully logged out). Gnome shell also restart when I try to lock (with super+L), and the computer doesn't get locked. Interestingly these bugs were not present on my previous 18.04 install on the very same laptop, and I didn't change a thing (same installer, same programs The only difference is my SSD, but I cannot find any errors on 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/1729028 Title: gnome-shell crashes when monitor sleeps or is turned off Status in gnome-shell package in Ubuntu: Confirmed Bug description: Gnome shell crashes reliably and only after a period of inactivity (15+ minutes). I have not seen it crash while using the desktop - even for hours at a time. I suspect it has something to do with locking the screen or turning off the monitor. However even after attempting to disable both lockscreen and blank screen it still happens. After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in libmutter-1.so.0.0.0[7fc6a72de000+141000] When the crash happens it goes back to the login screen. Logging in works fine. It happens pretty reliably but will sometimes successfully lock and blank the screen. I would say it happens 90% of the time I leave the computer alone for awhile. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 11:34:11 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2017-07-18 (105 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off
** Changed in: gnome-shell (Ubuntu) Status: Expired => 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/1729028 Title: gnome-shell crashes when monitor sleeps or is turned off Status in gnome-shell package in Ubuntu: Confirmed Bug description: Gnome shell crashes reliably and only after a period of inactivity (15+ minutes). I have not seen it crash while using the desktop - even for hours at a time. I suspect it has something to do with locking the screen or turning off the monitor. However even after attempting to disable both lockscreen and blank screen it still happens. After a crash dmesg shows [ 3726.608957] gnome-shell[2666]: segfault at 38 ip 7fc6a7330c30 sp 7fff0d12fe78 error 4 in libmutter-1.so.0.0.0[7fc6a72de000+141000] When the crash happens it goes back to the login screen. Logging in works fine. It happens pretty reliably but will sometimes successfully lock and blank the screen. I would say it happens 90% of the time I leave the computer alone for awhile. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 11:34:11 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'firefox.desktop', 'code.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2017-07-18 (105 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-18 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802584] [NEW] A good amount of pulseaudio modules can't be loaded
Public bug reported: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . - Am I forgetting something? Why can't I load them? + Am I forgetting something? Why can't I load them? Why are they not + listed? -- 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/1802584 Title: A good amount of pulseaudio modules can't be loaded Status in pulseaudio package in Ubuntu: New Bug description: I'm running ubuntu 18.04, and I've verified that this is true on two different installs (one fresh, one updated from 16.04). I wanted to load three modules from pulseaudio (module-ladspa-sink, module-loopback, module-null-sink), but it kept saying "Failure on module initialization" I listed the available modules with "pactl list modules" but none of the three were listed. They still seem to be there in /usr/lib/pulse-12.2/modules/ . Am I forgetting something? Why can't I load them? Why are they not listed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1802584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802586] [NEW] sane-backends library name issues
Public bug reported: There is a dispute in Debian about the package name for the sane library. See especially https://bugs.debian.org/913346 Also https://bugs.debian.org/913125 & https://bugs.debian.org/908681 ** Affects: sane-backends (Ubuntu) Importance: High Status: New ** Tags: block-proposed disco ** Changed in: sane-backends (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1802586 Title: sane-backends library name issues Status in sane-backends package in Ubuntu: New Bug description: There is a dispute in Debian about the package name for the sane library. See especially https://bugs.debian.org/913346 Also https://bugs.debian.org/913125 & https://bugs.debian.org/908681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1802586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802582] [NEW] Inconsistency in xfce4-mime-settings
Public bug reported: This bug report pertains to Xubuntu 16.04.3 LTS. My current kernel is 4.4.0-116-generic x86_64. Mime types can not be changed consistently. My attached bug report shows the details with screenshots for which I did not find out how to post them here. So look at the attachment, please. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1802582 Title: Inconsistency in xfce4-mime-settings Status in xorg-server package in Ubuntu: New Bug description: This bug report pertains to Xubuntu 16.04.3 LTS. My current kernel is 4.4.0-116-generic x86_64. Mime types can not be changed consistently. My attached bug report shows the details with screenshots for which I did not find out how to post them here. So look at the attachment, please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
And your fix helps: Still with SRU version installed: $ cat /sys/class/dmi/id/modalias dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: So, edit edit /lib/udev/hwdb.d/60-keyboard.hwdb: evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnXPS159575:pvr* KEYBOARD_KEY_88=unknown $ sudo udevadm hwdb --update $ sudo udevadm trigger evemu-record shows KEY_UNKNOWN: # Waiting for events # E: 0.01 0004 0004 0028 # EV_MSC / MSC_SCAN 28 E: 0.01 0001 001c # EV_KEY / KEY_ENTER0 E: 0.01 # SYN_REPORT (0) -- +0ms E: 3.143316 0004 0004 0136 # EV_MSC / MSC_SCAN 136 E: 3.143316 0001 00f0 0001 # EV_KEY / KEY_UNKNOWN 1 E: 3.143316 # SYN_REPORT (0) -- +3143ms E: 3.143370 0004 0004 0136 # EV_MSC / MSC_SCAN 136 E: 3.143370 0001 00f0 # EV_KEY / KEY_UNKNOWN 0 E: 3.143370 # SYN_REPORT (0) -- +0ms >>> RESULT: The disabling of the airplane mode works now (and enabling still works). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
The patch to resolve this bug was just accepted to upstream gnome-shell master: see https - gitlab.gnome dot org/GNOME/gnome- shell/merge_requests/140 (For some reason launchpad is not letting me submit a comment with a URL). Might it be possible to back-port this patch to GNOME Shell 3.28 for Bionic? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
I've added a similar comment / request on this related launchpad bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794655] Re: Firefox: Modal dialogs with password fields instantly hide.
The patch to resolve this bug was just accepted to upstream gnome-shell master: see https - gitlab.gnome dot org/GNOME/gnome- shell/merge_requests/140 (For some reason launchpad is not letting me submit a comment with a URL). Might it be possible to back-port this patch to GNOME Shell 3.28 for Bionic? -- 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/1794655 Title: Firefox: Modal dialogs with password fields instantly hide. Status in gnome-shell package in Ubuntu: Triaged Bug description: When I use Bitwarden extension by clicking on the icon, the popup immediately hides. See [1], although further digging suggest the bug was/in iBus, see [2] and [3]. Although, the source (or code path) originates from Gnome-Shell, see [4] and [5]. There is a propose fixed but it hasn't been merged. I'm reporting the issue here, so it can at least be tracked and I can get notified when it arrives in Ubuntu. Note: This issue affects all extensions that uses 'password field', see [6]. Firefox-Version: 62.0 Dist-Version: Ubuntu 18.04.1 LTS Gnome-Shell-Version: 3.28.3-0ubuntu0.18.04.2 iBus-Version: 1.5.17-3ubuntu4 1. https://github.com/bitwarden/browser/issues/694 2. https://bugzilla.mozilla.org/show_bug.cgi?id=1405634#c16 3. https://github.com/ibus/ibus/issues/2002#issuecomment-386537208 4. https://github.com/ibus/ibus/issues/2002#issuecomment-402596959 5. https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 6. https://github.com/MetaMask/metamask-extension/issues/3313#issuecomment-418677844 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767995] Re: Horizontal scroll doesn't honor Natural Scrolling preference
This horizontal scrolling behavior is very confusing. It would be very nice to have this fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1767995 Title: Horizontal scroll doesn't honor Natural Scrolling preference Status in gnome-control-center package in Ubuntu: Confirmed Bug description: It appears that the horizontal scroll setting is locked to only one direction and does not honor the natural scrolling preference. This has been posted on askubuntu.com (https://askubuntu.com/questions/1029128/inverted-horizontal- scrolling-ubuntu-18-04), but hasn't been reported as a bug yet (as per my searches). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: Thank you very much. With the SRU version installed (I hope that's right): sudo evemu-record Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: Wacom HID 486A Pen /dev/input/event6: Wacom HID 486A Finger /dev/input/event7: Intel HID events /dev/input/event8: Intel Virtual Button driver /dev/input/event9: Intel HID 5 button array /dev/input/event10: Integrated_Webcam_HD: Integrate /dev/input/event11: Integrated_Webcam_HD: Integrate /dev/input/event12: DELL080D:00 06CB:7A13 Touchpad /dev/input/event13: Dell WMI hotkeys /dev/input/event14: Video Bus /dev/input/event15: HDA Intel PCH Headphone Mic /dev/input/event16: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event17: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event18: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event19: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event20: HDA Intel PCH HDMI/DP,pcm=10 Select the device event number [0-20]: 4 # EVEMU 1.3 # Kernel: 4.18.0-11-generic # DMI: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: # Input device name: "AT Translated Set 2 keyboard" # Input device ID: bus 0x11 vendor 0x01 product 0x01 version 0xab41 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 1 (KEY_ESC) # Event code 2 (KEY_1) # Event code 3 (KEY_2) # Event code 4 (KEY_3) # Event code 5 (KEY_4) # Event code 6 (KEY_5) # Event code 7 (KEY_6) # Event code 8 (KEY_7) # Event code 9 (KEY_8) # Event code 10 (KEY_9) # Event code 11 (KEY_0) # Event code 12 (KEY_MINUS) # Event code 13 (KEY_EQUAL) # Event code 14 (KEY_BACKSPACE) # Event code 15 (KEY_TAB) # Event code 16 (KEY_Q) # Event code 17 (KEY_W) # Event code 18 (KEY_E) # Event code 19 (KEY_R) # Event code 20 (KEY_T) # Event code 21 (KEY_Y) # Event code 22 (KEY_U) # Event code 23 (KEY_I) # Event code 24 (KEY_O) # Event code 25 (KEY_P) # Event code 26 (KEY_LEFTBRACE) # Event code 27 (KEY_RIGHTBRACE) # Event code 28 (KEY_ENTER) # Event code 29 (KEY_LEFTCTRL) # Event code 30 (KEY_A) # Event code 31 (KEY_S) # Event code 32 (KEY_D) # Event code 33 (KEY_F) # Event code 34 (KEY_G) # Event code 35 (KEY_H) # Event code 36 (KEY_J) # Event code 37 (KEY_K) # Event code 38 (KEY_L) # Event code 39 (KEY_SEMICOLON) # Event code 40 (KEY_APOSTROPHE) # Event code 41 (KEY_GRAVE) # Event code 42 (KEY_LEFTSHIFT) # Event code 43 (KEY_BACKSLASH) # Event code 44 (KEY_Z) # Event code 45 (KEY_X) # Event code 46 (KEY_C) # Event code 47 (KEY_V) # Event code 48 (KEY_B) # Event code 49 (KEY_N) # Event code 50 (KEY_M) # Event code 51 (KEY_COMMA) # Event code 52 (KEY_DOT) # Event code 53 (KEY_SLASH) # Event code 54 (KEY_RIGHTSHIFT) # Event code 55 (KEY_KPASTERISK) # Event code 56 (KEY_LEFTALT) # Event code 57 (KEY_SPACE) # Event code 58 (KEY_CAPSLOCK) # Event code 59 (KEY_F1) # Event code 60 (KEY_F2) # Event code 61 (KEY_F3) # Event code 62 (KEY_F4) # Event code 63 (KEY_F5) # Event code 64 (KEY_F6) # Event code 65 (KEY_F7) # Event code 66 (KEY_F8) # Event code 67 (KEY_F9) # Event code 68 (KEY_F10) # Event code 69 (KEY_NUMLOCK) # Event code 70 (KEY_SCROLLLOCK) # Event code 71 (KEY_KP7) # Event code 72 (KEY_KP8) # Event code 73 (KEY_KP9) # Event code 74 (KEY_KPMINUS) # Event code 75 (KEY_KP4) # Event code 76 (KEY_KP5) # Event code 77 (KEY_KP6) # Event code 78 (KEY_KPPLUS) # Event code 79 (KEY_KP1) # Event code 80 (KEY_KP2) # Event code 81 (KEY_KP3) # Event code 82 (KEY_KP0) # Event code 83 (KEY_KPDOT) # Event code 85 (KEY_ZENKAKUHANKAKU) # Event code 86 (KEY_102ND) # Event code 87 (KEY_F11) # Event code 88 (KEY_F12) # Event code 89 (KEY_RO) # Event code 90 (KEY_KATAKANA) # Event code 91 (KEY_HIRAGANA) # Event code 92 (KEY_HENKAN) # Event code 93 (KEY_KATAKANAHIRAGANA) # Event code 94 (KEY_MUHENKAN) # Event code 95 (KEY_KPJPCOMMA) # Event code 96 (KEY_KPENTER) # Event code 97 (KEY_RIGHTCTRL) # Event code 98 (KEY_KPSLASH) # Event code 99
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sddm (Ubuntu Bionic) Status: New => Confirmed -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sddm (Ubuntu) Status: New => Confirmed -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802576] [NEW] Syslog filling up
Public bug reported: Description:Ubuntu 18.04.1 LTS Release:18.04 gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The Syslog keeps filling up with Gnome shell errors. bellow is an example of it: org.gnome.Shell.desktop[2475]: #8 0x7fffe34dade0 I resource:///org/gnome/shell/ui/layout.js:209 (0x7f8382b01780 @ 62) Nov 9 14:14:50 org.gnome.Shell.desktop[2475]: == Stack trace for context 0x5618fa9e8330 == Nov 9 14:14:50 --- org.gnome.Shell.desktop[2475]: #0 0x7fffe34d56a0 b /home/notmyname/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:881 (0x7f8266cb6560 @ 2363) Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: #1 0x7fffe34d5710 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8382eb5de0 @ 71) Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: #2 0x7fffe34d57f0 b self-hosted:920 (0x7f8382ef12b8 @ 428) Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: #3 0x7fffe34d70b0 b resource:///org/gnome/shell/ui/overviewControls.js:76 (0x7f8382bcfe68 @ 521) Nov 9 14:14:50 -- org.gnome.Shell.desktop[2475]: #4 0x7fffe34d7120 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8382eb5de0 @ 71) Nov 9 14:14:50 org.gnome.Shell.desktop[2475]: #5 0x7fffe34d9250 b resource:///org/gnome/gjs/modules/_legacy.js:39 (0x7f8382eb5b38 @ 215) Nov 9 14:14:50 --- org.gnome.Shell.desktop[2475]: #6 0x7fffe34d9320 b resource:///org/gnome/shell/ui/overviewControls.js:394 (0x7f8382bd52b8 @ 26) Nov 9 14:14:50 --- org.gnome.Shell.desktop[2475]: #7 0x7fffe34d9390 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8382eb5de0 @ 71) Nov 9 14:14:50 org.gnome.Shell.desktop[2475]: #8 0x7fffe34dade0 I resource:///org/gnome/shell/ui/layout.js:209 (0x7f8382b01780 @ 62) Nov 9 14:14:50 gnome-shell[2475]: Object St.Bin (0x5618fc15f3a0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Nov 9 14:14:50 gnome-shell[2475]: JS ERROR: TypeError: this._porthole is null#012ThumbnailsBox<._getPreferredHeight@//home/notmyname/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:680:1#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/layout.js:209:17#012_updateRegions@resource:///org/gnome/shell/ui/layout.js:982:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 Nov 9 14:14:50 - gnome-shell[2475]: Object St.Bin (0x5618fc160610), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: == Stack trace for context 0x5618fa9e8330 == Nov 9 14:14:50--org.gnome.Shell.desktop[2475]: #0 0x5618fae89fa0 i /home/notmyname/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:802 (0x7f8266cb65e8 @ 22) Nov 9 14:14:50 -- org.gnome.Shell.desktop[2475]: #1 0x7fffe34db3f0 b self-hosted:914 (0x7f8382ef12b8 @ 346) ** 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/1802576 Title: Syslog filling up Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The Syslog keeps filling up with Gnome shell errors. bellow is an example of it: org.gnome.Shell.desktop[2475]: #8 0x7fffe34dade0 I resource:///org/gnome/shell/ui/layout.js:209 (0x7f8382b01780 @ 62) Nov 9 14:14:50 org.gnome.Shell.desktop[2475]: == Stack trace for context 0x5618fa9e8330 == Nov 9 14:14:50 --- org.gnome.Shell.desktop[2475]: #0 0x7fffe34d56a0 b /home/notmyname/.local/share/gnome-shell/extensions/workspace-g...@mathematical.coffee.gmail.com/extension.js:881 (0x7f8266cb6560 @ 2363) Nov 9 14:14:50 - org.gnome.Shell.desktop[2475]: #1 0x7fffe34d5710 I
[Desktop-packages] [Bug 1795901] Re: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h
Got the libwebkit2gtk-4.0-dev:amd64=2.22.2-0ubuntu0.18.04.2 update and komorebi compiled successfuly. Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1795901 Title: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk source package in Bionic: Fix Released Status in webkit2gtk package in Debian: Fix Released Bug description: 2.22.2-0ubuntu0.18.04.1, just like https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=906519 /usr/include/webkitgtk-4.0/webkit2/WebKitJavascriptResult.h:28:10: fatal error: jsc/jsc.h: No such file or directory #include ^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1795901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802574] [NEW] laptop screen never comes on after undock / sleep / open of laptop
Public bug reported: I use a ThinkPad dock with two monitors plugged into it. I have a udev job configured to automatically put my laptop to sleep when I undock it. So, I'm working on my laptop in the dock. I undock it and drop it into my backpack. All by itself, it goes to sleep. A few minutes later, I open the laptop and it wakes up. I know it's up because the power light and LED on the lid both go to solid. But the laptop screen never comes on. I've undocked twice since upgrading to 18.10. This has happened both times. It's a regression from 18.04.1. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 13:18:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (43 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-11-08 (1 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic regression-release -- 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/1802574 Title: laptop screen never comes on after undock / sleep / open of laptop Status in gnome-shell package in Ubuntu: New Bug description: I use a ThinkPad dock with two monitors plugged into it. I have a udev job configured to automatically put my laptop to sleep when I undock it. So, I'm working on my laptop in the dock. I undock it and drop it into my backpack. All by itself, it goes to sleep. A few minutes later, I open the laptop and it wakes up. I know it's up because the power light and LED on the lid both go to solid. But the laptop screen never comes on. I've undocked twice since upgrading to 18.10. This has happened both times. It's a regression from 18.04.1. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 13:18:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (43 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-11-08 (1 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1802574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802313] Re: Update gnome-control-center to 3.30.2
Uploaded, thanks! If you want to SRU this then the added patches debian/patches/Debian-s-adduser-doesn-t-allow-uppercase-letters-by-defau.patch | 23 +++ debian/patches/region-Autodisconnect-IBusBus-connected-handler.patch | 29 + will need SRU bugs or removing, since they don't come from upstream debian/patches/08_lowercase_user_names.patch | 23 --- this patch removal will need to be justified too. (Or the adduer related changes dropped from the SRU). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1802313 Title: Update gnome-control-center to 3.30.2 Status in gnome-control-center package in Ubuntu: In Progress Bug description: Merge with Debian Unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1802313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802573] [NEW] Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen
Public bug reported: I have a fresh install of 18.10 on an old Thinkpad x220. Everything works fine with the internal display or an external Dell G2410 (1920x1080) connected via VGA. But when I try to switch to an external BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a time and then it flashes to black. This happens consistently for minutes --it never "settles down". I've tried the default configuration as well as copying xorg.conf from /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both xorg configurations with nomodeset in the bootloader and without. I have not been able to find any configuration that allows this external DisplayPort display to work. The same hardware combination works fine in Windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Nov 9 13:10:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2018-11-09 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 42872WU ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=cd4f21be-48dd-48e7-b289-a59a32bd0be3 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel" Driver "intel" # Option "AccelMethod" "uxa" EndSection dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 42872WU 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:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 42872WU dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1802573 Title: Thinkpad x220 - Unable to use 2560x1440 external display connected via DisplayPort due flashing black screen Status in xorg package in Ubuntu: New Bug description: I have a fresh install of 18.10 on an old Thinkpad x220. Everything works fine with the internal display or an external Dell G2410 (1920x1080) connected via VGA. But when I try to switch to an external BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a time and then it flashes to black. This happens consistently for minutes--it never "settles down". I've tried the default configuration as well as copying xorg.conf from /usr/share/doc/xserver-xorg-video-intel into /etc/x11. I've tried both xorg configurations with nomodeset in the bootloader and without. I have not been able to find any configuration that allows this external DisplayPort display to work. The same hardware combination works fine in Windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Nov 9 13:10:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor
[Desktop-packages] [Bug 1801780] Re: Unable to select Yaru sound theme in sound effects
Yes indeed, I mean the "sound effect" list in the sound settings page. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1801780 Title: Unable to select Yaru sound theme in sound effects Status in gnome-control-center package in Ubuntu: New Bug description: Release of Ubuntu: 18.10 Version of gnome-control-center: 1:3.30.1-1ubuntu2 Expected: Under the sound settings menu, the "default" setting in the sound effects tab should enable the user to reset the sound scheme to the now default "Yaru". "Yaru" should also be listed as an entry. What happened instead: If the sound scheme has already been changed, the "default" setting sets /org/gnome/desktop/sound/theme-name to "freedesktop" instead of the default "Yaru". I had to reset the sound effect by using the "Use default value" toggle in dconf-editor. Interestingly, if the sound scheme is already set to "Yaru", selecting the "default" option in the sound effects tab keeps the scheme set to "Yaru". Furthermore, "Yaru" is not listed as an entry in this tab at all. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 20:45:14 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-10-29 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1801780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1131571] Re: Nautilus properties window "Content" number continuously counting
same problem in 18.10 - ridiculous -- 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/1131571 Title: Nautilus properties window "Content" number continuously counting Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Triaged Bug description: 1. Press Ctrl H in your home directory 2. Selected all files inclusing hidden files 3. Right-click > Properties Result: Size keeps shifting (does not end counting). Can't find out the size of the selected files/folders. Expected: Ends counting with the size of the selected files/folders. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Fri Feb 22 00:59:57 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1290x831+1+52'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'219' InstallationDate: Installed on 2012-12-31 (53 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121230) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-01-01T18:32:27.165937 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1131571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
systemd uses pcre2 for a useful journal feature that we can't enable until pcre2 is in main LP: #1751006 ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Triaged Status in libpam-mount package in Ubuntu: Triaged Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Won't Fix Status in php7.3 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Triaged Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state
I've also got this problem in 18.04 with a Gigabyte motherboard.
When I use front jack input the problem disappears.
--
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/874535
Title:
Volume Slider Jumps, due to rapidly changing hardware jack sense state
Status in alsa-driver package in Ubuntu:
Triaged
Bug description:
In Oneiric Release, The volume slider randomly jump down a notch or
two for fraction of a second, even when there is no audio playing on
the system. If mute is selected, the menu will quickly flip out of
mute mode and back again. This change actually affects the audio
output, resulting in pops correlated with the volume changes.
nVidia GF106 Audio Controller
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jfrorie9959 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
Mixer name : 'Realtek ALC892'
Components : 'HDA:10ec0892,1462522c,00100302'
Controls : 35
Simple ctrls : 20
Card2.Amixer.info:
Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card2.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Package: pulseaudio 1:1.0-0ubuntu3.1
PackageArchitecture: amd64
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Tags: oneiric running-unity
Uname: Linux 3.0.0-14-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V25.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X58A-GD45 (MS-7522)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 5.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
dmi.product.name: MS-7522
dmi.product.version: 5.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+subscriptions
--
Mailing list: https://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 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
@Theo: Thanks for your help. On Fri, Nov 9, 2018 at 10:15 AM Theo Linkspfeifer < 1801...@bugs.launchpad.net> wrote: > I did not spot anything relevant in your log files either. > > Sadly, no idea how to debug this further also. > > ** Package changed: light-locker (Ubuntu) => xorg-server (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1801609 > > Title: > Fails to deactivate dpms off mode after user initiated wake-up > events(not system-suspended, just locked and dpms active) > > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > Xubuntu 18.10 with Xubuntu.desktop session running. System will lock > and turn-off monitors(automatically or manually), but--will not wake- > up monitors upon keyboard or mouse activity. I can type unlock > password, blindly and then the monitors will wake and show unlocked > session. > > WORKAROUND: I uninstalled light-locker, then, I installed gnome- > screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver > if light-locker is not found or installed. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: light-locker (not installed) > ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 > Uname: Linux 4.18.0-10-generic x86_64 > ApportVersion: 2.20.10-0ubuntu13 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Sun Nov 4 13:01:36 2018 > InstallationDate: Installed on 2018-11-03 (0 days ago) > InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > SourcePackage: light-locker > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions > -- 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/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) Status in xorg-server package in Ubuntu: Incomplete Bug description: Xubuntu 18.10 with Xubuntu.desktop session running. System will lock and turn-off monitors(automatically or manually), but--will not wake- up monitors upon keyboard or mouse activity. I can type unlock password, blindly and then the monitors will wake and show unlocked session. WORKAROUND: I uninstalled light-locker, then, I installed gnome- screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver if light-locker is not found or installed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: light-locker (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 4 13:01:36 2018 InstallationDate: Installed on 2018-11-03 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801780] Re: Unable to select Yaru sound theme in sound effects
Thank you for your bug report. What "sound theme selector" are you talking about? Is that the "sound effect" list? That includes file names and not only theme. But yeah, there are some issues in there, unsure if Yaru should be listed but at least selecting default should go back to the correct soundfile -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1801780 Title: Unable to select Yaru sound theme in sound effects Status in gnome-control-center package in Ubuntu: New Bug description: Release of Ubuntu: 18.10 Version of gnome-control-center: 1:3.30.1-1ubuntu2 Expected: Under the sound settings menu, the "default" setting in the sound effects tab should enable the user to reset the sound scheme to the now default "Yaru". "Yaru" should also be listed as an entry. What happened instead: If the sound scheme has already been changed, the "default" setting sets /org/gnome/desktop/sound/theme-name to "freedesktop" instead of the default "Yaru". I had to reset the sound effect by using the "Use default value" toggle in dconf-editor. Interestingly, if the sound scheme is already set to "Yaru", selecting the "default" option in the sound effects tab keeps the scheme set to "Yaru". Furthermore, "Yaru" is not listed as an entry in this tab at all. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 20:45:14 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-10-29 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1801780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801609] Re: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
I did not spot anything relevant in your log files either. Sadly, no idea how to debug this further also. ** Package changed: light-locker (Ubuntu) => xorg-server (Ubuntu) -- 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/1801609 Title: Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) Status in xorg-server package in Ubuntu: Incomplete Bug description: Xubuntu 18.10 with Xubuntu.desktop session running. System will lock and turn-off monitors(automatically or manually), but--will not wake- up monitors upon keyboard or mouse activity. I can type unlock password, blindly and then the monitors will wake and show unlocked session. WORKAROUND: I uninstalled light-locker, then, I installed gnome- screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver if light-locker is not found or installed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: light-locker (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 4 13:01:36 2018 InstallationDate: Installed on 2018-11-03 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
I believe the issue was originally created by that systemd change, https://github.com/systemd/systemd/pull/8762 I've submitted a revert on https://github.com/systemd/systemd/pull/10709 That change is going to have things working as designed, at least on the Inspiron but I'm unsure your issue is the same one at this point. We should probably reject the SRU though, or it would need to go with the systemd change to avoid the regression (but it might still impact on some models) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801609] [NEW] Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active)
You have been subscribed to a public bug: Xubuntu 18.10 with Xubuntu.desktop session running. System will lock and turn-off monitors(automatically or manually), but--will not wake-up monitors upon keyboard or mouse activity. I can type unlock password, blindly and then the monitors will wake and show unlocked session. WORKAROUND: I uninstalled light-locker, then, I installed gnome- screensaver. Xfce4(Xubuntu.desktop) will fallback on gnome-screensaver if light-locker is not found or installed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: light-locker (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 4 13:01:36 2018 InstallationDate: Installed on 2018-11-03 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug cosmic light-locker xubuntu -- Fails to deactivate dpms off mode after user initiated wake-up events(not system-suspended, just locked and dpms active) https://bugs.launchpad.net/bugs/1801609 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server 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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I'm also having an issue with my ux391ua running MATE18.04 with no Windows 10 installed. There is sound output audible with headphones on and volume >100% but it is very distorted and crackly. 18.10 was not helpful and updating kerenel to 19 doesn't change anything. aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 pacmd list-cards 1 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xec228000 irq 135" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9d71" device.product.name = "Sunrise Point-LP HD Audio" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" I've tried various mixer related avenues which do nothing. I noticed that pavucontrol shows sound btw. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA 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/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741027] Re: Screen sharing panels abort using an non-existent vino gsettings key
I can't reproduce the problem on 18.04. Sharing-Panel now appears under system. See https://community.ubuntu.com/t/testing-of-sharing-panel- in-u-c-c-bionic/4215/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: Screen sharing panels abort using an non-existent vino gsettings key Status in unity-control-center package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Status in vino package in Ubuntu: Invalid Bug description: [FFE] This happens because Gnome removed that particular gsettings key. The removal did not happen with the ui removal but rather much later than that. That is why it doesn't work with the latest version of vino. As of now If users try to open the new sharing panel, unity-control- center will crash. This sort behavior is not desired on LTS release (18.04). The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798996] Re: cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1798996 Title: cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: $ gnome-system-monitor cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied And it does not start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780310] Re: Option 'finishings' has value '3' and cannot be edited
** Changed in: system-config-printer Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1780310 Title: Option 'finishings' has value '3' and cannot be edited Status in System Config Printer: New Status in system-config-printer package in Ubuntu: Confirmed Bug description: Whenever I open the print queue for my local printer, I get a dialog box with the message: Option 'finishings' has value '3' and cannot be edited I can dismiss the dialog box and everything seems to work normally, but it is annoying. However, it's possible that some obscure printer feature does not work for me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: system-config-printer 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 5 12:30:50 2018 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2018-07-03 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 Lpstat: device for Ricoh-Aficio-MP-C3500: lpd://hqnvprint02.nvidia.com/secureprint MachineType: ASUS X299-A PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd: Permission denied ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=d418cc23-14fc-41cf-b75f-29644c2a16be ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnASUS:pnX299-A:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: X299-A dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1780310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: New Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802524] [NEW] gsd-media-keys spams my journal with GetVSyncParametersIfAvailable() failed!
Public bug reported: My journalctl is full of these: lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.225054:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.227435:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.242628:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.248687:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161830.258811:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:33 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161833.228289:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:33 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161833.242794:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:33 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161833.379889:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:33 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161833.392316:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:34 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161834.560700:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:34 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161834.575089:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:43 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161843.046966:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:43 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161843.058493:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:44 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161844.250630:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:44 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161844.252612:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:44 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161844.258635:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:44 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161844.258812:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:46 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161846.572135:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:46 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161846.575212:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:46 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161846.591944:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:49 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161849.955126:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:49 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161849.958343:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:49 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161849.974856:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:51 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161851.538471:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! lapkr. 09 16:18:51 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]: [5695:5695:1109/161851.541991:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! In total `journalctl -b
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
@Mario, could you copy the list of devices from "sudo evemu-record" and a log of the record from the keyboard after pressing the key once? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802520] [NEW] gnome-terminal prints gnome settings daemon log messages (?) every time I launch it
Public bug reported: $ gnome-terminal # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) $ Those three log messages printed when I run gnome-terminal are new in 18.10. See also https://gitlab.gnome.org/GNOME/gnome-terminal/issues/42. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-terminal 3.30.1-1ubuntu1 [modified: usr/share/applications/org.gnome.Terminal.desktop] ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 09:18:38 2018 InstallationDate: Installed on 2018-09-27 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to cosmic on 2018-11-08 (0 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1802520 Title: gnome-terminal prints gnome settings daemon log messages (?) every time I launch it Status in gnome-terminal package in Ubuntu: New Bug description: $ gnome-terminal # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) $ Those three log messages printed when I run gnome-terminal are new in 18.10. See also https://gitlab.gnome.org/GNOME/gnome-terminal/issues/42. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-terminal 3.30.1-1ubuntu1 [modified: usr/share/applications/org.gnome.Terminal.desktop] ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 09:18:38 2018 InstallationDate: Installed on 2018-09-27 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to cosmic on 2018-11-08 (0 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1802520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 944382] Re: gnome-terminal crashed with SIGABRT in g_assertion_message()
** Changed in: gnome-terminal Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/944382 Title: gnome-terminal crashed with SIGABRT in g_assertion_message() Status in GNOME Terminal: Won't Fix Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Crash occurs after a Unity general freeze when I tried to scan my music collection with banshee. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Thu Mar 1 22:45:52 2012 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) ProcCmdline: gnome-terminal ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-terminal StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: gnome-terminal crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/944382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 452387] Re: Subtitle delay in Totem
** Changed in: gstreamer Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/452387 Title: Subtitle delay in Totem Status in GStreamer: Expired Status in totem package in Ubuntu: Triaged Bug description: Binary package hint: totem When playing video with external subtitles in Totem, subtitles disappear for few seconds when seeking, for example when user seeks backwards the subtitles aren't shown at all (you have to wait 5-10 seconds for the subtitles to reappear). It happens with many subtitle formats (TMPlayer, MicroDVD, SRT). This doesn't happen with other players (such as VLC or MPlayer). To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/452387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043848] Re: gvfs-mount -u tries to mount, unclear --help
** Changed in: gvfs Status: New => Expired -- 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/1043848 Title: gvfs-mount -u tries to mount, unclear --help Status in gvfs: Expired Status in gvfs package in Ubuntu: Triaged Bug description: I have my USB stick automounted by nautilus/gvfs. Trying to unmount it gives: $ gvfs-mount -u -d /dev/sdb1 Error mounting /dev/sdb1: Device /dev/sdb1 is already mounted at `/media/martin/4805-C45B'. Apparently it tries to mount it again instead of unmount. Same with using --unmount. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1043848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802509] Re: gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1783673 *** https://bugs.launchpad.net/bugs/1783673 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1783673, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1802509/+attachment/5210844/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1802509/+attachment/5210846/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1802509/+attachment/5210850/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1802509/+attachment/5210851/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1802509/+attachment/5210852/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1802509/+attachment/5210853/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1802509/+attachment/5210854/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1783673 gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1802509 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: New Bug description: Was using laptop standalone (laptop LCD display only). Put it into dock which has two monitors plugged into it. Forgot that it was still powered on, so I pushed the power button on the dock, thinking I was waking it up when in fact I was putting it to sleep. When monitors didn't come alive, I opened the lid to see if that would help. That woke it up. Then I closed the lid again to switch to just the monitors. The monitors went blank for a while then I was able to log in, and that's the point at which I got the pop-up about gnome-shell having crashed. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 9 08:26:51 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-09-27 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd7d7a083e0:mov0x128(%rdi),%rax PC (0x7fd7d7a083e0) ok source "0x128(%rdi)" (0x0128) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-3.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-3.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-3.so clutter_x11_handle_event () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-3.so () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to cosmic on 2018-11-08 (0 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1802509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802512] [NEW] xorg does not work
Public bug reported: I;m usin geforce 8800GT ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..1c.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:1c: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 8.2.0 (Ubuntu 8.2.0-7ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Fri Nov 9 14:40:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.18.0-10-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-11-09 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Micro-Star International Co., Ltd MS-7C02 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=a037c8bc-adce-4a23-9b98-d6cd7b029fe0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.00:bd07/02/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 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.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1802512 Title: xorg does not work Status in xorg package in Ubuntu: New Bug description: I;m usin geforce 8800GT ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..1c.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:1c: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 8.2.0 (Ubuntu 8.2.0-7ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Fri Nov 9 14:40:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.18.0-10-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA
[Desktop-packages] [Bug 1797782] Re: evince immediately seg faults
I would point out that the reporter states (in the bug description) "Launching evince from the command line without specifying a file also crashes". This means that the problem is not related to any pdf file, so asking for an upload is perfectly unuseful. Please correct me if I'm wrong. As I experience the same bug (evince crash with segfault, even if I don't open any file), I can provide more information if something could help to solve it. Invoking evince from the command line suddenly crashes, but for example evince --version evince --help both work. Also please tell me if I better open a new bug. Running evince 3.28.4 on Ubuntu 18.04 -- 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/1797782 Title: evince immediately seg faults Status in evince package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 evince: Installed: 3.28.2-1 Candidate: 3.28.2-1 Version table: *** 3.28.2-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Expected Behavior: evince opens and displays PDF document. What Happened: When launching evince, it crashes immediately with a segmentation fault. This happens every time. I have tried opening multiple PDF documents both from the command line and file browser. Launching evince from the command line without specifying a file also crashes. The PDF documents open fine in xpdf. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18 Uname: Linux 4.15.0-1021-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:29:01 2018 InstallationDate: Installed on 2018-09-23 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1797782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen
Thank you, Theo! Based on that workaround, I have added Section "Files" ModulePath "/usr/lib/nvidia-340/xorg" ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg" ModulePath "/usr/lib/xorg/modules" EndSection to the xorg.conf and it's working! Thanks! -- 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/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802507] [NEW] "Launch Calculator" keyboard setting does not work
Public bug reported: Keyboard setting for "Launch Calculator" does _not_ work for snap installed "gnome-calculator". WORKAROUND: $sudo apt install gnome-calculator && sudo snap remove gnome-calculator ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 9 07:12:51 2018 InstallationDate: Installed on 2018-11-08 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug calculator cosmic gnome ** Also affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1802507 Title: "Launch Calculator" keyboard setting does not work Status in gnome-calculator package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Keyboard setting for "Launch Calculator" does _not_ work for snap installed "gnome-calculator". WORKAROUND: $sudo apt install gnome-calculator && sudo snap remove gnome- calculator ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 9 07:12:51 2018 InstallationDate: Installed on 2018-11-08 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center 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/1802507/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
"Now that the snap “gtk-common-themes” is in use, you should no longer experience this issue." What's that supposed to mean? How can you set the bug to invalid? I'm still experiencing the issue. -- 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/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme Status in gnome-calculator package in Ubuntu: Invalid Bug description: It also happen in system monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Apr 28 08:34:55 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.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/1767541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802504] [NEW] TILIX INFO
Public bug reported: TILIX SCREEN AFTER "SUDO APT UPDATE" Сущ:13 http://fr.archive.ubuntu.com/ubuntu bionic-proposed InRelease Сущ:14 http://ppa.launchpad.net/tista/adapta/ubuntu bionic InRelease Сущ:15 http://security.ubuntu.com/ubuntu artful-security InRelease Сущ:16 http://ppa.launchpad.net/ubuntubudgie/backports/ubuntu bionic InRelease Сущ:17 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu bionic InRelease Получено 83,2 kB за 2с (48,8 kB/s) Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово Все пакеты имеют последние версии. W: Цель Sources (main/source/Sources) настроена несколько раз в /etc/apt/sources.list:54 и /etc/apt/sources.list:55 W: Пропускается получение настроенного файла «main/source/Sources», так как репозиторий «https://dl.winehq.org/wine-builds/ubuntu bionic InRelease» его не предоставляет (возможно, репозиторий указан с ошибкой в sources.list?) W: Цель Sources (main/source/Sources) настроена несколько раз в /etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-artful.list:2 и /etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-bionic.list:1 W: Цель Sources (main/source/Sources) настроена несколько раз в /etc/apt/sources.list:54 и /etc/apt/sources.list:55 W: Цель Sources (main/source/Sources) настроена несколько раз в /etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-artful.list:2 и /etc/apt/sources.list.d/ubuntubudgie-ubuntu-backports-bionic.list:1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 410.73 Sat Oct 20 22:12:33 CDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Fri Nov 9 14:11:37 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 410.73, 4.15.0-39-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-33-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 970M] [1043:22da] InstallationDate: Installed on 2017-12-29 (314 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: ASUSTeK COMPUTER INC. G751JT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=3b41e99c-b074-4029-826b-39ad3587 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G751JT.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G751JT 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.:bvrG751JT.202:bd09/10/2014:svnASUSTeKCOMPUTERINC.:pnG751JT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG751JT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G751JT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 8 15:34:32 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu.
[Desktop-packages] [Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account
Confirmed on Ubuntu 18.04.1 LTS, Evolution 3.28.5-0ubuntu0.18.04.1, using EWS. The usual workaround (delete cfg, cache and pkill) works fine. https://askubuntu.com/questions/459504/evolution-appears-unable-to-store-mail-account-details -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1061195 Title: Evolution appears unable to create EWS or Exchange MAPI account Status in evolution-ews: Expired Status in evolution package in Ubuntu: Triaged Status in evolution-data-server package in Ubuntu: Triaged Status in evolution-ews package in Ubuntu: Triaged Status in evolution-mapi package in Ubuntu: Won't Fix Bug description: Evolution appears unable to create an EW or MAPI account. All the steps proceed normally, including fetching the URL (for EWS) or authenticating (for MAPI). However, at the conclusion of account creation process, no actual account appears in the list. I've tried starting Evolution from the command line using various DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm not exactly sure what to do next. I am fairly certain the problem doesn't lie with my corporate Exchange server, as web mail works fine and any other EWS-capable client (like the mail app in Android). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: evolution 3.6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 3 12:40:28 2012 InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Beta amd64 (20120925) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-ews/+bug/1061195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Alberto: Is there any chance that this work-around works without gdm3? I'm using ubuntu-server 18.04 and this my laptop configuration: ➜ ~ inxi -G Graphics: Card-1: Intel HD Graphics 5500 Card-2: NVIDIA GK208M [GeForce 920M] Display Server: X.Org 1.19.6 driver: intel Resolution: 1366x768@60.06hz OpenGL: renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) version: 4.5 Mesa 18.0.5 I followed the steps and installed required packages as follows: ➜ ~ sudo apt install nvidia-driver-390/bionic-updates ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-proposed nvidia-settings/bionic-updates libnvidia-gl-390/bionic-updates libnvidia-compute-390/bionic-updates libnvidia-decode-390/bionic-updates libnvidia-encode-390/bionic-updates libnvidia-ifr1-390/bionic-updates libnvidia-fbc1-390/bionic-updates Then I executed "sudo prime-select nvidia". But after rebooting, I have no openGl support and this error is present at Xorg's logs: VGA arbiter: cannot open kernel arbiter, no multi-card support Nvidia kernel modules are loaded and Xorg seems to register nvidia driver at init. If I try to run glxgears for example, I get the following message: glxinfo Error: couldn't get an RGB, Double-buffered visual And using "sudo prime-select intel" also leaves me without GL. I think this is something related to gpu-manager, because I am not using any display manager, just running xorg from startx. -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed
[Desktop-packages] [Bug 1795924] Re: Update to 7.1-1
https://launchpad.net/ubuntu/+source/fonts-smc-anjalioldlipi/7.1.1-1 ** Changed in: fonts-smc-anjalioldlipi (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-smc-anjalioldlipi in Ubuntu. https://bugs.launchpad.net/bugs/1795924 Title: Update to 7.1-1 Status in fonts-smc-anjalioldlipi package in Ubuntu: Fix Released Bug description: The changes in the new version are non trivial enough to land now in cosmic, that's for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-smc-anjalioldlipi/+bug/1795924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788374] Re: Update to 2.19
https://launchpad.net/ubuntu/+source/libblockdev/2.20-3 ** Changed in: libblockdev (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libblockdev in Ubuntu. https://bugs.launchpad.net/bugs/1788374 Title: Update to 2.19 Status in libblockdev package in Ubuntu: Fix Released Bug description: The version >= 2.17 require ndctl which is in Debian NEW for a while, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829257 It's not likely that we update for cosmic at this point since we would need the new library, a MIR and then a libblockdev update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libblockdev/+bug/1788374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797226] Re: Don't update to 2.57.1
https://launchpad.net/ubuntu/+source/glibmm2.4/2.58.0-1 ** Changed in: glibmm2.4 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glibmm2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1797226 Title: Don't update to 2.57.1 Status in glibmm2.4 package in Ubuntu: Fix Released Bug description: The new version isn't a stable one and the serie doesn't seem really active/leading to a stable version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1797226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797224] Re: Stay on 2.0 for cosmic, update next cycle
** Changed in: tracker (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1797224 Title: Stay on 2.0 for cosmic, update next cycle Status in tracker package in Ubuntu: Triaged Bug description: The new version requires the MIR situation to be sorted out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1797224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789489] Re: update to 0.3.12
https://launchpad.net/ubuntu/+source/volume-key/0.3.12-2 ** Changed in: volume-key (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/1789489 Title: update to 0.3.12 Status in volume-key package in Ubuntu: Fix Released Bug description: The update is not done in Debian yet because it fails to build, waiting for the next update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/1789489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797060] Re: Update to 2.8.1
https://launchpad.net/ubuntu/+source/udisks2/2.8.1-2 ** Changed in: udisks2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1797060 Title: Update to 2.8.1 Status in udisks2 package in Ubuntu: Fix Released Bug description: The new version is not bugfix only, it's for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1797060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758459] Re: Getting transmission 2.93 in Bionic
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1758459 Title: Getting transmission 2.93 in Bionic Status in transmission package in Ubuntu: Confirmed Status in transmission package in Debian: Fix Released Bug description: As referenced on #1752940 some trackers have started blacklisting Transmission versions below 2.93 on the basis that they have no way of telling if an older version has been patched for CVE-2018-5702 or not. Can we try to get 2.93 in Bionic before the final freeze, especially since this is an LTS and 2.92 is starting to get old (Apr 9, 2016). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1758459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801757] Re: all app indicators disappear
Also happening in 18.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Occasionally all of my app indicators just disappear. Right now, for example the only icons in my top bar are the wifi icon, the volume icon, and the battery charge icon. Everything else is gone. The applications associated with the missing indicators, e.g., Dropbox, Cloud Station Drive, Pritunl, Shutter, are still running, but their app indicators are no longer there. The only way I've found to get them back is to log out and log back in. I have no idea what provokes this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 11:37:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (39 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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-extension-appindicator/+bug/1801757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
Ok, so after some debugging the fix is working but it hits a bug on some Dell laptops >From my Inspirong 11 debugging - sudo evemu-record press the airplane key -> double events are generated then to fix it - cat /sys/class/dmi/id/modalias and see what the "pn" is - edit /lib/udev/hwdb.d/60-keyboard.hwdb and add a section (adapt the 'Inspiron*3138' according your 'pn' from the previous command) "#disable double airplane key events on Inspiron 3138 evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnInspiron*3138:pvr* KEYBOARD_KEY_88=unknown" - sudo udevadm hwdb --update - sudo udevadm trigger try again, the flackyness should be fixed (and the event record should show "unknow" keys now) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
Is there a way for the user to undo this GDK_CORE_DEVICE_EVENTS=1 'fix'? My panel is at the bottom of the screen, and I want xinput 2 scrolling -- 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/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: Confirmed Status in xfce4-panel package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790100] Re: unable to write ~ and ^ chars in the terminal
@Egmont: thank you for your input. I just added "gnome-terminal" package in Ubuntu. I hope it is alright for you. Note that I no longer have this issue on my side. @giannione: do you have this bug with Wayland too? I think you can send a few useful info by using a command like "ubuntu-bug -u 1790100" (I don't remember if you need do add "-p gnome-terminal"). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1790100 Title: unable to write ~ and ^ chars in the terminal Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Bug description: Hello, I am using Ubuntu 18.10 and since the last update, I am unable to write ~ and ^ chars in the terminal, in both gnome-terminal and Geany (both using libvte2.91). I don't have this issue with other applications (terminator, xterm, Firefox, Gedit, etc.). But note that now, when I type ^ for the first time in Gedit for example, I see this char but underlined. If I type it a second type (or press space), it is transformed in ^ without line under it. This is a new behaviour that can cause this bug in libvte. Please tell me if I need to join other info! Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libvte-2.91-0 0.52.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 31 11:17:43 2018 InstallationDate: Installed on 2015-08-10 (1116 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: vte2.91 UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790100] Re: unable to write ~ and ^ chars in the terminal
** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1790100 Title: unable to write ~ and ^ chars in the terminal Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Bug description: Hello, I am using Ubuntu 18.10 and since the last update, I am unable to write ~ and ^ chars in the terminal, in both gnome-terminal and Geany (both using libvte2.91). I don't have this issue with other applications (terminator, xterm, Firefox, Gedit, etc.). But note that now, when I type ^ for the first time in Gedit for example, I see this char but underlined. If I type it a second type (or press space), it is transformed in ^ without line under it. This is a new behaviour that can cause this bug in libvte. Please tell me if I need to join other info! Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libvte-2.91-0 0.52.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 31 11:17:43 2018 InstallationDate: Installed on 2015-08-10 (1116 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: vte2.91 UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1790100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802497] [NEW] cannot open a VT2
Public bug reported: On switching to a new session, the existing session is closed and the new opens at the same VT1. Xorg crashes and restart, thus assigning VT1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 9 10:02:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed 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: Dell 3rd Gen Core processor Graphics Controller [1028:056e] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-05-10 (182 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Vostro 3560 ProcEnviron: LANGUAGE=pt_BR:en_US TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-38-generic root=UUID=89a47e85-475c-4f6c-a0d8-d3aae572e9a5 ro rootflags=subvol=@ plymouth:debug=1=1 vesafb.invalid=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0R9N46 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A17 dmi.modalias: dmi:bvnDellInc.:bvrA17:bd04/14/2014:svnDellInc.:pnVostro3560:pvrA17:rvnDellInc.:rn0R9N46:rvrA01:cvnDellInc.:ct8:cvrA17: dmi.product.family: 103C_5335KV dmi.product.name: Vostro 3560 dmi.product.version: A17 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1802497 Title: cannot open a VT2 Status in xorg package in Ubuntu: New Bug description: On switching to a new session, the existing session is closed and the new opens at the same VT1. Xorg crashes and restart, thus assigning VT1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 9 10:02:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-38-generic, x86_64: installed 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: Dell 3rd Gen Core processor Graphics Controller [1028:056e] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-05-10 (182 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Vostro 3560 ProcEnviron: LANGUAGE=pt_BR:en_US TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-38-generic root=UUID=89a47e85-475c-4f6c-a0d8-d3aae572e9a5 ro rootflags=subvol=@ plymouth:debug=1=1 vesafb.invalid=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0R9N46 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A17
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Krzysztof: I don't think your GPU is the same as Andrew's. Please attach your /var/log/gpu-manager.log -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Guys .. I have Nvidia 1050ti with nvidia-390 driver installed. When i boot am on 900 resolution instead of a 1920x1080 normal resolution. Anyone got a solution for that ?? Thanks in advance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783903] Re: DHCP Renewal Kills Anyconnect VPN Connections
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1783903 Title: DHCP Renewal Kills Anyconnect VPN Connections Status in network-manager package in Ubuntu: Confirmed Bug description: When using the Cisco Anyconnect client to connect to my works VPN. The VPN is unstable and drops into re configuring mode when a DHCP request is sent. From my research if I remove the network-manager-config- connectivity-ubuntu package the connection is stable. Similar Issues for like package with FC28: https://bugzilla.redhat.com/show_bug.cgi?id=1576910 Description: Linux Mint 19 Tara Release: 19 network-manager: Installed: 1.10.6-2ubuntu1 Candidate: 1.10.6-2ubuntu1 Version table: *** 1.10.6-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status network-manager-config-connectivity-ubuntu: Installed: 1.10.6-2ubuntu1 Candidate: 1.10.6-2ubuntu1 Version table: *** 1.10.6-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status Log attached next comment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1783903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802208] Re: Reports won't open
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1802208 Title: Reports won't open Status in libreoffice package in Ubuntu: Confirmed Bug description: Reports that were working as of June this year (I haven't opened them since then) now are failing with the following error: Can not activate the factory for org.libreoffice.report.pentaho.SOReportJobFactory$_SOReportJobFactory I tried creating a fresh report to see if its some kind of out of date file format but I get the same error: 1. select "Create Report in Design View..." 2. select "Save" 3. Double click report 4. Same error as above Of course I'm expecting the report to open without an error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-report-builder 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:16:08 2018 InstallationDate: Installed on 2018-02-17 (263 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-01 (190 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768271] Please test proposed package
Hello uvgroovy, or anyone else affected,
Accepted desktop-file-utils into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/desktop-
file-utils/0.23-1ubuntu3.18.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1768271
Title:
sudo update-desktop-database results in "font/ttf" is an invalid MIME
type ("font" is an unregistered media type)
Status in desktop-file-utils package in Ubuntu:
Fix Released
Status in desktop-file-utils source package in Bionic:
Fix Committed
Status in desktop-file-utils source package in Cosmic:
Fix Committed
Bug description:
* Impact
The "update-desktop-database" command outputs some "invalid MIME type"
warnings
* Test case
- install gnome-font-viewer if it's not installed
- $ sudo update-desktop-database
you should not get warnings like those
Error in file "/usr/share/applications/org.gnome.font-viewer.desktop":
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
Error in file "/usr/share/applications/org.gnome.font-viewer.desktop":
"font/otf" is an invalid MIME type ("font" is an unregistered media type)
* Regression potential
Check that fonts files can still be opened from nautilus and preview
(browse e.g /usr/share/fonts/type1/gsfonts in nautilus and open a file
from there)
--
I think this is the same bug as this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1564650
Other info:
1.
$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
2.
$ apt-cache policy desktop-file-utils
desktop-file-utils:
Installed: 0.23-1ubuntu3
Candidate: 0.23-1ubuntu3
Version table:
*** 0.23-1ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3. Expected `sudo update-desktop-database` to not return an error
4. Error regarding invalid MIME type (see above) was returned.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: desktop-file-utils 0.23-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May 1 11:11:05 2018
InstallationDate: Installed on 2018-04-29 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: desktop-file-utils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1768271/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768271] Re: sudo update-desktop-database results in "font/ttf" is an invalid MIME type ("font" is an unregistered media type)
Hello uvgroovy, or anyone else affected,
Accepted desktop-file-utils into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/desktop-
file-utils/0.23-3ubuntu3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Also affects: desktop-file-utils (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: desktop-file-utils (Ubuntu Cosmic)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-cosmic
** Changed in: desktop-file-utils (Ubuntu Bionic)
Status: Triaged => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1768271
Title:
sudo update-desktop-database results in "font/ttf" is an invalid MIME
type ("font" is an unregistered media type)
Status in desktop-file-utils package in Ubuntu:
Fix Released
Status in desktop-file-utils source package in Bionic:
Fix Committed
Status in desktop-file-utils source package in Cosmic:
Fix Committed
Bug description:
* Impact
The "update-desktop-database" command outputs some "invalid MIME type"
warnings
* Test case
- install gnome-font-viewer if it's not installed
- $ sudo update-desktop-database
you should not get warnings like those
Error in file "/usr/share/applications/org.gnome.font-viewer.desktop":
"font/ttf" is an invalid MIME type ("font" is an unregistered media type)
Error in file "/usr/share/applications/org.gnome.font-viewer.desktop":
"font/otf" is an invalid MIME type ("font" is an unregistered media type)
* Regression potential
Check that fonts files can still be opened from nautilus and preview
(browse e.g /usr/share/fonts/type1/gsfonts in nautilus and open a file
from there)
--
I think this is the same bug as this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1564650
Other info:
1.
$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
2.
$ apt-cache policy desktop-file-utils
desktop-file-utils:
Installed: 0.23-1ubuntu3
Candidate: 0.23-1ubuntu3
Version table:
*** 0.23-1ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3. Expected `sudo update-desktop-database` to not return an error
4. Error regarding invalid MIME type (see above) was returned.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: desktop-file-utils 0.23-1ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May 1 11:11:05 2018
InstallationDate: Installed on 2018-04-29 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: desktop-file-utils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1768271/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734597] Re: Error when trying to create review for gnome extension
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. -- 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/1734597 Title: Error when trying to create review for gnome extension Status in gnome-software package in Ubuntu: Confirmed Bug description: I have a error when trying to create review for any gnome extension software. For example, Redmine issues. Test Case: 1) Open redmine issues extension in gnome software and login into Ubuntu account 2) Press a button for writing a review 3) Set rating, write theme and review and try to post you review 4) You will get an error "Got unknown content type text/html from reviews.ubuntu.com" 1) Ubuntu 17.10 2) 3.26.1-0ubuntu2 3) Review must sended successfully 4) Got an error Got unknown content type text/html from reviews.ubuntu.com" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 27 07:18:58 2017 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2017-05-11 (200 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Andrea, could you have a look? ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia
And the Qt team are now working on implementing the patch, so this
should be resolving in a forthcoming Qt release :-) See
https://bugreports.qt.io/browse/QTBUG-71488
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/941826
Title:
dlopen(libGL.so) resolves to mesa rather than nvidia
Status in NVIDIA Drivers Ubuntu:
New
Status in mesa package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
Confirmed
Status in pyqt5 package in Ubuntu:
Invalid
Status in python-qt4 package in Ubuntu:
Invalid
Bug description:
I'm having trouble with a combination of NVIDIA + Python + Qt +
Opengl.
I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and
errors like this these:
QGLShader: could not create shader
Vertex shader for simpleShaderProg (MainVertexShader
) failed to compile
This is an example application triggering the problem:
http://pastebin.com/R0aa8ejs
The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this
error when trying the original demo application from python-qt4-doc. Also,
calling
QtGui.QApplication.setGraphicsSystem("opengl")
produces the same errors.
I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
provided nvidia drivers (where 12.04 includes the most recent driver
for now). After installing the driver using the original NVidia
installer, the applications work as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 974912] Re: net_gateway adds route on wrong interface
** Also affects: network-manager-openvpn via https://bugzilla.gnome.org/show_bug.cgi?id=673636 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/974912 Title: net_gateway adds route on wrong interface Status in NetworkManager-OpenVPN: Unknown Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: When using push route on server side to bypass the vpn for a specific subnet : push "route 1.2.3.0 255.255.255.0 net_gateway" The network manager registers the route on tun0 instead of net_gateway interface : NetworkManager[1149]: Static Route: 1.2.3.0/24 Next Hop: 1.2.3.0 See the route in kernel : 1.2.3.0 192.168.0.1 255.255.255.0 UG0 0 0 tun0 192.168.0.1 is on eth2 but route is registered on tun0 and traffic to 1.2.3.0/24 is sent to tun0 instead of eth2 When I launch openvpn in command line I get the correct route : us=482299 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dns bypass-dhcp,route 1.2.3.0 255.255.255.0 net_gateway,comp-lzo yes,route-gateway x.x.x.x,topology subnet,ping 10,ping-restart 120,ifconfig x.x.x.y 255.255.255.0' us=490292 /sbin/route add -net 1.2.3.0 netmask 255.255.255.0 gw 192.168.0.1 and the route appears on eth2 1.2.3.0 192.168.0.1 255.255.255.0 UG0 0 0 eth2 then traffic to 1.2.3.0/24 flows through eth2 as expected To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/974912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723181] Re: shotwell crashed with SIGSEGV in g_menu_model_get_n_items()
Hello Jan, or anyone else affected, Accepted shotwell into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shotwell/0.30.1-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: shotwell (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: shotwell (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: shotwell (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1723181 Title: shotwell crashed with SIGSEGV in g_menu_model_get_n_items() Status in shotwell package in Ubuntu: Fix Released Status in shotwell source package in Bionic: New Status in shotwell source package in Cosmic: Fix Committed Status in shotwell package in Fedora: Confirmed Bug description: * Impact Shotwell hits a segfault in some situations * Test case There is no specific steps described to lead to the issue. The upstream commit "Fix crash when dismissing modifications". The issue is being reported to e.u.c though at least under those ids https://errors.ubuntu.com/problem/9dfc154a07b6ec76929e2c3c74419ac85a1de015 https://errors.ubuntu.com/problem/44455d848d6d64d4838e9a5af557eb0b092bd669 If the fix is right the new version should get no report * Regression potential Check that the notifications still work as they should and that there is no other visible regressions It happened during opening and closing some raw photos. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: shotwell 0.26.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 18:27:38 2017 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2017-10-06 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: shotwell /media/username/podatki\ in\ backup/SLIKE\ iz\ MY\ PICTURES\ 18GB/PIKNIK\ 3.VS/IMG_3803.CR2 SegvAnalysis: Segfault happened at: 0x7fa291b2e510 : mov (%rdi),%rax PC (0x7fa291b2e510) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: shotwell StacktraceTop: g_menu_model_get_n_items () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: shotwell crashed with SIGSEGV in g_menu_model_get_n_items() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia
I have found the source of the bug and provided a patch: see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913287
** Bug watch added: Debian Bug tracker #913287
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913287
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/941826
Title:
dlopen(libGL.so) resolves to mesa rather than nvidia
Status in NVIDIA Drivers Ubuntu:
New
Status in mesa package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
Confirmed
Status in pyqt5 package in Ubuntu:
Invalid
Status in python-qt4 package in Ubuntu:
Invalid
Bug description:
I'm having trouble with a combination of NVIDIA + Python + Qt +
Opengl.
I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and
errors like this these:
QGLShader: could not create shader
Vertex shader for simpleShaderProg (MainVertexShader
) failed to compile
This is an example application triggering the problem:
http://pastebin.com/R0aa8ejs
The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this
error when trying the original demo application from python-qt4-doc. Also,
calling
QtGui.QApplication.setGraphicsSystem("opengl")
produces the same errors.
I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
provided nvidia drivers (where 12.04 includes the most recent driver
for now). After installing the driver using the original NVidia
installer, the applications work as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Confirmed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802353] Re: Ubuntu 18.04 falls back to LLVMpipe (CPU render) with Intel graphics (i9-9900k => UHD-630)
*** This bug is a duplicate of bug 1789924 *** https://bugs.launchpad.net/bugs/1789924 thanks, this is a dupe of 1789924, mesa doesn't have 3e98 yet in a stable release ** This bug has been marked a duplicate of bug 1789924 Missing Intel GPU pci-id's -- 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/1802353 Title: Ubuntu 18.04 falls back to LLVMpipe (CPU render) with Intel graphics (i9-9900k => UHD-630) Status in xorg-server package in Ubuntu: Incomplete Bug description: A fresh Xubuntu 18.04.1 install (from an ISO), on a machine with only the Intel integrated graphics (i9-9900k => UHD-630). The graphic drivers module seems to be properly loaded, but X rendering seems to fallback to LLVMpipe. This was the case immediately after the install. The performance of the SW rendering improved significantly after the first update with the latest packages. $ glxinfo | grep "OpenGL" OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) OpenGL version string: 3.0 Mesa 18.0.5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) dmesg output: [4.725296] [drm] Replacing VGA console driver [4.731702] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.731704] [drm] Driver supports precise vblank timestamp query. [4.733885] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [4.734288] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [5.003709] [drm] failed to retrieve link info, disabling eDP [5.004608] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 [5.005628] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [5.005799] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 [5.174759] fbcon: inteldrmfb (fb0) is primary device [5.209969] Console: switching to colour frame buffer device 320x90 [5.229823] i915 :00:02.0: fb0: inteldrmfb frame buffer device I tried using the latest stable mesa from ubuntu-x-swat/updates but it did not help (I ppa-purge'd it before generating the bug report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libegl1 1.0.0-2ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 8 17:52:03 2018 InstallationDate: Installed on 2018-11-06 (2 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: libglvnd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1802353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libdrm (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Confirmed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Confirmed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802489] [NEW] Xorg freeze
Public bug reported: After upgrading to Ubuntu 18.10, the system won't boot any more correctly. When booting, it will get stuck at a purple screen and never show the login screen. Selecting the recovery boot in GRUB and continue the boot in the recovery boots the system correctly. dmesg shows a kernel warning: [ 19.856655] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 19.856665] WARNING: CPU: 3 PID: 1742 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 19.856665] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc devlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter binfmt_misc nvidia_uvm(POE) eeepc_wmi asus_wmi wmi_bmof sparse_keymap joydev intel_rapl cp210x usbserial x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi input_leds snd_hda_codec_realtek kvm snd_hda_codec_generic irqbypass crct10dif_pclmul snd_hda_intel crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec snd_hda_core snd_hwdep snd_pcm nvidia_drm(POE) snd_seq_midi aesni_intel nvidia_modeset(POE) snd_seq_midi_event aes_x86_64 crypto_simd cryptd glue_helper intel_cstate snd_rawmidi [ 19.856694] intel_rapl_perf nvidia(POE) serio_raw i915 snd_seq drm_kms_helper drm snd_seq_device ipmi_devintf snd_timer snd ipmi_msghandler i2c_algo_bit fb_sys_fops syscopyarea sysfillrect soundcore sysimgblt video mac_hid mei_me mei wmi sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid pata_acpi gpio_ich psmouse ahci libahci i2c_i801 lpc_ich r8169 mii pata_via [ 19.856722] CPU: 3 PID: 1742 Comm: Xorg Tainted: P OE 4.18.0-11-generic #12-Ubuntu [ 19.856722] Hardware name: System manufacturer System Product Name/P8H67-M PRO, BIOS 3904 04/27/2013 [ 19.856724] RIP: 0010:usercopy_warn+0x81/0xa0 [ 19.856725] Code: 90 a2 41 51 4d 89 d8 48 c7 c0 89 8d 8f a2 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 f0 a1 90 a2 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 83 c4 18 c9 c3 48 c7 c6 b2 8a 92 a2 49 89 f1 49 89 f3 eb [ 19.856746] RSP: 0018:bb3002583b08 EFLAGS: 00010286 [ 19.856747] RAX: RBX: 935d57f65cb0 RCX: 0006 [ 19.856748] RDX: 0007 RSI: 0096 RDI: 935d6f3964b0 [ 19.856749] RBP: bb3002583b20 R08: 0001 R09: 0478 [ 19.856750] R10: 0001 R11: R12: 0003 [ 19.856750] R13: 0001 R14: 935d57f65cb3 R15: 935d57f65cf8 [ 19.856752] FS: 7fe7a307da80() GS:935d6f38() knlGS: [ 19.856752] CS: 0010 DS: ES: CR0: 80050033 [ 19.856753] CR2: 7fe79f700110 CR3: 000414d06006 CR4: 000606e0 [ 19.856754] Call Trace: [ 19.856759] __check_heap_object+0xc2/0x110 [ 19.856761] __check_object_size+0x14c/0x178 [ 19.856895] os_memcpy_to_user+0x26/0x50 [nvidia] [ 19.857044] _nv009384rm+0xbf/0xe0 [nvidia] [ 19.857045] WARNING: kernel stack frame pointer at 05649f90 in Xorg:1742 has bad value 892d8e62 [ 19.857047] unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0 [ 19.857048] ec2c30aa: bb3002583b30 (0xbb3002583b30) [ 19.857049] cadd4750: a1a69a82 (__check_heap_object+0xc2/0x110) [ 19.857050] e8e36824: bb3002583b60 (0xbb3002583b60) [ 19.857051] 3592af1f: a1a91abc (__check_object_size+0x14c/0x178) [ 19.857052] 86c7dd25: 0003 (0x3) [ 19.857053] 8c88b4e5: 935d57f65cb0 (0x935d57f65cb0) [ 19.857053] 92bc319f: 55de94b2491e (0x55de94b2491e) [ 19.857054] 59b96776: ... [ 19.857055] 2c0f28f3: bb3002583b88 (0xbb3002583b88) [ 19.857141] c046880e: c078b5b6 (os_memcpy_to_user+0x26/0x50 [nvidia]) [ 19.857142] 870f32d1: 0003 (0x3) [ 19.857142] 077eb892: 55de94b2491e (0x55de94b2491e) [ 19.857143] 47ac0c10: 935d57f65cb0 (0x935d57f65cb0) [ 19.857144] 05649f90: 935d57f65ca8 (0x935d57f65ca8) [ 19.857290] d28c291e: c0d5b87f (_nv009384rm+0xbf/0xe0 [nvidia]) [ 19.857291] 0bf99a12: 935d57f65c88 (0x935d57f65c88) [ 19.857291] cc40361c: ... [ 19.857292] 260150fd: 935d549d3f08 (0x935d549d3f08) [ 19.857293] 3bbf4a77: 935d57f65db8 (0x935d57f65db8) [ 19.857293] 76aa34db: 7ffd341175d0 (0x7ffd341175d0) [ 19.857421] 28327c08: c0955259
[Desktop-packages] [Bug 1790100] Re: unable to write ~ and ^ chars in the terminal
Please understand: It's not that we (vte and gnome-terminal developers) don't want to hear about it. We've heard about it and we are pretty certain that this is a bug somewhere elsewhere. Vte's and gnome- terminal's source code has absolutely no sign of treating ^ or any other similar simple character specially. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1790100 Title: unable to write ~ and ^ chars in the terminal Status in vte2.91 package in Ubuntu: Fix Released Bug description: Hello, I am using Ubuntu 18.10 and since the last update, I am unable to write ~ and ^ chars in the terminal, in both gnome-terminal and Geany (both using libvte2.91). I don't have this issue with other applications (terminator, xterm, Firefox, Gedit, etc.). But note that now, when I type ^ for the first time in Gedit for example, I see this char but underlined. If I type it a second type (or press space), it is transformed in ^ without line under it. This is a new behaviour that can cause this bug in libvte. Please tell me if I need to join other info! Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libvte-2.91-0 0.52.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 31 11:17:43 2018 InstallationDate: Installed on 2015-08-10 (1116 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: vte2.91 UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1790100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
