Since it's still in proposed and a day is mostly over (and Europe is
asleep again) - could somebody outline / point me to the conditions for
a package to be moved from proposed to released?
This would be good to know to understand what is missing (and
potentially help?) instead of entering a lengt
@Ads2 Thanks for the link. Sadly, gdm3 is neither in the
autopkgtest-list, nor update-excuses, nor update-list, so it seems
things are stuck at an earlier stage and the documentation does not
clarify where to find out at which point help could be needed.
My intention was not to spam this repor
** Attachment added: "brasero-session.log"
http://launchpadlibrarian.net/14820010/brasero-session.log
** Also affects: brasero (Ubuntu)
Importance: Undecided
Status: New
** Also affects: k3b (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nautilus-cd-burner (U
Problem of wodim / cdrkit, thus only affecting brasero - no brasero-bug!
** Changed in: brasero (Ubuntu)
Status: New => Invalid
--
Regression: All burn-apps based on wodim are broken since hardy-upgrade
https://bugs.launchpad.net/bugs/236065
You received this bug notification because you
Problem of wodim / cdrkit, thus only affecting nautilus-cd-burner - no
n-c-b-bug!
** Changed in: nautilus-cd-burner (Ubuntu)
Status: New => Invalid
--
Regression: All burn-apps based on wodim are broken since hardy-upgrade
https://bugs.launchpad.net/bugs/236065
You received this bug notif
Problem of wodim / cdrkit, thus only affecting k3b - no k3b-bug!
** Changed in: k3b (Ubuntu)
Status: New => Invalid
--
Regression: All burn-apps based on wodim are broken since hardy-upgrade
https://bugs.launchpad.net/bugs/236065
You received this bug notification because you are a member
Same behaviour with Windows (just tried a live-cd).
So it must be hardware or - far more likely - media related. Thus, this bug can
be closed.
** Changed in: cdrkit (Ubuntu)
Status: New => Invalid
** Visibility changed to: Private
--
Regression: All burn-apps based on wodim are broken
The hal-update that arrived lately (yesterday?) fixes this, it seems.
However, unblacklisting the video-module breaks FN-F8 (CRT/LCD-Switcher) for me.
Brightness-control works fine again, even with video-module loaded.
Still, it would be nice if gnome-power-manager would have prevented it.
--
F
Sympy: Yes, I am. That was the name I had lost ^^. For me, blacklisting the
video-module fixed everything, and since the hal-info-update, I tried
unblacklisting video again.
Reboot proved brightness control was still working for me.
However, the FN-F8 to switch from CRT to DFP/LCD is gone.
Har
