Public bug reported:
If I use System > Administration > Time and Date to change my time zone
and click Close, nothing changes, nor is there even any indication that
it failed.
** Affects: gnome-system-tools (Ubuntu)
Importance: Untriaged
Assignee: Ubuntu Desktop Bugs
Status: Ne
Yeah, I forgot to say that I'm on edgy. Thanks.
--
time-admin silently fails to change time zones
https://launchpad.net/bugs/55720
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug reported:
Affects: hal (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
I just installed Dapper today (2006-05-05), and hal is reporting my vfat
partition's mount point as '>\r\n\t', which results in an oddly-
named icon on my desk
Public bug reported:
Binary package hint: gnome-session
GNOME plays the login sound before it starts to listen to the volume
control hotkeys, so the login sound can’t be muted or quieted. It
should wait to play the login sound until the volume control hotkeys are
working.
I’m using maverick (bu
** Changed in: gnome-terminal (Ubuntu)
Status: New => Confirmed
--
gnome-terminal doesn't handle colons in URLs
https://bugs.launchpad.net/bugs/377367
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in ubuntu.
--
d
RFC 3986 defines a “reserved” character as one that may have special
meaning in a URI, depending on the scheme-specific syntax; it does _not_
imply in any way that such characters are invalid. Indeed, if it
weren’t for these characters, we probably couldn’t write any useful URIs
at all:
res
To expand on this, the only restriction placed on the colon by section 3.3 is
“In addition, a URI reference (Section 4.1) may be a relative-path reference,
in which case the first path segment cannot contain a colon (":") character.”
(to avoid misinterpreting the relative path as a scheme), and th
Public bug reported:
Binary package hint: gnome-keyring
When I run, say,
gpg2 --use-agent -sa https://bugs.launchpad.net/bugs/642534
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs mailing list
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/642534/+attachment/1606331/+files/Dependencies.txt
** Attachment added: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/642534/+attachment/1606332/+files/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
https://
(gdb) bt
Backtrace from the spinning thread:
#0 __pthread_disable_asynccancel ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/cancellation.S:97
#1 0x7f3bf97d9b99 in read () at ../sysdeps/unix/syscall-template.S:82
#2 0x7f3bf8c9c6a2 in read (channel=0xe96c60, buf=0xe9b670 "", count=1024
anarcat: “Incomplete” means that the bug report is missing information,
not that the bug is not yet fixed. Marking “Confirmed” instead.
** Changed in: gdm (Ubuntu Lucid)
Status: Incomplete => Confirmed
--
The new gdm doesn't give an option to run /etc/X11/Xsession
https://bugs.launchpad.
libb-size-perl was deleted in Jaunty, so this monstrous bug can be
closed now.
** Changed in: libb-size-perl (Ubuntu)
Status: Confirmed => Invalid
--
[intrepid] Rebuild with perl 5.10
https://bugs.launchpad.net/bugs/230016
You received this bug notification because you are a member of Ubu
Public bug reported:
Binary package hint: gvfs
/etc/profile.d is the wrong place for a bash completion script; it only
affects login shells. The right place for gvfs-bash-completion.sh is
/etc/bash_completion.d.
** Affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
--
/etc
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:
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 rend
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 su
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-xs
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
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 s
** 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
** 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
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
T
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
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 d
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:/
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/50f0910cf05bdc1d10710c7
• 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
• 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)
• 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
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
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 i
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 mem
** 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-s
(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/+at
(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/1
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
=
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
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/1
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.launch
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/b
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/gnom
** 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 XGetModifierMa
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:
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.launchp
** 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
** 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_sh
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:
** 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
** 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(
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/b
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-0ub
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 fa
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 decide
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
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-
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.freede
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 my
** 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
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
** 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_
** 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
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
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=46525602364088398eeb3a98d7bcfa64deeddd4e
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_lp1
** 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
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.
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 nam
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 reaso
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 no
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 re
** 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/
Tobias, your improved-lcd-filtering PPA contains a version of poppler
labelled as “0.12.4-0ubuntu4~ppa1”. However, it is actually based on
0.12.4-0ubuntu1, and is missing the changes in Ubuntu’s 0.12.4-0ubuntu2,
even though it claims to have a higher version.
Similarly for evince 2.29.92-0ubuntu4
> I needed a method to override the packaged versions and by
> trial and error it appeared that I have to increment ubuntuX.
No; the correct versioning scheme for a PPA is described here:
https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage#Versioning
> On another note, you posted a pa
> Well, yes. And I received a stupefying reaction when I expressed
> disbelief about this claim back then:
> http://lists.freedesktop.org/archives/poppler/2009-August/005008.html
Sounds like he sees a slight difference, not enough to personally care
about it, but would accept a good patch if someo
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),
a
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: Un
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
** 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 man
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
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://b
** 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
T
** 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
ne
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
I’m assuming Gerry C. made a mistake (there isn’t even a new compiz in
karmic-updates at all), and restoring the Invalid status set by
mtecknology.
** Changed in: compiz (Ubuntu)
Status: Fix Released => Invalid
** Changed in: compiz (Debian)
Importance: Undecided => Unknown
** Changed
You added “or stopping rc RUNLEVEL=[2345]” rather than “or starting rc
RUNLEVEL=[2345]”. This will break openafs-modules-dkms because
/etc/init.d/openafs-client (which requires the kernel module to have
already been built) is started from rc.
** Changed in: dkms (Ubuntu)
Status: Fix Commit
And it will (bug 483506), but I worry that there may be other
initscripts with the same problem. In any event, should we really force
all of these transitions to happen at exactly the same time?
--
dkms should start before gdm if needed for video driver
https://bugs.launchpad.net/bugs/453365
You
Even if it is desirable to convert openafs-client to upstart right now,
forcing dkms to load after rc would force openafs-client to load after
rc. This will be a problem for other services that depend on openafs,
such as apache2 installations with docroot in /afs.
dkms provides kernel modules, an
> Now, if you chain that with the openafs upstart job waiting for DKMS to
> be done and apache/mysql/$favorite_server_service waiting for network
> file systems to be ready and you've got a very logical ordering to your
> boot process.
Yes yes, I understand that. And I want very much to live in t
> If the effort is just to get any packages in main by Lucid, I don't see why
> it's not achievable.
Fixing all of main isn’t good enough for many users (openafs is itself
in universe). Whether it’s acceptable to break universe is up to the
Ubuntu TB, but there’s absolutely no point in breaking *
> --- debian/gdm.upstart2009-12-11 05:36:55 +
> +++ debian/gdm.upstart2009-12-14 20:12:34 +
> @@ -9,7 +9,9 @@
> start on (filesystem
>and (graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1
> or drm-device-added card0 PRIMARY_DEVICE_FOR_DISPL
Filed as bug 497137.
--
dkms should start before gdm if needed for video driver
https://bugs.launchpad.net/bugs/453365
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu
I also saw a gdm greeter spawned during an upgrade, and I can reproduce
this with `sudo dpkg-reconfigure gdm`. It is not unresponsive for me,
though; I can log in as myself to return to my session.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
Unresponsive gdm greeter displayed
Public bug reported:
Binary package hint: gnome-screensaver
As of Karmic updates a few days ago (possibly gtk2 2.17.2-0ubuntu2 →
2.17.3-0ubuntu1, but I’m not sure), I can no longer unlock my screen.
The password entry box in the gnome-screensaver unlock dialog is
disabled (grayed out), so I canno
Public bug reported:
Binary package hint: gnome-screensaver
After today’s Jaunty gtk+2.0 2.14.5-1ubuntu2 -> 2.15.0-0ubuntu1 upgrade,
gnome-screensaver can no longer unlock the screen. When I enter the
correct password, gnome-screensaver-dialog just sits there displaying
“Checking...”. top shows
Here is a stacktrace with debug symbols from gnome-screensaver-dialog
while it is spinning.
** Attachment added: "ThreadStacktrace.txt"
http://launchpadlibrarian.net/21666786/ThreadStacktrace.txt
--
gnome-screensaver fails to unlock after gtk 2.15.0 upgrade
https://bugs.launchpad.net/bugs/320
My duplicate bug #320666 (“But…but I reported it first!” :-P) has a
stack trace with debugging symbols that might be useful for tracking
down this problem. When I enter the correct password, and gnome-
screensaver-dialog just sits there displaying “Checking...”, top shows
that the CPU is spinning,
Public bug reported:
Binary package hint: evolution
When using an account with hierarchical folders, Folder → Subscriptions
presents a collapsed tree with little triangles to expand subtrees.
These triangles are no longer functional in Jaunty’s evolution 2.25.90,
which makes it hard to subscribe
Hmm, I can no longer reproduce this. Closing for now.
** Changed in: evolution (Ubuntu)
Status: Incomplete => Invalid
--
Folder → Subscriptions expansion triangles broken in 2.25.90
https://bugs.launchpad.net/bugs/326994
You received this bug notification because you are a member of Ubun
** Changed in: gnome-keyring (Ubuntu)
Status: New => Confirmed
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
https://bugs.launchpad.net/bugs/328127
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Works for me too now with 2.25.91-0ubuntu1. If anyone still sees this
problem after installing this update, feel free to reopen the bug.
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Fix Released
--
gnome-keyring-daemon returns Agent admitted failure to sign using the key.
htt
1 - 100 of 260 matches
Mail list logo
