[Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
Still 197MB, not used, fresh after boot-up, on 18.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Please also try removing the other extensions. There's more than two: b'org.gnome.shell' b'enabled-extensions' b"['update- extensi...@franglais125.gmail.com', 'freon@Veske', 'netsp...@hedayaty.gmail.com', 'openweather-extens...@jenslody.de', 'public-ip-addr...@holdingitwrong.com', 'alternate-tab@gnome-shell- extensions.gcampax.github.com', 'window-list@gnome-shell- extensions.gcampax.github.com']" If the problem persists with no extensions (and after rebooting) then please run: journalctl -b > journal.txt and attach the resulting journal.txt here. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
apport information ** Tags added: apport-collected bionic ** Description changed: lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.2-0ubuntu0.18.04.1 Candidate: 3.28.2-0ubuntu0.18.04.1 Version table: *** 3.28.2-0ubuntu0.18.04.1 500 Since upgrading from 16.04.5LTS to 18.04.1LTS last Thursday my syslog has been filling with the below: Aug 19 11:34:11 localhost gnome-shell[2503]: Object Meta.Background (0x7febd401a470), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: == Stack trace for context 0x561c9a54e330 == Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #0 0x561c9a9edbd8 i resource:///org/gnome/shell/ui/background.js:718 (0x7febd000f450 @ 22) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #1 0x561c9a9edb50 i resource:///org/gnome/shell/ui/tweener.js:113 (0x7febd02c7e68 @ 37) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #2 0x7fff0e3e36e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7febd02d3b38 @ 54) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #3 0x7fff0e3e3830 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7febd02d3bc0 @ 1626) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #4 0x7fff0e3e38e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7febd02d3c48 @ 100) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #5 0x7fff0e3e3970 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7febd02d3cd0 @ 10) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #6 0x7fff0e3e3a60 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7febd02d3230 @ 386) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #7 0x7fff0e3e3b10 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7febd02cf808 @ 159) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #8 0x7fff0e3e3be0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7febd02b5de0 @ 71) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #9 0x7fff0e3e3c80 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7febd02cf780 @ 15) Following suggestions in previous bug reports about this I went through and removed all of my shell extensions: chris@localhost:~/.local/share/gnome-shell/extensions$ ls -l total 0 chris@localhost:~/.local/share/gnome-shell/extensions$ + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2014-10-24 (1395 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-32-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-08-17 (3 days ago) + UserGroups: adm cdrom dip kvm libvirt libvirtd lpadmin netdev plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1787822/+attachment/5177750/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
I reinstalled two of the Gnome Extensions, Freon and Window List since removing all extensions had no effect. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1787822/+attachment/5177751/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1787822/+attachment/5177752/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725836] Re: No more than 2 displays work simultaneously
Thanks. Comment #33 seems to be the most important one now. If the bug occurs in XFCE as well then this is not a gnome-shell bug. Instead it should be assigned to xorg-server, or the driver, or the kernel. ** No longer affects: mutter ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: mutter (Ubuntu) ** Summary changed: - No more than 2 displays work simultaneously + [radeon] No more than 2 displays work simultaneously ** Tags added: radeon ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: [radeon] No more than 2 displays work simultaneously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1055025] Re: Unable to rename .desktop file
*** This bug is a duplicate of bug 1786233 *** https://bugs.launchpad.net/bugs/1786233 ** This bug has been marked a duplicate of bug 1786233 Can't rename a desktop file -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1055025 Title: Unable to rename .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1055025/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787839] Re: Nautilus won't allow .desktop extension to be changed
*** This bug is a duplicate of bug 1786233 *** https://bugs.launchpad.net/bugs/1786233 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1786233, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1786233 Can't rename a desktop file -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1787839 Title: Nautilus won't allow .desktop extension to be changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1787839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1787822 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786233] Re: Can't rename a desktop file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1786233 Title: Can't rename a desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786233/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787809] Re: Main DVD menu of an ISO image fails to open in totem, but opens in VLC
** Summary changed: - Main menu of an ISO image fails to open in totem, but opens in VLC + Main DVD menu of an ISO image fails to open in totem, but opens in VLC -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1787809 Title: Main DVD menu of an ISO image fails to open in totem, but opens in VLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1787809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786233] Re: Can't rename a desktop file
** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1786233 Title: Can't rename a desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1786233/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 572045] Re: should be marked undumpable to avoid PTRACE attach
This was actually fixed (with a Debian patch) in the gnupg 2.1.7-1 upload. ** Changed in: gnupg2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/572045 Title: should be marked undumpable to avoid PTRACE attach To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/572045/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787748] Re: ubuntu.session is trying to write '/usr/share/gnome-session/sessions/ubuntu.session', which is also in the gnome-session
** Summary changed: - Ubuntu.session in gnome-session + ubuntu.session is trying to write '/usr/share/gnome-session/sessions/ubuntu.session', which is also in the gnome-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1787748 Title: ubuntu.session is trying to write '/usr/share/gnome- session/sessions/ubuntu.session', which is also in the gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1787748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04
Please tell us the ID of the bug created by (or related to) that crash report. If you can't find it then you can look for crash reports from the current boot by: journalctl -b | grep "OOPS ID" or from the previous boot: journalctl -b-1 | grep "OOPS ID" and tell us the new OOPS ID. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1787277 Title: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
Sounds like a good idea. But _GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED would have do be done for each app separately. It's not something the shell does. So this bug is now closed for gnome-shell, and should be reopened with tasks for each affected application. To do that click on "Also affects distribution/package" at the top of the bug. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
Indeed, removing all extensions should be the first thing to check when dealing with gnome-shell bugs. But calling them extension crashes isn't quite right. Extensions can effectively modify the code of gnome-shell at runtime and then gnome- shell crashes. This is unfortunate for reliability, but is probably the reason why we can have so many extensions at all. So I don't imagine gnome-shell will ever have a more reliable way of dealing with buggy extensions aside from us reminding people to uninstall them when problems occur. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777405] Re: Freezes on switching back from second login
** Changed in: gdm3 (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1777405 Title: Freezes on switching back from second login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777405/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787867] [NEW] Ubuntu 18.04 LTS bluetooth left discoverable
Public bug reported: Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable which opens up unnecessary vulnerability surface. There should be a separate UI switch for discoverability with auto timeout. Leaving bluetooth on (using a Bluetooth mouse) should not leave the computer always discoverable. Current behavior does not match documentation https://help.ubuntu.com/stable/ubuntu-help/bluetooth-visibility.html.en, even without Bluetooth panel open, the computer is still discoverable. ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787748] Re: Ubuntu.session in gnome-session
** Changed in: gnome-session (Ubuntu) Importance: Undecided => Critical ** Tags added: rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1787748 Title: Ubuntu.session in gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1787748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787863] Re: gnome-control-center occasionally fails to launch after multiple tries
Research leads me to believe this should be an upstream bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1787863 Title: gnome-control-center occasionally fails to launch after multiple tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1787863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787863] [NEW] gnome-control-center occasionally fails to launch after multiple tries
Public bug reported: Release: Ubuntu 18.04.1 LTS Package Version: 1:3.28.2-0ubuntu0.18.04.1 Expected Behavior: Program should always launch upon request. Problematic Behavior: Attempting to launch this program causes the shell to display the loading indicator for an unusual amount of time, only to never display the program. Description: Upon launching this program through a terminal emulator, it never opens and never displays any output. Passing the verbose (-v) option with the program has the same result. When I launch it through the GUI, the shell displays the spinning circle (loading indicator) for an absurd amount of time. The program still does not open. This is a fresh install, so I restarted my computer. When launched again, the program opened and operated normally. However, upon closing the program and opening it again, it does not open up. Task management tools only show the process for a brief 3-5 seconds after requesting it to open and then it disappears. To my knowledge, this bug does not affect any other programs. Workaround: Entering the command killall gnome-control-center allows it to open again upon next launches. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sun Aug 19 18:17:37 2018 InstallationDate: Installed on 2018-08-19 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1787863 Title: gnome-control-center occasionally fails to launch after multiple tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1787863/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770502] Re: Brasero hangs when burning cds
I was also unable to burn anything in Brasero with default options. Making cdrdao & wodim setuid root (4711) solved the problem for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1770502 Title: Brasero hangs when burning cds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714804] Re: Aardvark Daily: Indicator-Multiload doesn't show full-width
I can confirm that Martin Vysny's solution/workaround works in Ubuntu 18.04.1LTS. (this was not the case in Ubuntu Alpha when I reported this bug) Please note that you have to reboot (or log-off and logon again) for the system-monitor to show up in the gnome-tweaks extensions page. Time to say goodbye to indicator-multiload and thank Michael Hofmann for the years of enjoyment we had from his software indicator-multiload. Thank you Michael -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1714804 Title: Aardvark Daily: Indicator-Multiload doesn't show full-width To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/1714804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787839] Re: Nautilus won't allow .desktop extension to be changed
UpgradeStatus: No upgrade log present (probably fresh install) Yes it was a fresh install. I installed Bionic Beaver x64, one week ago. It was not an upgrade, it was a "clean" install on a newly formatted disk drive. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1787839 Title: Nautilus won't allow .desktop extension to be changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1787839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787839] [NEW] Nautilus won't allow .desktop extension to be changed
Public bug reported: Ubuntu 18.04 LTE Bionic Beaver. 1. right click mouse on desktop and select New Document -> Untitled The file Untitled.desktop appears. 2. Right click on the file and select Rename. 3. In the file name dialog box, rename as follows: From: Untitled.desktop To: Untitled.txt Then click the rename button in the dialog box. The dialog box closes and a file appears with a name of: Untitled.txt.desktop Thus, ".desktop" cannot be deleted or renamed. I expected to see Untitled.txt not Untitled.txt.desktop I also expect to be able to create a file with no extension at all on linux. Cannot do that either. I have also duplicated this behavior in other folders apart from the desktop such as the default documents folder. The only workaround I have is to create a file with extension that does not end with .desktop is to use a text editor like Notepad++ to create a new file then use "Save As". Is this a bug? If not, it seems odd behavior. If I want to create a new C++ file such as foo.cpp then I cannot do it with this behavior and the make built-in rules will never file foo.cpp.desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 14:51:12 2018 InstallationDate: Installed on 2018-08-13 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color 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) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1787839 Title: Nautilus won't allow .desktop extension to be changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1787839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04
Wrong crash file, oops (blush) I uploaded the gnome-shell one. whoopsie 114M aug 19 20:52 _usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1787277 Title: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04
Well gnome-shell crashed again and won't let me in again. whoopsie 35M aug 19 20:51 _opt_minergate_minergate.1000.crash I've attached a new previous boot ** Attachment added: "new previous boot" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+attachment/5177611/+files/previous_boot1.log.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1787277 Title: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
** Changed in: appstream (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] [NEW] gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.2-0ubuntu0.18.04.1 Candidate: 3.28.2-0ubuntu0.18.04.1 Version table: *** 3.28.2-0ubuntu0.18.04.1 500 Since upgrading from 16.04.5LTS to 18.04.1LTS last Thursday my syslog has been filling with the below: Aug 19 11:34:11 localhost gnome-shell[2503]: Object Meta.Background (0x7febd401a470), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: == Stack trace for context 0x561c9a54e330 == Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #0 0x561c9a9edbd8 i resource:///org/gnome/shell/ui/background.js:718 (0x7febd000f450 @ 22) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #1 0x561c9a9edb50 i resource:///org/gnome/shell/ui/tweener.js:113 (0x7febd02c7e68 @ 37) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #2 0x7fff0e3e36e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7febd02d3b38 @ 54) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #3 0x7fff0e3e3830 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7febd02d3bc0 @ 1626) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #4 0x7fff0e3e38e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7febd02d3c48 @ 100) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #5 0x7fff0e3e3970 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7febd02d3cd0 @ 10) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #6 0x7fff0e3e3a60 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7febd02d3230 @ 386) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #7 0x7fff0e3e3b10 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7febd02cf808 @ 159) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #8 0x7fff0e3e3be0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7febd02b5de0 @ 71) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #9 0x7fff0e3e3c80 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7febd02cf780 @ 15) Following suggestions in previous bug reports about this I went through and removed all of my shell extensions: chris@localhost:~/.local/share/gnome-shell/extensions$ ls -l total 0 chris@localhost:~/.local/share/gnome-shell/extensions$ ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787821] Re: appstreamcli refresh crashes with glib error
*** This bug is a duplicate of bug 1785498 *** https://bugs.launchpad.net/bugs/1785498 ** This bug has been marked a duplicate of bug 1785498 g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1787821 Title: appstreamcli refresh crashes with glib error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1787821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
** Changed in: appstream (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: appstream (Ubuntu) Assignee: (unassigned) => Matthias Klumpp (ximion) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787821] [NEW] appstreamcli refresh crashes with glib error
Public bug reported: After aptitude started reporting errors during a run of appstreamcli, I checked the mentioned command manually, and indeed it fails with a glib error: marc@ellen:~$ sudo appstreamcli refresh-cache (appstreamcli:16742): GLib-CRITICAL **: 18:30:00.982: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:16742): GLib-CRITICAL **: 18:30:00.982: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:16742): GLib-ERROR **: 18:30:00.982: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap I also tried: marc@ellen:~$ sudo appstreamcli refresh (appstreamcli:16676): GLib-CRITICAL **: 18:29:54.246: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:16676): GLib-CRITICAL **: 18:29:54.246: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:16676): GLib-ERROR **: 18:29:54.246: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap marc@ellen:~$ sudo appstreamcli refresh --force (appstreamcli:17374): GLib-CRITICAL **: 18:30:36.810: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:17374): GLib-CRITICAL **: 18:30:36.811: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:17374): GLib-ERROR **: 18:30:36.811: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap I am not sure whether this recent upgrade is related: [UPGRADE] libappstream-glib8:amd64 0.7.7-2 -> 0.7.10-1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: appstream 0.12.0-3 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Aug 19 18:26:51 2018 InstallationDate: Installed on 2016-01-20 (941 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1787821 Title: appstreamcli refresh crashes with glib error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1787821/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
This is fixed in Debian now, in package appstream/0.12.2-2. ** Bug watch added: Debian Bug tracker #906538 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906538 ** Also affects: appstream (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906538 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
** Changed in: appstream Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787774] Re: appstreamcli crashed with signal 5 in g_variant_new_parsed_va()
*** This bug is a duplicate of bug 1785498 *** https://bugs.launchpad.net/bugs/1785498 ** This bug has been marked a duplicate of bug 1785498 g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1787774 Title: appstreamcli crashed with signal 5 in g_variant_new_parsed_va() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1787774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787802] Re: appstreamcli crashed with signal 5 in g_variant_new_parsed_va()
*** This bug is a duplicate of bug 1785498 *** https://bugs.launchpad.net/bugs/1785498 ** This bug is no longer a duplicate of private bug 1787774 ** This bug has been marked a duplicate of bug 1785498 g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1787802 Title: appstreamcli crashed with signal 5 in g_variant_new_parsed_va() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1787802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1709144] Re: /usr/bin/appstreamcli:*** Error in `appstreamcli': double free or corruption (!prev): ADDR ***
This issue was actually fixed in AppStream ages ago - definitely resolved in Bionic+. ** Changed in: appstream (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1709144 Title: /usr/bin/appstreamcli:*** Error in `appstreamcli': double free or corruption (!prev): ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1709144/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
See the linked upstream issue for details - this will be fixed soon. ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Invalid ** Bug watch added: github.com/ximion/appstream/issues #198 https://github.com/ximion/appstream/issues/198 ** Also affects: appstream via https://github.com/ximion/appstream/issues/198 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787809] [NEW] Main menu of an ISO image fails to open in totem, but opens in VLC
Public bug reported: I used brasero to make an iso image of a DVD that I personally own myself (original, no copy) and if I try to open the iso in totem it fails to open the main menu. Nothing happens. If I open the same iso image with VLC it shows the main menu just fine and plays the movie. Opening the same iso image with mplayer (ran from a terminal window) skips the main menu, but plays the movie instantly so the iso image is OK. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Aug 19 14:24:41 2018 InstallationDate: Installed on 2018-08-14 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1787809 Title: Main menu of an ISO image fails to open in totem, but opens in VLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1787809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787802] Re: appstreamcli crashed with signal 5 in g_variant_new_parsed_va()
*** This bug is a duplicate of bug 1787774 *** https://bugs.launchpad.net/bugs/1787774 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 #1787774, 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/1787802/+attachment/5177457/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1787802/+attachment/5177459/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1787802/+attachment/5177463/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1787802/+attachment/5177464/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1787802/+attachment/5177465/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1787802/+attachment/5177466/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1787802/+attachment/5177467/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1787774 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1787802 Title: appstreamcli crashed with signal 5 in g_variant_new_parsed_va() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1787802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787802] [NEW] appstreamcli crashed with signal 5 in g_variant_new_parsed_va()
Public bug reported: Crashed when triggerred from initramfs, had to uninstall it to make progress. Reinstalled and running it manually shows no crashes but an assertion: (appstreamcli:5869): GLib-CRITICAL **: 11:01:51.409: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed AppStream cache update completed successfully ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: appstream 0.12.0-3 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Aug 18 21:19:53 2018 ExecutablePath: /usr/bin/appstreamcli InstallationDate: Installed on 2017-12-02 (259 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: appstreamcli refresh-cache Signal: 5 SourcePackage: appstream StacktraceTop: g_variant_new_parsed_va () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_parsed () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libappstream.so.4 () at /usr/lib/x86_64-linux-gnu/libappstream.so.4 as_cache_file_save () at /usr/lib/x86_64-linux-gnu/libappstream.so.4 Title: appstreamcli crashed with signal 5 in g_variant_new_parsed_va() UpgradeStatus: Upgraded to cosmic on 2018-08-07 (11 days ago) UserGroups: ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash cosmic need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1787802 Title: appstreamcli crashed with signal 5 in g_variant_new_parsed_va() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1787802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
