[Bug 1847551] [NEW] Mutter 3.34.1 broke Night Light, screen color profiles
Public bug reported: Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #851 https://gitlab.gnome.org/GNOME/mutter/issues/851 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/851 Importance: Unknown Status: Unknown -- 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/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844445] Re: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown()
** Information type changed from Private to Public -- 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/185 Title: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
This is fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/792 (I tested 850ef518795dcc20d3b9a4f661f70ff8d0ddacb2). -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #771 https://gitlab.gnome.org/GNOME/mutter/issues/771 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/771 Importance: Unknown Status: Unknown -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
By adding some debugging output to mutter and gnome-shell I verified that mutter emits the x11-display-opened signal before gnome-shell is able to connect a handler for it, and the handler never runs. (Possibly things would be different in the experimental autostart- xwayland mode, but the whole system froze when I tried to log in with that enabled.) -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
Hmm, I upgraded mutter from eoan-proposed and gnome-shell from eoan-
proposed plus those three commits
(https://launchpad.net/~andersk/+archive/ubuntu/ppa, if you want to
check my work), but it didn’t resolve the problem. Even after a reboot,
gsd-xsettings doesn’t start and X11 applications don’t get themed.
$ dpkg-query -W gir1.2-mutter-5 libmutter-5-0 mutter mutter-common gnome-shell
gnome-shell-common
gir1.2-mutter-5:amd64 3.33.92-1ubuntu1
gnome-shell 3.33.92-1ubuntu1andersk1
gnome-shell-common 3.33.92-1ubuntu1andersk1
libmutter-5-0:amd64 3.33.92-1ubuntu1
mutter 3.33.92-1ubuntu1
mutter-common 3.33.92-1ubuntu1
$ strings /usr/lib/gnome-shell/libgnome-shell.so | grep x11-display
global.display.connect('x11-display-opened', () => {
global.display.connect('x11-display-closing', () => {
$ systemctl --user status gnome-session-x11-services.target
gsd-xsettings.target gsd-xsettings.service
● gnome-session-x11-services.target - GNOME session X11 services
Loaded: loaded (/usr/lib/systemd/user/gnome-session-x11-services.target;
static; vendor preset: enabled)
Active: inactive (dead)
● gsd-xsettings.target - GNOME XSettings
Loaded: loaded (/usr/lib/systemd/user/gsd-xsettings.target; static; vendor
preset: enabled)
Active: inactive (dead)
● gsd-xsettings.service - GNOME XSettings
Loaded: loaded (/usr/lib/systemd/user/gsd-xsettings.service; static; vendor
preset: enabled)
Active: inactive (dead)
--
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/1843107
Title:
Themes and font settings don’t apply to X apps running in Wayland
(g-s-d 3.33.90 → 3.33.92 regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1843107/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843107] [NEW] Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)
Public bug reported: After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to 3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome- tweaks are no longer applied to X11 applications when running in a Wayland session (I tried Firefox and Emacs). This seems to be because gsd-xsettings is not running. Known workarounds: • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or • use Xorg instead of Wayland; or • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-settings-daemon 3.33.92-1ubuntu1 Uname: Linux 5.2.11-050211-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 6 17:24:02 2019 InstallationDate: Installed on 2016-02-19 (1295 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1843107 Title: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1843107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
The situation with apache2 is what I documented in https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9: “But since we’re apparently gathering information here: although Apache 2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of r1773454. (As you can see, this support was added by creating separate conditionally compiled code paths for PCRE and PCRE2.) https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570” trunk is the 2.5.x branch, not 2.4.x. -- 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/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"
I hope 3.32.1 will get into Disco, but in case this can’t happen and a more minimal set of patches is required, these are the nine upstream patches I added to my mutter package to get it to stop crashing on wakeup: fe86694dd renderer/native: Make EGLStream page flip errors non-fatal 1eabaf12d renderer/native: Make the EGLStreams operate in mailbox mode 4cae9b5b1 monitor-manager: Clean up DPMS state tracking 40e7e5d35 renderer-native: Fix page flip retry timeout calculation 53b59d8bf renderer-native: Fake page flipped if power saving when retrying 3cc3b7526 renderer-native: Fake page flipping slower when power saving 88e4ff740 backend: Add API to freeze/thaw frame clock 808a75b23 renderer-native: Add helper to get backend from renderer b2d0184c6 renderer-native: Freeze frames while retrying to page flip Note that they were accepted into master nonconsecutively, with other commits between 1eabaf12d and 4cae9b5b1. -- 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/1820331 Title: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820331] Re: gnome-shell crashed with SIGABRT
** Information type changed from Private to Public -- 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/1820331 Title: gnome-shell crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795556] Re: mutter 3.30.0-4 FTBFS
As long as you're working on this package would you mind including the one-line upstream patch for bug 1788483, if you haven't already? -- 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/1795556 Title: mutter 3.30.0-4 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795556] Re: mutter 3.30.0-4 FTBFS
That was a local build. I also saw it on Launchpad with an unrelated patch (bug 1788483): https://launchpadlibrarian.net/391298478/buildlog_ubuntu- cosmic-i386.mutter_3.30.0-4andersk1_BUILDING.txt.gz However, the failure seems to have disappeared with today’s updates of other packages, or maybe the tests are just flaky. I’ll reopen this if I see the failure again. ** Changed in: mutter (Ubuntu) Status: New => Invalid -- 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/1795556 Title: mutter 3.30.0-4 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal()
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Tags added: patch-accepted-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/1788483
Title:
gnome-shell crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (trap->end_sequence ==
0)") from gdk_x11_display_error_trap_pop_internal() from
meta_input_settings_x11_set_tablet_keep_aspect()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795556] [NEW] mutter 3.30.0-4 FTBFS
Public bug reported: mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1). A full build log is attached. The relevant part is these test failures. == clutter 1.26.1: tests/conform/test-suite.log == # TOTAL: 83 # PASS: 81 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 2 .. contents:: :depth: 2 ERROR: actor-offscreen-redirect === # random seed: R02Sb2875ff7949f70873efba32072c693a6 1..1 # Start of actor tests ** Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2) # Start of offscreen tests Aborted (core dumped) Bail out! Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2) ERROR: actor-offscreen-redirect - Bail out! Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2) ERROR: actor-shader-effect == # random seed: R02S35d2b55cc4cd821aa7b19454f0028a03 1..1 ** Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed (get_pixel (50, 50) == 0xff): (0 == 16711680) # Start of actor tests Aborted (core dumped) Bail out! Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed (get_pixel (50, 50) == 0xff): (0 == 16711680) ERROR: actor-shader-effect - Bail out! Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed (get_pixel (50, 50) == 0xff): (0 == 16711680) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ** Attachment added: "mutter_3.30.0-4_amd64.build" https://bugs.launchpad.net/bugs/1795556/+attachment/5195672/+files/mutter_3.30.0-4_amd64.build -- 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/1795556 Title: mutter 3.30.0-4 FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal()
(Is it really correct to mark this as “In Progress” and assigned to me
when there’s nothing else I can do to move this forward except wait for
a sponsor to pay attention?)
** Patch added: "debdiff adding upstream patch, rebased"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1788483/+attachment/5195604/+files/mutter_3.30.0-4_lp1788483.debdiff
--
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/1788483
Title:
gnome-shell crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (trap->end_sequence ==
0)") from gdk_x11_display_error_trap_pop_internal() from
meta_input_settings_x11_set_tablet_keep_aspect()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_trap_pop_internal()
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+attachment/5195090/+files/mutter_3.30.0-1_lp1788483.debdiff
--
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/1788483
Title:
gnome-shell crashed with SIGABRT in g_assertion_message() from
g_assertion_message_expr("assertion failed: (trap->end_sequence ==
0)") from gdk_x11_display_error_trap_pop_internal() from
meta_input_settings_x11_set_tablet_keep_aspect()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Likewise, nginx does not support PCRE2: https://trac.nginx.org/nginx/ticket/720 ** Bug watch added: trac.nginx.org/nginx/ #720 http://trac.nginx.org/nginx/ticket/720 ** Changed in: nginx (Ubuntu) Status: Triaged => Incomplete -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
I think that completes the analysis of the current state of things. Although it seems infeasible to demote PCRE at this time, there’s no reason that should block the promotion of PCRE2, especially seeing as a bundled copy of PCRE2 is already in main (18.04 and 18.10) via libqt5core5a. ** Changed in: sssd (Ubuntu) Status: Confirmed => Incomplete -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Note to those filing upstream bugs: probably don’t call the old library “pcre3” since that’s not a thing outside Debian/Ubuntu. -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• Quagga: no PCRE2 support • Rasqal: no PCRE2 support • S-Lang: no PCRE2 support ** Changed in: quagga (Ubuntu) Status: New => Incomplete ** Changed in: rasqal (Ubuntu) Status: New => Incomplete ** Changed in: slang2 (Ubuntu) Status: New => Incomplete -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• pam_mount: no PCRE2 support • nmap: no PCRE2 support • postfix: no PCRE2 support, http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html • pyScss: no PCRE2 support ** Changed in: libpam-mount (Ubuntu) Status: New => Incomplete ** Changed in: nmap (Ubuntu) Status: New => Incomplete ** Changed in: postfix (Ubuntu) Status: New => Incomplete ** Changed in: python-pyscss (Ubuntu) Status: New => Incomplete -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
• Aide: no PCRE2 support • Exim: no PCRE2 support, upstream bug: https://bugs.exim.org/show_bug.cgi?id=1878 • FreeRADIUS: no PCRE2 support, mentioned in passing: https://github.com/FreeRADIUS/freeradius-server/issues/1865 • GLib: no PCRE2 support • grep: no PCRE2 support ** Bug watch added: bugs.exim.org/ #1878 http://bugs.exim.org/show_bug.cgi?id=1878 ** Bug watch added: github.com/FreeRADIUS/freeradius-server/issues #1865 https://github.com/FreeRADIUS/freeradius-server/issues/1865 ** Changed in: aide (Ubuntu) Status: New => Incomplete ** Changed in: exim4 (Ubuntu) Status: New => Incomplete ** Changed in: freeradius (Ubuntu) Status: New => Incomplete ** Changed in: glib2.0 (Ubuntu) Status: New => Incomplete ** Changed in: grep (Ubuntu) Status: New => Incomplete -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Copying from https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20, HAProxy and SELinux upstream support PCRE2. https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b https://github.com/SELinuxProject/selinux/commit/50f0910cf05bdc1d10710c7c3fb748a178473387 -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
apr-util has a false Build-Depends on libpcre3-dev; it should simply be dropped. A corresponding Depends was already dropped in https://bugs.debian.org/757140. -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Andreas: No, it’s not a bug. PCRE2 is a new project that’s not intended to be compatible with the older PCRE (i.e. what Debian misnamed “pcre3”). The API is completely different and this is expected. See bug 163 for context, and specifically the PCRE2 release announcement linked in the bug description: https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html That’s why getting rid of PCRE “in favor of” PCRE2 is a pointless way to frame the issue. PCRE2 neither replaces nor conflicts with PCRE, as was pointed out many times in bug 163. But since we’re apparently gathering information here: although Apache 2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of r1773454. (As you can see, this support was added by creating separate conditionally compiled code paths for PCRE and PCRE2.) https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570 ** Bug watch added: Debian Bug tracker #757140 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757140 -- 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/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790992] Re: gnome-shell crashes with SIGABRT when touching stylus to screen, "assertion failed: (trap->end_sequence == 0)" in in gdk_x11_display_error_trap_pop_internal() from gdk_x11_display_er
GNOME on Wayland works around the crash. Based on the apport-retrace results, this is possibly a duplicate of bug 1788483. -- 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/1790992 Title: gnome-shell crashes with SIGABRT when touching stylus to screen, "assertion failed: (trap->end_sequence == 0)" in in gdk_x11_display_error_trap_pop_internal() from gdk_x11_display_error_trap_pop() from meta_x11_error_trap_pop_with_return() from meta_input_settings_x11_set_stylus_button_map() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1701289] Re: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat()
This may have been fixed by mutter 3.26.1-2 (bug 1722510). At least I can no longer reproduce it using the recipe in my duplicate bug 1722709. -- 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/1701289 Title: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1701289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722687] [NEW] ‘env GTK_IM_MODULE=uim gedit’ crashes with SIGSEGV in Wayland
Public bug reported: Running ‘env GTK_IM_MODULE=uim gedit’ in a Wayland session results in this crash. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 10 20:50:10 2017 Disassembly: => 0x2:Cannot access memory at address 0x2 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2016-02-19 (599 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: gedit ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x2: Cannot access memory at address 0x2 PC (0x0002) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: () XGetModifierMapping () at /usr/lib/x86_64-linux-gnu/libX11.so.6 im_uim_init_modifier_keys () at /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so im_module_init () at /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gedit crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-05-02 (161 days ago) UserGroups: ** Affects: gedit (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash artful ** Information type changed from Private to Public -- 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/1722687 Title: ‘env GTK_IM_MODULE=uim gedit’ crashes with SIGSEGV in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1722687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721681] Re: gnome-terminal-server crashed with SIGSEGV in XGetModifierMapping()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1721681 Title: gnome-terminal-server crashed with SIGSEGV in XGetModifierMapping() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1721681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
I’m not sure. Since it’s been a week without any sign of an upload to artful-proposed, I’m changing this back to Confirmed. I have a patched build of gnome-shell in my PPA if you need it now: https://launchpad.net/~andersk/+archive/ubuntu/ppa/+packages https://launchpadlibrarian.net/339202115/gnome-shell_3.26.0-0ubuntu2_3.26.0-0ubuntu2andersk1.diff.gz ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Confirmed ** Tags removed: wayland-session ** Tags added: patch patch-accepted-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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
It seems to be the TopIcons Plus extension that triggers this so often. I think that’s roughly consistent with the upstream bug report. -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
This might be triggered by a shell extension. I haven’t seen any crashes after turning them all off. I’ll see if I can bisect which one it is. -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
This is happening to me very frequently (several times a day) on both Wayland and Xorg. On Wayland, it brings down the entire session. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
** Information type changed from Private to Public -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714745/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default
** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658 Importance: Unknown Status: Unknown ** Changed in: systemd Importance: Unknown => Undecided ** Changed in: systemd Status: Fix Released => New ** Changed in: systemd Remote watch: Debian Bug tracker #761658 => None -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1449001 Title: systemd-resolved: please do not use Google public DNS by default To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1449001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1676115] [NEW] systemd-resolved spams the system log with useless “Processing query...” messages
Public bug reported: If you are running ‘journalctl -f’ to try to debug some other problem, you are constantly interrupted by zillions of these messages from systemd-resolved: Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query... This was fixed upstream in v233 by downgrading this message from log_info to log_debug: https://github.com/systemd/systemd/pull/5233 ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #5233 https://github.com/systemd/systemd/issues/5233 ** Also affects: systemd via https://github.com/systemd/systemd/issues/5233 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676115 Title: systemd-resolved spams the system log with useless “Processing query...” messages To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1676115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 897302] Re: Screen dims even automatic dimming is turned OFF (when on battery)
** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=665073 Importance: Unknown Status: Unknown -- 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/897302 Title: Screen dims even automatic dimming is turned OFF (when on battery) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/897302/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1649370] [NEW] libnss-{resolve,myhostname} don’t install correctly if previously removed without being purged
Public bug reported:
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname resolve [!UNAVAIL=return] dns
# apt remove libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
# apt install libnss-resolve
# grep hosts /etc/nsswitch.conf
hosts: files myhostname dns
libnss-resolve.postinst and libnss-myhostname.postinst only update
/etc/nsswitch.conf if [ "$1" = configure ] && [ -z "$2" ]. If the
package was previously removed but not purged (it is in the Config-Files
state), dpkg passes the previous version as $2, so this fails.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: zesty
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1649370
Title:
libnss-{resolve,myhostname} don’t install correctly if previously
removed without being purged
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649370/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1647031] [NEW] systemd-resolved’s 127.0.0.53 server does not follow CNAME records
Public bug reported:
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org. IN A
www.freedesktop.org.7146IN CNAME annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org. IN A
www.freedesktop.org.14399 IN CNAME annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN A 131.252.210.176
I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.
** Affects: systemd
Importance: Unknown
Status: Unknown
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #3826
https://github.com/systemd/systemd/issues/3826
** Also affects: systemd via
https://github.com/systemd/systemd/issues/3826
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1628778] [NEW] systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving
Public bug reported: On the MIT network (which runs some ancient version of BIND 9), systemd- resolved stops resolving anything that isn’t DNSSEC-signed after I disconnect and reconnect the network. Signed zones continue to resolve. This happens with either DNSSEC=yes or the default DNSSEC=allow- downgrade. $ systemd-resolve github.com github.com: 192.30.253.113 -- Information acquired via protocol DNS in 15.6ms. -- Data is authenticated: no $ # (disconnect and reconnect wifi) $ systemd-resolve github.com github.com: resolve call failed: DNSSEC validation failed: no-signature More debug information is available in my upstream report (https://github.com/systemd/systemd/issues/4175), which has gotten no response in the last week and a half. I’m refiling this here because I believe that this regression and others (bug 1588230, bug 1624071, bug 1624317, bug 1449001) indicate that systemd-resolved is not ready for production, and with final freeze just a week away, leaving systemd-resolved enabled for the yakkety release would be reckless. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release yakkety -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1628778 Title: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1628778/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624320] [NEW] systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Public bug reported: systemd-resolved, or more precisely the hook script /lib/systemd/system /systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624317] [NEW] systemd-resolved breaks VPN with split-horizon DNS
Public bug reported: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624071] [NEW] libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation
Public bug reported: The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the hosts line of /etc/nsswitch.conf. This makes DNSSEC validation impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because if libnss_resolve returns a validation failure, glibc will simply fall back to libnss_dns. It also makes NXDOMAIN lookups twice as slow. The following syntax would preserve the fallback in the case that systemd-resolved is not running at all, but allow systemd-resolved to fail lookups that should fail when it is running: hosts: files resolve [!TRYAGAIN=return] dns ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624071 Title: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624071/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1591868] Re: fwupd consuming 100% CPU
The infinite loop is not in libyaml (yaml_parser_parse), but rather in its caller in appstream-glib (as_node_yaml_process_layer), which is ignoring the error code returned by yaml_parser_parse and blindly going around the loop again. This patch fixes it. ** Patch added: "appstream-glib_0.5.17-0ubuntu1_lp1591868.debdiff" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1591868/+attachment/4722986/+files/appstream-glib_0.5.17-0ubuntu1_lp1591868.debdiff ** Changed in: libyaml (Ubuntu Xenial) Status: New => Invalid ** Changed in: libyaml (Ubuntu Yakkety) Status: New => Invalid -- 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/1591868 Title: fwupd consuming 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1591868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1528728] Re: gnome-terminal starts up at 79×23 instead of 80×24
** Patch added: "vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1528728/+attachment/4539301/+files/vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff ** Tags added: patch ** Bug watch added: Debian Bug tracker #787104 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787104 ** Also affects: vte2.91 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787104 Importance: Unknown Status: Unknown ** Package changed: gnome-terminal (Ubuntu) => vte2.91 (Ubuntu) ** Bug watch added: GNOME Bug Tracker #750559 https://bugzilla.gnome.org/show_bug.cgi?id=750559 ** Also affects: vte via https://bugzilla.gnome.org/show_bug.cgi?id=750559 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1528728 Title: gnome-terminal starts up at 79×23 instead of 80×24 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1528728/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1528728] [NEW] gnome-terminal starts up at 79×23 instead of 80×24
Public bug reported: Starting gnome-terminal results in a 79×23 window instead of the standard 80×24, at least in Ubuntu Gnome with the default Adwaita theme on a high-DPI laptop. This makes it irritating to use some applications designed for an 80-column terminal. According to an upstream bug report (https://bugzilla.gnome.org/show_bug.cgi?id=750559), the problem is caused by the Ubuntu patch debian/patches/0001-Add-the-style-context- provider-with-FALLBACK-priorit.patch, which was reverted upstream (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c6) and in Debian (https://bugs.debian.org/787104) for this reason. A new version of this patch (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c9) fixes the problem for me. ** Affects: vte Importance: Unknown Status: Unknown ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Affects: vte2.91 (Debian) Importance: Unknown Status: Unknown ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1528728 Title: gnome-terminal starts up at 79×23 instead of 80×24 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1528728/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1512209] Re: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys'
** Bug watch added: Python Roundup #25493 http://bugs.python.org/issue25493 ** Also affects: python via http://bugs.python.org/issue25493 Importance: Unknown Status: Unknown ** Bug watch added: GNOME Bug Tracker #757184 https://bugzilla.gnome.org/show_bug.cgi?id=757184 ** Also affects: pygobject via https://bugzilla.gnome.org/show_bug.cgi?id=757184 Importance: Unknown Status: Unknown ** Attachment removed: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/pygobject/+bug/1512209/+attachment/4510908/+files/CurrentDmesg.txt.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/pygobject/+bug/1512209/+attachment/4510912/+files/JournalErrors.txt ** Information type changed from Private to Public ** Also affects: pygobject (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1512209 Title: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys' To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1512209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1512209] Re: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys'
This is a combination of two problems. One is that starting update-
manager results in these warnings:
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to ensure
that the right version gets loaded.
from gi.repository import Gtk
/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py:26: PyGIWarning:
GdkX11 was imported without specifying a version first. Use
gi.require_version('GdkX11', '3.0') before import to ensure that the right
version gets loaded.
from gi.repository import Gdk, GdkX11
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning:
Dbusmenu was imported without specifying a version first. Use
gi.require_version('Dbusmenu', '0.4') before import to ensure that the right
version gets loaded.
from gi.repository import Dbusmenu, Unity
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning:
Unity was imported without specifying a version first. Use
gi.require_version('Unity', '7.0') before import to ensure that the right
version gets loaded.
from gi.repository import Dbusmenu, Unity
The other is that when openafs-client is installed, the presence of
/usr/bin/sys causes Python to crash while displaying these warnings (see
linked bugs).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1512209
Title:
update-manager crashed with SyntaxError in find_cookie(): invalid or
missing encoding declaration for '/usr/bin/sys'
To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1512209/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
Every time I press one of these keys, I get the message
(gnome-settings-daemon:7822): GLib-GIO-WARNING **: Dropping signal
AcceleratorActivated of type (ua{sv}) since the type from the expected
interface is (uuu)
This is probably the same thing that happened in LP: #1217196 and LP:
#1376471.
--
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/1427877
Title:
Media, brightness and volume keys don't work with GNOME 3.15.90
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
Specifically, this is caused because gnome-shell 3.16 has https://git.gnome.org/browse/gnome-shell/commit/?id=2aa4fb02dd9c568038d12fe609252b6934367e76 but gnome-settings-daemon 3.14 does not have https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=46525602364088398eeb3a98d7bcfa64deeddd4e -- 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/1427877 Title: Media, brightness and volume keys don't work with GNOME 3.15.90 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
Here’s a tested patch that reverts the relevant gnome-shell changes to make it work with gnome-settings-daemon 3.14.x. ** Patch added: gnome-shell_3.16.2-1ubuntu1_lp1427877.debdiff https://bugs.launchpad.net/ubuntu-gnome/+bug/1427877/+attachment/4416604/+files/gnome-shell_3.16.2-1ubuntu1_lp1427877.debdiff ** Tags added: patch -- 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/1427877 Title: Media, brightness and volume keys don't work with GNOME 3.15.90 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1406189] Re: evolution-addressbook-factory crashed with SIGABRT in g_mutex_clear()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1406189 Title: evolution-addressbook-factory crashed with SIGABRT in g_mutex_clear() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1406189/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1406164] Re: evolution-calendar-factory crashed with SIGABRT in g_mutex_clear()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1406164 Title: evolution-calendar-factory crashed with SIGABRT in g_mutex_clear() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1406164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1367779] Re: [IMAPx] Fails to handle QUOTA response with no quotas
The fix is included in evolution-data-server 3.12.6, which is in utopic. To get the fix into previous releases, follow the process documented at https://wiki.ubuntu.com/StableReleaseUpdates. As per the first step in that process, I’m marking this Fix Released. ** Changed in: evolution-data-server (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1367779 Title: [IMAPx] Fails to handle QUOTA response with no quotas To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1367779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1367005] Re: gnome-control-center.real crashed with SIGSEGV in net_device_get_nm_device()
** Information type changed from Private to Public -- 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/1367005 Title: gnome-control-center.real crashed with SIGSEGV in net_device_get_nm_device() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1367005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287915] Re: pdf not rendered to device pixels on high-dpi screen
** Also affects: evince via https://bugzilla.gnome.org/show_bug.cgi?id=723431 Importance: Unknown Status: Unknown -- 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/1287915 Title: pdf not rendered to device pixels on high-dpi screen To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1287915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
If I might ask a stupid question, why does whoopsie think it needs to constantly monitor network connectivity when it doesn’t even have any reports to upload? -- 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/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1341108] [NEW] Backlight brightness control regressed from logarithmic scale to linear scale
Public bug reported: After upgrading from kernel 3.15.0-6 to kernel 3.16.0-3, the backlight became very difficult to control near the low end of the scale. The lowest setting now turns the backlight completely off, but the second- lowest setting is too bright. Meanwhile, the difference between the highest several settings is nearly imperceptible. This happened because /sys/class/backlight/acpi_video0/brightness has disappeared in kernel 3.16 in favor of /sys/class/intel_backlight/brightness. But the relationship between acpi_video0 and intel_backlight is not linear. As acpi_video varies [0,1,2,…,13,14,15], intel_backlight varies as [52,87,139,…,2557,3358,4437]. I measured the exact relationship between the two scales on kernel 3.15 and plotted it with the intel_backlight values on a logarithmic scale (see attachment). You can see that the function intel_backlight = 60*(4/3)^acpi_video0 is a good fit. It’s well known that perceived brightness varies logarithmically with physical intensity (Fechner’s law), so it’s no surprise that the acpi_video0 scale was more useful. Either the kernel or GNOME should adjust the intel_backlight scale to logarithmic. (I’m running utopic on a Lenovo Thinkpad T510.) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-3-generic 3.16.0-3.8 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anders 2179 F pulseaudio CurrentDesktop: GNOME Date: Sat Jul 12 07:06:12 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fd305e7c-c58c-4061-8105-5cda63c38849 InstallationDate: Installed on 2010-12-05 (1315 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) MachineType: LENOVO 4313CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic root=/dev/mapper/fdisk-ubuntu ro init=/lib/systemd/systemd quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-3-generic N/A linux-backports-modules-3.16.0-3-generic N/A linux-firmware1.132 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2013-10-31 (254 days ago) dmi.bios.date: 09/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4313CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-release utopic ** Attachment added: intel_backlight vs. acpi_video0 brightness scales https://bugs.launchpad.net/bugs/1341108/+attachment/4151081/+files/backlight-scale.png ** Summary changed: - Backlight control regressed from logarithmic scale to linear scale + Backlight brightness control regressed from logarithmic scale to linear scale ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/1341108 Title: Backlight brightness control regressed from logarithmic scale to linear scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1341108/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1330117] Re: eog crashed with SIGSEGV in gtk_application_impl_set_app_menu()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1330117 Title: eog crashed with SIGSEGV in gtk_application_impl_set_app_menu() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1330117/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1321705] [NEW] [systemd] /lib/systemd/system/accounts-daemon.service is unpackaged
Public bug reported: Now that accountsservice is configured with --enable-systemd, a /lib/systemd/system/accounts-daemon.service gets installed into debian/tmp, but it is not packaged anywhere. The absence of the file prevents gdm from starting successfully: May 21 06:16:23 fixed-disk dbus-daemon[896]: dbus[896]: [system] Rejected send message, 1 matched rules; type=method_call, sender=:1.60 (uid=0 pid=20007 comm=/usr/sbin/gdm ) interface=org.freedesktop.DBus.Properties member=GetAll error name=(unset) requested_reply=0 destina May 21 06:16:23 fixed-disk dbus-daemon[896]: dbus[896]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' May 21 06:16:23 fixed-disk dbus[896]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' May 21 06:16:23 fixed-disk dbus[896]: [system] Activation via systemd failed for unit 'accounts-daemon.service': Unit accounts-daemon.service failed to load: No such file or directory. See system logs and 'systemctl status accounts-daemon.service' for details. May 21 06:16:23 fixed-disk dbus-daemon[896]: dbus[896]: [system] Activation via systemd failed for unit 'accounts-daemon.service': Unit accounts-daemon.service failed to load: No such file or directory. See system logs and 'systemctl status accounts-daemon.service' for details. This may be fixed by adding lib/systemd/system/accounts-daemon.service (or one of its parents) to debian/accountsservice.install. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: accountsservice 0.6.37-1ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5 Uname: Linux 3.15.0-1-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 21 06:26:37 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2010-12-05 (1263 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) SourcePackage: accountsservice UpgradeStatus: Upgraded to utopic on 2013-10-31 (202 days ago) ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug systemd-boot utopic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1321705 Title: [systemd] /lib/systemd/system/accounts-daemon.service is unpackaged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1321705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1313998] [NEW] [systemd] gdm needs a systemd unit file
Public bug reported: The gdm package provides an Upstart job /etc/init/gdm.conf but not a systemd unit. Therefore, an ubuntu-gnome system booted with systemd remains stuck on the splash screen forever with no display manager. One is already available in the source package (data/gdm.service.in), and already installed by ‘make install’ (/lib/systemd/system/gdm.service), so it probably just needs to be added to debian/gdm.install. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gdm 3.10.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 28 23:07:09 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2010-12-05 (1240 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) SourcePackage: gdm UpgradeStatus: Upgraded to utopic on 2013-10-31 (179 days ago) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug systemd-boot utopic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1313998 Title: [systemd] gdm needs a systemd unit file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1313998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1313998] Re: [systemd] gdm needs a systemd unit file
I confirmed that the upstream systemd unit seems to work. ** Bug watch added: Debian Bug tracker #677107 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677107 ** Also affects: gdm (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677107 Importance: Unknown Status: Unknown ** Bug watch added: GNOME Bug Tracker #681339 https://bugzilla.gnome.org/show_bug.cgi?id=681339 ** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=681339 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1313998 Title: [systemd] gdm needs a systemd unit file To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1313998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1302321] Re: Missing /lib/systemd/systemd-logind-launch (referred to by /usr/share/dbus-1/system-services/org.freedesktop.login1.service)
This is different from bug 1302264. It’s much less severe, but still present in systemd-services 204-5ubuntu17. ** This bug is no longer a duplicate of bug 1302264 systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1302321 Title: Missing /lib/systemd/systemd-logind-launch (referred to by /usr/share/dbus-1/system-services/org.freedesktop.login1.service) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1302321] [NEW] Missing /lib/systemd/systemd-logind-launch (referred to by /usr/share/dbus-1/system-services/org.freedesktop.login1.service)
Public bug reported: The /usr/share/dbus-1/system-services/org.freedesktop.login1.service file in systemd-services contains Exec=/lib/systemd/systemd-logind-launch However, /lib/systemd/systemd-logind-launch doesn’t exist, because it’s missing from debian/systemd-services.install. For some reason this doesn’t seem to be causing obvious problems, but I thought you’d like to know. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 4 00:04:23 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2010-12-05 (1215 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2013-10-31 (154 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1302321 Title: Missing /lib/systemd/systemd-logind-launch (referred to by /usr/share/dbus-1/system-services/org.freedesktop.login1.service) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1260896] [NEW] multiarch accountsservice moved typelib to wrong path, broke gdm greeter
Public bug reported: Yesterday’s multiarch of accountsservice 0.6.35-0ubuntu3 (bug 1260370) broke the gdm greeter, making it impossible to log in. From /var/log/gdm/:0-greeter.log: (gnome-shell:1981): Gjs-WARNING **: JS ERROR: Error: Requiring AccountsService, version none: Typelib file for namespace 'AccountsService' (any version) not found @/usr/share/gnome-shell/js/ui/endSessionDialog.js:25 @/usr/share/gnome-shell/js/ui/main.js:15 @main:1 In order to work around this, I had to symlink /usr/lib/girepository-1.0/AccountsService-1.0.typelib - /usr/lib/x86_64 -linux-gnu/girepository-1.0/AccountsService-1.0.typelib. As far as I can tell, gir has no multiarch support (see e.g. http://bugs.debian.org/720071), so the typelib needs to be moved back into /usr/lib/girepository-1.0 and ‘Multi-Arch: same’ needs to be dropped. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: multiarch regression-release trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1260896 Title: multiarch accountsservice moved typelib to wrong path, broke gdm greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1260896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
** Attachment removed: image002.jpg https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/49579/+attachment/3900363/+files/image002.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194664] [NEW] Removing libp11-kit-gnome-keyring causes errors in every application loading libp11-kit
Public bug reported: When libp11-kit-gnome-keyring is removed but not purged, the conffile /etc/pkcs11/modules/gnome-keyring.module stays around, which causes every application that loads libp11-kit to look for the now-nonexistent /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so and yell on stderr. $ sudo apt-get remove libp11-kit-gnome-keyring … Removing libp11-kit-gnome-keyring:amd64 ... … $ cat /etc/pkcs11/modules/gnome-keyring.module # The file is installed/loaded from the default module p11-kit directory module: gnome-keyring-pkcs11.so # And where to store and lookup trust objects x-trust-store: pkcs11:library-manufacturer=GNOME%20Keyring;serial=1:XDG:DEFAULT x-trust-lookup: pkcs11:library-manufacturer=GNOME%20Keyring $ lpq p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory See http://wiki.debian.org/DpkgConffileHandling. (This is the real reason for the symptoms of bug 1157904, which was incorrectly fixed by adding a dependency on libp11-kit-gnome-keyring to cups.) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libp11-kit-gnome-keyring:amd64 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Tue Jun 25 17:28:59 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-12-05 (933 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2012-11-15 (222 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1194664 Title: Removing libp11-kit-gnome-keyring causes errors in every application loading libp11-kit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1194664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194664] Re: Removing libp11-kit-gnome-keyring causes errors in every application loading libp11-kit
I would also like to point out that this is the *third time* that dpkg conffile stupidity has caused problems with *this same package* (bug 911436, bug 1038577). What the heck is /etc/pkcs11/modules doing in /etc, anyway? -- 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/1194664 Title: Removing libp11-kit-gnome-keyring causes errors in every application loading libp11-kit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1194664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1052132] Re: [sound]: gnome-control-center crashed with SIGSEGV in _int_malloc()
I reproduced this three times, by going to the Sound control panel and repeatedly changing the alert sound. ** Changed in: gnome-control-center (Ubuntu) Status: Expired = Confirmed -- 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/1052132 Title: [sound]: gnome-control-center crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1052132/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1132720] [NEW] package gtk2-engines-pixbuf 2.24.14-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/gtk2-engines-pixbuf/README.gz', which is different from other ins
Public bug reported: -rw-r--r-- 1 anders anders 8606 Feb 18 14:15 gtk2-engines-pixbuf_2.24.16-1ubuntu1_amd64/usr/share/doc/gtk2-engines-pixbuf/README.gz lrwxrwxrwx 1 anders anders 29 Feb 24 23:22 gtk2-engines-pixbuf_2.24.16-1ubuntu1_i386/usr/share/doc/gtk2-engines-pixbuf/README.gz - ../libgtk2.0-common/README.gz ProblemType: Package DistroRelease: Ubuntu 13.04 Package: gtk2-engines-pixbuf 2.24.14-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Mon Feb 25 05:03:27 2013 DuplicateSignature: Unpacking replacement gtk2-engines-pixbuf:amd64 ... dpkg: error processing /var/cache/apt/archives/gtk2-engines-pixbuf_2.24.16-1ubuntu1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/gtk2-engines-pixbuf/README.gz', which is different from other instances of package gtk2-engines-pixbuf:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/gtk2-engines-pixbuf/README.gz', which is different from other instances of package gtk2-engines-pixbuf:amd64 InstallationDate: Installed on 2010-12-05 (813 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) MarkForUpload: True SourcePackage: gtk+2.0 Title: package gtk2-engines-pixbuf 2.24.14-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/gtk2-engines-pixbuf/README.gz', which is different from other instances of package gtk2-engines-pixbuf:amd64 UpgradeStatus: Upgraded to raring on 2012-11-15 (101 days ago) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict raring -- 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/1132720 Title: package gtk2-engines-pixbuf 2.24.14-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/gtk2 -engines-pixbuf/README.gz', which is different from other instances of package gtk2-engines-pixbuf:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1132720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1132720] Re: package gtk2-engines-pixbuf 2.24.14-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/gtk2-engines-pixbuf/README.gz', which is different from other insta
No, the issue is that gtk2-engines-pixbuf:i386 has symlinks at the same place gtk2-engines-pixbuf:amd64 has regular files. -- 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/1132720 Title: package gtk2-engines-pixbuf 2.24.14-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/gtk2 -engines-pixbuf/README.gz', which is different from other instances of package gtk2-engines-pixbuf:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1132720/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Do you have a pointer to an explanation of this “inherent issue” and why it’s impossible to solve? What I don’t understand, in particular, is _why_ GTK menus need to grab the mouse and keyboard in the first place. (But if this is an absolute requirement, surely the GTK developers can work with the X developers to come up with a new type of grab that’s cancelable by global shortcut keys and by the screensaver.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1082602] Re: gnome-settings-daemon crashed with SIGSEGV in dialog_init()
** Information type changed from Private to Public -- 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/1082602 Title: gnome-settings-daemon crashed with SIGSEGV in dialog_init() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1082602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1046490] Re: Saving attachment displays error because of null path
** Changed in: evolution (Ubuntu) Status: Opinion = 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/1046490 Title: Saving attachment displays error because of null path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1046490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1038577] Re: p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
$ dpkg-query -W -f '${Conffiles}\n' gnome-keyring
/etc/pkcs11/modules/gnome-keyring.module 18338a3e1e347ea0b25f3bc2182e95a6
/etc/xdg/autostart/gnome-keyring-ssh.desktop d0633706edab7dcf53b813d1fa27bfa5
/etc/xdg/autostart/gnome-keyring-gpg.desktop 526e256b3ced265836f32ade9881adad
/etc/xdg/autostart/gnome-keyring-pkcs11.desktop
64bc5cf28b393d3ac666cf8a5471e951
/etc/xdg/autostart/gnome-keyring-secrets.desktop
ba4b9d132b504a05e16290d86f0c3a96
/etc/pkcs11/modules/gnome-keyring-module 18338a3e1e347ea0b25f3bc2182e95a6
obsolete
gnome-keyring-module was renamed to gnome-keyring.module, but the old file
stays around because it’s a conffile. We need calls to dpkg-maintscript-helper
rm_conffile in the maintainer scripts.
http://wiki.debian.org/DpkgConffileHandling
** Package changed: p11-kit (Ubuntu) = gnome-keyring (Ubuntu)
--
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/1038577
Title:
p11-kit: duplicate configured module: gnome-keyring.module:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1038577/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1015338] Re: ambiguous package name 'libglib2.0-0'
*** This bug is a duplicate of bug 1015329 *** https://bugs.launchpad.net/bugs/1015329 ** This bug has been marked a duplicate of bug 1015329 dpkg fails to run after update (error: file triggers record mentions illegal package name `libgtk2.0-0' (for interest in file `/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules'): ambiguous package name 'libgtk2.0-0' with more than one installed instance) -- 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/1015338 Title: ambiguous package name 'libglib2.0-0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1015338/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 911431] [NEW] package libgcr-3-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gcr-3/ui/gcr-import-dialog.ui', which is also in package libgcr-3-1 3.2.2-0ubuntu1
*** This bug is a duplicate of bug 911411 *** https://bugs.launchpad.net/bugs/911411 Public bug reported: From today’s precise updates. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libgcr-3-common (not installed) ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Uname: Linux 3.2.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Tue Jan 3 15:10:51 2012 DuplicateSignature: Unpacking libgcr-3-common (from .../libgcr-3-common_3.2.2-1ubuntu1_all.deb) ... dpkg: error processing /var/cache/apt/archives/libgcr-3-common_3.2.2-1ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/gcr-3/ui/gcr-import-dialog.ui', which is also in package libgcr-3-1 3.2.2-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/gcr-3/ui/gcr-import-dialog.ui', which is also in package libgcr-3-1 3.2.2-0ubuntu1 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) SourcePackage: gnome-keyring Title: package libgcr-3-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gcr-3/ui/gcr-import-dialog.ui', which is also in package libgcr-3-1 3.2.2-0ubuntu1 UpgradeStatus: Upgraded to precise on 2011-11-16 (48 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict precise -- 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/911431 Title: package libgcr-3-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gcr-3/ui/gcr-import-dialog.ui', which is also in package libgcr-3-1 3.2.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/911431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 911431] Re: package libgcr-3-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gcr-3/ui/gcr-import-dialog.ui', which is also in package libgcr-3-1 3.2.2-0ubuntu1
*** This bug is a duplicate of bug 911411 *** https://bugs.launchpad.net/bugs/911411 -- 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/911431 Title: package libgcr-3-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gcr-3/ui/gcr-import-dialog.ui', which is also in package libgcr-3-1 3.2.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/911431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 890555] [NEW] Alt stopped working as Meta in gnome-terminal with gtk+3.0 3.2.2-0ubuntu1
Public bug reported: My Alt key no longer acts as Meta in gnome-terminal on my precise system as of today. So for example in bash, Alt+b no longer moves back a word, Alt+Backspace no longer deletes a word, etc. These keystrokes now act as if Alt was not pressed. Other libvte-based terminals like xfce4-terminal are not affected. I traced this to the upload of gtk+3.0 3.2.2-0ubuntu1. After downgrading libgtk-3-0, libgail-3-0, libgail-3-common, gir1.2-gtk-3.0, libgtk-3-bin from 3.2.2-0ubuntu1 to 3.2.0-0ubuntu3 and restarting gnome- terminal, the problem goes away. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0 Uname: Linux 3.1.0-2-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 1.26-0ubuntu1 Architecture: amd64 Date: Tue Nov 15 01:53:57 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vte Importance: Unknown Status: Unknown ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise regression-release -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/890555 Title: Alt stopped working as Meta in gnome-terminal with gtk+3.0 3.2.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/890555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 890555] Re: Alt stopped working as Meta in gnome-terminal with gtk+3.0 3.2.2-0ubuntu1
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-release ** Bug watch added: GNOME Bug Tracker #663779 https://bugzilla.gnome.org/show_bug.cgi?id=663779 ** Also affects: vte via https://bugzilla.gnome.org/show_bug.cgi?id=663779 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/890555 Title: Alt stopped working as Meta in gnome-terminal with gtk+3.0 3.2.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/890555/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 825553] Re: gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:178: dequeue_pending_request: La declaración `!xcb_xlib_unknown_req_in_deq' no se cumple.
Bug 832160 is private. Unmarking as duplicate. ** This bug is no longer a duplicate of private bug 832160 -- 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/825553 Title: gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:178: dequeue_pending_request: La declaración `!xcb_xlib_unknown_req_in_deq' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/825553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 811291] Re: Weird inconsistent behavior/lack of syncrhonization with empathy messaging integration
Bug 816762 is caused by the same gjs API change. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/811291 Title: Weird inconsistent behavior/lack of syncrhonization with empathy messaging integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/811291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 811291] Re: Weird inconsistent behavior/lack of syncrhonization with empathy messaging integration
I filed bug 822464 “Upgrade gjs to 1.29.16”, which is probably the cleanest way to deal with this problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/811291 Title: Weird inconsistent behavior/lack of syncrhonization with empathy messaging integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/811291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 762760] Re: resize grip in terminals obscures text
** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/762760 Title: resize grip in terminals obscures text To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/762760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 798951] Re: Applications menu fails to open due to change to /etc/xdg/menus/gnome-applications.menu
/etc/xdg/menus/gnome-applications.menu is now considered an obsolete conffile and needs to be explicitly removed: http://wiki.debian.org/DpkgConffileHandling -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/798951 Title: Applications menu fails to open due to change to /etc/xdg/menus/gnome- applications.menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/798951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816086] Re: gnome-session 3.1.3-0ubuntu5 fails to source ~/.gnomerc
$BASESTARTUP was just a temporary variable computed from $STARTUP by the same script (55gnome-session_gnomerc). But it would be worth checking if $STARTUP is parsed anywhere else. -- 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/816086 Title: gnome-session 3.1.3-0ubuntu5 fails to source ~/.gnomerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/816086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816086] [NEW] gnome-session 3.1.3-0ubuntu5 fails to source ~/.gnomerc
Public bug reported: /etc/X11/Xsession.d/55gnome-session_gnomerc tests that $BASESTARTUP matches gnome-session* when deciding whether to source ~/.gnomerc. But in gnome-session 3.1.3-0ubuntu5, $STARTUP has changed from ‘gnome- session’ to ‘env XDG_CURRENT_DESKTOP=GNOME gnome-session’ or similar, so $BASESTARTUP is ‘env’. Therefore ~/.gnomerc doesn’t get sourced anymore. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session-common 3.1.3-0ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7 Uname: Linux 3.0.0-6-generic x86_64 NonfreeKernelModules: openafs Architecture: amd64 Date: Mon Jul 25 15:03:55 2011 Dependencies: EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric regression-release -- 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/816086 Title: gnome-session 3.1.3-0ubuntu5 fails to source ~/.gnomerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/816086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816086] Re: gnome-session 3.1.3-0ubuntu5 fails to source ~/.gnomerc
** Patch added: gnome-session_3.1.3-0ubuntu5_lp816086.debdiff https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/816086/+attachment/2231944/+files/gnome-session_3.1.3-0ubuntu5_lp816086.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/816086 Title: gnome-session 3.1.3-0ubuntu5 fails to source ~/.gnomerc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/816086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 785529] Re: gsettings crashed with SIGABRT in g_settings_schema_new()
Nope, I can no longer reproduce it. ** Changed in: glib2.0 (Ubuntu) Status: Incomplete = Fix Released -- 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/785529 Title: gsettings crashed with SIGABRT in g_settings_schema_new() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/785529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 689880] Re: Clicking on a link hangs gnome-terminal until the server responds
The underlying GLib bug still exists (https://bugzilla.gnome.org/show_bug.cgi?id=643224), but I think it was only showing up for me because of missing x-scheme-handler/http associations during the natty development cycle. ** Bug watch added: GNOME Bug Tracker #643224 https://bugzilla.gnome.org/show_bug.cgi?id=643224 ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=643224 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/689880 Title: Clicking on a link hangs gnome-terminal until the server responds To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/689880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787778] Re: Last update of librsvg makes the system not recognize some image types
This should be fixed for real in 2.34.0-0ubuntu4. librsvg (2.34.0-0ubuntu4) oneiric; urgency=low * debian/librsvg2-common.postinst: Use the correct multiarch directory for *.so too. -- Anders Kaseorg ande...@mit.edu Tue, 24 May 2011 20:26:27 -0400 ** Changed in: librsvg (Ubuntu) Status: Confirmed = Fix Released -- 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/787778 Title: Last update of librsvg makes the system not recognize some image types -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 787778] Re: Last update of librsvg makes the system not recognize some image types
Ah, I misread your version number. I’m pretty sure the only thing that could cause librsvg2-common.postinst to exit with an error status is if ‘dpkg-architecture -qDEB_HOST_MULTIARCH’ failed, so this is probably a slightly different bug. Can you please file a new bug report? -- 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/787778 Title: Last update of librsvg makes the system not recognize some image types -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 788115] Re: [Oneiric] dpkg error when upgrading librsvg (2.34.0-0ubuntu4)
dpkg-architecture is part of dpkg-dev, so it can’t be used in librsvg2-common.postinst (a dpkg-dev dependency seems wrong). ** Changed in: librsvg (Ubuntu) Status: New = Confirmed -- 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/788115 Title: [Oneiric] dpkg error when upgrading librsvg (2.34.0-0ubuntu4) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 481588] Re: Open gnome-terminals are resized back to 80×24 when starting or stopping compiz
This still happens in both natty and oneiric when running ‘compiz --replace’. ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/481588 Title: Open gnome-terminals are resized back to 80×24 when starting or stopping compiz -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 778205] Re: emacs daemon inhibits logout
** Attachment added: emacs-logout.png https://bugs.launchpad.net/bugs/778205/+attachment/2115604/+files/emacs-logout.png ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- 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/778205 Title: emacs daemon inhibits logout -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 410407] Re: Adobe Flash Player does not respond to mouse clicks [READ DESCRIPTION]
RussianNeuroMancer, please don’t change bugs without any justification. ** Changed in: nspluginwrapper (Fedora) Importance: Undecided = Unknown ** Changed in: nspluginwrapper (Fedora) Status: New = Unknown ** Changed in: nspluginwrapper (Fedora) Remote watch: None = Red Hat Bugzilla #542424 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/410407 Title: Adobe Flash Player does not respond to mouse clicks [READ DESCRIPTION] -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 410407] Re: Adobe Flash Player does not respond to mouse clicks [READ DESCRIPTION]
It’s better to wait for the bug watcher to come back up than to destroy the association between Launchpad bugs and Fedora bugs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/410407 Title: Adobe Flash Player does not respond to mouse clicks [READ DESCRIPTION] -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 704105] Re: Resize grip always appears in bottom right of GTK+2.0 windows
Sebastien: How can this be an application issue? gtk_window_set_has_resize_grip() does not exist in upstream gtk+ 2.0; it was added by an Ubuntu patch (debian/patches/044_grips.patch). In order to maintain compatibility with upstream applications, the default needs to be changed to FALSE. -- 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/704105 Title: Resize grip always appears in bottom right of GTK+2.0 windows -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 670128] Re: gnome-open uses firefox while it's not the preferred browser
This bug is still present in chromium-browser. (To be sure, I tested again with chromium-browser 10.0.648.204~r79063-0ubuntu2 and xdg-utils 1.1.0~rc1-2ubuntu2.) See Chris’s comment #16: “Chromium is shipping its own xdg-mime and xdg- settings, so I've assigned myself to that too”. ** Changed in: chromium-browser (Ubuntu Natty) Status: Invalid = Confirmed -- 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/670128 Title: gnome-open uses firefox while it's not the preferred browser -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
