[Bug 1845709] Re: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported"
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1845709 Title: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846853] [NEW] Mouse scroll should control VOLUME NOT TIME
Public bug reported: I want the mouse scroll to scroll the volume up and down, not the time forward and back. This is a non-standard behavior that I consider to be a BUG within Totem, and I preferentially use VNC because of this BUG. Fix it so mouse scroll controls volume instead of time please. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- 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/1846853 Title: Mouse scroll should control VOLUME NOT TIME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1846853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845709] Re: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported"
I just reported it upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/1243 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1243 https://gitlab.gnome.org/GNOME/nautilus/issues/1243 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1243 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/1845709 Title: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I get this problem several times a day and it's become very frustrating. Ubuntu 18.04.3 GNOME 3.28.2 Please let me know if any additional information can help triage the bug. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846837] Re: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64
I added gcc-9 and ffmpeg to related packages because if search "libgomp.so.1: cannot allocate memory in static TLS block" in Google you will find this issue starting to appear in different program this years (such as Anaconda installer, OpenCV, PHP ImageMagick module) so I don't think this issue is isolated to Totem. However, Totem is only program where I can reliable reproduce this issue right now. -- 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/1846837 Title: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1846837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846837] [NEW] totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64
Public bug reported: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. ** Affects: ffmpeg (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** Also affects: ffmpeg (Ubuntu) Importance: Undecided Status: New -- 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/1846837 Title: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1846837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846776] Re: Renaming a desktop item causes the shell to hang
I did several tries yesterday, but none of them worked. First I tried to remove the "emit" calls and the "addSignalMethods" in desktopGrid, just in case the problem was an incompatibility with the new class system in Gnome Shell 3.34. Also removed all the grabHelper calls, but also didn't work. The problem seems to be the text entry, that is not editable. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1846776 Title: Renaming a desktop item causes the shell to hang To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1846776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846759] Re: Ubuntu's evolution-data-server package incompatible with gnome-calendar package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-calendar (Ubuntu) Status: New => Confirmed -- 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/1846759 Title: Ubuntu's evolution-data-server package incompatible with gnome- calendar package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1846759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Changed in: gnome-software (Ubuntu) Status: Incomplete => Opinion ** Changed in: gnome-software (Ubuntu) Status: Opinion => Confirmed -- 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/1699360 Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1699360/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 I have the same issue, Ubuntu 19.04 disco Nvidia GeForce GTX 1050 Pentium G4600 nvidia-smi Fri Oct 4 17:24:16 2019 +-+ | NVIDIA-SMI 418.56 Driver Version: 418.56 CUDA Version: 10.1 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 1050Off | :01:00.0 On | N/A | | 35% 34CP0N/A / 75W |430MiB / 1991MiB | 0% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 1266 G /usr/lib/xorg/Xorg26MiB | |0 1300 G /usr/bin/gnome-shell 47MiB | |0 1520 G /usr/lib/xorg/Xorg 111MiB | |0 1659 G /usr/bin/gnome-shell 241MiB | +-+ lshw -C video *-display description: VGA compatible controller product: GP107 [GeForce GTX 1050] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838132] Re: file browser hangs system for several seconds on save/load/exit
*** This bug is a duplicate of bug 1833114 *** https://bugs.launchpad.net/bugs/1833114 @seb128, I added the log when you asked. This bug affects all file saves / loads on all applications on Ubuntu, so it is very debilitating. Can't imagine why there are no other complainants. ** This bug has been marked a duplicate of bug 1833114 print page dialog latency when trying to cancel or to save -- 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/1838132 Title: file browser hangs system for several seconds on save/load/exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1838132/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846776] Re: Renaming a desktop item causes the shell to hang
** Changed in: gnome-shell-extension-desktop-icons Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1846776 Title: Renaming a desktop item causes the shell to hang To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1846776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846785] [NEW] Crashes instantly on launch with Pentium J5005 Processor
Public bug reported: [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel Atom based processors. (I got a J5005 pentium ). Doesn't crash on a Intel® Core™ i7-7567U. Due to this bug https://sourceforge.net/p/djvu/bugs/293/ , and fixed in commit 8407dd, on the 7th of October 2018. >From git tags, it is included in 3.5.27.1-11 (probably version xxx -10, though I cannot see this tag in git history) I notice that no dependency change affects any of the versions to the build process up to Disco (3.5.27.1-10) For intel J5005 (or N5000 on other popular machines ) this bug renders the package useless. Indeed, it crashes immediately at application startup. Note that this affects rdependencies such as evince, djview4. I suggest upgrading the version available for Bionic LTS as part of the development hardware stack long term support to 3.5.27.1-11. Yours sincerly, Milvi ** Affects: djview4 (Ubuntu) Importance: Undecided Status: New ** Affects: djvulibre (Ubuntu) Importance: Undecided Status: New ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Description changed: - [PROBLEM] Djvulibre on bionic is 3.5.27.1-8 crashes immediately on intel Atom based processors. (I got a J5005 pentium ). + [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel Atom based processors. (I got a J5005 pentium ). Doesn't crash on a Intel® Core™ i7-7567U. Due to this bug https://sourceforge.net/p/djvu/bugs/293/ , and fixed in commit 8407dd, on the 7th of October 2018. From git tags, it is included in 3.5.27.1-11 (probably version xxx -10, though I cannot see this tag in git history) I notice that no dependency change affects any of the versions to the build process up to Disco (3.5.27.1-10) For intel J5005 (or N5000 on other popular machines ) this bug renders the package useless. Indeed, it crashes immediately at application startup. Note that this affects rdependencies such as evince, djview4. I suggest upgrading the version available to Bionic LTS as part of the development hardware stack long term support. Patch released under 3.5.27.1-11 solves it. (Check reproducibility) Yours sincerly, Milvi ** Also affects: evince (Ubuntu) Importance: Undecided Status: New ** Also affects: djview4 (Ubuntu) Importance: Undecided Status: New ** Description changed: [PROBLEM] Djvulibre version 3.5.27.1-8/bionic crashes immediately on intel Atom based processors. (I got a J5005 pentium ). Doesn't crash on a Intel® Core™ i7-7567U. Due to this bug https://sourceforge.net/p/djvu/bugs/293/ , and fixed in commit 8407dd, on the 7th of October 2018. From git tags, it is included in 3.5.27.1-11 (probably version xxx -10, though I cannot see this tag in git history) I notice that no dependency change affects any of the versions to the build process up to Disco (3.5.27.1-10) For intel J5005 (or N5000 on other popular machines ) this bug renders the package useless. Indeed, it crashes immediately at application startup. Note that this affects rdependencies such as evince, djview4. - I suggest upgrading the version available to Bionic LTS as part of the - development hardware stack long term support. Patch released under - 3.5.27.1-11 solves it. (Check reproducibility) + I suggest upgrading the version available for Bionic LTS as part of the + development hardware stack long term support to 3.5.27.1-11. Yours sincerly, Milvi -- 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/1846785 Title: Crashes instantly on launch with Pentium J5005 Processor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djview4/+bug/1846785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846779] [NEW] gsd-housekeeping is regularly opening /etc/fstab and the atime update is causing meta data write fluesh
Public bug reported: gsd-housekeeping is opening /etc/fstab every 60 seconds and because it is being opened without the O_NOATIME flag the access time updates are causing regular meta data flushes. On an idle laptop this can cause the HDD to spin up, flush write and spin down every 60 seconds. This consumes power unnecessarily. I've traced this using health-check for 15 minutes of activity: sudo heath-check -p gsd-housekeeping -d 900 -f -r -v > gnome-gsd- househeeping-15.min See attached log. Running strace on the process will show that the open of /etc/fstab does not use O_NOATIME, hence atime is being updated on the file each time it is accessed, causing dirtying of metadata for this file and hence the dirty metadata has to be flushed back periodically. Can this be fixed to save some power. I've estimated it can save ~0.1 Watts on my Lenovo x220. ** Affects: gnome-settings-daemon (Ubuntu) Importance: High Status: New ** Attachment added: "capture of gsd-housekeeping activity using heath-check tool" https://bugs.launchpad.net/bugs/1846779/+attachment/5294354/+files/gnome-gsd-housekeeping-15min.log ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => High -- 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/1846779 Title: gsd-housekeeping is regularly opening /etc/fstab and the atime update is causing meta data write fluesh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1846779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846776] Re: Renaming a desktop item causes the shell to hang
Upstream issue https://gitlab.gnome.org/World/ShellExtensions/desktop- icons/issues/153 ** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues #153 https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/153 ** Also affects: gnome-shell-extension-desktop-icons via https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/153 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1846776 Title: Renaming a desktop item causes the shell to hang To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1846776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846776] [NEW] Renaming a desktop item causes the shell to hang
Public bug reported: Right click on a desktop icon and rename it: - The shell will hang and there's no way to recover it ** Affects: gnome-shell-extension-desktop-icons Importance: Unknown Status: Unknown ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1846776 Title: Renaming a desktop item causes the shell to hang To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1846776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846771] [NEW] gnome-settings-daemon opens /usr/share/zoneinfo/* every 30 seconds or so
Public bug reported: I've been trying to figure out why my HDD keeps on flushing metadata out every minute on an idle laptop and discovered that gsd-color opens /usr/share/zoneinfo/Europe/London on my machine at regular intervals. This causes the access time (atime) to be updated causing a metadata flush afterwards. On an idle laptop this makes the HDD spin up, write data and then spin down again. This consumes power. Can this periodic open/closing be fixed or at least try to use O_NOATIME on the opening to reduce the metadata atime updates? I diagnosed this by running: sudo fnotifystat -v -x/sys,/proc,/home one can see that the gsd-color is opening and closing the file. Looking deeper, I used health-check on gsd-color to gather the attached activity log of 5 minutes of activity of gsd-color on the idle machine. To capture the activity I used: sudo health-check -p gsd-color -d 300 -f -r -v > gnome-gsd-color- 5min.log I'm pretty sure that opening the zoneinfo file with O_NOATIME will avoid the metadata atime flushes and because the data has not changed on disk it should avoid the HDD spinup/spindown cycling. Alternatively, can the regular zoneinfo reads be avoided to save power? This seems like an identical bug as: https://launchpad.net/bugs/1846768 ** Affects: gnome-settings-daemon (Ubuntu) Importance: High Status: New ** Attachment added: "capture of gnome-gsd-color activity using heath-check tool" https://bugs.launchpad.net/bugs/1846771/+attachment/5294348/+files/gnome-gsd-color-5min.log ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => High ** Description changed: I've been trying to figure out why my HDD keeps on flushing metadata out - every minute on an idle laptop and discovered that gnome-gsd-color opens + every minute on an idle laptop and discovered that gsd-color opens /usr/share/zoneinfo/Europe/London on my machine at regular intervals. This causes the access time (atime) to be updated causing a metadata flush afterwards. On an idle laptop this makes the HDD spin up, write data and then spin down again. This consumes power. Can this periodic open/closing be fixed or at least try to use O_NOATIME on the opening to reduce the metadata atime updates? I diagnosed this by running: sudo fnotifystat -v -x/sys,/proc,/home - one can see that the gnome-settings-daemon is opening and closing the - file. + one can see that the gsd-color is opening and closing the file. - Looking deeper, I used health-check on gnome-gsd-color to gather the - attached activity log of 5 minutes of activity of gnome-gsd-color on the - idle machine. + Looking deeper, I used health-check on gsd-color to gather the attached + activity log of 5 minutes of activity of gsd-color on the idle machine. To capture the activity I used: - sudo health-check -p gnome-gsd-color -d 300 -f -r -v > gnome-gsd-color- + sudo health-check -p gsd-color -d 300 -f -r -v > gnome-gsd-color- 5min.log I'm pretty sure that opening the zoneinfo file with O_NOATIME will avoid the metadata atime flushes and because the data has not changed on disk it should avoid the HDD spinup/spindown cycling. Alternatively, can the regular zoneinfo reads be avoided to save power? This seems like an identical bug as: https://launchpad.net/bugs/1846768 -- 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/1846771 Title: gnome-settings-daemon opens /usr/share/zoneinfo/* every 30 seconds or so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1846771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1721424] Re: 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is.
It's inconsistent, so very hard to reproduce, but I've experienced it intermittently at least up to 19.04. Maybe close it if it's not reproducible, I'm not sure what is best. On Fri, Oct 4, 2019, 07:01 Paul White <1721...@bugs.launchpad.net> wrote: > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. > > Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. > I'm not sure if I'm moving this to the right package but > > Is this still an issue? Unable to reproduce here with Ubuntu 18.04. > > Paul White > [Ubuntu Bug Squad] > > > ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) > > ** Tags added: artful > > ** Changed in: gnome-settings-daemon (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1721424 > > Title: > 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it > is. > > Status in gnome-settings-daemon package in Ubuntu: > Incomplete > > Bug description: > 4.13.0-12-generic > 17.10 > XPS 9560 > > Sound works fine, headphones or speakers. I initially thought it > didn't, based on a bug I had experienced days ago in 17.04. I tried > closing the lid and re-opening, but it did nothing. Then I watched a > YouTube video about how to fix sound, and HEARD SOUND. > > So I realized the little sound indicator square that pops up when u > press volume up or volume down just isn't "booping" any sound to give > that feedback of the sound level. > > Expected behavior: boops when i press volume up or volume down > Happened: no sound upon volume up or down, volume otherwise appears to > work fine. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1721424/+subscriptions > -- 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/1721424 Title: 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1721424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846768] Re: gnome-calendar opens /usr/share/zoneinfo/* every 60 seconds
Oh, actually, it was doing 10 accesses in 300 seconds, so it's polling every 30 seconds, higher than I first thought. ** Summary changed: - gnome-calendar opens /usr/share/zoneinfo/* every 60 seconds + gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => High -- 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/1846768 Title: gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1846768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846768] [NEW] gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds
Public bug reported: I've been trying to figure out why my HDD keeps on flushing metadata out every minute on an idle laptop and discovered that gnome-calendar opens /usr/share/zoneinfo/Europe/London on my machine every minute. This causes the access time (atime) to be updated causing a metadata flush afterwards. On an idle laptop this makes the HDD spin up, write data and then spin down again. This consumes power. Can this periodic open/closing be fixed or at least try to use O_NOATIME on the opening to reduce the metadata atime updates? I diagnosed this by running: sudo fnotifystat -v -x/sys,/proc,/home one can see that the gnome-calendar is opening and closing the file. Looking deeper, I used health-check on gnome-calendar to gather the attached activity log of 5 minutes of activity of gnome-calendar on the idle machine. One can see it sleeps for ~60 seconds on a poll() system call and every 60 seconds opens and closes the zoneinfo file. To capture the activity I used: sudo health-check -p gnome-calendar -d 300 -f -r -v > gnome-calendar- 5min.log I'm pretty sure that opening the zoneinfo file with O_NOATIME will avoid the metadata atime flushes and because the data has not changed on disk it should avoid the HDD spinup/spindown cycling. Alternatively, can the zoneinfo reads be avoided totally every 60 seconds to save power? ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Attachment added: "capture of gnome-calendar activity using heath-check tool" https://bugs.launchpad.net/bugs/1846768/+attachment/5294333/+files/gnome-calendar-5min.log -- 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/1846768 Title: gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1846768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822351] Re: Nautilus does not open after updating to 19.04
Same experience as julo. Also, I have a storage volume I use to mount manually after boot. If I mount it quickly I have no problems. Sometimes I get into this bug. And sometimes all starred locations on that volume disapper. It appears to be a race between me and the tracker. -- 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/1822351 Title: Nautilus does not open after updating to 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1822351/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747314] Re: gnome-terminal-server --help does not include option --app-id
** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1747314 Title: gnome-terminal-server --help does not include option --app-id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1747314/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846759] [NEW] Ubuntu's evolution-data-server package incompatible with gnome-calendar package
Public bug reported: On reporting an issue in gnome-calendar, I was told "GNOME Calendar 3.34 requires EDS 3.34 running in the host system.". Ubuntu has 3.32. See: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/464#note_617797 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.2-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 4 08:00:32 2019 InstallationDate: Installed on 2019-07-31 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2019-09-22T11:01:00.065291 ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- 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/1846759 Title: Ubuntu's evolution-data-server package incompatible with gnome- calendar package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1846759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721424] Re: 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is.
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. I'm not sure if I'm moving this to the right package but Is this still an issue? Unable to reproduce here with Ubuntu 18.04. Paul White [Ubuntu Bug Squad] ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) ** Tags added: artful ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- 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/1721424 Title: 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1721424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721424] [NEW] 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is.
You have been subscribed to a public bug: 4.13.0-12-generic 17.10 XPS 9560 Sound works fine, headphones or speakers. I initially thought it didn't, based on a bug I had experienced days ago in 17.04. I tried closing the lid and re-opening, but it did nothing. Then I watched a YouTube video about how to fix sound, and HEARD SOUND. So I realized the little sound indicator square that pops up when u press volume up or volume down just isn't "booping" any sound to give that feedback of the sound level. Expected behavior: boops when i press volume up or volume down Happened: no sound upon volume up or down, volume otherwise appears to work fine. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- 17.10 Sound Indicator Applet doesn't "boop" to let me know how loud it is. https://bugs.launchpad.net/bugs/1721424 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846742] [NEW] Dock location moves dock to wrong screen
Public bug reported: When my laptop is on its dock there is an option to select which monitor has the application dock. Selecting my external monitor moves the dock to my laptop's built in display and selecting built-in display moves the dock to my external monitor. Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gnome-control-center: Installed: 1:3.34.0.1-1ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 4 13:04:00 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-10-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1846742 Title: Dock location moves dock to wrong screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1846742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846718] [NEW] Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key
Public bug reported: Currently, this feature is incomplete, pressing and holding the Super key should display numbers [1-9] on the dock icons before actually pressing any number key. Steps to reproduce the bug: 1. Press and hold the Super key 2. Notice that no numbers appear on the dock icons 3. Press 0 (zero) key while still holding the Super key 4. Numbers appear on the dock icons for 2 seconds then disappear 5. Press any number key [1-9] that corresponds to an icon 6. Numbers appear on the dock icons for 2 seconds then disappear and the app launches What should happen: Numbers should appear on the dock icons while holding the Super key before pressing any number key in order to choose which number key to press to launch the corresponding app. I believe that's how this feature is supposed to work. And that's how it is working in Unity7 in Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Oct 4 13:21:32 2019 InstallationDate: Installed on 2018-11-29 (308 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (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-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1846718 Title: Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1846718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845578] Re: Power indicator doesn't show when charging
** Package changed: 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/1845578 Title: Power indicator doesn't show when charging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845578] [NEW] Power indicator doesn't show when charging
You have been subscribed to a public bug: This problem is intermittent, I have not found a pattern. Sometimes, when I plug my laptop into AC, the battery icon in the top right of the screen doesn't show the charging (lightning) symbol. Sometimes it stays this way until I restart, sometimes it shows the lightning bolt when it increases a % point. Description:Ubuntu 19.04 Release:19.04 apt-cache policy pkgname N: Unable to locate package pkgname ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment disco -- Power indicator doesn't show when charging https://bugs.launchpad.net/bugs/1845578 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843887] Re: egfault at ... error 6 in libglib-2.0.so
** Package changed: ubuntu => glib2.0 (Ubuntu) ** Tags added: disco ** Summary changed: - egfault at ... error 6 in libglib-2.0.so + segfault at ... error 6 in libglib-2.0.so -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1843887 Title: segfault at ... error 6 in libglib-2.0.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1843887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845302] Re: cannot click on others opened applications while the "application not responding" dialog is opened
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Tags added: bionic -- 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/1845302 Title: cannot click on others opened applications while the "application not responding" dialog is opened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845302/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard
** Changed in: oem-priority Importance: Undecided => High -- 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/1845163 Title: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846177] Re: 1910 Tap the sensor in the login window
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Tags removed: login pad touch ** Tags added: eoan -- 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/1846177 Title: 1910 Tap the sensor in the login window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843887] [NEW] egfault at ... error 6 in libglib-2.0.so
You have been subscribed to a public bug: Ubuntu 19.04 after waking up I get the following errors. Sometimes the laptop does not wake up. (I expect it to wake up) --- BIOS contains WGDS but no WRDS --- [ 4695.737914] geoclue[1309]: segfault at 20 this is the dmesg output (only after suspend). [ 4690.382631] PM: suspend entry (deep) [ 4690.382632] PM: Syncing filesystems ... done. [ 4690.641807] rfkill: input handler enabled [ 4690.666176] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 4690.667819] OOM killer disabled. [ 4690.667819] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 4690.669009] printk: Suspending console(s) (use no_console_suspend to debug) [ 4690.884850] wlp5s0: deauthenticating from 0e:8d:cb:6e:3e:4e by local choice (Reason: 3=DEAUTH_LEAVING) [ 4691.015894] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 4691.017317] sd 0:0:0:0: [sda] Stopping disk [ 4691.420328] ACPI: EC: interrupt blocked [ 4691.541129] ACPI: Preparing to enter system sleep state S3 [ 4691.544137] ACPI: EC: event blocked [ 4691.544138] ACPI: EC: EC stopped [ 4691.544139] PM: Saving platform NVS memory [ 4691.544188] Disabling non-boot CPUs ... [ 4691.544807] IRQ 157: no longer affine to CPU1 [ 4691.545841] smpboot: CPU 1 is now offline [ 4691.550093] smpboot: CPU 2 is now offline [ 4691.554206] smpboot: CPU 3 is now offline [ 4691.558467] smpboot: CPU 4 is now offline [ 4691.562523] smpboot: CPU 5 is now offline [ 4691.566191] IRQ 128: no longer affine to CPU6 [ 4691.567207] smpboot: CPU 6 is now offline [ 4691.571194] IRQ 125: no longer affine to CPU7 [ 4691.572245] smpboot: CPU 7 is now offline [ 4691.575342] IRQ 124: no longer affine to CPU8 [ 4691.576453] smpboot: CPU 8 is now offline [ 4691.579601] IRQ 23: no longer affine to CPU9 [ 4691.579606] IRQ 122: no longer affine to CPU9 [ 4691.580654] smpboot: CPU 9 is now offline [ 4691.584036] IRQ 127: no longer affine to CPU10 [ 4691.584045] IRQ 132: no longer affine to CPU10 [ 4691.584052] IRQ 152: no longer affine to CPU10 [ 4691.585080] smpboot: CPU 10 is now offline [ 4691.588113] IRQ 123: no longer affine to CPU11 [ 4691.589175] smpboot: CPU 11 is now offline [ 4691.598456] ACPI: Low-level resume complete [ 4691.598615] ACPI: EC: EC started [ 4691.598616] PM: Restoring platform NVS memory [ 4691.604642] Enabling non-boot CPUs ... [ 4691.604739] x86: Booting SMP configuration: [ 4691.604741] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 4691.610214] unchecked MSR access error: WRMSR to 0x10f (tried to write 0x) at rIP: 0xb9873fc8 (native_write_msr+0x8/0x30) [ 4691.610217] Call Trace: [ 4691.610228] intel_pmu_cpu_starting+0x87/0x260 [ 4691.610235] ? x86_pmu_dead_cpu+0x30/0x30 [ 4691.610241] x86_pmu_starting_cpu+0x1a/0x30 [ 4691.610247] cpuhp_invoke_callback+0x99/0x540 [ 4691.610254] notify_cpu_starting+0x58/0x70 [ 4691.610260] start_secondary+0xed/0x200 [ 4691.610265] secondary_startup_64+0xa4/0xb0 [ 4691.610515] cache: parent cpu1 should not be sleeping [ 4691.610633] intel_pstate: Disabling energy efficiency optimization [ 4691.610770] microcode: sig=0x906ea, pf=0x20, revision=0x84 [ 4691.615411] microcode: updated to revision 0xb4, date = 2019-04-01 [ 4691.615654] CPU1 is up [ 4691.615708] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 4691.617138] cache: parent cpu2 should not be sleeping [ 4691.622352] CPU2 is up [ 4691.622403] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 4691.623838] cache: parent cpu3 should not be sleeping [ 4691.629075] CPU3 is up [ 4691.629122] smpboot: Booting Node 0 Processor 4 APIC 0x8 [ 4691.630557] cache: parent cpu4 should not be sleeping [ 4691.635753] CPU4 is up [ 4691.635805] smpboot: Booting Node 0 Processor 5 APIC 0xa [ 4691.637241] cache: parent cpu5 should not be sleeping [ 4691.642570] CPU5 is up [ 4691.642646] smpboot: Booting Node 0 Processor 6 APIC 0x1 [ 4691.644329] cache: parent cpu6 should not be sleeping [ 4691.644569] microcode: sig=0x906ea, pf=0x20, revision=0xb4 [ 4691.645446] CPU6 is up [ 4691.645504] smpboot: Booting Node 0 Processor 7 APIC 0x3 [ 4691.646935] cache: parent cpu7 should not be sleeping [ 4691.647519] CPU7 is up [ 4691.647565] smpboot: Booting Node 0 Processor 8 APIC 0x5 [ 4691.648981] cache: parent cpu8 should not be sleeping [ 4691.649601] CPU8 is up [ 4691.649646] smpboot: Booting Node 0 Processor 9 APIC 0x7 [ 4691.651097] cache: parent cpu9 should not be sleeping [ 4691.651760] CPU9 is up [ 4691.651803] smpboot: Booting Node 0 Processor 10 APIC 0x9 [ 4691.653237] cache: parent cpu10 should not be sleeping [ 4691.653932] CPU10 is up [ 4691.653977] smpboot: Booting Node 0 Processor 11 APIC 0xb [ 4691.655415] cache: parent cpu11 should not be sleeping [ 4691.656156] CPU11 is up [ 4691.690038] ACPI: Waking up from system sleep state S3 [ 4691.697408] ACPI: button: The lid device is not compliant to SW_LID. [ 4691.701755] ACPI: EC: interrupt unblocked [ 4691.754868] ACPI: EC: event unblocked [ 4691.756283] sd
[Bug 1845302] [NEW] cannot click on others opened applications while the "application not responding" dialog is opened
You have been subscribed to a public bug: I cannot click on others opened applications while the "application not responding" dialog is opened in other application. To reproduce it: 1) upload a file of about 80 MB on a web server. 2) Open it with sublimetext3 through the sublime's SFTP plugin. 3) Save the file: the application will "freeze" until it finished to upload the modified file and the "application not responding" dialog will appear. While this dialog is opened, you cannot click on the others applications. lsb_release -rd: Description:Ubuntu 18.04.3 LTS Release:18.04 It's a fresh install. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- cannot click on others opened applications while the "application not responding" dialog is opened https://bugs.launchpad.net/bugs/1845302 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846177] [NEW] 1910 Tap the sensor in the login window
You have been subscribed to a public bug: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Dell Inspiron 3180 Laptop Touch on the sensor does not work in the login window. Pressing works only with the buttons on the sensor. It works in the system itself. This issue always occurs when the computer starts or when you log out of the account. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment login pad touch -- 1910 Tap the sensor in the login window https://bugs.launchpad.net/bugs/1846177 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 293832]
Thanks for sharing such a informative blog. It is really helpful for us. Keep sharing such informative blogs again. Office Com Setup - https://www.office-com-setup.com/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/293832 Title: printer prints page at wrong position, page cut To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/293832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846461] Re: Disconcerting Folder/Selection flashing when deleting files/folders
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1846461 Title: Disconcerting Folder/Selection flashing when deleting files/folders To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1846461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
Curious. I was looking at preparing a fix for Ubuntu 18.04 but in my initial setup for backporting have found that I can't reproduce the bug with Gnome 3.28. Though this is now with Nvidia driver 430.50 too. Is anyone seeing this bug in Ubuntu 18.04? If so then please tell me what Nvidia driver you are using. ** Changed in: mutter (Ubuntu Bionic) Status: Confirmed => Incomplete -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828491] Re: gnome-calendar not listed as a calendar app in default app settings
** Changed in: gnome-calendar 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/1828491 Title: gnome-calendar not listed as a calendar app in default app settings To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1828491/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
