[Desktop-packages] [Bug 1769386] Re: Cable network does not get recognized anymore, wifi works
@6 for me its not related to suspend..it just has stopped working all the time, even after reboots so not related your bug? -- 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/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653153] Re: Windows not always drawn in correct places in AO when under Wayland
** Changed in: gnome-shell Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1653153 Title: Windows not always drawn in correct places in AO when under Wayland Status in GNOME Shell: Fix Released Status in Ubuntu GNOME: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that quite often windows will be drawn in the wrong place in the Activities Overview: Window_drawn_wrong_place_AO.png ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 29 17:53:03 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (228 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1653153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691935] Re: Resuming from suspend requires no password
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1691935 Title: Resuming from suspend requires no password Status in gnome-shell package in Ubuntu: Expired Bug description: Resuming from suspend requires no password. Perhaps because we don't use gdm? Test case: 1. Click the power menu 2. Hold down Alt so the power button changes to a pause button. 3. Click it to suspend the system 4. Wake the system Expected: A password prompt Observed: My original desktop fully unlocked ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Fri May 19 13:28:57 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (16 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1691935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773009] Re: Xorg freeze
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1773009 Title: Xorg freeze Status in xorg package in Ubuntu: Expired Bug description: I am using the Thunderbolt port on my Lenovo P50, driving 2 Samsung 4k monitors with DisplayPort. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 23 13:06:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-20-generic, x86_64: installed nvidia, 390.48, 4.15.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230] InstallationDate: Installed on 2018-05-20 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20ENCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=302a2c3a-904a-4171-b934-6df4162e0e1f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET75W (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET75W(1.48):bd12/13/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773311] Re: Screen blanks a few seconds after resuming from suspend
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773311 Title: Screen blanks a few seconds after resuming from suspend Status in gnome-shell package in Ubuntu: Expired Bug description: After resuming from suspend screen blanking goes off after a few seconds even if the timeout is disabled or set to several minutes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 25 08:26:42 2018 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1409 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-03-24 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769386] Re: Cable network does not get recognized anymore, wifi works
Same as LP: #1779817? -- 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/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653153] Re: Windows not always drawn in correct places in AO when under Wayland
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1653153 Title: Windows not always drawn in correct places in AO when under Wayland Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that quite often windows will be drawn in the wrong place in the Activities Overview: Window_drawn_wrong_place_AO.png ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 29 17:53:03 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (228 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1653153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] Re: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable.
WORKAROUND: Download and manually install the previous version from here: https://launchpad.net/ubuntu/+source/gnome-shell/3.28.2-0ubuntu1/+build/15050190 -- 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/1783363 Title: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable. Status in gnome-shell package in Ubuntu: In Progress Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780627] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1780627 Title: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message() Status in gnome-keyring package in Ubuntu: Confirmed Bug description: Package: gnome-keyring Status: install ok installed Priority: optional Section: gnome Installed-Size: 3536 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: foreign Version: 3.28.0.2-1ubuntu1.18.04.1 -- ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Sun Jul 8 15:07:49 2018 DistroRelease: Ubuntu 18.04 ExecutablePath: /usr/bin/gnome-keyring-daemon ExecutableTimestamp: 1525893569 ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login ProcCwd: / ProcEnviron: SHELL=/usr/bin/zsh PATH=(custom, no user) LANG=fr_FR.UTF-8 XDG_RUNTIME_DIR= Disassembly: => 0x7ff49ed28e97 <__GI_raise+199>: mov0x108(%rsp),%rcx 0x7ff49ed28e9f <__GI_raise+207>: xor%fs:0x28,%rcx 0x7ff49ed28ea8 <__GI_raise+216>: mov%r8d,%eax 0x7ff49ed28eab <__GI_raise+219>: jne0x7ff49ed28ecc <__GI_raise+252> 0x7ff49ed28ead <__GI_raise+221>: add$0x118,%rsp 0x7ff49ed28eb4 <__GI_raise+228>: retq 0x7ff49ed28eb5 <__GI_raise+229>: nopl (%rax) 0x7ff49ed28eb8 <__GI_raise+232>: mov0x3abfa9(%rip),%rdx# 0x7ff49f0d4e68 0x7ff49ed28ebf <__GI_raise+239>: neg%eax 0x7ff49ed28ec1 <__GI_raise+241>: mov$0x,%r8d 0x7ff49ed28ec7 <__GI_raise+247>: mov%eax,%fs:(%rdx) 0x7ff49ed28eca <__GI_raise+250>: jmp0x7ff49ed28e80 <__GI_raise+176> 0x7ff49ed28ecc <__GI_raise+252>: callq 0x7ff49ee1ec80 <__stack_chk_fail> 0x7ff49ed28ed1: nopw %cs:0x0(%rax,%rax,1) 0x7ff49ed28edb: nopl 0x0(%rax,%rax,1) 0x7ff49ed28ee0 : test %edi,%edi SourcePackage: gnome-keyring Stacktrace: #0 0x7ff49ed28e97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 set = {__val = {512, 93934813221269, 93934813221468, 93934813221168, 93934813221468, 0, 2064, 124, 93934783944344, 140731733819248, 140688617200704, 140688613697496, 566935683072, 2048, 347476102400, 7}} pid = tid = #1 0x7ff49ed2a801 in __GI_abort () at abort.c:79 save_stage = 1 act = {__sigaction_handler = {sa_handler = 0xfefc, sa_sigaction = 0xfefc}, sa_mask = {__val = {93934813482240, 0, 140731733819248, 140728898420737, 16564058428705303040, 72057594037927936, 16777216, 6989586621679009792, 93932964806656, 93934813482240, 0, 0, 16564058428705303040, 93934783944344, 93934813482240, 98}}, sa_flags = -1615663648, sa_restorer = 0x7ffea900bf70} sigs = {__val = {32, 0 }} #2 0x7ff49f88cfa5 in g_assertion_message () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff49f88d00a in g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x556ee564fd07 in () #5 0x556ee564ffdd in () #6 0x556ee5650085 in () #7 0x7ff49dd00dae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #8 0x7ff49dd0071f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #9 0x7ff49fb40761 in g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7ff49fb3ff6d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7ff49fb52d3e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x7ff49fb5a960 in g_signal_emitv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x556ee565f659 in () #14 0x7ff49fe5b437 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x7ff49fe435bc in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x7ff49f8660f5 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7ff49f8664c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7ff49f8667d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x556ee5647d7a in () #20 0x7ff49ed0bb97 in __libc_start_main (main=0x556ee5647a50, argc=3, argv=0x7ffea900cae8, init=, fini=, rtld_fini=, stack_end=0x7ffea900cad8) at ../csu/libc-start.c:310 result = unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 1498076869208036635, 9393478024, 140731733822176, 0, 0, 4749789229303715099, 4755462022603330843}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7ff4a05fb733 <_dl_init+259>, 0x7ff4a05de6d8}, data = {prev = 0x0, cleanup = 0x0, canceltype = -1604339917}}} not_first_call = #21 0x556ee56482ca in ()
[Desktop-packages] [Bug 1783363] Re: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable.
** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1783363 Title: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable. Status in gnome-shell package in Ubuntu: In Progress Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653153] Re: Windows not always drawn in correct places in AO when under Wayland
** Changed in: ubuntu-gnome Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1653153 Title: Windows not always drawn in correct places in AO when under Wayland Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that quite often windows will be drawn in the wrong place in the Activities Overview: Window_drawn_wrong_place_AO.png ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 29 17:53:03 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (228 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1653153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
** Tags added: regression ** Summary changed: - Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed + [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable. Stuck in Activities Overview. ** Summary changed: - [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable. Stuck in Activities Overview. + [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable. -- 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/1783363 Title: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable. Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719408] Re: Application window outside of its frame in spread mode
*** This bug is a duplicate of bug 1653153 *** https://bugs.launchpad.net/bugs/1653153 The upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=792681 was marked as a duplicate of: https://bugzilla.gnome.org/show_bug.cgi?id=776588 which would make this a duplicate of bug 1653153...? ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** This bug has been marked a duplicate of bug 1653153 Windows not always drawn in correct places in AO when under Wayland -- 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/1719408 Title: Application window outside of its frame in spread mode Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/3 https://gitlab.gnome.org/GNOME/gnome-shell/issues/143 https://bugzilla.gnome.org/show_bug.cgi?id=792681 https://bugzilla.gnome.org/show_bug.cgi?id=776588 Test Case: 1. On a workspace with no window, toggle spread mode (super key) 2. Open a terminal with its keybinding: CTRL+ALT+T Expected result The terminal opens in the center of the screen with a frame around it Actual result The frame is displayed in the center of the screen but the application window is outside of the frame (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-bin 1.14.0-1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 15:00:29 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-11-generic, x86_64: installed virtualbox, 5.1.28, 4.13.0-11-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1507] InstallationDate: Installed on 2013-09-03 (1482 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1719408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653153] Re: Windows not always drawn in correct places in AO when under Wayland
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350754 -- 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/1653153 Title: Windows not always drawn in correct places in AO when under Wayland Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Incomplete Status in gnome-shell package in Ubuntu: Fix Released Bug description: After switching from Xorg to Wayland on Ubuntu GNOME 16.10 with GNOME 3.22 I have found that quite often windows will be drawn in the wrong place in the Activities Overview: Window_drawn_wrong_place_AO.png ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.22.2-1ubuntu1~ubuntu16.10.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 29 17:53:03 2016 DisplayManager: gdm3 InstallationDate: Installed on 2016-05-15 (228 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-10-19 (70 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1653153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713581] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Changed in: nautilus (Ubuntu) Status: Triaged => In Progress -- 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/1713581 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in nautilus package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/ef1ce30f6325c683b207fd96a3be93eda5384054 Fixed in https://gitlab.gnome.org/GNOME/nautilus/commit/b6691821b86460bf9d4caa6391666ae506a743c5 no idea,sorry ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.25.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 00:07:44 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-08-09 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7f8b19a60d27 : mov(%rdi),%rdx PC (0x7f8b19a60d27) ok source "(%rdi)" (0x0002) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1713581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782739] Re: Boot to Black
OK. Try downloading all of these: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux- headers-4.18.0-041800rc6_4.18.0-041800rc6.201807221830_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux- headers-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux-image- unsigned-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux- modules-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb When downloaded you can install them in a terminal by running: cd ~/Downloads sudo dpkg -i linux*4.18.0-041800rc6*.deb Then reboot. Now check that the new kernel is active by running: uname -a and send us the result that you see. Is the original bug also fixed now? -- 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/1782739 Title: Boot to Black Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see the splash screen as expected. The boot continues and it reaches the point where you would expect to see the login screen. I see what appears to be a non-backlighted blank black screen. If I wait until all hard drive activity ceases and then type in my password and press enter the login completes and I am presented a normal Ubuntu desktop. Thank you Gene ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 20 07:16:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:166d] InstallationDate: Installed on 2018-07-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. TP550LA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=5b0bd839-3614-4f3d-8536-bc400cd364e5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP550LA.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP550LA.210:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnTP550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782739] Re: Boot to Black
Note to self: possibly related to bug 1782934. -- 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/1782739 Title: Boot to Black Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see the splash screen as expected. The boot continues and it reaches the point where you would expect to see the login screen. I see what appears to be a non-backlighted blank black screen. If I wait until all hard drive activity ceases and then type in my password and press enter the login completes and I am presented a normal Ubuntu desktop. Thank you Gene ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 20 07:16:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:166d] InstallationDate: Installed on 2018-07-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. TP550LA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=5b0bd839-3614-4f3d-8536-bc400cd364e5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP550LA.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP550LA.210:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnTP550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
Temporarily reopening the gnome-shell task, just so people can find the bug. And are less likely to create more duplicates. ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => Confirmed -- 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685035] Re: GDM login doesn't scale on Hi-DPI display
Still happening for me as well... $ gnome-shell --version GNOME Shell 3.28.2 $ gdm3 --version GDM 3.28.2 $ uname --all Linux PS006 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic -- 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/1685035 Title: GDM login doesn't scale on Hi-DPI display Status in GNOME Settings Daemon: Fix Released Status in Ubuntu GNOME: Triaged Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Zesty: Fix Released Bug description: Impact -- GDM's login screen was being start with no gnome-settings-daemons plugins. In particular, this broke Hi-DPI support in the login screen Test Case - - Install the update on a computer running Ubuntu GNOME 17.04 with a Hi-DPI display (ideally one that worked well with Ubuntu GNOME 16.10). - Restart your computer. - The login screen should automatically show at the right scale. Regression Potential See the other 3.24.2 bugs but this commit is a simple typo fix. Original Bug Report --- Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800, login screen is too tiny to read. GDM login screen doesn't reflect changes to org.gnome.desktop.interface scaling-factor or text-scaling-factor. Eg: xhost +SI:localuser:gdm sudo su gdm -s /bin/bash gsettings set org.gnome.desktop.interface scaling-factor 2 gsettings set org.gnome.desktop.interface text-scaling-factor 2.0 no effect. Creating a gdm user under /etc/dconf and running dconf update has no effect either. Scaling-factor seems to scale the mouse cursor, but nothing else. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1685035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Description changed: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 + + https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status - ProblemType: Crash - DistroRelease: Ubuntu 18.04 + ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA - Signal: 11 - SourcePackage: gnome-shell + Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: -- 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05
[Desktop-packages] [Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
AlpineCarver, thanks for that suggestion. Still, I can't switch between Frequent and All applications view. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic Linux PS006 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have an Bangho AERO 1104 with touch screen, when I try to open the application drawer from the applications icon in the dock, it does not open. 1)- Ubuntu 17.10 Artful Aardvark 64 bit 2)- gnome-shell-extension-ubuntu-dock_0.7 3)- What should happen is that touching the applications icon in the dock, opens the application drawer. 4)- Instead, what has happened is that absolutely nothing happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Re-opening this bug as we had to revert the fix, because it was causing an installer regression: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1783326 That said, I think the "run it sometimes, but not always" fix was probably naive at best. The only two options that seem to make sense for fixing this properly are: 1) Make GNOME stop writing things to that file that console-setup doesn't understand, or 2) Make console-setup understand the things GNOME writes to that file. The second option is certainly the more appealing of the two, but it's clearly not going to happen before the point release in two days. ** Changed in: console-setup (Ubuntu Bionic) Status: Fix Released => Confirmed ** Changed in: console-setup (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 854959] Re: Connect to windows share: gvfs slow, smbclient fast
still present in 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/854959 Title: Connect to windows share: gvfs slow, smbclient fast Status in gvfs package in Ubuntu: Confirmed Bug description: If I connect to a windows share using Places | Connect To Server | Windows Share (aka GVFS), a file copies from the server to my machine at 1 MB/sec If I connect to the same windows share from the same computer using a console "smbclient", the file copies at 15 MB/sec. Since smbclient can copy the same file from the same server to the same harddrive 15X faster than gvfs, there must be a problem with gvfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/854959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350754 -- 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/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783449] [NEW] /usr/lib/gvfs/gvfsd-gphoto2:11:handle_bulk_completion:reap_for_handle:op_handle_events:handle_events:libusb_handle_events_timeout_completed
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gvfs. This problem was most recently seen with package version 1:1.28.1-2salbabix27xenial, the problem page at https://errors.ubuntu.com/problem/ffa1bc405248760b9d7c53bc1f94b5f63331f570 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1783449 Title: /usr/lib/gvfs/gvfsd- gphoto2:11:handle_bulk_completion:reap_for_handle:op_handle_events:handle_events:libusb_handle_events_timeout_completed Status in gvfs package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gvfs. This problem was most recently seen with package version 1:1.28.1-2salbabix27xenial, the problem page at https://errors.ubuntu.com/problem/ffa1bc405248760b9d7c53bc1f94b5f63331f570 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1783449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 643536] Re: Can't drag and drop mails to desktop as file
** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- 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: Incomplete 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 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
This is pretty dire. Same behaviour here as discussed in the description, it's wasted a ton of my time today. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Critical -- 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/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 509665] Re: Printing multiple messages to file, gets overwritten
Thanks for the clarification, Orin. I will try your steps and get back to you. :) G -- 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/509665 Title: Printing multiple messages to file, gets overwritten Status in thunderbird package in Ubuntu: New Bug description: Binary package hint: thunderbird When printing multiple messages (in one go) to a file, only the last message ends up in the file. Apparently the file gets overwritten for each message. I expected the file to contain all messages. To reproduce: 1. Select multiple messages. 2. File -> Print... , select Print To File. Printer "PostScript/default". Enter filename and click Print. 3. View generated PostScript file (in Evince, for example) to see it only contains the last message. This on Ubuntu 9.10, Thunderbird version 2.0.0.23 (20090817). ProblemType: Bug Architecture: i386 Date: Tue Jan 19 15:36:58 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: mozilla-thunderbird (not installed) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-genUser Name SourcePackage: thunderbird Uname: Linux 2.6.31-17-generic i686 --- AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eric 2196 F pulseaudio BuildID: 20180522092515 Channel: Unavailable CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-06-04 (391 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.178.1 dev wlp14s0 proto static metric 600 169.254.0.0/16 dev wlp14s0 scope link metric 1000 192.168.178.0/24 dev wlp14s0 proto kernel scope link src 192.168.178.27 metric 600 Locales: extensions.sqlite corrupt or missing Package: thunderbird 1:52.8.0+build1-0ubuntu0.17.10.1 PackageArchitecture: amd64 PrefSources: prefs.js ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Profiles: Profile0 (Default) - LastVersion=52.8.0/20180522092515 (In use) RunningIncompatibleAddons: False Tags: artful wayland-session Themes: extensions.sqlite corrupt or missing Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: Upgraded to artful on 2018-01-06 (175 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA70_HC dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.13:bd11/13/2012:svnAcer:pnAspireV3-771:pvrV2.13:rvnAcer:rnVA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Aspire V3-771 dmi.product.version: V2.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/509665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 583577] Re: "View by Threads with Unread" results in no ability to read some messages
** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- 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/583577 Title: "View by Threads with Unread" results in no ability to read some messages Status in thunderbird package in Ubuntu: Incomplete Bug description: Binary package hint: thunderbird On a fairly regular basis Thunderbird will show me messages that I can't read or otherwise interact with when viewing in "Threads with Unread" mode. In the attached image there are several threads that clicking on the '+' sign has absolutely no action. I cannot click the green circle to mark the messages as read either. This doesn't happen ALL the time, but seems to happen in particular when duplicate messages are delivered (in this case a yahoo! groups mailing list that occasionally sends duplicates) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.4+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Thu May 20 15:22:39 2010 ProcEnviron: PATH=(custom, user) LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/583577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1464629] Re: sftp/ssh backend : missing dependencie with python-paramiko
duplicity does not require all backends (over 20 at this point) be installed and details are provided in the README about what modules to load. I have put this into the Ubuntu camp to see if they want to expand the selections past what they supply. ** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New ** No longer affects: duplicity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1464629 Title: sftp/ssh backend : missing dependencie with python-paramiko Status in duplicity package in Ubuntu: New Bug description: Ubuntu 15.04 duplicity 0.7.01 # duplicity list-current-files sftp://host Traceback (most recent call last): File "/usr/bin/duplicity", line 1544, in log.FatalError(u"%s: %s" % (e.__class__.__name__, util.uexc(e)), File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 78, in uexc return ufn(str(e)) # apt-get install python-paramiko # duplicity list-current-files sftp://host (works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1464629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Won't Fix ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Won't Fix Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783441] [NEW] [Inspiron 530, Realtek ALC888, Grey Line Out, Rear] No sound at all
Public bug reported: under sound panel output there is only a "dummy" profile and another is not possible to add. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph17719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 24 19:46:33 2018 InstallationDate: Installed on 2018-07-22 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph17719 F pulseaudio Symptom_Jack: Grey Line Out, Rear Symptom_Type: No sound at all Title: [Inspiron 530, Realtek ALC888, Grey Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1783441 Title: [Inspiron 530, Realtek ALC888, Grey Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: under sound panel output there is only a "dummy" profile and another is not possible to add. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph17719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 24 19:46:33 2018 InstallationDate: Installed on 2018-07-22 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph17719 F pulseaudio Symptom_Jack: Grey Line Out, Rear Symptom_Type: No sound at all Title: [Inspiron 530, Realtek ALC888, Grey Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1783441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718931] Re: No VPN autoconnect
Fixed in: gnome-shell (3.28.3-0ubuntu1) cosmic; urgency=medium * debian/patches/30-remoteMenu-Prevent-the-shell-from-becoming-unrespons.patch, debian/patches/magnifier.js-Fix-zoom-juddering.patch, debian/patches/st-label-Unset-clutter-text-instance-on-disposal.patch, debian/patches/st-texture-cache-Don-t-add-NULL-textures-to-cache.patch, debian/patches/st-texture-cache-Save-cairo-surfaces-to-a-different-map.patch, debian/patches/ui-Theme-lookup-should-respect-XDG_DATA_DIRS.patch: - Drop patches applied on the 3.28 branch * debian/patches/js-fix-invalid-access-errors.patch: - Refreshed to reflect upstream changes ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1718931 Title: No VPN autoconnect Status in NetworkManager: Incomplete Status in gnome-shell package in Ubuntu: Fix Released Bug description: [ Impact ] When setting up VPN to auto connect with wifi (done through nm- connection-editor) the wifi never manages to connect. However if I unselect the auto connect option while it is attempting a reconnection then it manages to connect to both (wifi and VPN). Doing the connection manually also poses no issues [ QA ] This is part of the upstream fix: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ProblemType: BugDistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 13:15:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-09 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) IpRoute: default via 192.168.0.1 dev wlp6s0 proto static metric 600 169.254.0.0/16 dev wlp6s0 scope link metric 1000 192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=trueSourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp6s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 VM5055940 85b8f881-7ed9-477a-9c39-9afb5a40bda9 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1718931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782614] Re: Upgrade to 3.28.3 and SRU it
Fixed in: gnome-shell (3.28.3-0ubuntu1) cosmic; urgency=medium * debian/patches/30-remoteMenu-Prevent-the-shell-from-becoming-unrespons.patch, debian/patches/magnifier.js-Fix-zoom-juddering.patch, debian/patches/st-label-Unset-clutter-text-instance-on-disposal.patch, debian/patches/st-texture-cache-Don-t-add-NULL-textures-to-cache.patch, debian/patches/st-texture-cache-Save-cairo-surfaces-to-a-different-map.patch, debian/patches/ui-Theme-lookup-should-respect-XDG_DATA_DIRS.patch: - Drop patches applied on the 3.28 branch * debian/patches/js-fix-invalid-access-errors.patch: - Refreshed to reflect upstream changes ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1782614 Title: Upgrade to 3.28.3 and SRU it Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Bug description: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, VPN fixes so network related featurs should be checked more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783436] [NEW] package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: poging tot overschrijven van gedeelde '/usr
Public bug reported: not possible to use simple scan ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 25 01:50:26 2018 ErrorMessage: poging tot overschrijven van gedeelde '/usr/share/hplip/data/models/models.dat', dat verschilt van andere exemplaren van pakket libsane-hpaio:i386 InstallationDate: Installed on 2018-07-24 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP-Color-LaserJet-CM1015: hp:/usb/HP_Color_LaserJet_CM1015?serial=00CNF87B6GGS device for HP_Color_LaserJet_CM1015: hp:/usb/HP_Color_LaserJet_CM1015?serial=00CNF87B6GGS MachineType: HP HP ProBook 450 G4 Papersize: a4 PpdFiles: HP-Color-LaserJet-CM1015: HP Color LaserJet CM1015 Postscript (recommended) HP_Color_LaserJet_CM1015: HP Color LaserJet CM1015 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=1885aef5-cd8b-4333-bd55-56959bb06ba2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: hplip Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: poging tot overschrijven van gedeelde '/usr/share/hplip/data/models/models.dat', dat verschilt van andere exemplaren van pakket libsane-hpaio:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2016 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.03 dmi.board.name: 8231 dmi.board.vendor: HP dmi.board.version: KBC Version 42.61 dmi.chassis.asset.tag: 5CD7133BF9 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.03:bd12/05/2016:svnHP:pnHPProBook450G4:pvr:rvnHP:rn8231:rvrKBCVersion42.61:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G4 dmi.sys.vendor: HP mtime.conffile..etc.hp.hplip.conf: 2018-07-25T01:43:41.235699 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1783436 Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: poging tot overschrijven van gedeelde '/usr/share/hplip/data/models/models.dat', dat verschilt van andere exemplaren van pakket libsane-hpaio:i386 Status in hplip package in Ubuntu: New Bug description: not possible to use simple scan ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 25 01:50:26 2018 ErrorMessage: poging tot overschrijven van gedeelde '/usr/share/hplip/data/models/models.dat', dat verschilt van andere exemplaren van pakket libsane-hpaio:i386 InstallationDate: Installed on 2018-07-24 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP-Color-LaserJet-CM1015: hp:/usb/HP_Color_LaserJet_CM1015?serial=00CNF87B6GGS device for HP_Color_LaserJet_CM1015: hp:/usb/HP_Color_LaserJet_CM1015?serial=00CNF87B6GGS MachineType: HP HP ProBook 450 G4 Papersize: a4 PpdFiles: HP-Color-LaserJet-CM1015: HP Color LaserJet CM1015 Postscript (recommended) HP_Color_LaserJet_CM1015: HP Color LaserJet CM1015 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=1885aef5-cd8b-4333-bd55-56959bb06ba2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: hplip Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: poging tot overschrijven van gedeelde '/usr/share/hplip/data/models/models.dat', dat verschilt van andere exemplaren van pakket libsane-hpaio:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2016 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.03 dmi.board.name: 8231 dmi.board.vendor: HP dmi.board.version: KBC Version 42.61 dmi.chassis.asset.tag: 5CD7133BF9 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias:
[Desktop-packages] [Bug 1695326] Re: Firefox loader hardening
Hi Monochromec, I am new to bug triaging and have no idea how to confirm for the above patch. Could you please confirm the above patch so we can close this ticket? Thanks G -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1695326 Title: Firefox loader hardening Status in firefox package in Ubuntu: Incomplete Bug description: If the ld cache configuration is wrong, the correct shared objects contained in the package are never found or wrong versions being picked up. Example: libnss3 is defined by a quite a few packages including Thunderbird, libnss3 and Firefox. Depending on the particular linker cache config, the wrong version may be picked up. Mitigation: enhance /usr/bin/firefox to explicitely include the correct path of its shared objects in the loader path (cf. attached patch). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1695326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772791] Re: Lock Screen displayed password in clear text on one occasion
I just ran into the same behavior. I typed my password quickly and automatically into the lock/login screen... and was disturbed to see the whole thing right there in plaintext as I was hitting enter. I poked at it a bit, and here's a reproducer: * Go to the lock/login screen. * Right-click on the password input field. You get a little popup menu. * One of the options is "Show Text". If you choose that option, the password input now shows in plain text. I'm pretty sure I wasn't anywhere near the mouse when I originally saw this behavior, so I suppose there's some keyboard sequence that invokes the same option. I must have mashed that as I was getting the screen to wake up. I see why this feature could sometimes be useful when encountering an unfamiliar keyboard layout, etc. But triggering it by accident is pretty startling; so I'd love to set an option to make it impossible to trigger. I can't find such an issue in the GNOME configuration, but I'm not at all confident the places I was able to find to look in are comprehensive. There's an issue upstream (in gnome-shell) where someone asked for such an option: https://bugzilla.redhat.com/show_bug.cgi?id=1506370 Also an older bug report where others ran into this behavior by accident (the reproducer someone found there was helpful to my finding a reproducer, though that exact sequence doesn't do it for me on gnome-shell 3.28): https://bugzilla.redhat.com/show_bug.cgi?id=1178806 There's even a RH Knowledge Base article for the question of how to disable it! https://access.redhat.com/solutions/3224961 That's marked "Solution Verified", which sure sounds like there is a way... but without a Red Hat subscription, I can't see what it says. The open gnome-shell issue sure makes it sound like there isn't one. ** Bug watch added: Red Hat Bugzilla #1506370 https://bugzilla.redhat.com/show_bug.cgi?id=1506370 ** Bug watch added: Red Hat Bugzilla #1178806 https://bugzilla.redhat.com/show_bug.cgi?id=1178806 -- 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/1772791 Title: Lock Screen displayed password in clear text on one occasion Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Hello, folks, Today when I returned to my computer (which I locked with Super+L) and attempted to unlock it, it displayed my passphrase in cleartext in the 'Password' box. I noticed as soon as I got the first character in, then typed in the second character and it stayed clear. I then picked up my phone to record the attached video and while I was fiddling with it to get a good camera shot, the screen locked (for inactivity perhaps?) and when I unlocked this time, the password only displayed as dots (as expected). So unfortunately, I don't know how to replicate. It _did_ occur though, as the attached video will show if you go slowly (look for "hu", the first characters of legendary password "hunter2"). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 22 20:27:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:07a1] Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Dell Oland [Radeon HD 8570 / R7 240/340 OEM] [1028:1002] InstallationDate: Installed on 2018-05-02 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04d9:a0d5 Holtek Semiconductor, Inc. Bus 001 Device 002: ID 046d:c338 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7050 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=9d600b65-ce52-4147-aace-2de5ac8c3c34 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.9 dmi.board.name: 0NW6H5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.9:bd01/30/2018:svnDellInc.:pnOptiPlex7050:pvr:rvnDellInc.:rn0NW6H5:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family:
[Desktop-packages] [Bug 921321]
Wrong commit, redid the bisect. 839ca903f12ef8f09374e0b655456482536a733e is the new suspect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/921321 Title: nouveau: dark screen after suspend/resume Status in Nouveau Xorg driver: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: Nouveau works fine with brightness controls working fine after initial boot, but I do S3 suspend, and then resume via power button, and brightness controls don't work at all, and backlight is on, but set at extremely low level. hardware is Quadro 770M on HP 8530w laptop /sys/.../brightness control does nothing when in this state, suspend resume cycles after this first cycle all have the same problem. I'll test if a full hibernate has the issue or not after this and report back. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 Uname: Linux 3.3.0-rc1+ x86_64 .tmp.unity.support.test.1: ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,move,compiztoolbox,grid,vpswitch,gnomecompat,place,session,snap,mousepoll,regex,resize,imgpng,unitymtgrabhandles,wall,animation,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: None Date: Tue Jan 24 15:57:58 2012 DistUpgraded: Log time: 2011-10-20 21:20:49.957387 DistroCodename: oneiric DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: nVidia Corporation G96M [Quadro FX 770M] [10de:065c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30e7] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: Hewlett-Packard HP EliteBook 8530w PccardctlIdent: Socket 0: product info: "RICOH", "Bay8Controller", "", "" manfid: 0x, 0x function: 254 (unknown) PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-rc1+ root=UUID=824346e6-fd2f-4916-a2c9-e883c1fe860c ro splash quiet vga=771 crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-21 (95 days ago) Xrandr: Screen 0: minimum 0 x 0, current 3200 x 1200, maximum 4096 x 4096 dmi.bios.date: 12/13/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDV Ver. F.13 dmi.board.name: 30E7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.27 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.13:bd12/13/2010:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.13:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.27:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8530w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6 version.ia32-libs: ia32-libs 20090808ubuntu26 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/921321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Same. Except has now progressed to restart not providing workaround. On 25 July 2018 at 03:18, tom <1583...@bugs.launchpad.net> wrote: > Confirm 18.04 / 4.15 still happening for me too :*( > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1583801 > > Title: > No sound via headphones (headset) when Ubuntu boots with them plugged > in > > Status in PulseAudio: > Confirmed > Status in alsa-driver package in Ubuntu: > Confirmed > Status in pulseaudio package in Ubuntu: > Confirmed > > Bug description: > The bug is twofold, first when computer boots if the headset > (headphones with built-in mic, one audio jack) is plugged in, then > there is no sound (via headphones or otherwise). If you plug > headphones out and back in, then it usually works as expected. > > The second scenario is the same, except that plugging out and back in > again doesn't help. In that case, I just restart the laptop, then plug > them back in again and it works. > > In all cases, microphone works. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 > Uname: Linux 4.4.0-22-generic x86_64 > NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: crunch 3248 F pulseaudio > CurrentDesktop: Unity > Date: Thu May 19 22:13:20 2016 > InstallationDate: Installed on 2016-05-07 (12 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: crunch 3248 F pulseaudio > Symptom_Jack: Black Headphone Out, Left > Symptom_Type: No sound at all > Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No > sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/07/2016 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 01.02.00 > dmi.board.name: 0N7TVV > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.: > pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.name: XPS 15 9550 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/pulseaudio/+bug/1583801/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV
[Desktop-packages] [Bug 1783415] [NEW] Network-Manager misses option to disconnect VPN
Public bug reported: There is no menu item in the VPN submenu to disconnect a VPN connection. Only "configuring VPN" is offered. The only way to terminate a VPN connection is to click on the ongoing VPN connection again to trigger an error. Issue also discussed here: https://ubuntuforums.org/showthread.php?t=2355162 Such menu option did exit in Ubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 24 23:16:02 2018 EcryptfsInUse: Yes IpRoute: default via 192.168.178.1 dev enp0s25 proto static metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.178.0/24 dev enp0s25 proto kernel scope link src 192.168.178.37 metric 100 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. docker0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/2 docker0 edcde2ee-239e-42a5-808a-afa29c27e05c /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s25 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 3d00e91a-e309-402c-b847-0c1d7444192e /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "No menu item to terminate VPN connection" https://bugs.launchpad.net/bugs/1783415/+attachment/5167308/+files/Auswahl_002.jpg ** Summary changed: - Network-Manager missiong option to disconnect VPN + Network-Manager missing option to disconnect VPN ** Summary changed: - Network-Manager missing option to disconnect VPN + Network-Manager misses option to disconnect VPN ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167309/+files/CRDA.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167310/+files/Dependencies.txt ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167312/+files/IpAddr.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167317/+files/PciNetwork.txt ** Attachment removed: "nmcli-con.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167321/+files/nmcli-con.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167320/+files/WifiSyslog.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167319/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167318/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167316/+files/NetworkManager.conf.txt ** Attachment removed: "NetDevice.lo.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167315/+files/NetDevice.lo.txt ** Attachment removed: "NetDevice.enp0s25.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167314/+files/NetDevice.enp0s25.txt ** Attachment removed: "NetDevice.docker0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167313/+files/NetDevice.docker0.txt ** Attachment removed: "IfupdownConfig.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1783415/+attachment/5167311/+files/IfupdownConfig.txt -- You received this bug notification
[Desktop-packages] [Bug 700257] Re: Banshee does not import songs without extension
Hello. I am a new member of the Ubuntu community and I want to help to fix this bug. What are the steps to take? Should I download the development code using bzr and start reviewing the code and making changes? Is git supported? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/700257 Title: Banshee does not import songs without extension Status in Banshee: New Status in banshee package in Ubuntu: Triaged Bug description: Binary package hint: banshee In Natty we moved to Banshee from rhythmbox. Rhythmbox syncs songs from portable devices without any extension (atleast for ipod shuffle) when you import those songs in Banshee they are not added. I opened a bug upstream which turned out be a duplicate of an already 'wontfix' bug. I believe we need to fix this issue since many of our users would have imported songs from rhythmbox to their systems and when they wont be able to play those songs with the new default Music player that wont be good. To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/700257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783404] [NEW] unable to handle kernel NULL pointer dereference at 0000000000000230
Public bug reported: About a week and a half ago I would lose rendering of the desktop randomly while under a Wayland session. I would have the last displayed images on my monitor, mouse movement worked, video and audio still workedd, but visual feedback was lost when clicking on items in the browser or last app opened. Spacebar would work fine to pause a video, or media keys to stop the music player. I've been trying to hunt down the reason until I realised that I might be running under Wayland instead of Xorg. I changed the configuration option in /etc/gdm3/custom.conf to disable Wayland and enabled debugging and restarted. I was away from my desk earlier when I logged, in a few minutes later the screen went black, as if it went into power saving mode. Unlike the Wayland sessions I wasn't able to get to any TTY's. Upon restarting I noticed the following, which wasn't present in the previous journal under Wayland (see attached - to large for description field). At this point, this seems to be occurring randomly. I'm happy to help with debugging if need be. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-radeon 1:18.0.1-1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 24 21:33:29 2018 DistUpgraded: 2018-01-24 20:50:51,381 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-24-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7850] Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1458:254c] InstallationDate: Installed on 2016-10-25 (636 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: MSI MS-7850 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=de66cbe2-16ea-4c60-9081-ed9a0306f7af ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to bionic on 2018-01-24 (181 days ago) dmi.bios.date: 02/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V5.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV5.9:bd02/16/2016:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnH97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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-bug bionic ubuntu ** Attachment added: "Output of journalctl --since=2018-07-24 | grep kernel | grep radeon" https://bugs.launchpad.net/bugs/1783404/+attachment/5167273/+files/radeon.txt -- 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/1783404 Title: unable to handle kernel NULL pointer dereference at 0230 Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: About a week and a half ago I would lose rendering of the desktop randomly while under a Wayland session. I would have the last displayed images on my monitor, mouse movement worked, video and audio still workedd, but visual feedback was lost when clicking on items in the browser or last app opened. Spacebar would work fine to pause a video, or media keys to stop the music player. I've been trying to hunt down the reason until I realised that I might be running under Wayland instead
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated. Details below. Bug just happened again on unlocking session (versus switching users). I compared the output of journalctl. ## Around unlock time: nothing to see Around unlock time, journalctl only shows lightdm cleanup activity. Then, only when bug happens, lightdm starts again the whole sequence : systemd[somepid]: Starting User Manager for UID 110... systemd-logind[749]: New session c9 of user lightdm. systemd[somepid]: Started Session c9 of user lightdm. ... ## Around lock time: same correlation between log order and bug occurrence Again Indeed, bug happens when log is in this order: at-spi-bus-launcher[25560]: dbus-daemon[25565]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") at-spi-bus-launcher[25560]: dbus-daemon[25565]: Successfully activated service 'org.a11y.atspi.Registry' at-spi-bus-launcher[25560]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry dbus-daemon[25559]: [session uid=110 pid=25559] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") and things go smoothly when log is in this order: at-spi-bus-launcher[15685]: dbus-daemon[15690]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") dbus-daemon[15684]: [session uid=110 pid=15684] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") at-spi-bus-launcher[15685]: dbus-daemon[15690]: Successfully activated service 'org.a11y.atspi.Registry' at-spi-bus-launcher[15685]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719408] Re: Application window outside of its frame in spread mode
** Changed in: gnome-shell Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1719408 Title: Application window outside of its frame in spread mode Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/3 https://gitlab.gnome.org/GNOME/gnome-shell/issues/143 https://bugzilla.gnome.org/show_bug.cgi?id=792681 https://bugzilla.gnome.org/show_bug.cgi?id=776588 Test Case: 1. On a workspace with no window, toggle spread mode (super key) 2. Open a terminal with its keybinding: CTRL+ALT+T Expected result The terminal opens in the center of the screen with a frame around it Actual result The frame is displayed in the center of the screen but the application window is outside of the frame (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-bin 1.14.0-1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 15:00:29 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-11-generic, x86_64: installed virtualbox, 5.1.28, 4.13.0-11-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1507] InstallationDate: Installed on 2013-09-03 (1482 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1719408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
After downgrading gnome-shell and gnome-shell-common to version 3.28.2-0ubuntu1 all is back to normal. -- 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/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1695326] Re: Firefox loader hardening
Hasn't surfaces in recent releases but I haven't checked the presence of my suggested patch in the distribution. I would recommend confirming the above patch before closing this ticket. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1695326 Title: Firefox loader hardening Status in firefox package in Ubuntu: Incomplete Bug description: If the ld cache configuration is wrong, the correct shared objects contained in the package are never found or wrong versions being picked up. Example: libnss3 is defined by a quite a few packages including Thunderbird, libnss3 and Firefox. Depending on the particular linker cache config, the wrong version may be picked up. Mitigation: enhance /usr/bin/firefox to explicitely include the correct path of its shared objects in the loader path (cf. attached patch). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1695326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
** Attachment added: "Example log when things fail (bug happens)." https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+attachment/5167261/+files/2018y07m24d-16h34m12s_activite_repro_1776475_je_passe_sur_session_stephane_avec_export_xdg_seat_path__org_freedesktop_displaymanager_seat0___dm_tool_switch_to_user_stephaneexit.timestamped.log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
In order to investigate this bug, I started to write down each time I switch user and whether it works. The time information allowed to obtain time-bounded log extracts that focus on relevant parts using journalctl --since ... --until ... . After 3 "work" and one "fail" case, I observed a correlation, which might or might not be relevant. ## Logs when no bug, things work The following log sequence happens all 3 times things work okay: 2018-07-24T13:00:38.327651+0200 n551jk systemd[16387]: Startup finished in 26ms. 2018-07-24T13:00:38.327693+0200 n551jk systemd[1]: Started User Manager for UID 110. 2018-07-24T13:00:38.360247+0200 n551jk systemd[16387]: Started D-Bus User Message Bus. 2018-07-24T13:00:38.363237+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] AppArmor D-Bus mediation is enabled 2018-07-24T13:00:38.363739+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.364556+0200 n551jk systemd[16387]: Starting Accessibility services bus... 2018-07-24T13:00:38.368461+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Successfully activated service 'org.a11y.Bus' 2018-07-24T13:00:38.368546+0200 n551jk systemd[16387]: Started Accessibility services bus. 2018-07-24T13:00:38.371337+0200 n551jk at-spi-bus-launcher[16408]: dbus-daemon[16413]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.373982+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.374774+0200 n551jk at-spi-bus-launcher[16408]: dbus-daemon[16413]: Successfully activated service 'org.a11y.atspi.Registry' 2018-07-24T13:00:38.374918+0200 n551jk at-spi-bus-launcher[16408]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry 2018-07-24T13:00:38.375082+0200 n551jk systemd[16387]: Starting Virtual filesystem service... ## Logs when bug happens, things fail The bug happened once since I started to write down each operation, and it shows a difference: 2018-07-24T16:34:15.777621+0200 n551jk systemd[23296]: Startup finished in 23ms. 2018-07-24T16:34:15.777665+0200 n551jk systemd[1]: Started User Manager for UID 110. 2018-07-24T16:34:15.820108+0200 n551jk systemd[23296]: Started D-Bus User Message Bus. 2018-07-24T16:34:15.822959+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] AppArmor D-Bus mediation is enabled 2018-07-24T16:34:15.823499+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.824373+0200 n551jk systemd[23296]: Starting Accessibility services bus... 2018-07-24T16:34:15.828552+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Successfully activated service 'org.a11y.Bus' 2018-07-24T16:34:15.828659+0200 n551jk systemd[23296]: Started Accessibility services bus. 2018-07-24T16:34:15.831689+0200 n551jk at-spi-bus-launcher[23317]: dbus-daemon[23322]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.835154+0200 n551jk at-spi-bus-launcher[23317]: dbus-daemon[23322]: Successfully activated service 'org.a11y.atspi.Registry' 2018-07-24T16:34:15.835289+0200 n551jk at-spi-bus-launcher[23317]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry 2018-07-24T16:34:15.835578+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.836417+0200 n551jk systemd[23296]: Starting Virtual filesystem service... ## Difference between "work" and "fail" All 3 lines mentioning at-spi-bus-launcher come *before* : dbus-daemon ... Activating via systemd: service name='org.gtk.vfs.Daemon'. I don't know it this is relevant at this point in time. No other salient difference in logs. Logs attached. ** Attachment added: "Example log when things work." https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+attachment/5167260/+files/2018y07m24d-12h42m24s_activite_je_passe_sur_session_stephane_avec_export_xdg_seat_path__org_freedesktop_displaymanager_seat0___dm_tool_switch_to_user_stephaneexit.timestamped.log.txt -- You received this bug notification because you are a member
[Desktop-packages] [Bug 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
Same bug here too. -- 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/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
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/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
** Description changed: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons - simply don't appear on the screen. + simply don't appear on the screen. I'm also unable to search for + applications. Logging out and back in again is necessary to restore proper - functionality. + functionality until of course I again user the super key etc. - At first I thought this would only affect my main user but I also have + At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: New Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] Re: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
** Description changed: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the - launcher. Logging out and back in again is necessary to restore proper + launcher. At this point I can't use "Show Applications" as the icons + simply don't appear on the screen. + + Logging out and back in again is necessary to restore proper functionality. At first I thought this would only affect my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. - I've disabled all extensions but the problem remains. + I've disabled all extensions and of course rebooted but the problem + remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: New Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. At this point I can't use "Show Applications" as the icons simply don't appear on the screen. I'm also unable to search for applications. Logging out and back in again is necessary to restore proper functionality until of course I again user the super key etc. At first I thought this was only affecting my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions and of course rebooted but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Confirm 18.04 / 4.15 still happening for me too :*( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783364] Re: Preference 'recursive-search' is ignored when set to 'never'
According to Carlos Soriano from the Nautilus team this was broken be the Ubuntu patches. When can we expect a fix? Thank you! -- 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/1783364 Title: Preference 'recursive-search' is ignored when set to 'never' Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: --- 1. Run gsettings set org.gnome.nautilus.preferences recursive-search 'never' 2. Restart Nautilus 3. Search within Nautilus Current behavior --- Even after setting recursive-search to 'never' the search is still executed recursive. Expected behavior --- After setting recursive-search to 'never' the search should be not recursive anymore (only the current folder should be searched). Reproducible in: --- Ubuntu 18.04 with Nautilus 3.26.3-0ubuntu4 Releated upstream bugs: https://gitlab.gnome.org/GNOME/nautilus/issues/547 https://gitlab.gnome.org/GNOME/nautilus/issues/520 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1783364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783371] Re: ubuntu versions of libreoffice writer render and print some documents improperly, they show up with fewer/missing pages
output of ubuntu-bug attached, but as far as I can tell there is nothing system-specific about this bug, stock Ubuntu 18.04 is affected. ** Attachment added: "sudo ubuntu-bug --save lowriter.bug libreoffice-writer" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1783371/+attachment/5167228/+files/lowriter.bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1783371 Title: ubuntu versions of libreoffice writer render and print some documents improperly, they show up with fewer/missing pages Status in libreoffice package in Ubuntu: New Bug description: Libreoffice writer as packaged by Ubuntu is rendering and printing some documents incorrectly - differently than the debs from libreoffice and the versions for most other OSes. It is possibly triggered by lots of overlapping images that were pasted into the document. When you open the attached document it should show up as 7 pages. However with 6.0.3.2 ( 1:6.0.3-0ubuntu1 ) in the standard Ubuntu 18.04 repositories it briefly shows 1/7 pages in the lower left as the document loads and then switches to 1/5 pages, and only 5 pages show up and print. The same thing happens with 6.0.5.2 from the libreoffice fresh ppa and 6.0.6 from the prereleases ppa. This has been repeated using a clean 18.04 install, dist-upgraded. Between versions I remove --purge libreoffice* and delete. .config/libreoffice/. I filed this bug at libreoffice: https://bugs.documentfoundation.org/show_bug.cgi?id=118597 but then found out that the problem does not occur using a different OS like windows or redhat or debian or manjaro. ( linux mint shows the same behavior as Ubuntu). If you open that document with the .deb files downloaded directly from the libreoffice site and installed into /opt then the document renders as 7 pages. So it sure seems like this is an Ubuntu-specific bug. As mentioned in the libreoffice bug it is not as simple as a VCL gtk3 vs. gtk2 difference, I don't know what else is different between the ubuntu repository and ppa packages and the debs from libreoffice. The problem was initially discovered under Ubuntu 16.04 using 6.0.5.2 from the fresh ppa , some documents were showing as 7 pages but only 5 pages were printing, but only with certain printer ppds. The fact that the document displays as 7 vs. 5 pages is much easier to see and replicate and is hopefully related to the original printing missing pages problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1783371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783371] [NEW] ubuntu versions of libreoffice writer render and print some documents improperly, they show up with fewer/missing pages
Public bug reported: Libreoffice writer as packaged by Ubuntu is rendering and printing some documents incorrectly - differently than the debs from libreoffice and the versions for most other OSes. It is possibly triggered by lots of overlapping images that were pasted into the document. When you open the attached document it should show up as 7 pages. However with 6.0.3.2 ( 1:6.0.3-0ubuntu1 ) in the standard Ubuntu 18.04 repositories it briefly shows 1/7 pages in the lower left as the document loads and then switches to 1/5 pages, and only 5 pages show up and print. The same thing happens with 6.0.5.2 from the libreoffice fresh ppa and 6.0.6 from the prereleases ppa. This has been repeated using a clean 18.04 install, dist-upgraded. Between versions I remove --purge libreoffice* and delete. .config/libreoffice/. I filed this bug at libreoffice: https://bugs.documentfoundation.org/show_bug.cgi?id=118597 but then found out that the problem does not occur using a different OS like windows or redhat or debian or manjaro. ( linux mint shows the same behavior as Ubuntu). If you open that document with the .deb files downloaded directly from the libreoffice site and installed into /opt then the document renders as 7 pages. So it sure seems like this is an Ubuntu-specific bug. As mentioned in the libreoffice bug it is not as simple as a VCL gtk3 vs. gtk2 difference, I don't know what else is different between the ubuntu repository and ppa packages and the debs from libreoffice. The problem was initially discovered under Ubuntu 16.04 using 6.0.5.2 from the fresh ppa , some documents were showing as 7 pages but only 5 pages were printing, but only with certain printer ppds. The fact that the document displays as 7 vs. 5 pages is much easier to see and replicate and is hopefully related to the original printing missing pages problem. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "document that should be 7 pages but only renders as 5 on Ubuntu 18.04" https://bugs.launchpad.net/bugs/1783371/+attachment/5167227/+files/flowers-7-pages.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1783371 Title: ubuntu versions of libreoffice writer render and print some documents improperly, they show up with fewer/missing pages Status in libreoffice package in Ubuntu: New Bug description: Libreoffice writer as packaged by Ubuntu is rendering and printing some documents incorrectly - differently than the debs from libreoffice and the versions for most other OSes. It is possibly triggered by lots of overlapping images that were pasted into the document. When you open the attached document it should show up as 7 pages. However with 6.0.3.2 ( 1:6.0.3-0ubuntu1 ) in the standard Ubuntu 18.04 repositories it briefly shows 1/7 pages in the lower left as the document loads and then switches to 1/5 pages, and only 5 pages show up and print. The same thing happens with 6.0.5.2 from the libreoffice fresh ppa and 6.0.6 from the prereleases ppa. This has been repeated using a clean 18.04 install, dist-upgraded. Between versions I remove --purge libreoffice* and delete. .config/libreoffice/. I filed this bug at libreoffice: https://bugs.documentfoundation.org/show_bug.cgi?id=118597 but then found out that the problem does not occur using a different OS like windows or redhat or debian or manjaro. ( linux mint shows the same behavior as Ubuntu). If you open that document with the .deb files downloaded directly from the libreoffice site and installed into /opt then the document renders as 7 pages. So it sure seems like this is an Ubuntu-specific bug. As mentioned in the libreoffice bug it is not as simple as a VCL gtk3 vs. gtk2 difference, I don't know what else is different between the ubuntu repository and ppa packages and the debs from libreoffice. The problem was initially discovered under Ubuntu 16.04 using 6.0.5.2 from the fresh ppa , some documents were showing as 7 pages but only 5 pages were printing, but only with certain printer ppds. The fact that the document displays as 7 vs. 5 pages is much easier to see and replicate and is hopefully related to the original printing missing pages problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1783371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-menus (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in OEM Priority Project: Confirmed Status in gnome-menus package in Ubuntu: Confirmed Status in gnome-menus source package in Xenial: Confirmed Bug description: Dell XPS 13 9360 (CID 201606-22338) pre-installed (oem) image Xenial [Description] When I tried to perform 16.04 --> 18.04 update, the update process failed. The process guide me to file this bug report. [Steps to reproduce] 1. Update the system to the latest stack by "sudo apt-get update; sudo apt-get dist-upgrade -y" 2. Reboot 3. Make sure /etc/update-manager/release-upgrades is able to update (The configuration value of "Prompt" should be "lts", namely "Prompt=lts", not "Prompt=never"). 4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade -d" 5. During the update process, it prompts for "Configuring gdm3". There are two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the attachment for the prompt details as well. We should use "-d" because bionic beaver has not been officially released yet. [Expected Result] The release update completed and I could start using Bionic instead of Xenial. [Actual Result] The update process failed. It shows the error message[1] and automatically asking for filing this bug report. [1] Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over (5.5.1-1ubuntu1) ... Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb ... Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over (5.5.1-2ubuntu6) ... (Reading database ... 253705 files and directories currently installed.) Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ... Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ... Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ... Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: bamfdaemon -> gnome-menus packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications bamfdaemon: /usr/share/applications libglib2.0-0:amd64: /usr/share/glib-2.0/schemas desktop-file-utils: /usr/share/applications mime-support: /usr/share/applications dpkg: error processing package gnome-menus (--remove): triggers looping, abandoned Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ... Errors were encountered while processing: gnome-menus ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/gnome-menus.0.crash' Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (376.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): .. (a lot of them) qml-module-qtquick-controls2:amd64 qml-module-org-kde-kconfig:amd64 libunity-control-center1 libqt5quickcontrols2-5:amd64 libglib2.0-bin libkf5plasma5:amd64 locales qml-module-qtqml-models2:amd64 libkf5coreaddons5:amd64 gir1.2-goa-1.0:amd64 libwebkit2gtk-4.0-37:amd64 Processing was halted because there were too many errors. Upgrade complete The upgrade has completed but there were errors during the upgrade process. To continue please press [ENTER] ubuntu@201606-22338:~$ == ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 22:00:01 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned
[Desktop-packages] [Bug 1783364] Re: Preference 'recursive-search' is ignored when set to 'never'
Not sure if that is a bug in the Nautilus upstream source or the patches applied by the Ubuntu devs break the behaviour. ** Description changed: Steps to reproduce: --- 1. Run gsettings set org.gnome.nautilus.preferences recursive-search 'never' 2. Restart Nautilus 3. Search within Nautilus Current behavior --- Even after setting recursive-search to 'never' the search is still executed recursive. Expected behavior --- After setting recursive-search to 'never' the search should be not recursive anymore (only the current folder should be searched). Reproducible in: --- - Ubuntu 18.04 with Nautilus 1:3.26.3-0ubuntu4 + Ubuntu 18.04 with Nautilus 3.26.3-0ubuntu4 Releated upstream bugs: https://gitlab.gnome.org/GNOME/nautilus/issues/547 https://gitlab.gnome.org/GNOME/nautilus/issues/520 -- 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/1783364 Title: Preference 'recursive-search' is ignored when set to 'never' Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: --- 1. Run gsettings set org.gnome.nautilus.preferences recursive-search 'never' 2. Restart Nautilus 3. Search within Nautilus Current behavior --- Even after setting recursive-search to 'never' the search is still executed recursive. Expected behavior --- After setting recursive-search to 'never' the search should be not recursive anymore (only the current folder should be searched). Reproducible in: --- Ubuntu 18.04 with Nautilus 3.26.3-0ubuntu4 Releated upstream bugs: https://gitlab.gnome.org/GNOME/nautilus/issues/547 https://gitlab.gnome.org/GNOME/nautilus/issues/520 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1783364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783364] [NEW] Preference 'recursive-search' is ignored when set to 'never'
Public bug reported: Steps to reproduce: --- 1. Run gsettings set org.gnome.nautilus.preferences recursive-search 'never' 2. Restart Nautilus 3. Search within Nautilus Current behavior --- Even after setting recursive-search to 'never' the search is still executed recursive. Expected behavior --- After setting recursive-search to 'never' the search should be not recursive anymore (only the current folder should be searched). Reproducible in: --- Ubuntu 18.04 with Nautilus 3.26.3-0ubuntu4 Releated upstream bugs: https://gitlab.gnome.org/GNOME/nautilus/issues/547 https://gitlab.gnome.org/GNOME/nautilus/issues/520 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1783364 Title: Preference 'recursive-search' is ignored when set to 'never' Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: --- 1. Run gsettings set org.gnome.nautilus.preferences recursive-search 'never' 2. Restart Nautilus 3. Search within Nautilus Current behavior --- Even after setting recursive-search to 'never' the search is still executed recursive. Expected behavior --- After setting recursive-search to 'never' the search should be not recursive anymore (only the current folder should be searched). Reproducible in: --- Ubuntu 18.04 with Nautilus 3.26.3-0ubuntu4 Releated upstream bugs: https://gitlab.gnome.org/GNOME/nautilus/issues/547 https://gitlab.gnome.org/GNOME/nautilus/issues/520 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1783364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783363] [NEW] Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed
Public bug reported: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. Logging out and back in again is necessary to restore proper functionality. At first I thought this would only affect my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1783363 Title: Use of activities in GNOME Shell 3.28.3 prohibits applications from being displayed Status in gnome-shell package in Ubuntu: New Bug description: I noticed this problem immediately after updating GNOME Shell to 3.28.3 this afternoon. If I log in the super key works as normal as does "Show Applications". If I then start an application and then use the super key I cannot again use any open application. I have to close applications from the launcher. Logging out and back in again is necessary to restore proper functionality. At first I thought this would only affect my main user but I also have two other users set up. Their profiles have not been customised. I see the same behaviour with both users. Any display of Activities or Show Applications prohibits any further use of opened programs. I've disabled all extensions but the problem remains. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 24 17:02:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-12 (12 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
Unbelievable. Upgraded to Ubuntu 18.04 to find out about this crappy behaviour. Please fix it. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711617] Re: file conflict with gnome-shell-extension-dashtodock
There is no schedule schema changes as of now, so current replaces: is still good and we'll see later on if we fork the schema or not. Sounds good for the current states at least. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1711617 Title: file conflict with gnome-shell-extension-dashtodock Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: While upgrading to current artful I got this: trying to overwrite '/usr/share/glib-2.0/schemas/org.gnome.shell.extensions.dash-to-dock.gschema.xml', which is also in package gnome-shell-extension-dashtodock 60-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1711617/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769893] Re: CUPS Unauthorized when using Chrome browser in Ubuntu 18.04
** Summary changed: - CUPS Unauthorized when using Chrome browser + CUPS Unauthorized when using Chrome browser in Ubuntu 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1769893 Title: CUPS Unauthorized when using Chrome browser in Ubuntu 18.04 Status in cups package in Ubuntu: Confirmed Bug description: Using Chrome Version 66.0.3359.139 (Official Build) (64-bit) I am able to access and add a printer through Chrome by going to the page http://localhost:631/admin/login and I can add a printer fine. But I cannot add the printer if I go directly to http://localhost:631/admin and bypass the login. If I need to change any defaults of the printer through the same pages it gives me the "Unauthorized" and will not change anything. I can change it in Firefox and the printers control panel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 (Authentication failure) E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Tue May 8 07:18:47 2018 InstallationDate: Installed on 2018-05-05 (2 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for Deskjet_3520_series_75C0A7_: ipp://HP6C3BE575C0A7.local:631/ipp/print device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253 MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', '/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd: Permission denied grep: /etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5dae0d38-9bbe-48de-b110-62763c862892 ro nosplash net.ifnames=0 biosdevname=0 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: K9N2GM-FIH(MS-7508) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.8:bd09/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7508 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775226] Re: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
** Changed in: gnome-software (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1775226 Title: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades Status in gnome-software package in Ubuntu: New Bug description: In Ubuntu the GUI for upgrading packages is update-manager allowing debconf questions to be answered when needed and Ubuntu also offers unattended-upgrades for upgrading packages in the background and it keeps back packages from upgrading when configuration-file changes would need user interaction during the upgrade. Unattended-upgrades can be configured to perform upgrades during system shutdown. Gnome Software in Bionic started offering performing upgrades during shutdown using PackageKit independently from update-manager and unattended-upgrades without offering all of the features of either one. Unless there is a decision to fully switch to Gnome Software I suggest disabling the "Install pending software updates" on the shutdown screen to avoid confusing users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
This affects all academic users that uses eduroam to connect to the internet. Please fix. Eduroam did work with ubuntu 17.10 -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: Connection to open or WPA secured wifi works without any issues. Connection to WPA2/PEAP fails. Repeatedly asks for username/password. Possible gnome-shell integration issue. The system was updated from Xenial to Bionic in mid-January. At that time this WPA2/PEAP setup worked without any issues. With the updates coming in the last week of January / First February week - the bug was experienced. 1) ➜ syncthing git:(master) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) - up to date packages [code] ➜ cat /etc/apt/sources.list |egrep -v '^#' deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted [/code] Note: # some pkg version related to problem might be from proposed-updates repo 2b) [code] dpkg -l |egrep -i 'network manager|networkm|libnm' ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm-glib/libnm-util library ii gir1.2-nm-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm library ii gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1 amd64GObject introspection data for libnm-gtk ii libnm-glib-vpn1:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib VPN shared library) ii libnm-glib4:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib shared library) ii libnm-gtk0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm-glib version) ii libnm-util2:amd64 1.8.4-1ubuntu4 amd64network management framework (shared library) ii libnm0:amd64 1.8.4-1ubuntu4 amd64GObject-based client library for NetworkManager ii libnma0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm version) ii libproxy1-plugin-networkmanager:amd64 0.4.15-0ubuntu1 amd64automatic proxy configuration management library (Network Manager plugin) ii network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 all NetworkManager configuration to enable connectivity checking ii strongswan-nm 5.6.1-2ubuntu1 amd64strongSwan plugin to interact with NetworkManager ii wpasupplicant 2:2.6-15ubuntu2 amd64client support for WPA and WPA2 (IEEE 802.11i) [/code] 3,4) Connection to open or WPA secured wifi works withou any issues. Connection to WPA2/PLEAP (without cert, just with username/password fails). Although wifi layer get's is associated the client (network-manager) possibly due to bug deauthenticate itself without establishing an IP connection. Connect to network. 5) Logs (syslog/kernel) Core moments: [code] Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9125] keyfile: update /etc/NetworkManager/system-connections/WiFi (82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi") Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed and ... Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9450] device (wlp4s0): Activation: (wifi) connection 'WiFi' has security, and secrets exist. No new secrets needed. Feb 12 09:19:02 dontpanic
[Desktop-packages] [Bug 1525170] Re: caja crashed with signal 7
Thanks for the update, Lukas. I will close the ticket now. :) G Closed per reporter's feedback. ** Changed in: gvfs (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1525170 Title: caja crashed with signal 7 Status in gvfs package in Ubuntu: Invalid Bug description: crashed while starting thunderbird ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: caja 1.10.4-1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: MATE Date: Fri Dec 11 11:57:59 2015 ExecutablePath: /usr/bin/caja JournalErrors: No journal files were found. -- No entries -- ProcCmdline: caja ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: caja StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so Title: caja crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: employee rzcip-m sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1525170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769893] Re: CUPS Unauthorized when using Chrome browser
I solved using this command # usermod -aG lpadmin YourUserName -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1769893 Title: CUPS Unauthorized when using Chrome browser Status in cups package in Ubuntu: Confirmed Bug description: Using Chrome Version 66.0.3359.139 (Official Build) (64-bit) I am able to access and add a printer through Chrome by going to the page http://localhost:631/admin/login and I can add a printer fine. But I cannot add the printer if I go directly to http://localhost:631/admin and bypass the login. If I need to change any defaults of the printer through the same pages it gives me the "Unauthorized" and will not change anything. I can change it in Firefox and the printers control panel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 (Authentication failure) E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Tue May 8 07:18:47 2018 InstallationDate: Installed on 2018-05-05 (2 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for Deskjet_3520_series_75C0A7_: ipp://HP6C3BE575C0A7.local:631/ipp/print device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253 MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', '/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd: Permission denied grep: /etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5dae0d38-9bbe-48de-b110-62763c862892 ro nosplash net.ifnames=0 biosdevname=0 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: K9N2GM-FIH(MS-7508) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.8:bd09/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7508 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718931] Re: No VPN autoconnect
** Description changed: + [ Impact ] + When setting up VPN to auto connect with wifi (done through nm- connection-editor) the wifi never manages to connect. However if I unselect the auto connect option while it is attempting a reconnection then it manages to connect to both (wifi and VPN). Doing the connection manually also poses no issues - ProblemType: Bug - DistroRelease: Ubuntu 17.10 + [ QA ] + + This is part of the upstream fix: + https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + ProblemType: BugDistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 13:15:55 2017 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2017-09-09 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) IpRoute: - default via 192.168.0.1 dev wlp6s0 proto static metric 600 - 169.254.0.0/16 dev wlp6s0 scope link metric 1000 - 192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600 + default via 192.168.0.1 dev wlp6s0 proto static metric 600 + 169.254.0.0/16 dev wlp6s0 scope link metric 1000 + 192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - SourcePackage: network-manager + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=trueSourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: - DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH - wlp6s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 VM5055940 85b8f881-7ed9-477a-9c39-9afb5a40bda9 /org/freedesktop/NetworkManager/ActiveConnection/1 - lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- + DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH + wlp6s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 VM5055940 85b8f881-7ed9-477a-9c39-9afb5a40bda9 /org/freedesktop/NetworkManager/ActiveConnection/1 + lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.8.2connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.8.2connected started full enabled enabled enabled enabled enabled -- 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/1718931 Title: No VPN autoconnect Status in NetworkManager: Incomplete Status in gnome-shell package in Ubuntu: In Progress Bug description: [ Impact ] When setting up VPN to auto connect with wifi (done through nm- connection-editor) the wifi never manages to connect. However if I unselect the auto connect option while it is attempting a reconnection then it manages to connect to both (wifi and VPN). Doing the connection manually also poses no issues [ QA ] This is part of the upstream fix: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ProblemType: BugDistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 13:15:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-09 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) IpRoute: default via 192.168.0.1 dev wlp6s0 proto static metric 600 169.254.0.0/16 dev wlp6s0 scope link metric 1000 192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=trueSourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH
[Desktop-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error
How long? Errors were encountered while processing: /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb /var/cache/apt/archives/kaccounts-providers_4%3a15.12.3-0ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Got this on clean Ubuntu Xenial 16.04 LTS (!!!) installation without any PPA. ** Tags removed: wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Fix Released Status in Telepathy KDE: Fix Released Status in kaccounts-integration package in Ubuntu: Fix Committed Status in kaccounts-providers package in Ubuntu: Fix Committed Status in ktp-accounts-kcm package in Ubuntu: Triaged Status in libaccounts-glib package in Ubuntu: Fix Released Status in kaccounts-providers source package in Wily: Triaged Status in ktp-accounts-kcm source package in Wily: Triaged Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) SRU information === [Impact] It's not possible to install KDE and Unity in co-existence because of several file conflicts: many files under /usr/share/accounts/{providers,services}/ are provided by both the package "kaccounts-providers" and packages build from the "account- plugins" source package, for example 'account-plugin-facebook'. [Test case] Install both kaccounts-providers and account-plugin-facebook: you'll get file conflicts for /usr/share/accounts/services/facebook-im.service and /usr/share/accounts/providers/facebook.provider. You might get other conflicts as well, but those are due to bug 1565772 (also nominated for SRU). [Regression potential] Minimal: the changed packages belong to the default KDE installation, and have already landed in Yakkety. Things appear to be working fine there: account creation is still possible under KDE, even after changing the file paths as per this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782614] Re: Upgrade to 3.28.3 and SRU it
** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1782614 Title: Upgrade to 3.28.3 and SRU it Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Bionic: In Progress Bug description: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, VPN fixes so network related featurs should be checked more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 720011] Re: The page appears complete, but does not open, is a blank page.
Thank you for your reply. As this wasn't a confirmed bug we're closing this report as being "Invalid". Thank you again for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/720011 Title: The page appears complete, but does not open, is a blank page. Status in firefox package in Ubuntu: Invalid Bug description: Binary package hint: firefox Este erro ocorre no firefox, tanto no ubuntu como em windows. não possibilitando o uso da página: http://sistn.caixa.gov.br:443/sistn_internet/ ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 Architecture: i386 Date: Wed Feb 16 10:11:12 2011 FirefoxPackages: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=pt_BR:pt:en LANG=pt_BR.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/720011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780677] Re: X session crash after resuming from suspend
I noticed the status is still incomplete. What additional information should be provided? Thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1780677 Title: X session crash after resuming from suspend Status in xorg-server package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7 First I suspended my laptop, while a few applications were running (Firefox, Chrome and some others much smaller). A couple of hours later, I opened the lid and expected the Gnome session would resume. What happened instead was a crash of the X server, then the login page was shown again and a new Gnome session started: the old session got killed! In the Xorg.0.log.old file I found this, not sure if related: [ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0 [ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error [ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error [ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error [ 21189.338] (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 8 23:03:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidia, 390.48, 4.15.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05cc] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc] InstallationDate: Installed on 2018-06-21 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/vg-root ro scsi_mod.scan=sync quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 720011] Re: The page appears complete, but does not open, is a blank page.
The page was taken from the air, so the bug has no reason to remain open. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/720011 Title: The page appears complete, but does not open, is a blank page. Status in firefox package in Ubuntu: Incomplete Bug description: Binary package hint: firefox Este erro ocorre no firefox, tanto no ubuntu como em windows. não possibilitando o uso da página: http://sistn.caixa.gov.br:443/sistn_internet/ ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 Architecture: i386 Date: Wed Feb 16 10:11:12 2011 FirefoxPackages: firefox 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.13+build3+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=pt_BR:pt:en LANG=pt_BR.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/720011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783311] Re: Upgrade to 3.28.3 and SRU it
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Bionic) Status: New => In Progress ** Changed in: mutter (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1783311 Title: Upgrade to 3.28.3 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Bug description: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, some changes to the monitor management, so changing settings there should be tested deeply. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1783311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783311] [NEW] Upgrade to 3.28.3 and SRU it
Public bug reported: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, some changes to the monitor management, so changing settings there should be tested deeply. ** Affects: mutter (Ubuntu) Importance: Medium Status: Fix Released ** Affects: mutter (Ubuntu Bionic) Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- 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/1783311 Title: Upgrade to 3.28.3 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Bug description: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, some changes to the monitor management, so changing settings there should be tested deeply. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1783311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 726439] Re: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed
Modern bug link is https://gitlab.gnome.org/GNOME/yelp/issues/52 . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/726439 Title: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed Status in Yelp: Expired Status in yelp package in Ubuntu: Confirmed Bug description: Binary package hint: yelp TEST CASE: 1. Launch Yelp 2. Select the menu 'Go / All Documents" 2. Enter some text (e.g nautilus) in the address bar 3. Hit Enter Result: The following error is displayed: """ Unknown Error The URI ‘xref:search=nautilus’ could not be parsed. """ Expected Results: List of documents matching the search list is returned ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: yelp 2.91.90-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 Architecture: i386 Date: Mon Feb 28 11:01:37 2011 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: yelp To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/726439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1782739] Re: Boot to Black
Daniel, I am fairly literate and I am an IT professional by trade (Cisco Voice), however I am not a desktop specialist and especially not a Linux specialist. I am very willing to learn and do all I can to help resolve this issue but I would not know how to tell which kernel I am currently running nor how to select and install one from that massive list you provided. I do so appreciate your help and I hope it continues to be extended to a willing novice. Thank you Gene On Mon, Jul 23, 2018 at 9:15 PM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > OK. Next please try some newer (or older) kernels and see if you can > find a version which fixes the bug: > > http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1782739 > > Title: > Boot to Black > > Status in gdm3 package in Ubuntu: > Incomplete > Status in linux package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see > the splash screen as expected. The boot continues and it reaches the > point where you would expect to see the login screen. I see what > appears to be a non-backlighted blank black screen. If I wait until > all hard drive activity ceases and then type in my password and press > enter the login completes and I am presented a normal Ubuntu desktop. > > Thank you > Gene > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7 > ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 > Uname: Linux 4.15.0-23-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jul 20 07:16:51 2018 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation Haswell-ULT Integrated Graphics Controller > [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics > Controller [1043:166d] > InstallationDate: Installed on 2018-07-20 (0 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: ASUSTeK COMPUTER INC. TP550LA > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic > root=UUID=5b0bd839-3614-4f3d-8536-bc400cd364e5 ro quiet splash > vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/27/2014 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: TP550LA.210 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: TP550LA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP550LA.210:bd06/27/2014: > svnASUSTeKCOMPUTERINC.:pnTP550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.: > rnTP550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: TP > dmi.product.name: TP550LA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.91-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782739/+subscriptions > -- 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/1782739 Title: Boot to Black Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see the splash screen as expected. The boot continues and it reaches the point where you would expect to see the login screen. I see what appears to be a non-backlighted blank black screen. If I wait until all hard drive
[Desktop-packages] [Bug 802468] Re: Searching returns "Unknown error" e.g. "The URI ‘xref:search=orca’ could not be parsed." [wishlist: more helpful error message]
*** This bug is a duplicate of bug 726439 *** https://bugs.launchpad.net/bugs/726439 ** This bug has been marked a duplicate of bug 726439 Search for document returns an Unknown error: 'URI xref:search=' could not be parsed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/802468 Title: Searching returns "Unknown error" e.g. "The URI ‘xref:search=orca’ could not be parsed." [wishlist: more helpful error message] Status in yelp package in Ubuntu: New Bug description: I have the Orca screen reader installed. Clicking on it's "help" button shows the Orca documentation, as expected. However, if I run "gnome-help" manually, and then type "orca" in the location bar and press enter, I get an error: Unknown Error The URI ‘xref:search=orca’ could not be parsed. It's completely possible that I've neglected to install the package that implements this feature. But Ubuntu has spoilt me - I'm expecting a better class of error message. Usually Ubuntu is very good about telling you if there's a missing package, and what you need to install to make it work as intended. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: yelp 3.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Mon Jun 27 11:43:50 2011 ProcEnviron: LANGUAGE=C:en PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: yelp UpgradeStatus: Upgraded to natty on 2011-06-19 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/802468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I can also confirm this bug is still very much present (and an annoying feature) in 18.04, under Xorg. Ctrl+C works as expected though. Alt+[Arrow keys] switches VTs. -- 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/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
A 'backport' of "nvidia-340_340.106-0ubuntu3_amd64.deb" from Bionic should do the trick as this is fixed by NVidia in nvidia-340.106: http://www.nvidia.com/Download/driverResults.aspx/130042/en-us "Release Highlights: Fixed a compatibility problem between the nvidia.ko's Page Attribute Table (PAT) support and the kernel Page Table Isolation (PTI) patches." Forcing the installation of "nvidia-340_340.106-0ubuntu3_amd64.deb" from Bionic on Xenial seems to work: sudo dpkg -i --force-depends nvidia-340_340.106-0ubuntu3_amd64.deb This then needs a little massaging: sudo ln -s /usr/lib/nvidia-340/xorg /etc/alternatives/x86_64-linux-gnu_xorg_extra_modules sudo ln -s /etc/alternatives/x86_64-linux-gnu_xorg_extra_modules /usr/lib/x86_64-linux-gnu/xorg/extra-modules And commenting out ModulePath "/usr/lib/nvidia-340/xorg" in /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275290] Re: users-admin crashed with SIGSEGV in g_slice_free1()
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1275290/+attachment/3965540/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1275290 Title: users-admin crashed with SIGSEGV in g_slice_free1() Status in gnome-system-tools package in Ubuntu: New Bug description: I added a new user for which the home directory already existed. The user was added but a crash was reported once the additon process was complete. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-system-tools 3.0.0-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 1 17:45:29 2014 ExecutablePath: /usr/bin/users-admin InstallationDate: Installed on 2014-02-01 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140201) ProcCmdline: users-admin ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ffce5c8e6ad:mov(%rsi),%rdx PC (0x7ffce5c8e6ad) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-system-tools StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_type_free_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: users-admin crashed with SIGSEGV in g_slice_free1() 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-system-tools/+bug/1275290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783298] [NEW] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Public bug reported: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS /hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian.
[Desktop-packages] [Bug 1743736] Re: In overview, windows from all workspaces are shown for the second display (when using "Workspaces span displays")
@David: thanks for the link to the extension you saved my life :) works like a charm! sry, for noobing around, found the "affect me" button now. thanks & best regards! -- 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/1743736 Title: In overview, windows from all workspaces are shown for the second display (when using "Workspaces span displays") Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: I have disabled workspaces on primary display only, and I have enabled workspaces to span displays, in tweak tool. Now things mostly work how I expect. Windows are isolated to the workspace they are and I can move them between displays (monitors). The issue is if I go into an overview mode. Then, for the primary display, I see only windows from my current workspace. But for the secondary display, I see windows from all workspaces being shown in the overview mode. I would expect that only the windows from the current workspace are shown also on the secondary display in the overview mode. ProblemType: Bug 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-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 02:19:13 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-11-20 (57 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) This bug also affects the new LTS release: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 23 15:25:07 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-05-18 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1743736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743094] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Won't Fix Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748518] Re: [snap] bullets rendered incorrectly in docx files
Does this issue appear in LibreOffice 6.0.6 installed from ppa:libreoffice/libreoffice-prereleases ? If yes, then please report this issue at https://bugs.documentfoundation.org and add link to bugreport here (click on +Also affects project) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1748518 Title: [snap] bullets rendered incorrectly in docx files Status in libreoffice package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/call-for-testing- libreoffice-6-0-0/3917/6) Steps to reproduce: 1) create a text document with bullet points 2) save it in the docx format 3) close libreoffice, then re-open the document with writer Expected result: the bullets are rendered correctly as they were when the document was created and saved Actual result: bullets are rendered with another different glyph (that appears to vary from one setup to the other). I'm attaching a screenshot that demonstrates the issue (from the original forum post). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748518/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 726439] Re: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed
Ubuntu 16.04 LTS and 18.04 LTS are still affected by this bug. ** Changed in: yelp (Ubuntu) Status: Triaged => Confirmed ** Tags removed: i386 mago natty running-unity ** Tags added: bionic cosmic trusty xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/726439 Title: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed Status in Yelp: Expired Status in yelp package in Ubuntu: Confirmed Bug description: Binary package hint: yelp TEST CASE: 1. Launch Yelp 2. Select the menu 'Go / All Documents" 2. Enter some text (e.g nautilus) in the address bar 3. Hit Enter Result: The following error is displayed: """ Unknown Error The URI ‘xref:search=nautilus’ could not be parsed. """ Expected Results: List of documents matching the search list is returned ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: yelp 2.91.90-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 Architecture: i386 Date: Mon Feb 28 11:01:37 2011 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: yelp To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/726439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1525170] Re: caja crashed with signal 7
I'm sorry I forgot about this bug. I think it can be closed I switched to cinnamon since but my college is using Mate now and doesn't seem to occur anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1525170 Title: caja crashed with signal 7 Status in gvfs package in Ubuntu: Incomplete Bug description: crashed while starting thunderbird ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: caja 1.10.4-1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: MATE Date: Fri Dec 11 11:57:59 2015 ExecutablePath: /usr/bin/caja JournalErrors: No journal files were found. -- No entries -- ProcCmdline: caja ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: caja StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so Title: caja crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: employee rzcip-m sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1525170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
This is still happening on Ubuntu 18.04 and kernel 4.15 :( (Dell XPS 9550) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340250] Re: "#pragma weak" symbol is 0 even when defined
gcc u.c -Wl,--no-as-needed -lm; ./a.out; echo $? 0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1340250 Title: "#pragma weak" symbol is 0 even when defined Status in binutils package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Status in libidn package in Ubuntu: New Status in libunistring package in Ubuntu: New Bug description: This compiler bug is making the gnulib tests dump core; see: http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html Compile and run the following program t.c with the shell commands "gcc u.c -lm; ./a.out; echo $?" #include #pragma weak tgamma int main (void) { if (!tgamma) return 2; if (tgamma (1) == 1) return 0; return 1; } The program will exit with status 2. It should exit with status 0, because the math library does have a tgamma function and the function pointer should be non-null. I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu 4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcc 4:4.8.2-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 10 07:39:11 2014 InstallationDate: Installed on 2012-12-21 (566 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gcc-defaults UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1340250] Re: "#pragma weak" symbol is 0 even when defined
Wl,--no-as-needed works, while adding a manual "-lpthread" doesn't, because the library doesn't get linked to the program. Reason is probably that weak symbols are not added by the linker -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1340250 Title: "#pragma weak" symbol is 0 even when defined Status in binutils package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Status in libidn package in Ubuntu: New Status in libunistring package in Ubuntu: New Bug description: This compiler bug is making the gnulib tests dump core; see: http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html Compile and run the following program t.c with the shell commands "gcc u.c -lm; ./a.out; echo $?" #include #pragma weak tgamma int main (void) { if (!tgamma) return 2; if (tgamma (1) == 1) return 0; return 1; } The program will exit with status 2. It should exit with status 0, because the math library does have a tgamma function and the function pointer should be non-null. I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu 4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcc 4:4.8.2-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 10 07:39:11 2014 InstallationDate: Installed on 2012-12-21 (566 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gcc-defaults UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783264] Re: Xorg crash
It sounds like some part of the system has crashed. Please: 1. Apply the workaround from bug 994921. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash and tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the contents of the /var/lib/whoopsie/whoopsie-id file on the machine. Do you find any links to recent problems on the machine? If so then please send them to us. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1783264 Title: Xorg crash Status in Ubuntu: Incomplete Bug description: When the screen is turned off, sometime the computer freeze and logs me out. When logged in, i dont see any of my previously working programs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jul 24 07:22:09 2018 DistUpgraded: 2018-05-03 07:29:33,985 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0654] InstallationDate: Installed on 2018-03-02 (143 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 3543 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=6b4dcdfb-e9e1-494c-bfc4-471c1dd908d9 ro quiet splash acpi_backlight=vendor "acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-03 (81 days ago) dmi.bios.date: 03/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0WTMPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/20/2015:svnDellInc.:pnInspiron3543:pvrA04:rvnDellInc.:rn0WTMPT:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1783264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783265] Re: Freeze
*** This bug is a duplicate of bug 1783264 *** https://bugs.launchpad.net/bugs/1783264 Let's handle this as bug 1783264. ** This bug has been marked a duplicate of bug 1783264 Xorg crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1783265 Title: Freeze Status in xorg package in Ubuntu: New Bug description: The system freezes and logs me out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jul 24 07:32:29 2018 DistUpgraded: 2018-05-03 07:29:33,985 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0654] InstallationDate: Installed on 2018-03-02 (143 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 3543 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=6b4dcdfb-e9e1-494c-bfc4-471c1dd908d9 ro quiet splash acpi_backlight=vendor "acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-03 (82 days ago) dmi.bios.date: 03/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0WTMPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/20/2015:svnDellInc.:pnInspiron3543:pvrA04:rvnDellInc.:rn0WTMPT:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1783265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783264] [NEW] Xorg crash
Public bug reported: When the screen is turned off, sometime the computer freeze and logs me out. When logged in, i dont see any of my previously working programs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jul 24 07:22:09 2018 DistUpgraded: 2018-05-03 07:29:33,985 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0654] InstallationDate: Installed on 2018-03-02 (143 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 3543 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=6b4dcdfb-e9e1-494c-bfc4-471c1dd908d9 ro quiet splash acpi_backlight=vendor "acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-03 (81 days ago) dmi.bios.date: 03/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0WTMPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/20/2015:svnDellInc.:pnInspiron3543:pvrA04:rvnDellInc.:rn0WTMPT:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1783264 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: When the screen is turned off, sometime the computer freeze and logs me out. When logged in, i dont see any of my previously working programs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jul 24 07:22:09 2018 DistUpgraded: 2018-05-03 07:29:33,985 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0654] InstallationDate: Installed on 2018-03-02 (143 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 3543 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=6b4dcdfb-e9e1-494c-bfc4-471c1dd908d9 ro quiet splash acpi_backlight=vendor "acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-03 (81 days ago) dmi.bios.date: 03/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0WTMPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell
[Desktop-packages] [Bug 1783265] [NEW] Freeze
Public bug reported: The system freezes and logs me out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jul 24 07:32:29 2018 DistUpgraded: 2018-05-03 07:29:33,985 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0654] InstallationDate: Installed on 2018-03-02 (143 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 3543 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=6b4dcdfb-e9e1-494c-bfc4-471c1dd908d9 ro quiet splash acpi_backlight=vendor "acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-03 (82 days ago) dmi.bios.date: 03/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0WTMPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/20/2015:svnDellInc.:pnInspiron3543:pvrA04:rvnDellInc.:rn0WTMPT:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1783265 Title: Freeze Status in xorg package in Ubuntu: New Bug description: The system freezes and logs me out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jul 24 07:32:29 2018 DistUpgraded: 2018-05-03 07:29:33,985 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0654] InstallationDate: Installed on 2018-03-02 (143 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 3543 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=6b4dcdfb-e9e1-494c-bfc4-471c1dd908d9 ro quiet splash acpi_backlight=vendor "acpi_osi=!Windows 2013" "acpi_osi=!Windows 2012" vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-03 (82 days ago) dmi.bios.date: 03/20/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0WTMPT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/20/2015:svnDellInc.:pnInspiron3543:pvrA04:rvnDellInc.:rn0WTMPT:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3543 dmi.product.version: A04 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri