Public bug reported:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to t
I can do that if really required, but this is not a bug with my system -
it's just the way the system works right now, so I'm suggesting an idea
for how we can make it better :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in U
apport information
** Tags added: apport-collected bionic
** Description changed:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmo
apport info added.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this bug go to:
https://bugs.l
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1800277/+attachment/5206696/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bug
Reported as https://gitlab.gnome.org/GNOME/gdm/issues/438.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notificati
** Changed in: upstart (Ubuntu)
Status: Confirmed => Invalid
--
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/1256262
Title:
stop "triggers" logout (from gnome-session?)
There is an upstart logrotate job that runs automatically soon after
session start, however, it does not (yet) run periodically to handle
rogue jobs such as gnome-session. You can however run the job yourself
simply enough as a non-root user:
$ start logrotate
Please attach a few lines of the out
Thank you for reporting this bug. However, please do not report the same
bug three times :-)
** Package changed: upstart (Ubuntu) => gnome-session (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https
** Also 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/1342586
Title:
[utopic] [proposed] cgmanager breaks lig
** Changed in: upstart
Status: Confirmed => Fix Released
--
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/1235649
Title:
uevent spam causes libdbus client code in session upst
** Also affects: systemd-shim (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
Upstart jobs specifying cgroup
** Changed in: upstart
Status: In Progress => Invalid
** Changed in: upstart
Importance: Critical => Undecided
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
** Summary changed:
- systemd-shim fails to handle cgmanager being unavailable
+ upstart can race with cgmanager when using remove-on-empty
** Changed in: upstart
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
Public bug reported:
The fix for upstart bug 1357252 has highlighted the fact that systemd-
shim does not support functionality required by logind, namely:
- abandoncgroup (delete if possible)
- stopsession(kill all tasks and remove cgroup)
Because of this, systemd-shim sets the remove-on-empty
** Changed in: upstart
Status: In Progress => Fix Released
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu)
Status: New
Public bug reported:
/lib/systemd/system/ifup@.service specifies:
ExecStart=/sbin/ifup --allow=hotplug %I
This really needs to be:
ExecStart=/sbin/ifup --allow=hotplug %I
Since otherwise, for systems that don't use network-manager, the service
will only bring up interfaces which have speci
** Changed in: upstart (Ubuntu)
Status: Fix Released => Incomplete
** Changed in: upstart (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchp
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-session (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
http
Not an upstart issue. Sounds like it might be a non-privileged mounting
problem.
** Package changed: upstart (Ubuntu) => gvfs (Ubuntu)
--
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/106
This problem sounds like it could be kernel issue.
** Also affects: linux (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/98
A way to fix this:
$ gsettings set org.gnome.desktop.screensaver embedded-keyboard-command
''
For some reason, I had the following set:
$ gsettings get org.gnome.desktop.screensaver embedded-keyboard-command
'onboard -xid'
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
gnome-session/main.c has disabled all signal handling, but intention was
seemingly to only disable SIGSEGV signal handing:
10:43 chrisccoulson: hi - I'm looking at how gnome-session currently
shuts down and trying to understand why the following is
Public bug reported:
$ zenity --calendar
zenity: error while loading shared libraries: libGL.so.1: cannot open shared
object file: No such file or directory
$ ldd `which zenity`|grep -i gl
libglib-2.0.so.0 => /lib/i386-linux-gnu/libglib-2.0.so.0 (0xb703b000)
libGL.so.1 => not foun
Problem was caused by failed background apt-get update on my system
which had not yet configured nvidia-current.
** Changed in: zenity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to zenity in Ub
This problem appears to be resolved for me on an installed precise
system. Copying bar.desktop to ~/Desktop/ and once I allow the file to
be "executable" (right click, properties), the icon text shows line 1 as
"Install Ubuntu 12.04" and line 2 as "LTS".
** Attachment added: "bar.desktop"
http
Public bug reported:
Whilst investigating bug 937611, I enabled the on-screen keyboard.
However, I subsequently switched if off via "System Settings" ->
"Universal Access" -> Typing tab -> "Typing Assistant".
As expected, the keyboard no longer displays on the desktop but when the
screen locks au
--
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/942530
Title:
on-screen keyboard always displays once enabled
To manage notifications about this bug go to:
https://bugs.la
Public bug reported:
I'm not entirely sure where or why this is happening, but I have seen on
~5 occasions now my system spontaneously switch off.
Initially, I thought it might be an init/kernel issue, but today I saw
the problem occur twice and crucially, I also got to see the console and
there
*** This bug is a duplicate of bug 751689 ***
https://bugs.launchpad.net/bugs/751689
It's not aliens, it is of course the kernel :)
** This bug has been marked a duplicate of bug 751689
ThinkPads overheat due to slow fans when on 'auto'
--
You received this bug notification because you a
Thanks guys. I now have keychain and gnupg-agent installed to allow me
to provide a password via the command-line.
However, I do feel (1)+(2) should be fixed in ssh-agent / gnome-keyring
since it is rather unfriendly to grab the window aggressively (although
admittedly, gksudo does the same [but a
Fix tested on natty only at this stage.
--
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/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on post-bo
Fix now also tested on lucid.
--
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/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on post-boot runleve
It's looking like the change I made for bug 436936 might be the culprit,
but I am unable to recreate this issue at present.
Please could follow the steps below to run Upstart in debug mode:
1. Hold down SHIFT key before the splash screen appears (this will then display
the grub menu).
2. Type, "
@Fabio - two out of how many systems? Is it consistently reproducible
for those two systems?
--
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/735805
Title:
GDM fails to start
--
deskto
It's looking like the problem may be with the runlevel test here:
31 if [ "$curr" = S -o "$prev" = unknown ]
32 then
33 # Single-user mode
34 plymouth quit || :
35 exit 0
36 fi
I've attached a version of /et
@Benjamin: thanks for testing! Could you also confirm that if you boot
to recovery mode (single user mode) that once you've at a shell, running
"telinit 2" displays gdm as expected?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm i
@Benjamin: ok - I think that's why I added the "unknown" check which
clearly caused problems for some systems. The change below *should*
stop gdm from starting in recovery mode:
31 if [ "$curr" = S -o -z "`echo $UPSTART_EVENTS|egrep -o
"\"`" ]
32 then
33
If those who experienced this problem could help with testing a fix for
bug 436936, I have attached a new gdm.conf to bug 436936. Thanks very
much!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.n
Please could those who experienced the problems on bug 735805 provide
feedback on using the attached gdm.conf. If possible, could you confirm
that:
1) When you boot normally, gdm starts as expected.
2) When you boot to a recovery console that gdm does *NOT* start.
(hold down SHIFT and select
@Jonathan - thanks for testing! Good news. Yes, I think you are right re
friendly-recovery.
@Erick and others - I attach an updated gdm.conf which might help.
Looking at the old gdm.conf, I think it was missing a condition which
this new gdm.conf adds. Please let me know your findings. Thanks for
Public bug reported:
If I plug in my Logitech H530 USB Headset, it shows as "ClearChat Pro
USB" under Hardware in 'gnome-control-center sound', but it does *not*
show up as a valid input or output device if I click either the Input or
Output tabs.
On the input tab, the "Connector" menu only has 1
--
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/917165
Title:
gnome-control-center does not allow selection of USB headset for input
or output
To manage notifications
Hmm after a reboot, the problem appears to have gone away. My selected
h/w profile is "Analogue Stereo Output + Analogue Mono Input" (which has
not changed).
There are a couple of extra odd things going on here:
1) if I change the h/w profile for the headset to "Analogue Stereo
Output" and switch
*** This bug is a duplicate of bug 861268 ***
https://bugs.launchpad.net/bugs/861268
** This bug has been marked a duplicate of bug 861268
text corruption in terminals (xterm, urxvt) and emacs
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Fix has now had to change due to an update to gdm.conf for udev-
fallback-graphics.
An updated gdm.conf is attached.
** Attachment added: "gdm.conf"
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/436936/+attachment/2059024/+files/gdm.conf
--
You received this bug notification because yo
Public bug reported:
Binary package hint: gnome-control-center
> gnome-about-me
(gnome-about-me:4710): libebook-WARNING **: ebook.c:2254: cannot get book from
factory: Invalid source
(gnome-about-me:4710): libebook-WARNING **: ebook.c:2254: cannot get
book from factory: Invalid source
about-me
** Description changed:
--
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/685848
Title:
gnome-about-me crashes with invalid source
--
desktop-bugs mailing list
desktop-
This bug is natty-specific. I don't have the super powers seemingly to
specify this :)
--
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/685848
Title:
gnome-about-me cras
Public bug reported:
Binary package hint: gdm
/etc/init/gdm.conf shows:
emits starting-dm
However, this event is not emitted by gdm. It appears this was a remnant
of the changes associated with 2.29.1-0ubuntu4.
That said, gdm *is* emmitting two events that are not documented in
gdm.conf:
--
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/706842
Title:
gdm upstart config file lists incorrect events
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.
51 matches
Mail list logo
