Public bug reported:
my user is in the cdrom group
still I can not burn a CD
calling
wodim -dummy tmp.iso
results in the following error output:
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
wo
Public bug reported:
Binary package hint: brasero
wodim / cdrkit has lots of open "new" bugs which are quite old.
It seems to be in a bad state, with no cure in sight (same Version 9:1.1.9 in
intrepid, jaunty, karmic
maybe the dependency should be switched to cdrskin or something else
** Affec
Public bug reported:
Binary package hint: gconf2-common
during the upgrade from hardy to intrepid beta this message was output by the
upgrade tool with the caption "gconf2-common could not be installed"
"Unterprozess post-installation script gab den Fehlerwert 139 zurück"
** Affects: gconf (Ubu
*** This bug is a duplicate of bug 283942 ***
https://bugs.launchpad.net/bugs/283942
** This bug has been marked a duplicate of bug 283942
crashed during installing packages on upgrade vom hardy to intrepid beta
(after about half of the packages had been upgraded)
--
gconf2-common post i
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/863834
Title:
[regression] Suspend on lid cl
this problem is still present in natty
** Changed in: gdm (Ubuntu)
Status: Incomplete => Confirmed
--
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/561806
Title:
gdm is not (re)s
Public bug reported:
Binary package hint: gdm
steps to reproduce:
- boot the system normally
- either: log in graphically and open a console window
- or: switch to vt1 and log into the console
- issue the command: telinit 1
Processes will be stopped and so on, but the procedure ends in a state w
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43698036/Dependencies.txt
** Description changed:
Binary package hint: gdm
steps to reproduce:
- boot the system normally
- either: log in graphically and open a console window
- - or: switch to vt1 an log into t
additional note:
if ESC is pressed while the splash screen is still moving, I get to a console
where I can log in
--
switching from runlevel 5 to runlevel 1 locks up system
https://bugs.launchpad.net/bugs/560132
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
this is not a gdm problem -> invalid
I will post a new report elsewhere
** Changed in: gdm (Ubuntu)
Status: New => Invalid
--
switching from runlevel 5 to runlevel 1 locks up system
https://bugs.launchpad.net/bugs/560132
You received this bug notification because you are a member of Ubunt
** Summary changed:
- gdm upstart job checks /proc/cmdline for single user mode, won't dtrt on
post-boot runlevel change
+ gdm upstart job checks /proc/cmdline for single user mode, won't start on
post-boot runlevel change
--
gdm upstart job checks /proc/cmdline for single user mode, won't sta
Public bug reported:
Binary package hint: gdm
The error occurs with these steps:
- (freshly install lucid beta)
- boot the system normally
- switch to runlevel 1 with 'telinit 1', gdm is stopped properly.
- log in as root
- switch to runlevel 2 with 'telinit 2'
Now gdm is not started. Because /e
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43961094/Dependencies.txt
--
gdm is not (re)started on transition from runlevel 1 to runlevel 2
https://bugs.launchpad.net/bugs/561806
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
13 matches
Mail list logo
