[Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I am seeing similar interactivity issues on fully updated 22.04 on a Dell Precision laptop with Nvidia + X11 that started a day or so ago. Most noticeable in the terminal with lag/stuttering and seemingly lost keyboard inputs, but also affecting other apps with stuttering keyboard inputs and sometimes seemingly lost mouse clicks. I will try downgrading mutter and suggested. -- 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/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2018433] [NEW] display resolution stuck on 93Hz
Public bug reported: The display settings are stuck at 2560x1440 x 93Hz xrandr says: xrandr: Failed to get size of gamma for output default Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440 default connected primary 2560x1440+0+0 0mm x 0mm 2560x1440 93.00* ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 3 16:09:38 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-09 (298 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2018433 Title: display resolution stuck on 93Hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2012135] Re: Nautilus does not resize window when WIN+left or right arrow pressed
Hi Paul, On Sat, 18 Mar 2023 at 16:15, Paul White <2012...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You have told us about your installation or the version > of Ubuntu that you are using. > > Please execute the following command only once, as it will automatically > gather debugging information, in a terminal: > > apport-collect 2012135 > > and then change the status of the bug back to 'New'. > Done! > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > I'll try to remember to do that in future :) BW, Ian -- -- ACCU - Professionalism in programming - http://www.accu.org -- My writing - https://sites.google.com/site/ianbruntlett/ -- Free Software page - https://sites.google.com/site/ianbruntlett/home/free-software -- 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/2012135 Title: Nautilus does not resize window when WIN+left or right arrow pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012135] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2012135/+attachment/5655331/+files/ProcEnviron.txt ** Changed in: nautilus (Ubuntu) Status: Incomplete => 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/2012135 Title: Nautilus does not resize window when WIN+left or right arrow pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012135] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2012135/+attachment/5655330/+files/ProcCpuinfoMinimal.txt -- 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/2012135 Title: Nautilus does not resize window when WIN+left or right arrow pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012135] Re: Nautilus does not resize window when WIN+left or right arrow pressed
apport information ** Tags added: apport-collected focal ** Description changed: Nautilus does not resize window when WIN+left or right arrow pressed. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.25 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + GsettingsChanges: + + InstallationDate: Installed on 2023-03-18 (0 days ago) + InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) + Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 + Tags: focal + Uname: Linux 5.15.0-67-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + usr_lib_nautilus: ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2012135/+attachment/5655329/+files/Dependencies.txt -- 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/2012135 Title: Nautilus does not resize window when WIN+left or right arrow pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2012135] [NEW] Nautilus does not resize window when WIN+left or right arrow pressed
Public bug reported: Nautilus does not resize window when WIN+left or right arrow pressed. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2012135 Title: Nautilus does not resize window when WIN+left or right arrow pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2012135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
.. and the PPA means I am now running the 510 drivers successfully. Thanks again, Martin. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
It turns out that I may have misunderstood - the same thing happens for me when telling MATE Tweak that I want to use Compiz rather than Marco as my window manager. The switch to Compiz certainly happens (I am reminded of why I stopped using it..) and it is sticky between reboots. So either it's not just a Marco thing or some part of Marco is retained when using Compiz. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
Thank you, Martin. I do indeed have Marco with the 'adaptive compositor' (it's the default, I think...) It's been ages since I used Compiz, but... :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959599] [NEW] gnome-shell freezes upon trying to login
Public bug reported: On Impish 21.10, gnome-shell freezes up when trying to login, specifically after I have typed in my password and hit enter. I have seen this both when logging in after the display shuts itself off after whatever the automatic timeout is, and also after manually locking the screen. This is the stack trace I see from gnome-shell at the time it freezes up: https://pastebin.ubuntu.com/p/9RcnnT32Nf/ The freeze was at 09:58:16 in the log. In this specific instance I just force rebooted the machine, in the other instance this happened to me, I let it sit and see if it would recover but it had not recovered after an hour or two. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1959599 Title: gnome-shell freezes upon trying to login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Also I'm not sure I agree with jdstrand's apparmor profile which includes: /run/snapd.socket rw, which I don't think we want to grant to any PDF file opened with evince? -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1943434] [NEW] gnome-shell periodicall becomes extreemely active and eats CPU like crazy
Public bug reported: At seemingly random intervals throughout the day gnome-shell becomes very active, the CPU gets very busy and the fans kick in because of the large load. I attached health-check to the busy process for 60 seconds and got the following utilization stats: sudo health-check -p gnome-shell [sudo] password for cking: CPU usage (in terms of 1 CPU): PID ProcessUSR% SYS% TOTAL% Duration 3271 gnome-shell 29.82 11.20 41.02 60.00 (high load) Page Faults: PID Process Minor/secMajor/secTotal/sec 3271 gnome-shell 4.60 0.00 4.60 Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 3271 gnome-shell 8282.8916.93 8299.83 (high) 3294 gnome-shell909.89 1.40 911.29 (quite high) 3305 gnome-shell 7.35 0.00 7.35 (low) 3300 gnome-shell 7.12 0.00 7.12 (low) 3299 gnome-shell 6.60 0.00 6.60 (low) 3303 gnome-shell 6.57 0.00 6.57 (low) 3279 gnome-shell 5.97 0.00 5.97 (low) 3304 gnome-shell 5.95 0.00 5.95 (low) 3301 gnome-shell 5.37 0.00 5.37 (low) 3298 gnome-shell 5.07 0.00 5.07 (low) 3302 gnome-shell 4.97 0.00 4.97 (low) 3277 gnome-shell 3.18 0.00 3.18 (low) 3280 gnome-shell 0.27 0.02 0.28 (very low) 3286 gnome-shell 0.18 0.03 0.22 (very low) 3288 gnome-shell 0.18 0.00 0.18 (very low) 3285 gnome-shell 0.18 0.00 0.18 (very low) 3287 gnome-shell 0.15 0.02 0.17 (very low) Total 9251.8818.40 9270.28 File I/O operations: PID Process Count Op Filename 3271 gnome-shell 2R /usr/share/icons/Yaru/cursors/bottom_side 3271 gnome-shell 1C /usr/share/icons/Yaru/cursors/bottom_side 3271 gnome-shell 1O /usr/share/icons/Yaru/cursors/bottom_side Total 4 Op: O=Open, R=Read, W=Write, C=Close File I/O Operations per second: PID Process Open CloseRead Write 3271 gnome-shell 0.020.020.030.00 System calls traced: PID Process Syscall CountRate/SecTotal μSecs % Call Time 3271 gnome-shell recvmsg 865101441.8150 2874761 0.4511 3271 gnome-shell ioctl 601971003.2706 2474118 0.3883 3271 gnome-shell poll 33430 557.1596 28079642 4.4066 3271 gnome-shell getpid20354 339.2290 594754 0.0933 3271 gnome-shell writev14482 241.3636 655887 0.1029 3271 gnome-shell futex 11787 196.4475 988686 0.1552 3271 gnome-shell write 9189 153.1481 344908 0.0541 3271 gnome-shell read 5981 99.6821 160471 0.0252 3271 gnome-shell mprotect450 7.4999 11522 0.0018 3271 gnome-shell mmap 14 0.2333 843 0.0001 3271 gnome-shell getrusage12 0.2000 357 0.0001 3271 gnome-shell recvfrom 9 0.1500 173 0. 3271 gnome-shell close 4 0.0667 451 0.0001 3271 gnome-shell openat3 0.0500 185 0. 3271 gnome-shell timerfd_create3 0.0500 158 0. 3271 gnome-shell timerfd_settime 3 0.0500 188 0. 3271 gnome-shell newfstatat1 0.0167 38 0. 3271 gnome-shell lseek 1 0.0167 31 0. 3271 gnome-shell restart_syscall 1 0.0167 464 0.0001 3277 gnome-shell inotify_add_watch60 1. 4858 0.0008 3277 gnome-shell poll 15 0.2500 55977520 8.7846 3277 gnome-shell restart_syscall 1 0.0167
[Bug 1943434] Re: gnome-shell periodicall becomes extreemely active and eats CPU like crazy
** Attachment added: "ASCII log of health-check analysis" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943434/+attachment/5524939/+files/health-check-report.log -- 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/1943434 Title: gnome-shell periodicall becomes extreemely active and eats CPU like crazy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1939938] Re: dialog asking for restart appears on close of rhythmbox
This has occurred at 3 fresh installs of 21.10 on this laptop -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1939938 Title: dialog asking for restart appears on close of rhythmbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1939938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934761] Re: gnome keyboard settings panel enforces single iso-level3-shift key
This issue was fixed in https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/994 which avoids changing `xkb-options` unless the Alternate Characters dialog is opened. (That was originally part of MR 910, but was split off so it could be merged without being blocked on design concerns.) I've just added an additional commit to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/910 to also not change `xkb-options` on opening the dialog unless the setting is actually changed, with is less necessary but probably an improvement. -- 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/1934761 Title: gnome keyboard settings panel enforces single iso-level3-shift key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1939938] [NEW] dialog asking for restart appears on close of rhythmbox
Public bug reported: following last update to rhythmbox dialog box now appears at every closure of rhythmbox from top bar Ubuntu 21.10 image from 13/08 lenovo thinkpad T430 250gb ssd 16gb ram ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1939938 Title: dialog asking for restart appears on close of rhythmbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1939938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870597] Re: libinput says: scheduled expiry is in the past... your system is too slow
I have the same sort of issue... Ubuntu 20.04 (Ubuntu Studio spin). >From Xorg.0.log [ 13886.780] (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-9ms), your system is too slow [ 13926.080] (EE) client bug: timer event4 debounce: scheduled expiry is in the past (-15ms), your system is too slow Video freezes, external display will go black or the system will crash (I expect it is only X that crashes because if I am editing audio in Audacity, the audio will continue to play, yet I will have to hard reset my machine to regain control. Keyboard and mouse input are dead as part of X system. I have not tried remoting in to it from another machine yet. Running a MacBook Pro retina mid 2012 with 8GB RAM and the i7 processor with GeForce GT 650M Mac Edition graphics chip at 4K@30Hz output. If I have the system running powersave, I get the hard crashes, with ondemand governor I get the timeouts. Going to performance causes the fans to run all the time which is loud. -- 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/1870597 Title: libinput says: scheduled expiry is in the past... your system is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926794] [NEW] package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed
Public bug reported: Automatic upgrade failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0 2.48.2-0ubuntu4.8 ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Fri Apr 30 17:25:11 2021 DuplicateSignature: package:libglib2.0-0:2.48.2-0ubuntu4.8:11.0957:dependency problems - leaving triggers unprocessed ErrorMessage: 11.0957:dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2021-04-30 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: glib2.0 Title: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2021-04-30 (0 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 need-duplicate-check xenial -- 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/1926794 Title: package libglib2.0-0 2.48.2-0ubuntu4.8 failed to install/upgrade: 11.0957:dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926794/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474126/+files/prevboot.txt -- 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/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474125/+files/lspci.txt ** Attachment removed: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474124/+files/prevboot.txt -- 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/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
Here's lspci -- 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/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
Here's lspci -- 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/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly
Okay, so this time when it happened at Sun Mar 7 02:44 AM UTC 2021, here are the logs. I did not find any crash files in /var/crash, and there were no results for my whoopsie-id either. The journalctl output is attached ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474124/+files/prevboot.txt -- 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/1912246 Title: [nvidia] gnome-shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy
Here's lspci ** Attachment added: "lspci -kv" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1912246/+attachment/5471916/+files/lspci.txt ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy
Hey so sorry I missed that you wanted me to run those commands before, but it happened again this morning and here are the requested logs and lspci output. Note that I stripped out all the messages from snapd since I have debug mode enabled and it's extremely noisy, but if you think snapd could be at all at fault here I would love to know how and can share more info about that :-D ** Attachment added: "journalctl --no-hostname -b-1 --no-pager | grep -v 'snapd['" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1912246/+attachment/5471915/+files/prevboot.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/1912246 Title: [nvidia] gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy
So I disabled both ubuntu-dock and the desktop icons extensions and still see the freezes, here's a log of gnome-shell: https://pastebin.ubuntu.com/p/CXCfTVtkMJ/ ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: [nvidia] gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916029] [NEW] [nvidia] gnome-shell freezes randomly on login/startup
Public bug reported: The symptoms here for me are exactly the same as described in https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/+bug/1912246 where after starting up my Groovy system with X11 and proprietary NVIDIA drivers the desktop session just hangs for a minute or so. However I have the desktop-icons extension disabled now, so I think it's highly unlikely that that extension is the cause of this hang. Looking through the gnome-shell logs, I see some related things for the ubuntu- dock extension: Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the widget [0x5595d2b3cb40 Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive "dashtodockContainer"] which is not in the stage. Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called for actor 0x5595d2b3cb40/dashtodockContainer which isn't a descendent of the stage! Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the widget [0x5595d2b5bfd0 Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive "dashtodockContainer"] which is not in the stage. Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called for actor 0x5595d2b5bfd0/dashtodockContainer which isn't a descendent of the stage! Feb 18 06:19:59 gnome-shell[12469]: st_widget_get_theme_node called on the widget [0x5595d2ab2100 Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.bottom:insensitive "dashtodockContainer"] which is not in the stage. Feb 18 06:19:59 gnome-shell[12469]: Spurious clutter_actor_allocate called for actor 0x5595d2ab2100/dashtodockContainer which isn't a descendent of the stage! Feb 18 06:19:59 gnome-shell[12469]: Bogus presentation time 0 travelled back in time, using current time. full log at https://pastebin.ubuntu.com/p/z8jChdF4gw in addition to the ubuntu-bug auto-collected stuff ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 18 06:28:24 2021 InstallationDate: Installed on 2019-07-05 (594 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to groovy on 2021-01-16 (33 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1916029 Title: [nvidia] gnome-shell freezes randomly on login/startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1916029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy
Unfortunately, I seem to be on that version of gnome-shell-extension- desktop-icons and still experience the freeze when I enable the desktop icons extension. Here's the dpkg output and gnome-shell logs: https://pastebin.ubuntu.com/p/yqDTV5KBmC/ ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => 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/1912246 Title: gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy
So indeed after enabling _only_ the Desktop Icon extension I experienced a freeze. Here are the logs: https://pastebin.ubuntu.com/p/XwJS7N4tF5/ ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy
So after a full day of usage yesterday I did not see the freeze/crash at all, so it does indeed appear to be caused by one of the extensions bundled with Ubuntu. Should I try just enabling them one-by-one using the Extensions app? I can't remember what all Extensions are enabled by default, but I am fairly confident the "Desktop Icons" extension was enabled so I'll start with enabling that one today and see if the freezes reproduce. -- 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/1912246 Title: gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy
Well for the short bit that I've been using the system after disabling all the extensions through the Extensions app, I have not experienced any freeze. I will report back after the end of the day if I see any more freezes though. Interestingly, after disabling all Extensions, I have no more dock unless I press the "super" button in which case it momentarily appears on the left, is this intended? I guess I seem to remember "stock gnome" had a dock that was permanently on the screen... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] Re: gnome-shell freezes randomly after upgrading to groovy
Hi Daniel, I disabled all of these extensions, and then rebooted the machine and still a minute or two after logging in again experienced the freeze. Here are the logs from gnome-shell: https://pastebin.ubuntu.com/p/YKtMQ2qy4g/ Note, I only disabled the extensions located in ~/.local/share/gnome- shell/extensions, I didn't modify anything in /usr/share/gnome- shell/extensions, as I see there is at least one traceback related to the desktop-icons@csoriano extension (which I don't recall installing so I assume that is an Ubuntu provided extension?). ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1912246 Title: gnome-shell freezes randomly after upgrading to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912246] [NEW] gnome-shell freezes randomly after upgrading to groovy
Public bug reported: I recently upgrading from Focal to Groovy, and use proprietary NVIDIA drivers with X11 with otherwise standard GNOME, but some extensions installed. I see frequently errors relating to the dash-to-dock extension which I'm not sure are related, but I also see that gnome- shell freezes up for a minute or so, and the logs have this to say: https://pastebin.ubuntu.com/p/trWJZfZ77Z/ BTW this is the error from the dash-to-dock extension if relevant: Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 == Jan 18 07:50:24 gnome-shell[10186]: #0 7ffc8e0a3c00 I /home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (e02dce21a0 @ 208) Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. however that seems to be an issue reported upstream at https://github.com/micheleg/dash-to-dock/issues/1360 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 18 09:51:15 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-05 (563 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 RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: I recently upgrading from Focal to Groovy, and use proprietary NVIDIA drivers with X11 with otherwise standard GNOME, but some extensions installed. I see frequently errors relating to the dash-to-dock extension which I'm not sure are related, but I also see that gnome- shell freezes up for a minute or so, and the logs have this to say: - - Jan 18 09:47:12 gnome-shell[10186]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct. - Jan 18 09:47:12 gnome-shell[10186]: Object Meta.BackgroundActor (0x56536b1a0350), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. - Jan 18 09:47:12 gnome-shell[10186]: == Stack trace for context 0x565369c02220 == - Jan 18 09:47:12 gnome-shell[10186]: #0 7ffc8e0a19e0 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:574 (13b00fba4060 @ 25) - Jan 18 09:47:12 gnome-shell[10186]: #1 56536ebcd728 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:212 (150ef6731510 @ 85) - Jan 18 09:47:12 gnome-shell[10186]: #2 56536ebcd6a0 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (150ef6731650 @ 12) - Jan 18 09:47:12 gnome-shell[10186]: #3 56536ebcd618 i resource:///org/gnome/shell/ui/main.js:251 (13b00fbbed30 @ 12) - Jan 18 09:47:12 gnome-shell[10186]: invalid (NULL) pointer instance - Jan 18 09:47:12 gnome-shell[10186]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed - Jan 18 09:47:12 gnome-shell[10186]: Object Meta.BackgroundActor (0x56536b1a06d0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. - Jan 18 09:47:12 gnome-shell[10186]: == Stack trace for context 0x565369c02220 == - Jan 18 09:47:12 gnome-shell[10186]: #0 7ffc8e0a19e0 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:574 (13b00fba4060 @ 25) - Jan 18 09:47:12 gnome-shell[10186]: #1 56536ebcd728 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:212 (150ef6731510 @ 85) - Jan 18 09:47:12 gnome-shell[10186]: #2 56536ebcd6a0 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (150ef6731650 @ 12) - Jan 18 09:47:12 gnome-shell[10186]: #3 56536ebcd618 i resource:///org/gnome/shell/ui/main.js:251 (13b00fbbed30 @ 12) - Jan 18 09:47:12 gnome-shell[10186]: invalid (NULL) pointer instance - Jan 18 09:47:12 gnome-shell[10186]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed - Jan 18 09:47:12 gnome-shell[10186]: Object Meta.BackgroundActor (0x56536b1a0a50), has been already deallocated — impossible to access it. This might be caused
[Bug 1903334] [NEW] Xsession does not invoke the correct shell profile script
Public bug reported: The gdm3 package comes with a session launcher script /etc/gdm3/Xsession which starts everything up. In that script it unconditionally executes $HOME/.profile (if it exists). But this is not necessarily the correct shell startup file. If your shell is bash and you have a .bash_login file, tty logins will use that and never touch .profile; but logins via /etc/gdm3/Xsession won't execute .bash_login and therefore will not set up your correct environment. If your shell is csh then .profile was never in the picture and you need to instead execute .login and .cshrc (which of course are in a different syntax that the /bin/bash which executes Xsession won't understand). I understand this file comes from upstream, so the bug should probably be filed upstream as well. But Ubuntu doesn't have to include this Xsession in the gdm3 package and could supply its own. (Red Hat have written their own and supply it in their xorg-x11-xinit package; their gdm package simply symlinks that from /etc/gdm. They've solved the profile problem by making the script execute: exec -l $SHELL -c "[command]" where [command] is a shell command that starts up the session.) In fact Ubuntu already does have a more comprehensive Xsession system included as part of the x11-common package. So the Xsession supplied with gdm3 is redundant. (Unfortunately that other Xsession also does not set up your environment correctly; it doesn't seem to call any profile at all.) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1903334 Title: Xsession does not invoke the correct shell profile script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1903334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901429] Re: Bluetooth disabled even after being enabled
Is there any other way that I'm not thinking of to fix this? ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/gnome-bluetooth/+question/693642 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1901429 Title: Bluetooth disabled even after being enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1901429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901429] [NEW] Bluetooth disabled even after being enabled
Public bug reported: Whether going into the settings and enabling the bluetooth or using rfkill to unblock it, the bluetooth remains disabled. I've added myself to the bluetooth group and this did work until the next restart. After blocking it the indicator icon shows up, but upon unblocking again the icon shows up and then disappears ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: Invalid ** Project changed: launchpad => gnome-bluetooth (Ubuntu) ** Description changed: Whether going into the settings and enabling the bluetooth or using rfkill to unblock it, the bluetooth remains disabled. I've added myself - to the bluetooth group and this did work until the next restart. + to the bluetooth group and this did work until the next restart. After + blocking it the indicator icon shows up, but upon unblocking again the + icon shows up and then disappears -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1901429 Title: Bluetooth disabled even after being enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1901429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1891165] [NEW] gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed
Public bug reported: I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. But i got more errors The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but 3.26.1-2ubuntu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. sudo ln -sf /usr/bin/python2.7 /usr/bin/python ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 20:38:08 2020 InstallationDate: Installed on 2020-02-08 (184 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1891165 Title: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1891165/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1887652] [NEW] wayland not available with proprietary nvidia drivers
Public bug reported: With Ubuntu 20.04, GDM 3.34.1 (bundled with Focal), and the proprietary NVIDIA drivers, I am unable to use Wayland to login, and can only use XOrg. Debugging this a little, I found that wayland support is wholesale disabled when proprietary NVIDIA drivers are used by this rule: /lib/udev/rules.d/61-gdm.rules (coming from the gdm3 package), however it seems there may be more to this as well in upstream so this seems to affect mutter as well. To be clear, my system only has NVIDIA graphics, I do not also have an Intel integrated GPU, so this is not a duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: New ** Tags: focal groovy nvidia nvidia-drm.modeset ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1887652 Title: wayland not available with proprietary nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825593] Re: Display scale not remembered when X11 Fractional Scaling is enabled
Thanks folks, this works for me now as well. -- 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/1825593 Title: Display scale not remembered when X11 Fractional Scaling is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] fractional monitor scaling fails due to overlapping monitors
Daniel, it sounds then like you are saying this is a duplicate of 1873403? -- 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/1869042 Title: [nvidia] fractional monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] fractional monitor scaling fails due to overlapping monitors
(the issues here originally were that the screens go black and that I couldn't set the main monitor after changing scaling, for which I filed 1873266, as per your request) -- 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/1869042 Title: [nvidia] fractional monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] Re: [nvidia] with x11 fractional scaling enabled, cannot change main monitor after setting scaling for monitors
** Summary changed: - [nvidia] cannot change main monitor after setting scaling for monitors + [nvidia] with x11 fractional scaling enabled, cannot change main monitor after setting scaling for monitors -- 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/1873266 Title: [nvidia] with x11 fractional scaling enabled, cannot change main monitor after setting scaling for monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] all monitor scaling fails due to overlapping monitors
Okay, so now looking back at this bug, I see that when I have Focal with X11 and the 440 nvidia drivers enabled, I can set scaling to integer multiples without problems, but enabling fractional scaling and then using a fractional scaling results in the black screen problem mentioned in this bug as well as this in the system journal: gnome-control-c[6913]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors overlap ** Summary changed: - [nvidia] all monitor scaling fails due to overlapping monitors + [nvidia] fractional monitor scaling fails due to overlapping monitors -- 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/1869042 Title: [nvidia] fractional monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
Daniel, I just turned off fractional scaling and I no longer have this problem, so for me at least with nvidia drivers and focal, I don't see this bug and instead see 1825593 as you mentioned. -- 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/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] Re: [nvidia] cannot change main monitor after setting scaling for monitors
Also, if I disable Fractional Scaling, it now works to use/apply these settings in any order -- 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/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] Re: [nvidia] cannot change main monitor after setting scaling for monitors
Yes, 'Fractional Scaling' is enabled, sorry I should have specified. I am unable to actually use fractional scaling however due to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042 ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
Hi Daniel, I tried your instructions and there is no difference between ~/.config/monitors.xml and monitors-before.xml. Both files specify the desired configuration, but upon logging in the monitors are in the wrong configuration. Let me know if there's anything else I can try to help debug this issue. -- 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/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Hi Daniel, > Since your setup only uses gnome-shell in the host and not the guest it Host is KDE Plasma, guest is GNOME => I have problems with clipboard when I close virt-manager or shutdown the guest => no problems So if I remove GNOME from the equation, then it's OK. -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Hi Daniel, Thank you for coming back to me so fast. I don't think it's related to either of those bugs you mentioned. This is happening only when I'm running virtual machines and have "virt- manager" opened. Is it a bug in gnome-shell? It's difficult to say. I'm not experiencing the issue with non-desktop VMs (no X) so it might be something in X11. -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1873266/+attachment/5356137/+files/ProcCpuinfoMinimal.txt ** Changed in: mutter (Ubuntu) Status: Incomplete => Opinion ** Changed in: mutter (Ubuntu) Status: Opinion => New -- 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/1873266 Title: cannot change main monitor after setting scaling for monitors w/nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] Re: cannot change main monitor after setting scaling for monitors w/nvidia drivers
apport information ** Tags added: apport-collected focal package-from-proposed ** Description changed: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard-reboot (though I could probably try switching ttys, etc). - This is with focal and focal-proposed enabled. I also have the - proprietary 440 nvidia drivers enabled, and I'm using default gnome with - x11. + This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-07-05 (287 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia + Package: nvidia-graphics-drivers-440 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 + Tags: focal package-from-proposed + Uname: Linux 5.4.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1873266/+attachment/5356136/+files/Dependencies.txt -- 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/1873266 Title: cannot change main monitor after setting scaling for monitors w/nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] [NEW] hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Public bug reported: Could you please try install: - Kubuntu 20.04 Focal desktop on bare metal (laptop) - Upgrade all packages - Install virtualization as usually (qemu-kvm, libvirt, virt-manager) - Install Ubuntu 20.04 inside a VM - upgrade all packages in the VM - Start copying (CTRL+X, CTRL+V) plain text between the Kubuntu on laptop and Ubuntu inside VM? Doesn't take too long - doesn't need to much testing. After a couple of trials, the clipboard will hang and you loose the text in clipboard... I don't remember such issues in past. Copying worked fine when I used virt-manager a couple of years ago. Thank you all great people in Canonical for Ubuntu. Ian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 04:43:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] all monitor scaling fails due to overlapping monitors
Daniel, I filed that issue as https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873266 -- 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/1869042 Title: [nvidia] all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] [NEW] cannot change main monitor after setting scaling for monitors w/nvidia drivers
Public bug reported: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard-reboot (though I could probably try switching ttys, etc). This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1873266 Title: cannot change main monitor after setting scaling for monitors w/nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] all monitor scaling fails due to overlapping monitors
I should point out that the behavior in comment #9 happens when I am using the nvidia 440 drivers. I still cannot use fractional scaling with the nvidia drivers successfully under any ordering, but I can at least use 200% scaling if I set it first, then set the main monitor it works. -- 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/1869042 Title: [nvidia] all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292398] Re: Second screen position isn't saved from one session to another
Just to clarify, I still see this bug with Focal and X11 and nvidia drivers -- 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/1292398 Title: Second screen position isn't saved from one session to another To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] all monitor scaling fails due to overlapping monitors
It is still unfortunately happening to me, but I also have a new permutation of this, my machine also happens to suffer from https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1292398, so when I boot up my machine the incorrect monitor layout is present, and I find that if I first set the main monitor correctly (because it always uses the wrong one for the main monitor), then set scaling to 200% it does work. But if I do the inverse, and first set scaling to 200% then change the main monitor, it does not work and I have to reboot and then first set the main monitor. ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1869042 Title: [nvidia] all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: [nvidia] all monitor scaling fails due to overlapping monitors
Is this perhaps a duplicate of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869750 ? -- 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/1869042 Title: [nvidia] all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: all monitor scaling fails due to overlapping monitors
Actually after testing this out, I was able to use fractional scaling with X11 again by using the nouveau driver instead of the proprietary nvidia driver, which on my machine is at nvidia-440. This is a sufficient work-around for me, it's unfortunate I can't use the proprietary nvidia driver with fractional scaling but nouveau is okay for now. -- 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/1869042 Title: all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: all monitor scaling fails due to overlapping monitors
FWIW, if I switch to using the noveau driver and then login via Wayland, I can enable fractional scaling through Settings and that is successful, but unfortunately then all the text in some apps becomes rather blurry. -- 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/1869042 Title: all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: all monitor scaling fails due to overlapping monitors
Oddly enough I was able to get 200% scaling to work randomly by not quite lining up all the monitors and offsetting them from each other in the settings window. Is there anything I could try manually to unbreak the situation or is there a debian package I could downgrade to in order to get scaling to work again on my system? -- 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/1869042 Title: all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] Re: all monitor scaling fails due to overlapping monitors
Attaching monitors.xml since it doesn't seem that apport picked it up ** Attachment added: "~/.config/monitors.xml from my system" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+attachment/5341610/+files/monitors.xml -- 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/1869042 Title: all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869042] [NEW] all monitor scaling fails due to overlapping monitors
Public bug reported: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 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: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1869042 Title: all monitor scaling fails due to overlapping monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865063] Re: snapd package hangs on deb postinst
Just to be clear, the messages: ``` snapd.failure.service is a disabled or a static unit, not starting it. snapd.snap-repair.service is a disabled or a static unit, not starting it. ``` are normal and harmless. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1865063 Title: snapd package hangs on deb postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1865063/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855872] [NEW] package gimp-data (not installed) failed to install/upgrade: unable to open '/usr/share/gimp/2.0/menus/channels-menu.xml.dpkg-new': Operation not permitted
Public bug reported: Installing from Ubuntu Software store ProblemType: Package DistroRelease: Ubuntu 19.10 Package: gimp-data (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Tue Dec 10 11:45:08 2019 DuplicateSignature: package:gimp-data:(not installed) Unpacking gimp-data (2.10.8-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-65yuY4/13-gimp-data_2.10.8-2_all.deb (--unpack): unable to open '/usr/share/gimp/2.0/menus/channels-menu.xml.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/gimp/2.0/menus/channels-menu.xml.dpkg-new': Operation not permitted InstallationDate: Installed on 2019-12-03 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: gimp Title: package gimp-data (not installed) failed to install/upgrade: unable to open '/usr/share/gimp/2.0/menus/channels-menu.xml.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1855872 Title: package gimp-data (not installed) failed to install/upgrade: unable to open '/usr/share/gimp/2.0/menus/channels-menu.xml.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1855872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853113] Re: 'Convert to RGB working space' dialogue mixed language
Originally assigned to wrong package, sorry - I thought I had selected the right one, but hadn't pressed enough buttons! ** Package changed: nvidia-graphics-drivers-435 (Ubuntu) => gimp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1853113 Title: 'Convert to RGB working space' dialogue mixed language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1853113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852118] Re: Notifications don't have sound
Thanks for your prompt response Sebastien. Sorry i thought i had remembered there being a default notification sound in older versions of Ubuntu/gnome and thought this was a regression. My mistake. -- 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/1852118 Title: Notifications don't have sound To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1852118/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1702368] Re: Mounted sshfs filesystems sometimes prevent suspend
If it's any bit of helpful information, I occasionally have this issue (on 18.04) and it is fixed by a proper shutdown and boot. It seems to happen for me when one of the servers that I sshfs to crashes/becomes unavailable (or something else server side) and the issue persists past the time in which the server is back and functional. -- 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/1702368 Title: Mounted sshfs filesystems sometimes prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1702368/+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 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
[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 1774957] Re: Network icons in status menu disappearing
Looking good on 18.04.1 LTS Desktop. I have installed the patch from comment #23 and the network icon now appears consistently on both the status bar and the status menu. -- 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/1774957 Title: Network icons in status menu disappearing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778607] Re: Snaps with "Other Open Source" license (not SPDX compliant) are listed as Propietary.
This affects a new snap we uploaded with license metadata to the store around December 2018. We uploaded the snap and used the snap store description editor to choose "Other Open Source" software and it shows up as "Proprietary" in gnome-software. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1778607 Title: Snaps with "Other Open Source" license (not SPDX compliant) are listed as Propietary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774957] Re: Network icons in status menu disappearing
According to https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 this is fixed in Gnome Shell 3.30.1 & 3.28.4. Any chance of getting 3.28.4 (or the fix) in 18.04 LTS desktop? -- 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/1774957 Title: Network icons in status menu disappearing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774957/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)
Uncommenting this line worked for me. This bug occurred after a fresh install of 18.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766567] [NEW] rsyslog config of tmpfiles generates bogus log messages
Public bug reported: /usr/lib/tmpfiles.d/00rsyslog.conf (in the rsyslog package) includes these lines: # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - Maybe this overriding works, but it also means that every time tmpfiles runs, we get log messages like this: Apr 24 13:46:37 cue systemd-tmpfiles[28279]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. I suspect the best fix for this is to move the systemd config for /var/log into its own file (/usr/lib/tmpfiles.d/systemd-varlog.conf), then have rsyslog add an empty file (or /dev/null symlink) to suppress it (/etc/tmpfiles.d/systemd-varlog.conf or /run/tmpfiles.d/systemd- varlog.conf). Or just use apt to move the file out of the way when rsyslog is installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsyslog 8.16.0-1ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 24 14:56:42 2018 InstallationDate: Installed on 2018-03-23 (31 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766567 Title: rsyslog config of tmpfiles generates bogus log messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1766567/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1579142] Re: Evince windows cannot be resized after upgrade to Xenial
I am experiencing this on Ubuntu 18.04 with evince 3.28.2-1. A possible regression? -- 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/1579142 Title: Evince windows cannot be resized after upgrade to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1579142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758163] Re: Please remove xchat-gnome from Ubuntu (again)
I deem that it should be removed, it is too much of a maintenance overhead and has way too many issues to be fixed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1758163 Title: Please remove xchat-gnome from Ubuntu (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1758163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1696970] [NEW] softlockup DoS causes systemd-journald.service to abort with SIGABORT
Public bug reported: I was running the new stress-ng softlockup stressor and observed that systemd-journald gets killed with an abort and this corrupts the systemd journal. How to reproduce: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make clean; make sudo ./stress-ng --softlockup 0 -t 360 -v ..and wait for 360 seconds. dmesg shows the following, 100% reproduceable: [ 875.310331] systemd[1]: systemd-timesyncd.service: Watchdog timeout (limit 3min)! [ 875.310740] systemd[1]: systemd-timesyncd.service: Killing process 574 (systemd-timesyn) with signal SIGABRT. [ 875.327289] systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=6/ABRT [ 875.327666] systemd[1]: systemd-timesyncd.service: Unit entered failed state. [ 875.327686] systemd[1]: systemd-timesyncd.service: Failed with result 'watchdog'. [ 875.327917] systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart. [ 875.327954] systemd[1]: Stopped Network Time Synchronization. [ 875.328845] systemd[1]: Starting Network Time Synchronization... [ 875.525071] systemd[1]: Started Network Time Synchronization. [ 875.539619] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT [ 875.544257] systemd-journald[5214]: File /run/log/journal/440e485e550040e3b93b66b2faae8525/system.journal corrupted or uncleanly shut down, renaming and replacing. ** Affects: systemd (Ubuntu) Importance: High Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1696970 Title: softlockup DoS causes systemd-journald.service to abort with SIGABORT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1696970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1696261] [NEW] Settings app items have bad text wrapping
Public bug reported: Ubuntu GNOME 17.04 with GNOME 3.24. gnome-control-center: Installed: 1:3.24.1-0ubuntu1 Candidate: 1:3.24.1-0ubuntu1 What actually happened: When I open settings, I find that my perfectly innocuous Region & Language settings have been kidnapped by a stranger named Lan Guage. I don't know who Mr. Guage is but I would like him to return my settings. What I expected to happen: Find settings app that has not been visited by Lan Guage. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-control-center 1:3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 6 15:57:59 2017 InstallationDate: Installed on 2017-05-30 (7 days ago) InstallationMedia: System76 17.04 "Zesty Zapus" - Release amd64 (20170410) 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 gnome3-ppa third-party-packages zesty ** Attachment added: "Screenshot of Lan Guage" https://bugs.launchpad.net/bugs/1696261/+attachment/4890443/+files/Screenshot%20from%202017-06-06%2015-57-35.png -- 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/1696261 Title: Settings app items have bad text wrapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1696261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
I think this is a systemd/udevd kinda bug isn't it? ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1615685] [NEW] systemd-analyze stats for kernel startup time looks suspect
Public bug reported: I've instrumented a kernel so I can clearly see when processes start and exit, this allows me to see when exactly the kernel has handed off control to userspace. The time the kernel actually takes to initialize compared to the time systemd-analyze reports are different. $ systemd-analyze Startup finished in 16.878s (kernel) + 43.152s (userspace) = 1min 30ms For example: [2.286330] Freeing unused kernel memory: 1532K (b1755000 - b18d4000) [2.296300] Write protecting the kernel read-only data: 12288k [2.304356] Freeing unused kernel memory: 1872K (9d9c6e42c000 - 9d9c6e60) [2.317659] Freeing unused kernel memory: 1208K (9d9c6e8d2000 - 9d9c6ea0) [2.344896] x86/mm: Checked W+X mappings: passed, no W+X pages found. [2.368095] exec: 1 (swapper/0) -> /init [2.377284] _do_fork: 1 init [2.381933] exit 53 init [2.386444] _do_fork: 1 init [2.390741] exit 54 init [2.394899] _do_fork: 1 init and we have the initramfs initialization occurring, and then finally systemd starts: [ 16.571630] exec: 1 (run-init) -> /sbin/init [ 17.287342] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [ 17.307892] systemd[1]: Detected virtualization microsoft. [ 17.314765] systemd[1]: Detected architecture x86-64. [ 17.421589] systemd[1]: Set hostname to . So it seems that systemd is accounting initramfs time in the kernel time stats. It would be preferable to be able to report the kernel init time, the initramfs time and the userspace time rather just kernel + userspace. As it stands, the kernel passed off control to systemd at 16.571630 seconds, so I have no no idea why systemd is reporting 16.878 seconds. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615685 Title: systemd-analyze stats for kernel startup time looks suspect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615685/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1271777] Re: cannot type in search or page boxes in evince
This affects me, the search does not work, which is a real pain for large documents of thousands of pages; not being able to search makes the tool unusable for large docs. ** Changed in: evince (Ubuntu) Status: Expired => Confirmed ** Changed in: evince (Ubuntu) Importance: Low => Medium ** Changed in: evince (Ubuntu) Importance: Medium => High -- 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/1271777 Title: cannot type in search or page boxes in evince To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1271777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1577303] [NEW] package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
Public bug reported: Several errors reported during installation, all seemd related to amd-64. However on reboot, everything seems to be working, but the system has aksed for several erros reports, all of which have been completed. This post is therefore responding to system requests and has not been initiated by me ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Mon May 2 07:10:09 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2016-01-29 (93 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-05-02 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1577303 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1577303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1557797] Re: Big bug : CPU 100% load with gvfsd-smb-browse on Ubuntu Mate 16.04
This has been reported in a couple other places, like https://bugzilla.redhat.com/show_bug.cgi?id=1303300. It seems that many people encounter it (and this is the case for me) when on a network with one of those horrible DNS-hijacking landing pages that are all too common among USA ISPs. ** Bug watch added: Red Hat Bugzilla #1303300 https://bugzilla.redhat.com/show_bug.cgi?id=1303300 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1557797 Title: Big bug : CPU 100% load with gvfsd-smb-browse on Ubuntu Mate 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1557797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1278437] Re: can't move link type .desktop files around on desktop
A few discoveries in 15.10: 1. This bug doesn't affect non-URL type files. 2. (URL files only) Comment four doesn't work for me. Nautilus just crashes and all my files disappear until I log out and log back in. 3. (URL files only) If I repeat comment four with a file instead of a directory, it doesn't move anything but creates a new file-'thisismyurl.com (http)'. But yeah, as far as bugs go this seems fairly trivial (but annoying) to me :D. -- 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/1278437 Title: can't move link type .desktop files around on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1278437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1401917] Re: GVFS Samba mounts time out after inactivity
The upstream bug mentioned by Michael in comment #6 was fixed in libsmbclient 4.1.18 and 4.2.1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1401917 Title: GVFS Samba mounts time out after inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1401917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1486219] [NEW] Eye of GNOME doesn't display an error if the currently-viewed image is deleted
Public bug reported: Eye of GNOME doesn't display an error if the currently-viewed image is deleted. For example, if you open an image in EoG, close it, delete the image, then attempt to open the image from recent, you will receive an error stating No images found in 'file:///path/to/image/file.png'. However, if you are currently viewing an image, and delete it from outside of EoG, the the live-update will correctly remove it from display, but EoG remains open and simply displays grey. Using Ubuntu 15.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: eog 3.14.4-1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 18 13:38:57 2015 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid -- 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/1486219 Title: Eye of GNOME doesn't display an error if the currently-viewed image is deleted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1486219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1479524] [NEW] Totem Crashes at launch from missing libwayland-egl
Public bug reported: When trying to open a video file from Ubuntu 14.04.3 Daily Image (2015-07-29), it will not open. If totem is manually run from the terminal, this error occurs: totem: error while loading shared libraries: libwayland-egl.so.1: cannot open shared object file: No such file or directory Using Ubuntu 14.04.3 LTS (Daily Image from: 2015-07-29) 64-bit Totem version: 3.10.1-1ubuntu4 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 29 15:11:30 2015 InstallationDate: Installed on 2015-07-29 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS Trusty Tahr - Beta amd64 (20150729) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: system76 Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 14.04.3 amd64 apport-bug trusty -- 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/1479524 Title: Totem Crashes at launch from missing libwayland-egl To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1479524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1470845] [NEW] systemd on wily desktop generating short lived threads every second in a quiet system
Public bug reported:
I noticed that systemd on my idle Wily desktop is creating very short
lived threads at 1Hz. While these aren't doing much, it still consumes
power doing wakeups to create these periodic threads.
Showing thread creation with forkstat:
$ sudo forkstat
Time Event PID Info Duration Process
13:43:07 clone 1 parent /sbin/init splash
13:43:07 clone 7483 thread /sbin/init splash
13:43:07 exit 7483 00.001 /sbin/init splash
13:43:08 clone 1 parent /sbin/init splash
13:43:08 clone 7484 thread /sbin/init splash
13:43:08 exit 7484 00.000 /sbin/init splash
13:43:10 clone 1 parent /sbin/init splash
13:43:10 clone 7485 thread /sbin/init splash
13:43:10 exit 7485 00.000 /sbin/init splash
13:43:11 clone 1 parent /sbin/init splash
13:43:11 clone 7486 thread /sbin/init splash
13:43:11 exit 7486 00.000 /sbin/init splash
13:43:12 clone 1 parent /sbin/init splash
13:43:12 clone 7487 thread /sbin/init splash
13:43:12 exit 7487 00.000 /sbin/init splash
13:43:13 clone 1 parent /sbin/init splash
13:43:13 clone 7488 thread /sbin/init splash
13:43:13 exit 7488 00.000 /sbin/init splash
13:43:15 clone 1 parent /sbin/init splash
13:43:15 clone 7489 thread /sbin/init splash
13:43:15 exit 7489 00.000 /sbin/init splash
13:43:16 clone 1 parent /sbin/init splash
13:43:16 clone 7490 thread /sbin/init splash
13:43:16 exit 7490 00.000 /sbin/init splash
13:43:17 clone 1 parent /sbin/init splash
13:43:17 clone 7491 thread /sbin/init splash
13:43:17 exit 7491 00.000 /sbin/init splash
And it's consuming some cycles over time:
$ sudo perf stat -p 1
^C
Performance counter stats for process id '1':
7.519868 task-clock (msec) #0.000 CPUs utilized
41 context-switches #0.005 M/sec
39 cpu-migrations#0.005 M/sec
3 page-faults #0.399 K/sec
12,107,977 cycles#1.610 GHz
10,597,101 stalled-cycles-frontend # 87.52% frontend cycles
idle
0 stalled-cycles-backend#0.00% backend cycles
idle
2,285,818 instructions #0.19 insns per cycle
#4.64 stalled cycles per
insn
457,133 branches # 60.790 M/sec
69,444 branch-misses # 15.19% of all branches
46.099593011 seconds time elapsed
The thread is just doing the following:
clock_gettime(0x7 /* CLOCK_??? */, {52592, 947682919}) = 0
read(14, \1\0\0\0\0\0\0\0, 8) = 8
fcntl(30, F_DUPFD_CLOEXEC, 3) = 15
ioctl(30, 0xc0189374, 0x7ffeaf311470) = 0
fcntl(16, F_GETFD) = 0x1 (flags FD_CLOEXEC)
clone(Process 7466 attached
child_stack=0x7f97c3580e30,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
parent_tidptr=0x7f97c35819d0, tls=0x7f97c3581700, child_tidptr=0x7f97c35819d0)
= 7466
[pid 7466] set_robust_list(0x7f97c35819e0, 24) = 0
[pid 1] timerfd_settime(14, TFD_TIMER_ABSTIME, {it_interval={0, 0},
it_value={52594, 197493000}}, NULL unfinished ...
[pid 7466] ioctl(15, 0xc018937c unfinished ...
[pid 1] ... timerfd_settime resumed ) = 0
[pid 7466] ... ioctl resumed , 0x7f97c3580d60) = -1 EAGAIN (Resource
temporarily unavailable)
[pid 1] epoll_wait(4, unfinished ...
[pid 7466] close(15) = 0
[pid 7466] close(16) = 0
[pid 7466] madvise(0x7f97c2d81000, 8368128, MADV_DONTNEED) = 0
[pid 7466] _exit(0)= ?
[pid 7466] +++ exited with 0 +++
... epoll_wait resumed {{EPOLLIN, {u32=3, u64=3}}}, 34, -1) = 1
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- systemd on wily desktop generating short lived threads every second in a
quite system
+ systemd on wily desktop generating short lived threads every second in a
quiet system
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1470845
Title:
systemd on wily desktop generating short lived threads every second in
a quiet system
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1470845/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 962825] Re: Menubar still shows when off by default
Recommend closing this bug, I can't reproduce it now. -- 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/962825 Title: Menubar still shows when off by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/962825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1438301] [NEW] desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart
Public bug reported: For reasons I cannot fathom, my development server goes into deep suspend after ~3 minutes after startup with systemd, however, if I boot with upstart it does not. This happens everytime I boot with systemd, the machine just goes into a deep suspend without me requesting it. I enabled debug; attached is a gzip'd syslog showing the activity - look at the end of the log, it goes into deep suspend. No idea why. acpi_listen is showing some curious audio plug/unplug events that seem to occur on this development box, so maybe these are being misinterpreted as suspend events. $ acpi_listen jack/headphone HEADPHONE plug jack/headphone HEADPHONE unplug jack/headphone HEADPHONE plug jack/headphone HEADPHONE unplug jack/headphone HEADPHONE plug jack/headphone HEADPHONE unplug ..but I am not seeing any other ACPI related events that could be triggering a suspend request from acpi_listen. ** Affects: systemd (Ubuntu) Importance: Critical Status: New ** Attachment added: gzip'd syslog https://bugs.launchpad.net/bugs/1438301/+attachment/4361129/+files/syslog.gz ** Summary changed: - desktop machine suspends after ~3 minutes, does suspend with upstart + desktop machine suspends after ~3 minutes, does NOT suspend with upstart ** Summary changed: - desktop machine suspends after ~3 minutes, does NOT suspend with upstart + desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart ** Description changed: For reasons I cannot fathom, my development server goes into deep suspend after ~3 minutes after startup with systemd, however, if I boot - with upstart it does not. + with upstart it does not. This happens everytime I boot with systemd, + the machine just goes into a deep suspend without me requesting it. I enabled debug; attached is a gzip'd syslog showing the activity - look at the end of the log, it goes into deep suspend. No idea why. acpi_listen is showing some curious audio plug/unplug events that seem to occur on this development box, so maybe these are being misinterpreted as suspend events. - $ acpi_listen + $ acpi_listen jack/headphone HEADPHONE plug jack/headphone HEADPHONE unplug jack/headphone HEADPHONE plug jack/headphone HEADPHONE unplug jack/headphone HEADPHONE plug jack/headphone HEADPHONE unplug ..but I am not seeing any other ACPI related events that could be triggering a suspend request from acpi_listen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1438301 Title: desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1438301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1433720] [NEW] shutdown request timeouts out and leaves tty in non-echo mode
Public bug reported: I believe this is a change in shutdown tied somehow to systemd, but I am guessing. How to reproduce the bug: sudo shutdown -h now [ wait a couple of minutes, don't enter in one's password ] authentication times out and one is left with non-echo on one's tty. This has to be restored back to normal using tset. It's annoying and a regression on the old way shutdown worked. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 18 17:56:52 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-05 (286 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) MachineType: LENOVO 2320CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8f6baa39-b057-41c2-bfe9-6c77484299ab ro quiet splash pcie_aspm=force crashkernel=384M-:128M vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET31WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 2320CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET31WW(1.11):bd05/24/2012:svnLENOVO:pn2320CTO:pvrThinkPadX230:rvnLENOVO:rn2320CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2320CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1433720 Title: shutdown request timeouts out and leaves tty in non-echo mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1308648] Re: online-accounts don't sync in Evolution after connection loss
I'm guessing this is a duplicate of: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/897188 -- 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/1308648 Title: online-accounts don't sync in Evolution after connection loss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1308648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 897188] Re: Evolution doesn't get new messages from an IMAP server after suspend/resume
Getting this same behavior on 14.04 LTS. I'm sad to see that this has been reported for so long and doesn't have any activity. Is there any further information I can provide to help with troubleshooting? Of note: after a suspend, not only will my accounts fail to update automatically, but if I click Send/Receive, that dialog will hang forever with the Receive bar marked as Updating The cancel buttons in that dialog also do nothing and fail to dismiss the dialog. Sending still works, it's just receiving that is broken. -- 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/897188 Title: Evolution doesn't get new messages from an IMAP server after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/897188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1311257] Re: Wifi cannot connect or unstable after suspend 14.04
In reference to Milton's comments (and thanks for the follow-ups) - my problems (listed in #11) are *not* related to a post-suspend loss of wifi. My problems happen consistently on a fresh boot. Frankly my E6420 can be 'wobbly' after suspend (it has been since 10.10) so I rarely suspend (it can fail to restart wifi, sometimes it refuses to wake at all, sometimes it works fine but won't shutdown - I've no idea what causes this instability). For the time being I'm using a 2nd wifi device (a EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]) whilst in the office to avoid the loss of wifi problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/1311257 Title: Wifi cannot connect or unstable after suspend 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/1311257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1303079] Re: refresh rate value is not saved
I'm seeing this on 14.04 (Linux mint 17), 64 bit. I can't help but remember that I've seen this bug over the years. Two scenarios: 1) Edit|Preferences, Resources tab, Update interval is shown as 0.00, you can adjust it, Close, then if you go back it'll be marked as 0.00 (although the update speed in the charts has probably changed) 2) Make a change to Update interval, switch to another tab, the change is made and the graphs change speed, switch back to Resources tab and the interval is shown as 0.00 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1303079 Title: refresh rate value is not saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1303079/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1395584] [NEW] File transfer will become slowly or stop when switch DC to AC during transfer files from internal HDD to external storage on Notebook.
Public bug reported: Steps to reproduce: 1. Under notebook's DC mode, prepare the big file in internal HDD. 2. Plug-in the USB flash storage (DOK/SD card) and translate the file from the Internal HDD to it. 3. Plug-in the AC during file transferring, found file transfer speed become slowly or stop. Notes: This issue has a high fail rate with USB 2.0 storage devices. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Summary changed: - File transfer will become slowly or stop when switch DC to AC during transfer files from internal HDD to external storage. + File transfer will become slowly or stop when switch DC to AC during transfer files from internal HDD to external storage on Notebook. ** Description changed: Steps to reproduce: - 1. Under DC mode. Prepare the big file in internal HDD. + 1. Under notebook's DC mode, prepare the big file in internal HDD. 2. Plug-in the USB flash storage (DOK/SD card) and translate the file from the Internal HDD to it. 3. Plug-in the AC during file transferring, found file transfer speed become slowly or stop. Notes: This issue has a high fail rate with USB 2.0 storage devices. -- 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/1395584 Title: File transfer will become slowly or stop when switch DC to AC during transfer files from internal HDD to external storage on Notebook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1395584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
