[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it
The output of the command you asked for is $ systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-02-17 08:51:10 -03; 5h 33min ago Docs: man:NetworkManager(8) Main PID: 1206 (NetworkManager) Tasks: 3 (limit: 4915) Memory: 22.7M CGroup: /system.slice/NetworkManager.service └─1206 /usr/sbin/NetworkManager --no-daemon fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9009] device (p2p-dev-wlp3s0): supplicant management interface state: com fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9421] device (wlp3s0): supplicant interface state: authenticating -> asso fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9422] device (p2p-dev-wlp3s0): supplicant management interface state: aut fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9453] device (wlp3s0): supplicant interface state: associating -> associa fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9453] device (p2p-dev-wlp3s0): supplicant management interface state: ass fev 17 08:51:54 adcamp NetworkManager[1206]: [1581940314.0257] device (wlp3s0): supplicant interface state: associated -> complete fev 17 08:51:54 adcamp NetworkManager[1206]: [1581940314.0274] device (p2p-dev-wlp3s0): supplicant management interface state: ass fev 17 08:55:57 adcamp NetworkManager[1206]: [1581940557.0456] agent-manager: req[0x5652c8d3ab10, :1.407/org.gnome.Shell.NetworkAg fev 17 09:00:01 adcamp NetworkManager[1206]: [1581940801.3983] dhcp4 (wlp3s0): state changed bound -> expire fev 17 09:00:01 adcamp NetworkManager[1206]: [1581940801.3985] device (wlp3s0): DHCPv4: 480 seconds grace period started As the other thread mentions, it seems that it has to do with the NetworkManager. Since mine was already running (as I understood from the output above), I restarted it with $systemctl restart NetworkManager and the settings are working again. But the outputs of the status seems the same to me. See, after restart $ systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-02-17 15:15:22 -03; 14s ago Docs: man:NetworkManager(8) Main PID: 9778 (NetworkManager) Tasks: 4 (limit: 4915) Memory: 7.7M CGroup: /system.slice/NetworkManager.service └─9778 /usr/sbin/NetworkManager --no-daemon fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8784] device (p2p-dev-wlp3s0): supplicant management interface state: dis fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8802] device (wlp3s0): supplicant interface state: authenticating -> asso fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8802] device (p2p-dev-wlp3s0): supplicant management interface state: aut fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8924] device (wlp3s0): supplicant interface state: associating -> associa fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8924] device (p2p-dev-wlp3s0): supplicant management interface state: ass fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0012] device (wlp3s0): supplicant interface state: associated -> complete fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0013] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0013] device (p2p-dev-wlp3s0): supplicant management interface state: ass fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0015] device (wlp3s0): state change: config -> ip-config (reason 'none', fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0020] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 se However, the settings open only once. After closing it, it gives the same error. And if I restart the NetworkManager it opens again (once). -- 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/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description:
[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it
Sure. The output is $ dpkg -l | grep gnome-control-center ii gnome-control-center 1:3.34.1-1ubuntu2 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:3.34.1-1ubuntu2 all configuration applets for GNOME - data files ii gnome-control-center-faces1:3.34.1-1ubuntu2 all utilities to configure the GNOME desktop - faces images $ which gnome-control-center /usr/bin/gnome-control-center $ ldd -r $(which gnome-control-center) linux-vdso.so.1 (0x7ffd25b1f000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7ff46de64000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7ff46de07000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7ff46dcdf000) libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7ff46d5cc000) libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7ff46d4c8000) libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7ff46d4b7000) libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7ff46d469000) libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7ff46d43f000) libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x7ff46d31f000) libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7ff46d2f7000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff46d1a8000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7ff46d06a000) libcheese.so.8 => /usr/lib/x86_64-linux-gnu/libcheese.so.8 (0x7ff46d054000) libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7ff46d042000) libcheese-gtk.so.25 => /usr/lib/x86_64-linux-gnu/libcheese-gtk.so.25 (0x7ff46d031000) libwacom.so.2 => /usr/lib/x86_64-linux-gnu/libwacom.so.2 (0x7ff46d023000) libsnapd-glib.so.1 => /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1 (0x7ff46cfd1000) libsoup-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 (0x7ff46cf36000) libgnome-desktop-3.so.18 => /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.18 (0x7ff46cef1000) libgoa-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 (0x7ff46cea2000) libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x7ff46cce2000) libcolord.so.2 => /usr/lib/x86_64-linux-gnu/libcolord.so.2 (0x7ff46cc91000) libcolord-gtk.so.1 => /usr/lib/x86_64-linux-gnu/libcolord-gtk.so.1 (0x7ff46cc87000) libpolkit-gobject-1.so.0 => /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 (0x7ff46cc67000) libupower-glib.so.3 => /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 (0x7ff46cc3a000) libudisks2.so.0 => /usr/lib/x86_64-linux-gnu/libudisks2.so.0 (0x7ff46cbc) libgtop-2.0.so.11 => /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11 (0x7ff46cba4000) libgudev-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7ff46cb97000) libgoa-backend-1.0.so.1 => /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 (0x7ff46cb34000) libnm.so.0 => /usr/lib/x86_64-linux-gnu/libnm.so.0 (0x7ff46c9e4000) libnma.so.0 => /usr/lib/x86_64-linux-gnu/libnma.so.0 (0x7ff46c982000) libmm-glib.so.0 => /usr/lib/x86_64-linux-gnu/libmm-glib.so.0 (0x7ff46c8a6000) libgnome-bluetooth.so.13 => /usr/lib/x86_64-linux-gnu/libgnome-bluetooth.so.13 (0x7ff46c86) libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x7ff46c7cf000) libsmbclient.so.0 => /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 (0x7ff46c7a5000) libwhoopsie-preferences.so.0 => /usr/lib/x86_64-linux-gnu/libwhoopsie-preferences.so.0 (0x7ff46c799000) libaccountsservice.so.0 => /usr/lib/x86_64-linux-gnu/libaccountsservice.so.0 (0x7ff46c748000) libibus-1.0.so.5 => /usr/lib/x86_64-linux-gnu/libibus-1.0.so.5 (0x7ff46c6cf000) libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7ff46c689000) libsecret-1.so.0 => /usr/lib/x86_64-linux-gnu/libsecret-1.so.0 (0x7ff46c634000) libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0 (0x7ff46c5df000) libpulse-mainloop-glib.so.0 => /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0 (0x7ff46c5d9000) libgsound.so.0 => /usr/lib/x86_64-linux-gnu/libgsound.so.0 (0x7ff46c5d) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7ff46c4f3000) libpwquality.so.1 => /usr/lib/x86_64-linux-gnu/libpwquality.so.1 (0x7ff46c4ea000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff46c4c7000) libc.so.6 =>
[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it
Further information. After updating the packages the error returned (nvidia is still uninstalled). $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) The kernel is the same. -- 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/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it
Strangely, purging nvidia drivers seems to fix the issue (following advice from https://askubuntu.com/a/1183137/44054). However, I had a different error as noted in the original bug description. However, now I can't have nvidia working with the settings. -- 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/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862767] [NEW] gnome-control-center crashes when try to open it
Public bug reported: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- 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/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V
I have the same issue on Ubuntu 18.04.1 LTS (kernel 4.15.0-38-generic) connected with DisplayLink (driver 4.4.24). I'm connecting through Display port on a Dell Inspiron 15, and a docker D6000. The flicker occurs only on the laptop's monitor, and the external monitors seem fine. No flicker whatsoever. As similar reports, when the docker is disconnected the flicker stops. -- 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/1724307 Title: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V Status in xorg package in Ubuntu: Triaged Bug description: When I connect my laptop to my DisplayLink based device with USB (Wavlink universal USB 3.0 docking station https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers as per the following video: https://launchpadlibrarian.net/346625588/20171121_131417.mp4 Only if the mouse is on the laptop monitor, it can vanish for several minutes, but remains active. Animations/overlays or typing inside a Chrome window causes the mouse pointer to flicker more often. If there is no interaction or animation, the mouse pointer remains static and drawn. Monitor 1: 1920 x 1080 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor This issue doesn't happen if I don't connect my laptop to an external monitor via the Wavlink device. This issue is reproducible with DisplayLink driver 1.4, and 1.3.54. This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64. I've reported this to DisplayLink via: https://displaylink.org/forum/showthread.php?p=84713#post84713 WORKAROUND: Use GNOME Flashback (Metacity) session. WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary monitor change Rotation from Normal to any of the following: Clockwise Anti-clockwise 180 degrees ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 17 10:01:55 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:082a] InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.1 dmi.board.name: 05FPM2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Oct 17 09:39:15 2017 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5193 vendor SHP xserver.version: 2:1.19.3-1ubuntu1~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1646985] Re: Customizable keyboard shortcuts don't work anymore
Upgraded to 17.04 and problem persists. -- 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/1646985 Title: Customizable keyboard shortcuts don't work anymore Status in Nautilus: Incomplete Status in nautilus package in Ubuntu: Confirmed Bug description: Enabling the shortcut for "open a terminal here" in Ubuntu 16.10, by uncommenting (or adding) (gtk_accel_path "/ExtensionsMenuGroup/TerminalNautilus:OpenFolderLocal" "F12") in ~/.config/nautilus/accels is not working. I tested it on an upgraded machine from 16.04 to 16.10. The accelerator was working on 16.04 and it is not in 16.10. Also tested on freshly installed machine with 16.10. Same problem. Did the action accelerator changed for opening a terminal in the local folder? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1646985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1622265] Re: Alienware 17R3 sound stop working randomly, it returns after booting into Windows
I just updated all the packages yesterday. The audio card stop working and just had a constant noise sound. Booted into windows to try to restore it, as previously that work. And Windows couldn't find the device, nor the software to restore the card. After shutting the computer down and running a diagnostic (the one shipped with the laptop), I booted back into windows and the card appear again. Booted back into Ubuntu 16.10 just to discover that the card was working again. Probably some drivers issues? -- 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/1622265 Title: Alienware 17R3 sound stop working randomly, it returns after booting into Windows Status in alsa-driver package in Ubuntu: New Bug description: The sound stops working in what it seems a random fashion. The first time it happened, I started going through the sound troubleshooting, did all the installation and rebooting and the sound didn't come back. I came back later to uploads the logs, but changing the input from "Digital output" to "Line out" made the sound work again. So I didn't bother with uploading the logs. Now, the sound is gone again, without no apparent reason. Went through the troubleshooting again and the sound is not working (as before). However, changing the line to "Line out" is not working as before. I noticed that booting into Windows and booting back to Ubuntu restore the sound. Also, I have the problem of the headphones not working. I'm not sure if that is relevant, but better to tell the whole story. Here is the output of running Step 3 and 4 of the troubleshooting guide (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1622265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1646985] [NEW] "Open terminal here" shortcut not working
Public bug reported: Enabling the shortcut for "open a terminal here" in Ubuntu 16.10, by uncommenting (or adding) (gtk_accel_path "/ExtensionsMenuGroup/TerminalNautilus:OpenFolderLocal" "F12") in ~/.config/nautilus/accels is not working. I tested it on an upgraded machine from 16.04 to 16.10. The accelerator was working on 16.04 and it is not in 16.10. Also tested on freshly installed machine with 16.10. Same problem. Did the action accelerator changed for opening a terminal in the local folder? ** 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/1646985 Title: "Open terminal here" shortcut not working Status in nautilus package in Ubuntu: New Bug description: Enabling the shortcut for "open a terminal here" in Ubuntu 16.10, by uncommenting (or adding) (gtk_accel_path "/ExtensionsMenuGroup/TerminalNautilus:OpenFolderLocal" "F12") in ~/.config/nautilus/accels is not working. I tested it on an upgraded machine from 16.04 to 16.10. The accelerator was working on 16.04 and it is not in 16.10. Also tested on freshly installed machine with 16.10. Same problem. Did the action accelerator changed for opening a terminal in the local folder? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1646985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609211] Re: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all
Updated to Ubuntu 16.10, and the problem persists.
--
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/1609211
Title:
[Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at
all
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
When the headphones are plugged, they are not detected. All sound
comes from the built in speakers, and none from the headphones.
The jack works on Windows.
This bug seems similar to #1184838. However, I'm posting it as the
hardware is different.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: adin 4035 F...m pulseaudio
/dev/snd/controlC0: adin 4035 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 2 22:59:12 2016
InstallationDate: Installed on 2016-07-03 (30 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 successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: adin 4035 F...m pulseaudio
/dev/snd/controlC0: adin 4035 F pulseaudio
adin 32107 F alsamixer
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2016
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.15
dmi.board.name: Alienware 17 R3
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.name: Alienware 17 R3
dmi.product.version: 1.2.15
dmi.sys.vendor: Alienware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1609211/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1622265] [NEW] Alienware 17R3 sound stop working randomly, it returns after booting into Windows
Public bug reported: The sound stops working in what it seems a random fashion. The first time it happened, I started going through the sound troubleshooting, did all the installation and rebooting and the sound didn't come back. I came back later to uploads the logs, but changing the input from "Digital output" to "Line out" made the sound work again. So I didn't bother with uploading the logs. Now, the sound is gone again, without no apparent reason. Went through the troubleshooting again and the sound is not working (as before). However, changing the line to "Line out" is not working as before. I noticed that booting into Windows and booting back to Ubuntu restore the sound. Also, I have the problem of the headphones not working. I'm not sure if that is relevant, but better to tell the whole story. Here is the output of running Step 3 and 4 of the troubleshooting guide (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output of running the commands of troubleshooting guide" https://bugs.launchpad.net/bugs/1622265/+attachment/4738472/+files/output.txt -- 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/1622265 Title: Alienware 17R3 sound stop working randomly, it returns after booting into Windows Status in alsa-driver package in Ubuntu: New Bug description: The sound stops working in what it seems a random fashion. The first time it happened, I started going through the sound troubleshooting, did all the installation and rebooting and the sound didn't come back. I came back later to uploads the logs, but changing the input from "Digital output" to "Line out" made the sound work again. So I didn't bother with uploading the logs. Now, the sound is gone again, without no apparent reason. Went through the troubleshooting again and the sound is not working (as before). However, changing the line to "Line out" is not working as before. I noticed that booting into Windows and booting back to Ubuntu restore the sound. Also, I have the problem of the headphones not working. I'm not sure if that is relevant, but better to tell the whole story. Here is the output of running Step 3 and 4 of the troubleshooting guide (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1622265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609211] [NEW] [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all
Public bug reported: When the headphones are plugged, they are not detected. All sound comes from the built in speakers, and none from the headphones. The jack works on Windows. This bug seems similar to #1184838. However, I'm posting it as the hardware is different. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: adin 4035 F...m pulseaudio /dev/snd/controlC0: adin 4035 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 2 22:59:12 2016 InstallationDate: Installed on 2016-07-03 (30 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 successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: adin 4035 F...m pulseaudio /dev/snd/controlC0: adin 4035 F pulseaudio adin 32107 F alsamixer Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.15 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.15 dmi.sys.vendor: Alienware ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1609211 Title: [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: When the headphones are plugged, they are not detected. All sound comes from the built in speakers, and none from the headphones. The jack works on Windows. This bug seems similar to #1184838. However, I'm posting it as the hardware is different. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: adin 4035 F...m pulseaudio /dev/snd/controlC0: adin 4035 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 2 22:59:12 2016 InstallationDate: Installed on 2016-07-03 (30 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 successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: adin 4035 F...m pulseaudio /dev/snd/controlC0: adin 4035 F pulseaudio adin 32107 F alsamixer Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.15 dmi.board.name: Alienware 17 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 17 R3 dmi.product.version: 1.2.15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1609211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://la
