[Desktop-packages] [Bug 643536] Re: Can't drag and drop mails to desktop as file
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/643536 Title: Can't drag and drop mails to desktop as file Status in thunderbird package in Ubuntu: Expired Bug description: When i try to drag a mail to my desktop from the inbox, i get the following error message. (Translated from Danish) Error copying. An error ocured when gathering information about "fetch>UID>.INBOX.Sent>2897". - Show more details The specified location is not supported [Cancel] [Skip all] [Skip] [Try again] This error was observed with Thunderbird 3.0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/643536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()
** Patch added: "debdiff adding upstream patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5191867/+files/network-manager_1.12.2-0ubuntu4_lp1792745.debdiff -- 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/1792745 Title: NetworkManager crashed with SIGSEGV in _int_malloc() Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I’m seeing NetworkManager crash several times on startup and on resume from suspend. Apport doesn’t catch those for some reason, but this happened when I tried to reproduce by manually running NetworkManager --debug. (Different crash from bug 1792743? Also apport-retrace didn’t seem to like that one.) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Sat Sep 15 14:04:50 2018 EcryptfsInUse: Yes ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. Do not edit. InstallationDate: Installed on 2016-02-19 (939 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcCmdline: NetworkManager --debug SegvAnalysis: Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp %rcx,0x18(%rdx) PC (0x7f79966ea378) ok source "%rcx" ok destination "0x18(%rdx)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: _int_malloc (av=av@entry=0x7f799683ac40 , bytes=bytes@entry=4096) at malloc.c:4014 __libc_calloc (n=, elem_size=) at malloc.c:3420 g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314 _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88 Title: NetworkManager crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1792745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()
-- 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/1792745 Title: NetworkManager crashed with SIGSEGV in _int_malloc() Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I’m seeing NetworkManager crash several times on startup and on resume from suspend. Apport doesn’t catch those for some reason, but this happened when I tried to reproduce by manually running NetworkManager --debug. (Different crash from bug 1792743? Also apport-retrace didn’t seem to like that one.) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Sat Sep 15 14:04:50 2018 EcryptfsInUse: Yes ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. Do not edit. InstallationDate: Installed on 2016-02-19 (939 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcCmdline: NetworkManager --debug SegvAnalysis: Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp %rcx,0x18(%rdx) PC (0x7f79966ea378) ok source "%rcx" ok destination "0x18(%rdx)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: _int_malloc (av=av@entry=0x7f799683ac40 , bytes=bytes@entry=4096) at malloc.c:4014 __libc_calloc (n=, elem_size=) at malloc.c:3420 g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314 _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88 Title: NetworkManager crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1792745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
@Timo: This seems to be a reason to upgrade xkeyboard-config in Debian (and then Ubuntu) to 2.24. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Following upstream suggestion ** Package changed: gnome-settings-daemon (Ubuntu) => xkeyboard-config (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793918] Re: Setting to enable suspend on lid-close with external monitors attached
** Description changed: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems - to have no effect anymore and seems to be removed in the current scheme. + to have no effect anymore and seems to be removed in the current scheme + (repatched in ubuntu's version only). This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. - - As a realy bad workaround I now prevent gsd-power from beeing loaded at - all by "chmod a-x /usr/lib/gnome-settings-daemon/gsd-power". Of course - this have some unwanted side effect but better to have no suspend on - lid-close. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1793918 Title: Setting to enable suspend on lid-close with external monitors attached Status in gnome-settings-daemon package in Ubuntu: New Bug description: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme (repatched in ubuntu's version only). This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1793918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
>From the upstream report: "A possible explanation would be that gnome-settings-daemon is not handling one of the keys that it should be handling. And gnome-settings-daemon also disables the kernels handling of the RFKill keys at the same time. What you could do: Check which key is emitted using "xev" Check the low level key that is fired using "evemu-record" (you'll need to try different input devices) To be honest, the most likely explanation is that the following xkeyboard-config bugfix has not been merged into ubuntu yet: https://bugs.freedesktop.org/show_bug.cgi?id=100970, patch https://patchwork.freedesktop.org/patch/155965/ which should be in 2.24." And: "Just to make this clear. The above means that this is likely a downstream bug in Ubuntu which needs to upgrade (or patch) xkeyboard-config. i.e. if "XF86RFKill" is not mapped, then xkeyboard-config is outdated and the symptoms you describe fit perfectly." The "xev" output that I get is: KeyPress event, serial 38, synthetic NO, window 0x381, root 0x1a8, subw 0x0, time 1318232, (131,-31), root:(1962,997), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 38, synthetic NO, window 0x381, root 0x1a8, subw 0x0, time 1318232, (131,-31), root:(1962,997), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ** Bug watch added: freedesktop.org Bugzilla #100970 https://bugs.freedesktop.org/show_bug.cgi?id=100970 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in gnome-settings-daemon package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1
[Desktop-packages] [Bug 1793918] [NEW] Setting to enable suspend on lid-close with external monitors attached
Public bug reported: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme. This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. As a realy bad workaround I now prevent gsd-power from beeing loaded at all by "chmod a-x /usr/lib/gnome-settings-daemon/gsd-power". Of course this have some unwanted side effect but better to have no suspend on lid-close. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Description changed: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme. This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. + + As a realy bad workaround I now prevent gsd-power from beeing loaded at + all by "chmod a-x /usr/lib/gnome-settings-daemon/gsd-power". Of course + this have some unwanted side effect but better to have no suspend on + lid-close. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1793918 Title: Setting to enable suspend on lid-close with external monitors attached Status in gnome-settings-daemon package in Ubuntu: New Bug description: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme. This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. As a realy bad workaround I now prevent gsd-power from beeing loaded at all by "chmod a-x /usr/lib/gnome-settings-daemon/gsd-power". Of course this have some unwanted side effect but better to have no suspend on lid-close. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1793918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
In the upstream report for gnome-shell (https://gitlab.gnome.org/GNOME /gnome-shell/issues/555) some analysis steps were kindly provided. It seems that the actual cause is that gnome-settings-daemon's rfkill plugin fails to turn on airplane mode. Following the instructions, I can turn it on with the suggested test command: gdbus call --session --dest org.gnome.SettingsDaemon.Rfkill \ --object-path /org/gnome/SettingsDaemon/Rfkill \ --method org.freedesktop.DBus.Properties.Set \ org.gnome.SettingsDaemon.Rfkill AirplaneMode '' '' turns if off again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in gnome-settings-daemon package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
As per analysis result in upstream report ** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in gnome-settings-daemon package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758918] Re: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh
Yeah - 1:0.28.2-5ubuntu4 should be the package version of libvte - so I guess you must have installed a PPA with a later version. You should have purged the PPA first before installing budgie ** Changed in: budgie-desktop (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1758918 Title: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh Status in budgie-desktop package in Ubuntu: Invalid Status in vte2.91 package in Ubuntu: Expired Bug description: After upgrading libvte to latest release, When installing deb with gdebi, it shows following error: unable to read filedescriptor flags for https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1758918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+ (and 18.04 LTS)
I've recently had the same problem of vertical black stripes on scans from my Canon imageCLASS MF244DW under Ubuntu 18.04.1. Compiling and installing sane-backends from https://github.com/kkaempf/sane-backends solved the problem. -- 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/1731459 Title: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+ (and 18.04 LTS) Status in sane-backends package in Ubuntu: Confirmed Bug description: On Windows it works but on my Ubuntu 17.10 I see a black band on scanned image. The scanner is Canon CanoScan LIDE100. Libsane version is 1.0.27-1~experimental2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758918] Re: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh
It appears libvte-common was somehow stuck at 2.90 on my system, even though a newer one was available. My guess is that this was from a PPA. ** Changed in: budgie-desktop (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1758918 Title: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh Status in budgie-desktop package in Ubuntu: Incomplete Status in vte2.91 package in Ubuntu: Expired Bug description: After upgrading libvte to latest release, When installing deb with gdebi, it shows following error: unable to read filedescriptor flags for https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1758918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758918] Re: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh
I've got an issue that may be the same or related, but is occurring on install: ``` dpkg: error processing archive /var/cache/apt/archives/budgie-desktop-common_0.9.9ubuntu1_all.deb (--unpack): trying to overwrite '/etc/profile.d/vte.sh', which is also in package libvte-2.90-common 1:0.36.3-1ubuntu2 ``` ..does this provide the missing info needed to fix this bug, or is this unrelated? ** Changed in: budgie-desktop (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1758918 Title: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh Status in budgie-desktop package in Ubuntu: Incomplete Status in vte2.91 package in Ubuntu: Expired Bug description: After upgrading libvte to latest release, When installing deb with gdebi, it shows following error: unable to read filedescriptor flags for https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1758918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774560] Re: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child")
Is this a bug in mutter that has been fixed ? As I'm wondering why this bug is still open for xdg-desktop-portal-gtk and if it can be closed ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1774560 Title: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") Status in mutter package in Ubuntu: Fix Released Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: When running on a Wayland session, if xdg-desktop-portal-gtk is asked to display a window on behalf of a Wayland app, it gets disconnected from gnome-shell with one of these messages: Gdk-Message: 09:49:31.837: Lost connection to Wayland compositor. Gdk-Message: 09:50:28.438: Error 71 (Protocol error) dispatching to Wayland display. Running it with WAYLAND_DEBUG=1, the underlying error message that GDK seems to eat is: [3471970.531] wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") That is, when it tries to associate the dialog box with the confined application's window. It seems the underlying bug is in in Mutter: https://gitlab.gnome.org/GNOME/mutter/issues/138 According to duflu, the patch referenced in that bug report has been merged for 3.28.2 and 3.29.2. It seems like a candidate to backport to bionic if we want portals to work on the (non-default) Wayland session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1774560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793902] Re: package xserver-xorg-video-radeon 1:18.0.1-1 failed to install/upgrade: tentative de remplacement de « /usr/share/X11/xorg.conf.d/10-radeon.conf », qui appartient
Whoops, sorry, just noticed that it was related to Padoka's PPA, might be a few days old (I'm currently testing stuff to identify an issue with Mesa). I assume it's an issue with the PPA, bug report can likely be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1793902 Title: package xserver-xorg-video-radeon 1:18.0.1-1 failed to install/upgrade: tentative de remplacement de « /usr/share/X11/xorg.conf.d/10-radeon.conf », qui appartient aussi au paquet xserver-xorg-video-ati 1:18.0.99+git1809140020.2d58830~b~padoka0 Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Got this error randomly after an upgrade (not sure if it was after adding the Ubuntu-x-swat PPA or because of a previous upgrade of Mesa from the Ubuntu repos). Looks like there's a package issue with two xorg packages (ati and radeon) having a common config file. Using Ubuntu (MATE) 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-radeon 1:18.0.1-1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 18 12:14:39 2018 DistUpgraded: 2018-04-27 11:05:22,902 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-33-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed ErrorMessage: tentative de remplacement de « /usr/share/X11/xorg.conf.d/10-radeon.conf », qui appartient aussi au paquet xserver-xorg-video-ati 1:18.0.99+git1809140020.2d58830~b~padoka0 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1458:2556] MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=a7fa7861-a59a-4ae7-a396-d409348839be ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: xserver-xorg-video-ati Title: package xserver-xorg-video-radeon 1:18.0.1-1 failed to install/upgrade: tentative de remplacement de « /usr/share/X11/xorg.conf.d/10-radeon.conf », qui appartient aussi au paquet xserver-xorg-video-ati 1:18.0.99+git1809140020.2d58830~b~padoka0 UpgradeStatus: Upgraded to bionic on 2018-04-27 (148 days ago) dmi.bios.date: 10/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: GA-880GM-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd10/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GM-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.1.5-1ubuntu1~18.04.0~ppa1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1~18.04.0~ppa1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1793902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793902] [NEW] package xserver-xorg-video-radeon 1:18.0.1-1 failed to install/upgrade: tentative de remplacement de « /usr/share/X11/xorg.conf.d/10-radeon.conf », qui appartien
Public bug reported: Got this error randomly after an upgrade (not sure if it was after adding the Ubuntu-x-swat PPA or because of a previous upgrade of Mesa from the Ubuntu repos). Looks like there's a package issue with two xorg packages (ati and radeon) having a common config file. Using Ubuntu (MATE) 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-radeon 1:18.0.1-1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 18 12:14:39 2018 DistUpgraded: 2018-04-27 11:05:22,902 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-33-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed ErrorMessage: tentative de remplacement de « /usr/share/X11/xorg.conf.d/10-radeon.conf », qui appartient aussi au paquet xserver-xorg-video-ati 1:18.0.99+git1809140020.2d58830~b~padoka0 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1458:2556] MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=a7fa7861-a59a-4ae7-a396-d409348839be ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: xserver-xorg-video-ati Title: package xserver-xorg-video-radeon 1:18.0.1-1 failed to install/upgrade: tentative de remplacement de « /usr/share/X11/xorg.conf.d/10-radeon.conf », qui appartient aussi au paquet xserver-xorg-video-ati 1:18.0.99+git1809140020.2d58830~b~padoka0 UpgradeStatus: Upgraded to bionic on 2018-04-27 (148 days ago) dmi.bios.date: 10/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: GA-880GM-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd10/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GM-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.1.5-1ubuntu1~18.04.0~ppa1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1~18.04.0~ppa1 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 ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1793902 Title: package xserver-xorg-video-radeon 1:18.0.1-1 failed to install/upgrade: tentative de remplacement de « /usr/share/X11/xorg.conf.d/10-radeon.conf », qui appartient aussi au paquet xserver-xorg-video-ati 1:18.0.99+git1809140020.2d58830~b~padoka0 Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Got this error randomly after an upgrade (not sure if it was after adding the Ubuntu-x-swat PPA or because of a previous upgrade of Mesa from the Ubuntu repos). Looks like there's a package issue with two xorg packages (ati and radeon) having a common config file. Using Ubuntu (MATE) 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-radeon 1:18.0.1-1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 18 12:14:39 2018 DistUpgraded: 2018-04-27 11:05:22,902 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec
[Desktop-packages] [Bug 1793900] [NEW] NO HDMI Sound Working ! but not after Suspend! Help
Public bug reported: upload=true&script=true&cardinfo= !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Sun Sep 16 13:13:04 UTC 2018 !!Linux Distribution !!-- Ubuntu 18.04.1 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: OMEN X by HP Laptop 17-ap0xx Product Version: Firmware Version: F.18 Board Vendor: HP Board Name:83A5 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC0003:00/status 15 /sys/bus/acpi/devices/HPIC0004:00/status 15 /sys/bus/acpi/devices/HPQ6007:00/status 15 /sys/bus/acpi/devices/HPQ8001:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status 15 /sys/bus/acpi/devices/INT3400:00/status 15 /sys/bus/acpi/devices/INT3403:00/status 15 /sys/bus/acpi/devices/INT3403:01/status 15 /sys/bus/acpi/devices/INT3403:02/status 15 /sys/bus/acpi/devices/INT3403:03/status 15 /sys/bus/acpi/devices/INT340E:00/status 15 /sys/bus/acpi/devices/INT345D:00/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0C02:01/status 15 /sys/bus/acpi/devices/PNP0C02:03/status 3 /sys/bus/acpi/devices/PNP0C02:05/status 3 /sys/bus/acpi/devices/PNP0C04:00/status 31 /sys/bus/acpi/devices/PNP0C09:00/status 15 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0C:00/status 15 /sys/bus/acpi/devices/PNP0C0F:00/status 9 /sys/bus/acpi/devices/PNP0C0F:01/status 9 /sys/bus/acpi/devices/PNP0C0F:02/status 9 /sys/bus/acpi/devices/PNP0C0F:03/status 9 /sys/bus/acpi/devices/PNP0C0F:04/status 9 /sys/bus/acpi/devices/PNP0C0F:05/status 9 /sys/bus/acpi/devices/PNP0C0F:06/status 9 /sys/bus/acpi/devices/PNP0C0F:07/status 9 /sys/bus/acpi/devices/SYN3265:00/status 15 /sys/bus/acpi/devices/device:11/status 15 /sys/bus/acpi/devices/device:72/status 15 /sys/bus/acpi/devices/device:81/status 11 !!Kernel Information !!-- Kernel release:4.15.0-35-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k4.15.0-35-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdc628000 irq 137 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0403: 8086:a171 (rev 31) (prog-if 80) Subsystem: 103c:83a5 !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
[Desktop-packages] [Bug 1741027] Re: [FFE] Screen sharing panels abort using an non-existent vino gsettings key
I'm confused. Is this patch rolled out? I'm getting this issue. Has it really been impossible to VNC into an upgraded Ubuntu for over eight months? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: [FFE] Screen sharing panels abort using an non-existent vino gsettings key Status in unity-control-center package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Status in vino package in Ubuntu: Invalid Bug description: [FFE] This happens because Gnome removed that particular gsettings key. The removal did not happen with the ui removal but rather much later than that. That is why it doesn't work with the latest version of vino. As of now If users try to open the new sharing panel, unity-control- center will crash. This sort behavior is not desired on LTS release (18.04). The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793885] Re: additional drivers : change from nvidia-driver-390 to nvidia-340
*** This bug is a duplicate of bug 1783629 *** https://bugs.launchpad.net/bugs/1783629 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 #1783629, 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 ** This bug has been marked a duplicate of bug 1783629 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3. sudo password correct. if something else info necessary mail me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1793885 Title: additional drivers : change from nvidia-driver-390 to nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: application additional drivers : Change from nvidia-driver-390 to nvidia-340 apply ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 22 16:30:12 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.106-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2018-04-30 (145 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1793885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792807] Re: Login screen freeze
I've solved it for me now with a new graphics card. Couldn't bare the nomodeset anymore knowing there was an alternative solution. Imagine how much I am attached to Ubuntu to rather buy a new graphics card then to switch to another OS ;-). We can keep it open if you want further investigation and it might help with others. For me personally it is solved with the new graph card, so it can be closed as well. Up to you :-) -- 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/1792807 Title: Login screen freeze Status in gnome-shell package in Ubuntu: New Bug description: Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is frozen. I tried both gdm3 and lightdm login managers, with either I don't get into the system. I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD Graphics 2000. I have an external 24" ASUS display connected with VGA (tried HDMI as well but same problem). UPDATE: I now use "nomodeset" since that is the only way to get into the system. However, graphics are low and there's only 1 screen resolution available (1280x1024) which does not suit my screen at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 16 18:16:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-09-15 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. H67M-UD2H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 11/12/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: H67M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/12/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1809150630.283282~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1809160730.149768~oibaf~b 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.1.0+git1809141934.80514b~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1809061934.25c9a2~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793885] [NEW] additional drivers : change from nvidia-driver-390 to nvidia-340
*** This bug is a duplicate of bug 1783629 *** https://bugs.launchpad.net/bugs/1783629 Public bug reported: application additional drivers : Change from nvidia-driver-390 to nvidia-340 apply ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 22 16:30:12 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.106-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2018-04-30 (145 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1793885 Title: additional drivers : change from nvidia-driver-390 to nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: application additional drivers : Change from nvidia-driver-390 to nvidia-340 apply ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 22 16:30:12 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.106-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2018-04-30 (145 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1793885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
Never mind my previous question #22. I just had to enable the use of bionic-proposal, then the procedures worked. However, they generated a number of worrisome error messages. In any case, I am now able to use apt on my system again. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libgles1 The following packages will be upgraded: libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 libopengl0 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 268 kB of archives. After this operation, 66,6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 amd64 1.0.0-2ubuntu2.2 [17,4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 amd64 1.0.0-2ubuntu2.2 [84,8 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 amd64 1.0.0-2ubuntu2.2 [28,1 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 amd64 1.0.0-2ubuntu2.2 [31,3 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 amd64 1.0.0-2ubuntu2.2 [31,9 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.2 [46,6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Fetched 268 kB in 0s (1 575 kB/s) (Reading database ... 141610 files and directories currently installed.) Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Selecting previously unselected package libgles1:amd64. Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Errors were encountered while processing: /tmp/apt-dpkg-instal
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I was affected too, system info: Asus-K43SD: CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz GPU: NVIDIA Corporation GF119M [GeForce 610M] (rev a1) - [GeForce 610M/PCIe/SSE2] OS: 18.04 x64 Test update, works perfectly. Switching between Intel & NVIDIA happens right after logging out and getting in again. But GDM3 gone crazy(i guess it's not stable yet) and freezes after few logging in/out. Thank you for fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Sorry, I pressed wrong key!!! I was affected too, system info: Asus-K43SD: CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz GPU: NVIDIA Corporation GF119M [GeForce 610M] (rev a1) - [GeForce 610M/PCIe/SSE2] OS: 18.04 x64 Test update, works perfectly. Switching between Intel & NVIDIA happens right after logging out and getting in again. But GDM3 gone crazy(i guess it's not stable yet) and freezes after few logging in/out. Thank you for fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I was affected too, system info: Asus-K43SD: CPU: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz GPU: NVIDIA Corporation GF119M [GeForce 610M] (rev a1) - [GeForce 610M/PCIe/SSE2] OS: 18.04 x64 Test update, works perfectly. Switching between Intel & NVIDIABut GDM3 gone crazy(i guess it's not stable yet) and freezes after few logging in/out. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
Could you give me a simple command with complete syntax to download the new nvidia-340 driver for 18.04? I tried the following: apt download nvidia-340/bionic-proposed E: Release 'bionic-proposed' for 'nvidia-340' was not found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libgles1 The following packages will be upgraded: libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 libopengl0 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 268 kB of archives. After this operation, 66,6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 amd64 1.0.0-2ubuntu2.2 [17,4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 amd64 1.0.0-2ubuntu2.2 [84,8 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 amd64 1.0.0-2ubuntu2.2 [28,1 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 amd64 1.0.0-2ubuntu2.2 [31,3 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 amd64 1.0.0-2ubuntu2.2 [31,9 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.2 [46,6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Fetched 268 kB in 0s (1 575 kB/s) (Reading database ... 141610 files and directories currently installed.) Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Selecting previously unselected package libgles1:amd64. Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Errors were encountered while processing: /tmp/apt-dpkg-install-Gq7kQI/0-l
[Desktop-packages] [Bug 1792208] Re: nautilus 3.30 for cosmic in universe repro
*** This bug is a duplicate of bug 1786492 *** https://bugs.launchpad.net/bugs/1786492 No, sorry. We're not going to offer two different versions of nautilus in the Ubuntu package archives. Someone could make it available in a PPA. ** This bug has been marked a duplicate of bug 1786492 Update to nautilus 3.28 or newer -- 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/1792208 Title: nautilus 3.30 for cosmic in universe repro Status in nautilus package in Ubuntu: New Bug description: Hi, just a wish - would it be possible to include nautilus 3.30 for cosmic as unsupported alternative to 3.26 i.e. in the universe repro ? Advanced users (not complaining about the missing desktop icons support) can easily give it a try. I read somewhere that a snap is planned but I'm skeptical how well the desktop integration will work.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793881] [NEW] Bad import of PDF text for double 'f'.
Public bug reported: Open the attached pdf in inkscape. See that only one of the 'f's in "difference" are imported. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: inkscape 0.92.3-1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 14:52:32 2018 SourcePackage: inkscape UpgradeStatus: Upgraded to bionic on 2018-05-03 (142 days ago) ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "plot_NNI_4_skinny.pdf" https://bugs.launchpad.net/bugs/1793881/+attachment/5191720/+files/plot_NNI_4_skinny.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1793881 Title: Bad import of PDF text for double 'f'. Status in inkscape package in Ubuntu: New Bug description: Open the attached pdf in inkscape. See that only one of the 'f's in "difference" are imported. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: inkscape 0.92.3-1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 14:52:32 2018 SourcePackage: inkscape UpgradeStatus: Upgraded to bionic on 2018-05-03 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1793881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Alberto I was assuming that this should also work with sddm (on Kubuntu), but apparently not out of the box. Is there already something to test there? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
Installing using `sudo apt-get install nvidia-340/bionic-proposed` + `apt --fix-broken install` fails (as shown above in my comment). Downloading the nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb file (after enabling bionic-proposed https://wiki.ubuntu.com/Testing/EnableProposed ): $ apt download nvidia-340/bionic-proposed and installing it using: $ sudo dpkg -i nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb succeeds. To fix the previous failed installation, I've run: $ sudo apt-get install -f apt seems to be working now. ** Tags removed: verification-failed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libgles1 The following packages will be upgraded: libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 libopengl0 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 268 kB of archives. After this operation, 66,6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 amd64 1.0.0-2ubuntu2.2 [17,4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 amd64 1.0.0-2ubuntu2.2 [84,8 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 amd64 1.0.0-2ubuntu2.2 [28,1 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 amd64 1.0.0-2ubuntu2.2 [31,3 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 amd64 1.0.0-2ubuntu2.2 [31,9 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.2 [46,6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Fetched 268 kB in 0s (1 575 kB/s) (Reading database ... 141610 files and directories currently installed.) Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Selecting previously unselected package libgles1:amd64. Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1
[Desktop-packages] [Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt
Proposed solution:
As the stacktrace below shows the problem is caused by module
cogl_texture_new_with_size at cogl/cogl/deprecated/cogl/auto-texture.c .
This module is trying to create a texture with size 2560 x 1024, which is by
default is configured by gdm3 with wayland for 2 monitors.
This is not supported by graphics-card, causing error "Failed to create texture
2d due to size/format constraints".
The error is freed by cogl_texture_new_with_size, but the variable skip_error
is not set to NULL by the call to cogl_error_free (because the parameter is a
copy).
Then module tries to allocate a slice with max_waste -1. This also fails,
causing error "Sliced texture size of 2560 x 1024 not possible with max waste
set to -1".
Module cogl_set_error complains about the skip_error not being NULL with
message "CoglError set...", but does not set a new value to skip_error.
Also the second error is programmed to be freed by cogl_error_free at
cogl_texture_new_with_size, that in this way tries to free the same memory
twice. This causes the crash "double free or corruption (fasttop)", unless by
accident the same memory-address is allocated again.
To solve, the statement skip_error = NULL; should be added:
cogl_texture_new_with_size (unsigned int width,
unsigned int height,
CoglTextureFlags flags,
CoglPixelFormat internal_format)
{
CoglTexture *tex;
CoglError *skip_error = NULL;
_COGL_GET_CONTEXT (ctx, NULL);
if ((_cogl_util_is_pot (width) && _cogl_util_is_pot (height)) ||
(cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_BASIC) &&
cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_MIPMAP)))
{
/* First try creating a fast-path non-sliced texture */
tex = COGL_TEXTURE (cogl_texture_2d_new_with_size (ctx, width, height));
_cogl_texture_set_internal_format (tex, internal_format);
if (!cogl_texture_allocate (tex, &skip_error))
{
cogl_error_free (skip_error);
skip_error = NULL;
This solution is tested and solves the problem during startup and for right
corner click.
Stacktrace with modulenames/linenumbers:
Package: gnome-shell 3.30.0-1ubuntu2
Stacktrace:
#0 0xb7ef9d41 in __kernel_vsyscall ()
#1 0xb6a4e512 in __libc_signal_restore_set (set=0xbfcb8a0c) at
../sysdeps/unix/sysv/linux/internal-signals.h:84
set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273,
3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612,
3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0,
3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0,
3217787712}}
pid =
tid =
ret = 0
#2 0xb6a4e512 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273,
3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612,
3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0,
3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0,
3217787712}}
pid =
tid =
ret = 0
#3 0xb6a382b6 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb7996077 ,
sa_sigaction = 0xb7996077 }, sa_mask = {__val = {3080956952,
3060745084, 3080120357, 3217787880, 3060745084, 3217788000, 32868, 20347328, 0,
28984448, 2237142784, 3060745084, 3080120310, 3080956952, 3080956952,
3217788408, 1024, 31097824, 3080018485, 3060691022, 16, 3060756628, 0, 3, 4096,
3065078356, 2, 3066019840, 4096, 3217788168, 3064530671, 0}}, sa_flags = 4096,
sa_restorer = 0x3}
sigs = {__val = {32, 0 }}
#4 0xb6a9074c in __libc_message (action=do_abort, fmt=) at
../sysdeps/posix/libc_fatal.c:181
ap =
fd = 2
list =
nlist =
cp =
written =
#5 0xb6a975dd in malloc_printerr (str=str@entry=0xb6ba525c "double free or
corruption (fasttop)") at malloc.c:5336
#6 0xb6a98e6f in _int_free (av=, p=,
have_lock=) at malloc.c:4216
idx = 6
old =
old2 =
size =
fb =
nextchunk =
nextsize =
nextinuse =
prevsize =
bck =
fwd =
__PRETTY_FUNCTION__ = "_int_free"
#7 0xb7954290 in g_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#8 0xb7938c53 in g_error_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#9 0xb66d7058 in cogl_error_free (error=0x16cba70) at cogl-error.c:45
#10 0xb66db62c in cogl_texture_new_with_size (width=2560, height=1024,
flags=COGL_TEXTURE_NO_SLICING, internal_format=COGL_PIXEL_FORMAT_RGBA__PRE)
at deprecated/cogl-auto-texture.c:121
tex = 0x1da83e0
skip_error = 0x16cba70
ctx =
#11 0xb6e9a618 in clutter_offscreen_effect_real_create_texture
(effect=0x23c3b00
[Desktop-packages] [Bug 1793873] [NEW] document in \Templates does not show up on right click in Nautilus
Public bug reported: A Text Document (empty one) in \Templates does not show up on right click in Nautilus, I tried many locations. michal:~$ ls -ltr ~/Templates/ total 0 -rw-r--r-- 1 michal michal 0 Sep 14 08:49 text I just see in Right click: New Folder Paste Select All Properties Open in Terminal Restore Missing Files... I have michal@Beast:~$ apt list | grep nautil clamtk-nautilus/bionic,bionic,bionic,bionic 5.25-1 all easytag-nautilus/bionic,bionic 2.4.3-4 amd64 gir1.2-nautilus-3.0/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed,automatic] libnautilus-extension-dev/bionic 1:3.26.3-0ubuntu4 amd64 libnautilus-extension1a/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed] nautilus/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed] nautilus-admin/bionic,bionic,bionic,bionic 1.1.3-1 all nautilus-compare/bionic,bionic,bionic,bionic,now 0.0.4+po1-1 all [installed] nautilus-data/bionic,bionic,now 1:3.26.3-0ubuntu4 all [installed] nautilus-dropbox/bionic 2015.10.28-1ubuntu2 amd64 nautilus-emblems/bionic,bionic,bionic,bionic 0.3.1-3 all nautilus-extension-brasero/bionic,bionic 3.12.1-4ubuntu2 amd64 nautilus-extension-burner/bionic,bionic 3.0.4-0ubuntu1 amd64 nautilus-extension-gnome-terminal/bionic-updates,now 3.28.2-1ubuntu1~18.04.1 amd64 [installed,automatic] nautilus-filename-repairer/bionic,bionic 0.2.0-1 amd64 nautilus-gtkhash/bionic,bionic 1.1.1-2 amd64 nautilus-hide/bionic,bionic,bionic,bionic 0.2.3-2 all nautilus-ideviceinfo/bionic,bionic 0.1.0-0ubuntu14 amd64 nautilus-image-converter/bionic,bionic 0.3.1~git20110416-2 amd64 nautilus-owncloud/bionic,bionic,bionic,bionic 2.4.1+dfsg-1 all nautilus-script-audio-convert/bionic,bionic,bionic,bionic 0.3.1.1-0ubuntu6 all nautilus-script-collection-svn/bionic,bionic,bionic,bionic 0.9.2-0ubuntu3 all nautilus-script-debug/bionic,bionic,bionic,bionic 0.9.2-0ubuntu3 all nautilus-script-manager/bionic,bionic,bionic,bionic 0.0.5-0ubuntu5 all nautilus-scripts-manager/bionic,bionic,bionic,bionic 2.0-1 all nautilus-sendto/bionic,now 3.8.6-2 amd64 [installed] nautilus-share/bionic,now 0.7.3-2ubuntu3 amd64 [installed] nautilus-wipe/bionic,bionic 0.3-1 amd64 nitroshare-nautilus/bionic,bionic,bionic,bionic 0.3.3-1 all python-nautilus/bionic,bionic,now 1.1-6 amd64 [installed,automatic] rabbitvcs-nautilus/bionic,bionic,bionic,bionic 0.16-1.1 all seahorse-nautilus/bionic,bionic 3.11.92-2 amd64 subliminal-nautilus/bionic,bionic,bionic,bionic 1.1.1-2 all tortoisehg-nautilus/bionic,bionic,bionic,bionic 4.5.2-0ubuntu1 all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 06:45:44 2018 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-27 (329 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-09-03 (18 days ago) usr_lib_nautilus: ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1793873 Title: document in \Templates does not show up on right click in Nautilus Status in nautilus package in Ubuntu: New Bug description: A Text Document (empty one) in \Templates does not show up on right click in Nautilus, I tried many locations. michal:~$ ls -ltr ~/Templates/ total 0 -rw-r--r-- 1 michal michal 0 Sep 14 08:49 text I just see in Right click: New Folder Paste Select All Properties Open in Terminal Restore Missing Files... I have michal@Beast:~$ apt list | grep nautil clamtk-nautilus/bionic,bionic,bionic,bionic 5.25-1 all easytag-nautilus/bionic,bionic 2.4.3-4 amd64 gir1.2-nautilus-3.0/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed,automatic] libnautilus-extension-dev/bionic 1:3.26.3-0ubuntu4 amd64 libnautilus-extension1a/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed] nautilus/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed] nautilus-admin/bionic,bionic,bionic,bionic 1.1.3-1 all nautilus-compare/bionic,bionic,bionic,bionic,now 0.0.4+po1-1 all [installed] nautilus-data/bionic,bionic,now 1:3.26.3-0ubuntu4 all [installed] nautilus-dropbox/bionic 2015.10.28-1ubuntu2 amd64 nautilus-emblems/bionic,bionic,bionic,bionic 0.3.1-3 all nautilus-extension-brasero/bionic,bionic 3.12.1-4ubuntu2 amd64 nautilus-extension-burner/bionic,bionic 3.0.4-0ubuntu1 amd64 nautilus-extension-gnome-terminal/bionic-updates,now 3.28.2-1ubuntu1~18.04.1 amd64 [installed,automatic] nautilus-filename-repairer/bionic,bionic 0.2.0-1 amd64 nautilus-gtkhash/
[Desktop-packages] [Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
Okay, manually installing version the .deb of 340.107 did seem to work, but /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/nvidia_settings.conf: No such file or directory remained as an error even afterwards. Should I be worried about that? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libgles1 The following packages will be upgraded: libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 libopengl0 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 268 kB of archives. After this operation, 66,6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 amd64 1.0.0-2ubuntu2.2 [17,4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 amd64 1.0.0-2ubuntu2.2 [84,8 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 amd64 1.0.0-2ubuntu2.2 [28,1 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 amd64 1.0.0-2ubuntu2.2 [31,3 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 amd64 1.0.0-2ubuntu2.2 [31,9 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.2 [46,6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Fetched 268 kB in 0s (1 575 kB/s) (Reading database ... 141610 files and directories currently installed.) Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Selecting previously unselected package libgles1:amd64. Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Errors were
[Desktop-packages] [Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
Also, sudo dpkg --configure -a (which was suggested above) yields the following: Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/nvidia_settings.conf: No such file or directory Help? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libgles1 The following packages will be upgraded: libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 libopengl0 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 268 kB of archives. After this operation, 66,6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 amd64 1.0.0-2ubuntu2.2 [17,4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 amd64 1.0.0-2ubuntu2.2 [84,8 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 amd64 1.0.0-2ubuntu2.2 [28,1 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 amd64 1.0.0-2ubuntu2.2 [31,3 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 amd64 1.0.0-2ubuntu2.2 [31,9 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.2 [46,6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Fetched 268 kB in 0s (1 575 kB/s) (Reading database ... 141610 files and directories currently installed.) Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Selecting previously unselected package libgles1:amd64. Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Errors were encou
[Desktop-packages] [Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
I've enabled -proposed as suggested above to get 340.107 instead, put running dpkg --fix-broken install still results in the following output: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: gir1.2-osmgpsmap-1.0 libosmgpsmap-1.0-1 python3-dateutil python3-requests-oauthlib Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libgles1 libglvnd-dev The following NEW packages will be installed: libgles1 The following packages will be upgraded: libglvnd-dev 1 upgraded, 1 newly installed, 0 to remove and 157 not upgraded. Need to get 0 B/14.6 kB of archives. After this operation, 66.6 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 687305 files and directories currently installed.) Preparing to unpack .../libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Preparing to unpack .../libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 Errors were encountered while processing: /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) nightstallion@Mimir:~/Downloads$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: gir1.2-osmgpsmap-1.0 libosmgpsmap-1.0-1 python3-dateutil python3-requests-oauthlib Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libgles1 libglvnd-dev The following NEW packages will be installed: libgles1 The following packages will be upgraded: libglvnd-dev 1 upgraded, 1 newly installed, 0 to remove and 157 not upgraded. Need to get 0 B/14.6 kB of archives. After this operation, 66.6 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 687305 files and directories currently installed.) Preparing to unpack .../libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Preparing to unpack .../libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 Errors were encountered while processing: /var/cache/apt/archives/libgles1_1.0.0-2ubuntu2.2_amd64.deb /var/cache/apt/archives/libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculat
[Desktop-packages] [Bug 1439478] Re: Copy and Paste not Working in 15.04, 15.10, 16.04
I do have the same problem. Also using the workaround of installing remmina from the repo ppa:remmina-ppa-team/remmina-next I cannot copy text from the host and pasting it into the guest. My host is a Ubuntu 18.04 machine while my guest is a container running Ubuntu 16.04. remmina version is 1.2.31.4 xrdp server version is 0.6.1-2 architecture used is a Intel Core i5 8th gen. This configuration is fundamental for my work since I use Ubuntu 16.04 as a build system for Yocto that is only test on this Ubuntu version and of course I want to keep the possibility to run a newer OS for everything else. I think anyway this is a quite usual usage scenario and it is actually one of the possible applications containers are used for. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1439478 Title: Copy and Paste not Working in 15.04, 15.10, 16.04 Status in remmina: Fix Released Status in remmina package in Ubuntu: Fix Released Status in remmina source package in Xenial: Triaged Bug description: Remmina is probably one of the top 3 Linux applications "I need working right" to efficiently complete my work day. So, I consider it a critical bug that "copy and pasting" between "local and remote desktops" is not working in the 15.04 beta 2. This is one of those things, where if this is not fixed, I will have to return to Ubuntu 14.04, or figure out a way to install a version of Remmina that actually works correctly in 15.04. This bug has reared its ugly head before: https://bugs.launchpad.net/remmina/+bug/937522 However, the status of that bug seems to be practically closed, so that's the reason for this new posting. I want to do all I can to get this bug the attention it needs. Remmina is crucial for my work. I'm currently dealing with the fact that it crashes a few times a day, but this "copy and paste not working" is a real deal-breaker for me to stay on 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/remmina/+bug/1439478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.1
I downloaded the nvidia-340 driver from the link provided, installed the driver, fixed the broken packages and after that everything worked fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1791542 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Status in libglvnd package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in libglvnd source package in Bionic: Confirmed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] The new libgles1 conflicts with nvidia-340 which ships it's own copy of libGLESv1_CM.so [Test case] Enable proposed, install libgles1 and nvidia-340, they should install fine. [Regression potential] none, just fixes a file conflict -- Looks like I had a similar problem on 18.04.1 than https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1728352, just with nvidia-340 from https://launchpad.net/~graphics- drivers/+archive/ubuntu/ppa . Apt output: ``` $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libgles1 The following packages will be upgraded: libegl1 libgl1 libgles2 libglvnd-core-dev libglvnd-dev libglvnd0 libglx0 libopengl0 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 268 kB of archives. After this operation, 66,6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-dev amd64 1.0.0-2ubuntu2.2 [3 408 B] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd-core-dev amd64 1.0.0-2ubuntu2.2 [12,9 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles2 amd64 1.0.0-2ubuntu2.2 [17,4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgl1 amd64 1.0.0-2ubuntu2.2 [84,8 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglx0 amd64 1.0.0-2ubuntu2.2 [28,1 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libopengl0 amd64 1.0.0-2ubuntu2.2 [31,3 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libegl1 amd64 1.0.0-2ubuntu2.2 [31,9 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.2 [46,6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libgles1 amd64 1.0.0-2ubuntu2.2 [11,2 kB] Fetched 268 kB in 0s (1 575 kB/s) (Reading database ... 141610 files and directories currently installed.) Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Preparing to unpack .../1-libglvnd-core-dev_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd-core-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../2-libgles2_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles2:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../3-libgl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../4-libglx0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../5-libopengl0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libopengl0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../6-libegl1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libegl1:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Preparing to unpack .../7-libglvnd0_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... Selecting previously unselected package libgles1:amd64. Preparing to unpack .../8-libgles1_1.0.0-2ubuntu2.2_amd64.deb ... Unpacking libgles1:amd64 (1.0.0-2ubuntu2.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 Errors were encountered while processing: /tmp/apt-dpkg-install-Gq7kQI/0-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb /tmp/apt-dpkg-install-Gq7kQI/8-libgles1_1.
[Desktop-packages] [Bug 1742542] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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/1742542 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: Confirmed Bug description: Artful (17.10) Session logout after screen turned off Whenever I turn off my screen and then turn it on the problem occurs. the computer (a desktop PC) logs me out of my session. When I wake the screen, I get the GDM login screen and a new session opens. The previous session is lost. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Jan 8 18:33:01 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1510175942 GsettingsChanges: InstallationDate: Installed on 2017-12-03 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1742542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736512] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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/1736512 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: Confirmed Bug description: That crash happen after trying to use the driver r8168-dkms (which fully fails) for better performance with that r8168e chipset, instead of the kernel builtin r8169 which set a 576 MTU instead of a supported 1500. This is with a gnome on xorg login session. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Dec 5 17:14:05 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760499] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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/1760499 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: Confirmed Bug description: got crash as i logged in ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Mar 31 22:41:33 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-15 (107 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737501] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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/1737501 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: Confirmed Bug description: Got that crash while upgrading some applets from extensions.gnome.org ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 11 10:00:15 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() 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-shell/+bug/1737501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791502] Re: libpam-mount : copy problem with small files
Hi, This bug affects others Linux distributions like Fedora 28 Workstation, Manjaro XFCE Edition (17.1.12). Could it be a GTK library problem ? Kind regards. -- 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/1791502 Title: libpam-mount : copy problem with small files Status in nautilus package in Ubuntu: Incomplete Bug description: Dear all, With a fresh install of ubuntu 18.04 and libpam-mount, I encounter issue when I copy small text files of few ko from remote share to local host with nautilus. More exactly, when I paste the file from a mounted remote samba share to a local directory, nautilus reports a time of transfer of approximatively 596523 hours! The process keep locked and I need to kill nautilus to launch a new instance. It seems that nautilus is unable to "understand" the end of copy because the file is well copied from remote to local directory and is usable. Can you look at this issue please ? Kind regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792208] Re: nautilus 3.30 for cosmic in universe repro
** Tags added: upgrade-software-version -- 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/1792208 Title: nautilus 3.30 for cosmic in universe repro Status in nautilus package in Ubuntu: New Bug description: Hi, just a wish - would it be possible to include nautilus 3.30 for cosmic as unsupported alternative to 3.26 i.e. in the universe repro ? Advanced users (not complaining about the missing desktop icons support) can easily give it a try. I read somewhere that a snap is planned but I'm skeptical how well the desktop integration will work.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793861] [NEW] libreoffice crashes when libvclplug_gtk3lo is installed
Public bug reported: running on ubuntu cosmic with proposed packages. uninstalling libreoffice-gtk3 is a workaround. here is a stackdump, hope it helps... 130 NETZAGENTUR\josef@joebook ~ % loffice --norestore :( Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7f9c5c1b7fb3] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7f9c5c1b81c3] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f9c5bf9d100] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f9c5bf9d077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f9c5bf7e535] /usr/lib/libreoffice/program/libmergedlo.so(+0x11ec2fa)[0x7f9c5d3c42fa] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0x90)[0x7f9c5f00c630] /usr/lib/libreoffice/program/libmergedlo.so(+0x1efaa17)[0x7f9c5e0d2a17] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e39beb)[0x7f9c5f011beb] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x17202)[0x7f9c5c192202] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d08f)[0x7f9c5c1b808f] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f9c5bf9d100] /lib/x86_64-linux-gnu/libc.so.6(+0x183f11)[0x7f9c5c0dff11] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f9c5ad645a4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2eb3fef)[0x7f9c5f08bfef] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9996)[0x7f9c5ad59996] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9ba8)[0x7f9c5ad59ba8] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f9c5ad1f203] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8fad6)[0x7f9c5ad1fad6] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1812)[0x7f9c5ad51812] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f203)[0x7f9c5ad1f203] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8f239)[0x7f9c5ad1f239] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f9c5ab6cae8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ded8)[0x7f9c5ab6ced8] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f9c5ab6cf6c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x89923)[0x7f9c4fc4a923] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f9c5f00cb0e] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f9c5f00e285] /usr/lib/libreoffice/program/libmergedlo.so(+0x1f00376)[0x7f9c5e0d8376] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e3b376)[0x7f9c5f013376] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f9c5f013470] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x91)[0x7f9c5e0f4a21] /usr/lib/libreoffice/program/soffice.bin(+0x107b)[0x55b8274e107b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f9c5bf8009b] /usr/lib/libreoffice/program/soffice.bin(+0x10ba)[0x55b8274e10ba] ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice-gtk3 1:6.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 22 09:40:07 2018 SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic package-from-proposed ** Description changed: + running on ubuntu cosmic with proposed packages. uninstalling libreoffice-gtk3 is a workaround. - here is a stackdump, hope it helps... - 130 NETZAGENTUR\josef@joebook ~ % loffice --norestore :( Application Error - Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3cfb3)[0x7f9c5c1b7fb3] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d1c3)[0x7f9c5c1b81c3] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f9c5bf9d100] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f9c5bf9d077] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f9c5bf7e535] /usr/lib/libreoffice/program/libmergedlo.so(+0x11ec2fa)[0x7f9c5d3c42fa] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0x90)[0x7f9c5f00c630] /usr/lib/libreoffice/program/libmergedlo.so(+0x1efaa17)[0x7f9c5e0d2a17] /usr/lib/libreoffice/program/libmergedlo.so(+0x2e39beb)[0x7f9c5f011beb] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x17202)[0x7f9c5c192202] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d08f)[0x7f9c5c1b808f] /lib/x86_64-linux-gnu/libc.so.6(+0x41100)[0x7f9c5bf9d100] /lib/x86_64-linux-gnu/libc.so.6(+0x183f11)[0x7f9c5c0dff11] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f9c5ad645a4] /usr/lib/l
[Desktop-packages] [Bug 1793853] Re: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libglvnd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1793853 Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: Confirmed Bug description: Error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgles1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 22 18:10:09 2018 DuplicateSignature: package:libgles1:(not installed) Unpacking libglvnd-dev:amd64 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AY1GH7/05-libglvnd-dev_1.0.0-2ubuntu2.2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2018-06-30 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libgles1 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793818] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libglvnd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1793818 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: Confirmed Bug description: Error occurred during software update installing new packages ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglvnd-dev 1.0.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 Date: Fri Sep 21 13:39:17 2018 DpkgTerminalLog: Preparing to unpack .../0-libglvnd-dev_1.0.0-2ubuntu2.2_i386.deb ... Unpacking libglvnd-dev:i386 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-28PzbF/0-libglvnd-dev_1.0.0-2ubuntu2.2_i386.deb (--unpack): trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 DuplicateSignature: package:libglvnd-dev:1.0.0-2ubuntu2.1 Unpacking libglvnd-dev:i386 (1.0.0-2ubuntu2.2) over (1.0.0-2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-28PzbF/0-libglvnd-dev_1.0.0-2ubuntu2.2_i386.deb (--unpack): trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2016-06-12 (831 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: Upgraded to bionic on 2018-08-30 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1793818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769838] Re: Input source options does not work on Bionic with gnome-flashback
Hi Łukasz, now it should be better. ** Description changed: [Impact] * An explanation of the effects of the bug on users and: Setting the 'Input Source Options' to 'Allow different sources for each window' does not work. * justification for backporting the fix to the stable release: This is a bug in Ubuntu Bionic's version of gnome-flashback (3.28) (because the GUI lets the user change the input source option but the backend does nothing) [Test Case] * detailed instructions how to reproduce the bug - Set Input Source Options to Allow different sources for each window in gnome-control-center -> Region & Language -> Options - Realize that if you set different layouts for different windows it does not change automatically when changing windows. [Regression Potential] - * discussion of how regressions are most likely to manifest as a result - of this change: + * Metacity now ignores its own events when predicting focus changes. Its + own events are recognized by comparing timestamps and serial numbers. If + something potentially goes wrong, it can either not ignore its own + events, or ignore external events. In both cases the focus prediction + will be broken. Also there could be potentially a race condition, but + the patch protects against it by making a dummy request with bumped + serial number. (Note: the second metacity patch is an amendment for the + first one, so the previous analysis applies to both patches.) - This bug itself is a regression, because it was working in Ubuntu - Trusty. + * GNOME-Flashback has some new code for handling per-window input + sources. The change_per_window_source() function returns early if the + sources_per_window option (obtained from GSettings: org.gnome.desktop + .input-sources per-window) is false. As that option is false by default, + in the default configuration most of the new code won't be executed at + all. The potential breakage may happen if it is set to true. Such + potential breakage includes: wrong input sources handling (it was wrong + before anyway), gnome-flashback crashes. The patches are already applied + in Cosmic, and currently no crashes are reported against the Cosmic + version of gnome-flashback on errors.ubuntu.com. [Other Info] This needs fixes in both gnome-flashback and metacity. Here are the relevant commits in gnome-3-28 branches: https://gitlab.gnome.org/GNOME/metacity/commit/b96341dabffc3589 (ensure that we ignore our own focus events for focus predictions) https://gitlab.gnome.org/GNOME/metacity/commit/9956d376d38d0ad6 (fix problems with focus tracking) https://gitlab.gnome.org/GNOME/gnome-flashback/commit/3c4c6ecddef48cd5 (implement per window input sources) The gnome-session-flashback dependency on metacity will be bumped. ** Summary changed: - Input source options does not work on Bionic with gnome-flashback + Per-window input sources option does not work on Bionic with gnome-flashback -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1769838 Title: Per-window input sources option does not work on Bionic with gnome- flashback Status in gnome-flashback package in Ubuntu: Fix Released Status in metacity package in Ubuntu: Fix Released Status in gnome-flashback source package in Bionic: New Status in metacity source package in Bionic: New Bug description: [Impact] * An explanation of the effects of the bug on users and: Setting the 'Input Source Options' to 'Allow different sources for each window' does not work. * justification for backporting the fix to the stable release: This is a bug in Ubuntu Bionic's version of gnome-flashback (3.28) (because the GUI lets the user change the input source option but the backend does nothing) [Test Case] * detailed instructions how to reproduce the bug - Set Input Source Options to Allow different sources for each window in gnome-control-center -> Region & Language -> Options - Realize that if you set different layouts for different windows it does not change automatically when changing windows. [Regression Potential] * Metacity now ignores its own events when predicting focus changes. Its own events are recognized by comparing timestamps and serial numbers. If something potentially goes wrong, it can either not ignore its own events, or ignore external events. In both cases the focus prediction will be broken. Also there could be potentially a race condition, but the patch protects against it by making a dummy request with bumped serial number. (Note: the second metacity patch is an amendment for the first one, so the previous analysis applies to both patches.) * GNOME-Flashback has some new code for handling per-window input sources. The change_per_window_source() function returns early if the sources_per_windo
