[Bug 967397] Re: GNOME Shell suboptimal performance
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/967397 Title: GNOME Shell suboptimal performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/967397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 871133] Re: Volume Step not changeable in Unity and GNOME desktops
** Changed in: gnome-settings-daemon Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/871133 Title: Volume Step not changeable in Unity and GNOME desktops To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704520] gnome-shell crashed with signal 5 in _XIOError()
StacktraceTop: x_io_error () from /tmp/apport_sandbox_t7SnHs/usr/lib/i386-linux-gnu/libmutter-0.so.0 _XIOError (dpy=0x80d0c908) at ../../src/XlibInt.c:1469 _XEventsQueued (dpy=0x80d0c908, mode=2) at ../../src/xcb_io.c:352 XPending (dpy=0x80d0c908) at ../../src/Pending.c:55 gdk_event_source_prepare () from /tmp/apport_sandbox_t7SnHs/usr/lib/i386-linux-gnu/libgdk-3.so.0 -- 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/1704520 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704520] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1704520/+attachment/4914950/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1704520/+attachment/4914938/+files/CoreDump.gz ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-i386-retrace -- 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/1704520 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704520] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1704520/+attachment/4914948/+files/Stacktrace.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/1704520 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704520] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1704520/+attachment/4914949/+files/StacktraceSource.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/1704520 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704520] [NEW] gnome-shell crashed with signal 5 in _XIOError()
Public bug reported: Fault notice appeared before ubuntu update; submission rejected. Same fault notice appeared after daily ubuntu update at approximately 2045 14July2017, zone -7. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic i686 ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Jul 14 20:36:20 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-13 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170426) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libmutter-0.so.0 _XIOError () from /usr/lib/i386-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6 XPending () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash artful i386 need-i386-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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1704520 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1588150] Re: Remove webkitgtk from archive
https://launchpad.net/ubuntu/+source/gtkpod/2.1.5-6 https://launchpad.net/ubuntu/+source/maildir-utils/0.9.18-2 ** Changed in: gtkpod (Ubuntu) Status: Triaged => Fix Released ** Changed in: maildir-utils (Ubuntu) Status: Triaged => Fix Released ** Changed in: birdfont (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1588150 Title: Remove webkitgtk from archive To manage notifications about this bug go to: https://bugs.launchpad.net/bijiben/+bug/1588150/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 391755] Re: Nautilus leave "(invalid encoding)" when renaming
** Changed in: nautilus 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/391755 Title: Nautilus leave "(invalid encoding)" when renaming To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/391755/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
I can confirm that removing the dbus-user-session and reverting a workaround (calling the gnome-keyring-daemon --replace --foreground) solved the issue. There was no xdg-desktop-portal or xdg-desktop-portal- gtk packages in my case. I suppose the dbus-user-session was installed with the flatpak. Ubuntu 16.04.2 LTS -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704492] [NEW] Prebase vowels not moved to before consonants joined by virama
Public bug reported: This bug was present in the implementation of USE up to Version 1.1.2 of HarfBuzz - https://github.com/behdad/harfbuzz/issues/180 records problem and fix in Version 1.1.3. The bug also affects the much-afflicted Tai Tham script, e.g. in the word ᩉ᩠ᩅᩯᩁ /wɛːn/ 'ring (n.)'. Unfortunately, LTS Ubuntu release 16.04 is still at Version 1.0.1 - there are no backports from Yakkety (Harfbuzz 1.2.7) or Zesty (Harfbuzz 1.4.2). Potentially unsafe work-arounds include building HarfBuzz (e.g. Version 1.4.6) and replacing the sharable object libharfbuzz.so.0 with a user- generated sharable object. It is possible to backport from Yakkety oneself using the Firefox example in "Recommended alternative to pinning" at https://help.ubuntu.com/community/PinningHowto. Note that the final command is sudo apt-get -b source -t yakkety harfbuzz One then installs the corrected object by means of the command sudo dpkg -i libharfbuzz0b_1.2.7-1_i386.deb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libharfbuzz0b 1.0.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-102.149-generic 3.13.11-ckt39 Uname: Linux 3.13.0-102-generic i686 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 CurrentDesktop: Unity Date: Fri Jul 14 22:21:04 2017 InstallationDate: Installed on 2010-12-28 (2390 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: harfbuzz UpgradeStatus: Upgraded to xenial on 2016-11-19 (237 days ago) ** Affects: harfbuzz (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to harfbuzz in Ubuntu. https://bugs.launchpad.net/bugs/1704492 Title: Prebase vowels not moved to before consonants joined by virama To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/1704492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Seems to me like `dbus-user-session` was the real culprit causing all the trouble. I got it installed with anbox and that is when the problem started. I got my keyring daemon to correctly start, the Login keyring to unlock automatically while still being encrypted with my account password again this way: - Purge `dbus-user-session`, e.g. by running `sudo apt purge dbus-user-session` - Revert files in `/etc/pam.d` back to their original state. I had commented out a line in `/etc/pam.d/lightdm` to work around the `gnome-keyring-daemon` not starting in the correct mode issue. - Set my account password on the Login keyring again (using seahorse). I had removed the password and left the keyring unprotected to avoid being asked for the password each session. - Set my user account password to something completely different and then back to my normal password using the `passwd` command. Before doing this, it seemed like the Login keyring and account password weren't yet synced correctly despite being equal. When I rebooted before the `passwd`, it still asked for the keyring password to be entered manually. - Reboot. On my next login, it asked for the Login keyring password to be entered manually one last time, but offered a checkbox to enable unlocking that keyring automatically on boot, which I checked. After this procedure, my system seems to be as good as new again. Running 16.04 with vanilla Unity desktop and lightdm btw. -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
All I have running is /usr/bin/gnome-keyring-daemon --daemonize --login The files in your /etc/xdg/autostart look fine Just need to make sure you're not starting gnome-keyring anywhere else. -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
I added a bad command line into the GUI and .config/autostart file to be sure that it could not run the command to start the daemon. upon reboot I still see two daemons running, one with my username as owner and one with lightdm as owner. I'm still getting the same behavior of slow launch of terminal and extremely long load of chrome if I don't run the workaround command gnome-keyring-daemon --replace and enter my password. After logging in for the second time, the daemon owned by lightdm exits leaving only one daemon running owned by my user. -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Thank you, @leftyfb.
I'm seeing some strange behavior when deleting the files in
~/.config/autostart/
I can delete the file. If I open the GUI for startup Applications it
has a line for gnome-keyring-daemon --start --components=ssh which seems
unrelated to the text file in ~/.config/autostart. If I delete both the
GUI entry and the text file and reboot, I get the same behaviour and
have to run gnome-keyring-daemon --replace and enter my password. I
also have to open the HUD to get the password prompt to show itself
otherwise nothing happens.
Also after reboot, the entry in the startup applications gui shows up
again even though the text file is not there. Upon closing the GUI, the
text file appears again.
As for the rest of the system,
In /etc/xdg/autostart I have three gnome-keyring-daemon files for secrets, ssh,
and pkcs11. These files have been here since November 2015.
They contain:
Exec=/usr/bin/gnome-keyring-daemon --start --components={{one of
secrets, ssh, or pkcs11}}
the rest of these three files are the same and contain the following
lines:
OnlyShowIn=GNOME;Unity;MATE;
X-GNOME-Autostart-Phase=Initialization
X-GNOME-AutoRestart=false
X-GNOME-Autostart-Notify=true
X-GNOME-Bugzilla-Bugzilla=GNOME
X-GNOME-Bugzilla-Product=gnome-keyring
X-GNOME-Bugzilla-Component=general
X-GNOME-Bugzilla-Version=3.18.3
NoDisplay=true
--
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/1689825
Title:
gnome-keyring not unlocked on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1650395] Re: Large grey border around gnome-terminal shadows when transparency is enabled (wayland)
This bug was fixed in the package gnome-terminal - 3.24.2-0ubuntu4
---
gnome-terminal (3.24.2-0ubuntu4) artful; urgency=medium
*
debian/patches/0001-screen-window-Extra-padding-around-transparent-termi.patch:
Fix transparency on Wayland. Patch by Owen Taylor, via Debarshi Ray @
Fedora, thanks! (LP: #1650395)
* Rearrange the patches a bit.
* debian/control{,.in}: Fix Vcs-Svn to Vcs-Bzr
-- Iain Lane Thu, 13 Jul 2017 16:07:50 +0100
** Changed in: gnome-terminal (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1650395
Title:
Large grey border around gnome-terminal shadows when transparency is
enabled (wayland)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1650395/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
@antonioshadji I had to undo the workarounds in order for it to stop asking for passwords at login: In /etc/xdg/autostart/gnome-keyring-ssh.desktop I originally replaced: Exec=/usr/bin/gnome-keyring-daemon --start --components=ssh with #Exec=/usr/bin/gnome-keyring-daemon --daemonize --components=ssh Some people put a new gnome-keyring startup file in ~/.config/autostart/ Remove that. Then a complete reboot. -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704050] Re: [regression] Can't log in to Wayland Gnome sessions at all
** Changed in: gdm Status: Unknown => Confirmed ** Changed in: gdm Importance: Unknown => Medium -- 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/1704050 Title: [regression] Can't log in to Wayland Gnome sessions at all To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1704050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Removing flatpak/dbus-user-session did not change anything for me on 16.04.2. dbus-user-session was first installed on May 8th 2017 in conjunction with an upgrade of flatpak (and other software) as can be seen in attached apt history log entry. flatpak list org.pitivi.Pitivi/x86_64/stable org.gnome.Platform/x86_64/3.22 user,runtime flatpak --user uninstall org.pitivi.Pitivi flatpak --user uninstall org.gnome.Platform apt-get purge flatpak autoremoved libostree-1-1 xdg-desktop-portal xdg-desktop-portal-gtk apt-get purge dbus-user-session reboot and check for running gnome-keyring-daemon $ psa | grep gnome-keyring-daemon antonios 4592 0.0 0.0 14524 980 pts/17 S+ 13:58 0:00 | \_ grep gnome-keyring-daemon lightdm 1589 0.0 0.0 123296 3148 ?Sl 13:56 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login antonios 2652 0.1 0.2 232048 34776 ?SLl 13:57 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login the lightdm owned process stopped running after a few minutes. to workaround, I still have to run `gnome-keyring-daemon --replace' ** Attachment added: "I think the issue started after this upgrade" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+attachment/4914766/+files/upgrade-issue-begin.txt -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704438] [NEW] system freezes on IPv6 manual configuration
Public bug reported: I have the weirdest network bug ever... I'm using Gnome-desktop (not unity). When configuring IPv6 in the network preferences, if I set address to manual and enter my IPv6, its /64 prefix, and its gateway, the system FREEZES if something like firefox tries to make any IPv6 access. screen freezes, no ping, no console, good to be hard rebooted. This doesn't happen in automatic where I get a automated IPv6 from router announcement, and I can add my address with > ifconfig eth0 inet6 add myip/64 without any problem. Ubuntu 17.04 fresh install, I had the same on a upgraded install ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-control-center 1:3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jul 15 01:45:25 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-14 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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 zesty -- 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/1704438 Title: system freezes on IPv6 manual configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1704438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704427] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 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 #1688721, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 Packages that trigger multiple debconf prompts fail to install -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1704427 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1704427/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704427] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: I actually don't know WHAT happened, the error popped up after I installed this: [Attached] ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jul 14 17:08:26 2017 DpkgHistoryLog: Start-Date: 2017-07-14 16:54:15 Commandline: aptdaemon role='role-install-file' sender=':1.84' Install: gconf2-common:amd64 (3.2.6-3ubuntu7, automatic), libindicator7:amd64 (16.10.0+16.10.20160913-0ubuntu1, automatic), gconf-service:amd64 (3.2.6-3ubuntu7, automatic), gconf-service-backend:amd64 (3.2.6-3ubuntu7, automatic), libappindicator1:amd64 (12.10.1+17.04.20170215-0ubuntu1, automatic), libgconf-2-4:amd64 (3.2.6-3ubuntu7, automatic) ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-29 (45 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty ** Attachment added: "After installing this package sucessfully, I was notified of the errir," https://bugs.launchpad.net/bugs/1704427/+attachment/4914723/+files/discord-ptb-0.0.1.deb -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1704427 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1704427/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1130137] Re: Better sound settings icons
** Changed in: gnome-control-center Status: Unknown => Confirmed ** Changed in: gnome-control-center Importance: Unknown => Medium -- 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/1130137 Title: Better sound settings icons To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1130137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704422] [NEW] systemd-resolved keeps swapping DNS servers and breaking name resolution
Public bug reported: Hi, I think the name is self explanatory, let me paste some logs of what does my syslog look like at any given time: https://paste.ubuntu.com/25089356/ Jul 14 16:49:23 Tuxedo systemd-resolved[1120]: Using system hostname 'Tuxedo'. Jul 14 16:49:52 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 8.8.8.8. Jul 14 16:50:17 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 8.8.4.4. Jul 14 16:50:17 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 2001:4860:4860::. Jul 14 16:50:17 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 2001:4860:4860::8844. Jul 14 16:50:18 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 8.8.8.8. Jul 14 16:50:18 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 8.8.4.4. Jul 14 16:50:18 Tuxedo systemd-resolved[1120]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 8.8.4.4. Jul 14 16:50:18 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 2001:4860:4860::. Jul 14 16:50:19 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 2001:4860:4860::8844. (...) Jul 14 16:50:43 Tuxedo systemd-resolved[1120]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 78.46.223.24. Jul 14 16:50:43 Tuxedo systemd-resolved[1120]: Switching to DNS server 162.242.211.137 for interface tun0. Jul 14 16:50:44 Tuxedo systemd-resolved[1120]: Switching to DNS server 78.46.223.24 for interface tun0. Jul 14 16:50:45 Tuxedo systemd-resolved[1120]: Switching to DNS server 162.242.211.137 for interface tun0. Jul 14 16:50:48 Tuxedo systemd-resolved[1120]: Switching to DNS server 78.46.223.24 for interface tun0. Jul 14 16:50:48 Tuxedo systemd-resolved[1120]: Switching to DNS server 162.242.211.137 for interface tun0. Jul 14 16:50:49 Tuxedo systemd-resolved[1120]: Switching to DNS server 78.46.223.24 for interface tun0. Jul 14 16:50:50 Tuxedo systemd-resolved[1120]: Switching to DNS server 162.242.211.137 for interface tun0. Jul 14 16:50:50 Tuxedo systemd-resolved[1120]: Switching to DNS server 78.46.223.24 for interface tun0. This happens both over the VPN and without (only than without the VPN I don't get the log messages, just a huge packet loss): tux@Tuxedo:~$ ping google.es ^T192PING google.es (216.58.201.131) 56(84) bytes of data. 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=1 ttl=55 time=26.9 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=5 ttl=55 time=19.5 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=9 ttl=55 time=24.4 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=10 ttl=55 time=22.3 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=14 ttl=55 time=20.5 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=20 ttl=55 time=20.7 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=22 ttl=55 time=26.4 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=24 ttl=55 time=29.2 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=25 ttl=55 time=20.1 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=26 ttl=55 time=22.7 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=27 ttl=55 time=21.0 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=28 ttl=55 time=30.4 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=29 ttl=55 time=23.2 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=30 ttl=55 time=29.1 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=37 ttl=55 time=30.1 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=40 ttl=55 time=24.8 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=43 ttl=55 time=23.3 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=45 ttl=55 time=22.9 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=46 ttl=55 time=21.9 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=53 ttl=55 time=23.7 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=61 ttl=55 time=21.1 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=62 ttl=55 time=19.3 ms ^C --- google.es ping statistics --- 62 packets transmitted, 22 received, 64% packet loss, time 61869ms rtt min/avg/max/mdev = 19.394/23.851/30.417/3.404 ms Let me know if I can provide any other details. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1704422 Title: systemd-resolved keeps swapping DNS servers and breaking name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704422/+subscriptions --
[Bug 1413117] Re: icon captions info on desktop don't disappear
Hi Sebastien, the original issue was reported against "nautilus 3.10" which can't be selected on the upstream bug tracker (only >=3.14), and in the newer version 3.18 I cannot reproduce it. What do you suggest to do? -- 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/1413117 Title: icon captions info on desktop don't disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1413117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Removing dbus-user-session resolved my issue. It got added when I temporarily installed anbox. There was no xdg-desktop-portal or xdg- desktop-portal-gtk installed or available. -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704397] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 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 #1688721, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 Packages that trigger multiple debconf prompts fail to install -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1704397 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1704397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1614194] Re: epiphany's info dialog contain no notion of its name
Marking "Ubuntu" as being invalid as correct package already added. ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1614194 Title: epiphany's info dialog contain no notion of its name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1614194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704397] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: generated by the system ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 Date: Sat Jul 8 09:18:57 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-26 (17 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1704397 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1704397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1697882] Re: GDM should not allow X11 sessions when NVIDIA's KMS is enabled
@Doug: we are going to leave PRIME systems alone in any case. This bug report is about non hybrid systems. You are using the intel GPU to drive the screen, and that is why X11 + KMS works for you. As far as I know, Wayland doesn't support that yet. -- 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/1697882 Title: GDM should not allow X11 sessions when NVIDIA's KMS is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1697882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1653367] Re: Ubuntu crashes at startup.
** Package changed: ubuntu => gnome-software (Ubuntu) -- 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/1653367 Title: Ubuntu crashes at startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1653367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1653367] [NEW] Ubuntu crashes at startup.
You have been subscribed to a public bug: Package is gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial- 0ubuntu1~16.04.1[origin: unknown] Title is gnome-software crashed with signal 5 in g_main_context_new() ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 [origin: unknown] ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Sat Dec 31 11:19:41 2016 InstallationDate: Installed on 2016-12-07 (24 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial -- Ubuntu crashes at startup. https://bugs.launchpad.net/bugs/1653367 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1696134] Re: Nautilus and Desktop unexpected behaviour
** Package changed: ubuntu => nautilus (Ubuntu) -- 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/1696134 Title: Nautilus and Desktop unexpected behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1696134/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Thanks all! I uninstalled my flatpak apps, flatpak, and dbus-user-session... then rebooted and all's well. Uninstalling with --purge seems to have taken care of the /etc file markuslet pointed to. $ flatpak list $ flatpak --system uninstall com.xamarin.MonoDevelop $ flatpak --system uninstall org.freedessktop.Platform $ sudo apt-get remove --purge dbus-user-session $ sudo apt-get remove --purge flatpak $ sudo apt-get autoremove $ sudo reboot -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1696134] [NEW] Nautilus and Desktop unexpected behaviour
You have been subscribed to a public bug: When I drag the cursor on the desktop there is some unexpected behaviour and the select marquee doesn't appear. This only happens sometimes. I recorded a screencast where you can see this happening. Here is a link to the video: https://www.dropbox.com/s/8mljcuffp71hf45/ubuntu-desktop-bug.mp4?dl=0 I'm using Ubuntu 16.04.2 LTS. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Nautilus and Desktop unexpected behaviour https://bugs.launchpad.net/bugs/1696134 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
The Status dropdown is for "Affects" and flatpak affects this issue (not that it's the sole culprit). ** Changed in: flatpak (Ubuntu) Status: Invalid => Confirmed ** Also affects: dbus Importance: Undecided Status: New -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Thanks for everyone who helped -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Finally, this fixed the problem. -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704002] Re: Missing icon for mono speakers
** Changed in: gnome-control-center Status: Unknown => Confirmed ** Changed in: gnome-control-center Importance: Unknown => Medium -- 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/1704002 Title: Missing icon for mono speakers To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1704002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
That finally solved it for me, thank you @Eberhard and @all for looking into this and sharing your insights! A few notes: * in addition, I manually deleted file /etc/X11/Xsession.d/20dbus_xdg- runtime which comes with package dbus-user-session (and is actually the only file of the package) but was not removed on uninstall (Idk whether this step is always neccessary) * logout/login was not sufficient to see this solved. Full reboot was required. -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704360] [NEW] Cannot resize window in gnome wayland session with mouse
Public bug reported: Running gnome-shell + wayland on ubuntu 17.04 here. If I have a "legacy" (X11) application, like firefox or xterm (running with Xwayland, I guess) I can resize its window normally, ie mouse shape changes into resize-signaling shape near the window borders and I can do the job. However pure-wayland clients, like gnome-terminal it simply does not work, which is very annoying no need to say. I can do the resize with eg ALT+right click and select "resize" but it's kinda more work to do a very simple task (and also it seems there is only horizontal OR vertical resize, not the both what I used to if I move the mouse near to the corner of the window). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 14 11:43:52 2017 DisplayManager: gdm3 InstallationDate: Installed on 2015-07-10 (734 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-shell UpgradeStatus: Upgraded to zesty on 2017-06-20 (23 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- 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/1704360 Title: Cannot resize window in gnome wayland session with mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1704360/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
I could work around this problem by uninstalling dbus-user-session (and its dependendants xdg-desktop-portal and xdg-desktop-portal-gtk). Those packages came in through flatpak. Thanks to Olaf who brought me on the right track (https://forum.ubuntuusers.de/topic/gnome-keyring-daemon-doppelt/) -- 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/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703640] Re: nplan and libnss-resolve should be in same dependency
** Also affects: dbus (Ubuntu) Importance: Undecided Status: New ** Changed in: dbus (Ubuntu) Status: New => Confirmed ** Changed in: dbus (Ubuntu) Importance: Undecided => Critical ** Changed in: dbus (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1703640 Title: nplan and libnss-resolve should be in same dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1703640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1454603] Re: [systemd] Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8126
I can confirm that this issue is not fixed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1454603 Title: [systemd] Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1454603/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1693724] Re: Context menus have no animation/fade-in under Gnome Shell
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Low -- 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/1693724 Title: Context menus have no animation/fade-in under Gnome Shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693724/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704295] [NEW] Gnome Software titlebar is too thin during startup under Ambiance
Public bug reported: Gnome Software titlebar is too thin during startup under Ambiance ** Affects: gnome-software (Ubuntu) Importance: Medium Status: New ** Affects: ubuntu-themes (Ubuntu) Importance: Medium Status: New ** Tags: gnome-17.10 visual-quality ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags added: gnome-17.10 ** Tags added: visual-quality -- 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/1704295 Title: Gnome Software titlebar is too thin during startup under Ambiance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1704295] Re: Gnome Software titlebar is too thin during startup under Ambiance
Although closing the app and reopening it often skips the thin titlebars phase so it's not easy to reproduce on demand... ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium -- 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/1704295 Title: Gnome Software titlebar is too thin during startup under Ambiance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704295/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
