Public bug reported:
lsb_release -rd
No LSB modules are available.
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
This unresolved dependency seems to be the main t64 migration blocker
for the last weeks. I've manually thinned out the dependencies that "apt
upgrad
Public bug reported:
root@charion:~# systemctl status
● charion
State: starting
Jobs: 2 queued
Failed: 1 units
Since: Fri 2018-03-16 20:37:37 CET; 39min ago
CGroup: /
├─user.slice
│ ├─user-122.slice
│ │ ├─user@122.service
│ │ │ ├─pulse
Public bug reported:
after the recent upstart -> systemd "migration" my system is left unable to
complete it's boot process.
It asks for the first passphrase, but not for the second.
When booting with upstart (via the advanced boot options), the system
behaves correctly and asks for both passphr
--
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/1036998
Title:
[with fix] gnome-keyring installs duplicate identical config files
gnome-keyring[-.]module
To manage notificat
Public bug reported:
root@kyle:/etc/pkcs11/modules# ls -la
total 16
drwxr-xr-x 2 root root 4096 Aug 13 08:43 .
drwxr-xr-x 3 root root 4096 Sep 9 2011 ..
-rw-r--r-- 1 root root 293 Sep 18 2011 gnome-keyring-module
-rw-r--r-- 1 root root 293 Aug 13 02:57 gnome-keyring.module
root@kyle:/etc/pkc
On 10/03/2011 10:57 AM, Rodrigo Moya wrote:
> Before setting it, can you please let us know what are the values for
> "sleep-inactive-ac-timeout", "sleep-inactive-ac", "sleep-inactive-
> battery-timeout" and "sleep-inactive-battery"?
>
> You can get the values fromt he command line with:
>
> gsetti
** Description changed:
- System goes to hibernate or suspend even when set to "Don't suspend" on
+ System goes to hibernate or suspend even when set to "Don't suspend" on
the Suspend when inactive setting
- I use the affected Laptop additionally as a fileserver. The powermanagement
in 11.1
Public bug reported:
System goes to hibernate or suspend even when set to "Don't suspend" on
the Suspend when inactive setting
I use the affected Laptop additionally as a fileserver. The
powermanagement in 11.10 changed in the last few days in a way so that I
can't let the laptop sit without cons
Above I had already described a manual workaround.
After killling -9 gnome-session one can use the terminal provided by the rescue
session to start gnome-session
(the new Ubuntu gui is even more unusable then Gnome-3)
Killing gdm and running startx is not necessary.
Cheers
Mike
--
You rec
As additional data point:
Starting a rescue session will leave a terminal behind even after killing -9
gnome-session from the console.
>From within the terminal gnome-session can then successfully be restartet.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
--
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/811822
Title:
gnome-session gets stuck utilizing 100% cpu time of one core
To manage notifications about this bug go to:
https:
Public bug reported:
gnome-session gets stuck utilizing 100% cpu time of one core
killing gnome-session manually will kill -9 (it doesn't react to a normal kill)
leaves
an unusable session behind.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-session 3.1.3-0ubuntu3
ProcVersionSign
I wonder if this might be related to bug 438274?
Especially to the comment which Ross Alexander wrote on 2010-12-20:
"The reason for this is the gnome-settings-daemon is not working so GTK does
not pick up the correct icon theme so it defaults back to hicolor, which does
not have icons for "win
The error message is
metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion failed:
(default icon)
gnome-session[4259]: WARNING: Application 'metacity.desktop' killed by signal
gnome-session[4259]: WARNING: App 'metacity.desktop' respawning too quickly
--
You received this bug no
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/794854
Title:
metacity fails to start and causes "Oh no! Something has gone wrong"
message
To manage notifications about this bug
Public bug reported:
Binary package hint: metacity
metacity fails to start and causes "Oh no! Something has gone wrong"
message
On a dual screen setup one can see that Nautilus is running fine, only
one screen gets covered with the "Oh no!" message that forces the logout
ProblemType: Bug
Distro
16 matches
Mail list logo
