[Bug 2039365] [NEW] should not declare a directory that contains only hidden files "empty"
Public bug reported: Nautilus displays a big directory symbol alongside the message "directory is empty" [or something to that effect] for empty directories. However, it does not differentiate at all between directories that are truly empty, and directories that contain only hidden files and directories (i.e. their names start with a dot). I've lost data that way. By removing seemingly "empty" directories, I mean. More than once. (The fact that the recycle bin is broken on btrfs [see Debian bug #698640) does not help. Could nautilus display, I don't know, a question mark in the symbol and "contains only hidden items" in the description or something? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-lowlatency 6.2.16 Uname: Linux 6.2.0-1014-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 14 21:11:29 2023 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1877, 841)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'213' InstallationDate: Installed on 2023-08-02 (73 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/2039365 Title: should not declare a directory that contains only hidden files "empty" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2039365/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033323] Re: will only come up on second seat once [loginctl multiseat]
Workaround: apt install lightdm lightdm-gtk-greeter. Works OOTB for me, with the very big caveat that screen locking will be disabled (that requires gdm). -- 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/2033323 Title: will only come up on second seat once [loginctl multiseat] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2033323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033324] Re: no adapter found on second seat [loginctl multiseat]
Found the cause: gsd-rfkill[2049]: Could not open rfkill device: Could not open RFKILL control device, please verify your installation GNOME's BT GUI needs access to /dev/rfkill to work. It's tagged "uaccess" in udev, so in theory all logged-in users should get access via an ACL, but in practice this doesn't seem to work for seats other than seat0 in a multiseat scenario. Removing the "seat" tag and re-adding the "shared" tag via custom udev rule doesn't help--the acl doesn't get added if you don't login on seat0. Of course simply changing the permissions to 666 does the trick until the next reboot, but ... So, not a gnome-bluetooth* bug, nor a gnome-control-center one, but whose is it? Logind? /dev/rfkill should be available to all users logged in locally, IMHO. -- 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/2033324 Title: no adapter found on second seat [loginctl multiseat] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/2033324/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033324] [NEW] no adapter found on second seat [loginctl multiseat]
Public bug reported:
I've set up a second seat via loginctl --attach, resulting in the
following udev rules:
TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0",
ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_6e_00_1", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_6e_00_3-usb-0_1",
ENV{ID_SEAT}="seat1"
(Since loginctl doesn't consider BT adapters per-seat--they don't show
up in loginctl seat-status at all--adding an extra one and assigning it
to seat1 does accomplish nothing.)
However, when logged in on seat1 the GNOME BT settings panel insists
there's no BT adapter attached.
Funnily enough
- the top-right drop-down menu shows (some?) connected devices
- opening the BT settings panel triggers something alright (as seen in
bluetoothctl)
If a BT adapter is not a per-seat resource then I'd expect it to be
configurable by (authorised) users no matter what seat they log in on.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-bluetooth 3.34.5-8
Uname: Linux 6.4.12-060412-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Aug 29 00:22:00 2023
InstallationDate: Installed on 2023-08-25 (3 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
SourcePackage: gnome-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy third-party-packages
--
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/2033324
Title:
no adapter found on second seat [loginctl multiseat]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/2033324/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033323] [NEW] will only come up on second seat once [loginctl multiseat]
Public bug reported:
I've set up a second seat via loginctl --attach, resulting in the
following udev rules:
TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0",
ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_6e_00_1", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_6e_00_3-usb-0_1",
ENV{ID_SEAT}="seat1"
Because of #2033322, WaylandEnable=false is set in
/etc/gdm3/custom.conf.
It works great--except it does so only once. I can login on seat1 just fine,
except when I log out, the greeter doesn't come back up again, it just leaves
me with a black screen.
Can be recovered from by restarting gdm (via ssh from another box or from
seat0), but obviously that isn't ideal.
I've attached a pstree for the working case (no GUI logins, both
greeters up) and the non-working post-logout one (no GUI logins, only
seat0 hat a greeter up); please advise re. what logs to provide.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7.22.04.3
Uname: Linux 6.4.12-060412-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Aug 29 00:02:03 2023
InstallationDate: Installed on 2023-08-25 (3 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2023-08-28T23:54:05.623349
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy third-party-packages
** Attachment added: "output of pstree for the working and nonworking case"
https://bugs.launchpad.net/bugs/2033323/+attachment/5695783/+files/pstree.tgz
--
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/2033323
Title:
will only come up on second seat once [loginctl multiseat]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2033323/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033322] [NEW] multiseat (via loginctl) will not work unless Wayland is disabled
Public bug reported:
When a second seat is set up via loginctl --attach, the greeter will not
come up on the second screen unless WaylandEnable=false is set in
/etc/gdm3/custom.conf (and gdm restarted).
For completeness' sake, the udev rules set up by loginctl are:
TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0",
ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_6e_00_1", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_6e_00_3-usb-0_1",
ENV{ID_SEAT}="seat1"
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7.22.04.3
Uname: Linux 6.4.12-060412-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Aug 28 23:54:57 2023
InstallationDate: Installed on 2023-08-25 (3 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2023-08-28T23:54:05.623349
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy third-party-packages
--
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/2033322
Title:
multiseat (via loginctl) will not work unless Wayland is disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2033322/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2030963] [NEW] default theme highlights hard to see
Public bug reported: In 22.04's default theme, it's almost impossible for me to make out which app or window is the currently selected one in the window switcher (alt-tab) or the application switcher (super-tab). The "highlighted" item is just a slightly different shade of grey. I mean, I can make it out if I squint at it, but ... that just isn't a *highlight*. This is a use where Ubuntu Orange shines, too. :-( Similarly, the active workspace in the workspace overview (?) does get an orange frame, but it's very thin, much too thin to see unless you look closely. Again, that's not a highlight. A highlight is supposed to pop out. In comparison, the highlighting for the current tab in Terminal is ok- ish. I'd *prefer* for the entire tab to become orange, or to become a lighter colour in addition to the orange bar, but it's usable. "Ok, boomer, you're blind. I can see that just fine". Fair enough. Are you under thirty and (thus still) have 20:20 vision, by any chance? The point is, it isn't good UI design either way. What's worse, the high contrast accessibility setting doesn't touch any of it, and that is definitely a bug. (I could go on. For example, windows' title bars are now white vs the iconic Ubuntu Brown, which makes it hard to tell where the title bar is vs the window contents. Many applications also have buttons in the title bar now. It's no longer possible to just grab a window and move it on auto-pilot ... If the title bar can't be a different colour any more, at least separate it with a thick line or something. In any case, 22.04 is a massive regression in terms of visual UI design vs 18.04. Form should follow function, not the other way around.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 10 12:58:31 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (7 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/2030963 Title: default theme highlights hard to see To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2030963/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860705] [NEW] search provider / search bar integration has stopped working
*** This bug is a duplicate of bug 1859555 *** https://bugs.launchpad.net/bugs/1859555 Public bug reported: Previously, I could call up Gnome's desktop overview[?], e.g. via the Windows key, and type a simple calculation straight into the search bar on top. Gnome calculator would then provide the result of that calculation as a "search result", and give me the option to copy it to the clipboard or start gnome-calculator proper and continue working with it. Currently, typing numbers and/or operators into the search bar will not trigger gnome-calculator any more, as if its search provider was disabled. (It's not, I triple-checked.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator 1:3.28.2-1~ubuntu18.04.3 Uname: Linux 5.4.0-050400rc7-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 19:17:32 2020 InstallationDate: Installed on 2019-09-23 (122 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** This bug has been marked a duplicate of bug 1859555 Calculator does not work in GNOME activities search -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1860705 Title: search provider / search bar integration has stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1860705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
