[Bug 2063383] [NEW] [SRU] Ubuntu Unity takes 90 seconds to log out
Public bug reported: [ Impact ] Ubuntu Unity reliably takes 90 seconds to log out. This is due to the user-level gnome-session.service systemd unit not properly terminating gnome-session on logout. An attempt is made to send SIGTERM to the process, which gnome-session does not care about. Instead, gnome-session-quit should be invoked when the systemd unit shuts down, which acts effectively and immediately. [ Test Plan ] Actual behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that only the wallpaper is shown for 90 seconds prior to the login manager showing again. Expected behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that logging out takes a few seconds at most, and you are able to log back in as the same user, or a different one. [ Where problems could occur ] If the gnome-session or gnome-session-quit binaries change the arguments they accept by default, log in and log out functionality on Unity sessions are likely to break. Additionally, if lightdm or systemd changes in a non-reverse-compatible way, this increases the chance of a user-facing regression. ** Affects: gnome-session (Ubuntu) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Affects: gnome-session (Ubuntu Noble) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Summary changed: - Ubuntu Unity takes 90 seconds to log out + [SRU] Ubuntu Unity takes 90 seconds to log out ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed ** Changed in: gnome-session (Ubuntu) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Also affects: gnome-session (Ubuntu Noble) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Changed in: gnome-session (Ubuntu Noble) Milestone: None => noble-updates -- 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/2063383 Title: [SRU] Ubuntu Unity takes 90 seconds to log out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2062956] Re: CVE-2024-32462 - Need to update to the last secure patch
*** This bug is a duplicate of bug 2062406 *** https://bugs.launchpad.net/bugs/2062406 This is the same vulnerability as LP: #2062406. ** This bug has been marked a duplicate of bug 2062406 CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2062956 Title: CVE-2024-32462 - Need to update to the last secure patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2062956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060154] Re: Sort by "Modified" uses lexicographic ordering
** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/2060154 Title: Sort by "Modified" uses lexicographic ordering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060154] Re: Sort by "Modified" uses lexicographic ordering
nautilus --version GNOME nautilus 45.rc -- 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/2060154 Title: Sort by "Modified" uses lexicographic ordering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060154] [NEW] Sort by "Modified" uses lexicographic ordering
Public bug reported: I have opened a folder where the subfolder dates go back a few years. Expect 16 Feb 2024 < 9 Feb 2024 Actual 9 Feb 2024 < 16 Feb 2024 It seems that the folders are sorted lexicographically by their date string, not chronologically. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2024-04-03 11-58-15.png" https://bugs.launchpad.net/bugs/2060154/+attachment/5761500/+files/Screenshot%20from%202024-04-03%2011-58-15.png -- 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/2060154 Title: Sort by "Modified" uses lexicographic ordering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2060154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2058769] Re: proposed-migration for click 0.5.2-2
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: - click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf, - and possibly on all archs. + click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el, + s390x. - armhf binary will be removed from the release pocket. + In order to be able to run the tests without all-proposed=1, glib 2.0 is + needed, which is why I marked it as affected. + + Excerpt of the test logs: + + ERROR: test_list_simple (click_package.tests.integration.test_list.TestList.test_list_simple) + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_list.py", line 29, in test_list_simple + self.click_install(path_to_click, name, user) + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/helpers.py", line 99, in click_install + subprocess.check_call(cmd) + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) + subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '--allow-unauthenticated', '/tmp/tmpqhzp18eh/com.ubuntu.verify-ok_1.0_all.click']' returned non-zero exit status 1. + + == + ERROR: test_debsig_install_valid_signature (click_package.tests.integration.test_signatures.TestSignatureVerification.test_debsig_install_valid_signature) + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 207, in test_debsig_install_valid_signature + subprocess.check_call( + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) + subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--user=root', '/tmp/tmpymtfsjg9/org.example.debsig-valid-sig_1.0_all.click']' returned non-zero exit status 1. + + == + ERROR: test_debsig_install_can_install_with_sig_override (click_package.tests.integration.test_signatures.TestSignatureVerificationNoSignature.test_debsig_install_can_install_with_sig_override) + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.VczHPz/build.dRN/src/click_package/tests/integration/test_signatures.py", line 164, in test_debsig_install_can_install_with_sig_override + subprocess.check_call( + File "/usr/lib/python3.12/subprocess.py", line 413, in check_call + raise CalledProcessError(retcode, cmd) + subprocess.CalledProcessError: Command '['/usr/bin/click', 'install', '--allow-unauthenticated', '--user=root', '/tmp/tmpheysy9ze/org.example.debsig-no-sig_1.0_all.click']' returned non-zero exit status 1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2058769 Title: proposed-migration for click 0.5.2-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/2058769/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2056561] Re: Libc6 bug in gvfs-udisk
Unless I'm missing something, the issue you're linking is about glib, not glibc. Reassigning the bug accordingly. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2056561 Title: Libc6 bug in gvfs-udisk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2056561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
We had a mitigation for this in glibc but the latest change from simply denying the unshare() call to allowing it but then denying anything requiring capabilities *presumably* broke the glibc test suite again. I'm only basing this from looking at the test logs, as I'm temporarily unable to run autopkgtests locally and am lacking the time to fix it. 2 classes of errors: 2770s FAIL: stdlib/tst-system 2770s original exit status 1 2770s error: test-container.c:1136: could not create a private mount namespace That one is clearly userns-related, as it's due to a failing mount() call right after unshare() 2770s FAIL: sunrpc/tst-svc_register 2770s original exit status 1 2770s error: xwrite.c:32: write of 12 bytes failed after 0: Operation not permitted 2770s error: 1 test failures I can't tell for sure what this one is about since this is your basic write() call and I don't have a stack trace at hand, but the EPERM would suggest that it's related. I think a first fix would be to amend the test script to disable the userns restriction entirely for the duration of the tests (using 'needs- sudo'), while I'll still need to patch the test suite eventually to handle this new failure mode gracefully and simply ignore the tests, akin to https://sourceware.org/pipermail/libc- alpha/2024-February/154754.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
The workaround from #71 worked almost perfectly out of the box, I've only seen 1-2 windows staying under the dock. I probably simply need bump the delay a bit from the default value. Thanks a lot @popov895. @ballogy, thanks for working on this with upstream! -- 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/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049895] Re: Distorted mouse pointer in the remote window
With non-factional scale like 100%/200% the issue is not reproducible. Also, rare after OS restart the pointer is correct, but then there is an another issue: pointer cannot "touch" the upper edge of the screen so the autohided top bar does never show up on the remote screen. -- 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/2049895 Title: Distorted mouse pointer in the remote window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2049895/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
** Changed in: glibc (Ubuntu) Status: Triaged => Fix Released ** Changed in: pango1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
So, after some fairly exhausting debugging, I kind of gave up on that bug, but as a last ditch effort I tried a rebuild against the latest snapshot (even though the changelog didn't seem particularly relevant), nd... Now it builds. I'm so tired. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
** Changed in: glibc (Ubuntu) Importance: Undecided => Critical ** Changed in: glibc (Ubuntu) Status: New => Triaged ** Changed in: glibc (Ubuntu) Assignee: (unassigned) => Simon Chopin (schopin) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot
I'm currently focused on cataloguing failures, but I'll try to investigate it if nobody has picked it up by then. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2049881] [NEW] pango1.0: FTBFS against glibc 2.39 snapshot
Public bug reported: Hi, The package pango1.0 failed to build during the recent full archive test rebuild against a snapshot of the the development branch for the upcoming glibc 2.39, expected to land in Noble. This was subsequently confirmed locally against a more recent snapshot. Full logs for the FTBFS: https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz Full report: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html PPA with glibc snapshot: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Snippet showing the failure: === 22/27 test: test-fonts start time: 10:25:39 duration: 0.11s result: exit status 1 command: G_TEST_SRCDIR=/<>/tests srcdir=/<>/tests LC_ALL=en_US.UTF-8 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k --tap --- stdout --- TAP version 13 # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d 1..4 # Start of fontsets tests ok 1 /fontsets/cantarell2 # Contents don't match expected contents # --- /tmp/.OQTQH2 2024-01-19 11:25:39.214546169 +0100 # +++ /tmp/.OSTQH2 2024-01-19 11:25:39.214546169 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 2 /fontsets/mono2 ok 3 /fontsets/cantarell # Contents don't match expected contents # --- /tmp/.X3URH2 2024-01-19 11:25:39.234546069 +0100 # +++ /tmp/.FJURH2 2024-01-19 11:25:39.234546069 +0100 # @@ -4,7 +4,7 @@ # DejaVu Sans 20 # Noto Sans CJK JP 20 # Droid Sans Japanese 20 # -Cantarell 20 # +Cantarell 20 @wght=400 # Amiri 20 # DejaVu Sans Bold 20 # Font Awesome 5 Free Solid Heavy 20 # not ok 4 /fontsets/mono # End of fontsets tests --- stderr --- (test program exited with status code 1) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: test-rebuild-glibc-noble ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2049881 Title: pango1.0: FTBFS against glibc 2.39 snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
** Also affects: lxqt-session (Ubuntu) Importance: Undecided Status: New ** Changed in: lxqt-session (Ubuntu) Status: New => In Progress ** Changed in: lxqt-session (Ubuntu) Importance: Undecided => High ** Changed in: lxqt-session (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
** Changed in: lubuntu-update-notifier (Ubuntu) Importance: Undecided => Medium ** Changed in: lubuntu-update-notifier (Ubuntu) Status: New => Confirmed ** Changed in: lubuntu-update-notifier (Ubuntu) Milestone: None => ubuntu-24.04-feature-freeze ** Changed in: lubuntu-update-notifier (Ubuntu) Assignee: (unassigned) => Aaron Rainbolt (arraybolt3) -- 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/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2030720] [NEW] Cannot reach login screen after firmware update and ubuntu update
Public bug reported: I recently had firmware upgraded on my dell laptop and have upgraded unbuntu to Ubuntu 22.04.3 LTS No matter what nvidia-driver options I try I cannot get to the login screen without purging nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-78.85-generic 5.15.99 Uname: Linux 5.15.0-78-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Aug 8 19:46:29 2023 DisplayManager: lightdm InstallationDate: Installed on 2019-03-16 (1605 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2023-08-07 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "prevboots.zip" https://bugs.launchpad.net/bugs/2030720/+attachment/5691016/+files/prevboots.zip -- 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/2030720 Title: Cannot reach login screen after firmware update and ubuntu update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2030720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006110] Re: [SRU] Update to latest bugfix release for jammy
> [flatpak search meld] produces 3,010 spurious identical error messages That's https://github.com/ximion/appstream/issues/384, which is a libappstream bug that cannot be fixed by a Flatpak change (as much as we might like to). I contributed a fix which was included in appstream 0.15.3, so this SRU would incorporate that fix. ** Bug watch added: github.com/ximion/appstream/issues #384 https://github.com/ximion/appstream/issues/384 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to latest bugfix release for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2018583] Re: evince does not store setting "Select page size using document page size"
** Description changed: + Version: 42.3-0ubuntu3 + evince does not store setting "Select page size using document page size". the setting is overwritten by the setting "Draw border around pages" fix: diff -r evince-42.3/libview/ev-print-operation.c evince-42.3-patched/libview/ev-print-operation.c 2778c2778 < gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_PAGE_SIZE, print->draw_borders); --- > gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_DRAW_BORDERS, print->draw_borders); -- 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/2018583 Title: evince does not store setting "Select page size using document page size" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2018583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2018583] [NEW] evince does not store setting "Select page size using document page size"
Public bug reported: evince does not store setting "Select page size using document page size". the setting is overwritten by the setting "Draw border around pages" fix: diff -r evince-42.3/libview/ev-print-operation.c evince-42.3-patched/libview/ev-print-operation.c 2778c2778 < gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_PAGE_SIZE, print->draw_borders); --- > gtk_print_settings_set_bool (settings, EV_PRINT_SETTING_DRAW_BORDERS, > print->draw_borders); ** Affects: evince (Ubuntu) Importance: Undecided Status: Confirmed ** Package changed: fontconfig (Ubuntu) => evince (Ubuntu) ** Changed in: evince (Ubuntu) Status: New => Confirmed -- 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/2018583 Title: evince does not store setting "Select page size using document page size" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2018583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006110] Re: [SRU] Update to latest bugfix release for jammy
** Also affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Package changed: flatpak (Ubuntu) => flatpak -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to latest bugfix release for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/flatpak/+bug/2006110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)
Please remember to mention the bug number in the changelog entry. Additionally, for stylistic purposes, I changed this: * Merge from Debian unstable. The remaining difference is the change for ignoring test results on i386 to avoir failure. To this: * Merge from Debian Unstable (LP: #2006633). Remaining changes: - Don't fail the build on tests error for i386 Otherwise, looks good to me, uploading. Please keep this in mind for a later upload. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/2006633 Title: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/2006633/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
Out of curiosity, would it work if you rename Vidéos into Videos? ** Also affects: glib2.0 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04
** Also affects: ubuntu-release-upgrader (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tracker-miners (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1983859 Title: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04
** Package changed: tracker (Ubuntu) => tracker-miners (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1983859 Title: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983859] [NEW] tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04
Public bug reported: When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. However, the crash occurs because of a unhandled SIGSYS, meaning a seccomp filter issue. I've tried backporting this patch fixing a similar issue: https://gitlab.gnome.org/GNOME/tracker- miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef but it doesn't apply, likely due to the code having diverged too much since. My proposal is thus to disable tracker-extract during upgrade, including in all user sessions. I'm assuming that the new version will be enabled automatically as its unit file changed name anyway. ** Affects: tracker (Ubuntu) Importance: High Status: Confirmed ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: High Status: Confirmed ** Tags: fr-2595 ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => High ** Tags added: fr-2595 -- 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/1983859 Title: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1983859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970131] Re: Can't rotate display with AMD graphics on 22.04 LTS
*** This bug is a duplicate of bug 1970473 *** https://bugs.launchpad.net/bugs/1970473 This bug is fixed by packages now released to jammy-updates (22.04LTS updates):- xserver-xorg-video-radeon 1:19.1.0-2ubuntu1 xserver-xorg-video-ati 1:19.1.0-2ubuntu1 Due to phasing these may not install immediately on any particular system. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970131 Title: Can't rotate display with AMD graphics on 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970131/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
@Dave @XA Okay. It worked for me though. Just hope it wasn't a temporary fix. -- 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/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
Run this command: sudo apt remove gstreamer1.0-vaapi Got my solution from this article, check it out too. https://www.makeuseof.com/things-to-do-after-upgrading-to-ubuntu-2204-lts/ -- 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/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966127] Re: ubuntu-desktop-minimal pulls gnome-session which is in universe
Thanks Jeremy! -- 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/1966127 Title: ubuntu-desktop-minimal pulls gnome-session which is in universe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966127/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1957181] Re: Screen freeze
Thank you for the reply. Indeed removing the dock worked. More precisely, I noticed that I had (accidentally) connected two mouses one via the dock and one wireless via a usb port (and the trackpad ofcourse). Taking one of the two mouses out of the equation solved the problem for me. No more crashes since. -- 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/1957181 Title: Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1957181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1957779] [NEW] Regression: GNOME-specific interfaces not available in main
Public bug reported: Historically, xdg-desktop-portal-gtk had two roles: * Generic GTK implementations of various interfaces, suitable for all GTK desktops (GNOME, XFCE, etc.) and also as a fallback implementation for desktops that do not have something more "native". Interfaces: Access, Account, AppChooser, Email, FileChooser, Inhibit, Lockdown, Notification, Print, Settings. * GNOME-specific implementations of various interfaces, suitable for GNOME Shell only (and mybe Budgie, but not XFCE, MATE or Cinnamon because they do not use gnome-settings-daemon or a libmutter-based compositor). Interfaces: Background, Remote Desktop, Screencast, Screenshot, Wallpaper. In 1.10.0-2, these roles were separated: * Generic GTK stuff is still in x-d-p-gtk * GNOME-specific functionality has moved to x-d-p-gnome, a separate source package, which is installed by the gnome-core metapackage in Debian In Ubuntu, x-d-p-gtk is in main but x-d-p-gnome is in universe (and presumably not installed by default). This means that users of Snap and Flatpak apps will not have access to the affected interfaces via xdg- desktop-portal any more, which is a regression, particularly if using native Wayland rather than X11. There are two possible solutions to this: 1. Move x-d-p-gnome to main, and install it by default (in any installation that has GNOME Shell). GNOME upstream consider it to be part of a complete GNOME desktop. This is the long-term solution. 2. Patch x-d-p-gtk to reinstate the build-dependencies that were disabled in 1.10.0-2, and re-enable them in d/rules. This provides an older version of these interfaces, which is no longer routinely tested by upstream or Debian. This solution will probably stop working in a future release when these interfaces are removed completely. I would recommend the first solution for Ubuntu 22.04 LTS. I am probably going to use the second solution in Debian bullseye- backports, and if Ubuntu people want to maintain a backport of x-d-p-gtk to older suites like focal, it's probably the right thing to do for those too. ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New -- 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/1957779 Title: Regression: GNOME-specific interfaces not available in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1957779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1928161] Re: Wacom Tablet Map Buttons blank on Wayland
this affects me as well. tablet : Bus 003 Device 004: ID 056a:00b5 Wacom Co., Ltd PTZ-631W [Intuos3 (6x11)] Linux desktop 5.11.0-41-generic #45-Ubuntu SMP Fri Nov 5 11:37:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux gjs 1.67.2 button configuration screen is basically the same as the one above. completely filling the screen and esc. does nothing. unplugging the wacom closes the screen. -- 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/1928161 Title: Wacom Tablet Map Buttons blank on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1928161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1940657] Re: Cannot type in address bar nor page content in live session
Oh yes sorry, I should have done that in the initial report. I'm using a Lenovo Yoga laptop model 710-IKB, with an AZERTY keyboard layout. It had no external input devices plugged in. A notable HW feature of the laptop is that it has a touchscreen. I'll give it a few more tries later today to see if I can reproduce. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1940657 Title: Cannot type in address bar nor page content in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940657/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1940657] Re: Cannot type in address bar nor page content in live session
This bug seems to be intermittent. I've now rebooted 5 or 6 times the system and I could only reproduce the issue on the first reboot. :/ -- 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/1940657 Title: Cannot type in address bar nor page content in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940657/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1940657] Re: Cannot type in address bar nor page content in live session
After further testing it's not a Firefox problem, other applications have the same issue. Weirdly, gnome-shell itself doesn't have the issue, hence my initial mistake. Gnome terminal, thunderbird, and Ubuntu software all have the same symptoms. Note that mouse input works fine. Reaffecting to gnome-shell as it seems to be a problem there? ** Package changed: firefox (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1940657 Title: Cannot type in address bar nor page content in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940657/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Ubuntu 20.04 still has this bug with mutter 3.36.7+git20201123-0.20.04.1 amd64 and nvidia-340. The workaround to set the wallpaper resolution to the screen resolution does work though! Thanx for that! -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
>This effects me also: > >ubuntu 20.04 >GeForce GTX 1050 Ti Mobile >4k monitor - usb-c port > >That work find in ubuntu 19.10 and same driver. Above my problem is solved with grub setting. nvidia_drm.modeset=1 Thanks everyone!! Now I'm using Ubuntu 20.10. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Thank you so much, it works for me too! I am very impressed that bugs are still being fixed for the powerpc version... > On 7 Jul 2020, at 16:13, Rod Rivers <1876...@bugs.launchpad.net> wrote: > > @Joe, I’m glad to hear that it works! FYI, Ubuntu rolls out updates slowly > starting with 10% of users, increasing 10% every 6 hours if there are no > problems. This may explain why it took some time before you saw the update. > Everyone should have been able to apply the updates on Sunday. Details are > here: > https://wiki.ubuntu.com/StableReleaseUpdates#Phasing > > As for other distro’s I think it is time someone else takes over. At > this point is should be more of an administrative process since the > problem has been pinpointed and patches were made for one distro. You > will probably have to file a bug report, point back to this bug and > follow their procedures. Worst case the patches may have to be updated > slightly to account for different line numbers. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1876286 > > Title: > Evolution reports "Error performing TLS handshake: Internal error in > memory allocation." > > Status in Gnutls: > Unknown > Status in claws-mail package in Ubuntu: > Invalid > Status in evolution package in Ubuntu: > Invalid > Status in gnutls28 package in Ubuntu: > Fix Released > Status in gnutls28 source package in Xenial: > Fix Released > Status in gnutls28 source package in Bionic: > Fix Released > Status in claws-mail source package in Focal: > Invalid > Status in evolution source package in Focal: > Invalid > Status in gnutls28 source package in Focal: > Fix Released > Status in claws-mail source package in Groovy: > Invalid > Status in evolution source package in Groovy: > Invalid > Status in gnutls28 source package in Groovy: > Fix Released > Status in gnutls28 package in CentOS: > Unknown > > Bug description: > [Impact] > > Evolution and Claws email clients stopped connecting to Yahoo, AOL, > Verizon, AT, Bell South, etc email servers which are run by the same > group. Users are unable to get to their email. > > The underlying problem is that GnuTLS does not support zero length > session tickets. The fix works by checking that that ticket_len > 0 > prior to calling gnutls_realloc_fast(). > > Nominating for SRU, fulfills: "Updates that need to be applied to > Ubuntu packages to adjust to changes in the environment, server > protocols, web services, and similar, i. e. where the current version > just ceases to work." > > > [testcase] > > GnuTLS 3.6: > $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 > [...] > - Status: The certificate is trusted. > *** Fatal error: Internal error in memory allocation. > > the error should be fixed with the update > > GnuTLS 3.5: > $ gnutls-cli pop.verizon.net:995 > > GnuTLS 3.4: > $ gnutls-cli -p 995 pop.verizon.net > > > [regression potential] > > The fix works by checking that that ticket_len > 0 prior to calling > gnutls_realloc_fast(). This creates two separate execution paths: > > 1) If the session ticket length > 0, which is the primary use case, > the original code block will be executed. > > 2) If the session ticket len is 0, then the original code block will > be skipped. > > Testing will need to include connections to servers that return > session ticket length > 0 as well as ones that return session ticket > length of 0. Wireshark can be used to look at the NewSessionTicket > handshake message to confirm the session ticket length. > > > [Other Info] > > The GnuTLS project's merge request 1260 fixes this bug. It was reviewed and > approved by Daiki Ueno: > https://gitlab.com/gnutls/gnutls/-/merge_requests/1260 > > According to the GnuTLS project: "We utilize two continuous integration > systems, the gitlab-ci and travis. Gitlab-CI is used to test most of the > Linux systems (see .gitlab-ci.yml), and is split in two phases, build image > creation and compilation/test. The build image creation is done at the > gnutls/build-images subproject and uploads the image at the gitlab.com > container registry. The compilation/test phase is on every commit to gnutls > project." > Here are the results of the gitlab-ci pipeline showing all 19 tests passed > for merge request 1260: > https://gitlab.com/rrivers2/gnutls/-/pipelines/149155018 > > Page 8, section 3.3 of RFC5077 describes the NewSessionTicket handshake > message and indicates that a zero length session ticket is a legitimate value: > https://tools.ietf.org/pdf/rfc5077.pdf > > -- > > When GnuTLS connects to servers that return zero length session > tickets using older TLS versions it returns the error code > GNUTLS_E_MEMORY_ERROR and the connection is closed. This prevents > Evolution and Claws email clients from connecting to Yahoo, AOL, > Verizon, AT,
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Is this issue going to be fixed in Ubuntu 16.04 powerpc as well as the other architectures? I hope so, its great news that the fix is working. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877731] Re: "Evolution will not display emails from Yahoo or AOL. It gives a "Memory allocation error." Other mailboxes work fine (hotmail, gmail, etc...)
** Also affects: gnutls28 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1877731 Title: "Evolution will not display emails from Yahoo or AOL. It gives a "Memory allocation error." Other mailboxes work fine (hotmail, gmail, etc...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877731/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Same for me, the problem started a few weeks ago in xenial powerpc. Maybe Yahoo and AOL updated their security settings and "found" the bug that had been sitting there all along. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I would say yes, as it prevents Gnome's default email client as well as Claws Mail from accessing Yahoo and AOL email accounts. If you have such an email account it is a problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877731] Re: "Evolution will not display emails from Yahoo or AOL. It gives a "Memory allocation error." Other mailboxes work fine (hotmail, gmail, etc...)
This same bug is affecting Evolution in Ubuntu 18.04 even the mainstream x86_64 distro. It sounds as if it is a problem with the GNUTLS package. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1877731 Title: "Evolution will not display emails from Yahoo or AOL. It gives a "Memory allocation error." Other mailboxes work fine (hotmail, gmail, etc...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877731/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877731] [NEW] "Evolution will not display emails from Yahoo or AOL. It gives a "Memory allocation error." Other mailboxes work fine (hotmail, gmail, etc...)
Public bug reported: Today, my Yahoo and AOL mailboxes wouldn't connect. Evolution displayed a "memory allocation error" I have searched and it looks like plenty of others have the same problem. When you fix this, please update the powerpc one too. Ubuntu 16.04 on powerpc 32bit Description:Ubuntu 16.04.6 LTS Release:16.04 evolution: Installed: 3.18.5.2-0ubuntu3.2 Candidate: 3.18.5.2-0ubuntu3.2 Version table: *** 3.18.5.2-0ubuntu3.2 500 500 http://gb.ports.ubuntu.com/ubuntu-ports xenial-updates/universe powerpc Packages 100 /var/lib/dpkg/status 3.18.5.2-0ubuntu1 500 500 http://gb.ports.ubuntu.com/ubuntu-ports xenial/universe powerpc Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-178.208-powerpc-smp 4.4.217 Uname: Linux 4.4.0-178-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2.23 Architecture: powerpc CurrentDesktop: XFCE Date: Sat May 9 11:11:07 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-17 (1026 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug powerpc xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1877731 Title: "Evolution will not display emails from Yahoo or AOL. It gives a "Memory allocation error." Other mailboxes work fine (hotmail, gmail, etc...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877731/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I am experiencing the same issue using Evolution 3.18.5.2 on Ubuntu 16.04 powerpc. My Yahoo and Aim accounts will not connect and I get the message "The reported error was "Error performing TLS handshake: Internal error in memory allocation." -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
This effects me also: ubuntu 20.04 GeForce GTX 1050 Ti Mobile 4k monitor - usb-c port That work find in ubuntu 19.10 and same driver. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726922] Re: gnome-calendar keeps asking for my google password
Deleting files in ~/.config is suboptimail in my case; I have very few applications installed and already have 122 objects in .config. It would be nice if someone [who knows] told us what variable we are to look for. that Google seems to be the culprit in virtually all cases here, and that the applicationdoes not report itself whrn invoking this obscurity measure, fails to amaze me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1726922 Title: gnome-calendar keeps asking for my google password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726922/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long
Oops, it should have been LOW, not LEGACY. Here it is again to avoid any confusion: As a workaround, can you try lowering the profile from MEDIUM [1] to LOW [2]: sudo mkdir /etc/gnutls cat << EOF | sudo tee -a /etc/gnutls/config [overrides] default-priority-string = NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LOW EOF 1: https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38 2: https://gnutls.org/manual/html_node/Selecting-cryptographic-key-sizes.html#Selecting-cryptographic-key-sizes -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 As a workaround, can you try lowering the profile from MEDIUM [1] to LOW [2]: sudo mkdir /etc/gnutls cat << EOF | sudo tee -a /etc/gnutls/config [overrides] default-priority-string = NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LOW EOF 1: https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38 2: https://gnutls.org/manual/html_node/Selecting-cryptographic-key-sizes.html#Selecting-cryptographic-key-sizes -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long
As a workaround, can you try lowering the profile from MEDIUM [1] to LEGACY: sudo mkdir /etc/gnutls cat << EOF | sudo tee -a /etc/gnutls/config [overrides] default-priority-string = NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LEGACY EOF 1: https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38 ** Changed in: gnutls28 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long
** This bug is no longer a duplicate of bug 1872778 update-crypto-policies not affecting Gnome Online Accounts -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863518] [NEW] Menuitems with actions cannot be set sensitive when in popup menus (using Glade/Python)
Public bug reported: The bug may be assigned to the wrong package: I'm using Glade 3.22.1 and Python 3.7.5. Using popup menus, if I assign Gio.Actions to the menuitems, the menuitems become insensitive, so you cannot click on them, even if they have a handler for the "activate" signal as well. I can assign Gio.Actions successfully to menuitems in a menubar, or a drop_down menu attached to a menubar, or to other clickable widgets such as buttons, so I think the logic works. The Glade xml output looks as if it is correctly specified (although I'm no expert), so I guess that Gtk.Builder is not connecting the signals properly. Or there might be a restriction that I'm not aware of... so apologies if I am trying to do something not supported, but I have tried to research this. Behaviour: menuitems in popup menus that have actions assigned are always insensitive and cannot be made sensitive. Expected behaviour: menuitems in popup menus that have actions assigned should be sensitive and activatable. I have attached the python and glade code which demonstrate the problem. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk-3-0 3.24.12-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 16 20:37:22 2020 SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to eoan on 2019-10-23 (115 days ago) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Python code to demonstrate the problem" https://bugs.launchpad.net/bugs/1863518/+attachment/5328752/+files/menuitem_action_bug.py -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1863518 Title: Menuitems with actions cannot be set sensitive when in popup menus (using Glade/Python) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1863518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10
I just spent the day researching this only to discover it's an ongoing bug which is several years old. I outline my results here: https://forum.level1techs.com/t/ubuntu-19-10 -gnome-shell-memory-leak/153376 To summarize that post, simply moving windows and toggling workspaces causes gnome-shell to jump from 200mb to 1.2G of ram use in a matter of minutes (several hours if I'm not intentionally trying to open apps and move windows around). This bug is affecting me on Ubuntu 19.10 running on an Aorus Master X570 with a 3950X and 64G of memory. The machine is only a few weeks old. It's a clean install. -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860036] [NEW] Samsung 85" TV worked for short time, now doesn't
Public bug reported: I installed Ubuntu 18.04 on a media PC connected to a samsung smart TV. this morning the TV was no longer displaying, and reporting that the resolution was not possible to display. I tinkered with the settings, and now the TV will not connect to the PC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 11:47:50 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'enable-animations' b'false' b'org.gnome.desktop.interface' b'gtk-theme' b"'Adwaita-dark'" InstallationDate: Installed on 2020-01-11 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1860036 Title: Samsung 85" TV worked for short time, now doesn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860036/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Created an account just to confirm I too am hit with this bug. Started as 19.04 running on Ryzen 2700X, 32G, RTX2060 with nVidia 430 drivers. After successfully upgrading from 19.04 to 19.10, or so I thought, I was met with the login screen upon system reboot. This was very strange as I had auto-login set to true with 19.04 so I should *not* be seeing this login screen. My linux-fu is weak as I'm currently transitioning from OS X to Linux and was completely lost on how to continue. The solution was to go scorched earth and do a clean install of 19.10. My /home directory is on a separate drive so I was confident things would work out ok. The clean install went well but at this point I was still unaware that the issue was related to the auto-login (and perhaps nvidia 435 combo). So after modding my fstab and rebooting I was confronted again with the login screen and not being able to login (ie, no matter how many times I typed my password the login screen would ignore me). After some Googling I discovered this page you are reading now. I did another clean install but this time I mv'd .config and .local in my /home directory to borked.config and borked.local (as mentioned, my linux-fu is weak but I assumed that my previous auto-login setting is stored in a pref file *somewhere* in either of those directories). After updating fstab I then toggled the auto-login a few times to ensure the prefs would show it clearly in the OFF position. Then I rebooted. SUCCESS. The login screen appeared but this time I *was* able to login — I spent another hour moving files from my *borks* back to .config and .local and I'm mostly back to normal. As mentioned by anidotnet above, this is my second update (18.04 > 18.10 && 19.04 > 19.10) and both were extremely unpleasant with this latest update taking the cake. -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Hello, thanks for your reply. I have tested that kernel and I did not notice any such problem! -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Thanks & sorry for belated response. I've never manually installed a new kernel (and am not sure how to proceed about checking integrity, etc.). Is there any resource you'd advice to get info on the topic? Thanks in advance. For now I can confirm that since I added this to the kernel options, I have had 0 occurrences of the bug over the last 3 weeks. -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838890] [NEW] Suspected memory leak in xenial backport of fix for CVE-2019-13012
Public bug reported: (This is only from source code inspection, not tested in real use - I don't actually use Ubuntu.) The upstream fix for CVE-2019-13012 included this change: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700); However, g_file_peek_path() was only introduced in GLib 2.56. The backport in the xenial package has this instead: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700); This is not equivalent. The difference between g_file_peek_path() and the older g_file_get_path() is that g_file_get_path() makes a copy, which must be freed with g_free() after use. As a result, there is now a memory leak. A non-leaky backport would look something like this, which is what I've done in a proposed backport for Debian 9 'stretch': + char *dir; ... - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + dir = g_file_get_path (kfsb->dir); + g_mkdir_with_parents (dir, 0700); + g_free (dir); ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1838890 Title: Suspected memory leak in xenial backport of fix for CVE-2019-13012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1838890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
So it seems that it does away with the following kernel option: i915.enable_psr=0 It seems from some Dell user forum that some have had the same issues on Windows and disabling the panel self refresh worked for them so I was searching along these lines. I'm certain it's not a "clean" fix however to deactivate a measure that's suppose to save battery. -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
I have also been trying to see what are the packages difference between the OEM version and 19.04 since I suspect that Dell might have addressed this issue in their version. I have a list of all packages that were on the OEM but that might be tedious. If we contacted Dell directly, would they be able to help narrow it down / provide packages that they set up on the OEM? -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Hello all, I believe that I have this same bug, also after a 19.04 fresh install. I initially posted on that bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125 but they kindly directed me here. Of note, I am glad you tried wayland as I wanted to try if that made any difference. I have tried passing different kernel parameters (though not all combinations) namely: First try: i915.edp_vswing=2 Second try: i915.fastboot=1 i915.edp_vswing=1 i915.preliminary_hw_support=1 intel_idle.max_cstate=1 acpi_backlight=vendor acpi.osi=Linux (see https://www.reddit.com/r/linuxquestions/comments/ayi4n6/flickering_on_laptops_with_a_4k_screen_and_intel/) but that did not seem to make any difference apart from disabling the backlight controls It somewhat feels good to have that identified as a bug. -- 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/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834211] Re: [SRU] gconf FTBFS in Bionic
Before this is sponsored, I would like to see Brian's comment on the other bug addressed; does this need to go to Eoan, any other releases, or Debian? Thanks, and please resubscribe sponsors when this is answered. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1834784] Re: Xorg freeze
Hi. Everything freezes. The clock on my screen shows the seconds. which has also frozen. Pressing ctrl-alt-f2 etc, to get to a login prompt doesn't work. Only a hard reset can clear it. I have installed the amdgpu pro drivers, supplied by AMD, and will see if that helps resolve the issue. On Mon, Jul 1, 2019 at 4:15 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > When the problem happens does the mouse pointer freeze too? > > Only if the mouse pointer freezes is it the Xorg process that's frozen. > > ** Tags added: amdgpu > > ** Summary changed: > > - Xorg freeze > + [amdgpu[ Xorg freeze > > ** Summary changed: > > - [amdgpu[ Xorg freeze > + [amdgpu] Xorg freeze > > ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) > > ** Also affects: xorg-server (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) >Status: New => Incomplete > > ** Also affects: mutter (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1834784 > > Title: > [amdgpu] Xorg freeze > > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > Status in xserver-xorg-video-amdgpu package in Ubuntu: > Incomplete > > Bug description: > I can't provide much in the way of detail as the freezes are seemingly > random. They happen with different software being used. > > Release: Ubuntu 18.04.2 LTS > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 > Uname: Linux 4.18.0-25-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 30 17:40:47 2019 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: I just need to know a workaround > GpuHangFrequency: Several times a day > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Immediately after installing this version of Ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX > 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA > controller]) > Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 580 4GB > [1da2:e366] > InstallationDate: Installed on 2019-06-30 (0 days ago) > InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 > (20190210) > MachineType: System manufacturer System Product Name > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic > root=UUID=71fe103c-b7c8-4fbd-970d-39d7569306ab ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/19/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 4011 > dmi.board.asset.tag: Default string > dmi.board.name: PRIME X370-PRO > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.95-1~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1834784/+subscriptions > -- 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/1834784 Title: [amdgpu] Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1834784/+subscriptions
[Bug 1832330] [NEW] gnome archive manager: "show the files" -> "Close and show the files"
Public bug reported: this is about the application Archive manager (I do not like generic names btw. makes searching a pita) in gnome 3 as used by Ubuntu 18.04 If I open an archive and extract the contents, I get a window with two options: close and show the files. I always want to press both buttons at the same time as I am finished with the archive and want to continue with the extracted files. there is no need to keep the archive manager window open. Hence my request for a change of the button "show the files" to a "close and show the files" uname -a: Linux compaq 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu 18.04.2 LTS, Gnome 3.28.2 ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1832330 Title: gnome archive manager: "show the files" -> "Close and show the files" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1832330/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1786881] Re: Languages always shown with English names
Unsubscribing the sponsors team because there is nothing to sponsor. -- 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/1786881 Title: Languages always shown with English names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1786881/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820428] Re: gnome-logs cannot open display: :0
** Description changed: ** Changed in: gnome-logs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-logs in Ubuntu. https://bugs.launchpad.net/bugs/1820428 Title: gnome-logs cannot open display: :0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-logs/+bug/1820428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820428] [NEW] gnome-logs cannot open display: :0
Public bug reported: simon@pc ~> gnome-logs (gnome-logs:16346): Gtk-WARNING **: 23:28:19.106: cannot open display: :0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-logs (not installed) ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 23:32:08 2019 InstallationDate: Installed on 2019-03-13 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gnome-logs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-logs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-logs in Ubuntu. https://bugs.launchpad.net/bugs/1820428 Title: gnome-logs cannot open display: :0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-logs/+bug/1820428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815480] Re: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
Is there anything specific I should do? Just extracting the file in Nautilus doesn’t generate any entries in journalctl. -- 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/1815480 Title: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1815480/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815480] [NEW] “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
Public bug reported: For any .zip archive generated by the ownCloud software, it seems that extracting the files using Nautilus results in correctly-named directories/files to be created, but all files are actually empty (0 bytes). The archive can be extracted without issues using file-roller, unzip or 7z: $ unzip -t test.zip Archive: test.zip testing: test/OK testing: test/f1.txt OK testing: test/f2.txt OK testing: test/f3.txt OK No errors detected in compressed data of test.zip. $ unzip test Archive: test.zip creating: test/ extracting: test/f1.txt extracting: test/f2.txt extracting: test/f3.txt $ 7z x test.zip 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (306D4),ASM,AES-NI) Scanning the drive for archives: 1 file, 8656 bytes (9 KiB) Extracting archive: test.zip -- Path = test.zip Type = zip Physical Size = 8656 64-bit = + Everything is Ok Folders: 1 Files: 3 Size: 7850 Compressed: 8656 Expected behavior: Download the attached file “test.zip”, right-click the file in Nautilus and choose “Extract Here”. A directory “test” containing three non-empty files “f1.txt”, “f2.txt” and “f3.txt” should be created. Actual behavior: All three files are empty (0 bytes). Nautilus version: 1:3.26.4-0ubuntu7.1 (cosmic) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ** Attachment added: "Example .zip archive which exhibits the problem" https://bugs.launchpad.net/bugs/1815480/+attachment/5237721/+files/test.zip -- 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/1815480 Title: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1815480/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 156201] Re: gedit handles opening big files badly
“Unfortunately nano doesn't have syntax highlighting.” nano does have syntax highlighting! https://wiki.archlinux.org/index.php/nano#Syntax_highlighting -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/156201 Title: gedit handles opening big files badly To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/156201/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I can also confirm that this issue still occurs even with the version in -proposed. The only difference I’ve noticed with the new version is that the text on the keyboard layout indicator sometimes disappears. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
It is quite concerning to see how long it takes to fix security- sensitive bugs like this in Ubuntu. Anyways, what I wanted to add: To kind of make it worse, after the bug happens and after logging in, the dock is not working properly any more - when new programs are started that were not on the launcher before, the according symbol is not displayed in the launcher. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793322] Re: “Domain” field missing when editing WPA2 Enterprise connection
Reported at https://gitlab.gnome.org/GNOME/gnome-control- center/issues/325 -- 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/1793322 Title: “Domain” field missing when editing WPA2 Enterprise connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1793322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1808576] [NEW] gnome-control-center segfaults when unit bolt.service is masked
Public bug reported: I don't have any Thunderbolt devices so I masked the unused the bolt.service. This causes problem with gnome-control-center. Steps to reproduce: 1) launch gnome-control-center $ gnome-control-center 2) navigate to Thunderbolt section go to Devices, then Thunderbolt and close gnome-control-center 3) mask bold.service $ sudo systemctl stop bolt.service $ sudo systemctl mask bolt.service 4) re-launch gnome-control-center $ gnome-control-center (gnome-control-center:21859): thunderbolt-cc-panel-WARNING **: 14:04:53.423: Could not create client: Error calling StartServiceByName for org.freedesktop.bolt: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit bolt.service is masked. Segmentation fault (core dumped) Expected result: no segfault. Additional information: $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy gnome-control-center bolt gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages bolt: Installed: 0.5-0ubuntu0.18.04.1 Candidate: 0.5-0ubuntu0.18.04.1 Version table: *** 0.5-0ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 14 14:05:26 2018 InstallationDate: Installed on 2018-07-15 (152 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: LANG=en_CA.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) 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 third-party-packages -- 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/1808576 Title: gnome-control-center segfaults when unit bolt.service is masked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1808576/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1400470] Re: cannot download photos using shotwell via usb
Bug still occurring with Shotwell 0.30.1 under Ubuntu 18.10 when trying to access pictures on my Sony Xperia X phone. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1400470 Title: cannot download photos using shotwell via usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1400470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
No, still there. Lockscreen worked flawless for the last couple of locks, but I just ran into the same bug again. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Seems it was fixed with the last update. At least for me. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800179] [NEW] Search in recent files list only works with lowercase letters
Public bug reported: When clicking “Open” and typing to search the recently opened files, any search involving uppercase letters fails to return any result, even if files with uppercase letters in their file names have recently been opened. Searching for the same file names, but using all-lowercase letters, does yield results (see attached screenshot). So it seems that gedit converts the recently used file names to lowercase before comparing to the search term, which is incorrect. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ** Attachment added: "screenshot of the problematic behavior" https://bugs.launchpad.net/bugs/1800179/+attachment/5205885/+files/gedit_recent_search.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1800179 Title: Search in recent files list only works with lowercase letters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1800179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I am experiencing this issue too since the upgrade to 18.10. Sometimes in addition to the launcher I can even see an open program! Cannot use the program interface though before going to the unlock screen by pressing super + l and unlocking the system. I have gnome-tweaks installed, used it only to activate the Yaru theme which was not working after the upgrade (bug 1798984). So I guess that doesn't qualify as play with it. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
I can confirm this - except the freezing/non-responding on a fresh Ubuntu Installation. I installed with 18.04 and upgraded to 18.10 afterwards. The default dock (no dock extension in use) is visible and fully functional at the lock-screen. The problem occurs not always, but - estimated - at over 50% of all lock-screens. Full functional dock, e.g.: - Execution of the Favorites/applications is possible - Pre-view of application windows is possible -- 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/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1799430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799052] Re: Application/task bar on left side is visible and operable after screen lock
I can confirm that bug since the upgrade to 18.10. Sometimes also the field to enter the password is missing on the lock screen (see attached picture). ** Attachment added: "DSC_0882.JPG" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1799052/+attachment/5204309/+files/DSC_0882.JPG -- 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/1799052 Title: Application/task bar on left side is visible and operable after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1799052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793322] [NEW] “Domain” field missing when editing WPA2 Enterprise connection
Public bug reported: Ubuntu release: 18.04.1 LTS Package version: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 When *adding* a WPA2 Enterprise connection, the dialog that appears is very similar to the “Security” tab when *editing* the connection (see the attached screenshot). However, one field from the “create connection” dialog is conspicuously missing from the “edit connection” dialog: the “Domain:” field! (Marked in red in the screenshot.) In other words, it is not possible to change the domain for a WPA2 Enterprise connection after creating it. The field should be present in both dialogs. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "screenshot illustrating the problem" https://bugs.launchpad.net/bugs/1793322/+attachment/5190538/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1793322 Title: “Domain” field missing when editing WPA2 Enterprise connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1793322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)
I can confirm that I have tried this tonight on 18.04.1 LTS with a Portuguese layout Apple wired keyboard, and iso_layout=0 doesn't fix the problem for me either -- 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/1043336 Title: Swiss keyboard layout with Apple keyboard (period instead of comma) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)
Correction - it did fix it after a reboot. -- 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/1043336 Title: Swiss keyboard layout with Apple keyboard (period instead of comma) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787325] Re: Update wayland-protocols to version 1.16
Unsubscribing ~ubuntu-sponsors because there's nothing to sponsor. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to wayland-protocols in Ubuntu. https://bugs.launchpad.net/bugs/1787325 Title: Update wayland-protocols to version 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland-protocols/+bug/1787325/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1744941] Re: gnome-software crashes in as_app_parse_desktop_file
Unsubscribing sponsors as there's nothing left to sponsor. Artful is also EOL. Ping, Iain and Robie. ** Changed in: appstream-glib (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1744941 Title: gnome-software crashes in as_app_parse_desktop_file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1744941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
Artful is EOL. ** Changed in: gtk+3.0 (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1714518 Title: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1714518/+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
I can confirm that I am experiencing the same bug again since the vlc update to 3.0.3 -- 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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
** This bug is no longer a duplicate of private bug 1710637 -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768258] Re: Intermittend black screen - after login on bootup
Seems this bug was fixed. At least I cannot reproduce it any more since the recent updates. -- 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/1768258 Title: Intermittend black screen - after login on bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779526] Re: Please merge 2.24.32-2 from Debian Sid
https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.32-2ubuntu1 ** Changed in: gtk+2.0 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1779526 Title: Please merge 2.24.32-2 from Debian Sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1779526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779526] [NEW] Please merge 2.24.32-2 from Debian Sid
Public bug reported: 2.24.32-2 has been uploaded to Debian Sid fixing a few bugs. Let's merge it. ** Affects: gtk+2.0 (Ubuntu) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1779526 Title: Please merge 2.24.32-2 from Debian Sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1779526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772919] Re: pam-gnome-keyring.so reveals user’s password credential as a plaintext form
Setting to new because they submitted it upstream. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1772919 Title: pam-gnome-keyring.so reveals user’s password credential as a plaintext form To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1772919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772919] Re: pam-gnome-keyring.so reveals user’s password credential as a plaintext form
Setting to new because he submitted it upstream. ** Changed in: gnome-keyring (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1772919 Title: pam-gnome-keyring.so reveals user’s password credential as a plaintext form To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1772919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Oh wow this was driving me nuts - and indeed the "workspaces-to-dock" extension caused it like in comment #48 - thanks! -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770135] Re: Rhythmbox initially crashes when trying to play a song
The bug seems to be related to the alternative toolbar once again. When disabling the alternative toolbar, Rhythmbox works stable without those crashes. ** Also affects: alternative-toolbar Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1770135 Title: Rhythmbox initially crashes when trying to play a song To manage notifications about this bug go to: https://bugs.launchpad.net/alternative-toolbar/+bug/1770135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770135] [NEW] Rhythmbox initially crashes when trying to play a song
Public bug reported: With Ubuntu 18.04 and Rhythmbox 3.4.2 I have the following problem: Rhythmbox initially crashes when I try to play a song. When I open it again it plays the song as expected without crashing. How to reproduce the bug: 1) Open rhythmbox. 2) Search for a song. Doublecklick it to play it. --> Rhythmbox will crash. Open rhythmbox again, it works without crashing now. 3) Close rhythmbox with the Ctrl + Q command. Start over at 1), bug appears again. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1770135 Title: Rhythmbox initially crashes when trying to play a song To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1770135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768258] Re: Intermittend black screen - after login on bootup
I am experiencing the same problem with 18.04. After a failed login attempt and the subsequent login, the green stays black and only the mouse cursor is shown. -- 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/1768258 Title: Intermittend black screen - after login on bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
