[Desktop-packages] [Bug 1759008] [NEW] Revert automatic suspend by default for bionic?
Public bug reported: GNOME 3.28 has turned Automatic Suspend on by default and set it to 20 minutes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/2fdb48fa I generally think this is a good thing. There are a few issues though. 1. The computer will still suspend even if there are remote users logged in or the computer is being used as a server for files, printers, etc. 2. Some software doesn't set inhibit correctly. ~ahasenack mentioned he was using the Spotify Snap and the computer suspend after 20 minutes. (Maybe Spotify needs to use the screen-inhibit-control snap interface.) 3. Even if it does set inhibit, there is a report that the computer will suspend as soon as the inhibit is removed if there is no other activity. (Imagine a movie playing. At the end of the movie, the computer goes to sleep immediately.) More details and proposed fix at https://bugzilla.gnome.org/show_bug.cgi?id=705942#c21 4. There is no GUI way to change this setting for the login screen yet. https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22 5. Some users think that desktop computers should be always running unless told otherwise. Personally, I don't give this argument much weight at all. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: bionic rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1759008 Title: Revert automatic suspend by default for bionic? Status in ubuntu-settings package in Ubuntu: New Bug description: GNOME 3.28 has turned Automatic Suspend on by default and set it to 20 minutes: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/2fdb48fa I generally think this is a good thing. There are a few issues though. 1. The computer will still suspend even if there are remote users logged in or the computer is being used as a server for files, printers, etc. 2. Some software doesn't set inhibit correctly. ~ahasenack mentioned he was using the Spotify Snap and the computer suspend after 20 minutes. (Maybe Spotify needs to use the screen-inhibit-control snap interface.) 3. Even if it does set inhibit, there is a report that the computer will suspend as soon as the inhibit is removed if there is no other activity. (Imagine a movie playing. At the end of the movie, the computer goes to sleep immediately.) More details and proposed fix at https://bugzilla.gnome.org/show_bug.cgi?id=705942#c21 4. There is no GUI way to change this setting for the login screen yet. https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22 5. Some users think that desktop computers should be always running unless told otherwise. Personally, I don't give this argument much weight at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1759008/+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 1759009] [NEW] software bug
Public bug reported: I ran the installed x diagnosis software. The software found the bug. I have no idea what the problem is. My Ubuntu Apps application will not work. I tried removing and reinstall the application but it still will not work. I installed gnome-software as a work around but that doesn't seem to work either. I believe my Ubuntu 16.04 lts original installation is faulty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 Date: Mon Mar 26 12:02:22 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053e] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K2000M] [1028:153e] InstallationDate: Installed on 2018-03-23 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Precision M4700 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=6126fabd-0eaf-4345-ac41-42b5013ac682 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 082H3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/09/2017:svnDellInc.:pnPrecisionM4700:pvr01:rvnDellInc.:rn082H3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4700 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1759009 Title: software bug Status in xorg package in Ubuntu: New Bug description: I ran the installed x diagnosis software. The software found the bug. I have no idea what the problem is. My Ubuntu Apps application will not work. I tried removing and reinstall the application but it still will not work. I installed gnome-software as a work around but that doesn't seem to work either. I believe my Ubuntu 16.04 lts original installation is faulty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 Date: Mon Mar 26 12:02:22 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053e] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K2000M] [1028:153e] InstallationDate: Installed on 2018-03-23 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Precision M4700 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Desktop-packages] [Bug 1754125] Re: Rhythmbox stays running in the background after quit
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit Status in rhythmbox package in Ubuntu: New Bug description: If you do ps -alx you will see rhythmbox process still running. It causes opening rhythmbox to hang when trying to open again ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 7 13:21:51 2018 InstallationDate: Installed on 2018-03-07 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+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 1718139] Re: Update to version 1.2.1
It hasn't been updated since Xenial. ** Summary changed: - Update to version 1.2.1 + Merge 1.2.1-1 from Debian ** Description changed: + Please merge 1.2.1-1 from Debian. + The package should be updated to the current last stable version (1.2.1). - The current package version is 1.1.2 (the same as in xenial). + The current package version is 1.1.2 (the same as in Xenial). Version from 1.1.2 to 1.1.5 bring various bug fixes. Version 1.2 brings improvements described here: https://people.xiph.org/~jm/opus/opus-1.2/ + -- + + opus (1.2.1-1) unstable; urgency=medium + + * Fixes a bug in surround encoding causing very bad quality on loud signals + beyond a certain amplitude. + * Speech quality improvements especially in the 12-24 kbit/s range. + * Music quality improvements in the 32-48 kb/s range. + * More aggressive use of wider speech bandwidth, including fullband speech + starting at 14 kbit/s. + * Improved VBR encoding for hybrid mode. + * SILK CBR improvements. + * DTX support for CELT mode. + * Support for directly encoding packets up to 120 ms. + * Improves quality on files with powerful tones that cause MDCT leakage. + * Fixes for speech/music detection at the very beginning of files. + * Fixes an issue where the encoder can misdetect that the signal is SWB + instead of FB, lowpassing the signal. + + -- Ron LeeThu, 28 Sep 2017 01:48:45 +0930 + + opus (1.2~alpha2-1) unstable; urgency=medium + + * Run the tonality analysis at 24 kHz, which reduces complexity while giving + better frequency resolution for the tonality estimate. + * Speech quality improvements especially in the 12-20 kbit/s range. + * Improved VBR encoding for hybrid mode. + * More aggressive use of wider speech bandwidth, including fullband speech + starting at 14 kbit/s. + * Music quality improvements in the 32-48 kb/s range. + * Generic and SSE CELT optimizations. + * Support for directly encoding packets up to 120 ms. + * DTX support for CELT mode. + * SILK CBR improvements. + * Ensure that NLSF cannot be negative when computing a min distance between + them. This was reported and fixed in July, and assessed as having only a + relatively minor impact (garbage output, from the garbage input needed to + trigger it), or at very worst, an assertion failure or simple crash from + a slightly out of bounds read. In December it was assigned CVE-2017-0381 + by someone other than the upstream developers, with claims of it being a + 'Critical' issue on Android, but we're yet to see any analysis to back + that up. Closes: #851612 + + -- Ron Lee Fri, 20 Jan 2017 02:48:31 +1030 + + opus (1.1.3-1) unstable; urgency=medium + + * Remove the generation date from the docs to improve reproducible builds. + Closes: #825345 + * Fixes some corner cases with the soft clipper. + * Improve CBR and some other issues seen with using crazy low rates. + * More robustness fixes for reporting bad input. + * More optimisations, mostly for ARM. + * More precision fixes for edge cases. + * Fixes to comfort noise generation. + + -- Ron Lee Thu, 27 Oct 2016 23:58:06 +1030 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to opus in Ubuntu. https://bugs.launchpad.net/bugs/1718139 Title: Merge 1.2.1-1 from Debian Status in opus package in Ubuntu: Confirmed Status in opus package in Debian: Fix Released Bug description: Please merge 1.2.1-1 from Debian. The package should be updated to the current last stable version (1.2.1). The current package version is 1.1.2 (the same as in Xenial). Version from 1.1.2 to 1.1.5 bring various bug fixes. Version 1.2 brings improvements described here: https://people.xiph.org/~jm/opus/opus-1.2/ -- opus (1.2.1-1) unstable; urgency=medium * Fixes a bug in surround encoding causing very bad quality on loud signals beyond a certain amplitude. * Speech quality improvements especially in the 12-24 kbit/s range. * Music quality improvements in the 32-48 kb/s range. * More aggressive use of wider speech bandwidth, including fullband speech starting at 14 kbit/s. * Improved VBR encoding for hybrid mode. * SILK CBR improvements. * DTX support for CELT mode. * Support for directly encoding packets up to 120 ms. * Improves quality on files with powerful tones that cause MDCT leakage. * Fixes for speech/music detection at the very beginning of files. * Fixes an issue where the encoder can misdetect that the signal is SWB instead of FB, lowpassing the signal. -- Ron Lee Thu, 28 Sep 2017 01:48:45 +0930 opus (1.2~alpha2-1) unstable; urgency=medium * Run the tonality analysis at 24 kHz, which reduces
[Desktop-packages] [Bug 1759001] Re: gnome-shell crashed with SIGSEGV in cogl_object_unref()
*** This bug is a duplicate of bug 1754445 *** https://bugs.launchpad.net/bugs/1754445 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754445, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1759001/+attachment/5091456/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1759001/+attachment/5091458/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1759001/+attachment/5091461/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1759001/+attachment/5091462/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1759001/+attachment/5091463/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1759001/+attachment/5091464/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1759001/+attachment/5091465/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754445 gnome-shell crashed with SIGSEGV in cogl_object_unref() from iter_remove_or_steal() from g_hash_table_iter_remove() from st_texture_cache_evict_icons() from on_icon_theme_changed() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1759001 Title: gnome-shell crashed with SIGSEGV in cogl_object_unref() Status in gnome-shell package in Ubuntu: New Bug description: my name miss when i log in ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Mar 26 19:28:51 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f4d0e5ebe00 :mov (%rdi),%rax PC (0x7f4d0e5ebe00) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: cogl_object_unref () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in cogl_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759001/+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 1758990] Re: gnome-software crashed with signal 5
*** This bug is a duplicate of bug 1755064 *** https://bugs.launchpad.net/bugs/1755064 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1755064, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758990/+attachment/5091441/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758990/+attachment/5091443/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758990/+attachment/5091446/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758990/+attachment/5091447/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758990/+attachment/5091448/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758990/+attachment/5091449/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758990/+attachment/5091450/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1755064 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1758990 Title: gnome-software crashed with signal 5 Status in gnome-software package in Ubuntu: New Bug description: I am not sure what caused this ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 13:52:08 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-02-28 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180227) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 pk_client_resolve () at /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 () at /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so gs_plugin_refine () at /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so Title: gnome-software crashed with signal 5 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-software/+bug/1758990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10
@ramas This worked out very nice for me with Ubuntu 17.10. Thanks for your work! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1731459 Title: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10 Status in sane-backends package in Ubuntu: Confirmed Bug description: On Windows it works but on my Ubuntu 17.10 I see a black band on scanned image. The scanner is Canon CanoScan LIDE100. Libsane version is 1.0.27-1~experimental2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746884] Re: evolution-addressbook-factory-subprocess crashed with SIGSEGV in g_io_stream_get_input_stream()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evolution-data-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1746884 Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in g_io_stream_get_input_stream() Status in evolution-data-server package in Ubuntu: Confirmed Bug description: Addressbook is EWS-based ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.26.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Feb 1 22:10:18 2018 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess InstallationDate: Installed on 2018-01-24 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180123) ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx23890x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/23890/3 SegvAnalysis: Segfault happened at: 0x7f0aecac1650 : mov (%rdi),%rax PC (0x7f0aecac1650) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: g_io_stream_get_input_stream () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in g_io_stream_get_input_stream() 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/evolution-data-server/+bug/1746884/+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 1758994] [NEW] "There was an error playing video from the webcam"
Public bug reported: Chesee version: 3.28 Ubuntu version: 18.04 (26.03.18 updated) when i open cheese, cheese shows "There was an error playing video from the webcam" Crashlog: UNPC:~$ cheese (cheese:2): Gtk-WARNING **: 21:07:11.856: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version (cheese:2): cheese-WARNING **: 21:07:12.958: Device '/dev/video0' failed during initialization: gstv4l2object.c(3695): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for YUYV @ 1280x720: Input/output error ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1758994 Title: "There was an error playing video from the webcam" Status in cheese package in Ubuntu: New Bug description: Chesee version: 3.28 Ubuntu version: 18.04 (26.03.18 updated) when i open cheese, cheese shows "There was an error playing video from the webcam" Crashlog: UNPC:~$ cheese (cheese:2): Gtk-WARNING **: 21:07:11.856: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version (cheese:2): cheese-WARNING **: 21:07:12.958: Device '/dev/video0' failed during initialization: gstv4l2object.c(3695): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for YUYV @ 1280x720: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1758994/+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 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while
With Ubuntu switching to GNOME, looks like Unity folks don't care about this anymore. This and the fractional scaling issue were the only 2 issues that kept me from using anything higher than 16.10 until now, and I've decided to take the matter into my own hands. I've bisected the recent commit logs and found 2 possible faulty commits. Reverting those fixed the fractional scaling issue, and I'm pretty sure it fixes the reset bug. (The commit almost directly tells itself.) I'm still using 16.10 and tested those new Unity builds within a VM, so I can't test whether it fixes the reset bug myself. I'm preparing those PPAs to get ready for 18.04 LTS. (As I prefer Unity over GNOME.) https://launchpad.net/~arter97/+archive/ubuntu/unity I've added build for Xenial(16.04) as well. Please test it and let me know how it goes! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1689356 Title: UI scale being reset to 1 everytime when display sleeps for a while Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.04, the HiDPI setting(Scale for menu and title bars) is being reset to 1 everytime when display sleeps for a while, making everything looks small. If the display sleeps and I resume it instantly, it's fine, but if the display slept for long, the HiDPI setting gets reset to 1. My guess is that if a display is plugged in(detected), the old DPI setting is not restored. This issue is not present on previous Ubuntu versions and the same issue persists even after a fresh install. *-* This bug is now present also in 16.04 since a recent update, experiencing this in Xenial since 23 Feb 2018 at least. We could trace the cause of the bug in the recent backports/bugfix updates to Xenial. *-* ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 Uname: Linux 4.10.14-zen+ 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 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 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:Unity7 Date: Tue May 9 02:08:25 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa] Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] [1458:227b] InstallationDate: Installed on 2017-05-06 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on vfio_iommu_type1.allow_unsafe_interrupts=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz
[Desktop-packages] [Bug 1758979] Re: Enable scrolling for "Formats" and "Input Sources"
This is an upstream merge request to address this bug: https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/16 -- 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/1758979 Title: Enable scrolling for "Formats" and "Input Sources" Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: In Progress Bug description: The fix of bug #1727710, which deals with the presence of many installed languages, enables a scrollbar when needed for the first "Language" window in the region panel. To completely handle the presence of many installed languages, we need to enable scrolling for "Formats" and "Input Sources" too. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1758979/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
@Evgeniy Polyakov Live CD/USB almost always work perfectly, that is not a confirmation that the issue does not exist. It is not a Distro problem per say. If you installed Fedora, the second time you tried to use the audio device, it would fail/skip etc. I do not know why, but I have been fooled many times by a "working" live CD/USB only to find out that once installed, it does not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1727710] Re: Unable to access more than 20 languages in 1080p
Submitted bug #1758979. ** Changed in: gnome-control-center (Ubuntu Bionic) Status: In Progress => Fix Released -- 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/1727710 Title: Unable to access more than 20 languages in 1080p Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Released Bug description: There is no scroll bar on the language selection GUI, causing issues if you install more than 20 language selections. The ... button is on the bottom off the screen, meaning you can't access it. On resolutions smaller than 1080p, you could expect the same issues but with less language options. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1727710/+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 1758979] [NEW] Enable scrolling for "Formats" and "Input Sources"
Public bug reported: The fix of bug #1727710, which deals with the presence of many installed languages, enables a scrollbar when needed for the first "Language" window in the region panel. To completely handle the presence of many installed languages, we need to enable scrolling for "Formats" and "Input Sources" too. ** Affects: gnome-control-center Importance: Unknown Status: Unknown ** Affects: gnome-control-center (Ubuntu) Importance: Medium Assignee: Gunnar Hjalmarsson (gunnarhj) Status: In Progress ** Bug watch added: GNOME Bug Tracker #793861 https://bugzilla.gnome.org/show_bug.cgi?id=793861 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=793861 Importance: Unknown Status: Unknown -- 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/1758979 Title: Enable scrolling for "Formats" and "Input Sources" Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: In Progress Bug description: The fix of bug #1727710, which deals with the presence of many installed languages, enables a scrollbar when needed for the first "Language" window in the region panel. To completely handle the presence of many installed languages, we need to enable scrolling for "Formats" and "Input Sources" too. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1758979/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
@vanvugt I've compiled and installed the latest pulseaudio with and without ubuntu patches, and this does not help. Checked with fedora live cd and things work without any problems. Changing @audio group to have rt permissions as well as tuning pulseaudio in its config (setting nice, rtprio, large memory limits and so on) does not seem to change anything. Getting, that I currently have the pre-latest (5.48-0ubuntu3) bluez and pulseaudio, and problem persists, can it be related to something else? desktop is problem in this case is a little bit different, it does not skip terribly, but once per 2-5 seconds, while laptop mentioned yesterday is indeed in trouble. ubuntu-bug refuses to work if there is third-party software installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1758971] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758971/+attachment/5091378/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758971/+attachment/5091380/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758971/+attachment/5091383/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758971/+attachment/5091384/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758971/+attachment/5091385/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758971/+attachment/5091386/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758971/+attachment/5091387/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1758971 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: Nothing needs to be done to trigger this, as far as I'm aware. The error message pops up at every boot. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Mar 23 11:00:38 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-12-21 (460 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LocalLibraries: /usr/local/lib/libgpg-error.so.0.22.0 /usr/local/lib/libgcrypt.so.20.2.2 ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-01-28 (57 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758971/+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 1750846] Re: several g-s-d services are timing out when booting a live session
Mar 26 16:33:58 ubuntu gsd-xsettings[1729]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist ... Mar 26 16:34:00 ubuntu busctl[1419]: Sender=:1.13 Destination=org.freedesktop.DBus Path=/org/freedesktop/DBus Interface=org.freedesktop.DBus Member=RequestName Mar 26 16:34:00 ubuntu busctl[1419]: UniqueName=:1.13 Mar 26 16:34:00 ubuntu busctl[1419]: MESSAGE "su" { Mar 26 16:34:00 ubuntu busctl[1419]: STRING "org.gnome.Mutter.DisplayConfig"; Mar 26 16:34:00 ubuntu busctl[1419]: UINT32 1; Mar 26 16:34:00 ubuntu busctl[1419]: }; -- 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/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon source package in Bionic: Confirmed Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 1750846] Re: several g-s-d services are timing out when booting a live session
Tried to turn off rate limiting in systemd, here's my attempt, looks better from a first glance ** Attachment added: "busctl.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+attachment/5091376/+files/busctl.xz -- 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/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon source package in Bionic: Confirmed Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 1750846] Re: several g-s-d services are timing out when booting a live session
journalctl | grep -v busctl ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+attachment/5091377/+files/journal -- 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/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon source package in Bionic: Confirmed Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 1750846] Re: several g-s-d services are timing out when booting a live session
I'm sure there are many reports of the symptoms caused by this bug, but I'm going to track the work here. -- 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/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon source package in Bionic: Confirmed Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 1726643] Re: nautilus crashed with SIGABRT in g_assertion_message(), while/after moving large file (file->details->directory == directory)
Upstream bug link:- https://gitlab.gnome.org/GNOME/nautilus/issues/335 On 26/03/18 16:15, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. The issue you are reporting is an upstream one and it > would be nice if somebody having it could send the bug to the developers > of the software by following the instructions at > https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please > tell us the number of the upstream bug (or the link), so we can add a > bugwatch that will inform us about its status. Thanks in advance. > -- 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/1726643 Title: nautilus crashed with SIGABRT in g_assertion_message(), while/after moving large file (file->details->directory == directory) Status in nautilus package in Ubuntu: New Bug description: Moved 1.2GB .mp4 from Desktop to Home. Nautilus crashed (apparently after the move was complete) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 24 01:00:40 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-08-02 (82 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcCmdline: /usr/bin/nautilus file:///home/username ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 nautilus_directory_async_state_changed () ?? () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to artful on 2017-10-21 (2 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726643/+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 1750846] Re: several g-s-d services are timing out when booting a live session
Laney, see also LP: #1752083 then. -- 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/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon source package in Bionic: Confirmed Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 1756006] Re: FFe: Support suspend-to-hibernate
Actually, I guess an UIFe will anyway be required as for the gnome- settings-manager? I can't reach the Gnome gitlab today so I don't know for sure. If it does affect some user visible strings, please proceed as per my earlier comment and if the respective teams go +1 on it, we'll formally switch this bug to 'Triaged'. -- 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/1756006 Title: FFe: Support suspend-to-hibernate Status in gnome-settings-daemon package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1756006] Re: FFe: Support suspend-to-hibernate
I am generally fine with this feature, especially after Dimitri's input. So formally I approve of this FFe. But since this will also be changing user-visible strings in systemd, I *think* you will also need to have an UIFe, e.g. you will have to inform the doc and translation teams [1]. I'm not sure about this as I have no idea how systemd translations are driven as they do not seem to be handled through launchpad. It might be that both the documentation and translation teams do not provide any translation support for these packages per-se and no formal UIFe will be required. Anyway, FFe approved but please, just in case, reach out to the required teams to get a better understanding if any other exceptions need to be considered. [1] https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze_Exceptions -- 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/1756006 Title: FFe: Support suspend-to-hibernate Status in gnome-settings-daemon package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Still does not work in Lenovo Y700-17ISK (80Q0) :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752966] Re: Please Merge 3.4.2-2 from Debian (Fix use of mediakeys D-Bus API)
This bug was fixed in the package rhythmbox - 3.4.2-4ubuntu1 --- rhythmbox (3.4.2-4ubuntu1) bionic; urgency=medium * Merge with Debian (LP: #1752966). Remaining changes: + Split out zeitgeist plugin + debian/control.in: - Allow unity-control-center as alternate dependency - Suggest instead of recommend gst-plugins-ugly - Suggest rhythmbox-plugin-zeitgeist - Recommends rhythmbox-plugin-alternative-toolbar. It improves the user interface and makes it fit better with GNOME. + debian/rhythmbox-plugins.install, debian/control{,.in}: Drop context plugin - it's mostly broken and would need porting to webkit2 anyway. + debian/patches/02_use_escaped_podcast_uri.patch - Handle podcasts that have sound files with the same basename + debian/patches/03_magnatune_partner.patch: - Change magnatune partner ID to 'ubuntu'. + debian/patches/05_hide_on_quit.patch - Hide (not quit) if RB is playing when closed. + debian/patches/07_quicklists.patch - Add quicklists. + debian/patches/08_stop_quit.patch: - Add a "Stop & Quit"-option to the quickmenu (via .desktop) - Add new symbol to librhythmbox-core10.symbols + debian/patches/make-shuffle-repeat-proper-toggle-actions.patch, debian/patches/restore-traditional-menubar.patch: Add a traditional menubar back when we want it, and fix the shuffle/repeat actions so they work correctly there. + debian/patches/0002-grilo-container-max-tracks.patch: increase CONTAINER_MAX_TRACKS to 15000 + debian/patches/10_encoding_use_ubuntu_profiles.patch, debian/*.prs, debian/rhythmbox-data.install: - Add Ubuntu encoding presets and use them by default. + debian/source_rhythmbox.py: Add an apport hook. + Add breaks/replaces since we moved plugins from rhythmbox and rhythmbox- plugins-magnatune back to rhythmbox-plugins * Stop building rhythmbox-plugin-mozilla since it won't work in Firefox 53+ rhythmbox (3.4.2-4) unstable; urgency=medium * Cherry-pick fix-build-with-gstreamer114.patch: - Fix build with gstreamer 1.14 (Closes: #894103) * Drop obsolete debian/NEWS entry from 2009 rhythmbox (3.4.2-3) unstable; urgency=medium [ Simon McVittie ] * Update Vcs-* for migration from Alioth svn to salsa.debian.org git * debian/gbp.conf: Add * d/README.Debian, d/TODO: Remove svn Id markers. These are no longer useful for a package maintained in git. [ Jeremy Bicha ] * Bump debhelper compat to 11 rhythmbox (3.4.2-2) unstable; urgency=medium [ Simon McVittie ] * gir1.2-rb-3.0 Provides gir1.2-mpid-3.0, since it also contains MPID-3.0.typelib [ Laurent Bigonville ] * debian/patches/fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API * debian/control.in: Bump Standards-Version to 4.1.3 (no further changes) * debian/source_rhythmbox.py: Install apport hook (thanks to Ubuntu) -- Jeremy BichaMon, 26 Mar 2018 10:49:17 -0400 ** Changed in: rhythmbox (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1752966 Title: Please Merge 3.4.2-2 from Debian (Fix use of mediakeys D-Bus API) Status in rhythmbox package in Ubuntu: Fix Released Bug description: Please merge 3.4.2-2 from Debian. I cannot work on this merge myself. It has this cherry-pick (fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API) More info upstream: mmkeys: media-player-keys: Fix usage to match API documentation See https://bugzilla.gnome.org/show_bug.cgi?id=781326 https://bugzilla.gnome.org/show_bug.cgi?id=781664 --- rhythmbox (3.4.2-2) unstable; urgency=medium [ Simon McVittie ] * gir1.2-rb-3.0 Provides gir1.2-mpid-3.0, since it also contains MPID-3.0.typelib [ Laurent Bigonville ] * debian/patches/fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API * debian/control.in: Bump Standards-Version to 4.1.3 (no further changes) * debian/source_rhythmbox.py: Install apport hook (thanks to Ubuntu) -- Laurent Bigonville Thu, 08 Feb 2018 14:23:43 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1752966/+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 1740700] Re: rhythmbox keeps playing music after closing
Pause the music and then close. It will close. Ctrl+w also works. You forget not everyone using gnome-shell, so the dock is not available for everyone. Even default-shell doesn't use any dock. It is widely accepted behavior in Unity, Xubuntu and Budgie and even in KDE when using indicator-sound. It simply minimize to tray/dock hiding it's main window. There are other software which does that (gnome- calendar, gnome-software etc.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1740700 Title: rhythmbox keeps playing music after closing Status in rhythmbox package in Ubuntu: New Bug description: I am on 17.10 now but I also experienced the following behaviour all recent Ubuntu versions. What I expect to happen: After closing Rhythmbox by pressing "x" in the menu bar, the program should really close and music should stop playing. What actually happens: Rhythmbox keeps running in the background. To finally stop the music I have to press pause in the Gnome shell addon (17.10) or press the audio button in the top panel and pause the music there (17.04 and prior versions). I know that this a "feature" rather than a real bug. However, this behaviour very counterintuitive - all other programs (included in Ubuntu by default) close on "x". Plus it does not even have any benefit on usability- we have that neat dock to park programs that run in the background. Therefore I see no reason that Rhythmbox should in this regard behave different and I would call it a bug in user experience. I think it should be changed, at least in future Ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1740700/+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 1726919] Re: Ubuntu 17.10 desktops corrupted
Desktops for users 1002 and 1003 are corrupted with some sort of XFCE type of theme. Users admin (installer) and 1001 have the correct theme. This bug has never happened before in any release of Ubuntu. The adduser command was used to create 1001, 1002 and 1003. -- 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/1726919 Title: Ubuntu 17.10 desktops corrupted Status in nautilus package in Ubuntu: Incomplete Bug description: The following users were installed: admin from DVD install (login with X option) user id 1001 (login with default Ubuntu option) user id 1002 (login with default Ubuntu option) user id 1003 (login with default Ubuntu option) Desktops for admin and user 1001 are ok. Desktops for users 1002 and 1003 are corrupted. See attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 11:41:36 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus-desktop InstallationDate: Installed on 2017-10-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726919/+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 1758956] Re: Upstream translation not imported/synced
** Package changed: simple-scan (Ubuntu) => ubuntu-translations -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1758956 Title: Upstream translation not imported/synced Status in Ubuntu Translations: New Bug description: There has been a similar report recently, but I'm not sure if it was the exact same one. If I look at the POT template for simple-scan it looks like it is up to date with the upstream one: same strings count, same strings. The PO file though doesn't seem to have been imported, at least for the Italian language. The last changed date in Launchpad is set to 2016-03-15, but the upstream translation for the 3.28 cycle has been completed (and it was complete also for the 3.26 cycle). A few links to check things out: * The Launchpad Italian translation: https://translations.launchpad.net/ubuntu/bionic/+source/simple-scan/+pots/simple-scan/it/+translate * The upstream Italian translation: https://l10n.gnome.org/vertimus/simple-scan/master/po/it Upstream hasn't branched 3.28 yet, so I wonder if this is just a matter of waiting for a new release to be imported in Launchpad. On a side note: simple-scan doesn't seem to be the only package with this "problem" (template in sync with upstream, but not the actual translations). I could see at least evolution-data-server, and gnome- online-accounts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1758956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758918] Re: unable to read filedescriptor flags for
I don't know where your /etc/profile.d/vte.sh issue is coming from. vte2.91 instead ships /etc/profile.d/vte-2.91.sh I do see that budgie-desktop-common ships /etc/profile.d/vte.sh . Did you have that package installed? ** Changed in: vte2.91 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1758918 Title: unable to read filedescriptor flags for https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1758918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758918] Re: unable to read filedescriptor flags for
I'm setting to Incomplete because it's not clear how to reproduce this issue from a clean Ubuntu 18.04 install or from an upgrade from a previous Ubuntu release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1758918 Title: unable to read filedescriptor flags for https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1758918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758956] [NEW] Upstream translation not imported/synced
Public bug reported: There has been a similar report recently, but I'm not sure if it was the exact same one. If I look at the POT template for simple-scan it looks like it is up to date with the upstream one: same strings count, same strings. The PO file though doesn't seem to have been imported, at least for the Italian language. The last changed date in Launchpad is set to 2016-03-15, but the upstream translation for the 3.28 cycle has been completed (and it was complete also for the 3.26 cycle). A few links to check things out: * The Launchpad Italian translation: https://translations.launchpad.net/ubuntu/bionic/+source/simple-scan/+pots/simple-scan/it/+translate * The upstream Italian translation: https://l10n.gnome.org/vertimus/simple-scan/master/po/it Upstream hasn't branched 3.28 yet, so I wonder if this is just a matter of waiting for a new release to be imported in Launchpad. On a side note: simple-scan doesn't seem to be the only package with this "problem" (template in sync with upstream, but not the actual translations). I could see at least evolution-data-server, and gnome- online-accounts. ** Affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1758956 Title: Upstream translation not imported/synced Status in Ubuntu Translations: New Bug description: There has been a similar report recently, but I'm not sure if it was the exact same one. If I look at the POT template for simple-scan it looks like it is up to date with the upstream one: same strings count, same strings. The PO file though doesn't seem to have been imported, at least for the Italian language. The last changed date in Launchpad is set to 2016-03-15, but the upstream translation for the 3.28 cycle has been completed (and it was complete also for the 3.26 cycle). A few links to check things out: * The Launchpad Italian translation: https://translations.launchpad.net/ubuntu/bionic/+source/simple-scan/+pots/simple-scan/it/+translate * The upstream Italian translation: https://l10n.gnome.org/vertimus/simple-scan/master/po/it Upstream hasn't branched 3.28 yet, so I wonder if this is just a matter of waiting for a new release to be imported in Launchpad. On a side note: simple-scan doesn't seem to be the only package with this "problem" (template in sync with upstream, but not the actual translations). I could see at least evolution-data-server, and gnome- online-accounts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1758956/+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 1750846] Re: several g-s-d services are timing out when booting a live session
journal: Mar 26 14:58:58 ubuntu gsd-xsettings[1846]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist I can't find where that gets on the bus though, which is annoying because it eventually does get there -- 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/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon source package in Bionic: Confirmed Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 1756379] Re: Delay start of gnome-software service
ok, I thought this was about a live session too. It being about the installed system changes my assessment a bit. In particular, I think it should be discussed with upstream before we press ahead with changing anything about this bug in Ubuntu, whereas the live environment is more special so it's often more okay to do hacks there. So, please file a bug upstream or come to #gnome-software or post on the ML for a chat. -- 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/1756379 Title: Delay start of gnome-software service Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: Triaged Bug description: On a default Bionic Desktop installation, gnome-software starts early and slows down session startup. In the bootchart attached, it overlaps with gnome-shell startup which is also resource intensive. With gnome-software delayed gnome-shell starts 2 seconds faster. gnome-software service startup should be delayed if it cannot be stop completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 17:11:41 2018 InstallationDate: Installed on 2013-09-03 (1654 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+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 1749449] Re: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which i
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1749449 Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1 -mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 Status in mesa package in Ubuntu: Confirmed Bug description: Error occurred when running the software updater this morning. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 Date: Wed Feb 14 08:00:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-32-generic, x86_64: installed DuplicateSignature: package:libgl1-mesa-dri:17.2.8-0ubuntu0~16.04.1 Unpacking libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1) over (17.2.8-0ubuntu0~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] [1002:682b] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Pegatron Venus LE [Radeon HD 8830M] [1b0a:90f3] InstallationDate: Installed on 2014-09-06 (1256 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: HP 510-p127c ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=3dd39524-3a29-4831-9f5a-6decde86d996 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: mesa Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: CNV64609PD dmi.board.name: 822A dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV64609PD dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.14:bd10/07/2016:svnHP:pn510-p127c:pvr:rvnHP:rn822A:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p127c dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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: Sun Jan 28 01:00:43 2018 xserver.configfile: default xserver.errors: RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749449/+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 1726643] Re: nautilus crashed with SIGABRT in g_assertion_message(), while/after moving large file (file->details->directory == directory)
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. -- 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/1726643 Title: nautilus crashed with SIGABRT in g_assertion_message(), while/after moving large file (file->details->directory == directory) Status in nautilus package in Ubuntu: New Bug description: Moved 1.2GB .mp4 from Desktop to Home. Nautilus crashed (apparently after the move was complete) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Oct 24 01:00:40 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-08-02 (82 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcCmdline: /usr/bin/nautilus file:///home/username ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 nautilus_directory_async_state_changed () ?? () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to artful on 2017-10-21 (2 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726643/+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 1733569] Re: In file explorer Modified column has day of week only (no time)
** Changed in: nautilus Status: Unknown => Confirmed ** Changed in: nautilus Importance: Unknown => Medium -- 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/1733569 Title: In file explorer Modified column has day of week only (no time) Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: I opened the file explorer (Nautilus?) to check when a particular file was created. I was interested in time (this is what Windows would show). The Modified column shows only weekday name ("Thu") which makes it imprecise and kind of useless. I would expect to see at least hours and minutes ("Thu 07:44") When I replaced Modified column with Modified--Time (which shows "Thu 07:44"...), the change is not kept permanently. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1733569/+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 1750846] Re: several g-s-d services are timing out when booting a live session
I injected a dbus.service.wants/ unit to run busctl --user monitor, here is its output for the record. Not analysed yet, hoping it's going to contain something interesting when read in conjunction with... ** Attachment added: "bus" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+attachment/5091337/+files/bus -- 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/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon source package in Bionic: Confirmed Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 1758942] [NEW] écran noir au démarrage
Public bug reported: écran noir, impossible de rentrer mon mot de passe au démarrage, lecteur video ne fonctionne pas, impossible de supprimer des logiciels, plantage en cours de session ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 Date: Mon Mar 26 16:53:16 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:078c] InstallationDate: Installed on 2018-03-15 (11 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=fbcd4cac-8cb9-4527-af8f-a07d69322204 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.3 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Mar 26 16:32:28 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5574 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1758942 Title: écran noir au démarrage Status in xorg package in Ubuntu: New Bug description: écran noir, impossible de rentrer mon mot de passe au démarrage, lecteur video ne fonctionne pas, impossible de supprimer des logiciels, plantage en cours de session ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 Date: Mon Mar 26 16:53:16 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:078c] InstallationDate: Installed on 2018-03-15 (11 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Desktop-packages] [Bug 1750846] Re: several g-s-d services are timing out when booting a live session
journal from the same boot ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+attachment/5091338/+files/journal -- 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/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-settings-daemon source package in Bionic: Confirmed Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+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 966129] Re: Xscreensaver daemon crash returned to unlocked desktop
I can confirm this still exists. It's also definitely a security vulnerability. I just came back from the weekend and found my work machine completely unlocked, open, and accessible. Like many users in my place, this is completely unacceptable and dangerous. I have no choice but to stop using xscreensaver now. I'm running xscreensaver 5.34, and Ubuntu 16.04.4 LTS (Xenial Xerus) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/966129 Title: Xscreensaver daemon crash returned to unlocked desktop Status in xscreensaver package in Ubuntu: Confirmed Bug description: Ubuntu 11.10, xscreensaver 5.14-1ubuntu1. I use xscreensaver as my main screensaver and I've replaced the gnome- screensaver using the command suggested in the xscreensaver man page (sudo ln -sf /usr/bin/xscreensaver-command /usr/bin/gnome-screensaver- command). Recently it's been crashing more than usual, either partial (one screen hangs, the other works ok), or fully (can't lock screen or activate screensaver without restarting daemon). This does seem to happen more frequently when I've left my VirtualBox VM running, but I'm not sure it's related. At least twice now the crash has caused the OS to return to my desktop - unlocked - which seems like a pretty serious security concern, especially as it won't automatically relock either until I've manually restarted the xscreensaver daemon. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xscreensaver 5.14-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Mar 27 11:52:54 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/966129/+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 1758933] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758933/+attachment/5091262/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758933/+attachment/5091264/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758933/+attachment/5091268/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758933/+attachment/5091269/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758933/+attachment/5091270/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758933/+attachment/5091271/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758933/+attachment/5091272/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1758933 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Auto detect ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 Uname: Linux 4.16.0-041600rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Mar 26 21:24:54 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-06 (20 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758933/+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 1752966] Re: Please Merge 3.4.2-2 from Debian (Fix use of mediakeys D-Bus API)
** Changed in: rhythmbox (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1752966 Title: Please Merge 3.4.2-2 from Debian (Fix use of mediakeys D-Bus API) Status in rhythmbox package in Ubuntu: Fix Committed Bug description: Please merge 3.4.2-2 from Debian. I cannot work on this merge myself. It has this cherry-pick (fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API) More info upstream: mmkeys: media-player-keys: Fix usage to match API documentation See https://bugzilla.gnome.org/show_bug.cgi?id=781326 https://bugzilla.gnome.org/show_bug.cgi?id=781664 --- rhythmbox (3.4.2-2) unstable; urgency=medium [ Simon McVittie ] * gir1.2-rb-3.0 Provides gir1.2-mpid-3.0, since it also contains MPID-3.0.typelib [ Laurent Bigonville ] * debian/patches/fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API * debian/control.in: Bump Standards-Version to 4.1.3 (no further changes) * debian/source_rhythmbox.py: Install apport hook (thanks to Ubuntu) -- Laurent BigonvilleThu, 08 Feb 2018 14:23:43 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1752966/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: Fix Released Status in mythbuntu-control-centre package in Ubuntu: Fix Released Status in sessioninstaller package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-mate-welcome package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port- from-aptdaemon-to-packagekit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1758935] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758935/+attachment/5091279/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758935/+attachment/5091281/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758935/+attachment/5091285/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758935/+attachment/5091286/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758935/+attachment/5091287/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758935/+attachment/5091288/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758935/+attachment/5091289/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1758935 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Automatic report ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 Uname: Linux 4.16.0-041600rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Mar 26 21:24:54 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-06 (20 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758935/+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 1726625] Re: nautilus bookmarks become unclickable and hidden
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726625 Title: nautilus bookmarks become unclickable and hidden Status in nautilus package in Ubuntu: New Bug description: EXPECTED Clicking Nautilus bookmarks is expected to always open the bookmarked place. INSTEAD === * The last clicked user added bookmark disappears. * Cannot click on any sidebar item (including all bookmarks and mounted places). REPRODUCING === 1) Click a fixed bookmark (Documents, Videos, Pictures...) 2) Click a user added bookmark (not a mounted one, for example a bookmark of a local folder) 3) If you still able to click, go to step 1 Note: You may have to repeat it only once or a dozen times. PATCH (?) = Nautilus have to regenerate its sidebar to recover. It can be achieved either by unmounting something or by editing 'bookmarks' config file... etc. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 23:27:40 2017 InstallationDate: Installed on 2017-08-08 (76 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2017-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726625/+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 1716159] Re: gdm greeter does not allow non-US characters (like euro character €) when typing password
@Daniel: If that workaround makes a difference, it sounds like the cause of the problem is that LANG was set to a non-UTF-8 value (such as C or POSIX). So it would be an encoding issue. Can you confirm that? -- 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/1716159 Title: gdm greeter does not allow non-US characters (like euro character €) when typing password Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: In latest Artful (2017-09-08 daily), gdm does not allow to enter the euro character (€) when typing the password (be it with the real keyboard or with the visual on screen keyboard). Steps to reproduce: 1. on the gdm login screen, try to type € in the password field 2. the input is ignored (not big dot is added) 3. if your password contains a € symbol (which is allowed, incliding during installation with ubiquity), you cannot login anymore... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716159/+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 1729264] Re: Regression of file rename popover bug
The issue has been fixed in nautilus 3.26 which is in bionic ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- 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/1729264 Title: Regression of file rename popover bug Status in nautilus package in Ubuntu: Fix Released Bug description: It seems ctrl+z undo tries to undo the last file operation rather than the last text edit in the file name dialog. nautilus devs have fixed this behaviour previously, so it's probably an Ubuntu patch that's causing the problem. Here's the patch that was committed to fix it previously: https://gitlab.gnome.org/GNOME/nautilus/commit/bf6b1e2c2f0cd3d882f99029af79a3439bdacec1 Here's a video showing that the behaviour regression in 17.10 (ctrl+z is used to undo a text edit): https://www.dropbox.com/s/pvywye6alea76j4/nautilus_undo_history_bug.movie.mp4?dl=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729264/+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 1726919] Re: Ubuntu 17.10 desktops corrupted
Thank you for your bug report. What sort of corruption are you talking about? I don't see anything wrong in the user_1002.png image ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1726919 Title: Ubuntu 17.10 desktops corrupted Status in nautilus package in Ubuntu: Incomplete Bug description: The following users were installed: admin from DVD install (login with X option) user id 1001 (login with default Ubuntu option) user id 1002 (login with default Ubuntu option) user id 1003 (login with default Ubuntu option) Desktops for admin and user 1001 are ok. Desktops for users 1002 and 1003 are corrupted. See attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 11:41:36 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus-desktop InstallationDate: Installed on 2017-10-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726919/+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 1756379] Re: Delay start of gnome-software service
We still do. That's 2 different things: - This bug is to improve the session startup time of an installed system - Bug 1758920 is to lighten the load on the live session. I don't think we want to disable the service on an installed system. ** Changed in: gnome-software (Ubuntu Bionic) Status: Won't Fix => Triaged -- 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/1756379 Title: Delay start of gnome-software service Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: Triaged Bug description: On a default Bionic Desktop installation, gnome-software starts early and slows down session startup. In the bootchart attached, it overlaps with gnome-shell startup which is also resource intensive. With gnome-software delayed gnome-shell starts 2 seconds faster. gnome-software service startup should be delayed if it cannot be stop completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 17:11:41 2018 InstallationDate: Installed on 2013-09-03 (1654 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+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 1729887] Re: Drag-and-drop to desktop not possible without copying the file under wayland
** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged -- 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/1729887 Title: Drag-and-drop to desktop not possible without copying the file under wayland Status in Nautilus: Expired Status in nautilus package in Ubuntu: Triaged Bug description: since my upgrade to Ubuntu Desktop 17.10 all files moved with drag- and-drop from any folder to my desktop are copied but not moved. Using strg+x and strg+v works. When i open the desktop as a folder usual drag-and-drop from different folders do work without copying the files. This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like before and allows normal drag-and-drop from folders to the desktop. (I reported the issue before at https://askubuntu.com/questions/972533/) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1729887/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Confirm for Ubuntu 17.10, and 18.04 beta -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in GNOME Settings Daemon: Unknown Status in Ubuntu Flashback: New Status in Ubuntu GNOME: Fix Released Status in Ubuntu GNOME Flashback: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-control-center package in ALT Linux: Unknown Status in gnome-control-center package in Baltix: Confirmed Status in gnome-control-center package in Gentoo Linux: Unknown Status in gnome-control-center package in Mandriva: Unknown Bug description: [Impact] Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift, etc. Shift, Caps Lock keys are just ignored in settings. [Test Case] - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a combination of two modifier keys such as Ctrl+Shift -> the UI should reflect the new keys - add at least two input sources through gnome-control-center's text entry settings - press and release Ctrl+Shift -> the current input source should change [Regression Potential] That UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE=sharing). You can use the tag keyboard-layout-switching-hotkeys to find related bugs. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys For using layout switching hotkeys in Unity Greeter, see bug 1245137. For using layout switching hotkeys in GNOME lockscreen, see bug 1244548. For using layout switching hotkeys in GNOME FlashBack sessions, see bug 1687466 (at least). -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Hi all, I also just migrated 1 or 2 months ago to 17.10 (because of EOL) and it's horrible. I'm using Ubuntu mainly for work, so this change impacts my workflow quite heavily. Of course privately too. If you don't change the default behaviour, then you will face freezes. Most of my folders contain 100 and more subfolders and in some of them there are thousands of files. Many projects like those of Android Studio etc. contain ten-thousands of files. Just press a key by accident and nautilus freezes for 10 minutes and longer. To prevent that one has to switch of recursive search and full text search. By the heavens! This can't be the default behaviour!!! With the old behaviour, you can jump to where ever you need to. If all folders have a unique first letter, then navigation is done with one key press. Now, you still need to navigate through the results. Come on guys, "efficiency" is something different! This works even in Windows, why not in Nautilus? Btw.: I just tested the live CD of 18.04. The issue is not fixed. Just having the option to choose the behaviour would be fine. No need to abandon one for the other. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service
right, then we don't need to do this ** Changed in: gnome-software (Ubuntu Bionic) Status: New => Won't Fix -- 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/1756379 Title: Delay start of gnome-software service Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: Won't Fix Bug description: On a default Bionic Desktop installation, gnome-software starts early and slows down session startup. In the bootchart attached, it overlaps with gnome-shell startup which is also resource intensive. With gnome-software delayed gnome-shell starts 2 seconds faster. gnome-software service startup should be delayed if it cannot be stop completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 17:11:41 2018 InstallationDate: Installed on 2013-09-03 (1654 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+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 1758927] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758927/+attachment/5091241/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758927/+attachment/5091243/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758927/+attachment/5091246/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758927/+attachment/5091247/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758927/+attachment/5091248/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758927/+attachment/5091249/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758927/+attachment/5091250/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1758927 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: See attached information. None of the above bugs references "default_handle." Thank you. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 25 21:45:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-17 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758927/+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 1729918] Re: NFS support not enabled
*** This bug is a duplicate of bug 1637988 *** https://bugs.launchpad.net/bugs/1637988 ** This bug has been marked a duplicate of bug 1637988 gvfsd-nfs not present in gvfs-backends, why? -- 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/1729918 Title: NFS support not enabled Status in nautilus package in Ubuntu: New Bug description: nautilus is not compiled with libnfs support so uri's like nfs://my-ip :/my-export do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729918/+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 1731773] Re: Nautilus crashes when expanding folder after search
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1731773 Title: Nautilus crashes when expanding folder after search Status in nautilus package in Ubuntu: Incomplete Bug description: This bug happens in Ubuntu 17.10 with Files (Nautilus) version 3.26.0. It did not happen in 17.04. - Make sure that in settings the setting "Allow folders to be expanded" is switched on. - Search for files and folders and make sure the result list contains folders. - Expand a folder with the arrow in front of the folder. - The application crashes. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 12 17:50:04 2017 InstallationDate: Installed on 2016-10-30 (377 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: nautilus UpgradeStatus: Upgraded to artful on 2017-10-22 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731773/+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 1758517] Re: bamfdaemon.service: Failed with result 'core-dump'
I have the exact same core dumps from bamf. Running Arch linux. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1758517 Title: bamfdaemon.service: Failed with result 'core-dump' Status in bamf package in Ubuntu: Confirmed Bug description: bamfdaemon core dumps on my system frequently (up-to-date Manjaro Linux). The journal shows 63 core dumps since 8. February. They all look similar: Mär 23 23:11:02 rakete systemd[3008]: bamfdaemon.service: Failed with result 'core-dump'. Mär 23 23:11:02 rakete systemd-coredump[20314]: Process 29805 (bamfdaemon) of user 1000 dumped core. Stack trace of thread 29805: #0 0x5616c8bdb201 n/a (bamfdaemon) #1 0x7f1539895783 n/a (libglib-2.0.so.0) #2 0x7f1539894ca6 g_main_context_dispatch (libgli> #3 0x7f1539895081 n/a (libglib-2.0.so.0) #4 0x7f15398953b2 g_main_loop_run (libglib-2.0.so> #5 0x5616c8bd4d83 main (bamfdaemon) #6 0x7f1539295f4a __libc_start_main (libc.so.6) #7 0x5616c8bd4e2a _start (bamfdaemon) Stack trace of thread 29807: #0 0x7f153963db04 sendmsg (libpthread.so.0) #1 0x7f153a04dbcb n/a (libgio-2.0.so.0) #2 0x7f153a04e477 g_socket_send_message (libgio-2> #3 0x7f153a0a38f0 n/a (libgio-2.0.so.0) #4 0x7f153a0a3eed n/a (libgio-2.0.so.0) #5 0x7f153a0a4468 n/a (libgio-2.0.so.0) #6 0x7f153a05c24c n/a (libgio-2.0.so.0) #7 0x7f153a05c289 n/a (libgio-2.0.so.0) #8 0x7f1539894ca6 g_main_context_dispatch (libgli> #9 0x7f1539895081 n/a (libglib-2.0.so.0) #10 0x7f15398953b2 g_main_loop_run (libglib-2.0.so> #11 0x7f153a0a26d8 n/a (libgio-2.0.so.0) #12 0x7f15398bd26a n/a (libglib-2.0.so.0) #13 0x7f153963308c start_thread (libpthread.so.0) #14 0x7f153936ae7f __clone (libc.so.6) Stack trace of thread 29806: #0 0x7f153936097b __poll (libc.so.6) /usr/lib/systemd/user/bamfdaemon.service looks like this: [Unit] Description=BAMF Application Matcher Framework PartOf=graphical-session.target [Service] Type=dbus BusName=org.ayatana.bamf ExecStart=/usr/lib/bamf/bamfdaemon Restart=on-failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1758517/+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 1734891] Re: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file()
The upstream comments suggests it might be due to the dropbox plugin -- 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/1734891 Title: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() Status in nautilus package in Ubuntu: Triaged Bug description: Hello, I'm working with nautilus and crash. Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.0-0ubuntu1 Uname: Linux 4.15.0-041500rc1-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 11:17:57 2017 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'253' b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+255+180'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.desktop' b'home-icon-visible' b'true' InstallationDate: Installed on 2017-10-13 (45 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x5592953dfc28:mov0x10(%rbx),%rsi PC (0x5592953dfc28) ok source "0x10(%rbx)" (0xffc0) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_list_model_get_all_iters_for_file () nautilus_list_model_get_first_iter_for_file () ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1734891/+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 1758517] Re: bamfdaemon.service: Failed with result 'core-dump'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bamf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1758517 Title: bamfdaemon.service: Failed with result 'core-dump' Status in bamf package in Ubuntu: Confirmed Bug description: bamfdaemon core dumps on my system frequently (up-to-date Manjaro Linux). The journal shows 63 core dumps since 8. February. They all look similar: Mär 23 23:11:02 rakete systemd[3008]: bamfdaemon.service: Failed with result 'core-dump'. Mär 23 23:11:02 rakete systemd-coredump[20314]: Process 29805 (bamfdaemon) of user 1000 dumped core. Stack trace of thread 29805: #0 0x5616c8bdb201 n/a (bamfdaemon) #1 0x7f1539895783 n/a (libglib-2.0.so.0) #2 0x7f1539894ca6 g_main_context_dispatch (libgli> #3 0x7f1539895081 n/a (libglib-2.0.so.0) #4 0x7f15398953b2 g_main_loop_run (libglib-2.0.so> #5 0x5616c8bd4d83 main (bamfdaemon) #6 0x7f1539295f4a __libc_start_main (libc.so.6) #7 0x5616c8bd4e2a _start (bamfdaemon) Stack trace of thread 29807: #0 0x7f153963db04 sendmsg (libpthread.so.0) #1 0x7f153a04dbcb n/a (libgio-2.0.so.0) #2 0x7f153a04e477 g_socket_send_message (libgio-2> #3 0x7f153a0a38f0 n/a (libgio-2.0.so.0) #4 0x7f153a0a3eed n/a (libgio-2.0.so.0) #5 0x7f153a0a4468 n/a (libgio-2.0.so.0) #6 0x7f153a05c24c n/a (libgio-2.0.so.0) #7 0x7f153a05c289 n/a (libgio-2.0.so.0) #8 0x7f1539894ca6 g_main_context_dispatch (libgli> #9 0x7f1539895081 n/a (libglib-2.0.so.0) #10 0x7f15398953b2 g_main_loop_run (libglib-2.0.so> #11 0x7f153a0a26d8 n/a (libgio-2.0.so.0) #12 0x7f15398bd26a n/a (libglib-2.0.so.0) #13 0x7f153963308c start_thread (libpthread.so.0) #14 0x7f153936ae7f __clone (libc.so.6) Stack trace of thread 29806: #0 0x7f153936097b __poll (libc.so.6) /usr/lib/systemd/user/bamfdaemon.service looks like this: [Unit] Description=BAMF Application Matcher Framework PartOf=graphical-session.target [Service] Type=dbus BusName=org.ayatana.bamf ExecStart=/usr/lib/bamf/bamfdaemon Restart=on-failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1758517/+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 1752966] Re: Please Merge 3.4.2-2 from Debian (Fix use of mediakeys D-Bus API)
Rhythmbox now fails to build from source. I went ahead and pushed the merge to the ubuntu-desktop bzr packaging branch though. ** Changed in: rhythmbox (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1752966 Title: Please Merge 3.4.2-2 from Debian (Fix use of mediakeys D-Bus API) Status in rhythmbox package in Ubuntu: Triaged Bug description: Please merge 3.4.2-2 from Debian. I cannot work on this merge myself. It has this cherry-pick (fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API) More info upstream: mmkeys: media-player-keys: Fix usage to match API documentation See https://bugzilla.gnome.org/show_bug.cgi?id=781326 https://bugzilla.gnome.org/show_bug.cgi?id=781664 --- rhythmbox (3.4.2-2) unstable; urgency=medium [ Simon McVittie ] * gir1.2-rb-3.0 Provides gir1.2-mpid-3.0, since it also contains MPID-3.0.typelib [ Laurent Bigonville ] * debian/patches/fix_mediakeys_api.patch: Fix use of mediakeys D-Bus API * debian/control.in: Bump Standards-Version to 4.1.3 (no further changes) * debian/source_rhythmbox.py: Install apport hook (thanks to Ubuntu) -- Laurent BigonvilleThu, 08 Feb 2018 14:23:43 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1752966/+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 1758926] [NEW] keyboard mute, volume key, CTRL + ATL T ( terminal) not working anymore since last updates
Public bug reported: Description:Ubuntu 17.10 Release:17.10 Using Ubunutu budgie 17.10 GNOME 3.26.2 one of the last updates ( Ubuntu) broke some keyboard keys functionalities Sound keys : Volume Up, Down, Mute Calculator Key CTRL + ATL T To launch terminal not working anymore JF ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Mar 26 10:01:47 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-11 (42 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20180106) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1758926 Title: keyboard mute, volume key, CTRL + ATL T ( terminal) not working anymore since last updates Status in gnome-settings-daemon package in Ubuntu: New Bug description: Description: Ubuntu 17.10 Release: 17.10 Using Ubunutu budgie 17.10 GNOME 3.26.2 one of the last updates ( Ubuntu) broke some keyboard keys functionalities Sound keys : Volume Up, Down, Mute Calculator Key CTRL + ATL T To launch terminal not working anymore JF ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Mar 26 10:01:47 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-11 (42 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20180106) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758926/+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 1758924] [NEW] gnome-keyring no longer including ssh key comment 3.27.4-2 to 3.28.0.1-1
Public bug reported: Updated today, it moved from 2018-03-26 08:11:25 upgrade gnome-keyring:amd64 3.27.4-2ubuntu1 3.28.0.1-1ubuntu1 to 2018-03-26 08:14:34 status installed gnome-keyring:amd64 3.28.0.1-1ubuntu1 After this, noticed that some local code that uses ssh key comments (from 'ssh-add -l' output) for automatic annotations is no longer working right. Previously (example from 16.04): nneul@skyhawk:~ $ ssh-add -l 2048 SHA256:.. nn...@neulinger.org (RSA) Now (from current 18): nneul@infinity:~ $ ssh-add -l 2048 SHA256:.. /users/nneul/.ssh/id_rsa (RSA) This is a negative change from my perspective as we are making use of that comment for automatic annotations (not security sensitive) and things like automatically populating git identity when managing a shared application development/server accounts. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-keyring 3.28.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 26 08:51:30 2018 InstallationDate: Installed on 2015-11-09 (867 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to bionic on 2017-12-05 (110 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1758924 Title: gnome-keyring no longer including ssh key comment 3.27.4-2 to 3.28.0.1-1 Status in gnome-keyring package in Ubuntu: New Bug description: Updated today, it moved from 2018-03-26 08:11:25 upgrade gnome-keyring:amd64 3.27.4-2ubuntu1 3.28.0.1-1ubuntu1 to 2018-03-26 08:14:34 status installed gnome-keyring:amd64 3.28.0.1-1ubuntu1 After this, noticed that some local code that uses ssh key comments (from 'ssh-add -l' output) for automatic annotations is no longer working right. Previously (example from 16.04): nneul@skyhawk:~ $ ssh-add -l 2048 SHA256:.. nn...@neulinger.org (RSA) Now (from current 18): nneul@infinity:~ $ ssh-add -l 2048 SHA256:.. /users/nneul/.ssh/id_rsa (RSA) This is a negative change from my perspective as we are making use of that comment for automatic annotations (not security sensitive) and things like automatically populating git identity when managing a shared application development/server accounts. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-keyring 3.28.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 26 08:51:30 2018 InstallationDate: Installed on 2015-11-09 (867 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to bionic on 2017-12-05 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1758924/+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 1734387] Re: lost files during moving files to usb
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => High -- 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/1734387 Title: lost files during moving files to usb Status in nautilus package in Ubuntu: New Bug description: I moved three small files to a USB dongle after clicking the nautilus copy animation displayed that it was finished. I then proceeded to pull out the USB dongle after which my files were gone both on USB dongle and where I moved them from. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 24 22:01:28 2017 InstallationDate: Installed on 2017-10-20 (35 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1734387/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Confirmed Status in d-conf package in Ubuntu: Triaged Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Triaged Status in session-migration package in Ubuntu: Fix Released Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1758915] Re: gnome-software crashed with SIGSEGV in g_main_loop_is_running()
*** This bug is a duplicate of bug 1716508 *** https://bugs.launchpad.net/bugs/1716508 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1716508, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758915/+attachment/5091185/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758915/+attachment/5091187/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758915/+attachment/5091191/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758915/+attachment/5091192/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758915/+attachment/5091193/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758915/+attachment/5091194/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758915/+attachment/5091195/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1716508 gnome-software crashed with SIGSEGV in g_main_loop_is_running() ** Tags removed: need-amd64-retrace -- 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/1758915 Title: gnome-software crashed with SIGSEGV in g_main_loop_is_running() Status in gnome-software package in Ubuntu: New Bug description: ubuntu 18.04 . Again software not working (timeout error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 Uname: Linux 4.15.12-041512-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Mar 26 19:13:11 2018 ExecutablePath: /usr/bin/gnome-software InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu7 gnome-software-plugin-limba 3.28.0-0ubuntu7 gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service SegvAnalysis: Segfault happened at: 0x7f41d1c488e9: mov 0xc(%rdi),%eax PC (0x7f41d1c488e9) ok source "0xc(%rdi)" (0x0002010b) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: g_main_loop_is_running () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/liblimba.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with SIGSEGV in g_main_loop_is_running() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1758915/+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 1756559] Re: No status indicator for File Copy and/or Moves
I don't have my computer on me right now, but it was obvious to me that this is a bug. The little circle indicating a move was not there. On Mon, Mar 26, 2018, 8:20 AM Sebastien Bacherwrote: > Thank you for your bug report. Could you take a screenshot of your > nautilus window after starting the copy? There should be a circle icon > in the toolbar you can click on which displays the copy status/details. > > ** Changed in: nautilus (Ubuntu) >Importance: Undecided => Low > > ** Changed in: nautilus (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1756559 > > Title: > No status indicator for File Copy and/or Moves > > Status in nautilus package in Ubuntu: > Incomplete > > Bug description: > Nautilus does not show a status indicator when the user is copying or > moving a file from an NAS device to their local disk. > This is very important to have, as the user risks data loss or > corruption if not done correctly. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: nautilus 1:3.26.0-0ubuntu1 > ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13 > Uname: Linux 4.13.0-37-lowlatency x86_64 > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sat Mar 17 11:10:31 2018 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: nautilus > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1756559/+subscriptions > -- 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/1756559 Title: No status indicator for File Copy and/or Moves Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus does not show a status indicator when the user is copying or moving a file from an NAS device to their local disk. This is very important to have, as the user risks data loss or corruption if not done correctly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13 Uname: Linux 4.13.0-37-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 17 11:10:31 2018 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1756559/+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 1758331] Re: IPv6 Route to OpenVPN Server is not created
** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Committed -- 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/1758331 Title: IPv6 Route to OpenVPN Server is not created Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Committed Bug description: Hi, When the OpenVPN server pushes routes that overlaps with the openvpn server IP, it should add a route to the OpenVPN server. This seems to get done, but it fails: NetworkManager[1031]: [1521794922.6687] platform: signal: route 6 added: 2a00:x:x::3/128 via fe80::230:48ff:fedc:5067 dev 2 metric 100 mss 0 rt-src rt-ra src ::/128 pref-src 2a02:x:x:x:x:x:x:5fc6 NetworkManager[1031]: [1521794922.6687] device[0x55566c34c4e0] (enxa44cc890f4c8): queued IP6 config change NetworkManager[1031]: [1521794922.6688] platform: route: get IPv6 route for: 2a00:x:x::3 failed with unspecified 2a00:x:x::3 => VPN Server IPv6 Now this seems to be fixed in commit: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2d1fad641b950520bec1a87c450d0e3b1439e262 Can we get this cherry-picked in Bionic? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1758331/+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 1748323] Re: /usr/lib/chromium-browser/chromium-browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent
Hi Olivier, I'm sorry, I must've missed your reply. Apparently I did not auto- subscribe to the bug-updates. It crashed again today with 64.0.3282.167-0ubuntu0.17.10.1, so I went here, saw your response and tried to reproduce: before upgrading it crashed as expected, but with the latest version from your link (65.0.3325.88-0ubuntu0.17.10.1) it did NOT crash. So, that looks good :) (One minor nit: my failed attempts at reproducing somehow broke the scrolling in this Tab. The vertical slider works, but the mouse wheel just stopped working, both for the entire window and for this textarea where I'm typing this. In other Tabs the scroll-wheel works fine. And attempting to reproduce this new bug in other Tabs failed thusfar.) Cheers, Walter -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1748323 Title: /usr/lib/chromium-browser/chromium- browser:5:AsLocatedEvent:DispatchMouseEvent:DispatchEvent:non:DispatchEvent Status in chromium-browser package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 64.0.3282.140-0ubuntu0.17.10.1, the problem page at https://errors.ubuntu.com/problem/2ba87566e823966fa28f4720cc19be87bdb35b98 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/chromium-browser/+bug/1748323/+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 1733569] Re: In file explorer Modified column has day of week only (no time)
That's being discussed upstream in https://bugzilla.gnome.org/show_bug.cgi?id=774492 ** Bug watch added: GNOME Bug Tracker #774492 https://bugzilla.gnome.org/show_bug.cgi?id=774492 ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=774492 Importance: Unknown Status: Unknown -- 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/1733569 Title: In file explorer Modified column has day of week only (no time) Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: I opened the file explorer (Nautilus?) to check when a particular file was created. I was interested in time (this is what Windows would show). The Modified column shows only weekday name ("Thu") which makes it imprecise and kind of useless. I would expect to see at least hours and minutes ("Thu 07:44") When I replaced Modified column with Modified--Time (which shows "Thu 07:44"...), the change is not kept permanently. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1733569/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
This bug was fixed in the package ubuntu-fan - 0.12.10 --- ubuntu-fan (0.12.10) bionic; urgency=medium * fan-net: support systemd-networkd controlled interfaces (LP: #1718227) * fanctl: Fix net stop internal command (LP: #1744296) * fan-net: Harden networkctl usage (LP: #1718227) * ifupdown/ubuntu-fan: Test for missing fanctl (LP: #1742712) -- Stefan BaderFri, 16 Mar 2018 11:47:46 +0100 ** Changed in: ubuntu-fan (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1718227 Title: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts Status in aiccu package in Ubuntu: Invalid Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: New Status in bind9 package in Ubuntu: New Status in chrony package in Ubuntu: Confirmed Status in clamav package in Ubuntu: New Status in controlaula package in Ubuntu: New Status in epoptes package in Ubuntu: New Status in ethtool package in Ubuntu: New Status in guidedog package in Ubuntu: New Status in htpdate package in Ubuntu: New Status in ifenslave package in Ubuntu: New Status in ifmetric package in Ubuntu: New Status in ifupdown-multi package in Ubuntu: New Status in ifupdown-scripts-zg2 package in Ubuntu: New Status in isatapd package in Ubuntu: New Status in lprng package in Ubuntu: New Status in miredo package in Ubuntu: New Status in mythtv package in Ubuntu: New Status in nplan package in Ubuntu: New Status in nss-pam-ldapd package in Ubuntu: New Status in ntp package in Ubuntu: New Status in openntpd package in Ubuntu: New Status in openresolv package in Ubuntu: New Status in openssh package in Ubuntu: New Status in openvpn package in Ubuntu: New Status in postfix package in Ubuntu: New Status in quicktun package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in shorewall-init package in Ubuntu: New Status in sidedoor package in Ubuntu: New Status in slrn package in Ubuntu: New Status in tinc package in Ubuntu: New Status in ubuntu-fan package in Ubuntu: Fix Released Status in ucarp package in Ubuntu: New Status in uml-utilities package in Ubuntu: New Status in uruk package in Ubuntu: New Status in vlan package in Ubuntu: New Status in vzctl package in Ubuntu: New Status in wide-dhcpv6 package in Ubuntu: New Status in wpa package in Ubuntu: New Bug description: when network is configured with ifupdown, scripts in /etc/network/ifup.d/ were called on network being brought up and /etc/network/ifdown.d were called on network being brought down. Any packages that shipped these hooks need to be verified to have the same functionality under a netplan configured system. # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u) # for i in $binpkgs; do src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }'); [ -z "$src" ] && src="$i"; echo $src; done | sort -u aiccu aoetools avahi bind9 chrony clamav controlaula epoptes ethtool guidedog htpdate ifenslave ifmetric ifupdown-extra ifupdown-multi ifupdown-scripts-zg2 isatapd lprng miredo mythtv-backend nss-pam-ldapd ntp openntpd openresolv openssh openvpn postfix quicktun resolvconf sendmail shorewall-init sidedoor slrn tinc ubuntu-fan ucarp uml-utilities uruk vlan vzctl wide-dhcpv6 wpa Related bugs: * bug 1718227: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts * bug 1713803: replacement of resolvconf with systemd needs integration * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: netplan (not installed) ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 19 10:53:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service
+1, I filed a separate report in bug 1758920. -- 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/1756379 Title: Delay start of gnome-software service Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: New Bug description: On a default Bionic Desktop installation, gnome-software starts early and slows down session startup. In the bootchart attached, it overlaps with gnome-shell startup which is also resource intensive. With gnome-software delayed gnome-shell starts 2 seconds faster. gnome-software service startup should be delayed if it cannot be stop completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 17:11:41 2018 InstallationDate: Installed on 2013-09-03 (1654 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+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 1758917] [NEW] Can see and interact with dock on lock screen
Public bug reported: When I lock my screen, or the session becomes locked due to inactivity, I can see and interact with the dock on the lock screen. I am able to launch applications, though I cannot see the applications or interact with them until I log in. But upon logging in, those applications are open. I am using the dash-to-dock extension. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 09:44:25 2018 InstallationDate: Installed on 2018-03-24 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to bionic on 2018-03-26 (0 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1758917 Title: Can see and interact with dock on lock screen Status in gnome-screensaver package in Ubuntu: New Bug description: When I lock my screen, or the session becomes locked due to inactivity, I can see and interact with the dock on the lock screen. I am able to launch applications, though I cannot see the applications or interact with them until I log in. But upon logging in, those applications are open. I am using the dash-to-dock extension. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 09:44:25 2018 InstallationDate: Installed on 2018-03-24 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to bionic on 2018-03-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1758917/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758918] [NEW] unable to read filedescriptor flags for
Public bug reported: After upgrading libvte to latest release, When installing deb with gdebi, it shows following error: unable to read filedescriptor flags for https://bugs.launchpad.net/bugs/1758918 Title: unable to read filedescriptor flags for https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1758918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"
crashes on startup with [ATTENTION: default value of option force_s3tc_enable overridden by environment. [4005:4005:0326/150642.816056:ERROR:sandbox_linux.cc(375)] InitializeSandbox() called with multiple threads in process gpu-process. System XUbuntu 16.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1563184 Title: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process" Status in chromium-browser package in Ubuntu: Confirmed Bug description: crashes on startup with [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process Segmentation fault System ODROID XU3 armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+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 1758915] [NEW] gnome-software crashed with SIGSEGV in g_main_loop_is_running()
Public bug reported: ubuntu 18.04 . Again software not working (timeout error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 Uname: Linux 4.15.12-041512-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Mar 26 19:13:11 2018 ExecutablePath: /usr/bin/gnome-software InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu7 gnome-software-plugin-limba 3.28.0-0ubuntu7 gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service SegvAnalysis: Segfault happened at: 0x7f41d1c488e9: mov 0xc(%rdi),%eax PC (0x7f41d1c488e9) ok source "0xc(%rdi)" (0x0002010b) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: g_main_loop_is_running () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/liblimba.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with SIGSEGV in g_main_loop_is_running() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ** 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-software in Ubuntu. https://bugs.launchpad.net/bugs/1758915 Title: gnome-software crashed with SIGSEGV in g_main_loop_is_running() Status in gnome-software package in Ubuntu: New Bug description: ubuntu 18.04 . Again software not working (timeout error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 Uname: Linux 4.15.12-041512-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Mar 26 19:13:11 2018 ExecutablePath: /usr/bin/gnome-software InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu7 gnome-software-plugin-limba 3.28.0-0ubuntu7 gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service SegvAnalysis: Segfault happened at: 0x7f41d1c488e9 : mov 0xc(%rdi),%eax PC (0x7f41d1c488e9) ok source "0xc(%rdi)" (0x0002010b) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: g_main_loop_is_running () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/liblimba.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with SIGSEGV in g_main_loop_is_running() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1758915/+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 1733410] Re: awfully slow to respond when drawing selection rectangle
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1733410 Title: awfully slow to respond when drawing selection rectangle Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: open a folder containing some files click on an empty zone of the window and start dragging as if you wanted to select some files Expected behavior: as you move the mouse cursor while holding down the mouse button, the selection rectangle should be continuously redrawn. This redrawing should happen at a very fast rate (like more than a dozen times a second at the very least) so you would have the impression it is "continuous". Also, this should consume an almost undetectable amount of CPU. Observed behavior: the rectangle is not redrawn until you stop moving the mouse cursor. If you keep moving the mouse cursor, it will never be redrawn at all! If you do stop moving the mouse as you normally do, you will get the impression that the animation is terribly jerky, as if the computer was doing too much work. CPU consumption reaches 100% while you move the mouse, whether or not the selection rectangle is redrawn. The developers upstream say this is not an issue in Nautilus itself (I wonder how they can be so sure). https://gitlab.gnome.org/GNOME/nautilus/issues/127#note_8911 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 20 21:11:57 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1301x716+406+119'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1501 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1733410/+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 1733337] Re: Randomly fails to show folder contents, "loading..." forever
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => High -- 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/177 Title: Randomly fails to show folder contents, "loading..." forever Status in nautilus package in Ubuntu: New Bug description: This happens to me randomly every once in a very long while. I don't know of a way to reproduce it systematically. I just navigate to a folder. It says "Loading..." on the bottom-right of the window, and it stays like that forever, failing to display the contents of the folder, without any error message. It doesn't have to be a folder with lots of files. Right now I've just seen it happen with a folder that only contains 4 files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 20 15:28:13 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1377x833+2463+219'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1500 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/177/+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 1733342] Re: randomly doesn't show "index.html" file in folder
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1733342 Title: randomly doesn't show "index.html" file in folder Status in nautilus package in Ubuntu: Confirmed Bug description: I have a folder which contains a file called "index.html" and few more files. At random times, I open this folder in Nautilus and it shows all the files except for the one called index.html. It looks like it's just not there. The first time this happened I thought I had deleted it by accident. Exiting the folder and reopening it usually fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 20 16:19:19 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1301x716+406+119'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1500 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1733342/+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 1733073] Re: Files progress indicator blinks when file copy/move is in progress
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1733073 Title: Files progress indicator blinks when file copy/move is in progress Status in nautilus package in Ubuntu: Confirmed Bug description: When copying files from my computer's drive to a USB drive, the progress indicator constantly flickers. Please see here for a video recording of the issue: https://vimeo.com/243418988 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 00:41:44 2017 InstallationDate: Installed on 2017-11-04 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1733073/+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 1756379] Re: Delay start of gnome-software service
Disabling the gnome-software autostart for our live image sounds like a great idea to me. -- 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/1756379 Title: Delay start of gnome-software service Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: New Bug description: On a default Bionic Desktop installation, gnome-software starts early and slows down session startup. In the bootchart attached, it overlaps with gnome-shell startup which is also resource intensive. With gnome-software delayed gnome-shell starts 2 seconds faster. gnome-software service startup should be delayed if it cannot be stop completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 17:11:41 2018 InstallationDate: Installed on 2013-09-03 (1654 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+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 1756379] Re: Delay start of gnome-software service
+1 - I dont think there is a huge benefit to have it auto-start in the live session and starting the live session quicker seems more useful. -- 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/1756379 Title: Delay start of gnome-software service Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: New Bug description: On a default Bionic Desktop installation, gnome-software starts early and slows down session startup. In the bootchart attached, it overlaps with gnome-shell startup which is also resource intensive. With gnome-software delayed gnome-shell starts 2 seconds faster. gnome-software service startup should be delayed if it cannot be stop completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 17:11:41 2018 InstallationDate: Installed on 2013-09-03 (1654 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+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 1758896] Re: Machine fails to come back from suspend when running as a virtual machine
I tried duplicating #3 but all I got was a notification "Automatic Suspend Computer will suspend very soon because of inactivity." But it doesn't actually auto-suspend. So maybe it's a bit annoying to have that notification but not a critical bug. If you think that's a worthwhile bug, please file that bug separately. For #1, to resume from suspend, click in the VirtualBox menu: Machine > ACPI Shutdown. While not very intuitive, it vaguely makes sense that pressing the virtual power button would be a way to resume a computer from suspend if mouse or keyboard input doesn't work and there is no lid to open. So I'm going to reassign this bug to VirtualBox. ** Package changed: gnome-settings-daemon (Ubuntu) => virtualbox (Ubuntu) ** Changed in: virtualbox (Ubuntu) Importance: Undecided => Low ** Changed in: virtualbox (Ubuntu) Status: New => Confirmed -- 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/1758896 Title: Machine fails to come back from suspend when running as a virtual machine Status in virtualbox package in Ubuntu: Confirmed Bug description: This is a bit of a compound issue: 1) It is possible to suspend a machine via the top-right menu in GNOME Shell. Click and hold on the power button, it will change to a pause icon. Click this and the machine will suspend. You then can't get the machine to resume. 2) Not being able to resume could be a kernel bug, or a virtualbox bug, or none of these. 3) With a recent change upsteam https://gitlab.gnome.org/GNOME/gnome- settings-daemon/commit/2fdb48fa auto-suspending might be a default because of energy star requirements. If this setting is standard, then anyone running a virtual machine might find that they can't resume that machine because it's gone to sleep automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1758896/+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 1734891] Re: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file()
** Changed in: nautilus (Ubuntu) Status: New => Triaged -- 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/1734891 Title: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() Status in nautilus package in Ubuntu: Triaged Bug description: Hello, I'm working with nautilus and crash. Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.0-0ubuntu1 Uname: Linux 4.15.0-041500rc1-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 11:17:57 2017 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'253' b'org.gnome.nautilus.window-state' b'geometry' b"'890x547+255+180'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.desktop' b'home-icon-visible' b'true' InstallationDate: Installed on 2017-10-13 (45 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x5592953dfc28:mov0x10(%rbx),%rsi PC (0x5592953dfc28) ok source "0x10(%rbx)" (0xffc0) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_list_model_get_all_iters_for_file () nautilus_list_model_get_first_iter_for_file () ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1734891/+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 1756379] Re: Delay start of gnome-software service
I just saw that kalev proposed turning it off altogether on the Fedora live CD https://pagure.io/fedora-kickstarts/pull-request/368#request_diff ...maybe we should? -- 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/1756379 Title: Delay start of gnome-software service Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: New Bug description: On a default Bionic Desktop installation, gnome-software starts early and slows down session startup. In the bootchart attached, it overlaps with gnome-shell startup which is also resource intensive. With gnome-software delayed gnome-shell starts 2 seconds faster. gnome-software service startup should be delayed if it cannot be stop completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 17:11:41 2018 InstallationDate: Installed on 2013-09-03 (1654 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) InstalledPlugins: gnome-software-plugin-flatpak 3.28.0-0ubuntu3 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu3 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+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 1754809] Re: single click not working for "move/copy file context functions" of nautilus
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1754809 Title: single click not working for "move/copy file context functions" of nautilus Status in nautilus package in Ubuntu: New Bug description: "Single click" not working for "move/copy file context functions" of nautilus. Recentely I switched to the "Single click" mode of nautilus and this was the right decision. Works like a charme, BUT not if you right click a file an select "copy to" or "move to" functionalety. That's less of a bug than an inconsistence of the concept of the "Single click mode". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 [modified: usr/share/applications/nautilus-folder-handler.desktop] ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 10 07:17:22 2018 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754809/+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 1758398] Re: nautilus doesn't show network shares on 18.04
The change has been done in https://gitlab.gnome.org/GNOME/glib/commit/0d69462 -- 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/1758398 Title: nautilus doesn't show network shares on 18.04 Status in nautilus package in Ubuntu: New Bug description: After upgrade libglib2.0-0 from version 2.54.1-1ubuntu1 to 2.56.0-2ubuntu1 nautilus doesn't show on sidebar neither on desktop any mounted network share. I think it happens because changes in gio/gunixmounts.c at g_unix_is_system_fs_type() that added cifs and smbfs to ignore_fs. Network shares was mounted by pam_mount on /media/user/something. gsettings org.gnome.nautilus.desktop volumes-visible is set true. On Ubuntu Bionic 18.04 (devel branch) nautilus 1:3.26.2-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1758398/+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 1753267] Re: "Create new Document" Right click missing in Ubuntu 17.10
*** This bug is a duplicate of bug 1632027 *** https://bugs.launchpad.net/bugs/1632027 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1632027 New Document feature missing from Nautilus 3.20+ -- 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/1753267 Title: "Create new Document" Right click missing in Ubuntu 17.10 Status in nautilus package in Ubuntu: New Bug description: I am new user of Ubuntu. I love it's UI (user interface) and I am much interested learning Linux. Therefore, I have migrated from Windows to Ubuntu for few days back. For few days I started watching many tutorials on YouTube and many internet resources. While learning I have noticed that I am unable to create new document through using "Right Click" on mouse as I have seen some people did it successfully in their machine. Please help if you know about it for fixing the problem as I am facing right now. Moreover, I have mentioned the Ubuntu version I am using. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1753267/+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 1754671] Re: Full-tunnel VPN DNS leakage regression
** Tags added: incoming rs-bb- ** Tags removed: incoming rs-bb- ** Tags added: rls-bb-incoming -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in network-manager package in Ubuntu: Confirmed Bug description: In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1754671/+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 1740441] Re: Tag borders in nautilus search bar are truncated
Could you add a screenshot to the bug? The external one you are referencing to is not valid ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1740441 Title: Tag borders in nautilus search bar are truncated Status in Ubuntu theme: New Status in nautilus package in Ubuntu: Incomplete Status in ubuntu-themes package in Ubuntu: New Bug description: ubuntu 17.10 Nautilus search bar SS: https://i.hizliresim.com/rJWBP7.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1740441/+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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from
** Tags added: rls-bb-incoming -- 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/1748450 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from Status in gnome-shell package in Ubuntu: Triaged Bug description: *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+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 1758892] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1758892/+attachment/5091137/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1758892/+attachment/5091139/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1758892/+attachment/5091144/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1758892/+attachment/5091145/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1758892/+attachment/5091146/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1758892/+attachment/5091147/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1758892/+attachment/5091148/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1758892 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: Gnome-shell crashed when I opened the system menu. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 14:01:06 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-07-15 (1350 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_cancellable_make_pollfd () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_condition_timed_wait () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_input_stream_read () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) UserGroups: adm autopilot cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758892/+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 1755555] Re: nautilus crashed with SIGSEGV while trying to install Budgie Desktop applet
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/175 Title: nautilus crashed with SIGSEGV while trying to install Budgie Desktop applet Status in nautilus package in Ubuntu: Incomplete Bug description: This problem happens on Ubuntu Budgie 18.04 when first time in session I try to install applet using Budgie Desktop Applets. Seems like it only happens when installing Global menu applet (budgie-appmenu- applet) which afterwards also does not show up in applet list, though apt says it installed. But Pixel Saver applet (budgie-pixel-saver- applet) which has similar functionality installs without any problems and works fine. Release: 18.04 Description: Ubuntu Bionic Beaver (development branch) budgie-appmenu-applet: Installed: 0.6.92+repack1-3ubuntu1 budgie-pixel-saver-applet: Installed: 4.0+git20171102.30c1f94-0ubuntu1~bionic nautilus: Installed: 1:3.26.2-0ubuntu3.1 I should also mention that I could not login and got freezes after installation without nomodeset because of Nvidia drivers. I installed nvidia-384 driver and deleted xserver-xorg-video-nvidia-390 to fix these freezes and be able to login to desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 13 19:11:31 2018 Disassembly: No registers. ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+108+80'" b'org.gnome.nautilus.desktop' b'network-icon-visible' b'true' b'org.gnome.nautilus.desktop' b'volumes-visible' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-03-12 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180312) ProcCmdline: /usr/bin/nautilus --gapplication-service Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: nautilus Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/175/+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 1758896] [NEW] Machine fails to come back from suspend when running as a virtual machine
Public bug reported: This is a bit of a compound issue: 1) It is possible to suspend a machine via the top-right menu in GNOME Shell. Click and hold on the power button, it will change to a pause icon. Click this and the machine will suspend. You then can't get the machine to resume. 2) Not being able to resume could be a kernel bug, or a virtualbox bug, or none of these. 3) With a recent change upsteam https://gitlab.gnome.org/GNOME/gnome- settings-daemon/commit/2fdb48fa auto-suspending might be a default because of energy star requirements. If this setting is standard, then anyone running a virtual machine might find that they can't resume that machine because it's gone to sleep automatically. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1758896 Title: Machine fails to come back from suspend when running as a virtual machine Status in gnome-settings-daemon package in Ubuntu: New Bug description: This is a bit of a compound issue: 1) It is possible to suspend a machine via the top-right menu in GNOME Shell. Click and hold on the power button, it will change to a pause icon. Click this and the machine will suspend. You then can't get the machine to resume. 2) Not being able to resume could be a kernel bug, or a virtualbox bug, or none of these. 3) With a recent change upsteam https://gitlab.gnome.org/GNOME/gnome- settings-daemon/commit/2fdb48fa auto-suspending might be a default because of energy star requirements. If this setting is standard, then anyone running a virtual machine might find that they can't resume that machine because it's gone to sleep automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749007] Re: Snap mounts should be hidden from System Monitor
** Changed in: gnome-system-monitor (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1749007 Title: Snap mounts should be hidden from System Monitor Status in gnome-system-monitor package in Ubuntu: In Progress Bug description: As per https://community.ubuntu.com/t/snaps-in-system-monitor/3961 the snap mounts in System Monitor should be hidden just as they're hidden from GNOME Disks. Perhaps they should be grouped under a dropdown of / (though this would require developing a new feature)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1749007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update
@jdonald: how can I direct the output of 'layout asm' from gdb into a textfile? -- 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/1711337 Title: Firefox crashes at start on armv7L after 55.0.1 update Status in Mozilla Firefox: Expired Status in firefox package in Ubuntu: Confirmed Bug description: Firefox always crashes when launched after the 55.0.1 update on an Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi), even in safe mode. I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for ARM single-board computer) on a similar board (Orange Pi Plus 2e), installed Firefox and experienced the same problem--it won't load without crashing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 55.0.1+build2-0ubuntu0.16.04.2 Uname: Linux 3.4.113-sun8i armv7l AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.20.1-0ubuntu2.10 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jim1138 F pulseaudio /dev/snd/controlC0: jim1138 F pulseaudio BuildID: 20170814194718 Card0.Amixer.info: Card hw:0 'audiocodec'/'audiocodec' Mixer name : '' Components : '' Controls : 12 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'sndhdmi'/'sndhdmi' Mixer name : '' Components : '' Controls : 1 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'hdmi audio format Function',0 Capabilities: enum Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO' Item0: 'pcm' Channel: Unavailable CurrentDesktop: XFCE Date: Thu Aug 17 05:37:00 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.10.1 dev eth0 default via 192.168.10.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.107 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.108 metric 600 Locales: extensions.sqlite corrupt or missing PciMultimedia: PciNetwork: Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1711337/+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 1758398] Re: nautilus doesn't show network shares on 18.04
The description is misleading, smb: or ssh: mounts done from the desktop are listed, it's only about traditional mounts using cifs/smbfs right? -- 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/1758398 Title: nautilus doesn't show network shares on 18.04 Status in nautilus package in Ubuntu: New Bug description: After upgrade libglib2.0-0 from version 2.54.1-1ubuntu1 to 2.56.0-2ubuntu1 nautilus doesn't show on sidebar neither on desktop any mounted network share. I think it happens because changes in gio/gunixmounts.c at g_unix_is_system_fs_type() that added cifs and smbfs to ignore_fs. Network shares was mounted by pam_mount on /media/user/something. gsettings org.gnome.nautilus.desktop volumes-visible is set true. On Ubuntu Bionic 18.04 (devel branch) nautilus 1:3.26.2-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1758398/+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 1758398] Re: nautilus doesn't show network shares on 18.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1758398 Title: nautilus doesn't show network shares on 18.04 Status in nautilus package in Ubuntu: New Bug description: After upgrade libglib2.0-0 from version 2.54.1-1ubuntu1 to 2.56.0-2ubuntu1 nautilus doesn't show on sidebar neither on desktop any mounted network share. I think it happens because changes in gio/gunixmounts.c at g_unix_is_system_fs_type() that added cifs and smbfs to ignore_fs. Network shares was mounted by pam_mount on /media/user/something. gsettings org.gnome.nautilus.desktop volumes-visible is set true. On Ubuntu Bionic 18.04 (devel branch) nautilus 1:3.26.2-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1758398/+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 1756559] Re: No status indicator for File Copy and/or Moves
Thank you for your bug report. Could you take a screenshot of your nautilus window after starting the copy? There should be a circle icon in the toolbar you can click on which displays the copy status/details. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1756559 Title: No status indicator for File Copy and/or Moves Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus does not show a status indicator when the user is copying or moving a file from an NAS device to their local disk. This is very important to have, as the user risks data loss or corruption if not done correctly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-lowlatency 4.13.13 Uname: Linux 4.13.0-37-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 17 11:10:31 2018 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1756559/+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 1758745] Re: Single click in icon view not working in nautilus
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1758745 Title: Single click in icon view not working in nautilus Status in nautilus package in Ubuntu: New Bug description: In icon view single click setting seems not working. I need to double click to open a file or folder. Single click works as expected in details view. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 22:02:25 2018 InstallationDate: Installed on 2017-01-07 (441 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sl_SI.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1758745/+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