[Bug 1793571] [NEW] wodim fails to burn CD as user (not root)
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. wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 Bytes on /dev/zero. calling the same command as root works fine Release: 18.04 ** Affects: brasero (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1793571 Title: wodim fails to burn CD as user (not root) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1793571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 863834] Re: [regression] Suspend on lid close broken on Oneiric
** 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 close broken on Oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/863834/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 561806] Re: gdm is not (re)started on transition from runlevel 1 to runlevel 2
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)started on transition from runlevel 1 to runlevel 2 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 561806] Re: gdm is not (re)started on transition from runlevel 1 to runlevel 2
** 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, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 561806] [NEW] gdm is not (re)started on transition from runlevel 1 to runlevel 2
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 /etc/init/gdm.conf does not configure the service to start on switching to runlevel 2 This bug is not the same as https://bugs.launchpad.net/bugs/436936 where you start with _booting_ into single user mode. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gdm 2.30.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 Architecture: i386 Date: Mon Apr 12 22:20:17 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) ProcEnviron: LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: gdm ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- 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, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 436936] Re: gdm upstart job checks /proc/cmdline for single user mode, won't start on post-boot runlevel change
** 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 start on post-boot runlevel change https://bugs.launchpad.net/bugs/436936 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.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 560132] Re: switching from runlevel 5 to runlevel 1 locks up system
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 Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 560132] Re: switching from runlevel 5 to runlevel 1 locks up system
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, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 560132] Re: switching from runlevel 5 to runlevel 1 locks up system
** 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 the console + - 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 where - the ubuntu splash screen is shown with the last dot red - no reaction to any key presses (like ctrl-alt-f1) The only way out is to reset the computer (the system was a freshly installed 10.4-beta1, gdm and upstart upgraded today) ProblemType: Bug Architecture: i386 Date: Sat Apr 10 18:25:53 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) Package: gdm 2.30.0-0ubuntu3 ProcEnviron: - LANG=de_DE.utf8 - SHELL=/bin/bash + LANG=de_DE.utf8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: gdm Uname: Linux 2.6.32-16-generic i686 -- 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, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 560132] [NEW] switching from runlevel 5 to runlevel 1 locks up system
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 where - the ubuntu splash screen is shown with the last dot red - no reaction to any key presses (like ctrl-alt-f1) The only way out is to reset the computer (the system was a freshly installed 10.4-beta1, gdm and upstart upgraded today) ProblemType: Bug Architecture: i386 Date: Sat Apr 10 18:25:53 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) Package: gdm 2.30.0-0ubuntu3 ProcEnviron: LANG=de_DE.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: gdm Uname: Linux 2.6.32-16-generic i686 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- 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, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 525012] [NEW] brasero depends on wodim which has lots of problems
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 ** Affects: brasero (Ubuntu) Importance: Undecided Status: New -- brasero depends on wodim which has lots of problems https://bugs.launchpad.net/bugs/525012 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 283935] Re: gconf2-common post installation script error 139
*** 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 installation script error 139 https://bugs.launchpad.net/bugs/283935 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 283935] [NEW] gconf2-common post installation script error 139
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 (Ubuntu) Importance: Undecided Status: New -- gconf2-common post installation script error 139 https://bugs.launchpad.net/bugs/283935 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
