[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
@Brian The issue is gone after upgrading gnome-settings-daemon to 3.28.1-0ubuntu1.1. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Sounds like a fix, thanks. Fix committed upstream, scheduled for release in gnome-shell 3.30.2 or 3.31.x, whichever happens first. ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 + + --- + I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), has been already finalized. Impossible to set any property to it. May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) gnome-shell: Installed: 3.28.1-0ubuntu2 Candidate: 3.28.1-0ubuntu2 Version table: *** 3.28.1-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic There's similar bug that should be related to this one https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix didn't work for me. - --- + --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes GsettingsChanges: - b'org.gnome.shell' b'enabled-extensions' b"['pidgin-persistent-notificat...@ikkoku.de']" - b'org.gnome.shell'
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
With some digging on the gnome gitlab i've actually found what looks like an existing bug report: https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 Looks like a fix was merged https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243 a week ago. -- 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/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789887] Re: Dragging and dropping a folder onto the "New bookmark" item in the bookmark section has no effect
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1789887 Title: Dragging and dropping a folder onto the "New bookmark" item in the bookmark section has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1789887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800492] Re: Screen seems to think it is still locked after I've unlocked it
*** This bug is a duplicate of bug 1800475 *** https://bugs.launchpad.net/bugs/1800475 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1800475, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1800475 double unlock required to unlock the screen -- 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/1800492 Title: Screen seems to think it is still locked after I've unlocked it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800475] Re: double unlock required to unlock the screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1800475 Title: double unlock required to unlock the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800477] Re: Extensions are disabled after unlocking the screen
Related to bug 1796265? -- 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/1800477 Title: Extensions are disabled after unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800464] Re: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1800464 Title: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800475] Re: double unlock required to unlock the screen
Sounds like it could be related to bug 1799293. -- 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/1800475 Title: double unlock required to unlock the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
** Description changed:
= Problem =
It is too easy to make a system unusable.
+
+ https://gitlab.gnome.org/GNOME/gdm/issues/438
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to the login screen with no
indication of what went wrong.
== Session "dead" ==
- chmod 444 ~/.cache
- chmod 000 ~/.config
- chmod 444 ~
- chmod 000 ~
In this scenario, the system just freezes: the cursor is unresponsive
and users will be reaching for the power button.
= Observation =
These scenarios would all be caused by human error.
However, clearly it is possible for the system to detect such issues and
either alert the user to the problem or simply just fix the problem.
This does not happen in Ubuntu 18.04 LTS though.
= Idea =
Have the display manager call a utility prior to executing the users
preferred session. This utility -- which could be a simple shell script
I think ("friendly-session-fixer" maybe? :) -- would do one or both of
the following:
- Perform checks for the issues outlined above warn the user graphically
if any are found.
- Fix any issues found to allow the user to login.
However they are treated, all issues should also be logged in the
journal (could be the user journal, but the system journal may be best
to allow admins to spot such issues being detected more easily?)
= Rationale =
1) All the problems above, although user-generated, are:
- trivially fixable.
- potentially very hard / impossible for a naeve user to debug and resolve.
2) By handling such errors, users won't have a bad experience of Linux
if they inadvertently perturb a critical file.
3) Users will not need to resort to a re-install (which I can imagine
some may have to given the current behaviour).
= Ideas for further checks =
- Check to ensure key files exist and if not, copy them in from /etc/skel/,
etc.
- Check to ensure users home directory is owned by them and not root, etc.
- If the home partition / disk is 100% full, the script could logrotate and
compress the contents of ~/.cache/ ?
= Notes =
You could argue that the session managers themselves should deal with these
issues. In some cases that may be a fair comment. However, by having a single
central check/fix script, the problems can be handled centrally without the
issue whereby some session managers tolerate certain scenarios whereas others
don't.
- ---
+ ---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-10-29 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: gdm3 3.28.0-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
- TERM=xterm-256color
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_GB.UTF-8
- SHELL=/bin/bash
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_GB.UTF-8
+ SHELL=/bin/bash
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: 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/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754864] Re: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04
The good news is that this now correctly installs themes when installing an app. Unfortunately for me test "2.4 Update an app in GNOME Software" from the flatpak test plan [0], fails for me with the package from proposed. After reverting to an older commit hash, then refreshing gnome-software it shows the update. But when I click "Update" the UI shows progress, hides the item and then it reappears again. Furthermore using the CLI you can see that the package hasn't been updated. So this change appears to be breaking an update. When running from the console I get "01:38:32:0760 Gs tried overwriting org.gnome.Recipes.desktop key flatpak::Commit from 6d5f7c35ff1f3fd449b2789324843a89140257bb3cdca468f83a65162b177fa0 to 1ac37481845c65857a64e8c0680bae137b0b56faaf6f11f3f0d415a3205bc1c2" and if i run in verbose mode I get this https://pastebin.ubuntu.com/p/r8pWhpmcG7/ Note flipping back to 3.28.1-0ubuntu4.18.04.4 it works again. Therefore I am going to have to mark this as verification-failed-bionic for now. $ apt-cache policy gnome-software-plugin-flatpak gnome-software-plugin-flatpak: Installed: 3.28.1-0ubuntu4.18.04.5 Candidate: 3.28.1-0ubuntu4.18.04.5 Version table: *** 3.28.1-0ubuntu4.18.04.5 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu4.18.04.4 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu4 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 0 - https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1754864 Title: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Andrew, or anyone else experiencing this in 18.10, please report the bug here: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new bug ID. -- 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/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: gvfs may crash when parsing non-valid UTF8 in autorun.inf
What does an autorun.inf file do? If an autorun.inf file can tell gvfs to execute something directly, then it's probably not too critical that a malicious one can cause memory errors in gvfs. It could probably just have an evil payload as a command. Thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798725] Re: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*=
This was fixed in upstream commit https://gitlab.gnome.org/GNOME/gvfs/commit/a23eb6f14eb3cffa1585d4e5e566f779337d1e04 Uncertain whether this qualifies as a security issue - there doesn't seem to be any real security impact from the bug - so unmarking this as a security issue now. ** Information type changed from Public Security to Public ** Summary changed: - Content "n\xff=" can crash libpcre when an application is matching the pattern \s*= + gvfs may crash when parsing non-valid UTF8 in autorun.inf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: gvfs may crash when parsing non-valid UTF8 in autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1798725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790609] Re: Update evince to 3.28.4
I'm a bit confused here. As I understand it this upload uses the build option --enable-ps something that was disabled by upstream due to an unknown (the ghostscript bug is still private) security issue with postscript files. Is this security issue really fixed in Ubuntu 18.04? If so please provide some evidence. Thanks! ** Changed in: evince (Ubuntu Bionic) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1790609 Title: Update evince to 3.28.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1790609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798470] Re: gnome-software can't handle composite CAB files
Hello Mario, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed-bionic -- 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/1798470 Title: gnome-software can't handle composite CAB files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798228] Re: Snap search results not in the same order as command line
Hello Robert, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-bionic -- 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/1798228 Title: Snap search results not in the same order as command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798228/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773207] Re: symbol lookup error: /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0: undefined symbol: sqlite3_bind_pointer
I had to uninstall sqlite-autoconf to solve the problem. -- 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/1773207 Title: symbol lookup error: /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker- data.so.0: undefined symbol: sqlite3_bind_pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1773207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754864] Re: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04
Hello AsciiWolf, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-software (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1754864 Title: Flatpak related refs are not installed when using GNOME Software on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754864/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
Hello Merlijn, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- 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/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800542] [NEW] OpenVPN connection not stable after upgrade to 18.10 (udp, ipv6)
Public bug reported: After upgrade to Ubuntu 18.10, my connection to my employer's VPN server has become unstable. The server provides both ipv4 and ipv6 endpoints. Since I have global ipv6 at home, my client defaults to connecting over ipv6. The connection consistently drops after only a few minutes of being connected. If I force the connection to use ipv4 (by hard-coding the host resolution in /etc/hosts), the connection is stable. If I use ipv6 and force proto-tcp=yes, the connection is stable. If I use the default ipv6 and udp, the connection is not stable. Using tcp for VPNs is suboptimal. Hard-coding addresses in /etc/hosts is suboptimal. This may be a bug in openvpn rather than in network-manager-openvpn, but I'm starting here. It's possible there are pathMTU issues involved, but I reproduced this same problem when I was on a different network from my home network (though I did not confirm, when I had access to this other network, that it was ipv6-enabled). I will work on getting more details about both sides of the network to try to debug this. ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1800542 Title: OpenVPN connection not stable after upgrade to 18.10 (udp, ipv6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1800542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
Hello ethan.hsieh, or anyone else affected, Accepted gnome-settings-daemon into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-settings-daemon/3.28.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-settings-daemon (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798399] Re: totem silently fails to create screenshot gallery
Hello George, or anyone else affected, Accepted totem into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/totem/3.26.2-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1798399 Title: totem silently fails to create screenshot gallery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799116] Re: KDE Connect Indicator does not install
** Package changed: python3.6 (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/1799116 Title: KDE Connect Indicator does not install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799116/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
I'm sorry, I no longer use Ubuntu on my machines. But I can confirm this happened to me when the lockscreen is active. -- 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/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799116] [NEW] KDE Connect Indicator does not install
You have been subscribed to a public bug: In the software Boutique, installing KDE Connect Indicator fails with the message "package does not exist". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: python3.6-minimal 3.6.7~rc1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Mon Oct 22 00:55:47 2018 ExecutablePath: /usr/bin/python3.6 InstallationDate: Installed on 2018-10-22 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 SourcePackage: python3.6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- KDE Connect Indicator does not install https://bugs.launchpad.net/bugs/1799116 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 1800500] Re: Default Crop mode is confusing
** Changed in: shotwell (Ubuntu) Status: New => Triaged ** Changed in: shotwell (Ubuntu) Importance: Undecided => Low -- 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/1800500 Title: Default Crop mode is confusing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1800500/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800500] [NEW] Default Crop mode is confusing
Public bug reported: >From https://gitlab.gnome.org/GNOME/shotwell/issues/68 Steps to reproduce: - Open an image in Shotwell with default config. - Select Crop tool - Select area to crop, try to drag crop area horizontally. What was actually happening Crop tool uses Square mode by default, which prevents horizontal adjustment. This is an astonishing behaviour. The expected behaviour When I crop an image, the crop tool uses Unconstrained mode by default. This is the sane default, found in every other image editor I have used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: shotwell 0.28.2-0ubuntu1 ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 12:11:45 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (46 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: shotwell UpgradeStatus: Upgraded to bionic on 2018-09-28 (30 days ago) ** Affects: shotwell (Ubuntu) Importance: Low Status: Triaged ** Tags: amd64 apport-bug bionic -- 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/1800500 Title: Default Crop mode is confusing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1800500/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756597] Re: Rhythmbox plugin "Song Lyrics" not working
rather https://gitlab.gnome.org/GNOME/rhythmbox/issues -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1756597 Title: Rhythmbox plugin "Song Lyrics" not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1756597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices
if that's still an issue for some configs on Ubuntu (GNOME) 18.04/18.10 the best would be to report it upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues -- 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/1753525 Title: Wacom tablet not recognized in Settings > Devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799935] Re: System settings window does not display on screen after moving the dockbar to Bottom
The same problem happens for the software updater as well. After moving the dockbar to the bottom the software updater window does not show up. But, it is shown in the dockbar I am unable to use the settings window to change the dockbar back to the "Left". This is really frustrating. Is there a workaround. -- 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/1799935 Title: System settings window does not display on screen after moving the dockbar to Bottom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1799935/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756597] Re: Rhythmbox plugin "Song Lyrics" not working
The issues are upstream ones and should be reported on https://gitlab.gnome.org/GNOME/gnome-control-center/issues ** Changed in: rhythmbox (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1756597 Title: Rhythmbox plugin "Song Lyrics" not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1756597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800492] [NEW] Screen seems to think it is still locked after I've unlocked it
Public bug reported: Sometimes in 18.10 when I unlock my screen (well, not actually "unlock", since I don't have the screensaver configured to lock, so more accurately, when I disable the screensaver), I end up on a screen which looks like the computer still sort of thinks the screensaver is activated. My regular background isn't there, my system tray app indicators are missing, and the system tray menu looks like the one that shows when the screensaver is activated, but at the same time, there's a launch tray at the left side of the screen, and the rest of the ornamentation that usually displays when the screensaver is activated is missing. See the attached screenshot. Nothing I do at this point seems to have any effect, e.g. I can't launch app windows from the tray. This particular time this happened that has prompted me to report it was when I was accessing my desktop remotely (that's how I got a screenshot), but I _think_ I've also seen it when walking up to my desk and turning off the screensaver locally by hitting the Enter key. I.e., I don't _think_ this bug is related to using a remote desktop, but I can't be 100% certain. If I do notice it again when I'm local I'll update this bug to confirm. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 11:26:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-01-16 (1017 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-20 (8 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T07:35:17.955033 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "desktop.png" https://bugs.launchpad.net/bugs/1800492/+attachment/5206780/+files/desktop.png -- 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/1800492 Title: Screen seems to think it is still locked after I've unlocked it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800492/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800477] Re: Extensions are disabled after unlocking the screen
journal of the session ** Attachment added: "journal.log.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+attachment/5206749/+files/journal.log.gz -- 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/1800477 Title: Extensions are disabled after unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800477] Re: Extensions are disabled after unlocking the screen
List of extensions installed on the system. ** Attachment added: "extensions.list" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+attachment/5206748/+files/extensions.list -- 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/1800477 Title: Extensions are disabled after unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800477] [NEW] Extensions are disabled after unlocking the screen
Public bug reported: Quite often all the extension (excepted the dock) are disabled after unlocking the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 15:00:52 2018 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1567 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-03-24 (218 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1800477 Title: Extensions are disabled after unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800475] [NEW] double unlock required to unlock the screen
Public bug reported: I have to unlock the screen twice to unlock the screen. On 1rst attempt I have a completely aubergine screen without any widget at all (no label, password field, buttons, ...) Then I have to lock the screen and unlock it again to display the usual screen and be able to log in. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 14:49:17 2018 InstallationDate: Installed on 2014-07-15 (1567 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gdm3 UpgradeStatus: Upgraded to cosmic on 2018-03-24 (218 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1800475 Title: double unlock required to unlock the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800475] Re: double unlock required to unlock the screen
journal from this session ** Attachment added: "journal.log.gz" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800475/+attachment/5206743/+files/journal.log.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1800475 Title: double unlock required to unlock the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800464] Re: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0
On a different Cosmic platform, the symptoms are a little bit different: "traps: gnome-shell general protection error:0 in libglib-2.0.so.0.5800.1" ... Oct 28 22:00:24 msi-ge60-ubuntu kernel: [ 77.307798] traps: gnome-shell[4865] general protection ip:7f7b32927c00 sp:7fff46026330 error:0 in libglib-2.0.so.0.5800.1[7f7b32907000+7d000] Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Oct 28 22:00:25 msi-ge60-ubuntu kernel: [ 77.469526] rfkill: input handler enabled Oct 28 22:00:25 msi-ge60-ubuntu gnome-session[4202]: gnome-session-binary[4202]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 28 22:00:25 msi-ge60-ubuntu gnome-session-binary[4202]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 28 22:00:25 msi-ge60-ubuntu gnome-session-binary[4202]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 28 22:00:25 msi-ge60-ubuntu pulseaudio[4495]: ICE default IO error handler doing an exit(), pid = 4495, errno = 11 Oct 28 22:00:25 msi-ge60-ubuntu kdeconnectd.desktop[4721]: ICE default IO error handler doing an exit(), pid = 4721, errno = 11 Oct 28 22:00:25 msi-ge60-ubuntu at-spi-bus-launcher[]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" -- 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/1800464 Title: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800464] [NEW] CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0
Public bug reported: Ubuntu 18.10 gnome-shell 3.30.1-2ubuntu1 libmozjs-60-0 60.2.3-1 >From /var/log/syslog: ... Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: g_dir_open_with_errno: assertion 'path != NULL' failed Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: JS WARNING: [resource:///org/gnome/shell/ui/status/system.js 268]: reference to undefined property "names" Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: JS ERROR: TypeError: app.app_info.get_icon(...).names is undefined#012_createSubMenu@resource:///org/gnome/shell/ui/status/system.js:268:33#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init@resource:///org/gnome/shell/ui/status/system.js:126:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_init@resource:///org/gnome/shell/ui/panel.js:721:24#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1132:25#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_updateBox@resource:///org/gnome/shell/ui/panel.js:1143:29#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_updatePanel@resource:///org/gnome/shell/ui/panel.js:1053:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init@resource:///org/gnome/shell/ui/panel.js:831:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012_initializeUI@resource:///org/gnome/shell/ui/main.js:187:13#012start@resource:///org/gnome/shell/ui/main.js:136:5#012@:1:31 Oct 29 13:50:40 samsung5-ubuntu gnome-shell[4827]: Execution of main.js threw exception: Script threw an exception Oct 29 13:50:40 samsung5-ubuntu kernel: [ 34.380764] gnome-shell[4827]: segfault at 168 ip 7ffb177078ae sp 7ffcb7739a00 error 4 in libmozjs-60.so.0.0.0[7ffb1767b000+709000] Oct 29 13:50:40 samsung5-ubuntu kernel: [ 34.380769] Code: fe ff ff 49 8b 54 24 40 48 89 95 a8 fe ff ff 48 8d 9d a0 fe ff ff 49 89 5c 24 40 49 8b 94 24 a8 00 00 00 48 8b 92 c8 2a 00 00 <48> 3b 82 68 01 00 00 0f 84 a3 66 00 00 49 8b 45 f8 48 89 85 f0 fe Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 29 13:50:40 samsung5-ubuntu gnome-session[4565]: gnome-session-binary[4565]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Oct 29 13:50:40 samsung5-ubuntu gnome-session-binary[4565]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 29 13:50:40 samsung5-ubuntu at-spi-bus-launcher[4567]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" ... I tried to uninstall all gnome-shell-extensions packages, but the behavior is exactly the same. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1800464 Title: CRITICAL gnome-shell error: segfault error 4 in libmozjs-60.so.0.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774039] Re: package gdm3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
se possível, gostaria de receber somente atualizações compativeis com minha máquina. -- 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/1774039 Title: package gdm3 failed to install/upgrade: installed gdm3 package post- installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
Reported as https://gitlab.gnome.org/GNOME/gdm/issues/438. -- 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/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
apport information
** Tags added: apport-collected bionic
** Description changed:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to the login screen with no
indication of what went wrong.
== Session "dead" ==
- chmod 444 ~/.cache
- chmod 000 ~/.config
- chmod 444 ~
- chmod 000 ~
In this scenario, the system just freezes: the cursor is unresponsive
and users will be reaching for the power button.
= Observation =
These scenarios would all be caused by human error.
However, clearly it is possible for the system to detect such issues and
either alert the user to the problem or simply just fix the problem.
This does not happen in Ubuntu 18.04 LTS though.
= Idea =
Have the display manager call a utility prior to executing the users
preferred session. This utility -- which could be a simple shell script
I think ("friendly-session-fixer" maybe? :) -- would do one or both of
the following:
- Perform checks for the issues outlined above warn the user graphically
if any are found.
- Fix any issues found to allow the user to login.
However they are treated, all issues should also be logged in the
journal (could be the user journal, but the system journal may be best
to allow admins to spot such issues being detected more easily?)
= Rationale =
1) All the problems above, although user-generated, are:
- trivially fixable.
- potentially very hard / impossible for a naeve user to debug and resolve.
2) By handling such errors, users won't have a bad experience of Linux
if they inadvertently perturb a critical file.
3) Users will not need to resort to a re-install (which I can imagine
some may have to given the current behaviour).
= Ideas for further checks =
- Check to ensure key files exist and if not, copy them in from /etc/skel/,
etc.
- Check to ensure users home directory is owned by them and not root, etc.
- If the home partition / disk is 100% full, the script could logrotate and
compress the contents of ~/.cache/ ?
= Notes =
- You could argue that the session managers themselves should deal with
- these issues. In some cases that may be a fair comment. However, by
- having a single central check/fix script, the problems can be handled
- centrally without the issue whereby some session managers tolerate
- certain scenarios whereas others don't.
+ You could argue that the session managers themselves should deal with these
issues. In some cases that may be a fair comment. However, by having a single
central check/fix script, the problems can be handled centrally without the
issue whereby some session managers tolerate certain scenarios whereas others
don't.
+ ---
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-10-29 (0 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: gdm3 3.28.0-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_GB.UTF-8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
+ Tags: bionic
+ Uname: Linux 4.15.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1800277/+attachment/5206695/+files/Dependencies.txt
--
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/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
apport info added. -- 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/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1800277/+attachment/5206696/+files/ProcCpuinfoMinimal.txt -- 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/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754702] Re: Delay before you can type after switching input source
I have Ubuntu Gnome with English and Russian. When I click Meta+Space quickly, the "indicator menu" does NOT appear. But the input is blocked for an about a half of a second or a second. -- 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/1754702 Title: Delay before you can type after switching input source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754702/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
When putting emphasis on a stable system, staying with Xorg is probably a good idea for the time being. While I use Xwayland daily now, it definitely comes with a number of quirks. - Transparency comes and goes. For example, moving a window to near the top of the screen makes the top menu bar intransparent. - Sometimes shadows flicker around, which probably want to be window frame shadows, but get misplaced. - Copy & Paste by left/middle mouse button sometimes works, sometimes not. Be prepared to use Ctrl-C/Ctrl-V more often and/or to check every pasted text. - gnome-shell collects a lot more memory. Currently at ~500 MB after two days of usage. - Commodities like 'sudo synaptic' no longer work, it needs 'xhost +local:; sudo synaptic'. sudo somehow doesn't forward screen settings. Ignoring such quirks, it runs at least stable. No crashes so far. And screen drawing happens faster. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
I changed to Dolphin :-( -- 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/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
Ideally that would be reported upstream (https://gitlab.gnome.org/GNOME/gdm/issues/), there is more chance to have one of the project contributors looking at the problem there ** Changed in: gdm3 (Ubuntu) Status: Incomplete => 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/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
can you attach the journal log? ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
it's better if bugs are opened with apport so they get proper tagging for the ubuntu version they are reported against, etc, but I don't think it's a requirement for that one -- 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/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1595927] Re: Impossible to format a USB who contains bootable ISO
** Changed in: gnome-disk-utility (Ubuntu) Status: Confirmed => Triaged ** Also affects: gnome-disk-utility via https://bugzilla.gnome.org/show_bug.cgi?id=768031 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1595927 Title: Impossible to format a USB who contains bootable ISO To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1595927/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
Yes, in the least it helps us track the affected release and package versions. -- 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/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799840] Re: Input does not work for half a second while switching keyboard language
*** This bug is a duplicate of bug 1754702 *** https://bugs.launchpad.net/bugs/1754702 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1754702, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1754702 Delay before you can type after switching input source -- 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/1799840 Title: Input does not work for half a second while switching keyboard language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754702] Re: Delay before you can type after switching input source
** Package changed: gnome-control-center (Ubuntu) => gnome-shell (Ubuntu) -- 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/1754702 Title: Delay before you can type after switching input source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754702/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800277] Re: "chmod u-w ~/.ICEauthority" breaks login
I can do that if really required, but this is not a bug with my system - it's just the way the system works right now, so I'm suggesting an idea for how we can make it better :) -- 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/1800277 Title: "chmod u-w ~/.ICEauthority" breaks login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1800277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795028] Update Released
The verification of the Stable Release Update for nautilus has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1795028 Title: Nautilus crashes during search in is_recursive_search (search-engine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795028] Re: Nautilus crashes during search in is_recursive_search (search-engine)
This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.2 --- nautilus (1:3.26.4-0~ubuntu18.04.2) bionic; urgency=medium * d/p/search-engine-Query-file-system-to-determine-remoteness.patch: - Fix remote filesystem check on file during search (LP: #1795028) * d/p/0016-search-engine-add-a-recent-search-engine-listing-Gtk.patch: - Refreshed to add memory leak and potential crash fixes (LP: #1798426) -- Marco Trevisan (Treviño) Mon, 08 Oct 2018 18:30:01 +0200 ** Changed in: nautilus (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1795028 Title: Nautilus crashes during search in is_recursive_search (search-engine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798426] Update Released
The verification of the Stable Release Update for nautilus has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1798426 Title: Nautilus leaks memory for each recent engine search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1798426/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798426] Re: Nautilus leaks memory for each recent engine search
This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.2 --- nautilus (1:3.26.4-0~ubuntu18.04.2) bionic; urgency=medium * d/p/search-engine-Query-file-system-to-determine-remoteness.patch: - Fix remote filesystem check on file during search (LP: #1795028) * d/p/0016-search-engine-add-a-recent-search-engine-listing-Gtk.patch: - Refreshed to add memory leak and potential crash fixes (LP: #1798426) -- Marco Trevisan (Treviño) Mon, 08 Oct 2018 18:30:01 +0200 ** Changed in: nautilus (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1798426 Title: Nautilus leaks memory for each recent engine search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1798426/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754702] Re: Delay before you can type after switching input source
i am use key "WIN + SPACE", and have problem about this bug. now i can fix, it look like ubuntu delay if you use key "fn", "Win", "Super". i try to change change layout by use "crtl+space", now it so fast. may be help you. -- 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/1754702 Title: Delay before you can type after switching input source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1754702/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
Actually the fix is in the next future point release of 3.28 already as Marco pointed out: https://gitlab.gnome.org/GNOME/mutter/commit/1276cc97d1e It appears mutter version 3.28.4 will have the fix. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796607] Re: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_dis
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1796607 Title: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_display_open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799787] Re: gnome-shell crashes when forcing a restart if applications are started on multiple workspaces
*** This bug is a duplicate of bug 1796607 *** https://bugs.launchpad.net/bugs/1796607 Thanks Paul. That link shows the same crash happened today and it is still bug 1796607. So I am satisfied this is now a duplicate of that. ** This bug has been marked a duplicate of bug 1796607 gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_display_open -- 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/1799787 Title: gnome-shell crashes when forcing a restart if applications are started on multiple workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799787/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
That's incorrect. Ubuntu 18.04 will get the fix because the fix is small and should be easy to backport to 3.28. I don't know the timeframe though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
Edit the file /etc/gdm3/custom.conf it also worked for me. If someone had tried installing lighdm you can go back to gdm by doing sudo service lightdm stop sudo reboot -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799787] Re: gnome-shell crashes when forcing a restart if applications are started on multiple workspaces
Daniel, I've tried four times to create a new bug report. Although I get a prompt to advise that Ubuntu 18.10 has experienced an error and clicked on 'send' I just get returned to the terminal prompt. Here is my /var/crash directory which shows a .crash file was generated just a few minutes ago: drwxrwsrwt 2 root whoopsie4096 Oct 29 07:34 ./ drwxr-xr-x 14 root root4096 Oct 2 09:33 ../ -rwxrwxrwx 1 root whoopsie 0 Oct 29 07:27 .lock* -rw-r- 1 paul whoopsie 4555151 Oct 29 07:34 _usr_bin_gnome-shell.1000.crash -rw-rw-r-- 1 paul whoopsie 0 Oct 29 07:34 _usr_bin_gnome-shell.1000.upload -rw--- 1 whoopsie whoopsie 0 Oct 29 07:37 _usr_bin_gnome-shell.1000.uploaded Latest link on the error tracker: https://errors.ubuntu.com/oops/6d3ef9d8-db4d-11e8-9fbe-fa163e6cac46 A simpler way for me to reproduce the crash is to go directly to workspace 4, start an application and restart gnome-shell. Crashes every time. -- 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/1799787 Title: gnome-shell crashes when forcing a restart if applications are started on multiple workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799787/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
Well that's annoying: I need an LTS for a project. (The 5 years support frame for the LTS versions is too short, but we'll have to get by) so the remaining option is to wait for 20.4, right? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
this bug won't ever be solved in 18.04 because Canonical won't update its archive or repository to mutter 3.30 anyone who wants to fix this issue must upgrade to Ubuntu 18.10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1595927] Re: Impossible to format a USB who contains bootable ISO
The problem can be avoided by using gparted to format the usb drive -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1595927 Title: Impossible to format a USB who contains bootable ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1595927/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
