[Bug 2061728] Re: Apps don't launch from GNOME Software
I was able to resolve this by following the instructions on this page :
https://etbe.coker.com.au/2024/04/24/ubuntu-24-04-bubblewrap/
Basically create the file /etc/apparmor.d/bwrap with the following
contents :
abi ,
include
profile bwrap /usr/bin/bwrap flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
and execute 'systemctl reload apparmor'
--
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/2061728
Title:
Apps don't launch from GNOME Software
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2061728/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
Thanks - this fix appears to have resolved my lag issues. OS: Ubuntu 22.04.04 LTS $XDG_SESSION_TYPE: x11 nVidia: 535.171.04 Mobo/CPU: MSI MAG B550M BAZOOKA / AMD Ryzen 5 5600X Video card: MSI GeForce GT1030 2GB PCI Express Mostly this was affecting Gnome terminal for me, but just prior to applying this patch (thanks again!!) I used GnuCash and that lagged too. -- 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 or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" 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 2061364] Re: Remote login missing user list
I am also seeing this issue on baremetal (Intel NUC), Hyper-V, and LXD VM attempting to connect via RDP from a Windows 11 computer. I was able to capture the following error coming from gnome-shell logs after initiating an RDP connection: JS ERROR: TypeError: this._button is undefined _createSessionMenuButton@resource:///org/gnome/shell/gdm/loginDialog.js:663:13 _init@resource:///org/gnome/shell/gdm/loginDialog.js:589:14 LoginDialog@resource:///org/gnome/shell/gdm/loginDialog.js:487:4 _ensureUnlockDialog@resource:///org/gnome/shell/ui/screenShield.js:472:28 showDialog@resource:///org/gnome/shell/ui/screenShield.js:404:14 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:317:26 _prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:764:18 _loadBackground/signalIdhttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061364/+attachment/5765719/+files/Screenshot%202024-04-15%20114510.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061364 Title: Remote login missing user list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2061364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2025662] [NEW] mutter pauses for multiple seconds at random times
Public bug reported:
Hi, I have this weird bug in mutter (44.2-0ubuntu1) which seems to
correlate with uptime - if I kill mutter the problem seems to go away
for a few days, although killing mutter is very inconvenient because all
applications are also killed even with session persistence.
Upon strace analysis it can be seen that when the pauses are happening
there is a specific trace involving GEM operations happening immediately
after a ~1 second epoll expires.
During this state the entire UI is paused - video does not update, mouse
cursor does not move, keypresses have no response. However, input
events are "queued" so that when the pause ends, the mouse instantly
warps across the screen, and if a key was down at the time the pause
began, the key is repeated hundreds of times since it seems that the
key-up event is only processed when the "pause" ends.
The system is up to date 23.04 and mutter is using the Intel HD 530
integrated graphics. I do not believe this issue happened before 23.04
was released, although it has been intermittent and persistent since
that time.
Attached a strace with timestamps which provides an example of a multi-
second pause. Using grep -A1 epoll_wait you can see the instances of
the GEM operations during the pause. Eventually at around 09:40:57
local time in the trace the "pause" ended.
Example of an instance of the GEM operation trace after a ~1 second
epoll timeout:
[pid 686436] 09:40:54.750468 poll([{fd=3, events=POLLOUT}], 1, 5) = 1 ([{fd=3,
revents=POLLOUT}])
[pid 686436] 09:40:54.750719 epoll_wait(8, [], 256, 671) = 0
[pid 686436] 09:40:55.422886 ioctl(11, DRM_IOCTL_SYNCOBJ_DESTROY,
0x7ffce0975140) = 0
[pid 686436] 09:40:55.423213 ioctl(11, DRM_IOCTL_I915_GEM_EXECBUFFER2,
0x7ffce09751d0) = 0
[pid 686436] 09:40:55.423525 ioctl(11, DRM_IOCTL_I915_GEM_MADVISE,
0x7ffce0975098) = 0
[pid 686436] 09:40:55.423642 ioctl(11, DRM_IOCTL_SYNCOBJ_WAIT, 0x7ffce0974ef0)
= 0
[pid 686436] 09:40:55.423876 ioctl(11, DRM_IOCTL_I915_GEM_MADVISE,
0x7ffce0974fec) = 0
[pid 686436] 09:40:55.423971 ioctl(11, DRM_IOCTL_SYNCOBJ_CREATE,
0x7ffce0975100) = 0
[pid 686436] 09:40:55.424218 writev(45,
[{iov_base="#\221\360s\0\0\0\0\2\0\0\0\204\v \4\3\0\200\3s\213\0\0\243\v
\4\244\v \4", iov_len=32}], 1) = 32
[pid 686436] 09:40:55.424471 writev(45,
[{iov_base="#\221\360s\2\0\0\0\1\0\0\2\204\v
\4\3\0\200\3r\213\0\0\376S\340\252\37\2\0\0\311uf\0\0\0\0\0", iov_len=40}], 1)
= 40
[pid 686436] 09:40:55.424810 poll([{fd=3, events=POLLOUT}], 1, 5) = 1 ([{fd=3,
revents=POLLOUT}])
[pid 686436] 09:40:55.425150 epoll_wait(8, [], 256, 0) = 0
These pauses are often 10-15 seconds in length but can also be much
longer. I have observed it happening even with the screen locked
(screen lock unresponsive until pause ends).
FD 8 in the trace is anon_inode:[eventpoll] and FD 11 is
/dev/dri/renderD129, the Intel HD 530 DRI device.
Kernel is 6.2.0-24-generic from the distribution.
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "strace.txt"
https://bugs.launchpad.net/bugs/2025662/+attachment/5683579/+files/strace.txt
** Description changed:
Hi, I have this weird bug in mutter which seems to correlate with uptime
- if I kill mutter the problem seems to go away for a few days, although
killing mutter is very inconvenient because all applications are also
killed even with session persistence.
Upon strace analysis it can be seen that when the pauses are happening
there is a specific trace involving GEM operations happening immediately
- after a 1 second epoll expires.
+ after a ~1 second epoll expires.
During this state the entire UI is paused - video does not update, mouse
cursor does not move, keypresses have no response. However, input
events are "queued" so that when the pause ends, the mouse instantly
warps across the screen, and if a key was down at the time the pause
began, the key is repeated hundreds of times since it seems that the
key-up event is only processed when the "pause" ends.
The system is up to date 23.04 and mutter is using the Intel HD 530
integrated graphics. I do not believe this issue happened before 23.04
was released, although it has been intermittent and persistent since
that time.
Attached a strace with timestamps which provides an example of a multi-
second pause. Using grep -A1 epoll_wait you can see the instances of
the GEM operations during the pause. Eventually at around 09:40:57
local time in the trace the "pause" ended.
- Example of an instance of the GEM operation trace after a 1 second epoll
- timeout:
+ Example of an instance of the GEM operation trace after a ~1 second
+ epoll timeout:
[pid 686436] 09:40:54.750468 poll([{fd=3, events=POLLOUT}], 1, 5) = 1
([{fd=3, revents=POLLOUT}])
[pid 686436] 09:40:54.750719 epoll_wait(8, [], 256, 671) = 0
[pid 686436] 09:40:55.422886 ioctl(11, DRM_IOCTL_SYNCOBJ_DESTROY,
0x7ffce0975140) = 0
[pid 686436] 09:
[Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
And: https://github.com/ibus/ibus/issues/2486 https://gitlab.gnome.org/GNOME/gtk/-/issues/5347 ** Bug watch added: github.com/ibus/ibus/issues #2486 https://github.com/ibus/ibus/issues/2486 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #5347 https://gitlab.gnome.org/GNOME/gtk/-/issues/5347 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
@seb128 FYI: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2877 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2877 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2877 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1996652] [NEW] Nautilus search is slow and jumbles keyboard input on 22.10
Public bug reported: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stablecanonical✓ base core 16-2.57.2 13886 latest/stablecanonical✓ core core18 20221027 2620 latest/stablecanonical✓ base core20 20221027 1695 latest/stablecanonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stablecanonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stablecanonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
@martin-weinberg-5 I tried the dconf write as you suggested, and I did alt-F2 and "r" to restart Gnome, but it doesn't seem to have changed anything. ***As I wrote the above, I remembered that I'd left some terminal windows open during the process. I've re-tested but closed all windows before restarting Gnome and it *does* resolve the problem. However, I now have a menu bar on all my terminal windows. (screen grab attached for the benefit of others). For the moment, I'll reset that entry: dconf reset /org/gnome/terminal/legacy/headerbar ..but hopefully that will help a little in figuring out where the underlying bug is. ** Attachment added: "Screenshot of gnome terminal with headerbar set to @mb false via dconf" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+attachment/5618395/+files/Screenshot%20from%202022-09-23%2012-21-45.png -- 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/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
@prohlep I fresh installed Ubuntu 22.04 (64-bit) on 27th April 2022 and this is still occurring for me. (Hopefully) video attached of me opening three terminal windows, and then pressing F11 to toggle one of them to/from full screen. ** Attachment added: "Video of terminal window with effect of F11 / full screen toggling" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+attachment/5618087/+files/Screencast%20from%2022-09-22%2015%3A16%3A06.webm -- 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/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu
Bug happens for me, on fully updated 22.04. Only crashes if I pick one of the bookmarked folders. If I select "New Window", it does not crash. Linux dell-xps-8700 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Package: gnome-panel Version: 1:3.44.0-1ubuntu1 Package: nautilus Version: 1:42.2-0ubuntu1 Package: libwayland-client0 Version: 1.20.0-1 Package: libwayland-server0 Version: 1.20.0-1 -- 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/1934579 Title: Nautilus crashes when opening places from the dock contextmenu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1978044] [NEW] In Activities Overview search, only the first item can be selected
Public bug reported: Description:Ubuntu 22.04 LTS Release:22.04 gnome-shell: Installed: 42.1-0ubuntu0.1 Candidate: 42.1-0ubuntu0.1 Version table: *** 42.1-0ubuntu0.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 1. Press the GUI key or "Activities" in the top left of the screen 2. Search for an app. For example, type "calc". 3. Depending on the installed apps, you might see Calculator and LibreOffice Calc icons in some order. 4. Try clicking on an icon -- expected: the app launches, actual: nothing 5. Press an arrow key or tab to try to select a different app -- expected: switches focus to a different icon, actual: nothing is focused, cannot regain focus without mouse ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 22:51:31 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-13 (238 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1978044 Title: In Activities Overview search, only the first item can be selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978044/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971752] [NEW] Toggling F11 for fullscreen reduces the restored window size
Public bug reported: When I open a Gnome Terminal window at a given size (say 80 columns x 24 rows), press F11 to go full-screen, and then press F11 to restore the window to it's original size, it will be a bit smaller! It will lose both height and width. If I keep toggling with F11, the window will reduce to 3 lines and... I'm not sure exactly how many columns, but it's less than it had. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 18:03:50 2022 InstallationDate: Installed on 2022-04-26 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1971752 Title: Toggling F11 for fullscreen reduces the restored window size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1971752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968627] [NEW] file saving dialog grows and grows with each additional file dialog
Public bug reported: This might be an issue with xdg-desktop-portal-gnome as well, I am using the Brave Browser and noticed this. I *think* it uses xdg-desktop- portal-gtk for the time being though. This is 22.04 Daily Build from April 9th updated. What happens: If you decide to save an image, the file save dialog pops up, provided by either xdg-desktop-portal-gtk or -gnome, this is fine. However, multiple instances of calling the file save dialog such as saving multiple images from a website will cause the dialog box to grow and grow every time it is called, leading to it stretching off the main screen onto my secondary (which is a portrait 1080x1920 monitor to the right of the main 2560x1440 monitor). This is super annoying because you never know where the window is going to appear, and at what size (well, I guess you do know that it is going to grow each time, but it is VERY inconsistent). I've attached a scaled down webm, in it I am downloading cat pictures from Google Image Search. For the first image, it shows how large it tends to get, and I resize it to a smaller size. Then, with each image that the dialog is brought up for, it grows and grows. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gtk 1.14.0-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 15:39:25 2022 InstallationDate: Installed on 2022-04-09 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: xdg-desktop-portal-gtk UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screen recording of the file save dialog bug" https://bugs.launchpad.net/bugs/1968627/+attachment/5579502/+files/output.webm -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1968627 Title: file saving dialog grows and grows with each additional file dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1968627/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968451] [NEW] GNOME launcher folder icons and labels very small
Public bug reported: Ubuntu 22.04 Daily Build from April 9th The default Utilities folder in GNOME Shell applications launcher (the screen that shows when you hit Super twice) are extremely small/tiny. I haven't seen this with other versions of GNOME shell on other distros with this version of GNOME that I have tested, so it may be a Ubuntu specific issue. I've attached a screenshot of the "Utilities" folder as it existed by default after install, I did however change the icon theme to a few different ones before noticing, but it persisted after switching back to Yaru Icon Theme. I was able to get the normal behavior by dragging all the icons out one by one and recreating the folder, after which it appears normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 21:11:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Untitled.png" https://bugs.launchpad.net/bugs/1968451/+attachment/5578879/+files/Untitled.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968451 Title: GNOME launcher folder icons and labels very small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968451/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724732] Re: Wayland login options are missing when a radeon card is installed
I am having a similar issue on Ubuntu 22.04 with Asus Tuf A15 FA605IH -- 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/1724732 Title: Wayland login options are missing when a radeon card is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960436] Re: Touchpad setting toggles don't work
Restarting computer seems to have settings take affect properly -- 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/1960436 Title: Touchpad setting toggles don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1960436/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960436] [NEW] Touchpad setting toggles don't work
Public bug reported: It seems none of the touchpad toggles change anything. Natural scrolling: Always acts as disabled Tap to click: always acts enabled. Two finger scrolling: always acts enabled. Edge scrolling: always acts enabled. Also toggling two finger scrolling on will toggle edge scrolling off, and vice versa (not sure if intended, also doesn't affect functionality just the toggle visual). Asus ROG STRIX g15 if that helps anything. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.1-1ubuntu3 Uname: Linux 5.17.0-051700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 9 09:54:19 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-14 (26 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Description changed: It seems none of the touchpad toggles change anything. Natural scrolling: Always acts as disabled Tap to click: always acts enabled. Two finger scrolling: always acts enabled. Edge scrolling: always acts enabled. Also toggling two finger scrolling on will toggle edge scrolling off, and vice versa (not sure if intended, also doesn't affect functionality just the toggle visual). + + Asus ROG STRIX g15 if that helps anything. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.1-1ubuntu3 Uname: Linux 5.17.0-051700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 9 09:54:19 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-14 (26 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: - LANGUAGE=en_CA:en - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=en_CA.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_CA:en + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=en_CA.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) -- 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/1960436 Title: Touchpad setting toggles don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1960436/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
This is still broken on impish when running i3 under X11. Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5615]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5646]: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5658]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809685] Re: The evince application often freezes
I can confirm it happens to me also in 21.04. The PDF opens fine for me but the instant I hit print the evince process pegs the CPU and stays there indefinitely. Files are on the local disk. x86_64 architecture. The most recent PDF that did this to me is here: https://www.lcps.org/site/handlers/filedownload.ashx?moduleinstanceid=305856&dataid=381294&FileName=New%20Health%20form%20MCH-213G-032014.pdf Printing worked fine with 20.04, then I upgraded to 21.04 about a month ago and have not been able to print a PDF ever since. One possibly interesting bit: ryan@khym:/var/log$ sudo dmesg | tail [947533.329921] audit: type=1400 audit(1629163613.332:388): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-DTLIeIXr" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947538.329943] audit: type=1400 audit(1629163618.332:389): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-2diq9E0F" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947543.329859] audit: type=1400 audit(1629163623.332:390): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-n0LaY8dp" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947548.329836] audit: type=1400 audit(1629163628.332:391): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-GuW4c7UX" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947553.330670] audit: type=1400 audit(1629163633.332:392): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-lW4MWUNt" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947558.329769] audit: type=1400 audit(1629163638.332:393): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-jFM9PdLI" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947563.331063] audit: type=1400 audit(1629163643.336:394): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-jt0kRZuk" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947568.328371] audit: type=1400 audit(1629163648.332:395): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-9dOXwErT" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947573.326570] audit: type=1400 audit(1629163653.328:396): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-tz4r2Rco" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947975.225424] audit: type=1400 audit(1629164055.230:397): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=78607 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 -- 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/1809685 Title: The evince application often freezes To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1809685/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1910140] [NEW] Alignment of password field in 20.04 login screen not in centre
Public bug reported: ubuntu is now launching slowly for me it gives me a black screen at launch that shows the result of a system file check then it jumps to the login screen which seems strange as the alignment of the password field appears now on the left of the screen instead of in the centre as it used to be then ubuntu desktop starts, the screen seems to be shifting or 3 seconds then it adjusts itself to normal what should I reinstall to fix this please ? thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 19:35:37 2021 DisplayManager: lightdm InstallationDate: Installed on 2021-01-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 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/1910140 Title: Alignment of password field in 20.04 login screen not in centre To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Please open the new bug and provide a link so I can follow the progress and test the solution -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Status file too ** Attachment added: "status.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435346/+files/status.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Done! I see Nov 18 14:24:37 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: discord1, Impossible to lookup icon for 'discord1_33-panel' in path /tmp/.org.chromium.Chromium.PSxy7s Nov 18 14:24:37 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: unable to update icon for discord1 Nov 18 14:24:51 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: discord1, Impossible to lookup icon for 'discord1_39-panel' in path /tmp/.org.chromium.Chromium.cZ6PNp Nov 18 14:24:51 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: unable to update icon for discord1 Please see attached. ** Attachment added: "newmessages.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435342/+files/newmessages.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Why does the issue still occur with the fix? The severity is lessened but it is still there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
sudo apt install gnome-shell-extension-appindicator/focal seemed to restore it properly -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
After installing the deb (oddly asking me to downgrade to your supplied version) and logging back in, I was greeted with an error from my HP printer drivers saying there is no detected system tray and it's unable to start (attached). Discord and MegaSync still appear in the tray so I don't know what that's all about. The stutter/lag caused by discord still exists but it's MUCH improved. It's much harder to perceive, but it's certainly still there. I'd estimate the lags are 5-10x shorter in duration. I am testing on an AMD 5950X CPU so it's not caused by a lack of processing power. How do I restore the package back to my system maintainers version? ** Attachment added: "Screenshot from 2020-11-17 21-18-54.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435124/+files/Screenshot%20from%202020-11-17%2021-18-54.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
I'm running Pop OS 20.04 with this bug, I'd be happy to test this if I knew how to install the patch. Do I just need to enable proposed packages? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889102] Re: [ubuntu-dock] App grid has too many page dots on right
Version 69 of Dash to Dock fixed this bug, at least in my tests. Can someone else test if it works? Disable Ubuntu Dock in Extensions app and install version 69 of Dash to Dock in extensions.gnome.com -- 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/1889102 Title: [ubuntu-dock] App grid has too many page dots on right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892573] [NEW] syslog gdm-x-session "your system is too slow" as desktop GUI slows down and eventually stops
Public bug reported: After ~72 hours, my Gnome desktop will be very slow. In syslog I noticed that I get a bunch of these messages as the system slows down: /usr/lib/gdm3/gdm-x-session[13460]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-30ms), your system is too slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 18:02:23 2020 InstallationDate: Installed on 2020-02-23 (181 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1892573 Title: syslog gdm-x-session "your system is too slow" as desktop GUI slows down and eventually stops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892573/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders
I couldn't reproduce the bug without Ubuntu Dock. -- 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/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders
In my experience, when I open an app and meanwhile open and close a folder the GNOME freezes. -- 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/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Just to add I found that on the unscaled screens the text and general look was a little fuzzy. I assume this is something to do with the scaling going on. Also if fractional scaling is turned off I cannot set the 4k screen to 200% on its own as all screens then get set to 200%. I know its not related to this but VLC also does not work when scaling is on(Atleast for me), I assume this is more of an issue for VLC not Ubuntu. -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Ive just tried this again this morning 1. 2560 x 1440 2. 3840 x 2160 3. 1920 x 1200 I set fractional scaling to 1.50 on screen 2 (Others 100%) For the session it works perfectly fine, But after logging out and logging back in the settings do not get saved (Nvidia gtx 1080 with 440 driver) This was not working before, So I assume some updates have been made in this area? -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870847] Re: App grid has too many page dots on right
This bug is fixed in groovy, but shouldn't it be fixed in 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/1870847 Title: App grid has too many page dots on right To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen
For anyone else affected by this bug, I've written a script that toggles the scaling mode back and forth to fix the problem and then restore your desired scaling mode on each monitor. https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1875404/+attachment/5361667/+files/xrandr-fix.sh Just set that script to run at login (e.g. by adding it to Startup Applications). Your screen will flicker momentarily on login, since the script is changing resolutions, but then the extra mouse cursor will be gone automatically. -- 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/1873052 Title: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870847] Re: App grid has too many page dots on right
I disabled the Ubuntu Dock extension using the Gnome Extensions app and tried to reproduce the bug, and the bug didn't happen anymore. When I installed the Dash to Dock extension by the Gnome Extensions site, and tried to reproduce the error, nothing wrong happened. I think that the bug is caused by the dock, and the version 68 of Dash to Dock fixed this bug. The Ubuntu dock is still in version 67. -- 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/1870847 Title: App grid has too many page dots on right To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875404] [NEW] Non-integer X11 scaling causes mouse from login screen to stick around
Public bug reported: If you enable fraction scaling and then login using an X11 session, the mouse cursor that existed on the login screen (gdm3) will persist after logging in. This mouse cursor continues to exist at the same pixel coordinates as when the login was completed. A new mouse cursor is then created for that login, which is controlled by the mouse. The original cursor that persisted from the login screen now becomes static and can no longer be moved. However, like any mouse cursor, it hovers over all windows and the desktop, which is quite distracting when the cursor is in the middle of the screen. This extra mouse cursor can be eliminated by switching to a non- fractional scaling mode. Once it is eliminated, you can then switch back to fractional scaling and the extra cursor will not return. Seeing this, I have worked around this issue by adding a startup script to my session that toggles the scaling mode between integer scaling and my desired fractional scaling mode. Obviously this adds a bit of extra flicker to the login process, though, so it's not ideal. Note that a similar bug has been reported previously (#1827428), but that bug was closed in the Ubuntu 19.04 EOL. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:49:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-20 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-23 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Startup script to work around this bug" https://bugs.launchpad.net/bugs/1875404/+attachment/5361667/+files/xrandr-fix.sh -- 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/1875404 Title: Non-integer X11 scaling causes mouse from login screen to stick around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875404/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870725] Re: artifacts appearing on gnome shell
I believed I narrowed down the issue to how gnome-shell uses Xorg. As said before GDM did not have any issues, and (i may be seriously wrong here) GDM uses Wayland by default. When I launch the Ubuntu desktop with Wayland, the graphical issue went away and is running smoothly. So I narrowed down the issue to Xorg or gnome-shell. So I went ahead and installed Cinnamon DE which uses Xorg, and the issue did not arise. My theory is that gnome-shell has a problem with rendering the shell (not programs) with Xorg. I also attached another image showing the problem, could the issue be the compositor??? ** Attachment added: "Screenshot from 2020-04-04 13-11-46.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1870725/+attachment/5346554/+files/Screenshot%20from%202020-04-04%2013-11-46.png ** No longer affects: ubuntu-meta (Ubuntu) ** Also 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/1870725 Title: artifacts appearing on gnome shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867986] [NEW] gnome-shell crashes after laptop resume (trap libglib-2.0)
Public bug reported: traps: gnome-shell[123022] trap int3 ip:7f15b03dc0d5 sp:7ffe1bfdf010 error:0 in libglib-2.0.so.0.6400.1[7f15b03a+84000] % dmesg | grep trap [18311.547270] traps: gnome-shell[12034] trap int3 ip:7f33128f30d5 sp:7fff3a3b0be0 error:0 in libglib-2.0.so.0.6400.1[7f33128b7000+84000] [18332.082814] traps: gnome-shell[117297] trap int3 ip:7fade11620d5 sp:7ffd604b15e0 error:0 in libglib-2.0.so.0.6400.1[7fade1126000+84000] [18337.200121] traps: gnome-shell[117598] trap int3 ip:7f0c187c40d5 sp:7ffec16cb720 error:0 in libglib-2.0.so.0.6400.1[7f0c18788000+84000] [18342.569015] traps: gnome-shell[117775] trap int3 ip:7f0e1edff0d5 sp:7ffdac383f00 error:0 in libglib-2.0.so.0.6400.1[7f0e1edc3000+84000] [18347.669729] traps: gnome-shell[117997] trap int3 ip:7faf883020d5 sp:7ffebf340650 error:0 in libglib-2.0.so.0.6400.1[7faf882c6000+84000] [18351.607031] traps: gnome-shell[118217] trap int3 ip:7f11a42210d5 sp:7ffdf0700cd0 error:0 in libglib-2.0.so.0.6400.1[7f11a41e5000+84000] [18358.250075] traps: gnome-shell[118420] trap int3 ip:7f2c0a13f0d5 sp:7ffcab8a82f0 error:0 in libglib-2.0.so.0.6400.1[7f2c0a103000+84000] [18503.626029] traps: gnome-shell[123022] trap int3 ip:7f15b03dc0d5 sp:7ffe1bfdf010 error:0 in libglib-2.0.so.0.6400.1[7f15b03a+84000] [18507.787061] traps: gnome-shell[124304] trap int3 ip:7f38f6b5d0d5 sp:7ffcc27d2cd0 error:0 in libglib-2.0.so.0.6400.1[7f38f6b21000+84000] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 14:53:07 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-15 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne 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/1867986 Title: gnome-shell crashes after laptop resume (trap libglib-2.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1075923] Re: nautilus hangs copying large directories from a samba share
Still a problem on Eoan. -- 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/1075923 Title: nautilus hangs copying large directories from a samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791936] Re: GNOME system-monitor cpu graph color does not update or persist
Not only can I not change the colours (also in Ubuntu 18.04), it seems many other elements of the settings are broken. The stacked area chart button, and the smooth graph button result in unpredictable behavior. -- 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/1791936 Title: GNOME system-monitor cpu graph color does not update or persist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1791936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1833192] Re: VMware: post custom script isn't run correctly
Wrong source package ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: evince (Ubuntu) Status: New => Invalid ** Merge proposal linked: https://code.launchpad.net/~xiaofengw/cloud-init/+git/cloud-init/+merge/368902 -- 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/1833192 Title: VMware: post custom script isn't run correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1833192/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend
Just chiming in from Arch Linux, we got it too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720901] Re: VLC under Wayland causes system freezes in fullscreen mode
New bug (same issue, on VLC 3.0.3/Ubuntu 18.04) is here: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1785434 -- 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/1720901 Title: VLC under Wayland causes system freezes in fullscreen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720901/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787199] [NEW] wacom led toggle buttons assigned to opposite touch strips
Public bug reported: In Ubuntu 18.04.1, the button mappings for the Wacom Cintiq21ux2 touch strips are reversed. The Cintiq has 2 touch strips, 1 on each side of the Cintiq. Correlating with these touchstrips are toggle buttons, 1 for each. Every time the toggle button is pressed, one of 4 leds will light up, indicating a mode switch. The mode switch will change the button mappings of the touchstrip. What Ubuntu is doing, is mapping the wrong toggle button to the touchstrips. Instead of changing the mode to the touchstrip that is nearest to the button, it changes the touchstrip on opposite side of the Cintiq, making it useless. The file cintiq-21ux2.tablet in libwacom shows the diagram of the button mappings. A and J are reversed in Ubuntu 18.04.1. Button 'A' should correlate to 'a-A' touchstrip groupings, and J should correlate to 'b-B' groupings. This is an Ubuntu specific Bug, one that is not seen in OpenSUSE using Gnome, or Archlinux using Gnome. The gnome-control-center version I have is 1:3.28.2-0ubuntu0.18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 05:21:26 2018 InstallationDate: Installed on 2018-08-15 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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 bionic -- 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/1787199 Title: wacom led toggle buttons assigned to opposite touch strips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1787199/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768603] [NEW] All review score averages are 5 Stars - 1 Star reviews show as 5 Star
Public bug reported: OS: Ubuntu Studio 18.04 Bionic Beaver (Comes with: DE - XFCE4 Version of application: 3.28.1-0ubuntu4) Looking in the Gnome Software application, all applications with any ratings show as 5-star. One-star reviews show as 5-star in the reviews section. An easy example to demonstrate this issue is to look at the entry for WINE. 5 Star Reviews (x24) 4 Star Reviews (x9) 3 Star Reviews (x5) 2 Star Reviews (x11) 1 Star Reviews (x45) Overall average - 5 Stars. Scrolling down to read individual reviews shows five stars for obviously negative reviews: (5 Star Rating) Title: Doesn't work (5 Star Rating) Title: Garbage ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1768603 Title: All review score averages are 5 Stars - 1 Star reviews show as 5 Star To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768603/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766106] Re: ntp.ubuntu.com not reliable, but used in standard configuration
Thank you, 2001:67c:1560:8003::c8 availability has been fixed. $ ntpdate -q 2001:67c:1560:8003::c8 server 2001:67c:1560:8003::c8, stratum 2, offset 0.031201, delay 0.18932 24 Apr 13:10:37 ntpdate[26740]: adjust time server 2001:67c:1560:8003::c8 offset 0.031201 sec ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/1766106 Title: ntp.ubuntu.com not reliable, but used in standard configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766106/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765173] [NEW] networkd waits 10 seconds for ipv6 network discovery by default
Public bug reported: 1. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2. $ apt-cache policy systemd systemd: Installed: 237-3ubuntu8 Candidate: 237-3ubuntu8 Version table: *** 237-3ubuntu8 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. systemd-networkd-wait-online doesn't block for 10 seconds waiting on an IPV6 Router Advertisement 4. systemd-networkd sends at least two RA solicitation packets waiting for a response before setting the link to configured. This blocks the boot for every Ubuntu system where it does not have a IPV6 router responding to solicitations. THis includes bionic containers, cloud instances, vms and physical machines. -- We can see that we're spending 13 seconds waiting for networkd to say the network is up. % systemd-analyze blame 13.326s systemd-networkd-wait-online.service 999ms cloud-init-local.service 954ms cloud-init.service 887ms cloud-config.service 749ms dev-vda1.device 666ms cloud-final.service 248ms keyboard-setup.service 175ms systemd-udev-trigger.service 171ms lxd-containers.service 165ms snapd.service 154ms apparmor.service 147ms ssh.service 144ms systemd-timesyncd.service 133ms grub-common.service 130ms systemd-journald.service 130ms accounts-daemon.service 99ms systemd-modules-load.service 98ms systemd-resolved.service 94ms apport.service 92ms rsyslog.service 88ms systemd-logind.service 80ms lvm2-monitor.service 75ms iscsid.service 64ms ebtables.service 62ms user@1000.service 54ms dev-mqueue.mount 53ms ufw.service 52ms systemd-remount-fs.service 52ms kmod-static-nodes.service 34ms systemd-journal-flush.service 34ms polkit.service 32ms systemd-tmpfiles-setup-dev.service 27ms systemd-udevd.service 26ms systemd-networkd.service 26ms systemd-sysctl.service 25ms systemd-tmpfiles-setup.service 21ms dev-hugepages.mount 17ms sys-kernel-debug.mount 16ms console-setup.service 15ms plymouth-read-write.service 15ms snapd.socket 15ms plymouth-quit.service 14ms systemd-update-utmp.service 10ms systemd-user-sessions.service 9ms boot-efi.mount 8ms sys-fs-fuse-connections.mount 8ms systemd-update-utmp-runlevel.service 8ms lxd.socket 7ms blk-availability.service 5ms systemd-random-seed.service 3ms setvtrgb.service 3ms plymouth-quit-wait.service 3ms sys-kernel-config.mount Here we can see that we start networking at 18:30:51.69, and then IPv6 NDISC runs for 10 seconds and then the link is configured at 18:31:05. *AND* we see NDISC stays around and continues to see if it gets a RA packet. $ journalctl -o short-precise -u systemd-networkd.service | egrep "(Starting Network|Discovering IPv6 routers|NDISC|Configured)" Apr 18 18:30:51.691532 rharper-b1 systemd[1]: Starting Network Service... Apr 18 18:30:53.031041 rharper-b1 systemd-networkd[603]: ens3: Discovering IPv6 routers Apr 18 18:30:53.031306 rharper-b1 systemd-networkd[603]: NDISC: Started IPv6 Router Solicitation client Apr 18 18:30:53.031612 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 4s Apr 18 18:30:57.092282 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 8s Apr 18 18:31:05.040895 rharper-b1 systemd-networkd[603]: NDISC: No RA received before link confirmation timeout Apr 18 18:31:05.040932 rharper-b1 systemd-networkd[603]: NDISC: Invoking callback for 't'. Apr 18 18:31:05.041099 rharper-b1 systemd-networkd[603]: ens3: Configured Apr 18 18:31:05.484261 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 16s Apr 18 18:31:21.550612 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 33s Apr 18 18:31:54.706283 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 1min 5s Apr 18 18:33:00.232685 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 2min 15s Apr 18 18:35:15.436376 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 4min 32s Apr 18 18:39:48.111413 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 9min 16s networkd runs ndisc if your host is configured with ipv6 forwarding disabled and accept_ra enabled. % sysctl net.ipv6.conf.all.forwarding net.ipv6.conf.all.f
[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR
I'm seeing this on Artful as well, in Azure cloud. ** Also affects: glibc (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) 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/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
This issue is still happening in Ubuntu 18.04 LTS. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716813] Re: When using vaapi in a wayland session a gl renderer launch icon appears
It does this with GNOME Web too, it seems (even still in Ubuntu 18.04). It's not _too_ annoying if you're just watching Youtube or something, but if you scroll down a Facebook tab it gets pretty obnoxious, because it creates a new "OpenGL Renderer" entry on the dock each time you scroll past a video of something, and doesn't go away until you close the tab. -- 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/1716813 Title: When using vaapi in a wayland session a gl renderer launch icon appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1716813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758307] [NEW] package libpam-systemd:amd64 229-4ubuntu21.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: On: Description:Ubuntu 16.04.4 LTS Release:16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-systemd:amd64 229-4ubuntu21.2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 23 06:20:55 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-03-15 (8 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: systemd Title: package libpam-systemd:amd64 229-4ubuntu21.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1758307 Title: package libpam-systemd:amd64 229-4ubuntu21.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1758307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
** 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/1749722 Title: NTP: take into account systemd-timesyncd where present To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
At any given time: immediately after reboot, immediately after restarting gnome-shell (alt+F2 --> "r"), and during regular use gnome- shell is consuming at least 4GB RAM. I'm happy to provide a memory profile but I don't know how to do that so I need help. # ps auxwww | grep gnome-shell gdm 1595 0.0 1.2 3696204 211144 tty1 Sl+ Dec08 0:23 /usr/bin/gnome-shell 2176 0.4 2.6 4063428 431096 tty2 Sl+ Dec08 3:01 /usr/bin/gnome-shell # ps -p 1595,2176 -Fl F S USER PID PPID C PRI NI PSZ WCHANRSS PSR STIME TTY TIME CMD 0 S gdm 1595 1559 0 80 0 * 924307 poll_s 211648 0 Dec08 tty1 00:00:24 /usr/bin/gnome-shell 0 S2176 2060 0 80 0 * 1017742 poll_s 433852 1 Dec08 tty2 00:03:36 /usr/bin/gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1672297/+attachment/5020458/+files/JournalErrors.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/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1672297/+attachment/5020456/+files/Dependencies.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/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1672297/+attachment/5020457/+files/GsettingsChanges.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/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1672297/+attachment/5020459/+files/ProcCpuinfoMinimal.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/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-02 (36 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: mutter PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected artful -- 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/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1734735] [NEW] [xenial] nm-openvpn continuously retries with bad password after receiving AUTH_FAIL locking out my account
Public bug reported: I have nm-openvpn configured via the network manager gui on Xenial with a saved password. My organization has a password expiration policy of X days. If I forgot to update the saved password for nm-openvpn and try to VPN in, nm-openvpn tries the connection, fails without notice in the UI and retries until I stop it. This ultimately causes my account to get locked out for too many invalid auth attempts. sanitized/censored from syslog: Nov 27 09:11:06 carbon NetworkManager[1173]: nm-openvpn-Message: openvpn[4971] started Nov 27 09:11:06 carbon nm-openvpn[4971]: OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 22 2017 Nov 27 09:11:07 carbon nm-openvpn[4971]: library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: file '/home/myusername/Downloads/certs/ta.key' is group or others accessible Nov 27 09:11:07 carbon nm-openvpn[4971]: Control Channel Authentication: using '/home/myusername/Downloads/certs/ta.key' as a OpenVPN static key file Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: chroot will be delayed because of --client, --pull, or --up-delay Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay Nov 27 09:11:07 carbon nm-openvpn[4971]: UDPv4 link local: [undef] Nov 27 09:11:07 carbon nm-openvpn[4971]: UDPv4 link remote: [AF_INET]10.0.28.166:1195 Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: this cipher's block size is less than 128 bit (64 bit). Consider using a --cipher with a larger block size. Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: this cipher's block size is less than 128 bit (64 bit). Consider using a --cipher with a larger block size. Nov 27 09:11:07 carbon nm-openvpn[4971]: [VPNGate.example.com] Peer Connection Initiated with [AF_INET]10.0.28.166:1195 Nov 27 09:11:10 carbon nm-openvpn[4971]: AUTH: Received control message: AUTH_FAILED Nov 27 09:11:10 carbon nm-openvpn[4971]: SIGUSR1[soft,auth-failure] received, process restarting Nov 27 09:11:10 carbon NetworkManager[1173]: (nm-openvpn-service:4894): nm-openvpn-WARNING **: Password verification failed Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Nov 27 09:11:12 carbon nm-openvpn[4971]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 27 09:11:12 carbon nm-openvpn[4971]: UDPv4 link local: [undef] Nov 27 09:11:12 carbon nm-openvpn[4971]: UDPv4 link remote: [AF_INET]10.0.28.166:1195 Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: this cipher's block size is less than 128 bit (64 bit). Consider using a --cipher with a larger block size. Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: this cipher's block size is less than 128 bit (64 bit). Consider using a --cipher with a larger block size. Nov 27 09:11:12 carbon nm-openvpn[4971]: [VPNGate.example.com] Peer Connection Initiated with [AF_INET]10.0.28.166:1195 Nov 27 09:11:15 carbon nm-openvpn[4971]: AUTH: Received control message: AUTH_FAILED Nov 27 09:11:15 carbon nm-openvpn[4971]: SIGUSR1[soft,auth-failure] received, process restarting ... ... [eventually I caught on to what was happening and stopped it] ... ... Nov 27 09:12:00 carbon NetworkManager[1173]: nm-openvpn-Message: openvpn[4971]: send SIGTERM Nov 27 09:12:00 carbon nm-openvpn[4971]: event_wait : Interrupted system call (code=4) Nov 27 09:12:00 carbon nm-openvpn[4971]: SIGTERM[hard,] received, process exiting Nov 27 09:12:00 carbon NetworkManager[1173]: nm-openvpn-Message: openvpn[4971] exited with success (and yes, I know I should fix the cipher and key file permissions) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1734735 Title: [xenial] nm-openvpn continuously retries with bad password after receiving AUTH_FAIL locking out my account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1734735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1733162] [NEW] Epiphany creates an empty "OpenGL Renderer" window entry in the dock for every video embedded in a webpage.
Public bug reported: On Ubuntu 17.10, Epiphany (GNOME Web) creates an empty "OpenGL Renderer" window entry in the dock for every video embedded in a webpage. I wasn't sure where to report this. Probably an issue that could be fixed by blacklisting this by name from creating an entry on the dock? Testing is pretty easy. Open a youtube video and notice the empty window entry on the dock. Or (even better) scroll down a page with multiple videos and notice that a new "OpenGL Renderer" entry is created on the dock for each one. This is really aggravating with Facebook. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: epiphany-browser 3.26.1-1ubuntu1 Uname: Linux 4.14.0-041400-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 02:09:20 2017 InstallationDate: Installed on 2017-11-08 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: epiphany-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1733162 Title: Epiphany creates an empty "OpenGL Renderer" window entry in the dock for every video embedded in a webpage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1733162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731594] [NEW] Ubuntu Dock creates a window button called "OpenGL Renderer" when GNOME Web is playing a video.
Public bug reported: Ubuntu Dock creates a window button called "OpenGL Renderer" when GNOME Web (Epiphany Browser) is playing a video which goes away when you go to a different page that isn't playing a video. Since this shouldn't be happening, is there a way to blacklist it so that it doesn't show up on the Dock? ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu Dock creates a window button called "OpenGL Renderer" when GNOME - Web is playing a video which goes away when you go to a different page - that isn't playing a video. + Web (Epiphany Browser) is playing a video which goes away when you go to + a different page that isn't playing a video. Since this shouldn't be happening, is there a way to blacklist it so that it doesn't show up on the Dock? -- 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/1731594 Title: Ubuntu Dock creates a window button called "OpenGL Renderer" when GNOME Web is playing a video. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1731594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721156] Re: networkd does not set bridge forward delay value correctly
It turns out that if STP is enabled, then one cannot disable the forward delay, and a value < 2 is not compatible with STP. If I set stp: false in netplan, then we get: # cat /run/systemd/network/10-netplan-br0.netdev [NetDev] Name=br0 Kind=bridge [Bridge] AgeingTimeSec=250 Priority=22 ForwardDelaySec=1 HelloTimeSec=1 MaxAgeSec=10 STP=false which results in a proper value in brctl and sysfs matching. (1.00/100 respectively) ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1721156 Title: networkd does not set bridge forward delay value correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721156/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721156] [NEW] networkd does not set bridge forward delay value correctly
Public bug reported: 1) # lsb_release -rd Description:Ubuntu Artful Aardvark (development branch) Release:17.10 2) # apt-cache policy systemd systemd: Installed: 234-2ubuntu10 Candidate: 234-2ubuntu10 Version table: *** 234-2ubuntu10 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3) /sys/class/net/br0/bridge/foward_delay value should be 100 (equivalent to 1 second) 4) /sys/class/net/br0/bridge/foward_delay value is 200 (defaults to 2 seconds) Configured a bridge in Artful with netplan with the following config: % cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true match: macaddress: '52:54:00:12:34:00' set-name: eth0 eth1: match: macaddress: '52:54:00:12:34:02' set-name: eth1 eth2: match: macaddress: '52:54:00:12:34:04' set-name: eth2 bridges: br0: addresses: - 192.168.14.2/24 interfaces: - eth1 - eth2 parameters: ageing-time: 250 forward-delay: 1 hello-time: 1 max-age: 10 path-cost: eth1: 50 eth2: 75 priority: 22 This generates some runtime network configs: # cat 10-netplan-br0.netdev [NetDev] Name=br0 Kind=bridge [Bridge] AgeingTimeSec=250 Priority=22 ForwardDelaySec=1 HelloTimeSec=1 MaxAgeSec=10 STP=true Note that the value (ForwardDelaySec=1) matches the config yaml; however the system value from sysfs is not in seconds, but some other factor: # cat /sys/class/net/br0/bridge/forward_delay 200 And brctl confirms the value in seconds matches the kernel setting # brctl showstp br0 br0 bridge id 0016.ea251c32d10e designated root0016.ea251c32d10e root port 0path cost 0 max age 10.00 bridge max age10.00 hello time1.00 bridge hello time 1.00 forward delay 2.00 bridge forward delay 2.00 ageing time 250.00 hello timer 0.22 tcn timer 0.00 topology change timer 0.00 gc timer 118.63 flags I *think* networkd has an update unit conversion bug, looking at the upstream commit for bridge params support: https://github.com/systemd/systemd/pull/1459 Notice the unit is in Seconds, ForwardDelaySec=288 which results in a 2.88 second setting. I suspect that our setting of ForwardDelaySec=1 was *too* small and there is no warning (or it got rounded out in a conversion) Hrm, I set ForwardDelaySec=150 an I get a sysfs value of 3000, and a brctl value of 30 ForwardDelaySec= ForwardDelaySec specifies the number of seconds spent in each of the Listening and Learning states before the Forwarding state is entered. That's the manpage entry for netdev devices in systemd. Is it really being doubled? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Tue Oct 3 23:06:01 2017 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=05f7684f-c8ff-42d7-aaf4-c49045b1859a ro console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-artful dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-artful:cvnQEMU:ct1:cvrpc-i440fx-artful: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-artful dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful curtin uec-images -- 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/1721156 Title: networkd does not set bridge forward delay value correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721156/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1643183] Re: Natural scrolling is not working
*** This bug is a duplicate of bug 1683016 *** https://bugs.launchpad.net/bugs/1683016 There is no natural scrolling option for mouse wheel in settings. Went and changed /org/gnome/desktop/peripherals/mouse/natural-scroll to true but mouse still scrolls the same. -- 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/1643183 Title: Natural scrolling is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1643183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1694896] Re: GNOME forgets display backlight setting preference after session ends on Lenovo Yoga 900-13ISK2 laptop.
** Description changed: - When I reboot my computer, GNOME forgets my display backlight setting - and puts it back at (roughly) 80% on my Lenovo Yoga 900-13ISK2 laptop + When I reboot, GNOME forgets my display backlight setting and puts it + back at (roughly) 80% on my Lenovo Yoga 900-13ISK2 laptop That's not optimal for battery life since it causes power usage to be 1-2 watts higher than it would be under my preferred setting until I manually turn it back down. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-settings-daemon 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 31 23:50:16 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1694896 Title: GNOME forgets display backlight setting preference after session ends on Lenovo Yoga 900-13ISK2 laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1694896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1694896] [NEW] GNOME forgets display backlight setting preference after session ends on Lenovo Yoga 900-13ISK2 laptop.
Public bug reported: When I reboot, GNOME forgets my display backlight setting and puts it back at (roughly) 80% on my Lenovo Yoga 900-13ISK2 laptop That's not optimal for battery life since it causes power usage to be 1-2 watts higher than it would be under my preferred setting until I manually turn it back down. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-settings-daemon 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 31 23:50:16 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Summary changed: - GNOME forgets display backlight setting preference after session ends. + GNOME forgets display backlight setting preference after session ends on Lenovo Yoga 900-13ISK2 laptop. ** Description changed: When I reboot my computer, GNOME forgets my display backlight setting - and puts it back at (roughly) 80%. + and puts it back at (roughly) 80% on my Lenovo Yoga 900-13ISK2 laptop That's not optimal for battery life since it causes power usage to be 1-2 watts higher until I manually turn it back down. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-settings-daemon 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 31 23:50:16 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: When I reboot my computer, GNOME forgets my display backlight setting and puts it back at (roughly) 80% on my Lenovo Yoga 900-13ISK2 laptop That's not optimal for battery life since it causes power usage to be - 1-2 watts higher until I manually turn it back down. + 1-2 watts higher than it would be under my preferred setting until I + manually turn it back down. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-settings-daemon 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 31 23:50:16 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1694896 Title: GNOME forgets display backlight setting preference after session ends on Lenovo Yoga 900-13ISK2 laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1694896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672424] Re: Cannot install Debian files outside of the repositories
Still not working. Tried to install Dropbox 64bit deb from Dropbox site. Click install, no response. gdebi worked fine. Ubuntu Gnome 17.04 x64 kernel 4.10.0-20-generic -- 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/1672424 Title: Cannot install Debian files outside of the repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1673860] [NEW] systemd-resolved unit should run Before=network-online.target
Public bug reported: 1) Xenial, Yakkety and Zesty; (Xenial is affected if you're using networkd and resolved, but it's not the default) 2) 229-4ubuntu16, 231-9ubuntu3, 232-18ubuntu1 respectively to (1) 3) DNS resolution should be available once systemd has reached 'network-online.target' state 4) Sometimes systemd-resolved has not become active prior to network-online.target and DNS service is not available. The remaining issue for the systemd-resolved.service unit is that it needs to include a Before=network-online.target to ensure it's ordered to run before systemd reaches 'network-online.target' ** 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/1673860 Title: systemd-resolved unit should run Before=network-online.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1671951] [NEW] networkd should allow configuring IPV6 MTU
Public bug reported: 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: curtin maas netplan -- 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/1671951 Title: networkd should allow configuring IPV6 MTU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1669564] [NEW] udevadm trigger subsystem-match=net doesn't always run rules
Public bug reported: root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 root@ubuntu:~# apt-cache policy udev udev: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. udevadm trigger --verbose --subsystem-match=net --action=add will run read .link files from /run/systemd/network/10-netplan-interface1.link and apply MTU settings 4. during boot running (3) does not set the MTU; running (3) after boot has complete does. Here'a log during boot where cloud-init generates a netplan config, invokes netplan-generate and then udevadm trigger. Upon logging in interface1 has an MTU of 1500. Re-running udevadm trigger now runs the rules/link files and updates the MTU. Note that, if you run udevadm test /sys/class/net/interface1; this also will apply the MTU (test probably shouldn't change the interface, I'll file a bug for that as well). # journalctl -o short-precise --no-pager -b | grep WARK Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 'generate']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', '--no-block', 'systemd-udev-trigger.service']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', '--verbose', '--subsystem-match=net', '--action=add']: root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link [Match] MACAddress=52:54:00:12:34:02 [Link] Name=interface1 WakeOnLan=off MTUBytes=1492 root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1500 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 3287 (3.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add /sys/devices/pci:00/:00:04.0/virtio1/net/interface1 /sys/devices/pci:00/:00:05.0/virtio2/net/interface2 ys/devices/pci:00/:00:06.0/virtio3/net/interface0 /sys/devices/virtual/net/lo root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1492 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 37 bytes 3504 (3.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: udev 232-18ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Thu Mar 2 19:22:14 2017 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=8bbb84fe-91e8-4a9a-bd91-f6af4793727e ro console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.1-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-zesty:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-zesty dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug curtin uec-images zesty -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1669564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1668347] [NEW] Unable to set bridge_portpriority with networkd
Public bug reported: 1. root@ubuntu:/run/systemd/network# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 2. root@ubuntu:/run/systemd/network# apt-cache policy systemd systemd: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. Using a networkd config like this: # cat 10-netplan-eth1.network [Match] MACAddress=52:54:00:12:34:02 Name=eth1 [Network] Bridge=br0 LinkLocalAddressing=no IPv6AcceptRA=no [Bridge] Cost=50 Priority=28 % cat /sys/class/net/br0/brif/eth1/priority 28 4. % cat /sys/class/net/br0/brif/eth1/priority 32 When using ifupdown and /etc/network/interfaces to configure a bridge users are able to specify a bridge port priority: auto br0 iface br0 inet static address 192.168.1.1 bridge_ports eth1 eth2 bridge_portprio eth1 28 bridge_portprio eth2 14 Which results in the bridge hook scripts running: brctl setportprio br0 eth1 28 which is visible via: /sys/class/net/br0/brif/eth2/priority Note, networkd does not mention PortPriority under netdev Bridge section, however, PathCost is mentioned. It appears networkd is missing an implementation. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-18ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 17:11:32 2017 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=900c1e3f-f682-4455-949c-ebdbf60ac6f5 ro console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.1-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-zesty:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-zesty dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug curtin uec-images zesty -- 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/1668347 Title: Unable to set bridge_portpriority with networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1663725] [NEW] root on raid device doesn't get /dev/disk/by-id/md-{name, uuid} symlinks after boot
Public bug reported:
ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 4.9.0-15-generic #16-Ubuntu SMP Fri Jan 20 15:28:49 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@ubuntu:~$ apt-cache policy systemd
systemd:
Installed: 232-8
Candidate: 232-8
Version table:
*** 232-8 500
500 http://ports.ubuntu.com/ubuntu-ports zesty/main ppc64el Packages
100 /var/lib/dpkg/status
3) root@ubuntu:~# ls -al /dev/disk/by-id/md-*
lrwxrwxrwx 1 root root 9 Feb 10 19:42 /dev/disk/by-id/md-name-ubuntu:foobar ->
../../md0
lrwxrwxrwx 1 root root 9 Feb 10 19:42
/dev/disk/by-id/md-uuid-bd97a135:166d5e7e:29e6b0eb:a3cad7c3 -> ../../md0
4)root@ubuntu:~# ls -al /dev/disk/by-id/md-* returns nothing
Note, I can re-trigger events on md0 and the links will appear.
udevadm test $(udevadm info -q path -n /dev/md0)
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: udev 232-8
ProcVersionSignature: User Name 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic ppc64le
.var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
ApportVersion: 2.20.4-0ubuntu1
Architecture: ppc64el
CustomUdevRuleFiles: main_disk-part1.rules.rules third_disk.rules.rules
md0.rules.rules second_disk-part1.rules.rules second_disk.rules.rules
third_disk-part1.rules.rules main_disk-part2.rules.rules
fourth_disk.rules.rules fourth_disk-part1.rules.rules main_disk.rules.rules
Date: Fri Feb 10 19:38:42 2017
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.9.0-15-generic
root=UUID=a8f0a084-efb9-11e6-9e80-525400123456 ro console=hvc0
ProcLoadAvg: 0.32 0.17 0.06 1/146 6210
ProcLocks:
1: POSIX ADVISORY WRITE 5006 00:12:22238 0 EOF
2: POSIX ADVISORY WRITE 5015 00:12:22033 0 EOF
3: FLOCK ADVISORY WRITE 5007 00:12:22011 0 EOF
4: POSIX ADVISORY WRITE 4979 00:12:21491 0 EOF
5: POSIX ADVISORY WRITE 2643 00:12:13926 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 1157056 0 -1
ProcVersion: Linux version 4.9.0-15-generic (buildd@bos01-ppc64el-020) (gcc
version 6.3.0 20161229 (User Name 6.3.0-2ubuntu1) ) #16-User Name SMP Fri Jan
20 15:28:49 UTC 2017
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 1
cpu_coreson: Number of cores online = 1
cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255:
Machine is not SMT capable
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug curtin ppc64el uec-images zesty
** Tags added: curtin
--
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/1663725
Title:
root on raid device doesn't get /dev/disk/by-id/md-{name,uuid}
symlinks after boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1663725/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1649931] [NEW] systemd-networkd needs to ensure DNS is up before network-online.target
Public bug reported: Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached. This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug. ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: resolvconf (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/1649931 Title: systemd-networkd needs to ensure DNS is up before network- online.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1647020] [NEW] Brightness resets to full when on/off battery
Public bug reported: In yakkety, when my ThinkPad X250 goes on or off battery, the screen is reset to full brightness. Xenial and before did not have this problem. I have not found any other instances which trigger this (lid close, etc). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-power-manager 3.22.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 2 22:16:21 2016 InstallationDate: Installed on 2015-03-07 (637 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to yakkety on 2016-12-01 (1 days ago) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1647020 Title: Brightness resets to full when on/off battery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1647020/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] [NEW] systemd-networkd runs too late for cloud-init.service (net)
Public bug reported: Ubuntu Core 16 images using cloud-init fail to function when the DataSource is over the network (Like OpenStack) as networking is not yet available when cloud-init.service runs. cloud-init service unit deps look like this: [Unit] Description=Initial cloud-init job (metadata service crawler) DefaultDependencies=no Wants=cloud-init-local.service Wants=local-fs.target Wants=sshd-keygen.service Wants=sshd.service After=cloud-init-local.service After=networking.service Requires=networking.service Before=basic.target Before=dbus.socket Before=network-online.target Before=sshd-keygen.service Before=sshd.service Before=systemd-user-sessions.service Conflicts=shutdown.target Here's networkd unit deps: [Unit] Description=Network Service Documentation=man:systemd-networkd.service(8) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be # dropped once tuntap is moved to netlink After=systemd-udevd.service dbus.service network-pre.target systemd-sysusers.service systemd-sysctl.service Before=network.target multi-user.target shutdown.target Conflicts=shutdown.target Wants=network.target # On kdbus systems we pull in the busname explicitly, because it # carries policy that allows the daemon to acquire its name. Wants=org.freedesktop.network1.busname After=org.freedesktop.network1.busname And a critical-chain output: root@snap-test7:~# systemd-analyze critical-chain systemd-networkd Failed to get ID: Unit name systemd-networkd is not valid. The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. systemd-networkd.service +440ms └─dbus.service @11.461s └─basic.target @11.403s └─sockets.target @11.401s └─dbus.socket @11.398s └─cloud-init.service @10.127s +1.266s └─networking.service @9.305s +799ms └─network-pre.target @9.295s └─cloud-init-local.service @3.822s +5.469s └─local-fs.target @3.813s └─run-cgmanager-fs.mount @12.687s └─local-fs-pre.target @1.393s └─systemd-tmpfiles-setup-dev.service @1.116s +195ms └─kmod-static-nodes.service @887ms +193ms └─system.slice @783ms └─-.slice @721ms cloud-init would need networkd to run at or before 'networking.service' so it can raise networking to then find and use network-based datasources. # grep systemd /usr/share/snappy/dpkg.list ii libnss-resolve:amd64 229-4ubuntu11 amd64nss module to resolve names via systemd-resolved ii libpam-systemd:amd64 229-4ubuntu11 amd64system and service manager - PAM module ii libsystemd0:amd64 229-4ubuntu11 amd64systemd utility library ii systemd 229-4ubuntu11 amd64system and service manager ii systemd-sysv 229-4ubuntu11 amd64system and service manager - SysV links # grep cloud-init /usr/share/snappy/dpkg.list ii cloud-init 0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all Init scripts for cloud instances ** 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/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912/+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
According to the patch comments, it looks like it is fixed from nautilus 3.15.4 onwards. I am running Ubuntu 16.04.1 LTS and the "latest" version of nautilus I am running is 3.14.3. Sucks. -- 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 1506744] Re: Newly installed applications do not show in the dash
To elaborate on the previous remark: why didn't we just replace: menu_monitor_queue_event (event_info); with: g_timeout_add_seconds (2, menu_monitor_queue_event, event_info); (and make sure menu_monitor_queue_event() returns FALSE)? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
The latest patch looks good to me, but with a couple of notes (no need to fix these): - using the _full() version of the timeout call is not necessary here - now that this patch is simplified it becomes easy to see how all of this is just putting values into one structure and then later moving them into another structure. It seems like we could have just used the first structure type, or even just fixed the other queue mechanism to add the delay. Oh well. No real gain from making that change at this point. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
Switching away from Unity (and Ubuntu). This should be of high priority...especially because there is no launcher menu or other alternative to find your app. I'll try Ubuntu again in a year or so. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1506744] Re: Newly installed applications do not show in the dash
The patch in comment 42 is not acceptable, for two big reasons. First: you need to hold a ref on the GFile object when you put it into the info struct. This means that you cannot simply use g_free for the struct: you need to write a custom free func that handles the unref as well. Also: you can't cast g_source_remove() to a GDestroyNotify and expect that to work... one takes a pointer, and the other an int. This may randomly work on some architectures, sometimes, but you cannot rely on this. The entire act of keeping the list is slightly suspect. At the sprint I think I mentioned that it would be better to have one global timeout that is set (and reset) when any activity happens. The timeout would run after the activity died down, and it would handle all things together in one go. In that case, you'd still need a list, except for the info objects themselves. It's also fine to keep the list of the timeout IDs, but you can't free it in the way that you're doing in the current patch. Another nice approach, if you want to avoid running the callbacks after teardown: store a weak pointer to the main object in each of the info structs (g_object_add_weak_pointer). The info structs are then used as the user_data to the timeout (this assumes you keep the multiple timeouts). If you find the weak pointer to be empty, then just return without doing anything. That also means that you don't need to handle the "cleanup" -- it will happen automatically. It also means that you can avoid the custom free function if you are clever: the timeout will always run once, and you can do the cleanup from the normal handler (taking care regarding the early exit discussed above). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1409032] Re: gvfsd-smb: very high CPU utilisation
Ubuntu 16.04. gvfsd-smb-browse uses 100% CPU until I kill it. -- 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/1409032 Title: gvfsd-smb: very high CPU utilisation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573408] Re: GNOME Software does not install third-party .deb packages
The proposed fix worked for me as well. I was also able to do a standard 'sudo apt-get update' repo update afterwards, without error. I installed VirtualBox from a .deb -- 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/1573408 Title: GNOME Software does not install third-party .deb packages To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1573408/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1237355] Re: Logitech Ultrathin Touch Mouse needs to be repaired
I am also still experiencing the same issues using the Ultrathin Touch Mouse on Ubuntu 14.04. In addition the cursor gets extremely laggy at times. Not to the point where its unusable, but it is a noticeable drag. -- 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/1237355 Title: Logitech Ultrathin Touch Mouse needs to be repaired To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1237355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
Hi Pradeep, On Wed, Sep 16, 2015 at 06:14:21AM -, Pradeep Kumar wrote: >Sorry if i am re-asking again. Please let me know if the fix is released >for the below versions. Yes, it looks like you have the fixed version. >I could still see gray screen after logging in. >If it is released , Kindly let me know how to fix the same. Please ask for support in an appropriate venue: http://www.ubuntu.com/support http://ubuntuforums.org/ http://askubuntu.com/ I haven't looked at xrdp ever since working on this bug, but IIRC it did still require a bit of configuration (see e.g. comment 58) and reading of scripts to see how things are put together. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)
Still exists in Xubuntu 14.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/772709 Title: Network Manager Icon Is not changin when VPN is connected (nm-device- wired-secure icon is missing) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-icon-theme/+bug/772709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)
** Also affects: gnome-icon-theme Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/772709 Title: Network Manager Icon Is not changin when VPN is connected (nm-device- wired-secure icon is missing) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-icon-theme/+bug/772709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
** Bug watch added: bugs.x2go.org/ #96 http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=96 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
On Sat, Apr 25, 2015 at 08:51:37AM -, martin lantz wrote: >The screen resolution did not adjust to the monitor i am using and the >menu just happened to be off screen. The mate session seams to adjust >automatically. Ah, right. Yes, this is a known problem with GNOME3 under NX3 and its derivatives: https://www.nomachine.com/AR06J00636 http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=96 Glad you figured it out. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
On Thu, Apr 23, 2015 at 09:02:19AM -, martin lantz wrote: >I logged into NX using gnome-terminal. From there I run: >/usr/bin/gnome-session --session=gnome-flashback --disable-acceleration-check >&> gnome-session.log.0 > >The desktop background image appears, but nothing else seems to work. > >I uploaded gnome-session.log.0 here: >http://pastebin.com/tvVU2fMa Looks like the /etc/X11/Xsession wrapper is being used; it's trying to launch an Upstart session. In this case you need to export: DESKTOP_SESSION="gnome-fallback" XDG_CURRENT_DESKTOP="Unity" in order for the upstart Xsession.d scripts to work properly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
On Wed, Apr 22, 2015 at 06:04:55PM -, martin lantz wrote: >I have NX version 3.5 installed on a Ubuntu 14.04 server. I have just >install the relevant version of the packages discussed above. > >I can login successfully running the following command >"/etc/X11/Xsession mate-session" > >But when I login using "/usr/bin/gnome-session --session=gnome-flashback >--disable-acceleration-check" the desktop appears but there is no menu >and no unity launcher. Unity does not work under NX 3.5. These changes do not address that. You should be seeing the classic GNOME desktop with panels on top and bottom. I've just tested the same gnome-session command you mentioned under x2goserver (based on NX 3.5) and it works. Please double-check the versions of the relevant packages: - gnome-session-bin 3.9.90-0ubuntu12.1 - libgnome-desktop-3-7 3.8.4-0ubuntu3.1 If you still have problems, please log into your NX with just "xterm" as the command (or "gnome-terminal"), run your gnome-session command in that terminal, and pastebin the output somewhere. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
Hi all, The patches that were in my PPA (ppa:rtandy/flashback) are now in trusty-proposed and utopic-proposed; so if you were using those packages, please head over to bug 1416081, test the proposed packages, and leave your feedback there. If you had the PPA packages installed, please ensure you _downgrade_ to the proposed packages as the version in -proposed is lower than what was in the PPA. ppa-purge may help with that. (My bad; will choose ppa versions more carefully next time.) Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
On Wed, Apr 01, 2015 at 08:12:23PM -, Michael Plotkin wrote: >Apr 1 05:17:12 marina-net /usr/bin/x2goruncommand: launching session >with Xsession-x2go mechanism, using STARTUP="gnome-session >--session=gnome-flashback --disable-acceleration-c\ >heck" >Apr 1 05:17:20 marina-net kernel: [ 1747.973711] gnome-session[7806]: >segfault at 18 ip 7fc4c3952196 sp 7fff7f38a820 error 4 in >libgnome-desktop-3.so.7.0.0[7fc4c393+3\ >1000] This is bug 1416081. > So my conclusion is that the fix in the trusty-proposed repository as >it stands >there right now is not helpful at all Not true. Your STARTUP above includes '--disable-acceleration-check' which was only added in the version currently in trusty-proposed. > gnome-session-flashback/Unity fails to start without hardware > acceleration in cloud/remote environments > (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) > >To manage notifications about this bug go to: >https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions On Wed, Apr 01, 2015 at 08:36:48PM -, Alberts Muktupāvels wrote: >Segfault in libgnome-desktop is another bug/problem and is >not directly related to this bug. And probably should be reported as >separate/new bug. Already fixed in vivid, and proposed patches for SRU. Any help getting those uploaded would be tremendously welcome. :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
Marking verified, based on my own testing and on Xavier's confirmation that 'gnome-session --disable-acceleration-check' works for him in trusty. Xavier: right now 'gnome-session --disable-acceleration-check' is only supported in trusty-proposed, as soon as it's released to -updates that won't be needed any more. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 383118] Re: gamin doesn't notice local file creation on NFS4
$ lsb_release -cd Description:Ubuntu 14.04.2 LTS Codename: trusty $ grep /home /proc/mounts auto.misc /home autofs rw,relatime,fd=6,pgrp=1351,timeout=300,minproto=5,maxproto=5,direct 0 0 server:/home /home nfs4 rw,nosuid,nodev,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.0.253.227,local_lock=none,addr=10.0.2.1 0 0 $ gvfs-monitor-dir . & [1] 2986 $ touch test $ Directory Monitor Event: Child = /home/rtandy/test Event = CREATED Directory Monitor Event: Child = /home/rtandy/test Event = ATTRIB CHANGED Directory Monitor Event: Child = /home/rtandy/test Event = CHANGES_DONE_HINT $ rm test $ Directory Monitor Event: Child = /home/rtandy/test Event = DELETED Marking fixed in gvfs. I don't know how to test gamin. ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- 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/383118 Title: gamin doesn't notice local file creation on NFS4 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/383118/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
I tried to verify this, but bug 1416081 blocks testing with tightvncserver and xrdp as well as with x2goserver. Would anyone be willing to upload the patches in that bug to -proposed as well? I will fill in the SRU paperwork shortly. In the mean time, ppa:rtandy/flashback contains the necessary patches for testing. My testing steps: - install gnome-session-flashback and tightvncserver, - (trusty/utopic): install gnome-session-bin from -proposed, - create ~/.vnc/xstartup with appropriate contents: (vivid, session managed by gnome-session:) export XDG_CURRENT_DESKTOP="GNOME-Flashback:Unity" export STARTUP="gnome-session --session=gnome-flashback-metacity --disable-acceleration-check" exec /etc/X11/Xsession (vivid, session managed by upstart:) export DESKTOP_SESSION=gnome-flashback-metacity export XDG_CURRENT_DESKTOP="GNOME-Flashback:Unity" exec /etc/X11/Xsession gnome-session (trusty/utopic, session managed by gnome-session:) export STARTUP="gnome-session --session=gnome-flashback --disable-acceleration-check" exec /etc/X11/Xsession (trusty/utopic, session managed by upstart:) export DESKTOP_SESSION=gnome-fallback export XDG_CURRENT_DESKTOP=Unity exec /etc/X11/Xsession gnome-session - chmod +x ~/.vnc/xstartup, - run vncserver, - from another host, run vncviewer. The keyboard problem I mentioned earlier seems to be related to bug 568401 and bug 658723 (but not bug 112955 or bug 112309). Basically Super modifier is always active when connected over VNC (or xrdp, as it uses VNC behind the scenes). FreeNX/X2Go don't seem to have this problem. With regards to this bug specifically, AFAICT the gnome-session changes in -proposed (supporting the --disable-acceleration-check switch, and applying it to upstart-managed gnome-flashback sessions) are working, but I'd love if a second person would confirm that! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
Hi penalvch, Whether or not this works with xrdp probably depends on how your session is set up. I just tried installing gnome-session-flashback and xrdp on the vivid daily CD; the default configuration does nothing, but the following ~/.xsession: env DESKTOP_SESSION="gnome-flashback-metacity" XDG_CURRENT_DESKTOP ="GNOME-Flashback:Unity" gnome-session --session=gnome-flashback --disable-acceleration-check does load the session. (but the keyboard layout seems wrong somehow... :/) If xrdp needs to be adjusted to set this up by default, or documented somehow, maybe that should be a separate bug against xrdp. Thanks for your work triaging and testing! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
I am happily running GNOME Flashback with the FreeNX server, and nx-libs from the X2Go stable PPA, on multiple Trusty terminal servers and it has been quite stable. The gnome-session --disable-acceleration-check option is needed, and also bug 1416081 has to be fixed to stop unity-settings- daemon from crashing. I have uploaded all the necessary patches to ppa:rtandy/flashback and attached them to these bugs. In the PPA I also patched gnome-session-flashback to use --disable-acceleration-check, but it's not really necessary -- just for symmetry :). Attached is the FreeNX config file I use. Note it relies on the Upstart session job to pass "--disable-acceleration-check" to gnome-session. For X2Go, /usr/bin/x2goruncommand has to be adjusted similarly; I will follow up to their tracker (http://bugs.x2go.org/cgi- bin/bugreport.cgi?bug=774) soon. I hope these patches can be considered for vivid, and maybe for trusty/utopic SRU as well. Thanks for reading! ** Bug watch added: bugs.x2go.org/ #774 http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=774 ** Attachment added: "/etc/nxserver/node.conf.d/20_gnome-flashback.conf for freenx-server" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1251281/+attachment/4336491/+files/20_gnome-flashback.conf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
** Patch added: "utopic gnome-session patch" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1251281/+attachment/4336489/+files/gnome-session_3.9.90-0ubuntu17.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
** Patch added: "vivid gnome-session patch" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1251281/+attachment/4336487/+files/gnome-session_3.14.0-2ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
