** Description changed:
All extensions are disabled. All gnome-shell extensions, if enabled, do
severe spamming of the syslog. Most errors are related to "st.bin"
and/or "st.whatever" has been already deallocated. I.e., at least six
popular extensions experience similar crashes after softw
Public bug reported:
The fan and cpu is very active during this event, thousands of
assertions reported. Syslog case attached.
lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
apt-cache policy gnome-software
gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.3
Candidate
I think this bug i filed might be a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1795111
In my case i could detect that the desktop became unresponsive as well.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
Public bug reported:
The fan and cpu is very active during this event, thousands of errors
reported. Syslog case attached. The desktop becomes unresponsive during
this event (for instance cant close windows).
lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
apt-cache policy gnome-s
*** This bug is a duplicate of bug 1745666 ***
https://bugs.launchpad.net/bugs/1745666
** This bug has been marked a duplicate of bug 1745666
gsd-housekeeping leaks file descriptors
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1795108/+attachment/5194407/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1795108/+attachment/5194405/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1795108/+attachment/5194406/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
apport information
** Tags added: apport-collected bionic third-party-packages
** Description changed:
All extensions are disabled. All gnome-shell extensions, if enabled, do
severe spamming of the syslog. Most errors are related to "st.bin"
and/or "st.whatever" has been already deallocate
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1795109/+attachment/5194410/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1795109/+attachment/5194409/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
apport information
** Tags added: apport-collected bionic third-party-packages
** Description changed:
The fan and cpu is very active during this event, thousands of
assertions reported. Syslog case attached.
lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1795109/+attachment/5194411/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
** 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
I'm fairly sure this is related to changes in fs.inotify.max_user_watches ("Too
many open files"). I recently got a bunch of warnings in misc code editors
about low values. Took me a while to understand the max_user_watches had
reverted back to the default value of about 8000. I.e., some update
(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
=
Nope, the message persists even with fs.inotify.max_user_watches=524288
Total nr messages:
# journalctl -m | grep gsd-housekeepin | wc -l
1947297
Previous nr boot messages (no reboot after workaround was applied, could be
weeks):
#journalctl -b | grep gsd-housekeepin | wc -l
51500
Current nr bo
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
In 15 hours 6000 new messages occur.
#journalctl -b | grep gsd-housekeepin | wc -l
12000
The permission on /var/tmp
drwxrwxrwt 45 root root 56K okt 1 14:53 tmp/
The permissions on mkinitramfs stuff in /var/tmp
drwxr-xr-x 12 root root 4,0K jan 21 2017 mkinitramfs_NNARsN/
-rw--- 1 root
#journalctl -b | grep gsd-housekeepin | wc -l
100067
Going for #5 by Janne since nothing else works (annoying task to keep
performing). It is also the suggestion by Fedora maintainers as systemd
does the same task of cleaning tmp
(https://bugzilla.redhat.com/show_bug.cgi?id=1563445)
Upstream repo
Same issue, not as severe regarding disk space. No extensions active.
# NOTE: will only grep first line of stacktracce
journalctl -m | grep osdWindow.js | wc -l
3597
gnome-shell --version
GNOME Shell 3.28.3
Oct 8 11:15:02 computer gnome-shell[2515]: Object St.Icon (0x55a64961dc90),
has been al
Problem exist in 18.10 as well after upgrade.
--
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/1745666
Title:
gsd-housekeeping leaks file descriptors
To manage notific
Btw, for me this happens 100% of all suspend/manual lock cases. Gnome
has crashed once completely as well since upgrade due to this issue. In
18.04 the whole screen was visible sometimes for a very short period of
time after lock, this is worse.
--
You received this bug notification because you a
Same problem after upgrade from 18.04 to 18.10. However, the whole
screen is visible when manually locking the screen (ctrl + alt + L in my
case).
All programs are minimized when locking manually/or resuming from
suspend and the screen goes slightly blurry, but not enough to distort
text for insta
Hi @Plurto. Where is this setting and is it a default ubuntu setting?
Thanks.
Note: Just using the default installation (had no active extensions
before upgrade besides Ubuntu system defaults). I.e., have not installed
dash to dock.
--
You received this bug notification because you are a member
@Plurto your workaround was successful for my case as well. Thanks.
Weird bug, transparency affecting clicks and interaction through a lock
screen.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpa
This happens on a clean installation of 18.10 here as well, and I'd like
to point out that the window miniature previews are clearly visible and
in some cases even readable from the lock screen by right clicking the
application icons and selecting "All Windows".
--
You received this bug notificat
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
This bug came back in recent updated after using workaround #5 by Janne.
Didn't notice at first, then severe system slowdowns and odd power
behaviour started to occur. 100% Fan on etc. Killing my disk long term
as well. I detected it when the gsd-housekeepin service crashed and
Ubuntu notified this
** 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:
Hi, the synaptics (libinput also installed) package work well for me in
16.04 (and previous version to 12.04 at least) up to 17.04 on thinkpads
(x2XX to carbon X1). Currently using carbon x1 5th gen. There is however
some form of instability with settings that affects many users including
me.
Some
Related and probably duplicate of:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-
daemon/+bug/1351772
--
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/1576685
FYI: got a better experience in gnome when opening a terminal and
running syndaemon -d in gnome. However, that seem to freeze the mouse
slightly too long after I have stopped typing. The unity version works
better (not sure what differs yet).
https://askubuntu.com/questions/505007/ubuntu-gnome-14-
For anyone ending up here, i lost this feature in 17.04 and need it:
quick fix found at https://askubuntu.com/questions/11/create-new-
document-right-click-option-missing-in-ubuntu-gnome/791946
"
1. See if you have ~/Templates folder. Create one if it is missing using
command:
mk
** 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
Public bug reported:
...
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gimp (not installed)
ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
Uname: Linux 4.9.0-15-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu1
A
** 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
Public bug reported:
Gtk:ERROR:/build/buildd/gtk+3.0-3.4.2/./gtk/gtkfilesystemmodel.c:751:gtk_file_system_model_sort:
assertion failed: (r == n_visible_rows)
It happened when I modified a file with another editor, while gedit had the
Open Files dialogue open with the modified file in the list.
I
I experienced the same error when I right-clicked one of the document
tabs:
ahj@anders-laptop:~/projects/prot$ gedit TcpSampling.cpp
ahj@anders-laptop:~/projects/prot$
(gedit:22206): Gdk-WARNING **: The program 'gedit' received an X Window System
error.
This probably reflects a
Public bug reported:
Please note: there are obviously several different causes for this
error. Other reports on launchpad and elsewhere identified sddm,
systemd, nvidia drivers and grub config. Since none of the solutions
mentioned there helped in my case, I am deliberately leaving the
information
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
+1 on the last comment.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1314556
Title:
Unable to mount Android MTP device
To manage notifications about this bug go to:
https://bugs.la
** 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/
Public bug reported:
...
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 228-5ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
Date: Thu Feb 4 03:32:
Public bug reported:
...
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 228-5ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
Date: Thu Fe
It seems like if a third party package has been (attempted) installed,
automated updates are disabled.
/ (#17)
However, even after you get the deb package installed, it breaks your
ability to sudo apt-get update. /
---
"Hi, this has been fixed upstream. If you still have issues, please
fully up
Changing back to Confirmed. The upstream bug fix just says "Done.
Please check in git." at 6th of March.
** Changed in: libgnomekbd (Ubuntu Lucid)
Status: Fix Committed => Confirmed
--
Keyboard layout panel indicator ignores theme font color settings
https://bugs.launchpad.net/bugs/51315
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
Confirm (Super - L) not working on Ubuntu 18.04, switching keyboard
language does not work either most of the time (Super + Space). Those I
use the most. Extremely annoying after some time, especially when using
dual screens (since the Gnome top bar is only on one monitor which is
even more annoyin
Sorry, small adjustment. I use wayland as default since 17.10 with gdm
(works well in general for me):
loginctl show-session c1 -p Type
Type=wayland
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.l
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
Comment 19 worked for me after reboot on 14.04. The error happened in
relation to manual a password reset I did (replaced shadow and passwd
with a backup).
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-
privileges/+bug/1240336/comments/19
--
You received this bug notification becau
** Changed in: shotwell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1335600
Title:
Publishing to flickr broken since api.flickr went ht
** Changed in: gedit (Ubuntu)
Status: New => Confirmed
--
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/1335613
Title:
Bad interaction between "code snippets" and "autocompletio
** Changed in: nautilus (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/12154
Title:
Nautilus should have a superuser mode
To manage notif
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
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
Public bug reported:
Binary package hint: gdm
The GDM greeter will crash (and be respawned indefinitely) whenever the
GECOS-field of an entry in /etc/passwd contains an '&'-sign (ampersand).
Attached is the output from /var/log/gdm/:0-greeter.log.
The system is Ubuntu 9.10 Desktop/AMD64. The GDM
** Attachment added: "Log of GDM crash"
http://launchpadlibrarian.net/39403648/gdmcrash.log
--
GDM crashes with '&' in passwd entry
https://bugs.launchpad.net/bugs/524422
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
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
201 - 300 of 648 matches
Mail list logo
