Public bug reported:
Binary package hint: kpersonalizer
I upgraded to kde 3.5.4 and after that I experienced problems with the
package personalizer (3.5.4-0ubuntu1~dapper2).
KDEs first time wizard starts every time I start KDE. Expected behaviour
would be, that it starts only the first time or
yes, previously the user being a member of the cdrom group, which had
write perms on the device, was enough to be able to burn cds
--
cdrecord fails to burn cd's
https://launchpad.net/bugs/54828
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
** Changed in: Ubuntu
Sourcepackagename: None = foomatic-db
--
Can't add a printer in KDE: parser error?
https://launchpad.net/bugs/42965
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
thanks for that extra information, the binary name is supposed to be
sorted but this looks like it is missed for this
** Changed in: k3b (Ubuntu)
Status: Needs Info = Confirmed
--
k3b uses wrong normalize binary name
https://launchpad.net/bugs/44524
--
kubuntu-bugs mailing list
user reports fixed
** Changed in: k3b (Ubuntu)
Status: Needs Info = Fix Released
--
k3b and cdrecord priviliges problems
https://launchpad.net/bugs/32039
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
The negative comment by Sebastian Trueg in reply #10 of kde bug 82843
seems to be directed only towards the claim of k3b becoming unusable as
made in reply #9 of said bug, rather than the rejecting the general idea
of not having compulsary and unconditional md5 checking.
--
k3b should *not*
Could SCSI command filtering be the root cause:
http://lwn.net/Articles/193516/
--
cdrecord fails to burn cd's
https://launchpad.net/bugs/54828
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
