[Desktop-packages] [Bug 1768996] Re: Nautilus "Software caused connection abort" when copying file from smb share
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1768996 Title: Nautilus "Software caused connection abort" when copying file from smb share Status in nautilus package in Ubuntu: New Bug description: When copying a directory from a samba share on a NAS (Synology DS216j), it fails with "Software caused connection abort" after copying a few files. Expected to happen: Nautilus succesfully copies entire directory. What happens instead: Nautilus stops copying after a few files with the error "Software caused connection abort". Version: - Ubuntu 18.04. Behavior did not occur on 16.04. - samba version is 2:4.7.6+dfsg~ubuntu-0ubuntu2 - gvfs version is 1.36.1-0ubuntu1 - It seems related to https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312362. - It also does not seem to happen when using gio copy from the terminal. - I am also not sure whether this bug is in nautilus, gvfs, or samba. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 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: Unity:Unity7:ubuntu Date: Fri May 4 00:16:03 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'367' b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+215+203'" InstallationDate: Installed on 2018-05-01 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) Steps to reproduce the issue: 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
For PRIME users: as a workaround you can make you X session work with Intel driver with this minimal xorg.conf Section "ServerLayout" Identifier "layout" Screen 0 "Screen0" 0 0 Option "Xinerama" "0" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" Option "DPMS" "on" EndSection Section "Device" Identifier "intel" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" BusID "PCI:0@0:2:0" EndSection Section "Screen" Identifier "intel" Device "intel" Monitor"Monitor0" EndSection Section "Screen" Identifier "Screen0" Device "intel" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Virtual 1920 1080 Depth 24 EndSubSection EndSection Make sure to put your own BusID and screen size. Both are mandatory. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768906] Re: Xorg crash
Be sure to purge the previous used nvidia driver before testing a new one (settings removal). Do you get the same issue if 'nouveau' driver is used ? (nvidia purged, and reboot) -- 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/1768906 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: When attempting to log in to a newly updated bionic beaver via the display manager (I think this is the right term), I immediately see a crash, a return to the user selection/login screen and a no-longer functioning keyboard and mouse. This happens both with the proprietary driver installed drivers and with the apt installed nvidia-driver-396. some interesting tidbits from the syslog file are: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): Failing initialization of X screen 0 May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: "nvidia" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "wfb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "fb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) found, but none have a usable configuration. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens found(EE) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 09:28:59 2018 DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774] MachineType: ASUS All Series 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-lowlatency root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Thu May 3 09:20:03 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1768906] Re: Xorg crash
Same symptoms with a brand new GTX 1070 ti :( ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: When attempting to log in to a newly updated bionic beaver via the display manager (I think this is the right term), I immediately see a crash, a return to the user selection/login screen and a no-longer functioning keyboard and mouse. This happens both with the proprietary driver installed drivers and with the apt installed nvidia-driver-396. some interesting tidbits from the syslog file are: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): Failing initialization of X screen 0 May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: "nvidia" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "wfb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "fb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) found, but none have a usable configuration. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens found(EE) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 09:28:59 2018 DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774] MachineType: ASUS All Series 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-lowlatency root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Thu May 3 09:20:03 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906/+subscriptions
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
To monitor the latest news about a fix look at: https://gitlab.gnome.org/GNOME/gnome-shell/issues/227 And when that's available, we will update this bug with information about an Ubuntu 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: New Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: 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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Is there a fix for this or not?. Please tell me there is -^- -- 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: New Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: 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 1769029] [NEW] Display on Dell 1440x900 is not available
Public bug reported: Monitor resolution is limited to 1024x768 with no option for higher resolution 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 4 09:44:54 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: 945GZM-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 945GZM-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769029 Title: Display on Dell 1440x900 is not available Status in xorg package in Ubuntu: New Bug description: Monitor resolution is limited to 1024x768 with no option for higher resolution 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 4 09:44:54 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: 945GZM-S2 dmi.board.vendor: Gigabyte Technology
[Desktop-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
Mike, I agree we need smarter defaults and have proposed that for 18.10 here: https://trello.com/c/i3JvebJ9 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: The right (second) touchpad click does not work. It ceased to work about three months ago. ubuntu 18,04 aser ex2519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
I had GNOME (rather than Unity) as my default desktop before upgrading to 18.04, and I strongly believe that my settings should have been respected rather than overridden to the installation default. Whatever the merits of the choice of installation default, it seems clear error to impose it over a previously existing GNOME installation. My touchpad has hardware left and right buttons, and it is my understanding that it should therefore not default to "finger" mode but should instead default to "area" mode. I was not able to get two-finger secondary click to work in "finger" mode at all. The laptop is an Acer V3-574 and the touchpad identifies in dmesg as follows: hid-multitouch 0018:04F3:300B.0001: Ignoring the extra HID_DG_INPUTMODE input: ELAN0501:00 04F3:300B Touchpad as /devices/pci:00/INT3432:00/i2c-0/i2c-ELAN0501:00/0018:04F3:300B.0001/input/input8 hid-multitouch 0018:04F3:300B.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN0501:00 04F3:300B] on i2c-ELAN0501:00 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: The right (second) touchpad click does not work. It ceased to work about three months ago. ubuntu 18,04 aser ex2519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769022] [NEW] ubuntu 18.04 freezes after the login
Public bug reported: I am not able to log to ubuntu 18.04 after the upgrade. When I login I get setup screen with the word "Welcome" and the system freezes 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 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 23:29:56 2018 DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971] InstallationDate: Installed on 2016-11-19 (530 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 129925U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) dmi.bios.date: 07/20/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 54CN18WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Torpedo dmi.board.vendor: LENOVO dmi.board.version: 109-C06210-00B dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.family: IDEAPAD dmi.product.name: 129925U dmi.product.version: Ideapad Z575 dmi.sys.vendor: LENOVO 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 xserver.bootTime: Thu May 3 22:52:41 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769022 Title: ubuntu 18.04 freezes after the login Status in xorg package in Ubuntu: New Bug description: I am not able to log to ubuntu 18.04 after the upgrade. When I login I get setup screen with the word "Welcome" and the system freezes 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 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 23:29:56 2018 DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971] InstallationDate: Installed on 2016-11-19 (530 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 129925U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) dmi.bios.date: 07/20/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 54CN18WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Torpedo dmi.board.vendor: LENOVO dmi.board.version: 109-C06210-00B dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias:
[Desktop-packages] [Bug 1768906] Re: Xorg crash
Should I set this back to new? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When attempting to log in to a newly updated bionic beaver via the display manager (I think this is the right term), I immediately see a crash, a return to the user selection/login screen and a no-longer functioning keyboard and mouse. This happens both with the proprietary driver installed drivers and with the apt installed nvidia-driver-396. some interesting tidbits from the syslog file are: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): Failing initialization of X screen 0 May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: "nvidia" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "wfb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "fb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) found, but none have a usable configuration. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens found(EE) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 09:28:59 2018 DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774] MachineType: ASUS All Series 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-lowlatency root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Thu May 3 09:20:03 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
** Changed in: gnome-power Status: Unknown => Confirmed ** Changed in: gnome-power Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power: Confirmed Status in gnome-power-manager package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
Please try the 'xbacklight' command. And see also https://bugzilla.gnome.org/show_bug.cgi?id=688052 ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #688052 https://bugzilla.gnome.org/show_bug.cgi?id=688052 ** Also affects: gnome-power via https://bugzilla.gnome.org/show_bug.cgi?id=688052 Importance: Unknown Status: Unknown ** Changed in: gnome-power-manager (Ubuntu) Status: New => Confirmed ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power: Unknown Status in gnome-power-manager package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768991] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1768991 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768991 Title: [bytchtes8316] Sound does not work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: since I installed ubuntu the audio didn't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu May 3 23:38:40 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to kill PulseAudio daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: SmartBook 130 FullHD - M-SB130 dmi.product.version: Default string dmi.sys.vendor: Mediacom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768994] Re: Upgrade to 18.04 resets touchpad behavior to default, overriding existing GNOME settings
*** This bug is a duplicate of bug 1759300 *** https://bugs.launchpad.net/bugs/1759300 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 1759300, 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 1759300 Gnome Shell: Touchpad right click (bottom right) area does not work -- 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/1768994 Title: Upgrade to 18.04 resets touchpad behavior to default, overriding existing GNOME settings Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 18.04 defaults to setting the secondary (right) click on a touchpad to two-finger mode rather than the more common left and right buttons. It took me a while to figure out what was going on and how to fix it, having found this page explaining the situation: https://itsfoss.com/fix-right-click-touchpad-ubuntu/ There are two separate but closely related issues, either or both of which may constitute a bug. 1. When GNOME was installed prior to the upgrade to 18.04, the prior setting should be respected rather than reset to default. I simply lost the ability to secondary (right) click from the touchpad with no notice. Both left and right buttons acted as primary clicks. 2. My touchpad (Acer V3-574) has hardware left and right buttons, and my understanding from the documentation is that the two-finger method should not be enabled in that case. I was unable to get the two-finger method to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768991] Re: [bytchtes8316] Sound does not work
The same hardware is mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=189261, although it appears that's not what the original reporter of that bug has. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768991 Title: [bytchtes8316] Sound does not work Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: since I installed ubuntu the audio didn't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu May 3 23:38:40 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to kill PulseAudio daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: SmartBook 130 FullHD - M-SB130 dmi.product.version: Default string dmi.sys.vendor: Mediacom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768991] Re: outputsounddoesnotwork
I agree, that looks relevant:
[ 4849.250374] Audio Port: ASoC: no backend DAIs enabled for Audio Port
which comes from the kernel, sound/soc/soc-pcm.c:
/* there is no point preparing this FE if there are no BEs */
if (list_empty(>dpcm[stream].be_clients)) {
dev_err(fe->dev, "ASoC: no backend DAIs enabled for %s\n",
fe->dai_link->name);
ret = -EINVAL;
goto out;
}
** Summary changed:
- outputsounddoesnotwork
+ [bytchtes8316] Sound does not work
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Linux Kernel Bug Tracker #189261
https://bugzilla.kernel.org/show_bug.cgi?id=189261
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1768991
Title:
[bytchtes8316] Sound does not work
Status in linux package in Ubuntu:
New
Status in pulseaudio package in Ubuntu:
New
Bug description:
since I installed ubuntu the audio didn't work.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
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
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p',
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p',
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer']
failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Thu May 3 23:38:40 2018
InstallationDate: Installed on 2018-05-03 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed
to kill PulseAudio daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.name: SmartBook 130 FullHD - M-SB130
dmi.product.version: Default string
dmi.sys.vendor: Mediacom
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
Also, obviously, the above only works in Xorg logins. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** 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/1720438 Title: brightness control broken nvidia Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
Note to developers: The tricky thing about this bug is that you may need a pure Nvidia system. Not a hybrid. -- 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/1720438 Title: brightness control broken nvidia Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics
Please be more polite. I committed more time to researching this bug
report yesterday than any other. What the motherboard is capable of is
at least relevant and you should be aware of it.
While you are using the kernel parameter "nomodeset", the default X
graphics driver ("modesetting") will be limited to 1024x768. That is not
a bug.
If you would like to get back to the older graphics driver that may work
better for you (and may ignore the "nomodeset"), then you will need to
force it to use the intel driver instead of modesetting:
Section "Device"
Identifier "devname"
Driver "intel"
EndSection
in /etc/X11/xorg.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1767993
Title:
Lubuntu: X11 freezing/low resolution on N3150 intel graphics
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
Hi,
I just installed a fresh 18.04 on an ASRock beebox N3150 machine.
The regular ubuntu desktop installer hanged after entering X11 mode,
machine froze.
I then used Lubuntu alternate installer with the console based
installation, which worked without any problem.
But after rebooting the system again hung after the graphical login
prompt.
I then changed the boot options in /etc/default/grub to give the
kernel the options nosplash nomodeset and to leave the system in
console mode (I had similar experiences with former ubuntu versions on
that machine where X11 did not start when the mode had been set by
console.)
Now X11 works, but comes up in vesa mode (1024x768) only.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.6-1ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon Apr 30 12:25:09 2018
InstallationDate: Installed on 2018-04-30 (0 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-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)
That's not a bug. There's nothing on F7. Your session is on F2, and the login screen is F1. -- 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: New Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: 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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
** Description changed:
The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
it was working some weeks/months ago, so this is a recent regression.
+
+ Update: Actually the crash occurs on slow-ish systems due to a race
+ condition. It's not strictly only hi-DPI machines - that's just the most
+ common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up to
date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
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: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
In Progress
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
In Progress
Bug description:
The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
it was working some weeks/months ago, so this is a recent regression.
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
You will get the same behaviour using the cairo fix too:
https://bugs.freedesktop.org/show_bug.cgi?id=98883#c6
** Changed in: cairo (Ubuntu)
Importance: Undecided => High
** Changed in: cairo (Ubuntu Bionic)
Importance: Undecided => High
** No longer affects: glib2.0 (Ubuntu)
** No longer affects: glib2.0 (Ubuntu Bionic)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
In Progress
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
In Progress
Bug description:
The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
it was working some weeks/months ago, so this is a recent regression.
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
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: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions
"Expired" is a misnomer. It just moved to https://gitlab.gnome.org/GNOME/gtk/issues/539 Since we can't change that status, and shouldn't, I have just removed the gtk task. See the above link instead. ** No longer affects: gtk ** Description changed: + Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 + In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1698083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I also recall SGI workstations had some nice arbitrary scaling in the 1990's. But this is not about the state of the art, it's about the state of gnome-shell :) -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: In Progress Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768995] Re: The "Unlock" button of user administration asks for wrong user
Adding to a sudo-enabled group is not enough? Since /etc/passwd and /etc/shadow do not have 'account type' fields, what does it mean to be an administrator? Belong to the admin group? adm? sudo? Why did gnome-control-center asked specifically for patola's password? What if there were two people with 'administrator' types? Should it instead ask for the root password then? [22:08] [7973] [patola@buzinskas patola]% id uid=1000(patola) gid=1000(patola) groups=1000(patola),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),1001(procer3d) [22:08] [7974] [patola@buzinskas patola]% id razgriz uid=1002(razgriz) gid=1003(razgriz) groups=1003(razgriz),1001(procer3d) [22:08] [7975] [patola@buzinskas patola]% id felipe uid=1001(felipe) gid=1002(felipe) groups=1002(felipe),1001(procer3d) [22:08] [7976] [patola@buzinskas patola]% id ayrton uid=1003(ayrton) gid=1004(ayrton) groups=1004(ayrton),1001(procer3d) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 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: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Same problem here with a Dell XPS 15 9560 after Kubuntu 17.10 -> 18.04 upgrade. Finally solved after lots of retries and reboots. I have now: Graphics Drivers PPA (https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - sudo add-apt-repository ppa:graphics-drivers/ppa - sudo apt update - sudo apt dist-upgrade Replaced manually nvidia 390 drivers by the newest 396 Purged nouveau package because I saw a "segmentation fault" log in /var/log/Xorg.0.log - sudo apt purge xserver-xorg-video-nouveau - sudo vi /etc/X11/xorg.conf -> uncomment line #Driver "nvidia" of Section "Device". So my xorg.conf file is exactly the same as the pasted in comment #77 without the last Section "Monitor". - sudo reboot After the reboot I see my previous sddm login screen instead of a tty and I can login normally :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1660574] Re: IPv4 Address Lost 8 Days After Previous DHCP Allocation
I had this issue yesterday on 17.10. The IPV4 address for my Ethernet interface vanished. I could not find any option in the network portion of settings to ask the DHCP for the IP address, and sudo service network-manager restart did not recover, so I rebooted the system. This is obviously an extremely rare situation and I do not know how to reproduce it. If there is no notification that the network manager can register for to detect this situation automatically then there should be a reinitialize button in the network settings GUI. -- 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/1660574 Title: IPv4 Address Lost 8 Days After Previous DHCP Allocation Status in network-manager package in Ubuntu: Confirmed Bug description: My Ubuntu 16.04 desktop frequently loses the IPv4 address on its wired ethernet connection to my office's network. This happened this morning and previously happened 8 days ago. The network uses a Windows Small Business Server as its main Active Domain Domain Controller which includes a DHCP service. There are several other Ubuntu 16.04 machines on the network that do not seem to experience this issue. This is an IPv4 only network, no IPv6 services are configures and IPv6 is disabled on most machines. My PC has two wired network ports. One connects to the office network and uses DHCP to get an IPv4 address. The other connects to a switch on my desk that has test equipment connected to it and uses a static IPv4 address. I have the output from: ll /var/lib/NetworkManager nmcli -p c nmcli -p c show TN\ Wired Taken; after the renewal of the address eight days ago, this morning before I "Disconnect"ed the connection from the drop down menu and after I reconnected and an IPv4 address was re-acquired. If any of this would be helpful, please let me know and I shall post it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 31 09:55:10 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-03-12 (690 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IpRoute: default via 172.16.20.21 dev eth0 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 172.16.20.0/24 dev eth0 proto kernel scope link src 172.16.20.67 metric 100 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.10 metric 100 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-03-11T09:44:29.848008 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 TN Wired decbd8d4-b045-4214-88c3-904bcabaa386 /org/freedesktop/NetworkManager/ActiveConnection/2 eth1ethernet connected /org/freedesktop/NetworkManager/Devices/1 Test Network c2e4c3e8-027e-4201-8486-824d32ee164f /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1660574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1660574] Re: IPv4 Address Lost 8 Days After Previous DHCP Allocation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1660574 Title: IPv4 Address Lost 8 Days After Previous DHCP Allocation Status in network-manager package in Ubuntu: Confirmed Bug description: My Ubuntu 16.04 desktop frequently loses the IPv4 address on its wired ethernet connection to my office's network. This happened this morning and previously happened 8 days ago. The network uses a Windows Small Business Server as its main Active Domain Domain Controller which includes a DHCP service. There are several other Ubuntu 16.04 machines on the network that do not seem to experience this issue. This is an IPv4 only network, no IPv6 services are configures and IPv6 is disabled on most machines. My PC has two wired network ports. One connects to the office network and uses DHCP to get an IPv4 address. The other connects to a switch on my desk that has test equipment connected to it and uses a static IPv4 address. I have the output from: ll /var/lib/NetworkManager nmcli -p c nmcli -p c show TN\ Wired Taken; after the renewal of the address eight days ago, this morning before I "Disconnect"ed the connection from the drop down menu and after I reconnected and an IPv4 address was re-acquired. If any of this would be helpful, please let me know and I shall post it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 31 09:55:10 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-03-12 (690 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IpRoute: default via 172.16.20.21 dev eth0 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 172.16.20.0/24 dev eth0 proto kernel scope link src 172.16.20.67 metric 100 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.10 metric 100 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-03-11T09:44:29.848008 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 TN Wired decbd8d4-b045-4214-88c3-904bcabaa386 /org/freedesktop/NetworkManager/ActiveConnection/2 eth1ethernet connected /org/freedesktop/NetworkManager/Devices/1 Test Network c2e4c3e8-027e-4201-8486-824d32ee164f /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1660574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 931369] Czesc kochanie!
*** This bug is a duplicate of bug 818516 *** https://bugs.launchpad.net/bugs/818516 adna kobieta w twoim miecie czeka na ciebie Kliknij tutaj! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/931369 Title: gnome-system-log crashed with SIGABRT in raise() Status in gnome-utils package in Ubuntu: New Bug description: crashed while trying to open dmesg.0 in /var/log ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-system-log 3.2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 13 12:12:49 2012 ExecutablePath: /usr/bin/gnome-system-log InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1) ProcCmdline: gnome-system-log ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-utils StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () Title: gnome-system-log crashed with SIGABRT in raise() UpgradeStatus: Upgraded to precise on 2012-02-13 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/931369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768995] Re: The "Unlock" button of user administration asks for wrong user
I apologize. I mean you need to set that for razgriz. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 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: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768995] Re: The "Unlock" button of user administration asks for wrong user
You need to set patola's Account Type to Administrator for patola to be able to make changes to User Accounts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 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: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
I tried the patch for /usr/lib/ubiquity/ubiquity/misc.py in a virtual
machine.
Instead of corrupted graphics in the Ubiquity window, I saw a blank
white area above the "Copying files..." progress bar.
After a few seconds, the Ubiquity slide show appeared as usual, and I
did *not* get a crash.
I will also try this on actual hardware.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in glib2.0 package in Ubuntu:
Invalid
Status in ubiquity package in Ubuntu:
In Progress
Status in cairo source package in Bionic:
In Progress
Status in glib2.0 source package in Bionic:
Invalid
Status in ubiquity source package in Bionic:
In Progress
Bug description:
The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
it was working some weeks/months ago, so this is a recent regression.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
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: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768991] Bug is not a security issue
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768991 Title: outputsounddoesnotwork Status in pulseaudio package in Ubuntu: New Bug description: since I installed ubuntu the audio didn't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu May 3 23:38:40 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to kill PulseAudio daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: SmartBook 130 FullHD - M-SB130 dmi.product.version: Default string dmi.sys.vendor: Mediacom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768991] Re: outputsounddoesnotwork
This looks related: [ 4849.250374] Audio Port: ASoC: no backend DAIs enabled for Audio Port Also, your USB mass storage device may have troubles. (Probably not related to this.) Thanks ** 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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768991 Title: outputsounddoesnotwork Status in pulseaudio package in Ubuntu: New Bug description: since I installed ubuntu the audio didn't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu May 3 23:38:40 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to kill PulseAudio daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.name: SmartBook 130 FullHD - M-SB130 dmi.product.version: Default string dmi.sys.vendor: Mediacom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Offer some bounty then. Probably someone will help if you offer him a few hundred bucks. -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Wow, nobody want's to help us with this... -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768995] Re: The "Unlock" button of user administration asks for wrong user
Attachment screen showing the logged in user is indeed razgriz, but it asks for patola's password ** Attachment added: "unlock button askin password for wrong user" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+attachment/5133306/+files/Selection_001.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user Status in gnome-control-center package in Ubuntu: New Bug description: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 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: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768995] [NEW] The "Unlock" button of user administration asks for wrong user
Public bug reported: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaultsenv_reset Defaultsmail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification rootALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 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: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user Status in gnome-control-center package in Ubuntu: New Bug description: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 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: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1768752] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also i
** Information type changed from Private Security to Public ** Also affects: account-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1768752 Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 Status in account-plugins package in Ubuntu: New Status in kaccounts-providers package in Ubuntu: New Bug description: apart from kde config telepathy accounts package install error, I even cant update ubuntu base as i try every time the results is broken file. then it asks me to report the bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sun Apr 29 07:05:33 2018 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2018-04-26 (6 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1768752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768752] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also i
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1617564, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1768752 Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 Status in account-plugins package in Ubuntu: New Status in kaccounts-providers package in Ubuntu: New Bug description: apart from kde config telepathy accounts package install error, I even cant update ubuntu base as i try every time the results is broken file. then it asks me to report the bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sun Apr 29 07:05:33 2018 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2018-04-26 (6 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1768752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768996] [NEW] Nautilus "Software caused connection abort" when copying file from smb share
Public bug reported: When copying a directory from a samba share on a NAS (Synology DS216j), it fails with "Software caused connection abort" after copying a few files. Expected to happen: Nautilus succesfully copies entire directory. What happens instead: Nautilus stops copying after a few files with the error "Software caused connection abort". Version: - Ubuntu 18.04. Behavior did not occur on 16.04. - samba version is 2:4.7.6+dfsg~ubuntu-0ubuntu2 - gvfs version is 1.36.1-0ubuntu1 - It seems related to https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312362. - It also does not seem to happen when using gio copy from the terminal. - I am also not sure whether this bug is in nautilus, gvfs, or samba. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 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: Unity:Unity7:ubuntu Date: Fri May 4 00:16:03 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'367' b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+215+203'" InstallationDate: Installed on 2018-05-01 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: When copying a directory from a samba share on a NAS (Synology DS216j), it fails with "Software caused connection abort" after copying a few files. Expected to happen: Nautilus succesfully copies entire directory. What happens instead: Nautilus stops copying after a few files with the error "Software caused connection abort". Version: - Occurs on 18.04 and has not occurred on 16.04. + - Ubuntu 18.04. Behavior did not occur on 16.04. + - samba version is 2:4.7.6+dfsg~ubuntu-0ubuntu2 + - gvfs version is 1.36.1-0ubuntu1 - It seems related to https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312362. - It also does not seem to happen when using gio copy from the terminal. - I am also not sure whether this bug is in nautilus, gvfs, or samba. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 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: Unity:Unity7:ubuntu Date: Fri May 4 00:16:03 2018 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'367' - b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+215+203'" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'367' + b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+215+203'" InstallationDate: Installed on 2018-05-01 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: -- 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/1768996 Title: Nautilus "Software caused connection abort" when copying file from smb share Status in nautilus package in Ubuntu: New Bug description: When copying a directory from a samba share on a NAS (Synology DS216j), it fails with "Software caused connection abort" after copying a few files. Expected to happen: Nautilus succesfully copies entire directory. What happens instead: Nautilus stops copying after a few files with the error "Software caused connection abort". Version: - Ubuntu 18.04. Behavior did not occur on 16.04. - samba version is 2:4.7.6+dfsg~ubuntu-0ubuntu2 - gvfs version is 1.36.1-0ubuntu1 - It seems related to https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312362. - It also does not seem to happen when using gio copy from the terminal. - I am also not sure whether this bug is in nautilus, gvfs, or samba. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 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: Unity:Unity7:ubuntu Date: Fri May 4 00:16:03 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'367' b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+215+203'" InstallationDate: Installed on 2018-05-01 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about
[Desktop-packages] [Bug 1768994] [NEW] Upgrade to 18.04 resets touchpad behavior to default, overriding existing GNOME settings
Public bug reported: Ubuntu 18.04 defaults to setting the secondary (right) click on a touchpad to two-finger mode rather than the more common left and right buttons. It took me a while to figure out what was going on and how to fix it, having found this page explaining the situation: https://itsfoss.com/fix-right-click-touchpad-ubuntu/ There are two separate but closely related issues, either or both of which may constitute a bug. 1. When GNOME was installed prior to the upgrade to 18.04, the prior setting should be respected rather than reset to default. I simply lost the ability to secondary (right) click from the touchpad with no notice. Both left and right buttons acted as primary clicks. 2. My touchpad (Acer V3-574) has hardware left and right buttons, and my understanding from the documentation is that the two-finger method should not be enabled in that case. I was unable to get the two-finger method to work. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1768994 Title: Upgrade to 18.04 resets touchpad behavior to default, overriding existing GNOME settings Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 18.04 defaults to setting the secondary (right) click on a touchpad to two-finger mode rather than the more common left and right buttons. It took me a while to figure out what was going on and how to fix it, having found this page explaining the situation: https://itsfoss.com/fix-right-click-touchpad-ubuntu/ There are two separate but closely related issues, either or both of which may constitute a bug. 1. When GNOME was installed prior to the upgrade to 18.04, the prior setting should be respected rather than reset to default. I simply lost the ability to secondary (right) click from the touchpad with no notice. Both left and right buttons acted as primary clicks. 2. My touchpad (Acer V3-574) has hardware left and right buttons, and my understanding from the documentation is that the two-finger method should not be enabled in that case. I was unable to get the two-finger method to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768993] [NEW] Upgrade from 17.10 to 18.04 does not start gdm3 on boot
Public bug reported: Note, I have kde and gnome installed. Previously I was using lightdm, but since this was removed with the upgrade, I chose to use gdm. When booting, gdm did not start but instead I was at a shell login prompt. No errors were present in syslog or dmesg. dmesg output is attached. I could start the x server by executing `startx` from the CLI. I then issued a `dpkg-reconfigure sddm` and selected sddm, then `dpkg- reconfigure gdm` and selected gdm. It gave me some sort of error about invoke-rc.d, so I then did `invoke-rc.d gdm3 start`, and it started gdm fine without rebooting. Then on next reboot as well, gdm started. So I'm not sure what there actually caused it to work. 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: KDE Date: Thu May 3 15:46:12 2018 InstallationDate: Installed on 2017-10-06 (209 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "dmesg output" https://bugs.launchpad.net/bugs/1768993/+attachment/5133295/+files/dmesg -- 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/1768993 Title: Upgrade from 17.10 to 18.04 does not start gdm3 on boot Status in gdm3 package in Ubuntu: New Bug description: Note, I have kde and gnome installed. Previously I was using lightdm, but since this was removed with the upgrade, I chose to use gdm. When booting, gdm did not start but instead I was at a shell login prompt. No errors were present in syslog or dmesg. dmesg output is attached. I could start the x server by executing `startx` from the CLI. I then issued a `dpkg-reconfigure sddm` and selected sddm, then `dpkg- reconfigure gdm` and selected gdm. It gave me some sort of error about invoke-rc.d, so I then did `invoke-rc.d gdm3 start`, and it started gdm fine without rebooting. Then on next reboot as well, gdm started. So I'm not sure what there actually caused it to work. 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: KDE Date: Thu May 3 15:46:12 2018 InstallationDate: Installed on 2017-10-06 (209 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1768993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
I mean to list shares NT1 is needed with smbtree. the server will be listed but shares will not. we will see what happens down the road but this is actually a good thing because of security issues with lower protocols. -- 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/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in gvfs: Confirmed Status in samba: Unknown Status in nautilus package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768743] Re: /usr/lib/gnome-initial-setup/gnome-initial-setup:11:add_ubuntusso_account:login_and_enable_livepatch:on_livepatch_permission_acquired:g_simple_async_result_complet
** Changed in: gnome-initial-setup (Ubuntu) Status: New => Fix Committed ** Also affects: gnome-initial-setup (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-initial-setup (Ubuntu Bionic) Importance: Undecided => Low -- 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/1768743 Title: /usr/lib/gnome-initial-setup/gnome-initial- setup:11:add_ubuntusso_account:login_and_enable_livepatch:on_livepatch_permission_acquired:g_simple_async_result_complete:acquire_cb Status in gnome-initial-setup package in Ubuntu: Fix Committed Status in gnome-initial-setup source package in Bionic: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-initial-setup. This problem was most recently seen with package version 3.28.0-2ubuntu6, the problem page at https://errors.ubuntu.com/problem/c8e43a6cfaaa48659ff543bd3cfbfca433dceb54 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-initial-setup/+bug/1768743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
It's supposed to be a community, everybody tries to help best he can. -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768786] Re: Screen is displayed when resuming from suspend
*** This bug is a duplicate of bug 1532508 *** https://bugs.launchpad.net/bugs/1532508 It also happens on LightDM for me, so I am not sure if it is duplicate. -- 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/1768786 Title: Screen is displayed when resuming from suspend Status in budgie-desktop package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-unity-meta package in Ubuntu: New Bug description: Steps to reproduce and description: First test case - where things work correctly: 1. Open Settings-> Privacy and make sure that Automatic screen lock is ON. 2. Suspend your machine 3. Resume your machine 4. Notice that the lockscreen is shown on resume and that you can't see the desktop Second test case - where things are broken 1. Open Settings -> Privacy and make sure that Automatic screen lock is OFF. 2. Suspend your machine 3. Resume your machine 4. Notice that the desktop is visible for a second, then the screen blanks, then the lock screen appears, then the screen blanks again. You are left at a black screen and need to unlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749007] Re: Snap mounts should be hidden from System Monitor
It's work but I installed the standard gnome-system-monitor not the snap. -- 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/1749007 Title: Snap mounts should be hidden from System Monitor Status in gnome-system-monitor package in Ubuntu: In Progress Status in libgtop2 package in Ubuntu: Fix Committed Status in libgtop2 source package in Bionic: Fix Committed Bug description: * Impact snaps mount at listed in the system monitor but they are an implementation detail and not interesting there. We already filter them out of the Disks UI, we should do the same in the system monitor * Test case - have a snap installed (wshich is true in the default installation of Ubuntu) - open gnome-system-monitor - check the filesystem tabs content, snaps mounts shouldn't be listed * Regression potential Check that the system mounted partitions are still correctly listed -- As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the snap mounts in System Monitor should be hidden just as they're hidden from GNOME Disks. Perhaps they should be grouped under a dropdown of / (though this would require developing a new feature)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762163] Re: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it
The is an update: https://bugs.kde.org/show_bug.cgi?id=370975 Problem is not udisk, is Solid component. Patch available there (Comment 50) https://bugs.kde.org/show_bug.cgi?id=370975#c50 ** Bug watch added: KDE Bug Tracking System #370975 https://bugs.kde.org/show_bug.cgi?id=370975 ** Package changed: udisks2 (Ubuntu) => solid (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1762163 Title: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it Status in solid package in Ubuntu: New Bug description: There is a Fix proposed from comment 36 https://bugs.kde.org/show_bug.cgi?id=370975 I have this problem when trying to mount any removable device or internal disk partition, either from Dolphin or from removable device manager in panel. It always shows an error message when you try to mount the device first time, the device is not opened in Dolphin but it is mounted correctly. Then at the second attempt it does not show error message and device is opened in Dolphin. The messages that I get in Spanish: From Dolphin: "Ocurrió un error al acceder a «Carpeta personal», el sistema respondió: El dispositivo ya está montado: Device /dev/sdb3 is already mounted at `/media/yafu/PART 1'." From removable device manager in panel a window message titled "Error Cliente KIO ?" and "Formato de URL erroneo" message. By the way, in a recent Dolphin update, when you mount partitions from the small folder/home icon to the left of the Dolphin address bar (that icon only appears if you have Panels > Places disabled), every time you Mount a device from there that menu is filled enormously with "Umount <>" items. Really annoying. === Related messages in English: "Error KIO Client" with the text "malformed URL" "An error occurred while accessing 'Home', the system responded: The device is already mounted: Device /dev/sdl1 is already mounted at '/media/myuser/disk title'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solid/+bug/1762163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS
Might anyone be able to clarify what kinds of additional test cases (if any) are needed? If so, I would appreciate it. I'm making an attempt to be helpful in fixing this bug, but am a bit new to Canonical's internal processes in terms of what they expect to test / resolve these kinds of bugs. Any additional info / resources would be helpful. Thanks, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/1617535 Title: geoip.ubuntu.com does not utilize HTTPS Status in ubuntu-geoip package in Ubuntu: Fix Released Status in ubuntu-geoip source package in Trusty: Triaged Status in ubuntu-geoip source package in Xenial: Triaged Status in ubuntu-geoip source package in Artful: Triaged Bug description: Impact -- It's better to use https where we can. There were concerns about location leakage for users using a proxy (such as Tor). Test Case - Regression Potential As long as Canonical maintains https://geoip.ubuntu.com, things should be fine here. Minimal fix. Original Bug Report --- geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This can potentially be utilized by nation state adversaries to compromise user privacy. This service is called multiple times per day by the OS in order to track users. $ nc -zv geoip.ubuntu.com 80 Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded! $ nc -zv -w 3 geoip.ubuntu.com 443 nc: connect to geoip.ubuntu.com port 443 (tcp) timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749007] Re: Snap mounts should be hidden from System Monitor
You maybe tried before the package was actually built? You can also try by downloading the debs on https://launchpad.net/ubuntu/+source/libgtop2/2.38.0-2ubuntu0.18.04.1/+build/14822012 $ wget https://launchpad.net/ubuntu/+source/libgtop2/2.38.0-2ubuntu0.18.04.1/+build/14822012/+files/libgtop2-common_2.38.0-2ubuntu0.18.04.1_all.deb https://launchpad.net/ubuntu/+source/libgtop2/2.38.0-2ubuntu0.18.04.1/+build/14822012/+files/libgtop-2.0-11_2.38.0-2ubuntu0.18.04.1_amd64.deb $ sudo dpkg -i *.deb $ gnome-system-monitor but that's testing the deb version of gnome-system-monitor, the snap is going to be rebuilt to use the change... -- 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/1749007 Title: Snap mounts should be hidden from System Monitor Status in gnome-system-monitor package in Ubuntu: In Progress Status in libgtop2 package in Ubuntu: Fix Committed Status in libgtop2 source package in Bionic: Fix Committed Bug description: * Impact snaps mount at listed in the system monitor but they are an implementation detail and not interesting there. We already filter them out of the Disks UI, we should do the same in the system monitor * Test case - have a snap installed (wshich is true in the default installation of Ubuntu) - open gnome-system-monitor - check the filesystem tabs content, snaps mounts shouldn't be listed * Regression potential Check that the system mounted partitions are still correctly listed -- As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the snap mounts in System Monitor should be hidden just as they're hidden from GNOME Disks. Perhaps they should be grouped under a dropdown of / (though this would require developing a new feature)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Trying to install from ppa I get: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cinnamon-screensaver-x-plugin : Depends: cinnamon-screensaver (>= 3.1.0) but it is not going to be installed Recommends: xscreensaver-gl but it is not going to be installed Recommends: xscreensaver-gl-extra but it is not going to be installed gnome-keyring : Depends: gcr (>= 3.4) but it is not going to be installed Depends: pinentry-gnome3 but it is not going to be installed gvfs : Depends: gvfs-daemons (>= 1.36.1-0ubuntu1) Depends: gvfs-daemons (< 1.36.1-0ubuntu1.1~) gvfs:i386 : Depends: gvfs-daemons:i386 (>= 1.36.1-0ubuntu1) Depends: gvfs-daemons:i386 (< 1.36.1-0ubuntu1.1~) libappindicator3-1 : Depends: libindicator3-7 (>= 0.4.90) but it is not going to be installed libgtk-3-0 : Depends: libwayland-egl1-mesa (>= 10.0.2) but it is not going to be installed or libwayland-egl1 Recommends: libgtk-3-bin libkf5service5 : Depends: libkf5dbusaddons5 (>= 4.97.0) but it is not going to be installed Recommends: libkf5service-bin (= 5.44.0-0ubuntu1) but it is not going to be installed libkf5su-bin : Depends: libkf5su5 (>= 4.96.0) but it is not going to be installed libqt5gui5 : Depends: libegl1 but it is not going to be installed Depends: libgl1 but it is not going to be installed Recommends: libqt5svg5 but it is not going to be installed Recommends: qt5-gtk-platformtheme but it is not going to be installed mupen64plus-rsp-all : Depends: mupen64plus-rsp-hle but it is not going to be installed Recommends: mupen64plus-rsp-z64 but it is not going to be installed nvidia-304 : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 but it is not installable or xorg-video-abi-18 but it is not installable or xorg-video-abi-19 but it is not installable or xorg-video-abi-20 but it is not installable or xorg-video-abi-23 Depends: xserver-xorg-core but it is not going to be installed Recommends: nvidia-settings (>= 331.20) but it is not going to be installed zeitgeist : Depends: zeitgeist-datahub but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- 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 1749007] Re: Snap mounts should be hidden from System Monitor
I've followed the instructions at https://wiki.ubuntu.com/Testing/EnableProposed with pinning and /bionic- proposed and get 'E: Unable to locate package libgtop2' :( Could someone who knows the proper procedure update that article or what am I doing wrong? :) -- 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/1749007 Title: Snap mounts should be hidden from System Monitor Status in gnome-system-monitor package in Ubuntu: In Progress Status in libgtop2 package in Ubuntu: Fix Committed Status in libgtop2 source package in Bionic: Fix Committed Bug description: * Impact snaps mount at listed in the system monitor but they are an implementation detail and not interesting there. We already filter them out of the Disks UI, we should do the same in the system monitor * Test case - have a snap installed (wshich is true in the default installation of Ubuntu) - open gnome-system-monitor - check the filesystem tabs content, snaps mounts shouldn't be listed * Regression potential Check that the system mounted partitions are still correctly listed -- As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the snap mounts in System Monitor should be hidden just as they're hidden from GNOME Disks. Perhaps they should be grouped under a dropdown of / (though this would require developing a new feature)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+subscriptions -- Mailing list: https://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 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
On Thu, May 3, 2018 at 5:54 PM, tony <1767...@bugs.launchpad.net> wrote: > Andreas, it looks like to me that smbtree still needs NT1 to list > shares, as people harden there servers and disable less secure protocols > it will break browsing for shares. > Do you mean list shares or list computers? > the only way to get the computer listing with non-NT1 that I know of at > this point is with MDNS or Zeroconf/Bonjour > That's a remark I saw in the samba upstream bug too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in gvfs: Confirmed Status in samba: Unknown Status in nautilus package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary
I am on Ubuntu 18.04, fresh install using network-manager-openvpn -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1725779 Title: Gnome network manager cannot find authentication binary Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-ssh package in Ubuntu: Confirmed Bug description: From logs: Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7424] audit: op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" name="Library" pid=2510 uid=1000 result="success" Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7473] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Started the VPN service, PID 6934 Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7518] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Saw the service appear; activating connection Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7698] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Failed to request VPN secrets #3: No agents were available for t his request. Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7708] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: VPN plugin: state changed: stopped (6) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-pptp-gnome 1.2.4-4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 14:07:06 2017 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768597] Re: package filemanager-actions missing
** Tags removed: bot-comment ** Tags added: artful bionic ** Description changed: - - nautilus-actions was deprecated in favour of filemanager-actions. + nautilus-actions was deprecated in favour of filemanager-actions (see + https://github.com/GNOME/nautilus-actions ). But 18.04 repositories do not have either of the packages. -- 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/1768597 Title: package filemanager-actions missing Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus-actions was deprecated in favour of filemanager-actions (see https://github.com/GNOME/nautilus-actions ). But 18.04 repositories do not have either of the packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768786] Re: Screen is displayed when resuming from suspend
*** This bug is a duplicate of bug 1532508 *** https://bugs.launchpad.net/bugs/1532508 There is a much older gdm3 bug for this issue so I'm marking this a duplicate of that one. ** This bug has been marked a duplicate of bug 1532508 Screen contents revealed briefly on resume, before even unlocking -- 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/1768786 Title: Screen is displayed when resuming from suspend Status in budgie-desktop package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-unity-meta package in Ubuntu: New Bug description: Steps to reproduce and description: First test case - where things work correctly: 1. Open Settings-> Privacy and make sure that Automatic screen lock is ON. 2. Suspend your machine 3. Resume your machine 4. Notice that the lockscreen is shown on resume and that you can't see the desktop Second test case - where things are broken 1. Open Settings -> Privacy and make sure that Automatic screen lock is OFF. 2. Suspend your machine 3. Resume your machine 4. Notice that the desktop is visible for a second, then the screen blanks, then the lock screen appears, then the screen blanks again. You are left at a black screen and need to unlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768786] Re: Screen is displayed when resuming from suspend
*** This bug is a duplicate of bug 1532508 *** https://bugs.launchpad.net/bugs/1532508 ** Also affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-unity-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1768786 Title: Screen is displayed when resuming from suspend Status in budgie-desktop package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-unity-meta package in Ubuntu: New Bug description: Steps to reproduce and description: First test case - where things work correctly: 1. Open Settings-> Privacy and make sure that Automatic screen lock is ON. 2. Suspend your machine 3. Resume your machine 4. Notice that the lockscreen is shown on resume and that you can't see the desktop Second test case - where things are broken 1. Open Settings -> Privacy and make sure that Automatic screen lock is OFF. 2. Suspend your machine 3. Resume your machine 4. Notice that the desktop is visible for a second, then the screen blanks, then the lock screen appears, then the screen blanks again. You are left at a black screen and need to unlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
Andreas, it looks like to me that smbtree still needs NT1 to list shares, as people harden there servers and disable less secure protocols it will break browsing for shares. the only way to get the computer listing with non-NT1 that I know of at this point is with MDNS or Zeroconf/Bonjour -- 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/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in gvfs: Confirmed Status in samba: Unknown Status in nautilus package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768207] Re: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading
Might this have to do with nvidia driver 390 on optimus laptops? If I "sudo prime-select nvidia" the problem does not occur. But with "prime- select intel" it has... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768207 Title: gnome-control-center / Ubuntu settings takes 1 minute+ 100% CPU first time loading Status in gnome-control-center package in Ubuntu: New Bug description: First time starting gnome-control-center after login, it takes ~70seconds to load and 100%CPU. Only first time starting I get "nvc0_screen_create:906 - Error allocating PGRAPH context for M2MF: -16". In terminal "top" shows "gst-plugin-scan" is the offender. I installed two extensions initially but now all are switched off with same effect. Second and other times starting, all is normal Dell XPS 15, BIOS v1.9, Ubuntu 18.04LTS, *clean* install all default, just had to start nvidia to be able to login at all first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768976] [NEW] Ubuntu 18.04 is overheating after upgrade from 16.04
Public bug reported: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade ** Also affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in ubuntu-release-upgrader package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1768976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768637] Re: /etc/modprobe.d is not a file
Same thing here..wtf. May 3 22:31:40 camview-pxe systemd[1]: Stopped Light Display Manager. May 3 22:31:40 camview-pxe systemd[1]: Starting Detect the available GPUs and deal with any system changes... May 3 22:31:40 camview-pxe gpu-manager[599]: /etc/modprobe.d is not a file May 3 22:31:40 camview-pxe systemd[1]: Starting Set console scheme... May 3 22:31:40 camview-pxe gpu-manager[599]: /etc/modprobe.d is not a file May 3 22:31:40 camview-pxe NetworkManager[406]: [1525379500.4101] manager: startup complete May 3 22:31:40 camview-pxe systemd[1]: Started Set console scheme. May 3 22:31:40 camview-pxe gpu-manager[599]: /etc/modprobe.d is not a file May 3 22:31:40 camview-pxe systemd[1]: Created slice system-getty.slice. May 3 22:31:40 camview-pxe gpu-manager[599]: /etc/modprobe.d is not a file May 3 22:31:40 camview-pxe systemd[1]: Started Getty on tty1. May 3 22:31:40 camview-pxe gpu-manager[599]: Error: can't open /lib/modules/4.13.0-39-generic/updates/dkms May 3 22:31:40 camview-pxe gpu-manager[599]: Error: can't open /lib/modules/4.13.0-39-generic/updates/dkms May 3 22:31:40 camview-pxe systemd[1]: Reached target Login Prompts. May 3 22:31:40 camview-pxe systemd[1]: Started Detect the available GPUs and deal with any system changes. May 3 22:31:40 camview-pxe systemd[1]: Starting Light Display Manager... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1768637 Title: /etc/modprobe.d is not a file Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Hello, I noticed the following entries in my journal after upgrading to 18.04 LTS from 16.04 LTS: May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:31 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:31 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:33 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:33 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Start request repeated too
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Today I got all working, but although prime-select query showed me "nvidia", nvidia drivers were not loaded and nvidia-settings did not start. I regret that I decided to run "sudo prime-select intel". Login worked but it broke suspend mode and my logout/shutdown times are horrible: 1,5 minutes. * This makes the intel mode unusable for the XPS and I think all optimus prime Nvidia laptops, so if you need that, downgrage to 17.10 might be only solution for now ? Running prime-select nvidia gives good performance and suspend and logout work again, but with running fans and hot laptop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768786] Re: Screen is displayed when resuming from suspend
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/1768786 Title: Screen is displayed when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce and description: First test case - where things work correctly: 1. Open Settings-> Privacy and make sure that Automatic screen lock is ON. 2. Suspend your machine 3. Resume your machine 4. Notice that the lockscreen is shown on resume and that you can't see the desktop Second test case - where things are broken 1. Open Settings -> Privacy and make sure that Automatic screen lock is OFF. 2. Suspend your machine 3. Resume your machine 4. Notice that the desktop is visible for a second, then the screen blanks, then the lock screen appears, then the screen blanks again. You are left at a black screen and need to unlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768786] Re: Screen is displayed when resuming from suspend
I can confirm this happens on Gnome, Budgie and Unity. -- 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/1768786 Title: Screen is displayed when resuming from suspend Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce and description: First test case - where things work correctly: 1. Open Settings-> Privacy and make sure that Automatic screen lock is ON. 2. Suspend your machine 3. Resume your machine 4. Notice that the lockscreen is shown on resume and that you can't see the desktop Second test case - where things are broken 1. Open Settings -> Privacy and make sure that Automatic screen lock is OFF. 2. Suspend your machine 3. Resume your machine 4. Notice that the desktop is visible for a second, then the screen blanks, then the lock screen appears, then the screen blanks again. You are left at a black screen and need to unlock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768637] Re: /etc/modprobe.d is not a file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1768637 Title: /etc/modprobe.d is not a file Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Hello, I noticed the following entries in my journal after upgrading to 18.04 LTS from 16.04 LTS: May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:31 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:31 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:33 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:33 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Start request repeated too quickly. May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Failed with result 'start-limit-hit'. The referenced dkms path does not exist: sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/dkms ls: cannot access '/lib/modules/4.15.0-20-generic/updates/dkms': No such file or directory sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/ ls: cannot access '/lib/modules/4.15.0-20-generic/updates/': No such file or directory sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/ total 5292 lrwxrwxrwx 1 root root 40 Apr 23 21:56 build -> /usr/src/linux-headers-4.15.0-20-generic drwxr-xr-x 2 root root4096 Apr 23 21:56 initrd drwxr-xr-x 15 root root4096 May 1 18:23 kernel -rw-r--r-- 1 root root 1253762 May 1 18:36 modules.alias -rw-r--r-- 1 root root 1235639 May 1 18:36 modules.alias.bin -rw-r--r-- 1 root root7594 Apr 23 21:56 modules.builtin -rw-r--r-- 1 root root9600 May 1 18:36 modules.builtin.bin -rw-r--r-- 1 root root 552117 May 1 18:36 modules.dep -rw-r--r-- 1 root root 780401 May 1 18:36 modules.dep.bin -rw-r--r-- 1 root root 317 May 1 18:36 modules.devname -rw-r--r-- 1 root
[Desktop-packages] [Bug 1768597] Re: package filemanager-actions missing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1768597 Title: package filemanager-actions missing Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus-actions was deprecated in favour of filemanager-actions. But 18.04 repositories do not have either of the packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768967] Re: Screen randomly flips 180 degrees
** Summary changed: - Screen randomly flips 180 degreese twice + Screen randomly flips 180 degrees ** Description changed: - I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen - will become flipped, go black for a second, and then return to normal. + I'm running Ubuntu 18.04 on an HP 350 G1 laptop. According to jstest- + gtk, the laptop has a ST LIS3LV02DL Accelerometer with three axes. Axes + 0 and 2 remain at 0 (center) no matter what I do. Axis 1 on the other + hand senses how much the base of the laptop (the lower half of the clam + shell, the part with the keyboard), is tilted. When the laptop is level, + the Axis's value should be 0, but it can be anywhere from -20 to 20 + while the laptop is being typed on. When its reading is above 0, the + screen flips. These two facts cause the screen to flip seemingly + randomly while it's being used. + + Workarround: Lock the screen orientation in GNOME. 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 3 15:53:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:21b7] + Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:21b7] InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: - Bus 001 Device 002: ID 8087:8000 Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 002: ID 8087:8000 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC 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=1a8b0eca-695f-444c-9cb1-558fe4916595 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 21B7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 46.0B dmi.chassis.asset.tag: Classis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd10/17/2014:svnHewlett-Packard:pnHPPavilion350G1NotebookPC:pvr05A620300:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=242 dmi.product.name: HP Pavilion 350 G1 Notebook PC dmi.product.version: 05A620300 dmi.sys.vendor: Hewlett-Packard 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 -- 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/1768967 Title: Screen randomly flips 180 degrees Status in xorg package in Ubuntu: New Bug description: I'm running Ubuntu 18.04 on an HP 350 G1 laptop. According to jstest- gtk, the laptop has a ST LIS3LV02DL
[Desktop-packages] [Bug 1583182] Re: error on 01ifupdown script
I had the problem of ubuntu-fan not being installed after the upgrade to 17.10/18.04, please mark ubuntu-fan as a dependency to NetworkManager or something to fix this. It was by pure chance I ended up here to find a way to debug this problem. -- 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/1583182 Title: error on 01ifupdown script Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: When bring the interface up or down I see this message on the logs May 18 10:03:36 count0 nm-dispatcher[8608]: req:1 'up' [enp2s0], "/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. May 18 10:03:36 count0 NetworkManager[791]: [1463576616.8466] dispatcher: (29) 01ifupdown failed (failed): Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. Tracing the problem I see that the call to /usr/sbin/fanctl is done with incorrect parameters. If I execute /etc/NetworkManager/dispatcher.d/01ifupdown enp2s0 down I get this error run-parts: /etc/network/if-post-down.d/ubuntu-fan exited with return code 1 ubuntu-fan is doing the call in following way /usr/sbin/fanctl net "$MODE" "$IFACE" and the parameters passed by ubuntu-fan are $MODE=stop $IFACE=enp2s0 but fanctl expect other parameters as showed on the script's header -- details lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.1.93-0ubuntu4 Version table: *** 1.1.93-0ubuntu4 500 500 http://ar.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 18 10:50:24 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-76f79dfb13e0 proto kernel scope link src 172.18.0.1 linkdown 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.8 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH br-76f79dfb13e0 bridgeconnected /org/freedesktop/NetworkManager/Devices/2 br-76f79dfb13e0 0a9f5c9b-cd67-4fb8-a72d-1811ca6fbb68 /org/freedesktop/NetworkManager/ActiveConnection/1 docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 e5f99f7d-532f-4c52-8749-c78afa9271dd /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 ee3ec6ee-7242-4956-9d19-20ccb19c5fe5 /org/freedesktop/NetworkManager/ActiveConnection/8 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1583182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
I am having the same problem with Ubuntu 18.04 LTS release -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions. Please see wall of text on comment 50 for a long excuse. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768967] [NEW] Screen randomly flips 180 degreese twice
Public bug reported: I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen will become flipped, go black for a second, and then return to normal. 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 3 15:53:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:21b7] InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC 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=1a8b0eca-695f-444c-9cb1-558fe4916595 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 21B7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 46.0B dmi.chassis.asset.tag: Classis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd10/17/2014:svnHewlett-Packard:pnHPPavilion350G1NotebookPC:pvr05A620300:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=242 dmi.product.name: HP Pavilion 350 G1 Notebook PC dmi.product.version: 05A620300 dmi.sys.vendor: Hewlett-Packard 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1768967 Title: Screen randomly flips 180 degreese twice Status in xorg package in Ubuntu: New Bug description: I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen will become flipped, go black for a second, and then return to normal. 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 3 15:53:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:21b7] InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=
[Desktop-packages] [Bug 1698393] Re: Missing words in translation
** Changed in: ubuntu-translations Status: Fix Committed => Fix Released ** Changed in: simple-scan (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1698393 Title: Missing words in translation Status in Ubuntu Translations: Fix Released Status in simple-scan package in Ubuntu: Fix Released Bug description: A lot of words are missing to be translated in the software. None of the "settings" are translatable and many other text aren't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1698393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
Defaults for xenial (samba 4.3.11): client min protocol = CORE client max protocol = default (which is NT1 in this version of samba) Defaults for artful (samba 4.6.7): client min protocol = CORE client max protocol = default (which is NT1 in this version of samba) Defaults for bionic (samba 4.7.6): client min protocol = CORE client max protocol = default (which is SMB3_11 in this version of samba) So before bionic, if you wanted a more secure protocol, you had to specify it (like smbclient's -m SMB3 option). Now in bionic, if you want a *less* secure protocol. you have to specify it. Ideally, computer browsing and actually connecting to shares should happen with different protocol versions. smbclient in bionic does a quick downgrade to NT1 when needed. Notice the "Reconnecting" message intertwined in the output below: ubuntu@bionic-desktop:~$ smbclient -L xenial -N -m SMB3 Anonymous login successful Sharename Type Comment - --- print$ Disk Printer Drivers public Disk Public share IPC$IPC IPC Service (xenial-desktop server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. Anonymous login successful Server Comment ---- WorkgroupMaster ---- UBUNTU XENIAL In artful, that downgrade does not happen, and we don't get the workgroup listing: ubuntu@artful-desktop:~$ smbclient -L xenial -N -m SMB3 Anonymous login successful Sharename Type Comment - --- print$ Disk Printer Drivers public Disk Public share IPC$IPC IPC Service (xenial-desktop server (Samba, Ubuntu)) Anonymous login successful Server Comment ---- WorkgroupMaster ---- ubuntu@artful-desktop:~$ I suspect smbtree does the same. In bionic, where max protocol is SMB3_11 by default, it works out of the box. But in artful, if I set client max protocol to SMB3_11, it stops working: ubuntu@artful-desktop:~$ testparm -s -v 2>/dev/null|grep "client max protocol" client max protocol = default ubuntu@artful-desktop:~$ smbtree UBUNTU \\XENIALxenial-desktop server (Samba, Ubuntu) \\XENIAL\IPC$ IPC Service (xenial-desktop server (Samba, Ubuntu)) \\XENIAL\public Public share \\XENIAL\print$ Printer Drivers \\BIONICbionic-desktop server (Samba, Ubuntu) \\BIONIC\IPC$ IPC Service (bionic-desktop server (Samba, Ubuntu)) \\BIONIC\public Public share \\BIONIC\print$ Printer Drivers \\ARTFULartful-desktop server (Samba, Ubuntu) \\ARTFUL\IPC$ IPC Service (artful-desktop server (Samba, Ubuntu)) \\ARTFUL\public Public share \\ARTFUL\print$ Printer Drivers ubuntu@artful-desktop:~$ sudo vi /etc/samba/smb.conf ubuntu@artful-desktop:~$ testparm -s -v 2>/dev/null|grep "client max protocol" client max protocol = SMB3 ubuntu@artful-desktop:~$ smbtree ubuntu@artful-desktop:~$ So in summay, bionic samba's own tools seem to know when NT1 is needed and downgrade appropriately. Ideally the rest of the smb ecosystem should do the same, assuming there is no way to get the computer listing with non-NT1 protocols. -- 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/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in gvfs: Confirmed Status in samba: Unknown Status in nautilus package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Besides the login problem (wrong first attempt to login, then right password ,leads to a purple screen and nothing else happens) there is another problem when you are in gnome-shell if you issue ctrl-alt f4 you cannot get back with ctrl-alt f7 -- 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: New Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: 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 1749007] Re: Snap mounts should be hidden from System Monitor
Hello Ads2, or anyone else affected, Accepted libgtop2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libgtop2/2.38.0-2ubuntu0.18.04.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: libgtop2 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1749007 Title: Snap mounts should be hidden from System Monitor Status in gnome-system-monitor package in Ubuntu: In Progress Status in libgtop2 package in Ubuntu: Fix Committed Status in libgtop2 source package in Bionic: Fix Committed Bug description: * Impact snaps mount at listed in the system monitor but they are an implementation detail and not interesting there. We already filter them out of the Disks UI, we should do the same in the system monitor * Test case - have a snap installed (wshich is true in the default installation of Ubuntu) - open gnome-system-monitor - check the filesystem tabs content, snaps mounts shouldn't be listed * Regression potential Check that the system mounted partitions are still correctly listed -- As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the snap mounts in System Monitor should be hidden just as they're hidden from GNOME Disks. Perhaps they should be grouped under a dropdown of / (though this would require developing a new feature)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Fix for ubiquity proposed here:
https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in glib2.0 package in Ubuntu:
Invalid
Status in ubiquity package in Ubuntu:
In Progress
Status in cairo source package in Bionic:
In Progress
Status in glib2.0 source package in Bionic:
Invalid
Status in ubiquity source package in Bionic:
In Progress
Bug description:
The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
it was working some weeks/months ago, so this is a recent regression.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
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: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
Hello helboof, or anyone else affected, Accepted gnome-session into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- session/3.28.1-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-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: gnome-session (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed Status in gnome-session package in Ubuntu: Triaged Status in gnome-session source package in Bionic: Fix Committed Bug description: [Impact] * People having this particular setup: - removed ubuntu-desktop metapackage from their system - upgrading from 16.04 to 18.04 (or previously to 17.10) by manually editing /etc/apt/sources.lists without using do-release-upgrade (which reinstalls ubuntu-desktop). They end up with: - no ubuntu-dock installed - and consequentely, the settings migration script would trigger an apport dialog (crashing) due to lack of gsettings schema. * Even if this is an unsupported case (people shouldn't cowboy sources.list and use our upgrader tools), we can easily prevent this crash, ignoring settings migration in such a case. [Test Case] 1. Install 16.04 2. Remove ubuntu-desktop metapackage 3. Change your sources.list from "xenial" to "bionic" 4. apt update && apt full-upgrade 5. Reboot and log into a new session once upgrade is done. -> you won't get the ubuntu-dock, but the session migration script shouldn't crash. [Regression Potential] * The script was crashing (even if there is no settings to migrate, so it was a no-op). We prevents gsettings to segfault by guarding for schema existence in the standard way. -- Upgrade... ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 08:15:13 2017 ExecutablePath: /usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py InstallationDate: Installed on 2017-09-25 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py ProcEnviron: LANGUAGE=ru PATH=(custom, user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 Signal: 5 SourcePackage: gnome-session StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() 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-session/+bug/1720310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1701289] Re: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat()
** Changed in: gtk Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1701289 Title: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat() Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/fb179bc620e408d216f4b8700f714e6ebb2ebf09 --- cant login to gnome desktop ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 29 16:14:29 2017 DisplayManager: lightdm EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-03-25 (96 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=sv PATH=(custom, user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XIGetClientPointer () at /usr/lib/x86_64-linux-gnu/libXi.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1701289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768918] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
*** This bug is a duplicate of bug 1762827 *** https://bugs.launchpad.net/bugs/1762827 ** This bug has been marked a duplicate of bug 1762827 package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 -- 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/1768918 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: This issue popped up while installing WineHQ ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Thu May 3 23:01:51 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-14TGSm/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-04-12 (21 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 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/1768918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768929] [NEW] Ubuntu Welcome wizard shouldn't show at next login if user closes it
Public bug reported: Impact -- If a user closes the Welcome to Ubuntu wizard before completing it, it will still automatically start the next time the user logs in. This can be annoying so we're fixing it. Test Case -- 1. Install Ubuntu 18.04 LTS 2. Restart and log in. 3. The Welcome to Ubuntu wizard appears. Close it by either doing: a. Right Click on the icon in the Dock on the left and select Quit, or b. Click "Welcome to Ubuntu" in the top bar to open the app menu and then select Quit. 4. Log out. 5. Log back in. The Welcome to Ubuntu wizard should not start. Regression Potential Since none of the pages in the Welcome to Ubuntu wizard are mandatory, it is harmless for it to be ignored. Our patch also was careful to not change the "new user" mode which isn't really used in Ubuntu. See LP: #1762287 for details about that mode. Other Info -- We decided to apply this change even in the GNOME session. Ubuntu GNOME 17.04 included gnome-initial-setup by default. GNOME upstream at this time likes the feature where the wizard will show up on next login until it is completed. https://gitlab.gnome.org/Community/Ubuntu/gnome-initial- setup/merge_requests/1 ** Affects: gnome-initial-setup (Ubuntu) Importance: Low Status: Fix Committed ** Affects: gnome-initial-setup (Ubuntu Bionic) Importance: Low Status: In Progress ** Tags: bionic ** Also affects: gnome-initial-setup (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-initial-setup (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: gnome-initial-setup (Ubuntu Bionic) Status: New => In Progress -- 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/1768929 Title: Ubuntu Welcome wizard shouldn't show at next login if user closes it Status in gnome-initial-setup package in Ubuntu: Fix Committed Status in gnome-initial-setup source package in Bionic: In Progress Bug description: Impact -- If a user closes the Welcome to Ubuntu wizard before completing it, it will still automatically start the next time the user logs in. This can be annoying so we're fixing it. Test Case -- 1. Install Ubuntu 18.04 LTS 2. Restart and log in. 3. The Welcome to Ubuntu wizard appears. Close it by either doing: a. Right Click on the icon in the Dock on the left and select Quit, or b. Click "Welcome to Ubuntu" in the top bar to open the app menu and then select Quit. 4. Log out. 5. Log back in. The Welcome to Ubuntu wizard should not start. Regression Potential Since none of the pages in the Welcome to Ubuntu wizard are mandatory, it is harmless for it to be ignored. Our patch also was careful to not change the "new user" mode which isn't really used in Ubuntu. See LP: #1762287 for details about that mode. Other Info -- We decided to apply this change even in the GNOME session. Ubuntu GNOME 17.04 included gnome-initial-setup by default. GNOME upstream at this time likes the feature where the wizard will show up on next login until it is completed. https://gitlab.gnome.org/Community/Ubuntu/gnome-initial- setup/merge_requests/1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1768929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768918] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
** Tags removed: need-duplicate-check -- 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/1768918 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: This issue popped up while installing WineHQ ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Thu May 3 23:01:51 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-14TGSm/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-04-12 (21 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 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/1768918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768918] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o
Public bug reported: This issue popped up while installing WineHQ ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Thu May 3 23:01:51 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-14TGSm/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-04-12 (21 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- 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/1768918 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: This issue popped up while installing WineHQ ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Thu May 3 23:01:51 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-14TGSm/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-04-12 (21 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) 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: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 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/1768918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
Andreas Hasenack, my server is nas4free (https://www.nas4free.org/) running Samba version 4.7.6 smbstatus shows the connection with ubuntu 18.04 as SMB3_11. ubuntu 17.10 would use NT1 by default. so with 18.04 I would need to got to other "locations/connect to server" and enter smb://server to be able to list and browse the shares. if I want them to be automatically listed in "other locations" or "windows network" i would need to downgrade the client protocol to NT1 with "client max protocol = NT1" on the client conf. -- 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/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in gvfs: Confirmed Status in samba: Unknown Status in nautilus package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768906] Re: Xorg crash
Same thing happens with nvidia-346. -- 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/1768906 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When attempting to log in to a newly updated bionic beaver via the display manager (I think this is the right term), I immediately see a crash, a return to the user selection/login screen and a no-longer functioning keyboard and mouse. This happens both with the proprietary driver installed drivers and with the apt installed nvidia-driver-396. some interesting tidbits from the syslog file are: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): Failing initialization of X screen 0 May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: "nvidia" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "wfb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "fb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) found, but none have a usable configuration. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens found(EE) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 09:28:59 2018 DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774] MachineType: ASUS All Series 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-lowlatency root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Thu May 3 09:20:03 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 1515561] Re: Windows flash black briefly before being drawn
** Changed in: gtk Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1515561 Title: Windows flash black briefly before being drawn Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Since 3.18, windows flash black for a split second before they are drawn. It's visually disruptive. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1515561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
What are your servers? I can't get windows 10 or 2016 server to show up not even in artful (17.10). -- 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/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in gvfs: Confirmed Status in samba: Unknown Status in nautilus package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Try this: https://launchpad.net/~lubomir-brindza/+archive/ubuntu /nautilus-typeahead The changes are based on the patch from Arch community, with slight modifications to work on 3.26.3 release. -- 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/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I have managed to work nvidia binary drivers version 340.102 with kernel 4.15 with patch https://pastebin.com/raw/fVJVvQy7 , which is mentioned on https://devtalk.nvidia.com/default/topic/1026911/linux/4-15-rc1 -patches-for-384-98-and-340-104. My nvidia m720 graphics is working again on Ubuntu 18.04. 1. Install prerequisites # apt-get install build-essential libc6:i386 2. Download nvidia binary drivers from http://www.nvidia.com/content /DriverDownload-March2009/confirmation.php?url=/XFree86/Linux- x86_64/340.104/NVIDIA-Linux-x86_64-340.104.run=us=TITAN 3. Download patch for nvidia binary drivers in same directory # wget -O nv_patch_340.104_linux_kernel_4.15 https://pastebin.com/raw/fVJVvQy7 4. Boot ubuntu in single mode https://linuxconfig.org/how-to-boot- ubuntu-18-04-into-emergency-and-rescue-mode (How to access emergency.target at boot) 5. Enter root password 6. Unload nouveau driver # rmmod nouveau 7. Blacklist nouveau driver # echo "blacklist nouveau" > /etc/modprobe.d/blacklist-nouveau.conf # echo "options nouveau modeset=0" >> /etc/modprobe.d/blacklist-nouveau.conf File /etc/modprobe.d/blacklist-nouveau.conf should have following entries: blacklist nouveau options nouveau modeset=0 8. Update initial ramdisk # update-initramfs -u 9. Go to directory which contains downloaded nvidia-340 binary driver and set executable attribute # chmod +x NVIDIA-Linux-x86_64-340.104.run 10. Apply the patch to driver (maybe this could be done after downloading kernel 4.15 patch - have not tried it ...) # ./NVIDIA-Linux-x86_64-340.104.run --apply-patch nv_patch_340.104_linux_kernel_4.15 This will build custom NVIDIA binary driver package with name NVIDIA- Linux-x86_64-340.104-custom.run 11. Set executable attribute for custom driver package # chmod +x NVIDIA-Linux-x86_64-340.104-custom.run 12. Install the driver with command # ./NVIDIA-Linux-x86_64-340.104-custom.run Ignore errors and enable DKMS 13. Reboot computer # reboot Nvidia driver 340.120 should be loaded now and graphics fully working. This method is to complicated so I will also try methods mention in #112 and #113. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
Sebastien Bacher, I am not sure if it is documented anywhere? I did notice that by default nautilus connects with smb3_11 to my server. thats good because it uses a more secure protocol but it breaks network browsing. if you downgrade to NT1 like I mentioned above it will work again but with a lower protocol. -- 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/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in gvfs: Confirmed Status in samba: Unknown Status in nautilus package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1767454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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)
Work around does not work for. It is not about nvidia driver. Lets face it, it is a showstopper for ubuntu 18.04 until bug is 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: New Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: 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 1768906] Re: Xorg crash
With that card, use nvidia-331 or 346 instead. ** 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/1768906 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When attempting to log in to a newly updated bionic beaver via the display manager (I think this is the right term), I immediately see a crash, a return to the user selection/login screen and a no-longer functioning keyboard and mouse. This happens both with the proprietary driver installed drivers and with the apt installed nvidia-driver-396. some interesting tidbits from the syslog file are: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): Failing initialization of X screen 0 May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: "nvidia" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "wfb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "fb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) found, but none have a usable configuration. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens found(EE) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 09:28:59 2018 DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774] MachineType: ASUS All Series 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-lowlatency root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Thu May 3 09:20:03 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1768912] [NEW] Wifi connection drops regularly
Public bug reported: Description: A few times an hour the networking drops for around 20 seconds. It then automatically reconnects. The only clearly related message in journalctl is the DHCPREQUEST / DCHPACK followed the messages: Starting Network Manager Script Dispatcher Service... bound to X.X.X.X -- renewal in 1692 seconds. [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Started Network Manager Script Dispatcher Service. req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts) req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts... That makes me think that Network Manager silently died and was restarted. Notes: * The system is a new Dell Precision 5520 with a Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) * This system started as a clean install of Ubuntu 18.04 Beta on March 31, 2018 * The wireless networking was stable from install until a system update on April 27, 2018 * The wired networking is completely stable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 10:36:25 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-31 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180331) IpRoute: default via 10.4.0.1 dev wlp2s0 proto dhcp metric 600 10.4.0.0/20 dev wlp2s0 proto kernel scope link src 10.4.3.151 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Evernym c5f3aef0-8286-4268-a8e4-7b7272491d34 /org/freedesktop/NetworkManager/ActiveConnection/1 enx1065308d9647 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- 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 started full enabled enabled enabled enabled disabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1768912 Title: Wifi connection drops regularly Status in network-manager package in Ubuntu: New Bug description: Description: A few times an hour the networking drops for around 20 seconds. It then automatically reconnects. The only clearly related message in journalctl is the DHCPREQUEST / DCHPACK followed the messages: Starting Network Manager Script Dispatcher Service... bound to X.X.X.X -- renewal in 1692 seconds. [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Started Network Manager Script Dispatcher Service. req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts) req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts... That makes me think that Network Manager silently died and was restarted. Notes: * The system is a new Dell Precision 5520 with a Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) * This system started as a clean install of Ubuntu 18.04 Beta on March 31, 2018 * The wireless networking was stable from install until a system update on April 27, 2018 * The wired networking is completely stable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 10:36:25 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-31 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180331) IpRoute: default via 10.4.0.1 dev wlp2s0 proto dhcp metric 600 10.4.0.0/20 dev wlp2s0 proto kernel
[Desktop-packages] [Bug 1768906] [NEW] Xorg crash
Public bug reported: When attempting to log in to a newly updated bionic beaver via the display manager (I think this is the right term), I immediately see a crash, a return to the user selection/login screen and a no-longer functioning keyboard and mouse. This happens both with the proprietary driver installed drivers and with the apt installed nvidia-driver-396. some interesting tidbits from the syslog file are: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): Failing initialization of X screen 0 May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: "nvidia" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "wfb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: "fb" May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) found, but none have a usable configuration. May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error: May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens found(EE) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 09:28:59 2018 DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774] MachineType: ASUS All Series 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-lowlatency root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Thu May 3 09:20:03 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic crash possible-manual-nvidia-install third-party-packages 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/1768906 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When attempting to log in to a newly updated bionic beaver via the display manager (I think this is the right term), I immediately see a crash, a return to the user selection/login
[Desktop-packages] [Bug 1768755] Re: Missing links to libGL.so and libglapi.so
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1768755 Title: Missing links to libGL.so and libglapi.so Status in mesa package in Ubuntu: New Bug description: In Ubuntu 18.04, the package libgl1-mesa-dev:amd64 does not contain the symbolic links libGL.so and libglapi.so. Thus, it is not possible to use the -lGL option to compile a program... System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit Package: libgl1-mesa-dev:amd64 18.0.0~rc5-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1598295] Re: $GTK_IM_MODULE ignored after upgrade
** Changed in: gtk Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1598295 Title: $GTK_IM_MODULE ignored after upgrade Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Triaged Bug description: After upgrade trusty → xenial, Compose key stopped producing configured through ~/.XCompose characters for GTK3 only apps. To be sure that its the GTK problem, I created a simple GTK3 window with textbox, launched it like: $ GTK_IM_MODULE=xim XMODIFIERS=@im=none ./a and the textbox produces wrong characters for Compose key. (the variables are actually set globally, I wrote them here just for clarity). XCompose works fine for all other toolkit's apps, including GTK2 and Qt ones. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy libgtk-3-0 libgtk-3-0: Installed: 3.18.9-1ubuntu3 Candidate: 3.18.9-1ubuntu3 Version table: *** 3.18.9-1ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen «Compose + - + space» would produce «— » in GTK3 apps. 4) What happened instead «Compose + - + space» producing «~» in GTK3 apps. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1598295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
I kind of figured this out. In addition to Tracker, you need Gnome Documents and gnome-shell-extensions installed. Launch Gnome Documents, and it will index your files. Now you will be able to search by content from Gnome Documents and Gnome Shell, but still not from Nautilus. Perhaps this is because Ubuntu installs an older version of Nautilus (3.26). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Confirmed Bug description: Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input
** Changed in: gtk Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1719043 Title: Gnome web urlbar very slow to show typed input Status in GTK+: Expired Status in epiphany-browser package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gtk+3.0 source package in Artful: Invalid Status in mutter source package in Artful: Fix Released Status in gtk+3.0 package in Debian: Fix Released Bug description: Impact == It is very difficult to use the address bar in Epiphany on GNOME on Wayland because after a few characters, the address bar field stops redrawing. (This apparently was triggered by mutter 3.26?) Test Case = sudo apt install epiphany-browser Open the Web app Type a URL into the address bar. Type a lng URL. You should see all the characters you type into the address bar. Regression Potential === To fix this issue, an optimization commit applied earlier in 3.26 development was reverted. This fix is part of mutter 3.26.2 (LP: #1730097). Other Info == The first SRU gtk+3.0 3.22.24-0ubuntu2 caused a regression seen in totem and so was reverted in both gtk upstream and in the next SRU 3.22.25-0ubuntu0.1 Instead, this is being fixed in mutter. Original Bug Report === First two characters typed in urlbar show immediately, other characters take up to 30 seconds to appear, or url will appear in full once enter key is pressed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: epiphany-browser 3.26.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 18:42:19 2017 InstallationDate: Installed on 2017-09-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1719043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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)
Sum Sim Not sure it is the Nvidia driver, I have had the same problem on both the Nvidia-390 and the X-org Nouveau display driver. There seems to be a lot of talk about error occurring with incorrect password input, this is inconsistent with my experience. The best workaround I have seen so far is mentioned by Wayne Carr (above), rather than log-out when switching users, use the switch-user option. This obviously leaves all profiles active but the fault does not occur. -- 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: New Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: 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
