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:
** 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
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
** 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
** 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
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
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
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
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
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
** 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
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.
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
(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.
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
(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"
** 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
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
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
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
• 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
• 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)
• 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:
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
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.
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
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
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.
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
** 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
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
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.
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.
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.
** 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
** 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
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
** 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.
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
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
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
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
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
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
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:
** 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
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
** 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
**
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.
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.
--
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
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
** 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
** 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
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
** 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
** 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
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.
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
** 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
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
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),
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:
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
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
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
** 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.
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
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
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
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
-
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
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
** 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
** 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
$ 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
*** 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
*** 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:
*** 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
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
** 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
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
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
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
** 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
/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.
$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
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,
** 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,
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:
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
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
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
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
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.
** 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,
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
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.
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.
--
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
1 - 100 of 259 matches
Mail list logo
