[Bug 1913681] [NEW] multiple monitors with mixed DPI not scaling correctly
Public bug reported: I am running 3 monitors under wayland. 2x 1440p monitors at 1x scale (one of these is my primary display) 1x 4k laptop at 2x scale The majority apps seem to not get correct scaling on the 2x display. gnome-control-center is the one that seems to work correctly. Things like chrome, firefox and most other apps (which work fine when only using the single 4k) are all tiny on the laptop display. Its the same in reverse also, if I set the 4k screen as primary most windows (again except gnome-control-centre) are too large on the 1550p screens. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 29 17:43:58 2021 InstallationDate: Installed on 2020-07-23 (190 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session ** Description changed: I am running 3 monitors under wayland. 2x 1440p monitors at 1x scale (one of these is my primary display) 1x 4k laptop at 2x scale The majority apps seem to not get correct scaling on the 2x display. gnome-control-center is the one that seems to work correctly. Things like chrome, firefox and most other apps (which work fine when only using the single 4k) are all tiny on the laptop display. + + Its the same in reverse also, if I set the 4k screen as primary most + windows (again except gnome-control-centre) are too large on the 1550p + screens. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter 3.38.2-1ubuntu1~20.10.1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 29 17:43:58 2021 InstallationDate: Installed on 2020-07-23 (190 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1913681 Title: multiple monitors with mixed DPI not scaling correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1913681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895083] [NEW] Authenticate/Decrypt packet error: packet HMAC authentication failed
Public bug reported: Since upgrading to groovy my openvpn connection out to our corporate is not working. I was testing Iwd but have now reverted to wpa_supplicant. Connection to the vpn succeeds and routing table gets setup no traffic is flowing over the connection and I get the following errors nm-openvpn[4428]: Authenticate/Decrypt packet error: packet HMAC authentication failed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: network-manager-openvpn 1.8.12-2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Sep 10 15:06:03 2020 InstallationDate: Installed on 2020-07-23 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to groovy on 2020-08-31 (10 days ago) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- 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/1895083 Title: Authenticate/Decrypt packet error: packet HMAC authentication failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1895083/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
I had the same issue a few weeks ago, now however with 3.31.92 (on Disco) I do get the configuration dropdown when selecting my HDMI Audio device. It came up blank initially, but appears to have saved the correct setting since. -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819263] Re: GNOME Shell applet can't open System Monitor installed as Snap
Hi Peter, Thanks for your bug report. I was one of the original authors the system-monitor extension however no longer actively involved in the project. gnome-shell extensions are not supported by Canonical/Ubuntu (unless they are installed in the default session) or GNOME. You would need to fix system-monitor extension to support querying for snaps in case the desktop file is not found. This could easily be done through the CLI with `snap list` and `snap run`. However a much nicer solution would probably be to use snapd-glib which provides gobject-introspection bindings to snapd. I am not really familiar with their API, but suspect it should provide similar functionality to the CLI tool. I am going to close this bug since its not really a bug in gnome-system- monitor and could equally happen on any other distro that supports snaps, if the user has installed gnome-system-monitor as a snap instead of native packaging. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Invalid -- 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/1819263 Title: GNOME Shell applet can't open System Monitor installed as Snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1819263/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792403] Re: Nautilus 3.30 in Gnome Staging PP does not start without tracker package
Probably the tracker patch needs to be updated, there seem to be a couple of new modules using tracker that didnt exist when I wrote that patch. Upstream last I check only supports optional tracker at build time. Not run-time detection like we did in distro patches in Ubuntu. -- 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/1792403 Title: Nautilus 3.30 in Gnome Staging PP does not start without tracker package To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1792403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792403] Re: Nautilus 3.30 in Gnome Staging PP does not start without tracker package
** Bug watch added: Debian Bug tracker #908800 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800 ** Also affects: nautilus via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792403 Title: Nautilus 3.30 in Gnome Staging PP does not start without tracker package To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1792403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791991] Re: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff)
thumbnailers are working fine for me, both tiff and jpg, perhaps there is still a missing dependency, that is normally otherwise pulled in by vanilla-gnome-desktop. I generally only test gnome3-staging on systems with that meta package. Can you file a separate bug for nautilus not starting without out the tracker package installed. That will probably need to be optional when nautilus 3.30 lands in Ubuntu proper next cycle. -- 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/1791991 Title: Nautilus in Gnome3 Staging PPA does not create thumbnails (tiff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1791991] Re: Nautilus in Gnome3 Staging PPA will not start
can you try reinstall tracker 2.1.3 and see if that file exists on your filesystem? If it doesnt please run apport-collect which should colllect your dpkg/apt logs. see this page for manually getting backtraces https://wiki.ubuntu.com/DebuggingProgramCrash On 12/09/18 18:06, Harry wrote: > I did get the default.rule error (starting from terminal) when I had > installed both the nautilus_3.30.0-0ubuntu1~cosmic1 and the > tracker_2.1.3-1~cosmic1 packeges. > As I mentioned, at that time nautilus did not start, the small wheel on the > screen just kept on turning. > > Then, after downgrading tracker_2.1.3-1~cosmic1 back to the official > tracker_2.0.3-3, I did get nautilus_3.30.0-0ubuntu1~cosmic1 running. > However, the thumbnailer did not work then. > > Sorry, I am not familiar with the backtrace system. > -- 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/1791991 Title: Nautilus in Gnome3 Staging PPA will not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791991] Re: Nautilus in Gnome3 Staging PPA will not start
Hi Harry, Thank you for your bug report. I am running nautilus 3.30 with tracker 2.1.3 on two system and they are both working, so we will need some more info. Thumbnails are working also That default.rule file does exist in the tracker 2.1.3-1~cosmic1 package, is it not installed on your filesystem? does nautilus crash? if so can you get a backtrace. Unfortunately we no longer have retracers running against this ppa, so that need to be done manually using ubuntu-bug. -- 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/1791991 Title: Nautilus in Gnome3 Staging PPA will not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791991/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791484] [NEW] [FFe] Update tracker and tracker-miners to 2.1.4
Public bug reported: To go along with the rest of GNOME 3.30 Both tracker and tracker-miners 2.1.4 will be synced from Debian. tracker is not installed by default on any Ubuntu Flavours, but does provide an important part of the GNOME-Shell experience. These releases bring lots of fixes and a few new features. Tracker NEW in 2.1.4 - 2018-09-04 = * Fix build with format-security flag Translations: da, hr, lv NEW in 2.1.3 - 2018-08-30 = * Fix resource refcounting issues in database. Reset is advised. * Drop cardinality from nie:copyright, nie:license, nie:legal and dc:rights * Fix superfluous ontology checks on second tracker-store run * Use more SPARQL1.1 correct syntax. * Allow use of domain rules outside prefix * Compatibility fixes with C++ Translations: gl, id, ko NEW in 2.1.2 - 2018-08-15 = * libtracker-sparql: Delete TrackerResource elements one by one * libtracker-sparql: Fix compilation with C++ * build: Fixes for FreeBSD * build: Fixes on meson Translations: cs, el, fr, fur, hu, sl, tr, zh_TW NEW in 2.1.1 - 2018-08-01 = * libtracker-direct: Plug leaks * libtracker-sparql-backend: Fix fallback from direct to bus connection for queries. Translations: es, lt, ro NEW in 2.1.0 - 2018-07.22 = * Brown paper bag release * All features from unreleased 2.0.5 apply * One feature was missed: TrackerResource is now able to output JSON-LD. This is a new API call, so a minor bump should happen as per Semantic Versioning. From 2.0.5 NEWS: * build: Make tarballs able to build with meson. Future releases will eventually phase out Autotools * build: Various meson build fixes * tests: Many fixes to functional tests * libtracker-miner: Fixed race conditions that may result in spurious "parent not indexed yet" warnings. * libtracker-direct: Majorly rewritten * tracker-store: Streamlined to use a libtracker-direct connection instead of reimplementing most of it. Tracker-miners NEW in 2.1.4 - 2018-09-04 = Translations: da, hr, lv NEW in 2.1.3 - 2018-08-30 = * Unbreak watch on domain ontology owner. Fixes miners spuriously exiting. NEW in 2.1.2 - 2018-08-30 = * Allow use of domain rules outside prefix * Add core-as-subproject as explicit meson option * Ensure utf8ness in TrackerResource helpers * Fix multiple cardinality issues in different extractors/properties * Other minor SPARQL correctness fixes Translations: gl, id, ko NEW in 2.1.1 - 2018-08-15 = * tracker-miner-fs: Ignore mercurial repositories * build: Fix build with -Werror=format-security * tracker-extract: Ensure metadata strings are UTF-8 in JPEG/PNG extractors * tracker-extract: Do not add named destinations to PDF TOCs * tracker-extract: Ignore XMP image metadata on PDFs * tracker-extract: Fix ISO 8601 date string generation on gstreamer extractor Translations: cs, el, fr, fur, hu, lt, sl, tr, zh_TW NEW in 2.1.0 - 2018-07-23 = * tests: Many updates and fixes to functional tests * tracker-extract: Better infrastructure for tests, based on JSON-LD * tracker-miner-fs: Restart tracker extract from the right domain * tracker-extract: Persistently avoid files that trigger recoverable errors, to avoid log spamming on restarts. Translations: de, es, it, pl, pt_BR, ro, sv ** Affects: tracker (Ubuntu) Importance: Wishlist Status: New ** Tags: upgrade-software-version ** Summary changed: - [FFe] Update to 2.1.4 + [FFe] Update tracker and tracker-miners to 2.1.4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1791484 Title: [FFe] Update tracker and tracker-miners to 2.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1791484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774215] Re: adding a security banner key file in /etc/dconf does not work after latest update
What did you upgrade from? I think the banner would be set in /etc/gdm3/greeter.dconf-defaults these days -- 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/1774215 Title: adding a security banner key file in /etc/dconf does not work after latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774215/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770827] Re: GDM doesn’t use alternative for lock screen
the gdm greeter/login screen and the lock screen are mostly independent. The gdm greeter runs its own instance of gnome-shell running in a special gdm mode. The lock screen is drawn by the current gnome-shell session and thus uses the current gnome-shell theme. What gnome-shell theme are you using? I assume it is not adwaita. probably what you want to is to set the alternative to your gnome-shell theme ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- 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/1770827 Title: GDM doesn’t use alternative for lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770827/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout
OP said that this also affects Xubuntu and Lubuntu so its not likely only gnome-settings-daemon involved here, since neither of them use it. -- 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/1758647 Title: ubiquity doesn't preselect the right default keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756061] Re: '/var/log/gdm3/': Permission denied
/var/log/gdm is still used as a fallback in case journald is unavailable or disabled. Unless upstream remove that I don't think we should remove it from the packaging. ** Changed in: gdm3 (Ubuntu) Status: New => Won't Fix -- 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/1756061 Title: '/var/log/gdm3/': Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756061] Re: '/var/log/gdm3/': Permission denied
gdm still runs under wayland by default. It is the "Ubuntu" login session that defaults to Xorg. -- 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/1756061 Title: '/var/log/gdm3/': Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756061] Re: '/var/log/gdm3/': Permission denied
gdm logs to systemd journal these days. You need to enable debugging in /etc/gdm3/custom.conf to get any useful logs though -- 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/1756061 Title: '/var/log/gdm3/': Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
