[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
Although a fix is mentioned as released, I still can't see Wayland used or even available for choosing in the GDM (The wheel at the bottom right of the GDM login screen only show Ubuntu and Gnome Classic but no Wayland). How do I get Wayland to be used instead of X11? In Settings --> About, Window System states X11 System info: $ uname -srmpo Linux 5.15.0-47-generic x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy $ nvidia-smi +-+ | NVIDIA-SMI 470.141.03 Driver Version: 470.141.03 CUDA Version: 11.4 | |---+--+--+ $ gnome-shell libmutter-Message: 00:26:16.788: Running GNOME Shell (using mutter 42.2) as a X11 window and compositing manager org.gnome.Shell already exists on bus and --replace not specified -- 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/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769221] Re: "Switch User" fails, gives a blank screen with a mouse cursor.
*** This bug is a duplicate of bug 1766137 *** https://bugs.launchpad.net/bugs/1766137 ** Summary changed: - switching user fails + "Switch User" fails, gives a blank screen with a mouse cursor. -- 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/1769221 Title: "Switch User" fails, gives a blank screen with a mouse cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769221] Re: switching user fails
*** This bug is a duplicate of bug 1766137 *** https://bugs.launchpad.net/bugs/1766137 On several occasions, when I click on "Switch User" I would be directed to a black screen with a mouse cursor where the mouse cursor may work in a very lagging manner and nothing else seems to work(no keyboard response). To get out of this situation, I needed to manually power off my system and power it up again to boot the system up again. This recovery procedure is bad for my system. Sometimes this bad situation happens and sometimes I would successfully be directed to the login screen to switch users successfully. Any idea what is causing this issue or how I can fix this issue? [Update:] On my next bootup, I re-tried using the "Switch User" button. I got the same black screen and mouse cursor. But this time around, the default Ubuntu screensaver or screen shield appeared ( after several seconds of delay) instead of the background that I had set previously. After pressing any keyboard key, the screen shield goes away and the Login screen appears. I am able to login as myself or as another user. It was mentioned here that this situation is a duplicate of bug #1766137 and in that report a fixed had already been issued. But I still encounter this issue. There I like to reopen this issue. -- 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/1769221 Title: "Switch User" fails, gives a blank screen with a mouse cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769221/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841130] Re: idle, idle-python is missing from Apps Store
I think this issue is fixed. I can now find IDLE (using Python-3.6) in gnome-software. -- 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/1841130 Title: idle, idle-python is missing from Apps Store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1841130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841130] Re: idle, idle-python is missing from Apps Store
@Matthias. In Ubuntu18.04, after pressing the "Super" key on the keyboard and typing "idle" in the search box, a python icon does appear. Also, after selecting it and python-idle does appear, in the dash-to- dock a different icon is used to represent python-idle. So there are available and suitable icons that can be used to represent python-idle. Since there are available icons for representing python-idle, can you tell me what must I do to point to these icons? Thanks. I don't recall having this issue in Ubuntu 16.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/1841130 Title: idle, idle-python is missing from Apps Store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1841130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841130] Re: idle, idle-python is missing from Apps Store
The question https://askubuntu.com/questions/1120736/idle-for-python-3-6 -cant-open-py-files-on-ubuntu-18-04 shows evidence that idle was available in App Store 6 months. Evidence seems to show this issue had occurred 1yr 3mths ago, The situation seem to have been fixed 6 mths ago, and presently the bug has re-occurred. Something causing this regression. Hope the cause of this issue can be discovered and nipped out soon. Thanks. -- 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/1841130 Title: idle, idle-python is missing from Apps Store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1841130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841130] [NEW] idle, idle-python is missing from Apps Store
Public bug reported: The following packages cannot be found in the Apps Store in Ubuntu 18.04 and 19.04: idle/bionic-updates,bionic-updates 3.6.7-1~18.04 all idle-python2.7/bionic-updates,bionic-updates,bionic-security,bionic-security 2.7.15-4ubuntu4~18.04 all idle-python3.6/bionic-updates,bionic-updates,bionic-security,bionic-security 3.6.8-1~18.04.1 all idle-python3.7/bionic-updates,bionic-updates,bionic-security,bionic-security 3.7.3-2~18.04.1 all idle3/bionic-updates,bionic-updates 3.6.7-1~18.04 all They used to be available. These are default tools for python scripting and should be made available. $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep linux-generic-hwe- ii linux-generic-hwe-18.04 5.0.0.25.82amd64 Complete Generic Linux kernel and headers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ dpkg -l | grep ubuntu-software ii ubuntu-software3.28.1-0ubuntu4.18.04.10 all Utility for browsing, installing, and removing software $ dpkg -l | grep gnome-software ii gnome-software 3.28.1-0ubuntu4.18.04.10 amd64 Software Center for GNOME ii gnome-software-common 3.28.1-0ubuntu4.18.04.10all Software Center for GNOME (common files) ii gnome-software-plugin-snap 3.28.1-0ubuntu4.18.04.10 amd64 Snap support for GNOME Software $ grep -r --include '*.list' '^deb ' /etc/apt/sources.list /etc/apt/sources.list.d/ /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic main restricted /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic universe /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-updates universe /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic multiverse /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-updates multiverse /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse /etc/apt/sources.list:deb http://archive.canonical.com/ubuntu bionic partner /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-security main restricted /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-security universe /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu bionic-security multiverse https://askubuntu.com/questions/1167734/where-is-idle-python3-6 Asked today https://askubuntu.com/questions/1057574/software-centre-how-does-it-choose-what-to-show Asked 1 year, 1 month ago https://askubuntu.com/questions/1029872/where-is-idle-18-04 Asked 1 year, 3 months ago ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1841130 Title: idle, idle-python is missing from Apps Store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1841130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I discovered that the Software & Updates application "Authentication" tab's "Remove" button does not work properly too. After pressing the "Remove" button, pkexec was called. After submitting the password for administration level, nothing happens, i.e. Trusted software keys that was selected for deletion do not get removed. Not error was shown in terminal. $ dpkg -l | grep software-properties ii python3-software-properties0.96.24.32.11 all manage the repositories that you install software from ii software-properties-common 0.96.24.32.11 all manage the repositories that you install software from (common) ii software-properties-gtk0.96.24.32.11 all manage the repositories that you install software from (gtk) I had filed a bug report (see https://bugs.launchpad.net/ubuntu/+source /software-properties/+bug/1840624). Should it fall under this bug report too and this bug report's title be amended to include the "Authentication" Tab? -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1553802] Re: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them)
:) All the more reason for Ubuntu 18.04 to receive the fix? Any timeline planned? My bad for mixing 16.04 end of life with 18.04. -- 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/1553802 Title: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1553802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1553802] Re: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them)
Any chance that this bug will be fixed for Ubuntu 18.04? It still has about 1.5 years of support life to it? -- 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/1553802 Title: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1553802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1553802] Re: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them)
I would like to nominate the fix be made available to Ubuntu 18.04. It seems strange the fix isn't made available to a LTS version which is more highly used than a .10 version. I tried pressing the nomination button, but it complained that: "You do not have permission to nominate this bug." I had filed a similar bug report here https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840265. -- 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/1553802 Title: Date and time jump around on locked screen when showing seconds (and also sometimes display strange shadows behind them) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1553802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I encountered this same issue in a freshly installed Ubuntu 18.04 system. $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 $ gnome-shell --version GNOME Shell 3.28.4 To discover the error, I ran this app via command line: $ /usr/bin/python3 /usr/bin/software-properties-gtk ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved ERROR:root:Authentication canceled, changes have not been saved The above errors appear every time the mouse arrow left-clicks on the checkbox. I circumvent this issue by: 1. left-click on Canonical Partners to select it. 2. left click on the edit button. 3. after the Edit Source GUI appeared, I left-clicked on the "OK" button. 4. finally when I left-click on the checkbox of Canonical Partners, the checkbox becomes selected. -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840265] Re: "Date" in Ubuntu 18.04 Lock Screen is not always center aligned when "Tweaks-->Top Bar-->Seconds" is set to be "True".
** Summary changed: - "Date" in Ubuntu 18.04 Lock Screen is not always center aligned. + "Date" in Ubuntu 18.04 Lock Screen is not always center aligned when "Tweaks-->Top Bar-->Seconds" is set to be "True". -- 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/1840265 Title: "Date" in Ubuntu 18.04 Lock Screen is not always center aligned when "Tweaks-->Top Bar-->Seconds" is set to be "True". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1840265/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840265] Re: "Date" in Ubuntu 18.04 Lock Screen is not always center aligned.
I discovered the trigger for the misalignment, i.e. it occurs when `Tweaks-->Top Bar-->Seconds` is set to be `True`. -- 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/1840265 Title: "Date" in Ubuntu 18.04 Lock Screen is not always center aligned when "Tweaks-->Top Bar-->Seconds" is set to be "True". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1840265/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840265] [NEW] "Date" in Ubuntu 18.04 Lock Screen is not always center aligned.
Public bug reported:
Issue:
In Ubuntu 18.04, there appears to be an issue with the alignment of the
shown "Date" in the locked screen, i.e. `.screen-shield-clock-date{}` in
`/usr/share/gnome-shell/theme/ubuntu.css`. It sometimes appear center-
aligned and sometimes left-aligned w.r.t `.screen-shield-clock{}`. It
seems that `.screen-shield-clock-date{}` is a child of
.screen-shield-clock {
color: white;
text-shadow: 0px 1px 2px rgba(0, 0, 0, 0.6);
font-weight: bold;
text-align: center;
padding-bottom: 1.5em; }
which already contains the `text-align: center` argument to require center
alignment.
I have tried adding `margin: auto; width: 100%;` in both
`.screen-shield-clock{}` and `.screen-shield-clock-date{}`, and also adding
`text-align: center` in `.screen-shield-clock-date{}` but these approaches
don't seem to work?
How can a user fix this date alignment issue or is this a bug with gdm3?
**System information:**
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ dpkg -l | grep gdm
ii gdm3 3.28.3-0ubuntu18.04.4 amd64 GNOME Display Manager
ii gir1.2-gdm-1.0 3.28.3-0ubuntu18.04.4 amd64 GObject introspection
data for the GNOME Display Manager
ii libgdm13.28.3-0ubuntu18.04.4 amd64 GNOME Display Manager
(shared library)
$ apt-cache policy gdm3
gdm3:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
*** 3.28.3-0ubuntu18.04.4 500
500 http://sg.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1 500
500 http://sg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
$ apt-cache policy gir1.2-gdm-1.0
gir1.2-gdm-1.0:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
*** 3.28.3-0ubuntu18.04.4 500
500 http://sg.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1 500
500 http://sg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
$ apt-cache policy libgdm1
libgdm1:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
*** 3.28.3-0ubuntu18.04.4 500
500 http://sg.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1 500
500 http://sg.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: 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/1840265
Title:
"Date" in Ubuntu 18.04 Lock Screen is not always center aligned.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1840265/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
My system had the following packages upgraded: Upgrade: linux-headers-generic:amd64 (4.4.0.130.136, 4.4.0.131.137), linux-libc-dev:amd64 (4.4.0-130.156, 4.4.0-131.157), linux-image- generic:amd64 (4.4.0.130.136, 4.4.0.131.137), linux-generic:amd64 (4.4.0.130.136, 4.4.0.131.137) After that, there were errors again whenever I did `sudo apt update`. I opened `/var/cache/app-info/xmls/fwupd.xml` as `sudo`, went to line 256 and changed symbol `&` to ``, saved the changes, and ran command `sudo appstreamcli refresh --force`. Thereafter, no errors appeared during `sudo apt update`. W/o running command `sudo appstreamcli refresh --force` the error persisted. Hope this finding will be helpful to others in the same situation. -- 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/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically
I am encountering the same after sudo apt update. . AppStream system cache was updated, but problems were found: Metadata files have errors: /var/cache/app-info/xmls/fwupd.xml Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi' E: Sub-process returned an error code After reading the solution from https://askubuntu.com/a/1053844/541417, I did the following: 1. Backed up `fwupd.xml` and `50appstream`. 2. Performed the procedure mentioned in the link. I found the above mentioned errors disappeared during `sudo apt update` (tested for a few reboots). 3. I reinserted `50appstream` to it's original location, ran `sudo appstreamcli refresh --force` followed by `sudo apt update`; no error msg appeared. 4. After reinserting `fwupd.xml` to its original location, and running `sudo appstreamcli refresh --force` followed by `sudo apt update`, I found the above mentioned error reappearing. Specifically, `AppStream system cache was updated, but problems were found: Metadata files have errors: /var/cache/app-info/xmls/fwupd.xml.` So `fwupd.xml` really caused the error. Opening the file, the document mentioned the error was in line 265. Reading https://askubuntu.com/a/1053018/541417 and https://github.com/hughsie /8bitdo-firmware/commit/7b8eff0c8bb75336c6fd8aca13f9f5093abc5fd7#diff- 81541301f84363c9ec1c910b8b45cdb8R32. I concluded the issue is really caused by the typo in line 265 of `fwupd.xml`. Need to change to . That is symbol `&` should change to ``. Then save the file. After this fix, when I run 'sudo apt update', every thing works again. -- 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/1644498 Title: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1644498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1400470] Re: cannot download photos using shotwell via usb
I see the following message from Shotwell 0.22.0 in Ubuntu 16.04 every time a iPhone4s is plugged in to my computer usb: Shotwell Unable to fetch previews from the camera: Could not claim the USB device (-53) I have to click "Ok" to remove this message before I can access Shotwell. This warning has always appeared for a few years. Annoying. It will be great that this warning be removed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
It's coming to a year since I reported this issue. Below are the messages plaguing my syslog when Nautilus is started and when I press the items on the left are pressed. The look to be the same issues. I am using: kernel 4.4.0-64-generic nautilus 1:3.18.4.is.3.14.3-0ubuntu5. libglib-perl 3:1.320-2 libglib2.0-0:amd64 2.48.2-0ubuntu1 Can an importance be defined and someone fix them? Mar 12 22:14:46 Eliot gnome-session[2264]: message repeated 5 times: [ (nautilus:2558): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed] Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GObject-WARNING **: invalid (NULL) pointer instance Mar 12 22:15:05 Eliot gnome-session[2264]: (nautilus:26639): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Mar 12 22:15:05 Eliot dbus[1432]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Mar 12 22:15:05 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed Mar 12 22:15:05 Eliot systemd[1]: Starting Hostname Service... Mar 12 22:15:05 Eliot dbus[1432]: [system] Successfully activated service 'org.freedesktop.hostname1' Mar 12 22:15:05 Eliot systemd[1]: Started Hostname Service. Mar 12 22:15:13 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed Mar 12 22:15:15 Eliot gnome-session[2264]: message repeated 2 times: [ ** (nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed] Mar 12 22:15:16 Eliot gnome-session[2264]: ** (nautilus:2558): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed -- 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/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1575484] Re: "Set document metadata failed"
(gedit:3616): Gtk-WARNING **: Theme parsing error: gtk.css:4:12: 'min- height' is not a valid property name (gedit:3616): Gtk-WARNING **: Theme parsing error: gtk.css:10:12: 'min- height' is not a valid property name (gedit:3616): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (gedit:3616): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-enabled not supported ** (gedit:3616): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported ** (gedit:3616): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported In Ubuntu 16.04, First 2 warning/error --- appears when gedit starts. 3rd warning/error --- don't know the reason Last 3 warnings --- appears when save button was pressed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1575484 Title: "Set document metadata failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1575484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1661305] [NEW] Many Gtk-CRITICAL and GLib-GIO-CRITICAL failures in syslog during startup and shutdown of nautilus
Public bug reported: I have this installed: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 Is there a way to resolve these many critical failure messages by nautilus. I get them whenever I start or close nautilus. See below: Feb 2 23:41:59 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed Feb 2 23:41:59 Eliot gnome-session[2247]: message repeated 5 times: [ (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed] Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GObject-WARNING **: invalid (NULL) pointer instance Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Feb 2 23:42:17 Eliot dbus[1469]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Feb 2 23:42:17 Eliot systemd[1]: Starting Hostname Service... Feb 2 23:42:17 Eliot gnome-session[2247]: ** (nautilus:2465): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed Feb 2 23:42:17 Eliot dbus[1469]: [system] Successfully activated service 'org.freedesktop.hostname1' Feb 2 23:42:17 Eliot systemd[1]: Started Hostname Service. Feb 2 23:43:28 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed I also get many other failure messages in syslogs just by clicking different parts of nautilus. For example: Feb 2 23:41:59 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed Feb 2 23:41:59 Eliot gnome-session[2247]: message repeated 5 times: [ (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed] Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GObject-WARNING **: invalid (NULL) pointer instance Feb 2 23:42:17 Eliot gnome-session[2247]: (nautilus:7279): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Feb 2 23:42:17 Eliot gnome-session[2247]: ** (nautilus:2465): CRITICAL **: nautilus_menu_provider_get_background_items: assertion 'NAUTILUS_IS_MENU_PROVIDER (provider)' failed Feb 2 23:43:28 Eliot gnome-session[2247]: (nautilus:2465): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed ** Affects: nautilus (Ubuntu) Importance: Undecided Status: 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/1661305 Title: Many Gtk-CRITICAL and GLib-GIO-CRITICAL failures in syslog during startup and shutdown of nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1661305/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1641417] [NEW] Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.
Public bug reported: Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via gphoto2, where access is limited to viewing and copying photos and videos. The 2nd connection that is mounted via afc fail to work, hence other folders in iPhone are not accessible. Action 2: Unplugged and re-plugged iPhone 4 to the workstation. Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount point appear. Checks and Remedy used: 1. "ideviceinfo" and lsusb command show iPhone 4 is connected. 2. "idevicepair validate" command shows "SUCCESS: Validated pairing with device [UDID]" 3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in Nautilus as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 appears and are accessible. I believe the 1st mounting of iPhone 4 on Nautilus is due to the "gvfs- backends" package. W/o it, auto detection/connection of iPhone 4 would not occur and appear in Nautilus. However, the afc mount failed to work The 2nd mounting is caused by ifuse. This works perfectly but requires manual mounting and unmounting. Questions: 1. How to overcome issues/failures mentioned in Result 1 & 2? 2. Ideally, i would like the automatic detection-connection between Ubuntu and iPhone to work. If not, is there a way to automate connection via ifuse? System and package info: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial $ uname -or 4.4.0-47-generic GNU/Linux $ dpkg -l | grep iPhone ii ifuse1.1.2-0.1build3 amd64 FUSE module for iPhone and iPod Touch devices ii libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 amd64 Library for communicating with iPhone and iPod Touch devices ii libimobiledevice6:amd64 1.2.0+dfsg-3~ubuntu0.2 amd64 Library for communicating with the iPhone and iPod Touch ii libusbmuxd-tools 1.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - tools ii libusbmuxd4:amd641.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - library ii usbmuxd 1.1.0-2 amd64 USB multiplexor daemon for iPhone and iPod Touch devices $ dpkg -l | grep libusb ii libgusb2:amd64 0.2.9-0ubuntu1 amd64 GLib wrapper around libusb1 ii libusb-0.1-4:amd64 2:0.1.12-28 amd64 userspace USB programming library ii libusb-1.0-0:amd64 2:1.0.20-1 amd64 userspace USB programming library ii libusb-1.0-0:i3862:1.0.20-1 i386userspace USB programming library ii libusbmuxd-tools 1.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - tools ii libusbmuxd4:amd641.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - library ii libusbredirhost1:amd64 0.7.1-1 amd64 Implementing the usb-host (*) side of a usbredir connection (runtime) ii libusbredirparser1:amd64 0.7.1-1 amd64 Parser for the usbredir protocol (runtime) $ dpkg -l | grep gvfs ii gvfs:amd64 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - GIO module ii gvfs-backends 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - backends ii gvfs-bin1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - binaries ii gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual filesystem - common data files ii gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - servers ii gvfs-fuse 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - fuse server ii gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - private libraries ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1641417 Title: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1641417/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1583403] [NEW] gnome-software Button widget status do not correctly reflect updated status and generates a lot of Gs-WARNING in syslog
Public bug reported: $ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 $ apt-cache policy gnome-session gnome-session: Installed: 3.18.1.2-1ubuntu1 Candidate: 3.18.1.2-1ubuntu1 Version table: *** 3.18.1.2-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status Problems & Actions: - I noticed that after removing an app, the status button of the App do not correctly reflect the updated status. Neither is the removed App removed from the Installed tab immediately after a removal. - I notice a lot failures and warnings in my syslog within just 10 mins of using gnome-software. - I hope these info can help figure out the issues and provide a bug fix soon. ++ $ cat /var/log/syslog | grep gnome-software May 19 08:13:03 Eliot gnome-session[1940]: (gnome-software:2387): Gtk- CRITICAL **: gtk_widget_draw: assertion '!widget->priv->alloc_needed' failed May 19 09:51:43 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered May 19 09:51:43 Eliot gnome-session[1880]: message repeated 3 times: [ (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered] May 19 09:51:44 Eliot gnome-session[1880]: (gnome-software:2309): GsPlugin-WARNING **: failed to load stock icon gnome-volume-control: Icon 'gnome-volume-control' not present in theme (null) May 19 09:51:44 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered May 19 09:51:44 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered May 19 09:51:44 Eliot gnome-session[1880]: (gnome-software:2309): GsPlugin-WARNING **: failed to load stock icon gnome-volume-control: Icon 'gnome-volume-control' not present in theme (null) May 19 09:51:45 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered May 19 09:51:49 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered May 19 09:52:10 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered May 19 09:52:10 Eliot gnome-session[1880]: (gnome-software:2309): GsPlugin-WARNING **: failed to load stock icon gnome-volume-control: Icon 'gnome-volume-control' not present in theme (null) May 19 09:52:10 Eliot gnome-session[1880]: (gnome-software:2309): GsPlugin-WARNING **: failed to load stock icon gnome-volume-control: Icon 'gnome-volume-control' not present in theme (null) May 19 09:52:11 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered May 19 09:52:11 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.packagekit.trigger-offline-update is not registered May 19 09:52:12 Eliot gnome-session[1880]: (gnome-software:2309): As-WARNING **: failed to rescan: Failed to parse /usr/share/applications/bamf-2.index file: cannot process file of type text/plain May 19 09:52:15 Eliot gnome-session[1880]: (gnome-software:2309): Gs-WARNING **: Failed to create permission org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action
[Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
Clarification on the above mentioned failures observed during bootup (see below for syslog). The same gnome-session process, in this case [1940], appears to trigger 16 GLib-GObject-CRITICAL failures and 1 Gtk- CRITICAL failure. I have not found a way to resolve them. Pls help. $ cat /var/log/syslog | grep fail May 19 08:13:03 Eliot gnome-session[1940]: (gnome-software:2387): Gtk- CRITICAL **: gtk_widget_draw: assertion '!widget->priv->alloc_needed' failed May 19 08:16:22 Eliot gnome-session[1940]: gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session[1940]: gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session[1940]: gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session[1940]: gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session[1940]: gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session[1940]: gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session[1940]: gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session[1940]: gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 08:16:22 Eliot gnome-session-binary[1940]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed -- 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/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup
** Summary changed: - GLib-GObject-CRITICAL failures by Nautilus in Ubuntu 16.04 + GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup -- 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/1582496 Title: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573052] Re: [packaging] gnome-software provides a broken symlink of /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so on Ubuntu 16.04
I also have the same failure notice in my syslog. May 18 10:08:28 Eliot gnome-session[1871]: (gnome-software:2295): Gs- WARNING **: failed to open plugin /usr/lib/gs- plugins-9/libgs_plugin_xdg_app_reviews.so: /usr/lib/gs- plugins-9/libgs_plugin_xdg_app_reviews.so: cannot open shared object file: No such file or directory Action taken: $ cd /usr/lib/gs-plugins-9 $ ls -la Found that the link is broken(the link is in red colour). Neither can I find the filelibgs_plugin_xdg_app_reviews.so.0.0.0 lrwxrwxrwx 1 root root37 Apr 28 16:40 libgs_plugin_xdg_app_reviews.so -> libgs_plugin_xdg_app_reviews.so.0.0.0 Looking forward to receiving this bug fix. -- 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/1573052 Title: [packaging] gnome-software provides a broken symlink of /usr/lib/gs- plugins-9/libgs_plugin_xdg_app_reviews.so on Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1573052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1582496] [NEW] GLib-GObject-CRITICAL failures by Nautilus in Ubuntu 16.04
Public bug reported: I submitted this question a week but did not receive an answer or advice to solving them. https://answers.launchpad.net/ubuntu/+source/gnome- session/+question/293479 These failures are still plaguing my syslog every time I activate Nautilus. Appreciate help to resolve these failures. Earlier question After a recent updating, I notice these failures in the systemlogs. May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: (zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed May 9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed May 9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed The last three failures appears whenever I activate nautilus. Nautilus will appear and work as usual. How can I resolve these failure notices? Thanks in advance. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- 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/1582496 Title: GLib-GObject-CRITICAL failures by Nautilus in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1582496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1575484] Re: "Set document metadata failed"
I have similar issue. My warning msgs are shown below. The lower two msgs appear when i click save on gedit. (gedit:2335): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (gedit:2335): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-enabled not supported ** (gedit:2335): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1575484 Title: "Set document metadata failed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1575484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
