[Desktop-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
I forgot to tell you: this issue is only pressent on ubuntu, audio on Windows works fine -- 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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN 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/1818802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819132] Re: DNS is broken after reboot or suspend
** Package changed: network-manager (Ubuntu) => systemd (Ubuntu) -- 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/1819132 Title: DNS is broken after reboot or suspend Status in systemd package in Ubuntu: New Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
With the last update today: Dropbox, Radiotray-NG and gEncFS Manager indicators came back working in the top panel. -- 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 1805025] Re: gnome-control-center power - 'Turn off Wi-Fi to save power' label is confusing
** Changed in: gnome-control-center Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1805025 Title: gnome-control-center power - 'Turn off Wi-Fi to save power' label is confusing Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Bug description: The 'Turn off Wi-Fi to save power' setting defaults to ON. Toggling 'Turn off Wi-Fi to save power' to OFF causes the wifi device to be soft blocked. BEFORE$ sudo rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no AFTER$ sudo rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: Power saving for wifi will be disabled. Actual behavior: Wifi is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1805025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819183] [NEW] FFe: Update pygobject to 3.32
Public bug reported: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.31.4-1 is in Debian experimental ready to be synced over once this FFe is approved. 3.32.0 is expected next week. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.31.4-1 is in Debian experimental ready to be synced over once this FFe is approved. 3.32.0 is expected next week. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
1:3.26.4-0~ubuntu18.04.4 fixed this bug for me. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: In Progress Status in nautilus source package in Bionic: Fix Committed Status in nautilus source package in Cosmic: Fix Committed Bug description: * Impact The text search feature, which is depending on tracker, is not working even when the service is installed * Test case - install tracker and restart your session - echo 'Nautilus is great' > ~/txt - open nautilus and type 'great' in the search entry -> the file should be listed * Regression potential That's changing the search provider logic, make sure that searching for file without tracker still works (that only look at filenames) and there is no extra logging/cpu usage --- Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732991] Re: I can't use mouse buttons to navigate Ubuntu Desktop Guide
The bug is still present in Bionic. ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1732991 Title: I can't use mouse buttons to navigate Ubuntu Desktop Guide Status in yelp package in Ubuntu: New Bug description: Extra mouse buttons work elsewhere in the system, e.g., in Nautilus and Firefox, but not in the Desktop Guide. I'd expect to be able to browse forwards and backwards with the extra mouse buttons. I suspect that this is a bug. Tested in Ubuntu 17.10, Wayland session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1732991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** Tags added: fixed-3.32.1 fixed-upstream -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811402] Re: Can not switch to virtual console (TTY)
Does not work with 340.107-0ubuntu0.18.04.2 either. HW: Geforce 9400M. I do not know, if related, but with different hardware and 340.107-0ubuntu0.16.04.2 in Xenial I can switch to TTY: On a laptop with a monitor connected to HDMI, the TTY is seen in integrated display only even if the X session is seen on the HDMI monitor. On a (Xenial) PC with a VGA monitor connected TTY is shown in the monitor. -- 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/1811402 Title: Can not switch to virtual console (TTY) Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker is not used). This happens with nvidia-340 driver (I am using version 340.107-0ubuntu0.18.04.1 from bionic-updates), but not with nouveau driver. This bug also breaks light-locker, suspend to RAM, switching user and maybe something else. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 11 16:17:15 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (735 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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/1811402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
disabling 10bpc solved the problem, thanks -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819080] Re: The extension can't be disabled
Thank you for your bug report. That's not a bug though but the way the ubuntu session is set up, you can install/log into the gnome stock session if you prefer that experience ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1819080 Title: The extension can't be disabled Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: On a clean Disco install by default we get the desktop icons, but the extension appears as disabled in gnome-tweaks: the setting is not consistent with the actual observed behavior. It seems that the extension "switch" in gnome-tweaks has no effect: even when turned off changing the extension settings (by clicking on the gear icon) does change which icons are shown on the desktop. This also means that the extension can't be fully disabled, removing all the desktop icons. Note that turning off the "personal folder" and "trash" icons is not enough: the contents of ~/Desktop are still shown. Uninstalling gnome-shell-extension-desktop-icons is not an option, as it is a dependency of ubuntu-desktop-minimal. This is observed on Disco with gnome-shell-extension-desktop-icons 19.01.1-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1819080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819194] [NEW] TTY not visible
*** This bug is a duplicate of bug 1811402 *** https://bugs.launchpad.net/bugs/1811402 Public bug reported: NA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-340 340.107-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 8 19:29:33 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (792 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** This bug has been marked a duplicate of bug 1811402 Can not switch to virtual console (TTY) -- 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/1819194 Title: TTY not visible Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-340 340.107-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 8 19:29:33 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-05 (792 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1819194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 993292] Re: pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs them all
** Changed in: poppler Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/993292 Title: pdftotext -htmlmeta does output incomplete metadata, pdfinfo outputs them all Status in Poppler: New Status in poppler package in Ubuntu: New Bug description: pdftotext -htmlmeta does miss metadata from PDF catalog. pdfinfo does output all values known: e.g. a pdfinfo output: Title: Titel Author: Word Creator:WordToPDF 2.4 build 127 Producer: AFPL Ghostscript 8.54 CreationDate: Fri Jul 2 09:14:02 2007 ModDate:Fri Jul 2 09:14:02 2007 Tagged: no Pages: 6 Encrypted: no Page size: 595 x 842 pts (A4) File size: 104664 bytes Optimized: no PDF version:1.3 in contrast the meta section of the pdftotext -htmlmeta output: Titel Does not match and miss some meta data. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: poppler-utils 0.16.7-2ubuntu2 Uname: Linux 3.3.3-030303-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed May 2 15:44:06 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64+mac (20110427.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: poppler UpgradeStatus: Upgraded to oneiric on 2012-02-16 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/993292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Fixed in 340.107-0ubuntu0.16.04.2 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927065] Re: Firefox 10.0 crashes when visiting a website with a java applet
** Changed in: icedtea-web (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/927065
Title:
Firefox 10.0 crashes when visiting a website with a java applet
Status in Iced Tea:
Fix Released
Status in firefox package in Ubuntu:
Invalid
Status in icedtea-web package in Ubuntu:
Confirmed
Status in icedtea-web package in Debian:
Fix Released
Bug description:
Visiting https://www.netbank.nordea.dk/netbank/index.jsp will make it
crash
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: firefox 10.0+build1-0ubuntu0.11.10.1
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 6541 F pulseaudio
BuildID: 20120129141257
CRDA: Error: [Errno 2] Ingen sådan fil eller filkatalog
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb32 irq 48'
Mixer name : 'Analog Devices AD1984A'
Components : 'HDA:11d4194a,103c30ec,00100400
HDA:11c11040,103c1378,00100200'
Controls : 18
Simple ctrls : 11
Channel: release
Date: Sun Feb 5 11:09:13 2012
DefaultProfileIncompatibleExtensions:
JavaScript Debugger - ID={f13b157f-b174-47e7-a34d-4815ddfdfeb8},
Version=0.9.88.2, minVersion=1.9.1, maxVersion=2.0.*, Location=app-profile,
Type=extension, Active=Yes
Elasticfox - ID={2204c510-88f3-11db-b606-0800200c9a66}, Version=1.7.000116,
minVersion=2.0, maxVersion=4.0, Location=app-profile, Type=extension, Active=Yes
Screengrab - ID={02450954-cdd9-410f-b1da-db804e18c671}, Version=0.96.3,
minVersion=3.0, maxVersion=6.*, Location=app-profile, Type=extension, Active=Yes
EcryptfsInUse: Yes
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
172.16.253.0/24 dev vmnet8 proto kernel scope link src 172.16.253.1
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.148
metric 2
192.168.155.0/24 dev vmnet1 proto kernel scope link src 192.168.155.1
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=da_DK.UTF-8
SHELL=/usr/bin/tcsh
Profile1IncompatibleExtensions: Firebug - ID=fire...@software.joehewitt.com,
Version=1.7.3, minVersion=1.9.2, maxVersion=2.2.0.*, Location=app-profile,
Type=extension, Active=Yes
Profiles:
Profile0 (Default) - LastVersion=10.0/20120129141257 (Running)
Profile1 - LastVersion=5.0/20110622232440 (Out of date)
Profile2 - LastVersion=10.0/20120129141257
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PAD Ver. F.13
dmi.board.name: 30EC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.25
dmi.chassis.asset.tag: CNU01143H6
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8730w
dmi.product.version: F.13
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/icedtea/+bug/927065/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819184] [NEW] LO 6.2.1.1 Popup on Files, Edits, etc out of position
Public bug reported: When one clicks on the Files, Edit, View, Insert, etc the popup window is positions to the top of the desktop. In addition the spacing between the popup items is much larger than 6.1 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Mar 8 08:57:51 2019 InstallationDate: Installed on 2019-03-01 (6 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190131) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Screenshot from 2019-03-08 08-56-34.png" https://bugs.launchpad.net/bugs/1819184/+attachment/5244753/+files/Screenshot%20from%202019-03-08%2008-56-34.png -- 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/1819184 Title: LO 6.2.1.1 Popup on Files, Edits, etc out of position Status in libreoffice package in Ubuntu: New Bug description: When one clicks on the Files, Edit, View, Insert, etc the popup window is positions to the top of the desktop. In addition the spacing between the popup items is much larger than 6.1 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Mar 8 08:57:51 2019 InstallationDate: Installed on 2019-03-01 (6 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190131) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1819184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819189] [NEW] gtk_label_set_attributes core dump
Public bug reported:
Program terminated with signal SIGSEGV, Segmentation fault.
in gtk_label_set_attributes () from libgtk-3.so.0
gtk/gtklabel.c
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv = label->priv;
g_return_if_fail (GTK_IS_LABEL (label));
to
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv;
g_return_if_fail (GTK_IS_LABEL (label));
priv = label->priv;
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1819189
Title:
gtk_label_set_attributes core dump
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
Program terminated with signal SIGSEGV, Segmentation fault.
in gtk_label_set_attributes () from libgtk-3.so.0
gtk/gtklabel.c
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv = label->priv;
g_return_if_fail (GTK_IS_LABEL (label));
to
void
gtk_label_set_attributes (GtkLabel *label,
PangoAttrList*attrs)
{
GtkLabelPrivate *priv;
g_return_if_fail (GTK_IS_LABEL (label));
priv = label->priv;
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1819189/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819193] [NEW] Document search does not work
Public bug reported:
1. Description: Ubuntu 18.04.2 LTS
2. 3.28.3-0ubuntu0.18.04.4
3. I expect to be able to search document by content from the gnome shell
("Type to search..."). The option is enabled from settings.
4. Nothing happens. No documents are retrieved.
I get the following error message in logs repeatedly:
"Wrong number of result metas returned by search provider
org.gnome.Documents.desktop: expected 5 but got 0"
gnome-documents also gives this:
"JS ERROR: GLib.Error g-invoke-error-quark: Could not locate
gd_filename_strip_extension: (null)"
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic gnome-documents gnome-shell
** Tags added: gnome-documents
--
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/1819193
Title:
Document search does not work
Status in gnome-shell package in Ubuntu:
New
Bug description:
1. Description: Ubuntu 18.04.2 LTS
2. 3.28.3-0ubuntu0.18.04.4
3. I expect to be able to search document by content from the gnome shell
("Type to search..."). The option is enabled from settings.
4. Nothing happens. No documents are retrieved.
I get the following error message in logs repeatedly:
"Wrong number of result metas returned by search provider
org.gnome.Documents.desktop: expected 5 but got 0"
gnome-documents also gives this:
"JS ERROR: GLib.Error g-invoke-error-quark: Could not locate
gd_filename_strip_extension: (null)"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819193/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
** Tags added: rls-dd-incoming -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794033]
The CI Bug Log issue associated to this bug has been archived. New failures matching the above filters will not be associated to this bug anymore. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794033]
(In reply to Mark Janes from comment #15) > Mesa CI reproduce these test failures immediately: > > https://mesa-ci.01.org/mesa_master/builds/15252/group/ > 63a9f0ea7bb98050796b649e85481845 > > Builds have fairly recent kernels: > > Linux otc-gfxtest-sklgt2-01 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 > (2018-12-22) x86_64 GNU/Linux Thanks for the info! I'll treat this as a mesa bug and since we are using your blacklist, we should be safe to just ignore it from our side. I'll close our kernel issue. Thanks to everyone involved! -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Confirmed Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
1:3.26.4-0~ubuntu18.04.4 fixed this bug for me too! -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: In Progress Status in nautilus source package in Bionic: Fix Committed Status in nautilus source package in Cosmic: Fix Committed Bug description: * Impact The text search feature, which is depending on tracker, is not working even when the service is installed * Test case - install tracker and restart your session - echo 'Nautilus is great' > ~/txt - open nautilus and type 'great' in the search entry -> the file should be listed * Regression potential That's changing the search provider logic, make sure that searching for file without tracker still works (that only look at filenames) and there is no extra logging/cpu usage --- Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819137] Re: switching workspaces shotcut stops working
please run apport-collect 1819137 to attach more details about your installation ** Also affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg-server (Ubuntu) ** Changed in: budgie-desktop (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/1819137 Title: switching workspaces shotcut stops working Status in budgie-desktop package in Ubuntu: Incomplete Bug description: After a while of using Ubuntu Budgie, the keyboard keycombination for switching workspaces stops working. Iam not sure, what is triggering this or what package is causing this behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1819137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817285] Re: SRU xdg-desktop-portal 1.0.3
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1817285 Title: SRU xdg-desktop-portal 1.0.3 Status in xdg-desktop-portal package in Ubuntu: Invalid Status in xdg-desktop-portal source package in Xenial: Fix Committed Status in xdg-desktop-portal source package in Bionic: Fix Committed Bug description: [Impact] * To improve the snap experience on the desktop we have been working with xdg-desktop-portal upstream to enable snap support. Portals will greatly improve the snap experience. Full snap support landed in xdg-desktop-portal 1.0. We're SRU'ing 1.0.3 as it includes bug fixes. * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, so these will be promoted to main as well. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 [Test Case] * This can be tested by installing the portal-test snap from the edge channel and xdg-desktop-portal-gtk also from proposed. Verify the file selection lets you select a file and open local opens test.txt in a text editor of your choice. [Regression Potential] * No regression potential. This package was not seeded by default. It could only have been used by flatpak, however, the version in bionic had limited functionality. The package was never available in xenial. [Other Info] * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817287] Re: SRU xdg-desktop-portal-gtk 1.0.2
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1817287 Title: SRU xdg-desktop-portal-gtk 1.0.2 Status in xdg-desktop-portal-gtk package in Ubuntu: Invalid Status in xdg-desktop-portal-gtk source package in Xenial: Fix Committed Status in xdg-desktop-portal-gtk source package in Bionic: Fix Committed Bug description: [Impact] * To improve the snap experience on the desktop we have been working with xdg-desktop-portal-gtk upstream to enable snap support. Portals will greatly improve the snap experience. Full snap support landed in xdg-desktop-portal-gtk 1.0. We're SRU'ing 1.0.2 as it includes bug fixes. * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and xenial, so these will be promoted to main as well. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 Also requires xdg-desktop-portal https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285 [Test Case] * This can be tested by installing the portal-test snap from the edge channel and xdg-desktop-portal also from proposed. Verify the file selection lets you select a file and open local opens test.txt in a text editor of your choice. [Regression Potential] * No regression potential. This package was not seeded by default. It could only have been used by flatpak, however the version in bionic had limited functionality. The package was never available in xenial. [Other Info] * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817285] Re: SRU xdg-desktop-portal 1.0.3
FWIW this also passes from a flatpak point of view on bionic as noted in xdg-desktop-portal-gtk here https://bugs.launchpad.net/ubuntu/+source /xdg-desktop-portal-gtk/+bug/1817287/comments/2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1817285 Title: SRU xdg-desktop-portal 1.0.3 Status in xdg-desktop-portal package in Ubuntu: Invalid Status in xdg-desktop-portal source package in Xenial: Fix Committed Status in xdg-desktop-portal source package in Bionic: Fix Committed Bug description: [Impact] * To improve the snap experience on the desktop we have been working with xdg-desktop-portal upstream to enable snap support. Portals will greatly improve the snap experience. Full snap support landed in xdg-desktop-portal 1.0. We're SRU'ing 1.0.3 as it includes bug fixes. * There is now an approved MIR for xdg-desktop-portal for bionic and xenial, so these will be promoted to main as well. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 [Test Case] * This can be tested by installing the portal-test snap from the edge channel and xdg-desktop-portal-gtk also from proposed. Verify the file selection lets you select a file and open local opens test.txt in a text editor of your choice. [Regression Potential] * No regression potential. This package was not seeded by default. It could only have been used by flatpak, however, the version in bionic had limited functionality. The package was never available in xenial. [Other Info] * xdg-desktop-portal is in main and seeded by ubuntu-desktop in cosmic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819077] Re: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible point
Works fine with 340.107-0ubuntu0.16.04.2 -- 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/1819077 Title: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible- pointer-types]) Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Bug description: SRU Request: [Impact] nvidia-340 (from xenial-proposed) breaks compatibility with linux-generic-hwe-16.04. [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update simply re-enables a patch that had been disabled in 340.107-0ubuntu0.16.04.1 _ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.15.0-46-generic Date: Fri Mar 8 01:23:53 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed DuplicateSignature: dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1202 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.107-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32
>From an pygobject upstream POV this cycle hasn't seen any high risk changes, so +1 from me in case that helps :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.31.4-1 is in Debian experimental ready to be synced over once this FFe is approved. 3.32.0 is expected next week. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817287] Re: SRU xdg-desktop-portal-gtk 1.0.2
FWIW from a flatpak point of view this passes the relevant parts of the test plan on bionic and some exploratory testing :-) I'll continue checking that nothing has regressed. I tested this with the following versions $ apt policy flatpak xdg-desktop-portal xdg-desktop-portal-gtk flatpak: Installed: 1.0.7-0ubuntu0.18.04.1 Candidate: 1.0.7-0ubuntu0.18.04.1 Version table: *** 1.0.7-0ubuntu0.18.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 100 /var/lib/dpkg/status 0.11.3-3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages xdg-desktop-portal: Installed: 1.0.3-0ubuntu0.1 Candidate: 1.0.3-0ubuntu0.1 Version table: *** 1.0.3-0ubuntu0.1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.11-1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages xdg-desktop-portal-gtk: Installed: 1.0.2-0ubuntu1.1 Candidate: 1.0.2-0ubuntu1.1 Version table: *** 1.0.2-0ubuntu1.1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.11-1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1817287 Title: SRU xdg-desktop-portal-gtk 1.0.2 Status in xdg-desktop-portal-gtk package in Ubuntu: Invalid Status in xdg-desktop-portal-gtk source package in Xenial: Fix Committed Status in xdg-desktop-portal-gtk source package in Bionic: Fix Committed Bug description: [Impact] * To improve the snap experience on the desktop we have been working with xdg-desktop-portal-gtk upstream to enable snap support. Portals will greatly improve the snap experience. Full snap support landed in xdg-desktop-portal-gtk 1.0. We're SRU'ing 1.0.2 as it includes bug fixes. * There is now an approved MIR for xdg-desktop-portal-gtk for bionic and xenial, so these will be promoted to main as well. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 Also requires xdg-desktop-portal https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1817285 [Test Case] * This can be tested by installing the portal-test snap from the edge channel and xdg-desktop-portal also from proposed. Verify the file selection lets you select a file and open local opens test.txt in a text editor of your choice. [Regression Potential] * No regression potential. This package was not seeded by default. It could only have been used by flatpak, however the version in bionic had limited functionality. The package was never available in xenial. [Other Info] * xdg-desktop-portal-gtk is in main and seeded by ubuntu-desktop in cosmic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1817287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 I'm afraid I have to add to the pile of users reporting issues here. Kernel 4.20.14 with 418.43 drivers. Ubuntu 18.04.2 LTS, on an X1 Extreme. Using both GDM3 and lightdm, "prime-switch intel" doesn't seem to power off the nvidia GPU. power seems to go between 25-35W on battery. Using powertop to set the Nvidia GPU to `Good` doesn't seem to help (100% usage in Device stats). Attached are gpu-manager.log and gpu-manager-switch.log (while in prime- select intel mode). I'm not using bbswitch. I've rebooted a few times while in intel mode to see if that would take. No die. Also including output of apt-list --installed | grep nvidia: libnvidia-cfg1-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] libnvidia-common-418/bionic,bionic,now 418.43-0ubuntu0~18.04.1 all [installed,automatic] libnvidia-compute-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] libnvidia-decode-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] libnvidia-encode-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] libnvidia-fbc1-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] libnvidia-gl-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] libnvidia-ifr1-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] nvidia-compute-utils-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] nvidia-dkms-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] nvidia-driver-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed] nvidia-kernel-common-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] nvidia-kernel-source-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] nvidia-prime/bionic-updates,bionic-updates,now 0.8.8.2 all [installed] nvidia-settings/bionic,now 418.43-0ubuntu0~gpu18.04.1 amd64 [installed,automatic] nvidia-utils-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] xserver-xorg-video-nvidia-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic] I'm fairly new to Linux, but if there's any additional information I can provide, I'd be glad to assist. ** Attachment added: "gpu-manager logs." https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5244873/+files/gpu-manager-logs.tar.gz -- 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
[Desktop-packages] [Bug 1818829] Re: Disconnected monitors act as present
** Changed in: xorg-server (Ubuntu) Status: Opinion => 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: New Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1818829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809836] Re: system keeps freezing frequently. Mouse moves but nothing else works
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809836 Title: system keeps freezing frequently. Mouse moves but nothing else works Status in gnome-shell package in Ubuntu: Expired Bug description: System freezes without a noticeable pattern Mouse moves but nothing else works ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 23:05:32 2018 InstallationDate: Installed on 2015-11-27 (1125 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to bionic on 2018-12-25 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810362] Re: System completely hangs, high disk I/O when running a VirtualBox VM alongside Firefox with a few tabs open
[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: virtualbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1810362 Title: System completely hangs, high disk I/O when running a VirtualBox VM alongside Firefox with a few tabs open Status in gnome-shell package in Ubuntu: Expired Status in virtualbox package in Ubuntu: Expired Bug description: Experienced complete system lockup and hang on two different machines when trying to boot a VirtualBox VM running Fedora 29 live (no virtual disk) when Firefox is open with a few (~5-10) inactive tabs. System 1: 4GB RAM host 1536MB guest, no virtual disk swapfile System 2: 6 GB RAM host 1792MB guest, no virtual disk separate swap partition (4GB) - Load Fedora in guest from live ISO On boot of the guest (after boot menu), the entire system locks up for easily 30 minutes or more, with constant host disk activity. GNOME shell becomes completely unresponsive, can move the cursor some but interacting doesn't work and the UI shell doesn't respond to mouse hover. Requires closing the lid to attempt force sleep and resume to be able to regain access to the applications and GNOME shell. After resuming, VM seems to be usable. Seems like the system is running low on memory but not handling/terminating applications, and thrashing, and/or there are bad memory leaks happening when booting the VM. Expected behaviour: Runs normally or fails out of memory without locking up the entire system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox 5.2.18-dfsg-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 22:16:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-13 (203 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: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1810362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809940] Re: ASPEED AST2400 graphics failure on normal start but work on recovery start
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1809940 Title: ASPEED AST2400 graphics failure on normal start but work on recovery start Status in mutter package in Ubuntu: Expired Bug description: I have an ASUS P10S-I server motherboard with integrated ASPEED AST2400 VGA chipset. With earlier Ubuntu version (maybe on Ubuntu 16.04.3 ?) it worked well. Once when I updated (but before the actual version) it went wrong. To be truth it not really the xresver...-ast's problem because this earlier not installed automatically and the poroblem was the same. When i found it on synaptic as uninstalled i hoped that this will solve the problem and i had installed it but it not worked at all... The issue: When I boot normally the login window load slowly and keybord and mouse very slow too but work. I can login. But after i login the screen not show the desktop it show diagonal stripes. (see the attachment) This stripes made from original screen but unrecognisable the things. But the items work if you can click the right places. (for example i can click on the main switch button if i have luck and Crl+Alt+Del log out me.) After i log out the login screen corrupted on the same diagonal stripe way. But also work I can re login. How it work: If I start the recovery mode and on the recovery window choose continue start normally (and nothing else needed) it works without problem. Evrithing is fine. I tried to install ASPEED driver but on the Softwares and Updates menu Another driver don't found it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Engedély megtagadva: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 28 00:28:01 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9] InstallationDate: Installed on 2017-11-20 (402 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a: Creative Labs Optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. P10S-I Series ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=1e49958f-dcf2-402d-b5ec-4e379ec72739 ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P10S-I Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr4401:bd03/05/2018:svnASUSTeKCOMPUTERINC.:pnP10S-ISeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP10S-ISeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: Server dmi.product.name: P10S-I Series dmi.product.version: System Version 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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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: Fri Dec 28 00:17:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD,
[Desktop-packages] [Bug 1810808] Re: blocchi continui pagine
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1810808 Title: blocchi continui pagine Status in xorg-server package in Ubuntu: Expired Bug description: aprendo le pagine il computer va in blocco e non risponde piu ai comandi ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Mon Jan 7 17:27:27 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated Graphics Controller [144d:c059] Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated Graphics Controller [144d:c059] InstallationDate: Installed on 2016-10-10 (819 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. R519/R719 ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=3b9ac247-cddd-4beb-ae47-cd4dfa76b6f1 ro nopat vesafb.invalid=1 drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 09CI.M060.20100401.JIP dmi.board.name: R519/R719 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr09CI.M060.20100401.JIP:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR519/R719:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR519/R719:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R519/R719 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~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 1:2.10.5-1ubuntu1 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 Oct 4 11:40:09 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1810808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-vmware (Ubuntu) Status: New => Confirmed -- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-vmware package in Ubuntu: Confirmed Bug description: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0 I should add that this bug seems specific to Kubuntu, and (I guess) associated with running under Virtualbox. I have another Ubuntu 18.04 (i.e. not _K_ubuntu) running on bare metal and it is not having any problems. Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH 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 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1815693/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
Thanks. I did install the .debs and now the fix is working for me. I will note that after installing the .debs and rebooting my machine, the GUI would not come up. This was resolved by reinstalling the desktop from the CLI. In any event, the fix is working and I appreciate the help. If you need any information from me, please let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) [Test Case] 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. [Regression Potential] Low. The affected code is only used in rendering shell panels and popup menus at the moment. So any potential regression (like the original bug) would be noticed in those places only, and not beyond. Furthermore, the upstream fix has been tested regularly for 8 months already. [Other Info] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 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 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-vmware package in Ubuntu: Confirmed Bug description: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0 I should add that this bug seems specific to Kubuntu, and (I guess) associated with running under Virtualbox. I have another Ubuntu 18.04 (i.e. not _K_ubuntu) running on bare metal and it is not having any problems. Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH 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 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1815693/+subscriptions -- Mailing list: https://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 1818944] Re: unable to remove or add apps
Thank you Daniel. I applied commands. Program manager is now working. Thank you very much. Perry On Thu, Mar 7, 2019 at 7:50 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Please open a terminal and try this: > > sudo apt update > sudo apt -f install > sudo apt full-upgrade > > and then run again: > > sudo apt update > sudo apt full-upgrade > > and tell us if you get any errors from that final command. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1818944 > > Title: > unable to remove or add apps > > Status in gnome-software package in Ubuntu: > New > > Bug description: > unable to remove or add apps. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 > Uname: Linux 4.15.0-45-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > CompositorRunning: None > Date: Wed Mar 6 19:04:29 2019 > DistUpgraded: 2018-09-05 18:27:31,982 DEBUG icon theme changed, > re-reading > DistroCodename: bionic > DistroVariant: ubuntu > DpkgLog: > > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) > (prog-if 00 [VGA controller]) > Subsystem: eVga.com. Corp. GT218 [GeForce 8400 GS Rev. 3] [3842:1302] > InstallationDate: Installed on 2017-08-04 (579 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: To be filled by O.E.M. To be filled by O.E.M. > ProcEnviron: >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic > root=UUID=50cfe61f-c8b2-425d-8e49-ebb4f48f5173 ro quiet splash > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2018-09-06 (182 days ago) > dmi.bios.date: 03/24/2016 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 2701 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: M5A97 LE R2.0 > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev 1.xx > 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.:bvr2701:bd03/24/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: To be filled by O.E.M. > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: To be filled by O.E.M. > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.95-1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~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 > 1:2.10.5-1ubuntu1 > 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: Wed Sep 5 16:21:29 2018 > xserver.configfile: default > xserver.errors: >Failed to load module "nvidia" (module does not exist, 0) >Failed to load module "nvidia" (module does not exist, 0) >Logitech Rechargeable Touchpad T650: Read error 19 >Logitech Rechargeable Touchpad T650: Read error 19 > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: Output DVI-I-1 > HDMI-1 VGA-1 > xserver.version: 2:1.18.4-0ubuntu0.8 > xserver.video_driver: nouveau > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1818944/+subscriptions > -- 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/1818944 Title: unable to remove or add apps Status in gnome-software package in Ubuntu: New Bug description: unable to remove or add apps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Wed Mar 6 19:04:29 2019 DistUpgraded: 2018-09-05 18:27:31,982 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too
[Desktop-packages] [Bug 1809536] Re: Empty desktop background after screen unlock - only dock with app icons and top panel, cannot see any app
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809536 Title: Empty desktop background after screen unlock - only dock with app icons and top panel, cannot see any app Status in gnome-shell package in Ubuntu: Expired Bug description: Steps to reproduce (intermittently, ~1 per 10 times): 1. Leave the computer until the screen is blank - two monitors, no multimonitor plugin 2. Move the mouse to unblank the screen 3. Drag lock screen to top + enter password Actual results - Ubuntu dock is visible (with app icons) - Top panel is visible, but with limited options (e.g. no "Sleep" button, no app indicators) - Empty desktop background - Clicking the app icon does nothing - there is some animation effect, but it looks like the application would be 'behind' the background - Clicking "Applications" menu animates but then disappear as well Partial workaround: 1. Ctrl-Alt-F1 2. Choose the same user and enter password 3. You'll come back to the "empty desktop". But in a few seconds applications appear with a few limitations: a) Top panel features are still limited (no sleep/power off buttons in menu, no app indicators) b) Ubuntu dock shows different set of apps on each 1st and 2nd monitor Might be related to one of the stack traces in journalctl -first is probably when the screen was locked, second when unclodked gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: == Stack trace for context 0x55b45f34c210 == gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #0 7ffd0163ba40 b resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f054eccc040 @ 25) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #1 7ffd0163bae0 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7f051f315790 @ 20) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #2 7ffd0163bbd0 b self-hosted:261 (7f054ecc1dc0 @ 223) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #3 7ffd0163bc90 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7f051f315700 @ 172) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #4 7ffd0163c910 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #5 55b46572a1c0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:424 (7f051f315820 @ 17) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #6 7ffd0163d880 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #7 55b46572a140 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:89 (7f051f310ee0 @ 42) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #8 7ffd0163e7f0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #9 55b46572a0b8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:456 (7f05237fbd30 @ 82) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #10 7ffd0163f760 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #11 55b46572a020 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1784 (7f051f30c160 @ 116) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #12 7ffd016406d0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #13 55b4647f2360 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1903 (7f051f30c550 @ 37) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #14 7ffd01641640 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f054ecb0b80 @ 71) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #15 55b4647f22e0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/extension.js:31 (7f05237fb4c0 @ 12) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #16 55b4647f2220 i resource:///org/gnome/shell/ui/extensionSystem.js:83 (7f054e85a040 @ 436) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #17 55b4647f21a0 i resource:///org/gnome/shell/ui/extensionSystem.js:354 (7f054e85ab80 @ 13) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #18 7ffd016427b0 b self-hosted:261 (7f054ecc1dc0 @ 223) gru 22 10:23:59 alex-notebook org.gnome.Shell.desktop[4475]: #19 55b4647f2120 i
[Desktop-packages] [Bug 1809660] Re: When starting new user session, new gdm session may spawn
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1809660 Title: When starting new user session, new gdm session may spawn Status in gdm3 package in Ubuntu: Expired Bug description: Sometimes, when user start new session, gdm session may spawn several times. Example: - System started, gdm session at tty1. - User eugene enter. Eugene session at tty2. - User vladik start new session from locked screen. Vladik session at tty4, and, unexpected, second gdm session at tty3! - After some logins/logouts with another users gdm session spawns more. Attached output of 'ps -fU gdm'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Dec 24 16:05:34 2018 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1809660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809655] Re: Items in the panel menu not aligned properly
[Expired for yaru-theme (Ubuntu) because there has been no activity for 60 days.] ** Changed in: yaru-theme (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1809655 Title: Items in the panel menu not aligned properly Status in yaru-theme package in Ubuntu: Expired Bug description: Items in the popup menu on the right hand side of the panel (panel- status-indicators-box menu) are not properly horizontally aligned. This is most visible when switching to a different font instead of the default Ubuntu font. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.6 [modified: usr/share/gnome-shell/theme/Yaru/gnome-shell.css] ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 24 13:37:41 2018 Dependencies: InstallationDate: Installed on 2018-12-01 (22 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1809655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809517] Re: OS freezes after screen turns off and I return to account
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809517 Title: OS freezes after screen turns off and I return to account Status in gnome-shell package in Ubuntu: Expired Bug description: I recently upgraded to the newest 18.10 I have disabled Ubuntu from requiring my password after the screen turns off due to inactivity but I'm still taken to the landing page as if I needed to unlock my computer. After sliding up or hitting enter the screen stays purple with the taskbar visible. I can click the application shortcuts on the taskbar but nothing happens afterwards.It doesn't happen every time, only once out of every 5 to 10 times. I'm using a Dell Inspiron 5559 64bit, graphics card is Intel HD Graphics 520 (Skylake GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806983] Re: desktop environment resumes badly when resuming from suspend mode
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1806983 Title: desktop environment resumes badly when resuming from suspend mode Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: I've a problem when resuming from suspend mode and try to unlock my pc. Expected Behavior: Interface shows correctly after resuming from suspend mode. Real Behavior: Interface shows badly after resume PC from suspend. unlock interface doesn't shows at all; instead of it, desktop (or last application) is shown. Have to re-suspend PC and re-resume, so the unlock interface is showed but application's bar shows like pc is still locked, so it doesn't show real opened applications. "resize and move windows" shortcuts doesn't work either. How to reproduce bug: Go to suspend mode, resume. mostly the bug doesn't appear, but sometimes yes. Distro Description: Ubuntu 18.10 Installed: 3.30.1-1ubuntu5 Candidate: 3.30.1-1ubuntu5 Version Table: *** 3.30.1-1ubuntu5 500 500 http://it.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 5 20:16:03 2018 InstallationDate: Installed on 2017-10-21 (410 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to cosmic on 2018-10-20 (46 days ago) mtime.conffile..etc.gdm3.Init.Default: 2017-11-21T14:48:20.846402 mtime.conffile..etc.gdm3.custom.conf: 2018-10-20T16:29:04.442996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1806983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806983] Re: desktop environment resumes badly when resuming from suspend mode
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1806983 Title: desktop environment resumes badly when resuming from suspend mode Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: I've a problem when resuming from suspend mode and try to unlock my pc. Expected Behavior: Interface shows correctly after resuming from suspend mode. Real Behavior: Interface shows badly after resume PC from suspend. unlock interface doesn't shows at all; instead of it, desktop (or last application) is shown. Have to re-suspend PC and re-resume, so the unlock interface is showed but application's bar shows like pc is still locked, so it doesn't show real opened applications. "resize and move windows" shortcuts doesn't work either. How to reproduce bug: Go to suspend mode, resume. mostly the bug doesn't appear, but sometimes yes. Distro Description: Ubuntu 18.10 Installed: 3.30.1-1ubuntu5 Candidate: 3.30.1-1ubuntu5 Version Table: *** 3.30.1-1ubuntu5 500 500 http://it.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 5 20:16:03 2018 InstallationDate: Installed on 2017-10-21 (410 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to cosmic on 2018-10-20 (46 days ago) mtime.conffile..etc.gdm3.Init.Default: 2017-11-21T14:48:20.846402 mtime.conffile..etc.gdm3.custom.conf: 2018-10-20T16:29:04.442996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1806983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809552] Re: Ubuntu sees duplicate display for each graphics card on Macbook Pro
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1809552 Title: Ubuntu sees duplicate display for each graphics card on Macbook Pro Status in xorg-server package in Ubuntu: Expired Bug description: After booting Ubuntu in BIOS mode on my machine for years, I just switched over to EFI boot. The reason for which I switched is that, on this machine, Ubuntu cannot detect the integrated GPU under BIOS boot. Ubuntu now recognizes both integrated and discrete GPU on my machine, but it also seems to think I have two monitors. Expected Behavior: Ubuntu properly recognizes that both graphics cards are in fact controlling the same display Actual Behavior: Ubuntu thinks I have two displays (each being controlled by a separate card?). If I navigate to the "Devices > Displays" section of the settings app, then Ubuntu lists two "Built in Displays," and offers options to "Join Displays," mirror them, etc. I have created a question on AskUbuntu (https://askubuntu.com/questions/1103696/ubuntu-duplicates-display- for-each-graphics-card-fresh-install) detailing this issue; it presents much of the same information in this bug report, along with several images. I have also discovered a similar thread from three years ago (https://askubuntu.com/questions/582574/my-macbook-has-two-built-in- displays) suggesting that I am not the only Macbook user to suffer from this issue. The user in said thread worked around this issue by powering off his iGPU. I would like to set up graphics switching in the future, so this is not an option for me. In any case, I have tested his "solution" and it DOES NOT work on my machine (I also don't have a /sys/kernel/debug/vgaswitcheroo folder like he apparently does) SYSTEM INFORMATION OS Version: Ubuntu (64-bit) 18.04.1 Kernel: 4.15.0-43-generic GRAPHICS CARD INFORMATION == $ lshw -c video *-display description: VGA compatible controller product: GK107M [GeForce GT 650M Mac Edition] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:45 memory:c000-c0ff memory:9000-9fff memory:a000-a1ff ioport:2000(size=128) memory:c100-c107 *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: driver=i915 latency=0 resources: irq:47 memory:c140-c17f memory:b000-bfff ioport:3000(size=64) MORE GRAPHICS CARD INFORMATION == $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] (rev a1) DISPLAY CONFIGURATION INFO (1) == NOTE: In this diagnostic, I have chosen the "Single Display" option via the System Settings app. Only one of the two "built-in displays" is actually usable, selecting the other just gives me a black screen until my changes are auto-reverted $ xrandr - q Screen 0: minimum 320 x 200, current 1440 x 900, maximum 16384 x 16384 LVDS-1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1440x900 59.90*+ 1152x864 59.97 1024x768 59.95 800x600 59.96 640x480 59.94 720x400 59.97 640x400 59.96 640x350 59.84 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) LVDS-1-2 connected (normal left inverted right x axis y axis) 1440x900 59.90 + 59.89 1400x900 59.9659.88 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.96
[Desktop-packages] [Bug 1810601] Re: Graphics trouble
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1810601 Title: Graphics trouble Status in xorg-server package in Ubuntu: Expired Bug description: Can't seem to get system to use nvidia driver instead of Nouveau ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-lowlatency 4.15.18 Uname: Linux 4.15.0-43-lowlatency 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.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 5 16:03:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102] NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF119 [NVS 310] [10de:1154] InstallationDate: Installed on 2018-08-14 (143 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-lowlatency root=UUID=89dc7f0c-2342-4866-bf1f-7d5c9635d42c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: Z77 Extreme4-M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd03/02/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1810601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810362] Re: System completely hangs, high disk I/O when running a VirtualBox VM alongside Firefox with a few tabs open
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1810362 Title: System completely hangs, high disk I/O when running a VirtualBox VM alongside Firefox with a few tabs open Status in gnome-shell package in Ubuntu: Expired Status in virtualbox package in Ubuntu: Expired Bug description: Experienced complete system lockup and hang on two different machines when trying to boot a VirtualBox VM running Fedora 29 live (no virtual disk) when Firefox is open with a few (~5-10) inactive tabs. System 1: 4GB RAM host 1536MB guest, no virtual disk swapfile System 2: 6 GB RAM host 1792MB guest, no virtual disk separate swap partition (4GB) - Load Fedora in guest from live ISO On boot of the guest (after boot menu), the entire system locks up for easily 30 minutes or more, with constant host disk activity. GNOME shell becomes completely unresponsive, can move the cursor some but interacting doesn't work and the UI shell doesn't respond to mouse hover. Requires closing the lid to attempt force sleep and resume to be able to regain access to the applications and GNOME shell. After resuming, VM seems to be usable. Seems like the system is running low on memory but not handling/terminating applications, and thrashing, and/or there are bad memory leaks happening when booting the VM. Expected behaviour: Runs normally or fails out of memory without locking up the entire system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox 5.2.18-dfsg-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 22:16:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-13 (203 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: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1810362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819127] Re: /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_cmpnum:st_image_content_get_preferred_size
*** This bug is a duplicate of bug 1819126 *** https://bugs.launchpad.net/bugs/1819126 ** This bug has been marked a duplicate of private bug 1819126 -- 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/1819127 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_cmpnum:st_image_content_get_preferred_size Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.31.92-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/40bb6815b23393e7dfa95f5895de4b0603ac431b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819127] [NEW] /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_cmpnum:st_image_content_get_preferred_size
*** This bug is a duplicate of bug 1819126 *** https://bugs.launchpad.net/bugs/1819126 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.31.92-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/40bb6815b23393e7dfa95f5895de4b0603ac431b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: disco -- 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/1819127 Title: /usr/bin/gnome- shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_cmpnum:st_image_content_get_preferred_size Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.31.92-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/40bb6815b23393e7dfa95f5895de4b0603ac431b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718839] Re: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .f
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Triaged ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Triaged => Invalid -- 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/1718839 Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror =incompatible-pointer-types] .fault = _fault,) Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Bug description: After installing new drivers when I restart, it shows crash report. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: nvidia-340 340.104-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 4.13.0-11-generic Date: Thu Sep 21 15:08:42 2017 DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu1:/var/lib/dkms/nvidia-340/340.104/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2017-04-03 (171 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageVersion: 340.104-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~rc4 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1718839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819128] [NEW] Can't open exFAT-USB-Stick
Public bug reported: I've got an exFAT-USB-Stick. If I'm plugging the stick it seems to be mounted (the mounted symbol appears in nautlius). But I'm not able to open the stick to open files or for writing new files to the stick. Just if I'm formatting the stick with GNOME Disks and mounting it directly after formatting about GNOME Disks I can open the stick. After unmounting the same problem appears. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 10:00:28 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'206' b'org.gnome.nautilus.window-state' b'geometry' b"'856x481+26+23'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-11-30 (97 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- 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/1819128 Title: Can't open exFAT-USB-Stick Status in nautilus package in Ubuntu: New Bug description: I've got an exFAT-USB-Stick. If I'm plugging the stick it seems to be mounted (the mounted symbol appears in nautlius). But I'm not able to open the stick to open files or for writing new files to the stick. Just if I'm formatting the stick with GNOME Disks and mounting it directly after formatting about GNOME Disks I can open the stick. After unmounting the same problem appears. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 10:00:28 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'206' b'org.gnome.nautilus.window-state' b'geometry' b"'856x481+26+23'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-11-30 (97 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1819128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819129] [NEW] No CPU record on Virtualbox
Public bug reported:
On a virtualbox guest ubuntu-report doesn't report CPU information.
u@pc:~$ ubuntu-report show
{
"Version": "19.04",
"OEM": {
"Vendor": "innotek GmbH",
"Product": "VirtualBox"
},
"BIOS": {
"Vendor": "innotek GmbH",
"Version": "VirtualBox"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "15ad",
"Model": "0405"
}
],
"RAM": 2,
"Disks": [
21.5
],
"Partitions": [
20.5
],
"Screens": [
{
"Size": "0mmx0mm",
"Resolution": "800x600",
"Frequency": "60.00"
}
],
"Autologin": true,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu",
"Type": "x11"
},
"Language": "en_US",
"Timezone": "America/New_York",
"Install": {
"Media": "Ubuntu 19.04 \"Disco Dingo\" - Alpha amd64 (20190305.1)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "use_device",
"DownloadUpdates": true,
"Language": "en",
"Minimal": false,
"RestrictedAddons": false,
"Stages": {
"0": "language",
"2": "language",
"8": "console_setup",
"16": "console_setup",
"20": "prepare",
"24": "partman",
"26": "start_install",
"86": "timezone",
"90": "usersetup",
"97": "user_done",
"582": "done"
}
}
}
@pc:~$ lscpu
Architecture:x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s):1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 10
Model name: AMD Phenom(tm) II X6 1055T Processor
Stepping:0
CPU MHz: 2812.342
BogoMIPS:5624.68
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache:512K
L3 cache:6144K
NUMA node0 CPU(s): 0
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp
lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid
tsc_known_freq pni monitor cx16 x2apic popcnt hypervisor lahf_lm cr8_legacy abm
sse4a misalignsse 3dnowprefetch vmmcall
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-report 1.4.0
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 8 04:06:58 2019
Dependencies:
gcc-9-base 9-20190220-0ubuntu1
libc6 2.28-0ubuntu1
libgcc1 1:9-20190220-0ubuntu1
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu1
InstallationDate: Installed on 2019-03-07 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-report
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu-report (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug disco
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1819129
Title:
No CPU record on Virtualbox
Status in ubuntu-report package in Ubuntu:
New
Bug description:
On a virtualbox guest ubuntu-report doesn't report CPU information.
u@pc:~$ ubuntu-report show
{
"Version": "19.04",
"OEM": {
"Vendor": "innotek GmbH",
"Product": "VirtualBox"
},
"BIOS": {
"Vendor": "innotek GmbH",
"Version": "VirtualBox"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "15ad",
"Model": "0405"
}
],
"RAM": 2,
"Disks": [
21.5
],
"Partitions": [
20.5
],
"Screens": [
{
"Size": "0mmx0mm",
"Resolution": "800x600",
"Frequency": "60.00"
}
],
"Autologin": true,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu",
"Type": "x11"
},
"Language": "en_US",
"Timezone": "America/New_York",
"Install": {
"Media": "Ubuntu 19.04 \"Disco Dingo\" - Alpha amd64 (20190305.1)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "use_device",
"DownloadUpdates": true,
"Language": "en",
"Minimal": false,
"RestrictedAddons": false,
"Stages": {
"0": "language",
"2": "language",
"8": "console_setup",
"16": "console_setup",
"20": "prepare",
"24": "partman",
"26": "start_install",
"86": "timezone",
"90": "usersetup",
"97": "user_done",
"582": "done"
}
}
}
@pc:~$ lscpu
[Desktop-packages] [Bug 1819126] Re: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image-content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)]
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1819126 Title: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image- content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)] Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1027 https://errors.ubuntu.com/problem/40bb6815b23393e7dfa95f5895de4b0603ac431b --- The crash happened when a new application or system crash report window from update-notifier showed up. Reproducer: 1. sleep 1000 on one terminal 2. kill -SIGSEGV $(pidof sleep) -> wait for update-notifier to try showing up apport (application crash) or update-notifier (system crash) windows. This can take up to 180s. - ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 09:32:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-05-24 (287 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_cmpnum () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so clutter_actor_get_preferred_size () at /usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0 clutter_actor_get_transformed_size () at /usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to disco on 2019-01-08 (58 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766775] Re: Notifications do not disappear
** Tags removed: artful -- 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/1766775 Title: Notifications do not disappear Status in GNOME Shell: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1766775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730458] Re: Ubuntu (gnome) freezes temporarily upon login
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1730458 Title: Ubuntu (gnome) freezes temporarily upon login Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I have noticed that gnome-shell CPU usage shoots up to over 100% for a few seconds shortly after logging in, completely freezing the shell for a good 10-20s. This happens on a migrated Unity 7 > Ubuntu session as well as on a completely new Ubuntu session (eg a user just created to test this). Ubuntu 17.10 (upgraded from 17.04), Ubuntu session (Wayland). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Nov 6 17:05:45 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 'standard_notes.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'" b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'" InstallationDate: Installed on 2016-03-13 (603 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734044] Re: gnome-shell crashes when monitor turned off or switch kvm [meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (
** Tags removed: artful ** Tags added: 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/1734044 Title: gnome-shell crashes when monitor turned off or switch kvm [meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Bug description: Gnome shell will crash every time when I turn off monitor or switch the kvm to my other system. Following message was captured in my journalctl log previously: Nov 10 17:34:31 ubox gnome-shell[1235]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Nov 10 17:34:31 ubox gnome-shell[1235]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 22 23:10:24 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-27 (27 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1734044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728455] Re: Inputting in Chrome URL Bar Triggering UI Freeze, pegged CPU and Major Memory Leak
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1728455 Title: Inputting in Chrome URL Bar Triggering UI Freeze, pegged CPU and Major Memory Leak Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: OS: Ubuntu 17.10 (Linux weilong-Ubuntu 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux) GNOME version: GNOME Shell 3.26.1 Chrome version: Version 62.0.3202.75 (Official Build) (64-bit) Description: This may very likely have something to do with my Chinese input method (iBus). I encounter this consistently while the system input method is Chinese (WubiHaifeng86) but the mode within the input method is English. Inputting in Chrome URL bar is triggering UI freeze and major memory meak. The whole UI freezes and won't respond to either mouse or keyboard. Can't switch to console by Ctrl+Alt+Fx. Was able to ssh in from another machine and gather information. Reproduce Steps: 1. Switch system input method to Chinese (WubiHaifeng86) 2. Switch to English inputting mode (while system input method is still Chinese). 3. Open Chrome 4. Input some characters in URL bar and the bug should occur. If not, use Backspace to delete some and input some more. (Sometimes swapping step 2 and 3 might help reproduce the issue.) Some info: top: top - 11:35:02 up 23 min, 3 users, load average: 2.70, 2.10, 1.20 Tasks: 221 total, 4 running, 217 sleeping, 0 stopped, 0 zombie %Cpu(s): 59.1 us, 2.9 sy, 0.0 ni, 37.9 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 8161428 total, 1386928 free, 5591952 used, 1182548 buff/cache KiB Swap: 472404 total, 472404 free,0 used. 2244372 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 870 weilong 20 0 7634048 3.726g 100292 R 116.9 47.9 6:50.39 gnome-shell 1376 weilong 20 0 399472 40320 8032 R 91.0 0.5 4:19.32 ibus-daemon 1591 weilong 20 0 273556 32908 14976 S 26.2 0.4 1:18.30 python3 1805 weilong 20 0 1513112 260204 119888 S 10.6 3.2 1:35.11 chrome 256 root 20 0 88024 13660 12756 S 1.3 0.2 0:05.23 systemd-journal 922 weilong 20 0 732384 66480 53788 S 1.3 0.8 0:21.74 Xwayland 2211 weilong 20 0 1316096 169220 58552 S 1.0 2.1 0:13.77 chrome 2078 weilong 20 0 1164120 99948 59080 S 0.7 1.2 0:06.08 chrome 35 root 20 0 0 0 0 S 0.3 0.0 0:02.60 kworker/2:1 syslogs: Oct 29 12:58:59 weilong-Ubuntu google-chrome.desktop[10633]: Created new window in existing browser session. Oct 29 12:59:21 weilong-Ubuntu org.gnome.Shell.desktop[5354]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Oct 29 12:59:24 weilong-Ubuntu org.gnome.Shell.desktop[5354]: message repeated 105 times: [ Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!] Oct 29 12:59:24 weilong-Ubuntu org.gnome.Shell.desktop[5354]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! ^C This bug is also reported to https://bugzilla.gnome.org/show_bug.cgi?id=789634 A screenshot seconds before the issue occurs is attached. Notice at the right top corner, the system input method is Chinese but in English inputting mode (showing a "英" character to indicate English inputting mode with Chinese Input method selected) 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: Sun Oct 29 14:45:33 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['ubuntu-bug gnome', 'ubuntu-bug gnome-shell']" b'org.gnome.shell' b'app-picker-view' b'uint32 1'
[Desktop-packages] [Bug 1733727] Re: visual-bell-type frame-flash does not work
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1733727 Title: visual-bell-type frame-flash does not work Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I tried to enable visual bell, frame-flash type, by doing: gsettings set org.gnome.desktop.wm.preferences visual-bell true gsetings set org.gnome.desktop.wm.preferences visual-bell-type 'frame-flash' The issue is that while visual bell gets enabled, it always flashes the whole screen. I am trying this by pressing backspace in the terminal app. 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.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 16:08:47 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-20 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1733727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727742] Re: "peek" hangs gnome-shell Wayland sessions (but not Xorg)
According to the upstream bug this was fixed in 3.28.2. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1727742 Title: "peek" hangs gnome-shell Wayland sessions (but not Xorg) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: I have "peek" installed from its PPA repository as described at https://github.com/phw/peek#ubuntu . When I attempt to record a GIF with peek under Wayland, it counts down and then my display hangs. I can't even switch VTs, so the only thing I can do at this point is power-cycle my laptop. I know it's just the display hanging, not everything, because the music I'm listening to continues to play. This occurs whether or not I set GDK_BACKEND to x11 before launching peek. Peek works fine when I use it under Xorg instead of Xwayland. See also https://github.com/phw/peek/issues/202 , the bug I filed with the peek developers about this, but regardless of whether peek is doing something wrong, it shouldn't be able to cause the display server to hang. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:09:23 2017 DistUpgraded: 2017-10-20 10:34:09,954 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller [1558:7410] InstallationDate: Installed on 2017-05-19 (159 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System76, Inc. Galago UltraPro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731420] Re: gnome-shell hangs (goes into key repeat runaway) when key repeat is used on chromium-browser's address bar
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1731420 Title: gnome-shell hangs (goes into key repeat runaway) when key repeat is used on chromium-browser's address bar Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: GNOME Shell running in Wayland completely hangs when the key repeat rate is sufficiently high and used inside Chromium and/or Google Chrome. Then GNOME Shell, at-spi's dbus-daemon, ibus-daemon, and chromium-browser all get stuck at 100% CPU. GNOME Shell's RSS also quickly increases to >2GB and continues climbing. Attempting to kill chromium-browser in a separate TTY either causes one of two things: - gnome-shell, dbus-daemon and ibus-daemon remain at 100% CPU and stuck; or - gnome-shell temporarily recovers, then crashes, taking the entire session with it and returning to the login screen. Steps to reproduce: 1. Set key repeat rates to a high value (these are my actual settings): $ gsettings set org.gnome.desktop.peripherals.keyboard repeat-interval 3 $ gsettings set org.gnome.desktop.peripherals.keyboard repeat true $ gsettings set org.gnome.desktop.peripherals.keyboard delay 180 2. Start chromium-browser 3. Focus the location bar in chromium-browser 4. Press and hold a key (e.g. a) for a few seconds (~10 should do) 5. Observe that gnome-shell probably has hung by this point. If it hasn't, proceed to step 6. 6. Press and hold the backspace button until the location bar has cleared, then continue for another few seconds (~10 seconds should do) This also affected GNOME Shell 3.24, but I was able to reduce the chances of it happening by renicing my chromium processes to +10, thereby giving GNOME Shell a greater chance at the CPU. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.13.4-hyper2+ x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 16:50:13 2017 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-11-04 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1731420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727308] Re: when you try to change the layout for a long time reacts
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1727308 Title: when you try to change the layout for a long time reacts Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: when you try to change the layout for a long time reacts and uses caps lock to change the size of letters simultaneously with the change of layout. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 17:06:55 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-08-27 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730184] Re: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: mesa (Ubuntu) Status: Incomplete => Won't Fix -- 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/1730184 Title: org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address Status in gnome-shell package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in gnome-shell package in Fedora: Unknown Bug description: Went to log into my fairly newly upgraded ubuntu artful system today but was presented with a new login instead of a login with all my applications running, similar to #1728474 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ), only I didn't have to Ctrl-Alt-F1 to get a new login, I was presented with one when I came to log in in the morning. syslog gives a clue: Nov 5 02:17:43 eva org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address Nov 5 02:17:44 eva gnome-shell[29954]: Connection to xwayland lost Nov 5 02:17:44 eva kernel: [1339701.543472] traps: gnome-shell[29954] trap int3 ip:7fcceb716961 sp:7ffd8b486020 error:0 in libglib-2.0.so.0.5400.1[7fcceb6c6000+111000] This, followed by everything that was running failing to various degrees of cleanness. intel-microcode: Installed: 3.20170707.1 Candidate: 3.20170707.1 Version table: *** 3.20170707.1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/restricted amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/restricted amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-video-intel: Installed: 2:2.99.917+git20170309-0ubuntu1 Candidate: 2:2.99.917+git20170309-0ubuntu1 Version table: *** 2:2.99.917+git20170309-0ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status libglib2.0-0: Installed: 2.54.1-1ubuntu1 Candidate: 2.54.1-1ubuntu1 Version table: *** 2.54.1-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 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: Sun Nov 5 07:27:04 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'libreoffice-calc.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']" b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-04-18 (200 days ago) InstallationMedia: Ubuntu 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. SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-19 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716265] Re: Disabling screenlock has no effect
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1716265 Title: Disabling screenlock has no effect Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Test Case; Settings > privacy > disable screenlock (log out/in or reboot doesn't help.. Let screen blank (default 5 min or to speed up set to 1 min Wake up What happens: lockscreen What should happen: go directly to desktop Test case 2: Let or make pc suspend Bring out of suspend, same as above, lockscreen Note this occurred before latest ubuntu-settings update ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.14 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 10 13:52:34 2017 InstallationDate: Installed on 2017-09-10 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1716265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718932] Re: Child windows do not have shadows in Gnome Shell
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Won't Fix -- 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/1718932 Title: Child windows do not have shadows in Gnome Shell Status in Ubuntu UX: New Status in gnome-shell package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: Some child windows do not have shadows. Test case: Open Thunderbird for the first time. A child window will appear to create a new account. It does not have shadows. Synaptic package manager also have the same issue. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170918-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 14:20:26 2017 InstallationDate: Installed on 2017-09-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1718932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
** Tags removed: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power: Confirmed Status in gnome-power-manager package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726821] Re: It takes a while for the tray notification menu to open when clicking on the time and date in the top bar
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1726821 Title: It takes a while for the tray notification menu to open when clicking on the time and date in the top bar Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Dear all, Once I click on the time and date entry in the top bar, it takes a couple of seconds for the menu to open [1]. Tested on Ubuntu 17.10 with the latest updates installed. Not sure if this is a bug or user error. [1] https://www.useloom.com/share/a80d02fd2f894c9fa6eac201c4fa1c7b --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: org.gnome.shell enabled-extensions ['clipboard-indica...@tudmotu.com', 'gnome-shell-screens...@ttll.de', 'appindicatorsupp...@rgcjonas.gmail.com', 'ubuntu-d...@ubuntu.com', 'topIcons@adel.gadl...@gmail.com', 'drive-m...@gnome-shell-extensions.gcampax.github.com'] org.gnome.shell favorite-apps ['org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'google-chrome.desktop'] org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' org.gnome.desktop.interface clock-show-date true InstallationDate: Installed on 2017-09-30 (24 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1726821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698515] Re: On screen keyboard stays English even after changing language to Finnish
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1698515 Title: On screen keyboard stays English even after changing language to Finnish Status in gnome-shell package in Ubuntu: Won't Fix Bug description: When choosing another keyboard layout (in my case Finnish) the on screen keyboard from accessibility settings still uses an English layout with no umlauts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CasperVersion: 1.383 CurrentDesktop: GNOME Date: Sat Jun 17 05:52:45 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170616) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1698515/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720745] Re: connecting to a WPA-enterprise network from gnome-shell opens up the "Networks" panel instead of the Wi-Fi panel
Fix released in 2017 according to the upstream bug. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1720745 Title: connecting to a WPA-enterprise network from gnome-shell opens up the "Networks" panel instead of the Wi-Fi panel Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: When selecting a WPA-ENTERPRISE Network for the first time, using gnome-shell "select network" popup, gnome-control-center is automatically started with the "Network" panel open. But in gnome 3.26's new control center this panel only lists Wired, Mobile Broadband, VPN connections and Network Proxy setup. WiFi configuration has been moved to a separate "Wi-Fi" panel, which I think should be opened instead. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1720745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723554] Re: Highlight border flickers in Overview when you hover mouse away from & over window
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1723554 Title: Highlight border flickers in Overview when you hover mouse away from & over window Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: BEHAVIOR When you enter activities overview, and hover your mouse over an open window (or away from an open window and then back over an open window) the border around the window flickers: it briefly fades, then returns. The border also flickers when you hover over the "X" close button at the top-right of a window in Overview, and then back to the window. EXPECTED BEHAVIOR That the blue border wouldn't flicker (or quickly fade out then fade back in) when you move the mouse into, over, or away from the window in Activities Overview. BUG DISCOVERED USING Ubuntu 17.10 beta 2 GNOME shell 3.26.1 (gnome-session package, vanilla gnome shell) Nvidia 384.90 proprietary drivers X.org 1.19.4 Linux kernel 4.13.0-15-generic To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819132] [NEW] DNS is broken after reboot or suspend
Public bug reported: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1819132 Title: DNS is broken after reboot or suspend Status in network-manager package in Ubuntu: New Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev:
[Desktop-packages] [Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()
Yes, the crash stopped happening before 18.10. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1726352 Title: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request() Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/53c0d16d8db1d08fe8ae663d632981c54b476052 --- Ordinary bug report in 17.10 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 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: ubuntu:GNOME Date: Mon Oct 23 13:08:15 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f8d82fc8c5c:mov0x18(%rax),%esi PC (0x7f8d82fc8c5c) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_x11_configure_request () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1726352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720262] Re: gnome-screenshot Actions don't work in default Ubuntu 17.10 session
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1720262 Title: gnome-screenshot Actions don't work in default Ubuntu 17.10 session Status in GNOME Shell: Confirmed Status in gnome-screenshot package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in gnome-screenshot source package in Artful: Fix Released Bug description: Ubuntu 17.10 Beta Ubuntu session (Wayland) Open the Activities Overview. Right-click on Screenshot. 2 of the 3 extra desktop actions don't work. Works = Take a Screenshot of the Whole Screen Doesn't Work Take a Screenshot of the Current Window Take a Screenshot of a Selected Area Other Info == All 3 functions work if you open Screenshot and click the buttons in the app. The Current Window action is upstream, but Selected Area is an Ubuntu patch. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1720262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819128] Re: Can't open exFAT-USB-Stick
Thank you for your bug report. Can you make a screenshot of nautilus after connecting the stick? Did you install some exfat support yourself? Ubuntu doesn't include exfat handking out of the box for patent reasons ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1819128 Title: Can't open exFAT-USB-Stick Status in nautilus package in Ubuntu: Incomplete Bug description: I've got an exFAT-USB-Stick. If I'm plugging the stick it seems to be mounted (the mounted symbol appears in nautlius). But I'm not able to open the stick to open files or for writing new files to the stick. Just if I'm formatting the stick with GNOME Disks and mounting it directly after formatting about GNOME Disks I can open the stick. After unmounting the same problem appears. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 10:00:28 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'206' b'org.gnome.nautilus.window-state' b'geometry' b"'856x481+26+23'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-11-30 (97 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1819128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691677] Re: gnome-shell on-screen keyboard has no Esc Ctrl or Alt keys
** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- 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/1691677 Title: gnome-shell on-screen keyboard has no Esc Ctrl or Alt keys Status in gnome-shell package in Ubuntu: Won't Fix Bug description: gnome-shell on-screen keyboard has no Esc Ctrl or Alt keys ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:26:37 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1691677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652179] Re: gnome-tweak-tool "Show location of pointer" (now "Pointer Location") does not work under Wayland
** Tags removed: artful yakkety -- 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/1652179 Title: gnome-tweak-tool "Show location of pointer" (now "Pointer Location") does not work under Wayland Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-tweak-tool package in Ubuntu: Confirmed Bug description: I have found that after switching from Xorg to Wayland via the login screen on Ubuntu GNOME 16.10 with GNOME 3.22 that the "Show location of pointer" gnome-tweak-tool option no longer functions in the sense that when the setting is on and I press CTRL nothing happens. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 22 22:43:16 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (221 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1652179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733727] Re: visual-bell-type frame-flash does not work
I can confirm that in 18.04 and Wayland this works as expected and only the frame flashes. -- 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/1733727 Title: visual-bell-type frame-flash does not work Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I tried to enable visual bell, frame-flash type, by doing: gsettings set org.gnome.desktop.wm.preferences visual-bell true gsetings set org.gnome.desktop.wm.preferences visual-bell-type 'frame-flash' The issue is that while visual bell gets enabled, it always flashes the whole screen. I am trying this by pressing backspace in the terminal app. 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.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 16:08:47 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-20 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1733727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys
** Tags removed: artful gnome-17.10 -- 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/1692394 Title: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I press the volume keys on my keyboard the shell displays an overlay showing the volume level. Normally this overlay is stationary, but sometimes when adjusting the volume, the overlay shifts slightly a pixel or two left or right. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Mon May 22 11:02:57 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (18 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1692394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1694373] Re: Gnome Shell app list scrolls too quickly with mouse wheel
** Tags removed: artful -- 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/1694373 Title: Gnome Shell app list scrolls too quickly with mouse wheel Status in GNOME Shell: Invalid Status in gnome-shell package in Ubuntu: New Bug description: Gnome Shell app list scrolls too quickly with mouse wheel. It seems to scroll one page per wheel tick, which is way too much. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue May 30 14:08:46 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'command-history' b"['ls', 'xterm', 'caribou', 'cariboukkk', 'cariboujj']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'chromium-browser.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (27 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1694373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1693724] Re: Context menus have no animation/fade-in under Gnome Shell
** Tags removed: artful gnome-17.10 -- 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/1693724 Title: Context menus have no animation/fade-in under Gnome Shell Status in gnome-shell package in Ubuntu: Triaged Status in ubuntu-themes package in Ubuntu: Confirmed Status in gnome-shell package in Arch Linux: New Bug description: Context menus have no animation/fade-in under Gnome Shell. The transitions under Unity7 for context menus look nicer, less abrupt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696030] Re: gnome-shell logging is too brief to be useful
** Tags removed: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1696030 Title: gnome-shell logging is too brief to be useful Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: gnome-shell appears to only log a couple of relevant lines at most on start-up (`journalctl /usr/bin/gnome-shell`): org.gnome.Shell.desktop[1893]: glamor: EGL version 1.4 (DRI2): gnome-shell[1893]: GNOME Shell started at Tue Jun 06 2017 09:38:50 GMT+0800 (AWST) Not enough information to be useful for debugging peoples' GPU and monitor start-up issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue Jun 6 10:04:35 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'command-history' b"['ls', 'xterm', 'caribou', 'cariboukkk', 'cariboujj']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'chromium-browser.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1696030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
** Tags removed: artful ** Tags added: disco -- 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/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1559650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1030309] Re: There is no 'man gnome-shell-extension-tool'
** Tags removed: artful precise quantal ** Tags added: 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/1030309 Title: There is no 'man gnome-shell-extension-tool' Status in gnome-shell package in Ubuntu: Confirmed Bug description: There is no 'man gnome-shell-extension-tool'. '~$ man gnome-shell-extension-tool ; Kein Handbucheintrag für gnome-shell-extension-tool vorhanden.' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-shell 3.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Sat Jul 28 15:36:11 2012 InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to precise on 2012-05-15 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1030309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1566357] Re: Unable to type passwords with the "Japanese (Anthy)" input method
** Tags removed: artful wily yakkety -- 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/1566357 Title: Unable to type passwords with the "Japanese (Anthy)" input method Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I recently found that I am unable to type using the "Japanese (Anthy)" input source in password fields in gnome-shell. That is I am unable to type using it (I just get English) on the login screen in the password field (though I haven't tried the username field), I am unable to type using it in the graphical prompts for authentication, and I am unable to type using it when setting a new password through the gnome- control-center. I am running Ubuntu GNOME 15.10 with GNOME 3.18 but have also experienced this issue with Ubuntu GNOME 16.04 with GNOME 3.18 as well as with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1566357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
** Tags removed: saucy vivid wily zesty ** Tags removed: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus Status in GNOME Settings Daemon: Confirmed Status in compiz package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-shell package in Fedora: Confirmed Status in gnome package in openSUSE: Unknown Bug description: When pressing any global keyboard shourtcut (configurable via System settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout, volume up/down), focus temporary switches from active text input to something else, then restores back shortly. Maybe even active window loses focus, but window frame does not shows this (window header remains to look active). For example: when I press ctrl+shift here to switch keyboard layout, when writing this description, yellow frame disappears from text input box, text caret disappears too; they appear again when releasing ctrl+shift. The same occurs in all other programs, i.e. terminal. It causes serious annoyance, for example in Twitter when losing focus in Reply text box, reply rolls up and I have to click it again with mouse and set caret to correct place each time I switch keyboard layouts. Other key combinations, not only ctrl+shift, also cause this. It is especially annoying when using keyboard layout switch shortcut handled by the same subsystem (media-keys plugin): case SWITCH_INPUT_SOURCE_KEY: case SWITCH_INPUT_SOURCE_BACKWARD_KEY: do_switch_input_source_action (manager, type); break; (Original gnome-settings-daemon, from which unity-settings-daemon was forked, does not use media-keys plugin to switch keyboard layout). -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 11:42:19 2013 InstallationDate: Installed on 2013-10-23 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1389650] Re: Ctrl+Alt+L fails to lock the screen in the default setup of Gnome 3 (gnome shell)
The key combo was changed to Super+L and it seems to work at least in 18.04 onward. ** Tags removed: artful ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1389650 Title: Ctrl+Alt+L fails to lock the screen in the default setup of Gnome 3 (gnome shell) Status in GNOME Settings Daemon: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Ctrl+Alt+L fails to lock the screen in the default setup of Ubuntu 14.10 + Gnome 3 (gnome shell). All packages are up to date and I verified that Ctrl+Alt+L is indeed the shortcut to lock the screen. What helped was adding gnome-screensaver to the startup programs (was installed but wasn't started by default) as mentioned here: http://askubuntu.com/a/542391 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1389650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login
I tried installing 4.18, but it persisted. I tried an older kernel, and then the networking stopped working. I tried re-installing Bionic Beaver, and when booting from USB everything works. But after install and update, it's broken again. -- 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/1818899 Title: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I can boot to login, but if I input correct information it freezes. If I boot in recovery mode and choose to resume boot, I can login. But my external display doesn't register. If I choose the failsafeX version there is an error text related to xorg. I have not had any problems before on this terminal. It came when I let the system update and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 20:26:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:119b] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1197] InstallationDate: Installed on 2018-11-26 (100 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-71G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmeleon_KLS dmi.board.vendor: KBL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA715-71G:pvrV1.10:rvnKBL:rnCharmeleon_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-71G dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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: Wed Mar 6 20:16:01 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 --- ProblemType: Bug .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:119b] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
Hello Mordi, or anyone else affected, Accepted nautilus into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nautilus/1:3.26.4-0ubuntu7.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-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. ** Changed in: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: In Progress Status in nautilus source package in Bionic: Fix Committed Status in nautilus source package in Cosmic: Fix Committed Bug description: * Impact The text search feature, which is depending on tracker, is not working even when the service is installed * Test case - install tracker and restart your session - echo 'Nautilus is great' > ~/txt - open nautilus and type 'great' in the search entry -> the file should be listed * Regression potential That's changing the search provider logic, make sure that searching for file without tracker still works (that only look at filenames) and there is no extra logging/cpu usage --- Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700465] Re: gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory
Is this bug still present in the final release of 18.04 or later? The 'bionic' tag was added in 2017. ** Tags removed: artful zesty ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1700465 Title: gnome-shell --replace does not work: Can't initialize KMS backend: Could not get session ID: No such file or directory Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: gnome-shell --replace does not work and reports: (gnome-shell:15848): mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory (gnome-shell:16495): mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory (gnome-shell:4910): mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-25.29-generic 4.10.17 Uname: Linux 4.10.0-25-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 26 09:03:06 2017 DisplayManager: gdm3 InstallationDate: Installed on 2015-07-10 (716 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-shell UpgradeStatus: Upgraded to zesty on 2017-06-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1700465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions)
** Tags removed: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions) Status in GTK+: New Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697521] Re: gnome-shell crashed with SIGSEGV in _clutter_id_pool_remove() from _clutter_stage_release_pick_id() from clutter_actor_real_unmap()
Zero crash reports in 18.10 onward. ** Tags removed: artful ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- 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/1697521 Title: gnome-shell crashed with SIGSEGV in _clutter_id_pool_remove() from _clutter_stage_release_pick_id() from clutter_actor_real_unmap() Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/2da983b391f69f4806106b9cac88533222d00359 --- Gnome shell just crashed when the computer as idle and had the crash dialog open when I came back. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 12 18:41:37 2017 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-06-03 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170602) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7efd6e972fa1:movq $0x0,(%rax,%rsi,8) PC (0x7efd6e972fa1) ok source "$0x0" ok destination "(%rax,%rsi,8)" (0x55df79740238) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so () at /usr/lib/gnome-shell/libgnome-shell.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1697521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697143] Re: GNOME Shell's Suspend feature is hidden in power menu
** Tags removed: artful gnome-17.10 ** Tags added: disco -- 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/1697143 Title: GNOME Shell's Suspend feature is hidden in power menu Status in gnome-shell package in Ubuntu: Confirmed Bug description: There is no suspend option in the power menu with gnome. There is supposed to be some modifier + click combination which I forget but no way to find it out except by accident. Suspend is a standard feature that's been in the unity menu and should be retained with the move to gnome shell. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CasperVersion: 1.383 CurrentDesktop: GNOME Date: Sat Jun 10 06:58:11 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1697143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818595] Re: Update to 1.46
needs SRU template also, "fix committed" is set when the package is accepted to proposed ** Changed in: snapd-glib (Ubuntu Cosmic) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818595 Title: Update to 1.46 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Cosmic: Incomplete Status in snapd-glib source package in Disco: Fix Released Bug description: https://wiki.ubuntu.com/SnapdGlibUpdates Overview of changes in snapd-glib 1.46 * New API: - snapd_channel_get_released_at - SNAPD_ERROR_DNS_FAILURE * Fix tests breaking due to undefined order of results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818595/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712122] Re: Desktop keyboard shortcuts autorepeat (probably shouldn't)
** Tags removed: artful -- 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/1712122 Title: Desktop keyboard shortcuts autorepeat (probably shouldn't) Status in gnome-shell package in Ubuntu: Triaged Bug description: "Please hold down CTRL+ALT and press T" sometimes results in (novice) users holding down all three keys at once. Desired behaviour:- One terminal opens, keyboard combination does not repeat. Actual behaviour:- Bazillions of terminals launch On my Ubuntu 16.04 system running Unity, the keyboard shortcut does not repeat. On 17.10 GNOME Shell it does. I believe it should not. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 18:12:51 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-control-center', 'bin/telegram', '~/bin/Telegram', '~/bin/telegram', '/home/alan/bin/telegram', '/home/alan/bin/Telegram', 'brackets', '/snap/bin/brackets']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1712122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706476] Re: Mysterious shadow around window when check marking an option box inside of window
** Tags removed: artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1706476 Title: Mysterious shadow around window when check marking an option box inside of window Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: this mysterious shadow occurs when I click inside an empty option box in a window to download a file from my cloud service. it's the option box for "do this automatically for files like this for now on." the shadow is very brief and completely surrounds the window and is the same shape as the window, square. I've never seen this type of behavior on any version of Ubuntu so I thought it was a bug of some kind worth mentioning and it occurs every time I click the box to select/deselect it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 25 18:25:25 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com', 'refresh-w...@kgshank.net']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'thunderbird.desktop', 'hexchat.desktop', 'gimp.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.Calculator.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-07-25 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
Is there a 16.04 package? This was a regression there caused by an earlier update. I have users reporting the same bizarre behaviour I wasn't able to clearly describe before — essentially, DNS being sent out seemingly random interfaces (sometimes VPN, sometimes local). My advice to just install this package *and* manually set dns-priority=-1,dns-search=~. and get on with life even though you really shouldn't have to manually set the latter, doesn't work for the 16.04 users... And yes, when other things stop being on fire I need to undo those settings and try to work out what's going wrong. We aren't using systemd-resolve here because historically it also hasn't worked right while dnsmasq did. -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: * Impact When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not * Test case Configure the system to send all the traffic to a VPN, do a name resolution, the request should not go to the public DNS server (to be checked by capturing the traffic by example with wireshark) * Regression potential The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Any progress on this? It would be nice to get this fixed in distribution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Incomplete Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every jon, insteaf of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 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 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750197] Re: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg
It seems the fix is upstream already in the gnome-3-28 branch, but didn't appear there early enough to make it into bionic-proposed version 3.28.3+git20190124-0ubuntu18.04.1 :/ ** Changed in: gnome-shell (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1750197 Title: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Released Status in gnome-shell source package in Disco: Fix Released Bug description: Upstream Issues: https://gitlab.gnome.org/GNOME/gnome-shell/issues/349 https://gitlab.gnome.org/GNOME/mutter/issues/233 Ubuntu Release: 17.10 and 18.04 gnome-shell version: 3.28.2 System Theme: CommuniTheme Opening the Applications Overview (App Grid) displays a very janky animation, and my CPU will spike to nearly 90% for each open/close. This happens regardless of using XOrg or Wayland; however Wayland appears to have an overall higher impact on resource usage. This same issue is still existent, but somewhat less noticeable on my other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds after opening/closing the app drawer. Please do not hesitate to follow up with requests for more info, as I will be happy to help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Feb 17 19:13:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750197] Re: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg
Found the fix hiding in gnome-shell_3.28.3+git20190124.orig.tar.xz So it's already in bionic-proposed: https://launchpad.net/ubuntu/+source/gnome- shell/3.28.3+git20190124-0ubuntu18.04.1 ** Changed in: gnome-shell (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1750197 Title: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Released Status in gnome-shell source package in Disco: Fix Released Bug description: Upstream Issues: https://gitlab.gnome.org/GNOME/gnome-shell/issues/349 https://gitlab.gnome.org/GNOME/mutter/issues/233 Ubuntu Release: 17.10 and 18.04 gnome-shell version: 3.28.2 System Theme: CommuniTheme Opening the Applications Overview (App Grid) displays a very janky animation, and my CPU will spike to nearly 90% for each open/close. This happens regardless of using XOrg or Wayland; however Wayland appears to have an overall higher impact on resource usage. This same issue is still existent, but somewhat less noticeable on my other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds after opening/closing the app drawer. Please do not hesitate to follow up with requests for more info, as I will be happy to help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Feb 17 19:13:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1757091] Re: systemctl enable lightdm
Is there a workaround tip in order to re-enable lightdm in ubuntu 18.04 ? I am using systemd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1757091 Title: systemctl enable lightdm Status in lightdm package in Ubuntu: Confirmed Bug description: Synchronizing state of lightdm.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable lightdm The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Mar 20 11:44:46 2018 InstallationDate: Installed on 2018-01-22 (57 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
