Confirmed this behavior on post-install Mythbuntu 10.10 RC. Leaving as status new because I'm what this should really be against:
1. Apport, for not gracefully handling a permission problem (but if this a unique case, is having apport handle this the right thing to do vs. some other solution?) 2. the casper apport-hook (in ubiquity?) 3. casper or ubiquity for making casper.log read-only by root. Looking at the contents of that file, I'm not sure why it needs to be set so secure - but I admit I don't know what all might end up in that log. Marking as low since: 1. reporting against apport in live-cd (which is the most likely use case) works fine 2. apport has to be manually added to an installed system 3. reporting a bug against it in that situation strikes me as somewhat rare 4. it errors out with a meaningful message (permission problem), and so is obvious to users they need to use sudo or change the permission on that file ** Changed in: apport (Ubuntu) Importance: Undecided => Low -- [Maverick] ubuntu-bug fails when reporting a bug about ubiquity https://bugs.launchpad.net/bugs/653046 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
