[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
** Changed in: gdm3 (Ubuntu) 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Changed in: gnome-menus (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Re
[Desktop-packages] [Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
Fix committed upstream. It will be included in gnome-shell versions 3.28.3 and 3.29.3. ** Bug watch added: GNOME Bug Tracker #788931 https://bugzilla.gnome.org/show_bug.cgi?id=788931 ** Tags added: fixed-in-3.28.3 fixed-in-3.29.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() Status in GNOME Shell: Unknown Status in gjs package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/811164cadd3e9e891f9e2d439bda59925f91a62c --- trying to get vpn up and running ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 18:00:19 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['vpn-indica...@howdoicomputer.fastmail.com']" 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', 'org.gnome.Terminal.desktop', 'cisco-anyconnect.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-03-23 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fd17cf23d3d : movzbl 0x16(%rax),%edx PC (0x7fd17cf23d3d) ok source "0x16(%rax)" (0x00024562) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to bionic on 2018-03-24 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1759621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
For me, "apt-get remove libnvidia-gl-390" solved it. No idea how it came to be installed, but for some reason the active EGL driver was nvidia, and that interfered with the X start sequence. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: Confirmed Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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+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/+bug/1752938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import certificates in Ubuntu 18.04
Affects email signing, encryption through Thunderbird and signing of documents through LibreOffice. Had to show a demo to my boss on how Ubuntu + G Suite could be used for field users and got an unpleasant surprise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import certificates in Ubuntu 18.04 Status in gnome-keyring package in Ubuntu: Confirmed Status in seahorse package in Ubuntu: Confirmed Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1771880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt
** Tags added: rls-bb-incoming ** Summary changed: - [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt + [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt ** Description changed: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 - Ubuntu 18.04 login screen rejects a valid password on first attempt. - Always works on the second attempt.. + Workaround: + Hit a lower-case key, then backspace, then enter your password. + + Original description: + Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell package in Fedora: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Workaround: Hit a lower-case key, then backspace, then enter your password. Original description: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 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/1765261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen
The time of the Xorg crash file is ~correct for the crash that logged me out (between 1st & 2nd line in my syslog snippet). I was using XFCE or Xubuntu-session login (this issue only ever happened with XFCE/Xubuntu but I can't guarantee it was XFCE the first in list & not Xubuntu- session; they look & act identical [for me] after login) the other one (light-locker) I can't recall. Yes I've been testing sleep (inc. other DEsktops but not at that time (I don't remember, this recall is from scanning syslog messages). I can see I hand't put my machine to sleep for some time before or after it, and the next minute opened a terminal (common behavior), hence don't believe it's related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772542 Title: after waking from sleep i get text radeon error message then return login screen Status in xorg package in Ubuntu: Incomplete Bug description: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pul
[Desktop-packages] [Bug 1771971] Re: dns broken after upgrade to bionic
I purged `netplan` and `/etc/init.d/netplan` was removed. I reinstalled `netplan.io` but `/etc/init.d/netplan` now is missing completely. The nameserver however is now shown in `systemd-resolve --status` but still it does not work. ``` ~# cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile,ofono dns=dnsmasq no-auto-default=E8:03:9A:F1:C2:6B, [ifupdown] managed=false ``` -- 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/1771971 Title: dns broken after upgrade to bionic Status in network-manager package in Ubuntu: Incomplete Bug description: After upgrade to Bionic my DNS is broken. `resolv.conf` contains ``` # 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. nameserver 127.0.0.53 ``` and network is configured via network manager and DHCP. But DNS will only work when entering the IP manually. Maybe something wrong with netplan? ``` ~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlan0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (eth0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: netplan.io 0.36.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: i3 Date: Fri May 18 09:56:49 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-03 (1444 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: netplan.io UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1771971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
Same problem here. After upgrading my laptop from Lubuntu 16.04 to Lubuntu 18.04, there is no hardware acceleration anymore. AMD STONEY was perfectly capable of this on the older release. glxinfo shows: OpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits) /var/log/Xorg.0.log shows: [16.679] (EE) AMDGPU(0): eglGetDisplay() failed [16.679] (EE) AMDGPU(0): glamor detected, failed to initialize EGL. [16.685] (==) AMDGPU(0): DRI3 disabled ... [16.692] (II) AIGLX: Screen 0 is not DRI2 capable [16.692] (EE) AIGLX: reverting to software rendering [16.699] (II) IGLX: enabled GLX_MESA_copy_sub_buffer [16.700] (II) IGLX: Loaded and initialized swrast [16.700] (II) GLX: Initialized DRISWRAST GL provider for screen 0 Nothing in the kernel log indicates that there is a problem with the amdgpu driver. Tried creating a xorg.conf and forcing DRI to 3, but no dice. LIBGL_ALWAYS_SOFTWARE is not set, there is no /etc/X11/Xsession.d/50_check_unity_support, so it's probably not bug #1767468. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: Confirmed Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 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+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/+bu
[Desktop-packages] [Bug 1774094] Re: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file
The attachment ".desktop rename patch for Nautilus" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1774094 Title: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file Status in nautilus package in Ubuntu: New Bug description: When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is automatically appended. This causes the .desktop extension to get duplicated, where renaming `app.desktop` to `app2.desktop` will actually rename it to `app2.desktop.desktop`. The included patch fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727421] Re: Desktop focus border radius not matching overview panel border radius
[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/1727421 Title: Desktop focus border radius not matching overview panel border radius Status in gnome-shell package in Ubuntu: Expired Bug description: When enabling the activities overview, the current thickness/border- radius values of the currently focused desktop conflict with the outer perimeter of the overview panel. Solution: Decrease the focus border thickness and/or enable a border-radius value to the ubuntu.css override for the desktop/window focus border so that both corner roundings match and do not conflict visually. See attached image for details. ProblemType: Bug 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 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 12:11:03 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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/1727421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759758] Re: gsd-locate-pointer crashed with signal 5 in _XEventsQueued()
[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Expired -- 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/1759758 Title: gsd-locate-pointer crashed with signal 5 in _XEventsQueued() Status in gnome-settings-daemon package in Ubuntu: Expired Bug description: - ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 14:18:10 2018 ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-locate-pointer InstallationDate: Installed on 2018-03-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-locate-pointer Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gsd-locate-pointer crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen
Chris Guiver: 1) Going forward, please don't quote snips of logs, as the root cause issue could have happened well before this, and what you are snipping is collateral damage. Instead, attach the log in its entirety as you have done. 2) Regarding #7: >"New crash reports in /var/crash are -rw-r- 1 guiverc whoopsie 882227 May 29 14:17 _usr_bin_light-locker.1000.crash -rw-r- 1 guiverc whoopsie 24809765 May 30 09:54 _usr_lib_xorg_Xorg.1000.crash" To clarify, did these both happen after a resume from suspend, and then you attempted to login? If so, what desktop session specifically (e.g. Ubuntu)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772542 Title: after waking from sleep i get text radeon error message then return login screen Status in xorg package in Ubuntu: Incomplete Bug description: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.
[Desktop-packages] [Bug 1774053] Re: Missing characters in gnome-shell after lock screen
** Changed in: gnome-shell Status: Unknown => Confirmed ** Changed in: gnome-shell Importance: Unknown => Medium -- 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/1774053 Title: Missing characters in gnome-shell after lock screen Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: I locked my screen, came back from lunch, and found that about half the characters in the lock screen were missing. After I logged back in, half the characters in the desktop were missing (https://drive.google.com/file/d/1mIDF4_jY0PIFOT53FoOOVoTY1BWeaNfy/view?usp=sharing). Chrome and Nautilus are not missing any characters, just the system UI. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 12:25:58 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-04-10 (48 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=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/1774053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774094] [NEW] [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file
Public bug reported: When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is automatically appended. This causes the .desktop extension to get duplicated, where renaming `app.desktop` to `app2.desktop` will actually rename it to `app2.desktop.desktop`. The included patch fixes the issue. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Patch added: ".desktop rename patch for Nautilus" https://bugs.launchpad.net/bugs/1774094/+attachment/5146234/+files/desktop-rename.patch -- 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/1774094 Title: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file Status in nautilus package in Ubuntu: New Bug description: When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is automatically appended. This causes the .desktop extension to get duplicated, where renaming `app.desktop` to `app2.desktop` will actually rename it to `app2.desktop.desktop`. The included patch fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774081] Re: /etc/gdm3/Init/Default not evaluated
The problem has already been reported here: https://gitlab.gnome.org/GNOME/gdm/issues/317 Please comment on that bug if you have more information. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed ** Description changed: + https://gitlab.gnome.org/GNOME/gdm/issues/317 + + --- + /etc/gdm3/Init/Default is not evaluated on my fresh install of Ubuntu 18.04 (minimal). I replaced this file by one with the following content to test it: #!/bin/sh touch /tmp/a touch /mnt/a After a reboot, these files are not available. When I use the same file for /etc/gdm3/PostLogin/Default, it works. ** Bug watch added: GNOME Bug Tracker #783497 https://bugzilla.gnome.org/show_bug.cgi?id=783497 ** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=783497 Importance: Unknown Status: Unknown -- 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/1774081 Title: /etc/gdm3/Init/Default not evaluated Status in gdm: Unknown Status in gdm3 package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/317 --- /etc/gdm3/Init/Default is not evaluated on my fresh install of Ubuntu 18.04 (minimal). I replaced this file by one with the following content to test it: #!/bin/sh touch /tmp/a touch /mnt/a After a reboot, these files are not available. When I use the same file for /etc/gdm3/PostLogin/Default, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1774081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774053] Re: Missing characters in gnome-shell after lock screen
Also tracking in https://bugzilla.gnome.org/show_bug.cgi?id=728158 ** Summary changed: - Missing characters in and after lock screen + Missing characters in gnome-shell after lock screen ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Bug watch added: GNOME Bug Tracker #728158 https://bugzilla.gnome.org/show_bug.cgi?id=728158 ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=728158 Importance: Unknown Status: Unknown ** Tags added: nvidia -- 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/1774053 Title: Missing characters in gnome-shell after lock screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: I locked my screen, came back from lunch, and found that about half the characters in the lock screen were missing. After I logged back in, half the characters in the desktop were missing (https://drive.google.com/file/d/1mIDF4_jY0PIFOT53FoOOVoTY1BWeaNfy/view?usp=sharing). Chrome and Nautilus are not missing any characters, just the system UI. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 12:25:58 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-04-10 (48 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=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/1774053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774047] Re: gnome (or something) uses a lot of memory
*** This bug is a duplicate of bug 1672297 *** https://bugs.launchpad.net/bugs/1672297 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1672297, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1672297 gnome-shell uses lots of memory, and grows over time -- 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/1774047 Title: gnome (or something) uses a lot of memory Status in gnome-shell package in Ubuntu: New Bug description: After I log in (ubuntu session) the systen(?), shell(?) uses a lot of memory. When the computer has 2GB RAM, 1.2GB is used. When the computer has 4GB RAM, 1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried it out in virtualbox with a newly installed system. I changed the memory size and started ubuntu. I think a new, clean system should use the same amount of memory independently of the RAM size. Not to mention that the system is unusable, because RAM quickly fills up (memory leak?) and become laggy. Unity in 16.04 uses approx. 800kB memory. Why does gnome-shell need so much memory? I think it should be fixed, because 18.04 is an LTS release! I would like to work with it.Description: Ubuntu 18.04 LTS Release: 18.04 gnome-shell: Telepítve: 3.28.1-0ubuntu2 Jelölt:3.28.1-0ubuntu2 Verziótáblázat: *** 3.28.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 20:21:39 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (221 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763648] Re: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04
I am getting the same error as Ricardo installing from PPA on Ubuntu 18.04. It also fails if I attempt to install from the script provided on the NVidia website for my card (nVidia GeForce 7800 GT) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1763648 Title: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04 Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: nvidia-304 is not available in the Ubuntu 18.04. Newer versions are available but I have an old nVidia 7600 GT, so I need 304.137. I searched online and found that at https://answers.launchpad.net/ubuntu/bionic/amd64/nvidia-304/304.137-0ubuntu2 it has Status: Deleted :( Could you please pack this for the new release of Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1763648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen
** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772542 Title: after waking from sleep i get text radeon error message then return login screen Status in xorg package in Ubuntu: Incomplete Bug description: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22. 67 May 22 09:36:29 d960-ubu2 systemd-logind[1108]: Removed session 166. 68 May 22 09:37:39 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session opened for user guiverc by (uid=0) 69 May 22 0
[Desktop-packages] [Bug 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time
All, Can you please test to see if moving the Chrome window away from the launcher (on the left) reduces the CPU usage of gnome-shell? I know that having windows changing near the launcher is a problem. And I will get back to fixing that soon (bug 1743976). ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772365 Title: gnome-shell + chrome doing nothing consumes high CPU all the time Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is somewhat similar to https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1696305 After a few cycles of suspend, working with external monitor, running Chrome with 10+ opened tabs causes gnome-shell and chrome to use 60% of CPU just idling. When I do some more active work - it consumes even more. My laptop is hot all the time. 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 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 10:34:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-01-31 (474 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) 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/1772365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell even when idle
What screen resolution are you using? You can just run 'xrandr' and send us the output. -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). 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 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772365 Title: gnome-shell + chrome doing nothing consumes high CPU all the time Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is somewhat similar to https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1696305 After a few cycles of suspend, working with external monitor, running Chrome with 10+ opened tabs causes gnome-shell and chrome to use 60% of CPU just idling. When I do some more active work - it consumes even more. My laptop is hot all the time. 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 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 10:34:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-01-31 (474 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) 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/1772365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time
** Summary changed: - gnome-shell + chrome doing nothing consumes 60%+ CPU all the time + gnome-shell + chrome doing nothing consumes high CPU all the time -- 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/1772365 Title: gnome-shell + chrome doing nothing consumes high CPU all the time Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is somewhat similar to https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1696305 After a few cycles of suspend, working with external monitor, running Chrome with 10+ opened tabs causes gnome-shell and chrome to use 60% of CPU just idling. When I do some more active work - it consumes even more. My laptop is hot all the time. 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 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 10:34:07 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-01-31 (474 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) 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/1772365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773528] Re: High CPU usage by gnome-shell when using Google Chrome
*** This bug is a duplicate of bug 1772365 *** https://bugs.launchpad.net/bugs/1772365 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1772365, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1772365 gnome-shell + chrome doing nothing consumes high CPU all the time -- 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/1773528 Title: High CPU usage by gnome-shell when using Google Chrome Status in gnome-shell package in Ubuntu: Triaged Bug description: Usually 40% or more CPU usage. May be related to AMD GPU. Problem disappears while using XFCE. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 26 16:59:28 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-28 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/1773528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell even when idle
Also, is the terminal window touching the launcher to the left? Is it maximized? Or does the problem persist when the terminal is a small window in the middle of the screen? ** Summary changed: - High CPU usage by gnome-shell even when idle + High CPU usage by gnome-shell when only running gnome-terminal ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). 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 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell even when idle
I agree the CPU usage is too high. Please: 1. Avoid using extensions if you can, or at least verify a bug exists when no extensions are loaded. 2. After unloading all extensions, let us know exactly which apps are running to trigger the problem. ** Tags added: performance -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). 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 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770731] Re: [nvidia] multimonitor ghostly flickering display artifacts
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Description changed: + https://gitlab.gnome.org/GNOME/mutter/issues/175 + + --- + On Ubuntu 18.04, running nvidia-390 driver (on a GTX 1080), and gnome shell 3.28.1. I have a 3 monitor setup. When I open a terminal in the middle window and some other window, like nautilus on the left, and quickly drag the nautilus window to the right, covering the terminal, and back without releasing the mouse, a flickering ghost of the window remains on the terminal for about a minute or so. - --- + --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: - b'org.gnome.shell' b'favorite-apps' redacted by apport - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" - b'org.gnome.desktop.interface' b'clock-format' b"'12h'" + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2018-05-10 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1770731 Title: [nvidia] multimonitor ghostly flickering display artifacts Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/175 --- On Ubuntu 18.04, running nvidia-390 driver (on a GTX 1080), and gnome shell 3.28.1. I have a 3 monitor setup. When I open a terminal in the middle window and some other window, like nautilus on the left, and quickly drag the nautilus window to the right, covering the terminal, and back without releasing the mouse, a flickering ghost of the window remains on the terminal for about a minute or so. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2018-05-10 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-22-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/ubuntu/+source/gnome-shell/+bug/1770731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773955] Re: GDM very slow after resume from suspend
** Tags added: performance ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: resume -- 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/1773955 Title: GDM very slow after resume from suspend Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: When resuming from suspend GDM is very unresponsive. It takes several seconds to show the login screen after starting to type the password and it's common to need to press enter several times before it will recognize and unlock. This is a big regression on this machine compared to 16.04 where the login interface was much more usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:17:56 2018 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
Actually it was fix released. Someone should tell Red Hat :) -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Won't Fix Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Changed in: gnome-menus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Fix Released Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-25 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Re: [Desktop-packages] [Bug 137527] Re: Unhelpful response when inserting encrypted DVD in default installation
Stop On Thu, May 24, 2018, 9:45 PM Bug Watch Updater <137...@bugs.launchpad.net> wrote: > ** Changed in: totem >Status: In Progress => Expired > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (219062). > https://bugs.launchpad.net/bugs/137527 > > Title: > Unhelpful response when inserting encrypted DVD in default > installation > > Status in Totem: > Expired > Status in totem package in Ubuntu: > Triaged > > Bug description: > Ubuntu 4.10, 5.04, 5.10, 6.06, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, > 10.04, 10.10, 11.04, 11.10, 12.04, 14.04 > > 1. Install Ubuntu. > 2. Insert a standard movie DVD. > > What happens: > * In Ubuntu 10.10 and earlier, "An error occurred" - "Could not read > from resource." > * In Ubuntu 11.10, "An error occurred" - "Could not read DVD. This may > be because the DVD is encrypted and a DVD decryption library is not > installed." > > Without libdvdcss2, Totem, VLC, and others are unable to play my > original DVD-s. I know it's illegal to ship Ubuntu with libdvdcss2, > but it could be in multiverse repos, and totem's plugin installer > could install it, OR add the medibuntu repo to the list (but leave > unchecked), then Totem's plugin installer should give a hint, to use > that repo's libdvdcss2 to play your DVDs. Newbies wont find out how to > solve this problem by theirself, go back to win, and then it will be > harder to solve the bug #1 :) > > Not to be confused with: > * bug 502426, where DVDs don't play when libdvdcss is installed > * bug 745515, "An error occured location not found" while trying to play > a DVD > * bug 747433, "Totem cannot play this type of media DVD because it does > not have the appropriate plugins to be able to read from this disc" > > To manage notifications about this bug go to: > https://bugs.launchpad.net/totem/+bug/137527/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/137527 Title: Unhelpful response when inserting encrypted DVD in default installation Status in Totem: Expired Status in totem package in Ubuntu: Triaged Bug description: Ubuntu 4.10, 5.04, 5.10, 6.06, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, 10.04, 10.10, 11.04, 11.10, 12.04, 14.04 1. Install Ubuntu. 2. Insert a standard movie DVD. What happens: * In Ubuntu 10.10 and earlier, "An error occurred" - "Could not read from resource." * In Ubuntu 11.10, "An error occurred" - "Could not read DVD. This may be because the DVD is encrypted and a DVD decryption library is not installed." Without libdvdcss2, Totem, VLC, and others are unable to play my original DVD-s. I know it's illegal to ship Ubuntu with libdvdcss2, but it could be in multiverse repos, and totem's plugin installer could install it, OR add the medibuntu repo to the list (but leave unchecked), then Totem's plugin installer should give a hint, to use that repo's libdvdcss2 to play your DVDs. Newbies wont find out how to solve this problem by theirself, go back to win, and then it will be harder to solve the bug #1 :) Not to be confused with: * bug 502426, where DVDs don't play when libdvdcss is installed * bug 745515, "An error occured location not found" while trying to play a DVD * bug 747433, "Totem cannot play this type of media DVD because it does not have the appropriate plugins to be able to read from this disc" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/137527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen
no crash report numbers ** Attachment added: "auth.log copied after i could login again" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5146202/+files/auth.log.2018-05-30.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772542 Title: after waking from sleep i get text radeon error message then return login screen Status in xorg package in Ubuntu: Incomplete Bug description: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22. 67 May 22 09:36:29 d960-ubu2 systemd-l
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen
** Attachment added: "dmesg (copied after i logged in again)" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5146203/+files/dmesg_2018-05-30.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772542 Title: after waking from sleep i get text radeon error message then return login screen Status in xorg package in Ubuntu: Incomplete Bug description: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. 66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22. 67 May 22 09:36:29 d960-ubu2 systemd-logind[1108]: Removed session 16
[Desktop-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen
// from auth.log (29-may was last night, 30-may was wake of system today) May 30 09:54:56 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc May 30 09:54:59 d960-ubu2 dbus-daemon[1020]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.220" (uid=1000 pid=25256 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) May 30 09:55:07 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session opened for user guiverc by (uid=0) // I think crash was 09:54:59 (in that log) // from syslog May 30 09:54:51 d960-ubu2 systemd-resolved[895]: Using degraded feature set (UDP) for DNS server 203.0.178.191. May 30 09:54:56 d960-ubu2 transmission-gt[17087]: transmission-gtk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. May 30 09:54:56 d960-ubu2 at-spi-bus-launcher[1995]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" May 30 09:54:57 d960-ubu2 at-spi-bus-launcher[1995]: after 37113 requests (37113 known processed) with 0 events remaining. May 30 09:54:57 d960-ubu2 [23692]: mate-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. May 30 09:54:57 d960-ubu2 /usr/lib/gdm3/gdm-x-session[1844]: xfce4-volumed: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. May 30 09:54:57 d960-ubu2 [3451]: gnome-clocks: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. May 30 09:54:57 d960-ubu2 /usr/lib/gdm3/gdm-x-session[1844]: wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. May 30 09:54:57 d960-ubu2 [2213]: blueman-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. May 30 09:54:57 d960-ubu2 /usr/lib/gdm3/gdm-x-session[1844]: audacious: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. May 30 09:54:57 d960-ubu2 [3236]: xfce4-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. May 30 09:54:57 d960-ubu2 /usr/lib/gdm3/gdm-x-session[1844]: kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. May 30 09:54:57 d960-ubu2 [2059]: telegram: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. these messages repeat for each app I must have had open, then for XFCE apps ... - refer attachment // i think 09:55:07 is X starting again sending me to greeter after crash NOTE: I'm no expert & this is only 'user' opinion New crash reports in /var/crash are -rw-r- 1 guiverc whoopsie 882227 May 29 14:17 _usr_bin_light-locker.1000.crash -rw-r- 1 guiverc whoopsie 24809765 May 30 09:54 _usr_lib_xorg_Xorg.1000.crash I'll upload these & add any report-numbers to this on next comment. I will attach my current syslog & next comment auth.log & dmesg (dated 2018-05-30 & timestamped just before 1000) ** Attachment added: "syslog_2018-05-30 (copied to ~ when I could login again)" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772542/+attachment/5146198/+files/syslog.2018-05-30.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772542 Title: after waking from sleep i get text radeon error message then return login screen Status in xorg package in Ubuntu: Incomplete Bug description: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwh
[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
even if not the default ntp implementation, I think this is still a valid bug task and should be tracked as such. ** Changed in: ntp (Ubuntu) Importance: Undecided => Low ** Changed in: ntp (Ubuntu) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1718227 Title: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts Status in aiccu package in Ubuntu: Invalid Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: New Status in bind9 package in Ubuntu: Invalid Status in chrony package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Triaged Status in controlaula package in Ubuntu: Invalid Status in epoptes package in Ubuntu: New Status in ethtool package in Ubuntu: Triaged Status in guidedog package in Ubuntu: New Status in htpdate package in Ubuntu: New Status in ifenslave package in Ubuntu: Won't Fix Status in ifmetric package in Ubuntu: Won't Fix Status in ifupdown-multi package in Ubuntu: New Status in ifupdown-scripts-zg2 package in Ubuntu: Invalid Status in isatapd package in Ubuntu: New Status in lprng package in Ubuntu: New Status in miredo package in Ubuntu: New Status in mythtv package in Ubuntu: New Status in nplan package in Ubuntu: New Status in nss-pam-ldapd package in Ubuntu: New Status in ntp package in Ubuntu: Triaged Status in openntpd package in Ubuntu: New Status in openresolv package in Ubuntu: Won't Fix Status in openssh package in Ubuntu: New Status in openvpn package in Ubuntu: New Status in openvswitch package in Ubuntu: New Status in postfix package in Ubuntu: New Status in quicktun package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in shorewall-init package in Ubuntu: New Status in sidedoor package in Ubuntu: New Status in slrn package in Ubuntu: New Status in tinc package in Ubuntu: New Status in ubuntu-fan package in Ubuntu: Fix Released Status in ucarp package in Ubuntu: New Status in uml-utilities package in Ubuntu: New Status in uruk package in Ubuntu: New Status in vlan package in Ubuntu: Won't Fix Status in vzctl package in Ubuntu: Triaged Status in wide-dhcpv6 package in Ubuntu: New Status in wpa package in Ubuntu: New Bug description: when network is configured with ifupdown, scripts in /etc/network/ifup.d/ were called on network being brought up and /etc/network/ifdown.d were called on network being brought down. Any packages that shipped these hooks need to be verified to have the same functionality under a netplan configured system. # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u) # for i in $binpkgs; do src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }'); [ -z "$src" ] && src="$i"; echo $src; done | sort -u aiccu aoetools avahi bind9 chrony clamav controlaula epoptes ethtool guidedog htpdate ifenslave ifmetric ifupdown-extra ifupdown-multi ifupdown-scripts-zg2 isatapd lprng miredo mythtv-backend nss-pam-ldapd ntp openntpd openresolv openssh openvpn postfix quicktun resolvconf sendmail shorewall-init sidedoor slrn tinc ubuntu-fan ucarp uml-utilities uruk vlan vzctl wide-dhcpv6 wpa Related bugs: * bug 1718227: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts * bug 1713803: replacement of resolvconf with systemd needs integration * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: netplan (not installed) ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 19 10:53:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Found a workaround: xrandr --addmode HDMI-1-2 1920x1080 xrandr --output HDMI-1-2 --mode 1920x1080 This sequence of commands enables clone display. However, I still don't see anywhere in Displays/Monitors the secondary display. Here is the xrandr output (while projector is on): HDMI-1-1 disconnected 1920x1080+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1920x1080 60.02* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: New Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 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.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43
[Desktop-packages] [Bug 1770971] Re: Update gnome-system-monitor to 3.28.2
This bug was fixed in the package gnome-system-monitor - 3.28.2-0ubuntu1 --- gnome-system-monitor (3.28.2-0ubuntu1) bionic; urgency=medium * New upstream release (LP: #1770971) -- Jeremy Bicha Sun, 13 May 2018 11:20:50 -0400 ** Changed in: gnome-system-monitor (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1770971 Title: Update gnome-system-monitor to 3.28.2 Status in gnome-system-monitor package in Ubuntu: Fix Released Status in gnome-system-monitor source package in Bionic: Fix Released Bug description: Impact -- 3.28.2 is the latest bugfix release in the stable 3.28 series. https://git.gnome.org/browse/gnome-system-monitor/tree/NEWS https://git.gnome.org/browse/gnome-system-monitor/log Test Case - We can test the bugfix: 1. Ubuntu 18.04 LTS uses the snap version of gnome-system-monitor for new installs. To ensure, we're testing the right version, run sudo apt install gnome-system-monitor 2. Install chromium-browser (apt or snap is fine). 3. Run chromium-browser. 4. Run gnome-system-monitor from the command line (to avoid picking the snap version if you have that installed) 5. In the list select "chromium-browser --type=renderer" 6. Click End Process The end process dialog should display "Are you sure you want to end the selected process "chromium-browser" With 3.28.1, it instead displayed a very large dialog with the entire command line argument between those quotation marks. Feel free to uninstall chromium-browser or gnome-system-monitor afterwards. Regression Potential - The GNOME stack has an SRU Micro-release exception https://wiki.ubuntu.com/StableReleaseUpdates#GNOME This is a very minor change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1770971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770971] Update Released
The verification of the Stable Release Update for gnome-system-monitor has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1770971 Title: Update gnome-system-monitor to 3.28.2 Status in gnome-system-monitor package in Ubuntu: Fix Released Status in gnome-system-monitor source package in Bionic: Fix Released Bug description: Impact -- 3.28.2 is the latest bugfix release in the stable 3.28 series. https://git.gnome.org/browse/gnome-system-monitor/tree/NEWS https://git.gnome.org/browse/gnome-system-monitor/log Test Case - We can test the bugfix: 1. Ubuntu 18.04 LTS uses the snap version of gnome-system-monitor for new installs. To ensure, we're testing the right version, run sudo apt install gnome-system-monitor 2. Install chromium-browser (apt or snap is fine). 3. Run chromium-browser. 4. Run gnome-system-monitor from the command line (to avoid picking the snap version if you have that installed) 5. In the list select "chromium-browser --type=renderer" 6. Click End Process The end process dialog should display "Are you sure you want to end the selected process "chromium-browser" With 3.28.1, it instead displayed a very large dialog with the entire command line argument between those quotation marks. Feel free to uninstall chromium-browser or gnome-system-monitor afterwards. Regression Potential - The GNOME stack has an SRU Micro-release exception https://wiki.ubuntu.com/StableReleaseUpdates#GNOME This is a very minor change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1770971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04
Thomas Diesenreiter, the next step is to fully commit bisect from 4.13.4 to 4.15.17, in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully commit bisecting. Also, the kernel release names are irrelevant for the purposes of bisecting. It is most helpful that after the bad commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed. Thank you for your help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771204 Title: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04 Status in xorg package in Ubuntu: Incomplete Bug description: My laptop was running fine for years, but after the latest update to 18.04 and the reboot there were horizontal lines everywhere. It seems like its a regression of an older bug, because its the same bug with the same strange behaviour as listed here: https://bugs.freedesktop.org/show_bug.cgi?id=64332 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon May 14 22:31:29 2018 DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0f9] InstallationDate: Installed on 2013-11-21 (1635 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago) dmi.bios.date: 04/26/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P00ACX dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X3F-K01DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 900X3F dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 Apr 22 16:22:53 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1495 vendor BOE xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774081] [NEW] /etc/gdm3/Init/Default not evaluated
Public bug reported: /etc/gdm3/Init/Default is not evaluated on my fresh install of Ubuntu 18.04 (minimal). I replaced this file by one with the following content to test it: #!/bin/sh touch /tmp/a touch /mnt/a After a reboot, these files are not available. When I use the same file for /etc/gdm3/PostLogin/Default, it works. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/1774081 Title: /etc/gdm3/Init/Default not evaluated Status in gdm3 package in Ubuntu: New Bug description: /etc/gdm3/Init/Default is not evaluated on my fresh install of Ubuntu 18.04 (minimal). I replaced this file by one with the following content to test it: #!/bin/sh touch /tmp/a touch /mnt/a After a reboot, these files are not available. When I use the same file for /etc/gdm3/PostLogin/Default, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Hi I tested gdm3 - 3.28.2-0ubuntu1.1 on Ubuntu 18.04 LTS. I ran the following tests: a) Boot Ubuntu 18.04 LTS, attempt login with correct password - pass. b) Log out and then log back in with correct password - pass. c) Log out and then enter the wrong password a few times then enter the correct password press enter to login - pass. d) Reboot Ubuntu 18.04 LTS, enter the wrong password a few times then enter the correct password, press enter to login - pass. e) Login then allow the screen to blank, attempt unlock with correct password - pass. f) Login then allow the screen to blank, attempt unlock with wrong password then enter correct password and press enter - pass. g) Click on the lock button, attempt unlock with incorrect password a few times then enter correct password and press enter - pass. h) Click on the lock button, attempt unlock with correct password - pass. Fix therefore works now and appears to have no issues so far. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04
** Tags removed: kernel-bug-exists-upstream-4.17.0-041700rc6-generic ** Tags added: kernel-bug-exists-upstream-4.17-rc6 ** Tags removed: kernel-bug-exists-upstream ** Tags added: needs-upstream-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771204 Title: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04 Status in xorg package in Ubuntu: Incomplete Bug description: My laptop was running fine for years, but after the latest update to 18.04 and the reboot there were horizontal lines everywhere. It seems like its a regression of an older bug, because its the same bug with the same strange behaviour as listed here: https://bugs.freedesktop.org/show_bug.cgi?id=64332 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon May 14 22:31:29 2018 DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0f9] InstallationDate: Installed on 2013-11-21 (1635 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago) dmi.bios.date: 04/26/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P00ACX dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X3F-K01DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 900X3F dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 Apr 22 16:22:53 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1495 vendor BOE xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu
I am on 4.15.0.22 using Nvidia 980. I initially encountered the same bug. But after upgrading to NVIDIA 390.59, I was able to boot up normally. -- 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/1764005 Title: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu Status in nvidia-prime package in Ubuntu: Fix Released Bug description: Upgraded from Ubuntu Budgie 17.10 to 18.04. After the plymouth splash left with a black screen. Purged all the nivdia-* packages and rebooted - graphical logon and logged in ok with nouveau. Tried software & updates to reinstall the nvidia 390 drivers. Rebooted. Left at black screen again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.48-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sat Apr 14 21:42:04 2018 InstallationDate: Installed on 2016-11-26 (503 days ago) InstallationMedia: budgie-remix 16.10 "Budgie-remix" - amd64 (20161013) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1764005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
No. sudo scanimage -L gives the same result. It does not detect the scanner. However schroot with chroot of Ubuntu 16.04 detects it correctly. See below. peter@andromeda:~$ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). peter@andromeda:~$ sudo scanimage -L [sudo] password for peter: No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). peter@andromeda:~$ schroot -c chroot:xenial (xenial)peter@andromeda:~$ scanimage -L device `brother4:net1;dev0' is a Brother Brother_DCP7065DN DCP-7065DN (xenial)peter@andromeda:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04
Tested it with 4.17.0-041700rc6-generic, the bug still exists. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.17.0-041700rc6-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771204 Title: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04 Status in xorg package in Ubuntu: Incomplete Bug description: My laptop was running fine for years, but after the latest update to 18.04 and the reboot there were horizontal lines everywhere. It seems like its a regression of an older bug, because its the same bug with the same strange behaviour as listed here: https://bugs.freedesktop.org/show_bug.cgi?id=64332 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon May 14 22:31:29 2018 DistUpgraded: 2018-05-11 10:45:03,937 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.13.0-41-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0f9] InstallationDate: Installed on 2013-11-21 (1635 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3F ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--gnome--vg-root ro vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-05-11 (3 days ago) dmi.bios.date: 04/26/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P00ACX dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP900X3F-K01DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP00ACX:bd04/26/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3F:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3F-K01DE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 900X3F dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.92+git1805100630.cb592a~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805140730.ff7521~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805140730.ff7521~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 Apr 22 16:22:53 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1495 vendor BOE xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755490] Re: Incorrect information about display shown in unity-control-center
In case it helps, I've seen comments regarding some TVs encoding the aspect ratio (16/9 or 16/10) as though it was the size: https://github.com/linuxmint/slick-greeter/blob/master/files/usr/bin /slick-greeter-check-hidpi#L24-L29 Not sure what is the actual source of this information, though. -- 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/1755490 Title: Incorrect information about display shown in unity-control-center Status in hwdata package in Ubuntu: In Progress Status in unity-settings-daemon package in Ubuntu: In Progress Bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773597] Re: USB flash drive won't mount
Booted a tower machine (it had been powered off) running Ubuntu 17.10 (Artful). Ran SW updates. Rebooted. Inserted encrypted USB flash drive. Was asked several times for the password. Gave it - multiple times. Finally I was able to open drive. That lasted about 10 minutes when all the files in the window disappeared (folder is empty message). Pulled the flash drive and reinserted it. This time it worked. Request for password showed up in its black window. I entered the password (twice - I might have screwed it up). Was able to access files with no problems. -- 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/1773597 Title: USB flash drive won't mount Status in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=870f1d77-345c-44b2-99e6-79adea07159c ro quiet splash vt.handoff=1 Ubuntu version: Ubuntu 18.04 LTS, software is up to date Steps to create problem: 1. Reboot 2. Insert USB flash drive USB flash drive does not appear on desktop or in Nautilus file window dmesg | tail [ 1435.463032] usb 2-1.3: new high-speed USB device number 8 using ehci-pci [ 1435.685760] usb 2-1.3: New USB device found, idVendor=05dc, idProduct=c75c [ 1435.685763] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1435.685765] usb 2-1.3: Product: USB Flash Drive [ 1435.685766] usb 2-1.3: Manufacturer: Lexar [ 1435.685767] usb 2-1.3: SerialNumber: D2036779FCE9EDC016EF lsusb Bus 002 Device 007: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card Bus 002 Device 006: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 002 Device 005: ID 413c:8157 Dell Computer Corp. Integrated Keyboard Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 002 Device 008: ID 05dc:c75c Lexar Media, Inc. Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:640f Microdia Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1773597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Ah, thanks for saying that since I was testing in my other machine and wasn't unable to reproduce this anymore... My second user has no password set, but there's no much difference in terms of the issue. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Sorry I commented too quickly below after first tryout. After couple of boots and tryouts it did finally succeed after longer wait time and now after testing some 5 times I have managed to log with different user after loging out. it is slow, but it will get there. So certainly I see good progress, looks better now. ti 29. toukok. 2018 klo 22.47 Heikki Moisander (moisan...@gmail.com) kirjoitti: > heikki@ThinkPad-X301:~$ apt-cache policy gdm3 > gdm3: > Asennettu: 3.28.2-0ubuntu1.1 > Ehdokas: 3.28.2-0ubuntu1.1 > Versiotaulukko: > *** 3.28.2-0ubuntu1.1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main > amd64 Packages > 100 /var/lib/dpkg/status > 3.28.0-0ubuntu1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > I seem to have fixed version now. It does not work for me any different > from the previous version. Nothing happens while trying to change user or > log in with different user account. After trying I can get back to login > screen but then only way to login is boot. > > ti 29. toukok. 2018 klo 17.31 Łukasz Zemczak (1766...@bugs.launchpad.net) > kirjoitti: > >> Hello Chris, or anyone else affected, >> >> Accepted gdm3 into bionic-proposed. The package will build now and be >> available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 >> in a few hours, and then in the -proposed repository. >> >> Please help us by testing this new package. See >> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how >> to enable and use -proposed.Your feedback will aid us getting this >> update out to other Ubuntu users. >> >> If this package fixes the bug for you, please add a comment to this bug, >> mentioning the version of the package you tested and change the tag from >> verification-needed-bionic to verification-done-bionic. If it does not >> fix the bug for you, please add a comment stating that, and change the >> tag to verification-failed-bionic. In either case, without details of >> your testing we will not be able to proceed. >> >> Further information regarding the verification process can be found at >> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in >> advance! >> >> ** Changed in: gdm3 (Ubuntu Bionic) >>Status: In Progress => Fix Committed >> >> ** Tags removed: verification-failed-bionic >> ** Tags added: verification-needed-bionic >> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1768619). >> https://bugs.launchpad.net/bugs/1766137 >> >> Title: >> [regression] Password accepted but login fails (blank purple screen >> and mouse pointer only) >> >> Status in gdm: >> Fix Released >> Status in Release Notes for Ubuntu: >> Fix Released >> Status in gdm3 package in Ubuntu: >> In Progress >> Status in gnome-shell package in Ubuntu: >> Invalid >> Status in gdm3 source package in Bionic: >> Fix Committed >> Status in gnome-shell source package in Bionic: >> Invalid >> >> Bug description: >> [ Description ] >> >> Due to a refcounting bug, a GDBusConnection was getting disposed when >> it was still required. The symptom of this was that you couldn't log >> in on the second attempt if you'd got your password wrong on the first >> attempt. All you'd see is a blank purple screen and mouse pointer >> only. >> >> [ Test case ] >> >> 1. Boot to GDM >> 2. Click your username >> 3. Type the wrong password a couple of times, pressing enter after each >> time >> 4. Type the right password >> >> If the bug is happening, after 4. the system hangs at a blank screen >> with the mouse cursor. If you then switch to a VT or otherwise connect >> to the machine, you can examine the journal and you'll see a >> G_IS_DBUS_CONNECTION failure. >> >> [ Fix ] >> >> Marco and I worked upstream on this fix. We found out that there was a >> problem like this- >> >> The GdmClient has a shared GDBusConnection for its operations. The >> first time someone calls for it, it is created and stored in the >> object's private structure. Subsequent calls return *a new reference* >> to this same object. It turned out that the asynchronous method to get >> the connection was accidentally unreferencing its object before giving >> it to the caller if it was returning an already-existing connection. >> >> For this to work properly, we need to nullify the pointer we stored >> when the connection goes away, so we know when to make a new one. >> There were some cases where we didn't add the weak references required >> to do that. Those are also fixed. >> >> [ Regression potential ] >> >> Now we share connections more than we did before. We also more >> carefully track when to clear our object. If we got this wrong, we >> might end up leaking the connection or dropping it in even more cases. >> >> [ Original report ] >> >> WORKAROUND: After typing an incorrect password, click Ca
[Desktop-packages] [Bug 909022] Re: Various akonadi processes use 100% CPU and 200% RAM at every KDE session startup
Don't know whetherit is the same reason as back in 2011, but there's still a major performance impact of mysqld/akonadiserver in Kubuntu 18.04 (akonadiserver 5.7.3). mysqld takes 25% and akonadiserver 20% CPU permanently. I did the delete (.local/share/akonadi and .config/akonadi) a few months ago (on 16.10), but a few days later the issue has been back again. I have 12 imap ressources configured, but told them to just sync from twice a day up to 4x/day, so this can't be the reason. Strange feeling to just browse the web (not even having kmail open) with cooler sounds like playing a HQ game... :-/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/909022 Title: Various akonadi processes use 100% CPU and 200% RAM at every KDE session startup Status in Akonadi: Incomplete Status in akonadi package in Ubuntu: Invalid Bug description: On every KDE session startup, a bunch of akonadi-related processes are started. These start hogging the system CPU and RAM shortly after startup, and quickly tie up 100% CPU and 200% RAM (i.e. they use up almost 8G physical RAM and start chewing on swap as well!) In order not to have my 2-core 8G RAM machine completely bogged down by these processes, I have to kill the processes manually, else my session becomes unusable and I have to reset the machine. Ubuntu: up-to-date 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/909022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769981] Re: Temporary screen freeze when coming back from screen standby
I just had a series of freezes, and managed to ssh and watch logs in the meantime, the only messages that I that might be relevant are the following (repeated many times): May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_map: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed May 29 22:02:34 kashyyyk gnome-shell[3295]: _shell_embedded_window_unmap: assertion 'SHELL_IS_EMBEDDED_WINDOW (window)' failed ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769981 Title: Temporary screen freeze when coming back from screen standby Status in gnome-shell package in Ubuntu: Confirmed Bug description: When waking up the PC screen from standby, quite often the screen freezes for 10-20s. I can't move the mouse or type anything. After a while, it unfreezes. This is quite annoying because often the freeze is long enough to send the screen to standby again for absence of singal, so then I have to wake it up and wait again. This is not 100% reproducible but happens very frequently, both when the screen is locked and when it's not. 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 CurrentDesktop: GNOME Date: Tue May 8 20:26:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-25 (72 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) 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/1769981/+subscriptions -- Mailing list: https://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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
heikki@ThinkPad-X301:~$ apt-cache policy gdm3 gdm3: Asennettu: 3.28.2-0ubuntu1.1 Ehdokas: 3.28.2-0ubuntu1.1 Versiotaulukko: *** 3.28.2-0ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages I seem to have fixed version now. It does not work for me any different from the previous version. Nothing happens while trying to change user or log in with different user account. After trying I can get back to login screen but then only way to login is boot. ti 29. toukok. 2018 klo 17.31 Łukasz Zemczak (1766...@bugs.launchpad.net) kirjoitti: > Hello Chris, or anyone else affected, > > Accepted gdm3 into bionic-proposed. The package will build now and be > available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 > in a few hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed.Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested and change the tag from > verification-needed-bionic to verification-done-bionic. If it does not > fix the bug for you, please add a comment stating that, and change the > tag to verification-failed-bionic. In either case, without details of > your testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance! > > ** Changed in: gdm3 (Ubuntu Bionic) >Status: In Progress => Fix Committed > > ** Tags removed: verification-failed-bionic > ** Tags added: verification-needed-bionic > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > In Progress > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > Fix Committed > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing an incorrect password, click Cancel, then > click your name, then enter your password again. > > --- > > Trying to log into my session (Gnome, Xorg), if I enter the wrong > password before entering it correctly, the session doesn't load and I > get a purple screen, a mouse cursor, and an invisible but clickable > menu in the top right. If I enter it correctly the first time, there > is no problem. > > I've replicated this from a fresh boot, after logging out and after > 'sudo service gdm restart' from the Ctrl-Alt-F4 console. > > This is a
[Desktop-packages] [Bug 1774053] [NEW] Missing characters in and after lock screen
Public bug reported: I locked my screen, came back from lunch, and found that about half the characters in the lock screen were missing. After I logged back in, half the characters in the desktop were missing (https://drive.google.com/file/d/1mIDF4_jY0PIFOT53FoOOVoTY1BWeaNfy/view?usp=sharing). Chrome and Nautilus are not missing any characters, just the system UI. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 12:25:58 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-04-10 (48 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot of the start menu" https://bugs.launchpad.net/bugs/1774053/+attachment/5146135/+files/Screenshot%20from%202018-05-29%2012-20-44.png -- 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/1774053 Title: Missing characters in and after lock screen Status in gnome-shell package in Ubuntu: New Bug description: I locked my screen, came back from lunch, and found that about half the characters in the lock screen were missing. After I logged back in, half the characters in the desktop were missing (https://drive.google.com/file/d/1mIDF4_jY0PIFOT53FoOOVoTY1BWeaNfy/view?usp=sharing). Chrome and Nautilus are not missing any characters, just the system UI. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 12:25:58 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-04-10 (48 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=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/1774053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774051] [NEW] wrong screen resolution (640x480) with Nouveau driver
Public bug reported: I use ubuntu 18.04 on Toshiba notebook with Nvidia card. When i use Nouveau Driver the screen resolution is set to very low value: 640 x 480 (4:3) and is not possible to change it. If i use NVidia property driver the resolution is set correctly. I attach files with the output of commands: lspci, uname -a, cpuinfo, lshw Thanks ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau 1:1.0.15-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una 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.106 Tue Jan 9 15:10:23 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 29 21:11:49 2018 DistUpgraded: 2018-05-20 00:53:03,968 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.106, 4.15.0-22-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT218M [NVS 2100M] [10de:0a6a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems GT218M [NVS 2100M] [1179:0001] MachineType: TOSHIBA TECRA S11 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=efdf25e3-36ae-4c91-a9f9-142e25478afe ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) dmi.bios.date: 10/23/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.50 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.50:bd10/23/2012:svnTOSHIBA:pnTECRAS11:pvrPTSE3E-01N01CIT:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: TECRA S11 dmi.product.version: PTSE3E-01N01CIT dmi.sys.vendor: TOSHIBA 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.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 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: Tue May 29 21:01:04 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "command_output.zip" https://bugs.launchpad.net/bugs/1774051/+attachment/5146115/+files/command_output.zip ** Description changed: I use ubuntu 18.04 on Toshiba notebook with Nvidia card. - When i use Nouveau Driver the screen resolution is set to 640 x 480 (4:3) and is not possible to change it. + When i use Nouveau Driver the screen resolution is set to very low value: 640 x 480 (4:3) and is not possible to change it. If i use NVidia property driver the resolution is set correctly. I attach files with the output of commands: lspci, uname -a, cpuinfo, lshw ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-nouveau 1:1.0.15-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una 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.106
[Desktop-packages] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor
*** This bug is a duplicate of bug 1760849 *** https://bugs.launchpad.net/bugs/1760849 ** Description changed: - I'm running bionic on a Lenovo X230 laptop. - It works fine to boot it with either my hdmi monitor or my VGA monitor. - It also works to attach the VGA monitor after booting and logging in with the HTMI monitor. + If I boot up with two external monitors connected, the login screen + doesn't show up on any monitor. - But if both are connected while I boot, the graphical login prompt never - appears, and just the mouse appears in the laptop window on a blue - screen, with the HDMI monitor showing a blank blue screen, and the VGA - monitor getting no signal. + The laptop display shows the mouse cursor on a blue screen, the HDMI + monitor shows a blank blue screen, and the VGA monitor shows no signal. - This monitor configuration worked fine with this computer in Trusty. + WORKAROUND: Use Trusty. - I ran apport-bug to report the problem, and chose the first option: - "Display (X.org)". I'm not positive what I'm running, but note that - after booting and getting both monitors plugged in and running after - login, I see both an Xwayland process and an Xorg process. I suggest - also changing apport-bug to appropriately reflect that wayland is - somehow involved, and I hope that the included debug info will include - any appropriate wayland info. I note that it does seem to be possible - to get some info via `apport-bug xwayland`. + WORKAROUND: Boot with only one external monitor connected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Mon May 28 11:40:58 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2018-05-01 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 343522U ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GCETA1WW (2.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Changed in: xorg (Ubuntu) Status: Incomplete => New ** This bug has been marked a duplicate of bug 1760849 Enhancement: Make the login screen follow the mouse to other monitors -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773850 Title: No login prompt when booting bionic with both hdmi and vga monitor Status in xorg package in Ubuntu: New Bug description: If I boot up with two external monitors connec
[Desktop-packages] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor
*** This bug is a duplicate of bug 1760849 *** https://bugs.launchpad.net/bugs/1760849 Neal McBurnett: 1) Regarding your crash files, please execute the following via a terminal to have them automatically processed: ubuntu-bug /var/crash/FILENAME.crash where FILENAME is the file name of the crash file to report. The upload is successful when the file with extension .uploaded is subsequently created. 2) With regard to this report, you have at least two to three bugs here. One for each of the distinct crash files you noted, which reporting them will help to see them resolved. The third is along the lines of your Title+Bug Description: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1760849 >From my cursory viewpoint, the crashes appear to be unrelated to the login issue reported. Hence, for now, let this be marked a duplicate of LP#1760849. However, if after it is resolved your issue is still present, this report may always be unduplicated, and resumed from there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773850 Title: No login prompt when booting bionic with both hdmi and vga monitor Status in xorg package in Ubuntu: New Bug description: If I boot up with two external monitors connected, the login screen doesn't show up on any monitor. The laptop display shows the mouse cursor on a blue screen, the HDMI monitor shows a blank blue screen, and the VGA monitor shows no signal. WORKAROUND: Use Trusty. WORKAROUND: Boot with only one external monitor connected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Mon May 28 11:40:58 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2018-05-01 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 343522U ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GCETA1WW (2.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774047] [NEW] gnome (or something) uses a lot of memory
Public bug reported: After I log in (ubuntu session) the systen(?), shell(?) uses a lot of memory. When the computer has 2GB RAM, 1.2GB is used. When the computer has 4GB RAM, 1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried it out in virtualbox with a newly installed system. I changed the memory size and started ubuntu. I think a new, clean system should use the same amount of memory independently of the RAM size. Not to mention that the system is unusable, because RAM quickly fills up (memory leak?) and become laggy. Unity in 16.04 uses approx. 800kB memory. Why does gnome-shell need so much memory? I think it should be fixed, because 18.04 is an LTS release! I would like to work with it.Description:Ubuntu 18.04 LTS Release:18.04 gnome-shell: Telepítve: 3.28.1-0ubuntu2 Jelölt:3.28.1-0ubuntu2 Verziótáblázat: *** 3.28.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 20:21:39 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (221 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (44 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774047 Title: gnome (or something) uses a lot of memory Status in gnome-shell package in Ubuntu: New Bug description: After I log in (ubuntu session) the systen(?), shell(?) uses a lot of memory. When the computer has 2GB RAM, 1.2GB is used. When the computer has 4GB RAM, 1.7GB is used. When the computer has 8GB RAM, 2.2GB is used. I tried it out in virtualbox with a newly installed system. I changed the memory size and started ubuntu. I think a new, clean system should use the same amount of memory independently of the RAM size. Not to mention that the system is unusable, because RAM quickly fills up (memory leak?) and become laggy. Unity in 16.04 uses approx. 800kB memory. Why does gnome-shell need so much memory? I think it should be fixed, because 18.04 is an LTS release! I would like to work with it.Description: Ubuntu 18.04 LTS Release: 18.04 gnome-shell: Telepítve: 3.28.1-0ubuntu2 Jelölt:3.28.1-0ubuntu2 Verziótáblázat: *** 3.28.1-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 20:21:39 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-20 (221 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
** Changed in: mutter (Fedora) Status: Confirmed => 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Won't Fix Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762984] Re: DNS resolving not working due to wrong entry in resolv.conf
Fixed - The symlink of resolv.conf was wrong. The following shows how - resolv.conf-BAK was the old, broken one, resolv.conf the one I fixed. I don't know how that happened, but I have installed the 18.04 beta version, may that was the reason. lrwxrwxrwx 1 root root 32 Mai 29 10:55 resolv.conf -> /run/systemd/resolve/resolv.conf lrwxrwxrwx 1 root root 39 Apr 9 12:26 resolv.conf-BAK -> ../run/systemd/resolve/stub-resolv.conf ** Changed in: network-manager (Ubuntu) Status: New => Fix Committed -- 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/1762984 Title: DNS resolving not working due to wrong entry in resolv.conf Status in network-manager package in Ubuntu: Fix Committed Bug description: In my ``/etc/resolv.conf`` I have the entry: ``` nameserver 127.0.0.53 ``` I'm connected to the network via WIFI. My IP is ``192.168.0.31`` The network-manager applet shows me automatic DNS configuration and a DNS server of 192.0.0.1, which is correct. Changing DNS configuration in the network-manager applet to manual and editing it there doesn't work either. I have to edit the resolv.conf file in order to get DNS resolving work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 11:51:58 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-09 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.31 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NSACIAGCHQ5 f8431fbb-6f3c-4848-bcc4-4449012df3f7 wifi 1523440039 Mi 11 Apr 2018 11:47:19 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlp1s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- welanseppaf2f9fd1-2a81-4e2c-95e5-3f4e9a9997b9 wifi 1523402504 Mi 11 Apr 2018 01:21:44 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 NSACIAGCHQ5 f8431fbb-6f3c-4848-bcc4-4449012df3f7 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1762984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1239129. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-07-03T16:05:10+00:00 Ian wrote: 1. Install xterm 2. Write a file at /etc/X11/xorg.conf.d/20-bit16.conf containing: Section "Screen" Identifier "Screen0" DefaultDepth 16 EndSection 3. Log in with GNOME desktop 4. Go to Activities, type 'xt' and see the xterm icon appear 5. Click on the xterm icon 6. Boom This was originally encountered by installing tigervnc-server-module which comes with a config file specifying DefaultDepth 16 but clearly the vnc server itself is not required. gnome-shell outputs the following message before crashing: mutter:ERROR:x11/iconcache.c:301:standard_pict_format_for_depth: code should not be reached Analysis of this function shows that it doesn't believe that 16-bit pixmaps exist. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/0 On 2016-07-19T15:11:16+00:00 Fedora wrote: Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/1 On 2016-07-19T16:16:09+00:00 Ian wrote: Still crashes on Fedora 24 with the same error message and traceback. $ rpm -q mutter mutter-3.20.3-1.fc24.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/2 On 2017-07-25T18:58:48+00:00 Fedora wrote: This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/3 On 2017-08-03T17:28:59+00:00 Ian wrote: Still crashes mutter-3.24.4-1.fc26.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1766938/comments/4 On 2018-05-03T08:49:05+00:00 Fedora wrote: This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible d
[Desktop-packages] [Bug 1714459]
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Won't Fix Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714459]
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Won't Fix Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.
Mike L: 1) Regarding your comment: >"removing and reinserting the transciever fixes it until you reboot into >Windows 10 again." To clarify, you personally tested with your hardware that after removing and reinserting, you can reboot Ubuntu as many times as you want and this will never happen. However, if you reboot into Windows, then reboot back into Ubuntu, the problem will occur again? 2) Going forward, it is most helpful you advise to what you have personally tested with the hardware in your possession, versus cite what someone else speculates, said they did, what you think might occur but didn't confirm yourself, etc. ** Summary changed: - Microsoft Mice on dual boot systems can scroll multiple lines at a time. + [Microsoft Sculpt Ergonomic Mouse] on dual boot systems can scroll multiple lines at a time. ** Description changed: - Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who - knows how long. See https://askubuntu.com/questions/47100/mouse-wheel- - scrolling-too-fast. Installing the workaround package or removing the - transceiver appears to be a workaround for the time being. Xorg should - automatically scroll normally, not multiple lines at time after - rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions - the bug dating back to Natty. + In 16.04 and 18.04, the mouse scrolls multiple lines at time. Sometimes + rebooting doesn't fix the issue. This problem doesn't happen in Windows + 10. + + WORKAROUND: https://sourceforge.net/projects/resetmsmice/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 - GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 + GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 19 13:02:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] -Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] + Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: HP HP ENVY m7 Notebook ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: HP dmi.board.version: 64.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m7 Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git201712
[Desktop-packages] [Bug 1774039] [NEW] package gdm3 3.28.2-0ubuntu1.1 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
Public bug reported: Could not install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.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 Architecture: amd64 Date: Tue May 29 23:33:46 2018 ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-05-05 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gdm3 Title: package gdm3 3.28.2-0ubuntu1.1 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-from-proposed third-party-packages -- 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/1774039 Title: package gdm3 3.28.2-0ubuntu1.1 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 Status in gdm3 package in Ubuntu: New Bug description: Could not install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.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 Architecture: amd64 Date: Tue May 29 23:33:46 2018 ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-05-05 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gdm3 Title: package gdm3 3.28.2-0ubuntu1.1 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.
** Tags added: latest-bios-f.49 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772183 Title: Microsoft Mice on dual boot systems can scroll multiple lines at a time. Status in xorg package in Ubuntu: Incomplete Bug description: Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who knows how long. See https://askubuntu.com/questions/47100/mouse-wheel- scrolling-too-fast. Installing the workaround package or removing the transceiver appears to be a workaround for the time being. Xorg should automatically scroll normally, not multiple lines at time after rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions the bug dating back to Natty. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 19 13:02:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: HP HP ENVY m7 Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: HP dmi.board.version: 64.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m7 Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773612] Re: I am just loading the OS onto my computer
Gary De Maroney, thank you for reporting this and helping make Ubuntu better. 1) Is this something that started to happen after an update? If so, which and when precisely? 2) Do you have any actual issues uing the OS? 3) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Tags added: latest-bios-a11 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773612 Title: I am just loading the OS onto my computer Status in xorg package in Ubuntu: Incomplete Bug description: I am not sure yet on all this ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 26 19:42:37 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. NV44 [GeForce 6200 TurboCache] [1043:81d5] InstallationDate: Installed on 2018-05-27 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) MachineType: Dell Inc. OptiPlex GX620 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=12a1802d-2e8f-4134-abe3-6ced79d9f318 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8098 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8098:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773744] Re: Desktop session crash
Sami Pietila: 1) Regarding the crash files, please report these via executing the following at a terminal: ubuntu-bug _opt_Gitter_linux64_Gitter.1000.crash ubuntu-bug _usr_bin_gnome-shell.1000.crash ubuntu-bug _usr_bin_Xwayland.1000.crash ubuntu-bug _usr_lib_chromium-browser_chromium-browser.1000.crash ubuntu-bug _usr_lib_xorg_Xorg.1000.crash The reporting is successful if files with the extension .uploaded are populated after a few minutes. 2) In regard to gnome-session-flashback, at the login screen you clicked the gear, chose GNOME Flashback (Metacity), logged in, didn't launch any programs, connected the third monitor, and then the desktop crashed? 3) As per the sticker of the monitors (not from the Bug Description, or the result of a terminal command), could you please provide the full manufactuer and model? 4) How are you connecting your computer to the monitors? 5) Are you using any dongles/adapters when connecting to the monitors? 6) To confirm a regression, could you please test http://releases.ubuntu.com/xenial/ubuntu-16.04.4-desktop-amd64.iso and advise to the results? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773744 Title: Desktop session crash Status in xorg package in Ubuntu: Incomplete Bug description: If I connect third monitor to my Ubuntu PC, the whole graphical display session crashes. Additionally, the login does not show texts correctly. The texts are mostly missing. The errors happend with both Wayland and X. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 28 10:15:54 2018 DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e4] Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1002:6771] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X OEM] [103c:90b8] InstallationDate: Installed on 2016-11-22 (551 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago) dmi.bios.date: 09/09/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.18 dmi.board.asset.tag: CZC3427KBP dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3427KBP dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.sys.vendor: Hewlett-Packard 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.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
is there a problem if i run firefox with GTK_IM_MODULE unset? On one of my machines, firefox is unusable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in ibus package in Ubuntu: Confirmed Bug description: tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773744] Re: Desktop session crash
** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773744 Title: Desktop session crash Status in xorg package in Ubuntu: Incomplete Bug description: If I connect third monitor to my Ubuntu PC, the whole graphical display session crashes. Additionally, the login does not show texts correctly. The texts are mostly missing. The errors happend with both Wayland and X. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 28 10:15:54 2018 DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e4] Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1002:6771] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X OEM] [103c:90b8] InstallationDate: Installed on 2016-11-22 (551 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago) dmi.bios.date: 09/09/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.18 dmi.board.asset.tag: CZC3427KBP dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3427KBP dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.sys.vendor: Hewlett-Packard 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.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.
Editing source in audacity to "pulse: Internal Mic 0" works on Ubuntu 18.04 and official audacity packager from their ppa version: 2.2.2-1build1 -- 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/1257956 Title: Headphones stopped working after use of Audacity. They are detected, but no sound is produced. Status in alsa-driver package in Ubuntu: Expired Bug description: I'm running 13.10 and the latest GNOME. I've just fresh installed everything and the problem has occured again the same way. I would like to be able to use audacity, but I suppose in the mean time I will just reinstall everything. Steps to reproduce : 1) Install audacity 2.0.3 from official Ubuntu repositories 2) Open Audacity and play something with it 3) That's it : no more headphones sound. - alsa log created with 'alsa-info.sh' (https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/ - pulse log when I plug in my headphones, I run a MP3 file with VLC, close VLC then unplug headphones (https://wiki.ubuntu.com/PulseAudio/Log) : http://paste.ubuntu.com/7131713/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770176] Re: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange.
Since yesterday's update, it is working now. -- 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/1770176 Title: Ubuntu 18.04 - NetworkManager menu items in top right menu behaves very strange. Status in network-manager package in Ubuntu: Confirmed Bug description: In a fresh Ubuntu 18.04 desktop install, I've found a very strange behaviour on my Dell XPS 15. This laptop doesn't have an integrated Ethernet port, so I've to use external USB 3.0 Ethernet adapters. When I boot Ubuntu with the adapter plugged in, the wired connection section in the top right menu doesn't show the "Via cavo collegato" section (in Italian, sorry... maybe in English it is "Through connected cable") in the correct way, often but not every time... The menu section title is sometimes " collegato" and expanding the section it doesn't list all the defined Ethernet connection profiles I've on my machine. To access all profiles and to change it I've to select the "Wired network settings" item in the section and so the system settings window appears and all defined profiles are there (so I can change connection by clicking here). Another strange behaviour occours with the "VPN" section in the same topright menu. I have two VPN profiles defined (one of Cisco type, the other is of OpenVPN type). If I select one of this two profiles, VPN connection is established but the switch button in the menu doesn't reflect the state of the connection. To see the correct state of the VPN connection I've to open the "system settings" window, again. It seems there is some trouble in the topright menu communication with the NetworkManager subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1770176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
@Peter Bennett, Let me make sure I'm following. scanimage -L doesn't find the scanner, but sudo scanimage -L does? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773762] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
*** This bug is a duplicate of bug 1773820 *** https://bugs.launchpad.net/bugs/1773820 ** This bug has been marked a duplicate of bug 1773820 package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1 ** Information type changed from Private Security to Public -- 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/1773762 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Can not to intall ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-lowlatency 4.15.17 Uname: Linux 4.15.0-22-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon May 28 03:28:06 2018 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1 InstallationDate: Installed on 2018-05-25 (2 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1 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/1773762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773820] Re: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете nvidia-kernel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- 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/1773820 Title: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: romanshevelev@HOME-PC2:~$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 romanshevelev@HOME-PC2:~$ apt-cache policy nvidia-340 nvidia-340: Установлен: 340.106-0ubuntu3 Кандидат: 340.106-0ubuntu3 Таблица версий: *** 340.106-0ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 340.106-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun May 27 21:30:51 2018 ErrorMessage: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете nvidia-kernel-common-390 390.59-0ubuntu0~gpu18.04.1 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/1773820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773612] Re: I am just loading the OS onto my computer
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773612 Title: I am just loading the OS onto my computer Status in xorg package in Ubuntu: New Bug description: I am not sure yet on all this ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 26 19:42:37 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. NV44 [GeForce 6200 TurboCache] [1043:81d5] InstallationDate: Installed on 2018-05-27 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228) MachineType: Dell Inc. OptiPlex GX620 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=12a1802d-2e8f-4134-abe3-6ced79d9f318 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F8098 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8098:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex GX620 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774007] [NEW] /usr/bin/gnome-software:11:magazine_chain_pop_head:magazine_chain_prepare_fields:magazine_cache_push_magazine:private_thread_memory_cleanup:__nptl_deallocate_tsd
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.28.1-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/80db1ab810dc5348d8a286fdf246c5c7c0dc79dd 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-software (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic xenial yakkety zesty -- 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/1774007 Title: /usr/bin/gnome- software:11:magazine_chain_pop_head:magazine_chain_prepare_fields:magazine_cache_push_magazine:private_thread_memory_cleanup:__nptl_deallocate_tsd Status in gnome-software package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.28.1-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/80db1ab810dc5348d8a286fdf246c5c7c0dc79dd 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-software/+bug/1774007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754400] Re: "General input/output error" when attempting to save a document to google drive
(maybe) relevant bug: https://bugs.documentfoundation.org/show_bug.cgi?id=101630 -- 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/1754400 Title: "General input/output error" when attempting to save a document to google drive Status in libreoffice package in Ubuntu: Confirmed Bug description: (bug initially reported upstream, but apparently only affects ubuntu: https://bugs.documentfoundation.org/show_bug.cgi?id=97898) Steps to reproduce: - start a document in libreoffice writer - menu File > Save Remote… - use the "Add Service" button to configure an existing google account (not one using 2FA, that's not implemented yet) Expected result: the document is saved on your google drive Current result: an error dialog box that reads: "Error saving the document Untitled 1: General input/output error." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 17:22:50 2018 InstallationDate: Installed on 2018-02-08 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) 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/1754400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer&system details to help improving Ubuntu
This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.2 --- ubuntu-release-upgrader (1:18.10.2) cosmic; urgency=medium * Add upgrade telemetry information (LP: #1755456) * Updated translations -- Didier Roche Tue, 29 May 2018 15:15:45 +0200 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1755456 Title: [ffe] Optional recording/sending of installer&system details to help improving Ubuntu Status in gnome-initial-setup package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Triaged Bug description: [Rationale] We added telemetry data for people installing ubuntu from ubiquity. We didn't get the time to do the same on upgrade despite the FFe acking it. It was decided it was better to first polish the installation and report experience, and then, tackling the upgrade for .1, where most LTS users will migrate from. ubuntu-release-upgrade just drop a telemetry file (like ubiquity is dropping one) which is then picked up by ubuntu-report for user's review and approval before sending. Note that ubuntu-report is already aware of the upgrade telemetry and just ignores it when it's missing it (case of install of ugprade without this ubuntu-release-upgrade versinon) [Impact] * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is dropping one) which is then picked up by ubuntu-report for user's review and approval before sending. * Note that ubuntu-report is already aware of the upgrade telemetry and just ignores it when it's missing it (case of install of ugprade without this ubuntu-release-upgrade versinon) * The ubuntu-release-upgrade only drops a file thus. The logic is really similar to the one included in ubiquity for 18.04. The telemetry class is similar. * The telemetry is reported by all existing UI. * What we send is: - From (distro we ugprade from) - Type of installer (GTK, KDE, non interactive, text…) - If third party ressources were used (but not the list of those external repos) - Original installation media - Stages of installation indexed by their relative time duration [Test Case] * Install ubuntu-release-upgrade on an artful machine * Run an upgrade from artful to bionic * Check that once the upgrade finished, there is a /var/log/ugprade/telemetry file present on disk. [Regression Potential] * The code is similar to ubiquity ones, and the impact is only dropping a file on disk. * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, GTK3 and KDE frontends. --- The topic has been discussed on the ubuntu-devel@ list, see https://lists.ubuntu.com/archives/ubuntu- devel/2018-February/040139.html The feature has different parts - the installer is going to record some informations about the installation details & options selected - the session is going to have a command line/GUI part that let user review&send those informations - the desktop settings should have a control to change the option later on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1755456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754400] Re: "General input/output error" when attempting to save a document to google drive
After allowing less secure apps in my google account security settings (https://myaccount.google.com/security#connectedapps), I was able to save a writer document on my google drive by only providing e-mail address and password. However I tested with another account with 2FA enabled, and I'm still getting the prompt to enter a 6-digit PIN code, but I'm not receiving any code via SMS on my phone as I would expect. ** Bug watch added: Document Foundation Bugzilla #101630 https://bugs.documentfoundation.org/show_bug.cgi?id=101630 -- 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/1754400 Title: "General input/output error" when attempting to save a document to google drive Status in libreoffice package in Ubuntu: Confirmed Bug description: (bug initially reported upstream, but apparently only affects ubuntu: https://bugs.documentfoundation.org/show_bug.cgi?id=97898) Steps to reproduce: - start a document in libreoffice writer - menu File > Save Remote… - use the "Add Service" button to configure an existing google account (not one using 2FA, that's not implemented yet) Expected result: the document is saved on your google drive Current result: an error dialog box that reads: "Error saving the document Untitled 1: General input/output error." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 17:22:50 2018 InstallationDate: Installed on 2018-02-08 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) 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/1754400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771971] Re: dns broken after upgrade to bionic
You seem to have a bad /etc/init.d/netplan file on the system; it's not coming from the netplan.io package. You should make sure you do not have the 'netplan' package installed (the network plan server). Please attach the contents of /etc/NetworkManager/NetworkManager.conf. ** Package changed: netplan.io (Ubuntu) => network-manager (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/1771971 Title: dns broken after upgrade to bionic Status in network-manager package in Ubuntu: Incomplete Bug description: After upgrade to Bionic my DNS is broken. `resolv.conf` contains ``` # 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. nameserver 127.0.0.53 ``` and network is configured via network manager and DHCP. But DNS will only work when entering the IP manually. Maybe something wrong with netplan? ``` ~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlan0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (eth0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: netplan.io 0.36.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: i3 Date: Fri May 18 09:56:49 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-03 (1444 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: netplan.io UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1771971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768130] Re: libssh-dev libraries are returning a different version from package
Running into this as well. The 0.8.0 branch has renamed 'ssh_get_publickey' to 'ssh_get_server_publickey' however it is not possible to test for this in the macro because from the headers is looks like we are running libssh 0.7.0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1768130 Title: libssh-dev libraries are returning a different version from package Status in libssh package in Ubuntu: New Bug description: System: Description: Ubuntu 18.04 LTS Release: 18.04 Package: libssh-dev: Installed: 0.8.0~20170825.94fa1e38-1build1 Candidate: 0.8.0~20170825.94fa1e38-1build1 Version table: *** 0.8.0~20170825.94fa1e38-1build1 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I'm using libssh-dev to compile some projects like libvirt and others. The current package installed is 0.8.0, but if we check the headers /usr/include/libssh/libssh.h, we can see it: /* libssh version */ #define LIBSSH_VERSION_MAJOR 0 #define LIBSSH_VERSION_MINOR 7 #define LIBSSH_VERSION_MICRO 0 If we try to use the version inside a C code, we get: printf("%x", LIBSSH_VERSION_INT); I expect to see: 800 I'm seeing: 700 Check pkg-config too: $ pkg-config --modversion libssh 0.8.0 It does not match with the package version and some new functions were implemented after libssh release 0.7.5. This libssh.h file needs to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1768130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771971] [NEW] dns broken after upgrade to bionic
You have been subscribed to a public bug: After upgrade to Bionic my DNS is broken. `resolv.conf` contains ``` # 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. nameserver 127.0.0.53 ``` and network is configured via network manager and DHCP. But DNS will only work when entering the IP manually. Maybe something wrong with netplan? ``` ~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlan0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (eth0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: netplan.io 0.36.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: i3 Date: Fri May 18 09:56:49 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-03 (1444 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: netplan.io UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic -- dns broken after upgrade to bionic https://bugs.launchpad.net/bugs/1771971 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773850] Re: No login prompt when booting bionic with both hdmi and vga monitor
Thank you, penalvch. 1) viewsonic vx2433wm model VS12324 2010-01-28 samsung 22" led tv series 5 5000 model code UN22F5000AFXZA Version: FP02 2) For the HDMI connection from the thinkpad, I'm using an INSIGNIA DisplayPort-to-HDMI Adapter 3) Yes, except while I am then able to configure the two external screens, the laptop screen becomes blank. So I can use 2 out of the 3 screens. That was also a limitation in Trusty where I used Unity. 4) I haven't tried it on anything between trusty and bionic. 5) Standard bionic: Gnome 3. 6) This may be out-of-date, and I've pasted back in two crash files that I had moved to another directory at 10:57: drwxrwsrwt 2 root whoopsie 4096 May 28 10:57 . drwxr-xr-x 14 root root 4096 Apr 26 12:30 .. -rw-r--r-- 1 root whoopsie0 May 28 09:27 _usr_bin_Xwayland.120.upload -rw--- 1 whoopsie whoopsie0 May 28 09:28 _usr_bin_Xwayland.120.uploaded -rw-r- 1 gdm whoopsie 5069766 May 28 09:22 _usr_bin_Xwayland.120.crash -rw-r- 1 neal neal 17800803 May 28 09:20 _usr_lib_xorg_Xorg.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773850 Title: No login prompt when booting bionic with both hdmi and vga monitor Status in xorg package in Ubuntu: Incomplete Bug description: I'm running bionic on a Lenovo X230 laptop. It works fine to boot it with either my hdmi monitor or my VGA monitor. It also works to attach the VGA monitor after booting and logging in with the HTMI monitor. But if both are connected while I boot, the graphical login prompt never appears, and just the mouse appears in the laptop window on a blue screen, with the HDMI monitor showing a blank blue screen, and the VGA monitor getting no signal. This monitor configuration worked fine with this computer in Trusty. I ran apport-bug to report the problem, and chose the first option: "Display (X.org)". I'm not positive what I'm running, but note that after booting and getting both monitors plugged in and running after login, I see both an Xwayland process and an Xorg process. I suggest also changing apport-bug to appropriately reflect that wayland is somehow involved, and I hope that the included debug info will include any appropriate wayland info. I note that it does seem to be possible to get some info via `apport-bug xwayland`. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Mon May 28 11:40:58 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2018-05-01 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 343522U ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=51612d4c-57c8-45d0-b308-86df52604f07 ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GCETA1WW (2.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETA1WW(2.61):bd02/12/2015:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.91
[Desktop-packages] [Bug 1773597] Re: USB flash drive won't mount
** Tags added: 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/1773597 Title: USB flash drive won't mount Status in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=870f1d77-345c-44b2-99e6-79adea07159c ro quiet splash vt.handoff=1 Ubuntu version: Ubuntu 18.04 LTS, software is up to date Steps to create problem: 1. Reboot 2. Insert USB flash drive USB flash drive does not appear on desktop or in Nautilus file window dmesg | tail [ 1435.463032] usb 2-1.3: new high-speed USB device number 8 using ehci-pci [ 1435.685760] usb 2-1.3: New USB device found, idVendor=05dc, idProduct=c75c [ 1435.685763] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1435.685765] usb 2-1.3: Product: USB Flash Drive [ 1435.685766] usb 2-1.3: Manufacturer: Lexar [ 1435.685767] usb 2-1.3: SerialNumber: D2036779FCE9EDC016EF lsusb Bus 002 Device 007: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card Bus 002 Device 006: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick Bus 002 Device 005: ID 413c:8157 Dell Computer Corp. Integrated Keyboard Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 002 Device 008: ID 05dc:c75c Lexar Media, Inc. Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:640f Microdia Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1773597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700649] Re: MTP device fails to mount
usbfs: process (mtp.so) did not claim interface 0 before use I get this error message on ubuntu 18.4. I believe there are two different problems. First problem could be that InternalSD is readonly to the MTP process on the phone (see last line in log), why? Read-only requests worked. The other problem are the failed read attempts with varying errno, see below. Log from phone is: 05-28 15:32:02.505 D/MtpService(3263): Adding MTP storage 0x10001 at /storage/emulated/0 05-28 15:32:02.505 D/MtpService(3263): Adding MTP storage 0xa5bf0001 at /storage/7743-14FD 05-28 15:32:02.505 D/MtpService(3263): starting MTP server in MTP mode with storage /storage/emulated/0 disabled 05-28 15:32:13.094 E/MtpServer(3263): request read returned -1, errno: 5 05-28 15:32:13.551 D/MtpService(3263): starting MTP server in MTP mode with storage /storage/emulated/0 05-28 15:32:13.558 D/MtpService(3263): Adding MTP storage 0xa5bf0001 at /storage/7743-14FD 05-28 15:32:13.558 D/MtpService(3263): Adding MTP storage 0x10001 at /storage/emulated/0 05-28 15:32:26.711 E/MtpServer(3263): request read returned -1, errno: 5 [ above repeated several times. ] 05-28 15:35:30.269 D/MtpService(3263): Adding MTP storage 0xa5bf0001 at /storage/7743-14FD 05-28 15:35:30.270 D/MtpService(3263): Adding MTP storage 0x10001 at /storage/emulated/0 05-28 15:35:53.914 E/MtpServer(3263): deletePath stat failed for /storage/emulated/0/DCIM/Camera/IMG_20180519_202734.jpg: No such file or directory [repeated for each file] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1700649 Title: MTP device fails to mount Status in gvfs package in Ubuntu: Confirmed Bug description: In 17.04 thunar/gvfs is no longer able to access my phone over USB. (This worked fine in 16.10 with the same phone/android version.) On connecting the phone the device shows up in Thunar and double clicking it shows the two folders (Internal Shared Storage and SD Card), however another window immediately pops up saying: Failed to mount "E5823" Unable to open MTP device '[usb:003,048]' The phone will then pop up the dialog asking how to use the USD connection (charging or transfer files) like when initially connected. Choosing Transfer causes the device to show up again in Thunar, but the same thing happens again if trying to access it. The output of dmesg shows lots of lines like: usbfs: process 13035 (events) did not claim interface 0 before use and a few lines like: usbfs: process 12893 (pool) did not claim interface 0 before use where the process id changes every time I reconnect the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1700649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions
** Package changed: gstreamer1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1770725 Title: [i915 SNB] Totem window is all black in Wayland sessions Status in Gstreamer1.0: Incomplete Status in gstreamer-vaapi package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello, You can not see the image of the movie. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.0-1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.10-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 15:35:17 2018 InstallationDate: Installed on 2017-10-13 (210 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700649] Re: MTP device fails to mount
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1700649 Title: MTP device fails to mount Status in gvfs package in Ubuntu: Confirmed Bug description: In 17.04 thunar/gvfs is no longer able to access my phone over USB. (This worked fine in 16.10 with the same phone/android version.) On connecting the phone the device shows up in Thunar and double clicking it shows the two folders (Internal Shared Storage and SD Card), however another window immediately pops up saying: Failed to mount "E5823" Unable to open MTP device '[usb:003,048]' The phone will then pop up the dialog asking how to use the USD connection (charging or transfer files) like when initially connected. Choosing Transfer causes the device to show up again in Thunar, but the same thing happens again if trying to access it. The output of dmesg shows lots of lines like: usbfs: process 13035 (events) did not claim interface 0 before use and a few lines like: usbfs: process 12893 (pool) did not claim interface 0 before use where the process id changes every time I reconnect the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1700649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773628] Re: package cups-browsed 1.17.9-0ubuntu1.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127
*** This bug is a duplicate of bug 1773629 *** https://bugs.launchpad.net/bugs/1773629 ** This bug has been marked a duplicate of bug 1773629 package apache2 2.4.27-2ubuntu4.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1773628 Title: package cups-browsed 1.17.9-0ubuntu1.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 Status in cups-filters package in Ubuntu: New Bug description: memcached ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cups-browsed 1.17.9-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Sun May 27 10:55:56 2018 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 Lpstat: device for Canon-G3000: cnijbe2://Canon/?port=net&serial=84-BA-3B-5E-63-D7 MachineType: Hewlett-Packard HP ProBook 430 G2 Papersize: a4 PpdFiles: Canon-G3000: Canon G3000 series Ver.5.30 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic root=UUID=94718cde-02bd-40cb-baab-db57e87057a5 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: cups-filters Title: package cups-browsed 1.17.9-0ubuntu1.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127 UpgradeStatus: Upgraded to artful on 2018-03-05 (82 days ago) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M73 Ver. 01.42 dmi.board.name: 2246 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 59.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM73Ver.01.42:bd09/26/2016:svnHewlett-Packard:pnHPProBook430G2:pvrA3008CD10003:rvnHewlett-Packard:rn2246:rvrKBCVersion59.23:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 430 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1773628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Hello Chris, or anyone else affected, Accepted gdm3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gdm3 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in on the second attempt if you'd got your password wrong on the first attempt. All you'd see is a blank purple screen and mouse pointer only. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1769403] Re: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude
Can you remove all kernel parameters that are not defaults, and try the latest mainline kernel? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769403 Title: USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: Hi, I am facing the problem that is similar to the one described in the thread: https://ubuntuforums.org/showthread.php?t=2342985 Laptop (Dell Latitude 6420) randomly stops responding to the usb Trackball and Keyboard. Unplugging & plugging them back into a different port does not fix the problem. Sometimes the problem is fixed after rebooting or suspending the laptopo, then turning it on; but the problem re-appears almost immediately - after 10". The problem is related to the Logitech trackman wheel & Mircosoft PS2 Keyboard, both are old. Command "lsusb" for the 2 devices gives: Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter Command "tlp-stat -u" for the 2 devices gives: Bus 002 Device 005 ID 046d:c404 control = on, autosuspend_delay_ms = -1000 -- Logitech, Inc. TrackMan Wheel (usbhid) Bus 002 Device 006 ID 0a81:0205 control = on, autosuspend_delay_ms = -1000 -- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid) Command "uname -ra" gives: Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This problem tends to be very frustrating. note: I think this is not related with autosuspend, but rather with buffer overflow for the specific devices due to that they are not supported in the kernel code. Regards --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kpapadim 2115 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=07c8ef4a-5fe5-4d04-905b-4e2d8ffdafe5 InstallationDate: Installed on 2017-07-23 (292 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude E6420 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e51bbf95-8017-48ae-bad5-f74efc43adda ro noapic quiet splash usbcore.autosuspend=-1 usbhid.quirks=0x046d:0xc404:0x0400 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
rls-bb-notfixing means that this doesn't need to be tracked as a team release-critical bug; anyone else should feel free to work on the remaining items ** Tags added: rls-bb-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1761554 Title: [bionic] Extended characters in GNOME screen keyboard don't get entered Status in gnome-shell package in Ubuntu: Triaged Status in gnome-user-docs package in Ubuntu: New Status in im-config package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Status in gnome-user-docs source package in Bionic: New Status in im-config source package in Bionic: Fix Committed Bug description: im-config SRU request = [Impact] When in a Wayland session, accented characters as well as some special characters can't be entered via the screen keyboard. The issue is fixed via the proposed upload of im-config, which has been changed to not set the GTK_IM_MODULE environment variable for IBus on Wayland (previously GTK_IM_MODULE was set to "ibus"). Making this accessibility tool work without issues on Wayland is important enough to justify this SRU. [Test Case] 1. Log in to an Ubuntu on Wayland session 2. Open gedit and enable the screen keyboard (Settings -> Universal Access -> Typing) -> Accented characters via long-press does not work. Example: long-press a and select à from the popup Also, certain keys for special characters result in incorrect characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢ 3. Install im-config from bionic-proposed 4. Relogin and repeat step 2. -> Everything works as expected [Regression Potential] There are reasons to presuppose that GTK_IM_MODULE does not need to be set at all for IBus on a GNOME desktop: * GTK has a mechanism for selecting a built-in IM. * IBus is default in GNOME, and vanilla GNOME (which does not make use of im-config) does not set the GTK_IM_MODULE environment variable. But the change is only made for Wayland sessions, which is not default in 18.04. Given this limitation, the regression risk is deemed to be low. [Original description] I filed this bug upstream last month but it hasn't gotten much attention so I'm filing it here because I think we need to track this issue for the Ubuntu 18.04 release https://gitlab.gnome.org/GNOME/gnome-shell/issues/109 Test Case - 1. Open the Settings app. Click Universal Access. 2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal Access Menu" to make turning the Screen Keyboard on and off easier.) 3. Open Text Editor 4. Click the u button on the Screen Keyboard 5. Long-press the u button on the Screen Keyboard for a few seconds. On the popup, click the ü character. What Happens In Step 4, u is entered in the Text Editor document. Nothing is entered in Step 5. This bug affects any of the "extended characters" clicked on from the long-press popup in the Screen Keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
@Ken Wright Thanks for the info. I installed gufw. I found that the firewall was disabled for "Home" and enabled for "Office" and "Public". I disabled it for all and rebooted. scanimage -L still does not find the Brother scanner. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & gnome-shell fail to start?
** Tags removed: rls-bb-incoming ** Tags added: rls-bb-notfixing -- 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/1765724 Title: Xenial -> Bionic - System fails to boot after upgrade - gnome- screensaver & gnome-shell fail to start? Status in cryptsetup package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Test Case: 1. Install Xenial Desktop with encrypted home 2. Upgrade to bionic 3. Reboot Actual Result The system appears to fail to start gnome-shell / gnome-screensaver: Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] Activating service name='org.gnome.ScreenSaver' requested by ':1.3' (uid=121 pid=1647 comm="/usr/lib/gnome-session/gnome-session-binary --auto Apr 23 14:17:12 ubuntu org.gnome.ScreenSaver[1645]: Unable to init server: Could not connect: Connection refused Apr 23 14:17:12 ubuntu gnome-screensav[1654]: Cannot open display: Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1 Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error Apr 23 14:17:12 ubuntu gnome-shell[1656]: Failed to create backend: Could not find a primary drm kms device Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 23 14:17:12 ubuntu gdm-launch-environment][1627]: pam_unix(gdm-launch-environment:session): session closed for user gdm Apr 23 14:17:12 ubuntu gdm3[1187]: GdmDisplay: display lasted 0.292659 seconds Apr 23 14:17:12 ubuntu systemd-logind[1028]: Removed session c2. Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No data available Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No data available Apr 23 14:17:12 ubuntu gdm3[1187]: Child process -1643 was already dead. Also the system hangs on boot when it activates the encrypted swap. There are the following entries in the journal: $ journalctl -b-1 -o short-monotonic |grep crypt [1.535326] ubuntu kernel: Key type encrypted registered [ 125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. [ 125.637789] ubuntu systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. [ 125.638311] ubuntu systemd[1]: Dependency failed for /dev/mapper/cryptswap1. [ 125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. [ 125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. [ 125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted Volumes. [ 125.640128] ubuntu systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'. [ 125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. [ 383.902153] ubuntu systemd[1]: Starting Cryptography Setup for cryptswap1... [ 383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b. [ 384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1. [ 384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes. [ 384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1. [ 384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1... [ 384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. Priority:-2 extents:1 across:2093564k FS [ 384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1. But eventually activates, once the device is there. Note this is not a hang, as timeouts are reached "instantly". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:2.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentD
[Desktop-packages] [Bug 1770725] Re: [i915 SNB] Totem window is all black in Wayland sessions
Hello Daniel van Vugt, If I remove "gstreamer1.0-vaapi" you can see the video in Wayland with Totem. Regards, -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1770725 Title: [i915 SNB] Totem window is all black in Wayland sessions Status in Gstreamer1.0: Incomplete Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Hello, You can not see the image of the movie. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.0-1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.10-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri May 11 15:35:17 2018 InstallationDate: Installed on 2017-10-13 (210 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer1.0/+bug/1770725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773561] Re: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789).
** Summary changed: - Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017-*). + Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789). ** Description changed: Hello. GIMP package ('Universe/Security' section), available in "Xenial"/16.04 LTS Release, contains unfixed security issues and is vulnerable to, for example, heap-buffer over-read, out of bounds read and stack-based - buffer over-read etc. The whole this is pretty strange, because Ubuntu + buffer over-read etc. The whole thing is pretty strange, because Ubuntu Releases released before and after "Xenial", contains updated GIMP - version! + package! Anyway, it looks this way: in "Trusty" the available version is: '2.8.10-0ubuntu1.2' (please see [1]). "Bionic" has '2.8.20-1.1' version (please see [2]). Both Releases contains fixes for mentioned security issues: CVE-2017-* etc. However, GIMP version in "Xenial" is '2.8.16-1ubuntu1.1' and does not contain any security updates from 2017. (The last one is from Thu, 30 Jun 2016.; please see [3]). Security updates with fixes for mentioned CVE's (please compare changes in 1. and 2. with 3.) were released on Thu., 18 Jan 2018 - for "Trusty" and Tue., 26 Dec 2017 - for "Bionic". In "Xenial", the last security update is from Thu., 30 Jun 2016 (fix for CVE-2016-4994) and there is no further updates! - Here is a CVE list, which are not fixed in "Xenial", but in "Trusty" and - "Bionic" only: + Here is a CVE list of security issues not fixed in "Xenial", but in + "Trusty" and "Bionic" etc.: - 1/ CVE-2017-17786: Out of bounds read - 2/ CVE-2017-17789: Heap-based buffer overflow in read_channel_data - 3/ CVE-2017-17784: Heap-buffer over-read in load_image file-gbr.c + 1/ CVE-2017-17784: Heap-buffer over-read in load_image file-gbr.c + 2/ CVE-2017-17785: Heap-based buffer overflow in fli_read_brun function + 3/ CVE-2017-17786: Out of bounds read 4/ CVE-2017-17787: Heap-based buffer over-read in read_creator_block - 5/ CVE-2017-17785: Heap-based buffer overflow in fli_read_brun function - 6/ CVE-2017-17788: Stack-based buffer over-read in xcf_load_stream + 5/ CVE-2017-17788: Stack-based buffer over-read in xcf_load_stream + 6/ CVE-2017-17789: Heap-based buffer overflow in read_channel_data - I wanted to send an email an email to Mr Marc Deslauriers, because he - made the last security update for GIMP in "Xenial" (fix for - CVE-2016-4994). But I decided to report a bug on Launchpad. I hope that - it's an acceptable way. If not, I'm sorry. + And the most important thing: if User had installed GIMP package in + "Xenial" Release, he is affected - since one year, at least - because of + a vulnerable version. Security issues, mentioned above, are from 2017. + So, maybe it's a good opportunity to update GIMP to v2.10.2 version, + released on 20., May 2018? (Version 2.8.X is very outdated). - ✗✗✗ And the most important thing: if an User had installed GIMP package - in "Xenial" Release, he is affected because he is using a vulnerable - version since one year! Security issues, mentioned above, are from 2017. - So, maybe it's a good opportunity to update GIMP to v2.10.2 version, - released on 20., May 2018? At least in non-LTS Releases. Of course I'm - not talking about "Cosmic" here. (Version 2.8.X is very outdated). + I wanted to send an email to Mr Marc Deslauriers, because he made the + last security update for GIMP in "Xenial" (fix for CVE-2016-4994). But I + decided to report a bug on Launchpad. I hope that it's an acceptable + way. If not, I'm sorry. By the way: similar problems with unfixed security issues, can be found e.g. in Audacious and Parole packages. But that's a different story, completely different story... Thanks, best regards. __ 1. http://changelogs.ubuntu.com/changelogs/pool/main/g/gimp/gimp_2.8.10-0ubuntu1.2/changelog 2. http://changelogs.ubuntu.com/changelogs/pool/universe/g/gimp/gimp_2.8.20-2/changelog 3. http://changelogs.ubuntu.com/changelogs/pool/universe/g/gimp/gimp_2.8.16-1ubuntu1.1/changelog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1773561 Title: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789). Status in gimp package in Ubuntu: Confirmed Bug description: Hello. GIMP package ('Universe/Security' section), available in "Xenial"/16.04 LTS Release, contains unfixed security issues and is vulnerable to, for example, heap-buffer over-read, out of bounds read and stack-based buffer over-read etc. The whole thing is pretty strange, because Ubuntu Releases released before and after "Xenial", contains updated GIMP package! Anyway, it looks this way: in "Trusty" the available version is: '2.8.10-0ubuntu1.2' (please see [1]). "Bionic" has '2.8.20-1.1' version (please see [2]). B
[Desktop-packages] [Bug 1772183] Re: Microsoft Mice on dual boot systems can scroll multiple lines at a time.
1) The mouse model is Microsoft Sculpt Ergonomic Mouse. 2) This issue does not appear in Microsoft Windows 10, the version I have installed to my other partition. I believe from reading the comments on askububtu the bug needs a dual boot configuration to exist. 3) I don't believe I tested for this particular bug, but I noticed odd scrolling in Half Life in Steam that was only fixed by rebooting in the proper sequence. I had no clue about the depth of the bug at the time. But it definitely existed in 16.04 as well. Can't recall if it existed prior, but it wouldn't surprise me. 4) Computer is an HP envy m7-n101dx. 5) The workaround package is located here: https://sourceforge.net/projects/resetmsmice/ 6) Yeah removing and reinserting the transciever fixes it until you reboot into Windows 10 again. You don't have to do it intermittently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772183 Title: Microsoft Mice on dual boot systems can scroll multiple lines at a time. Status in xorg package in Ubuntu: Incomplete Bug description: Running Ubuntu 18.04. Noticed this bug in 16.04 and earlier for who knows how long. See https://askubuntu.com/questions/47100/mouse-wheel- scrolling-too-fast. Installing the workaround package or removing the transceiver appears to be a workaround for the time being. Xorg should automatically scroll normally, not multiple lines at time after rebooting. Sometimes rebooting doesn't fix the issue. Askubuntu mentions the bug dating back to Natty. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24 Thu Apr 26 00:10:09 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 19 13:02:28 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de] Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de] InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) MachineType: HP HP ENVY m7 Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.49 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80DE dmi.board.vendor: HP dmi.board.version: 64.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY m7 Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://he
[Desktop-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer&system details to help improving Ubuntu
** Description changed: - The topic has been discussed on the ubuntu-devel@ list, see - https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html + [Rationale] + We added telemetry data for people installing ubuntu from ubiquity. We didn't get the time to do the same on upgrade despite the FFe acking it. It was decided it was better to first polish the installation and report experience, and then, tackling the upgrade for .1, where most LTS users will migrate from. + + ubuntu-release-upgrade just drop a telemetry file (like ubiquity is + dropping one) which is then picked up by ubuntu-report for user's review + and approval before sending. + + Note that ubuntu-report is already aware of the upgrade telemetry and + just ignores it when it's missing it (case of install of ugprade without + this ubuntu-release-upgrade versinon) + + [Impact] + * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is dropping one) which is then picked up by ubuntu-report for user's review and approval before sending. + * Note that ubuntu-report is already aware of the upgrade telemetry and just ignores it when it's missing it (case of install of ugprade without this ubuntu-release-upgrade versinon) + * The ubuntu-release-upgrade only drops a file thus. The logic is really similar to the one included in ubiquity for 18.04. The telemetry class is similar. + * The telemetry is reported by all existing UI. + + [Test Case] + * Install ubuntu-release-upgrade on an artful machine + * Run an upgrade from artful to bionic + * Check that once the upgrade finished, there is a /var/log/ugprade/telemetry file present on disk. + + + [Regression Potential] + + * The code is similar to ubiquity ones, and the impact is only dropping a file on disk. + * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, GTK3 and KDE frontends. + + --- + + + The topic has been discussed on the ubuntu-devel@ list, see https://lists.ubuntu.com/archives/ubuntu-devel/2018-February/040139.html The feature has different parts - the installer is going to record some informations about the installation details & options selected - the session is going to have a command line/GUI part that let user review&send those informations - the desktop settings should have a control to change the option later on ** Also affects: ubuntu-meta (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-initial-setup (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu Bionic) Status: New => Triaged ** No longer affects: ubuntu-meta (Ubuntu Bionic) ** No longer affects: ubiquity (Ubuntu Bionic) ** No longer affects: gnome-initial-setup (Ubuntu Bionic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1755456 Title: [ffe] Optional recording/sending of installer&system details to help improving Ubuntu Status in gnome-initial-setup package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Triaged Status in ubuntu-release-upgrader source package in Bionic: Triaged Bug description: [Rationale] We added telemetry data for people installing ubuntu from ubiquity. We didn't get the time to do the same on upgrade despite the FFe acking it. It was decided it was better to first polish the installation and report experience, and then, tackling the upgrade for .1, where most LTS users will migrate from. ubuntu-release-upgrade just drop a telemetry file (like ubiquity is dropping one) which is then picked up by ubuntu-report for user's review and approval before sending. Note that ubuntu-report is already aware of the upgrade telemetry and just ignores it when it's missing it (case of install of ugprade without this ubuntu-release-upgrade versinon) [Impact] * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is dropping one) which is then picked up by ubuntu-report for user's review and approval before sending. * Note that ubuntu-report is already aware of the upgrade telemetry and just ignores it when it's missing it (case of install of ugprade without this ubuntu-release-upgrade versinon) * The ubuntu-release-upgrade only drops a file thus. The logic is really similar to the one included in ubiquity for 18.04. The telemetry class is similar. * The telemetry is reported by all existing UI. [Test Case] * Install ubuntu-release-upgrade on an artful machine * Run an upgrade from artful t
[Desktop-packages] [Bug 1770731] Re: [nvidia] multimonitor ghostly flickering display artifacts
Gnome bug link: https://gitlab.gnome.org/GNOME/mutter/issues/175 -- 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/1770731 Title: [nvidia] multimonitor ghostly flickering display artifacts Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: On Ubuntu 18.04, running nvidia-390 driver (on a GTX 1080), and gnome shell 3.28.1. I have a 3 monitor setup. When I open a terminal in the middle window and some other window, like nautilus on the left, and quickly drag the nautilus window to the right, covering the terminal, and back without releasing the mouse, a flickering ghost of the window remains on the terminal for about a minute or so. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2018-05-10 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-22-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/ubuntu/+source/gnome-shell/+bug/1770731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773744] Re: Desktop session crash
Hi Christopher, Thank you for taking time to look into this issue. 1) No. The issue started when I connected third monitor to my Ubuntu PC. I have not tried 3-monitor setup with previous Ubuntu releases. 2) ls -la /var/crash total 256020 drwxrwsrwt 1 root whoopsie 366 touko 29 15:03 . drwxr-xr-x 1 root root 128 tammi 27 2017 .. -rwxrwxrwx 1 root whoopsie 0 touko 29 15:03 .lock -rw-r- 1 sami whoopsie 5969518 touko 25 19:24 _opt_Gitter_linux64_Gitter.1000.crash -rw-r- 1 sami whoopsie 28507228 touko 25 19:30 _usr_bin_gnome-shell.1000.crash -rw-r- 1 sami whoopsie 50895637 touko 28 09:58 _usr_bin_Xwayland.1000.crash -rw-r- 1 sami whoopsie 105541228 touko 25 19:12 _usr_lib_chromium-browser_chromium-browser.1000.crash -rw-r- 1 sami whoopsie 71245625 touko 25 19:24 _usr_lib_xorg_Xorg.1000.crash 3) I now did install gnome-session-flashback and rebooted the machine. Even after this, the desktop crashed. 4) I just downloaded and booted to the latest cd-image from the link. Desktop on the cd-image crashed as well with three monitors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773744 Title: Desktop session crash Status in xorg package in Ubuntu: Incomplete Bug description: If I connect third monitor to my Ubuntu PC, the whole graphical display session crashes. Additionally, the login does not show texts correctly. The texts are mostly missing. The errors happend with both Wayland and X. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 28 10:15:54 2018 DistUpgraded: 2018-04-25 16:14:35,274 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e4] Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1002:6771] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Caicos XTX [Radeon HD 8490 / R5 235X OEM] [103c:90b8] InstallationDate: Installed on 2016-11-22 (551 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=6c13d412-1c2a-4455-bfe8-351c03c72d2b ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-04-25 (32 days ago) dmi.bios.date: 09/09/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.18 dmi.board.asset.tag: CZC3427KBP dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC3427KBP dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.18:bd09/09/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.sys.vendor: Hewlett-Packard 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.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp