[Bug 1835332] Re: Add support for NVMe devices
Mate-applets merged https://github.com/mate-desktop/mate- applets/pull/409 to work around the libgtop issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1835332 Title: Add support for NVMe devices To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/1835332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835332] Re: Add support for NVMe devices
A patch was provided at https://github.com/mate-desktop/mate- applets/issues/290 ** Bug watch added: gitlab.gnome.org/GNOME/libgtop/issues #43 https://gitlab.gnome.org/GNOME/libgtop/issues/43 ** Also affects: libgtop via https://gitlab.gnome.org/GNOME/libgtop/issues/43 Importance: Unknown Status: Unknown ** Bug watch added: github.com/mate-desktop/mate-applets/issues #290 https://github.com/mate-desktop/mate-applets/issues/290 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1835332 Title: Add support for NVMe devices To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/1835332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835332] [NEW] Add support for NVMe devices
Public bug reported: The system load monitor applet 3.28.0 does not show disk I/O when NVMe disks are used (white box in the screen shot). This is because NVMe devices are named e.g. /dev/nvme0n1 instead of e.g. /dev/sda1. This is a tracking bug. To be fixed via gnome-applets: https://gitlab.gnome.org/GNOME/gnome-applets/issues/12 libgtop (root of the issue): https://gitlab.gnome.org/GNOME/libgtop/issues/43 (contains more details) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-applets 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jul 4 04:12:13 2019 InstallationDate: Installed on 2014-11-29 (1677 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-applets UpgradeStatus: Upgraded to bionic on 2018-09-18 (288 days ago) ** Affects: gnome-applets Importance: Unknown Status: Unknown ** Affects: libgtop Importance: Unknown Status: Unknown ** Affects: gnome-applets (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "Disk IO in system load applet (right box is white for NVMe disk)" https://bugs.launchpad.net/bugs/1835332/+attachment/5274970/+files/Auswahl_860.png ** Bug watch added: gitlab.gnome.org/GNOME/gnome-applets/issues #12 https://gitlab.gnome.org/GNOME/gnome-applets/issues/12 ** Also affects: gnome-applets via https://gitlab.gnome.org/GNOME/gnome-applets/issues/12 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1835332 Title: Add support for NVMe devices To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/1835332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1757280] Re: Night Light only works on one Monitor
I'm using 18.04.1, together with gnome flashback (3.28.0-1ubuntu1.3). For me, night mode only works with one screen, which is the primary screen. In my case, this is an external screen. With all 3 screens attached however, night mode however does not work with my two other monitors: - one internal screen of the laptop - another external screen -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1757280 Title: Night Light only works on one Monitor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1757280/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1588197] Re: Can't type anything in search box
For some PDFs I can type something in the search field. Seems to be related to the PDF (if it contains text or not). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1588197 Title: Can't type anything in search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1588197] Re: Can't type anything in search box
Right after upgrading from 16.04 to 18.04, I can't type in evince's search field any more. Proposed packages where never installed on that system. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1588197 Title: Can't type anything in search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1691289] Re: gnome desktop session segfaulted
unattended upgrades did an upgrade this morning: libgdm1 That could be the reason for this issue. Eventually, a restart of the display manager would have avoided this issue after the update. I'll track this issue for some time and see if it reappears after a reboot and in regular execution (without update behind the scenes). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1691289 Title: gnome desktop session segfaulted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1691289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1691289] Re: gnome desktop session segfaulted
Attached is an excerpt of my syslog which should contain the relevant period of time. ** Attachment added: "syslog_excerpt.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1691289/+attachment/4877834/+files/syslog_excerpt.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1691289 Title: gnome desktop session segfaulted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1691289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1691289] [NEW] gnome desktop session segfaulted
Public bug reported: My gnome desktop session just segfaulted or somehow crashed. Before the crash, the desktop session was running for hours, it even survived several s2ram's during the past days. I did not have these issues for a long time. My syslog shows up a lot of errors around the crash, not sure which one actually is responsible for the crash. Something I noticed is that my bluetooth headset got disconnected for no reason a few seconds before the crash. And a few seconds before the bluetooth headset got disconnected, a youtube live video (rather audio than video) ended expectedly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 17 00:21:29 2017 InstallationDate: Installed on 2014-11-29 (899 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-session UpgradeStatus: Upgraded to xenial on 2016-06-15 (335 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1691289 Title: gnome desktop session segfaulted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1691289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1688933] [NEW] systemd restart-loops logind
Public bug reported: Syslog logs systemd trying to restart logind every few seconds: May 7 00:51:29 server systemd[1]: Starting Login Service... May 7 00:51:54 server systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE May 7 00:51:54 server systemd[1]: Failed to start Login Service. May 7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered failed state. May 7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 'exit-code'. May 7 00:51:54 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. May 7 00:51:54 server systemd[1]: Stopped Login Service. May 7 00:51:54 server systemd[1]: Starting Login Service... May 7 00:52:19 server systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE May 7 00:52:19 server systemd[1]: Failed to start Login Service. May 7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered failed state. May 7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 'exit-code'. May 7 00:52:19 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. May 7 00:52:19 server systemd[1]: Stopped Login Service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun May 7 00:51:07 2017 InstallationDate: Installed on 2013-08-21 (1353 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) 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 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@ SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-10-24 (193 days ago) dmi.bios.date: 03/13/2014 dmi.bios.vendor: Intel Corp. dmi.bios.version: SWQ6710H.86A.0067.2014.0313.1347 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ67OW dmi.board.vendor: Intel Corporation dmi.board.version: AAG12528-309 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0067.2014.0313.1347:bd03/13/2014:svn:pn:pvr:rvnIntelCorporation:rnDQ67OW:rvrAAG12528-309:cvn:ct3:cvr: ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1688933 Title: systemd restart-loops logind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1688933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1569970] Re: Nautilus does not start
I'm using up-to-date ubuntu 16.04 I've seen this issue for the first time, after upgrading to 4.8 HWE kernel, including xorg-xserver hwe. Kernel is 4.8.0-36-generic Syslog says: Feb 18 05:03:35 lat61 gnome-session[2876]: (nautilus:3580): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Feb 18 05:03:35 lat61 gnome-session[2876]: (nautilus:3580): GLib-GObject-WARNING **: invalid (NULL) pointer instance Feb 18 05:03:35 lat61 gnome-session[2876]: (nautilus:3580): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1569970 Title: Nautilus does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1569970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1608125] Re: Error in `gnome-panel': munmap_chunk(): invalid pointer: 0x00000000027512cd
** Attachment added: "sys_log.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1608125/+attachment/4710579/+files/sys_log.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1608125 Title: Error in `gnome-panel': munmap_chunk(): invalid pointer: 0x027512cd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1608125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1608125] [NEW] Error in `gnome-panel': munmap_chunk(): invalid pointer: 0x00000000027512cd
Public bug reported: Gnome desktop crashes after resuming from suspend to ram. With the log files attached, the scenario was: - s2ram'ed laptop with closed lid attached to docking station (dual monitor setup) - Press power button on docking station (with lid still closed) -> Laptop resumes - Press undocking button on docking station (with lid still closed) -> Laptop suspends to RAM (which is in itself unexpected but not subject of this issue) - Open laptop's lid -> Laptop resumes - Result: Screen flackering, wrong screen resolution, screen partly visible without login. Then it seems as if the gnome desktop crashes after a few seconds. Then comes a clean login window while the old gnome session has gone, including all open applications (-> data loss). I'm not sure if the dual monitor plays a role or the docking station or if this is just a random fault when resuming from s2ram. Whatever it is, I have seen this multiple times now with 16.04. I did not have these issues with later versions of 14.04 with HES-kernel 4.2. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-session-bin 3.18.1.2-1ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sat Jul 30 23:03:59 2016 InstallationDate: Installed on 2014-11-29 (609 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-session UpgradeStatus: Upgraded to xenial on 2016-06-15 (45 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1608125 Title: Error in `gnome-panel': munmap_chunk(): invalid pointer: 0x027512cd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1608125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1603715] Re: bluetooth unavailable after rfkill hard blocking and unblocking
Same behaviour for soft blocking the device: rfkill block bluetooth rfkill list bluetooth 2: dell-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no rfkill unblock bluetooth rfkill list bluetooth 2: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 9: hci0: Bluetooth Soft blocked: no Hard blocked: no Result: Bluetooth not working and indicator-applet is gray. There's already a debian bug for soft unblocking: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812150 ** Bug watch added: Debian Bug tracker #812150 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812150 ** Also affects: systemd via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812150 Importance: Unknown Status: Unknown ** Summary changed: - bluetooth unavailable after rfkill hard blocking and unblocking + bluetooth unavailable after rfkill hard (or soft) unblocking -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1603715 Title: bluetooth unavailable after rfkill hard (or soft) unblocking To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1603715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1603715] [NEW] bluetooth unavailable after rfkill hard blocking and unblocking
Public bug reported:
DELL Latitude E5510 has a hardware switch to disable and enable
bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
terms of wifi, this works great: After hard unblocking, the device
resumes back to normal operation without any manual intervention. That
was also working with bluetooth as of ubuntu 14.04, kernel 4.2.
In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this is
not working any more:
After hard blocking and unblocking
- bluetooth is not working at all
- the applet-indicator remains gray
- bluetooth cannot be enabled with the applet-indicator (see
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
Applet-indicator remains gray
- rfkill list tells me that the kernel knows about the hard unblocking (turns
from "yes" to "no"):
rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
8: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
The device is a
sudo lsusb
Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Workaround: After a
sudo service bluetooth restart
the bluetooth device turns back to normal operation and the applet-
indicator turns from gray to black (available).
Suggested fix: Make the workaround obsolete.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Jul 17 04:00:58 2016
InstallationDate: Installed on 2014-11-29 (595 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Latitude E5510
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
** Description changed:
DELL Latitude E5510 has a hardware switch to disable and enable
- bluetooth and wifi devices ("hard blocking" in terms of rfkill. In terms
- of wifi, this works great: After hard unblocking the device resumes to
- normal operation with no manual intervention. That was also working with
- bluetooth as of 14.04, kernel 4.2.
+ bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
+ terms of wifi, this works great: After hard unblocking, the device
+ resumes back to normal operation without any manual intervention. That
+ was also working with bluetooth as of ubuntu 14.04, kernel 4.2.
In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this is
not working any more:
After hard blocking and unblocking
- bluetooth is not working at all
- the applet-indicator remains gray
- bluetooth cannot be enabled with the applet-indicator (see
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
Applet-indicator remains gray
- rfkill list tells me that the kernel knows about the hard unblocking (turns
from "yes" to "no"):
rfkill list bluetooth
2: dell-bluetooth: Bluetooth
- Soft blocked: no
- Hard blocked: no
+ Soft blocked: no
+ Hard blocked: no
8: hci0: Bluetooth
- Soft blocked: no
- Hard blocked: no
+ Soft blocked: no
+ Hard blocked: no
The device is a
sudo lsusb
Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Workaround: After a
sudo service bluetooth restart
the bluetooth device turns back to normal operation and the applet-
indicator turns from gray to black (available).
Suggested fix: Make the workaround obsolete.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Jul 17 04:00:58 2016
InstallationDate: Installed on 2014-11-29 (595 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
MachineType: Dell Inc. Latitude E5510
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016
[Bug 1426662] Re: gvfsd-trash crashed with SIGSEGV in g_slice_alloc()
*** This bug is a duplicate of bug 1216148 *** https://bugs.launchpad.net/bugs/1216148 Plus. I want to let you know that this error occured for the first time on my machine after doing the following updates: accountsservice 0.6.35-0ubuntu7.2 libaccountsservice0 0.6.35-0ubuntu7.2 libldap-2.4-2 2.4.31-1+nmu2ubuntu8.1 libspice-server1 0.12.4-0nocelt2ubuntu1 spice-client 0.12.4-0nocelt2ubuntu1 gir1.2-gudev-1.0 1:204-5ubuntu20.12 grub2-common 2.02~beta2-9ubuntu1.2 grub-common 2.02~beta2-9ubuntu1.2 grub-pc 2.02~beta2-9ubuntu1.2 grub-pc-bin 2.02~beta2-9ubuntu1.2 isc-dhcp-client 4.2.4-7ubuntu12.2 isc-dhcp-common 4.2.4-7ubuntu12.2 libgudev-1.0-0 1:204-5ubuntu20.12 libnautilus-extension1a 1:3.10.1-0ubuntu9.8 libpam-systemd 204-5ubuntu20.12 libreoffice-l10n-de 1:4.2.8-0ubuntu1 libsystemd-daemon0 204-5ubuntu20.12 libsystemd-journal0 204-5ubuntu20.12 libsystemd-login0 204-5ubuntu20.12 libudev1 204-5ubuntu20.12 libudev1:i386 204-5ubuntu20.12 nautilus 1:3.10.1-0ubuntu9.8 nautilus-data 1:3.10.1-0ubuntu9.8 systemd-services 204-5ubuntu20.12 udev 204-5ubuntu20.12 I guess one of them comes along with a regression, but I'm not sure about that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1426662 Title: gvfsd-trash crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1426662/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1426662] Re: gvfsd-trash crashed with SIGSEGV in g_slice_alloc()
*** This bug is a duplicate of bug 1216148 *** https://bugs.launchpad.net/bugs/1216148 As #1216148 is private, I want to confirm, that I get exactly the same error using uname -a Linux lat61 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux with up-to-date ubuntu 14.04. Apport reports "gvfsd-trash crashed with SIGSEGV in g_slice_alloc()" and "reading unknown VMA". Just to let you know that the current LTS release is affected, too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1426662 Title: gvfsd-trash crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1426662/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1425029] Re: Shutdown and restart dialog window's cancel function broken
*** This bug is a duplicate of bug 1363630 *** https://bugs.launchpad.net/bugs/1363630 I can reproduce this bug using gnome-flashback-compiz on ubuntu 14.04.2, kernel 3.16.0-31 (latest hwe) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1425029 Title: Shutdown and restart dialog window's cancel function broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1425029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069843] Re: Nautilus consuming memory and cpu
I guess a symlink in the home directories needs to be fixed by the distros, not by gnome upstream. Changes in the package would not necessarily fix the symlink in the home directories. Plus, the nautilus software can't delete the wrong ~/.cache/thumbnails directory, because this directory only has root permissions, which nautilus eventually does not have. Maybe there's a way to work around that, I don't know... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1069843 Title: Nautilus consuming memory and cpu To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1069843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069843] Re: Nautilus consuming memory and cpu
fedora might still be affected using gnome. I just can't test it. ** No longer affects: nautilus (Fedora) ** Bug watch added: GNOME Bug Tracker #690981 https://bugzilla.gnome.org/show_bug.cgi?id=690981 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=690981 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1069843 Title: Nautilus consuming memory and cpu To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1069843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069843] Re: Nautilus consuming memory and cpu
There's a bunch of bug reports out there, also affecting other distros: https://bugs.debian.org/731304 https://lists.debian.org/debian-user/2012/09/msg00124.html https://ask.fedoraproject.org/en/question/33842/why-is-nautilus-using-100-of-the-cpu-on-fedora-19/ As long as nautilus can't write thumbnails (disk full) it seems to consume cpu according to https://bugzilla.gnome.org/show_bug.cgi?id=655421. The missing symlink could also prevent nautilus from writing thumbnails. ** Bug watch added: Debian Bug tracker #731304 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731304 ** Bug watch added: GNOME Bug Tracker #655421 https://bugzilla.gnome.org/show_bug.cgi?id=655421 ** Also affects: nautilus (Fedora) via https://bugzilla.gnome.org/show_bug.cgi?id=655421 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1069843 Title: Nautilus consuming memory and cpu To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1069843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069843] Re: Nautilus consuming memory and cpu
The old directory entry was ls -la .cache/|grep thumbnails drwx-- 1 root root 18 Jul 15 01:40 thumbnails which came from 12.04 or before, I guess. I can't remember to have ever touched this directory manually. I guess this is the world's most energy consuming missing symlink ever. I expect the number of affected users to be MUCH higher than 129, because this bug was not reported automatically because of an application crash. Think of environmental pollution, think of energy costs (approx. 30USD per year just for me. Multiply with all users coming from older ubuntu versions), think of battery consumption, noise, heat, cooling, and slowness of affected systems. This bug MUST have a HIGH PRIORITY and can be fixed so easy. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1069843 Title: Nautilus consuming memory and cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1069843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069843] Re: Nautilus consuming memory and cpu
The sudo mv ~/.cache/thumbnails ~/.cache/thumbnails_ ln -s ~/.thumbnails ~/.cache/thumbnails did the trick for me as well. I have noticed that ~/.cache/thumbnails only had permissions for the root user. Plus, it just had a size of just 24kilobytes, which means it did not really contain thumbnails. Which is why nautilus did not display any on 14.04. In the end, I can work three times as long as before on battery and, as a bonus, I even can SEE the thumbnails. By simply fixing a symlink. I just can't understand why this bug, which is fixable THAT easy still is not fixed in the packages. Btw, I did not notice the cpu consumption of nautilus in 12.04.4, which means it seems to be a regression after updating to 14.04. And I updated just some days ago, so I guess the transition during the update to 14.04 still is buggy. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1069843 Title: Nautilus consuming memory and cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1069843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069843] Re: Nautilus consuming memory and cpu
Same here on a Dell Latitude E5510, which I updated to 14.04 these days. I have compiz enabled. For me, CPU consumption begins right after executing nautilus, while nautilus consumes approximately 25% to 40% of the cpu according to top. It seems as if as if all 4 threads of my dualcore cpu are in use by nautilus. Once consuming cpu, it does not stop anymore until I close nautilus. Definately, it is unusable that way on a laptop on battery. Capacity drops from 5-6 hours to 1-2 hours just because of nautilus. Please fix this annoying bug which seemed to be active for years now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1069843 Title: Nautilus consuming memory and cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1069843/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 620842] Re: laptop halts while it should go to sleep
I opened a new bug report #621834 for my problem which seems to be different. -- laptop halts while it should go to sleep https://bugs.launchpad.net/bugs/620842 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 620842] Re: laptop halts while it should go to sleep
I have a Dell Inspiron 6000 with Intel Centrino (Pentium-M), 32bit. ATI X300 graphics. I updated my system from karmic to lucid. Using jaunty, it was very very seldom that suspend to ram did not work. Same behaviour with lucid. System was updated frequently. Since I installed a kernel update from 2.6.32-23 to 2.6.32-24 in the last days, I can't suspend to ram or hibernate reproducably. The system halts before it sleeps or is switched off. I have to switch the system off and on again. After rebooting, all network connections are switched off and I have to reenable them using NetworkManager. Using 2.6.32-23, I also can't suspend to ram or hibernate any more. A few days ago, this worked fine in most cases. However sometimes I had the same behaviour as now (about one in 10 times it did not suspend). When I reboot my system using kernel 2.6.32-22, suspend to ram and hibernate work fine. Reproducably. -- laptop halts while it should go to sleep https://bugs.launchpad.net/bugs/620842 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
