[Bug 1767145] [NEW] Power status says my battery is fully charged. I'm on a desktop. I have no battery
Public bug reported: Just upgraded to bionic. Gnome says my battery is fully charged. ONly thing is, this isn't a laptop. I have no batter. It is impossible for my battery to be fully charged, since it doesn't exist. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-power-manager 3.26.0-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 26 11:38:12 2018 InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "See my non-existent battery's status." https://bugs.launchpad.net/bugs/1767145/+attachment/5127725/+files/gnome-power-panel.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1767145 Title: Power status says my battery is fully charged. I'm on a desktop. I have no battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1767145/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
@seb, per discussion via IRC, here are my logs from /var/log/dist- upgrade (upgrade started last night and finally wrapped up this morning after a lot of coffee and swearing). To answer the questions: I started off with 'do-release-upgrade -d' last night and ended up this morning with a reboot into rescue mode and a lot of 'apt-get -f install', 'dpkg --reconfigure -a' and finally an 'apt-get dist-upgrade' (or was it a -f install again?) to get the remaining held 2400+ packages updated. NOW I believe I'm finally updated to Bionic and running again. Also, will asked if I had manually modified anything in /etc/apt/sources.list and the answer is no, all that was handled by the upgrader. ** Attachment added: "xenial-bionic-upgrade-logs.tgz" https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5127748/+files/xenial-bionic-upgrade-logs.tgz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
FWIW, it's entirely possible I had other issues that just also included this one, or just exposed this one where I may not have seen it otherwise. This just happened to be the only one that Apport was able to create and submit. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
I think I'm experiencing the same problem. I installed Ubuntu 18.04 beta last Tuesday. When I power on my computer, the screen blinks 50-53 times over the span of 2-1/2 minutes (this is perfectly reproducible) and then for the rest of the session, everything works flawlessly. After LinuxFest Northwest, I was told to do an apt dist-upgrade and that did not clear the problem. I have two video cards: VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1) I'm not sure what other information would be helpful. -- 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/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1731911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 608162] Re: GNOME Keyring Daemon stops panel's shutdown
I've just started getting this on my laptop with a current version of Linux Mint Cinnamon with all the updates. Also if I close my laptop (so it sleeps) when I open it, sometimes the screen just goes blank and even REISUB or REISUO will not work. I've also had to run fschk to fix issues which I think are cause by forcing the shutdown while the screen is blank. Not sure if the blank screen is related to the gnome-keyring- daemon or not, but they both started at the same time. There have been a lot of updates recently with the Intel chip problem, so I have no idea which (if any) have caused 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/608162 Title: GNOME Keyring Daemon stops panel's shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752430] [NEW] tracker-miner-apps fails when /usr/local/share/applications is a link
Public bug reported: /usr/local/share/applications is a symbolic link on one of my systems because I am using xstow to manage packages in /usr/local. There are valid .desktop files within this linked directory, however. tracker-miner-apps cannot parse this file/link/directory, so it keeps trying forever with high CPU usage, and spewing error messages to syslog. Feb 28 12:55:25 gallium gnome-session[30827]: (tracker-miner-apps:30995): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/local/share/applications': 'Couldn't load desktop file:'/usr/local/share/applications'' Feb 28 12:55:25 gallium gnome-session[30827]: message repeated 40 times: [ (tracker-miner-apps:30995): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/local/share/applications': 'Couldn't load desktop file:'/usr/local/share/applications''] I worked around the problem by making /usr/local/share/applications and directory containing symbolic links to .desktop files within the stowed packages. This is what it looks like now: jeffrey@gallium:/usr/local/share/applications$ ls -l total 20 -rw-r--r-- 1 root root 13 Feb 25 20:27 mimeinfo.cache lrwxrwxrwx 1 root root 61 Feb 28 13:14 thinlinc-setup.desktop -> ../../stow/thinlinc/share/applications/thinlinc-setup.desktop lrwxrwxrwx 1 root root 65 Feb 28 13:14 thinlinc-webaccess.desktop -> ../../stow/thinlinc/share/applications/thinlinc-webaccess.desktop lrwxrwxrwx 1 root root 62 Feb 28 13:14 thinlinc-webadm.desktop -> ../../stow/thinlinc/share/applications/thinlinc-webadm.desktop lrwxrwxrwx 1 root root 75 Feb 28 13:12 vncviewer.desktop -> ../../stow/tigervnc-Linux-x86_64-1.6.0/share/applications/vncviewer.desktop After this change tracker-miner-apps seems to be happy. More generally, it's bad and wrong that an indexer can peg the CPU when it has a bug. It should limit rescan attempts to a certain number and then put them on a queue to check infrequently. Would it be just as aggressive if I created a bad .desktop file? An indexer should be as tolerant as possible of bad files, IMO. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker-miner-fs 1.6.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Feb 28 13:26:36 2018 InstallationDate: Installed on 2015-11-19 (832 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) JournalErrors: -- No entries -- ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: tracker UpgradeStatus: Upgraded to xenial on 2016-09-17 (528 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1752430 Title: tracker-miner-apps fails when /usr/local/share/applications is a link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1752430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767129] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: I am desperately trying to fix a Xenial to Bionic upgrade that had a LOT of broken package upgrades. I've finally managed to get through a lot of them and this one prompted apart once I had rebooted into a rescue shell and tried to run 'apt-get -f install' ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 25 16:43:42 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-02-11 (804 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1767129 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1767129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767185] [NEW] Must click logout twice to log out.
Public bug reported: Upgraded from Xenial to Bionic. Now, when I select Logout from the menu (on both Unity and Gnome) I must do so twice before the logout is initiated. Steps: click the menu in the upper right corner click the Logout option Menu closes Click the menu again Click the logout option again Logout dialog appears Expected steps: Same as above, without having to repeat myself. Note I tried this in both Unity and Gnome3 and the results are the same in both. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session-bin 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 26 15:58:16 2018 InstallationDate: Installed on 2016-02-11 (805 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1767185 Title: Must click logout twice to log out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1767185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
After some googling around, in the end I ended up doing this: sudo apt install gnome-calculator sudo snap remove gnome-calculator And now both my keyboard calculator shortcut works as well as the calculator is no longer transparent. I have no idea what snap even is. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
It's hitting me right now. Which kind of info should I be providing? I'm on Ubuntu 18.04 desktop, latest `apt dist upgrade`... ** Attachment added: "screenshot of transparent calc" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+attachment/5242387/+files/calc_back.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725955] Re: "Printer added" notification
Happens to me in 18.04 desktop -- 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/1725955 Title: "Printer added" notification To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1725955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Precise is EOL ** Changed in: gnome-screensaver (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Precise is EOL ** Changed in: unity (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849254] [NEW] Noto Sans Mono Bold not available from /etc/fonts/local.conf
Public bug reported: I tried to change my monospace font to "Noto Sans Mono Bold" in /etc/fonts/local.conf but that didn't have an effect so I did a little digging. First I ran $ sudo fc-cache -f -v && sudo dpkg-reconfigure fontconfig fontconfig-config Which succeeded, then: $ fc-list :style=bold | grep -i notosansmono >/usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf: Noto Sans Mono:style=Bold So then: $fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf | less which seemed to return a normal looking result similar to: $fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Regular.ttf | less Then I ran: $ fc-match -s "monospace" | grep -i bold >DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold" >MathJax_Fraktur-Bold.otf: "MathJax_Fraktur" "Bold" >padmaa-Bold.1.1.ttf: "padmaa-Bold.1.1" "Bold.1.1" >DejaVuSans-BoldOblique.ttf: "DejaVu Sans" "Bold Oblique" Which obviously isn't right since it isn't in that list. Also: $fc-match -s "NotoSansMono" | grep -i notosansmono >NotoSansMono-Regular.ttf: "Noto Sans Mono" "Regular" My system is up to date and here is my version: $lsb_release -a lsb_release: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $uname -a >Linux 9343 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 >x86_64 x86_64 x86_64 GNU/Linux ** Affects: fonts-noto (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1849254 Title: Noto Sans Mono Bold not available from /etc/fonts/local.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1849254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1374403] Re: EOG - CMYK jpg colors are saturated and not correct
This bug still exist, 2020 here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1374403 Title: EOG - CMYK jpg colors are saturated and not correct To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1374403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905513] [NEW] Mouse does not respect primary/secondary button settings after being disconnected and reconnected.
Public bug reported: After installing 20.04, in the gnome control center I selected the right mouse button to be the primary button. When I unplug the mouse and replug it in, the right mouse button is no longer the primary button. When I look at the gnome control center, the setting says that the right mouse button is the primary button. To get the right button as the primary button I need to click on the GUI control to make the left button primary and then on the same control a second time to make the right button primary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108853~20.04~8bcf10e~dev-generic 5.8.17 Uname: Linux 5.8.0-7630-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 20:43:26 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2014-10-04 (2244 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-11-12 (12 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1905513 Title: Mouse does not respect primary/secondary button settings after being disconnected and reconnected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930943] [NEW] package evolution-common 3.36.4-0ubuntu1 failed to install/upgrade: unable to stat './usr/share/help/sl/evolution/figures' (which I was about to install): Input/output error
Public bug reported: Novice user. submitting report because Ubuntu said I should ProblemType: Package DistroRelease: Ubuntu 20.04 Package: evolution-common 3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 5 11:35:08 2021 ErrorMessage: unable to stat './usr/share/help/sl/evolution/figures' (which I was about to install): Input/output error InstallationDate: Installed on 2021-05-27 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: evolution Title: package evolution-common 3.36.4-0ubuntu1 failed to install/upgrade: unable to stat './usr/share/help/sl/evolution/figures' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- 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/1930943 Title: package evolution-common 3.36.4-0ubuntu1 failed to install/upgrade: unable to stat './usr/share/help/sl/evolution/figures' (which I was about to install): Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1930943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's only the three built in extensions installed. Thanks I'll run journalctl -b-1 > prevboot.txt next time. ls /var/crash/ says _usr_lib_systemd_systemd-timesyncd.102.crash _usr_lib_systemd_systemd-timesyncd.102.upload _usr_lib_systemd_systemd-timesyncd.102.uploaded I only see a similar error on https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a Is the lock screen handled by gnome-shell itself or some outside process like gdm3? If there some signal or whatever I can send to gnome-shell -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It now manifests as a black screen with the same behavior, mouse works but no keyboard, except for Fn+Alt+Ctrl+F?? working. I've attacked the output of journalctl but from the current boot since I used killall -HUP gnome-shell, which yes leave some applications running, but not firefox (or tor browser). It's much less common now but this one happened on suspend trigger by the lid being closed. Thanks! :) ** Attachment added: "black_screen_killall_hup_gnomeshell.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5570958/+files/black_screen_killall_hup_gnomeshell.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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's again waking with a black screen in which only mouse and Fn+Ctrl+Alt+F?? keys work. I've attached the jountalctl -b0 output from prior to reboot, probably more relevant than grabbing the actual reboot. Mär 23 07:09:16 aletheia kernel: Restarting tasks ... done. Mär 23 07:09:16 aletheia systemd-logind[1556]: Lid opened. Mär 23 07:09:16 aletheia Tor[1683]: Tor has been idle for 26589 seconds; assuming established circuits no longer work. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: The canary thread is apparently starving. Taking action. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: Demoting known real-time threads. Mär 23 07:09:16 aletheia rtkit-daemon[1766]: Demoted 0 threads. Mär 23 07:09:16 aletheia Tor[1683]: Heartbeat: Tor's uptime is 0:00 hours, with 0 circuits open. I've sent 0 kB and received 0 kB. Mär 23 07:09:16 aletheia systemd[1]: NetworkManager-dispatcher.service: Succeeded. Mär 23 07:09:16 aletheia kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Mär 23 07:09:16 aletheia kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mär 23 07:09:16 aletheia systemd[1]: Starting Daily apt download activities... Mär 23 07:09:16 aletheia systemd[1]: Starting Refresh fwupd metadata and update motd... Mär 23 07:09:16 aletheia systemd[1]: Starting Message of the Day... Mär 23 07:09:16 aletheia systemd[1]: Starting Ubuntu Advantage Timer for running repeated jobs... Mär 23 07:09:16 aletheia systemd[1]: motd-news.service: Succeeded. Mär 23 07:09:16 aletheia systemd[1]: Finished Message of the Day. Mär 23 07:09:16 aletheia upowerd[1864]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia upowerd[1864]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia systemd-sleep[34855]: System resumed. Mär 23 07:09:16 aletheia kernel: PM: suspend exit Mär 23 07:09:16 aletheia gsd-power[2839]: Error calling suspend action: GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress Mär 23 07:09:16 aletheia fwupd[3148]: 06:09:16:0867 FuEngine failed to record HSI attributes: failed to get historical attr: json-glib version too old Mär 23 07:09:16 aletheia systemd[1]: systemd-suspend.service: Succeeded. Mär 23 07:09:16 aletheia systemd[1]: Finished Suspend. We compare this semi-locked gnome-shell with a working unsleep from a brief lid close: Mär 23 07:42:19 aletheia kernel: Restarting tasks ... Mär 23 07:42:19 aletheia kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Mär 23 07:42:19 aletheia systemd-logind[1529]: Lid opened. Mär 23 07:42:19 aletheia kernel: done. Mär 23 07:42:19 aletheia upowerd[1838]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:42:19 aletheia kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mär 23 07:42:19 aletheia upowerd[1838]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb3/3-3 Mär 23 07:09:16 aletheia systemd-sleep[34855]: System resumed. Mär 23 07:42:19 aletheia kernel: PM: suspend exit Mär 23 07:42:19 aletheia systemd[1]: systemd-suspend.service: Succeeded. Mär 23 07:42:19 aletheia systemd[1]: Finished Suspend. I wind up with gnome-shell being stuck when "kernel: done" never appears, the "upowerd" line appears twice, and we get the error: Mär 23 07:09:16 aletheia gsd-power[2839]: Error calling suspend action: GDBus.Error:org.freedesktop.login1.OperationInProgress: There's already a shutdown or sleep operation in progress I've maybe some early unsleep phase not finishing correctly, which then convinces gsd-power believing that sleep continues? * Irrelevant looking differences: The mei_hdcp comes before the lid opened line. Activities like tor and rt-kit-daemon have not been asleep long enough to be doing restart work. ** Attachment added: "black_screen_with_mouse.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572108/+files/black_screen_with_mouse.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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I'd another crash with a purple screen and no mouse movement, but this time only a 10 minute lid close caused the crash. Awful lot of gdm and gnome-shell errors this time, but not clear the source. ** Attachment added: "purple_no_mouse-23_march.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572272/+files/purple_no_mouse-23_march.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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's growing kinda worst with 5.14.0-1031-oem in that gnome-shell now more reliably fails unsleep, but I've not yet seen any real crash under 5.14.0-1031-oem. I've still not tried non OWM kernels. ** Attachment added: "black_screen_with_mouse-29_march-b.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5574448/+files/black_screen_with_mouse-29_march-b.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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Is it normal that gnome-session-bin is installed but gnome-session is not installed? I believe this black screen version is different because when switching back with Fn+Ctrl+Alt+F1 it simply returns to the black screen, without any purple password prompt. I suppose another problem must be causing both versions. -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's related to during being suspended: It does not trigger on pressing suspend from the menu bar, waiting briefly, and then pressing keys to wake. It also does not trigger if I close and open the lid less than a minute later. It can now trigger if I close the lid and then reopen the lid 10 minutes later. At this point it arrives at a purple ubuntu login screen, but no responses to keyboard or mouse, and not network presence. Could this be caused by the system changing sleep/suspend mode while sleeping/suspended? Could this be related to /swapfile being only 4 gigs, while main memory is 16 gigs? It's a ThinkPad X1 Carbon Gen 11 running a kernel 5.14.0-1027-oem for a Gen 9 (nothing else exists afaik). I've no idea what OEM kernels change of course, but I can try to figure out changing the kernel. I'll likely need to change something in /etc/default/grub to get access to a grub boot menu to choose kernels. ** Attachment added: "purple_no_mouse_two.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5571706/+files/purple_no_mouse_two.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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've found some lenovo firmware oddities too https://github.com/fwupd/firmware-lenovo/issues/210 so I'll poke around there too. ** Bug watch added: github.com/fwupd/firmware-lenovo/issues #210 https://github.com/fwupd/firmware-lenovo/issues/210 -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've also found folks fixed similar issues by downgrading the kernel to 5.11.0.38: https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I'd something new this time, after sleep/suspend it returned to the purple login screen, but now nothing worked, no mouse or keyboard. It ran the fan for a little while, so I give it some time to return, but no luck. ** Attachment added: "purple_no_mouse.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5571532/+files/purple_no_mouse.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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Also the Fn+Ctrl+Alt+F?? keys no longer worked here. -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've also found folks fixed similar issues by downgrading the kernel to 5.11.0.38: https://askubuntu.com/questions/1384450/ubuntu-20-04-wont-wake-from-suspend-or-completely-shutdown -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Appears nope I've purely a sleep problem, unless all this fwupd playing turnned off hibernate: ``` root@aletheia:/home/jeff/Downloads# systemctl status hibernate.target ● hibernate.target - Hibernate Loaded: loaded (/lib/systemd/system/hibernate.target; static; vendor prese> Active: inactive (dead) Docs: man:systemd.special(7) root@aletheia:/home/jeff/Downloads# systemctl status hybrid-sleep.target ● hybrid-sleep.target - Hybrid Suspend+Hibernate Loaded: loaded (/lib/systemd/system/hybrid-sleep.target; static; vendor pr> Active: inactive (dead) Docs: man:systemd.special(7) ``` -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
oops alright. I've no gnome-shell reports in /var/crash only another systemd-timesyncd report. I don't think gnome-ghell is crashing, but sometimes just stuck when emerging from suspend. -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've still not tried other kernels, in part because ubuntu keeps pushing out new OEM kernels, so I give them all a try, but the same basic problem persist, either gnome-shell gives only a black screen, or else the whole system hangs on the purple screen. I've far more diverse crashes with the latest kernels and the bolt upgrade: https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Another purple screen lockup. It's now also more common the system runs how while closed. ** Attachment added: "purple_screen_lockup-8_april.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5578017/+files/purple_screen_lockup-8_april.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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
This one seemed like it refused to wake even enough to draw a black scree, just stayed asleep. I've no idea if this is hlepful ** Attachment added: "refuses_to_wake.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5579458/+files/refuses_to_wake.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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's seemingly much less bad if I disable suspend when plugged into power, and maybe the remaining problems come from plugging in power before resume. -- 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/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 539243] Re: initial account creation window gives no indication of successful account creation
** Changed in: empathy (Ubuntu) Status: Triaged => Invalid -- 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/539243 Title: initial account creation window gives no indication of successful account creation To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/539243/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 576669] Re: Document Viewer has no support for common office document file formats
** Changed in: evince (Ubuntu) Status: Triaged => Won't Fix -- 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/576669 Title: Document Viewer has no support for common office document file formats To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/576669/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Also affects: gnome-screensaver (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: gnome-screensaver (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 655713] Re: Logic needed to disable built in pointing devices when external devices are connected
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-control-center Status: New => Invalid -- 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/655713 Title: Logic needed to disable built in pointing devices when external devices are connected To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/655713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-shell (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: unity (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-shell (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-screensaver (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-screensaver (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1991002] [NEW] gimp crashes when adding text
Public bug reported: Going to the text tool and trying to type anything instantly crashes gimp, every time. ``` GNU Image Manipulation Program version 2.10.30 git-describe: GIMP_2_10_30 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.2.0 (Ubuntu 11.2.0-16ubuntu1) # Libraries # using babl version 0.1.92 (compiled against version 0.1.88) using GEGL version 0.4.34 (compiled against version 0.4.34) using GLib version 2.72.1 (compiled against version 2.71.1) using GdkPixbuf version 2.42.8 (compiled against version 2.42.6) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.50.6 (compiled against version 1.50.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` /lib/x86_64-linux-gnu/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x3d8)[0x7fe773b0add8] gimp(+0xec78e)[0x556263f4478e] gimp(+0xec84e)[0x556263f4484e] gimp(+0xec8ad)[0x556263f448ad] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7fe772c42520] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x7ec0a)[0x7fe773bbdc0a] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(gdk_device_get_state+0x143)[0x7fe773bbdde3] gimp(gimp_device_info_get_device_coords+0x79)[0x5562640daf99] gimp(gimp_device_info_get_event_coords+0x56)[0x5562640db166] gimp(+0x1f9896)[0x556264051896] gimp(+0x1fe99b)[0x55626405699b] gimp(gimp_display_shell_canvas_tool_events+0x91)[0x556264047331] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1434d7)[0x7fe773d434d7] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7fe7731ddd2f] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x30b76)[0x7fe7731f9b76] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xbb6)[0x7fe7731faf66] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x7fe7731fb7a3] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x26f024)[0x7fe773e6f024] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_widget_send_focus_change+0x95)[0x7fe773e76975] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x27dee6)[0x7fe773e7dee6] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x280f26)[0x7fe773e80f26] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x281193)[0x7fe773e81193] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1434d7)[0x7fe773d434d7] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7fe7731ddd2f] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x30564)[0x7fe7731f9564] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xbb6)[0x7fe7731faf66] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x7fe7731fb7a3] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x26f024)[0x7fe773e6f024] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_main_do_event+0x54b)[0x7fe773d428bb] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x6716b)[0x7fe773ba616b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x26b)[0x7fe7730e4d1b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0xaa6f8)[0x7fe7731396f8] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x73)[0x7fe7730e4293] gimp(app_run+0x3fc)[0x556263f49adc] gimp(main+0x362)[0x556263f3f752] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7fe772c29d90] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7fe772c29e40] gimp(_start+0x25)[0x556263f3f8d5] ``` ** Affects: gimp (Ubuntu) Importance:
[Bug 2045948] [NEW] Incorrect time zone detected
Public bug reported: Ubuntu version: 22.04.3 LTS gnome-settings-daemon version: 42.1-1ubuntu2.2 My system is incorrectly setting the time zone to "MST (Denver, United States)" while I am currently in Austin, TX which is CST. geoclue shows the correct latitude/longitude: $ /usr/libexec/geoclue-2.0/demos/where-am-i Geolocation service in use Client object: /org/freedesktop/GeoClue2/Client/7 New location: Latitude:30.376800° Longitude: -97.893500° Accuracy:5000.00 meters Timestamp: Thu 07 Dec 2023 09:36:18 PM MST (1702010178 seconds since the Epoch) which corresponds to Austin, TX. My syslog shows 1000s of assertion errors in gsd-datetime: Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: message repeated 302 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: message repeated 1315 times: [ g_object_ref: assertion 'G_IS_OBJECT (object)' failed] Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_has_coords: assertion 'loc != NULL' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_get_city_name: assertion 'loc != NULL' failed Dec 6 00:06:31 jnchase-thinkpad gsd-datetime[1964]: gweather_location_get_country: assertion 'loc != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-settings-daemon 42.1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.14.0-1059.67-oem 5.14.21 Uname: Linux 5.14.0-1059-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Dec 7 23:57:53 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220425-68+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-05-10 (576 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220425-07:09 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to jammy on 2023-06-15 (175 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- 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/2045948 Title: Incorrect time zone detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2045948/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 162695] will not play audio from library after changing location to new network folder
Public bug reported: Binary package hint: rhythmbox - access to drive (library source) from other machines and applications is confirmed - permissions are set for access to library source - set library source to be a network location; let library build tracklist - change library source to a different network location tracks will then not play from new source, and library doesn't build. Errors accumulate when importing the tracks saying Gstreamer error report a bug. Resolution: Manually Delete all tracks in the library. Change library location source. Close program, open program wait for a bit, and finally the library starts to build from the newly set location. ProblemType: Bug Architecture: i386 Date: Wed Nov 14 11:44:35 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.11.2-0ubuntu4 PackageArchitecture: i386 ProcCmdline: rhythmbox ProcCwd: /home/network-ninja ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux network-ninja-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- will not play audio from library after changing location to new network folder https://bugs.launchpad.net/bugs/162695 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 162695] Re: will not play audio from library after changing location to new network folder
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/10367054/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/10367055/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/10367056/ProcStatus.txt -- will not play audio from library after changing location to new network folder https://bugs.launchpad.net/bugs/162695 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 668785] [NEW] [wishlist] Change a contact's avatar
Public bug reported: Binary package hint: empathy I'd like to be able to choose the avatar displayed in Contact List for my contacts. I envision the Edit Contact Information dialog showing both the latest avatar supplied by my contact and the avatar I have currently selected for that contact, if any. So I can either select to use the contact-supplied avatar or select an image from my filesystem. ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- [wishlist] Change a contact's avatar https://bugs.launchpad.net/bugs/668785 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069531] Re: Cannot login to Empathy after setting up Google online account
Killing signonpluginprocess worked for me too. 13.10. -- 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/1069531 Title: Cannot login to Empathy after setting up Google online account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1069531/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/-/issues/191 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1616332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850707] Re: "Data source "u...@gmail.com" does not support OAuth 2.0 authentication" shown each time Evolution starts
This might be https://gitlab.gnome.org/GNOME/evolution/-/issues/538 ? ** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #538 https://gitlab.gnome.org/GNOME/evolution/-/issues/538 -- 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/1850707 Title: "Data source "u...@gmail.com" does not support OAuth 2.0 authentication" shown each time Evolution starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1850707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1136644] Re: gedit search function is not practical anymore
** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #398 https://gitlab.gnome.org/GNOME/gedit/-/issues/398 ** Also affects: gedit via https://gitlab.gnome.org/GNOME/gedit/-/issues/398 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1136644 Title: gedit search function is not practical anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1136644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1136644] Re: gedit search function is not practical anymore
While it won't address your UX annoyances, I have filed an issue upstream proposing an approach to make live search faster for big files: https://gitlab.gnome.org/GNOME/gedit/-/issues/398 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1136644 Title: gedit search function is not practical anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1136644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1943488] Re: when typeing too fast in the search line searching stops to work
If this is related to the bug I had filed upstream (linked above), then this should be fixed in Nautilus 43.1 or later. ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1731 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731 Importance: Unknown Status: Unknown -- 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/1943488 Title: when typeing too fast in the search line searching stops to work To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1943488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993308] Re: Update gnome-calendar to 43.1
Hi Jeremy, we keep getting users reporting bugs on 43.0 upstream. Why does 43.1 not show up in https://packages.ubuntu.com/search?keywords=gnome- calendar=names=kinetic=all ? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1993308 Title: Update gnome-calendar to 43.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008532] Re: Typing a filename in a nautilus window, and the letters are not in the order I typed them.
This is not strictly a Nautilus bug, it's way bigger than that, it potentially affects all GTK4 applications when the system is under stress. I was told it's an ibus bug rather than GTK, so I filed it here, and I would really appreciate it if your team can help investigate or fix it: https://github.com/ibus/ibus/issues/2486 ** Bug watch added: github.com/ibus/ibus/issues #2486 https://github.com/ibus/ibus/issues/2486 ** Also affects: nautilus via https://github.com/ibus/ibus/issues/2486 Importance: Unknown Status: Unknown ** Project changed: nautilus => ibus -- 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/2008532 Title: Typing a filename in a nautilus window, and the letters are not in the order I typed them. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/2008532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 637519] Re: Automatically select the user in GDM if there's only one
** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #49 https://gitlab.gnome.org/GNOME/gdm/-/issues/49 ** Changed in: gdm Importance: Wishlist => Unknown ** Changed in: gdm Status: Expired => Unknown ** Changed in: gdm Remote watch: GNOME Bug Tracker #637566 => gitlab.gnome.org/GNOME/gdm/-/issues #49 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/637519 Title: Automatically select the user in GDM if there's only one To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/637519/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
** Also affects: nautilus via https://github.com/ibus/ibus/issues/2486 Importance: Unknown Status: Unknown ** Project changed: nautilus => ibus -- 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/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915468] Re: calendar should have a button in its top bar
** Changed in: gnome-calendar (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1915468 Title: calendar should have a button in its top bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1915468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551776] Re: Calendar: high cpu usage while open
** Bug watch added: bugzilla.gnome.org/ #762724 https://bugzilla.gnome.org/show_bug.cgi?id=762724 ** Changed in: gnome-calendar Importance: Medium => Unknown ** Changed in: gnome-calendar Status: Fix Released => Unknown ** Changed in: gnome-calendar Remote watch: GNOME Bug Tracker #762724 => bugzilla.gnome.org/ #762724 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1551776 Title: Calendar: high cpu usage while open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1551776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960339] Re: Problems setting Monday as first day of week
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #160 https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/160 ** Also affects: gnome-calendar via https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/160 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1960339 Title: Problems setting Monday as first day of week To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1960339/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1405005] Re: GNOME Calendar doesn't show correct first day of the week
** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #160 https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/160 ** Also affects: gnome-calendar via https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/160 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1405005 Title: GNOME Calendar doesn't show correct first day of the week To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1405005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826043] Re: Events spanning multiple days are displayed on the wrong day in week view
Shouldn't happen in recent versions, at least based on comments upstream. ** Changed in: gnome-calendar (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1826043 Title: Events spanning multiple days are displayed on the wrong day in week view To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1826043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1948556] Re: calendar has low contrast in both default themes
This was fixed in version 43-44 and newer. ** Changed in: gnome-calendar (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1948556 Title: calendar has low contrast in both default themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1948556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843910] Re: cannot add public (unauthenticated) web ics calendar
This was fixed in versions 45-46. ** Changed in: gnome-calendar (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1843910 Title: cannot add public (unauthenticated) web ics calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1843910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551776] Re: Calendar: high cpu usage while open
AFAIK this was fixed in versions 43-44 or so. Try version 46. ** Changed in: gnome-calendar (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1551776 Title: Calendar: high cpu usage while open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1551776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
