[Bug 978333] Re: xfwm4 is not running after failed shut down

2012-07-08 Thread Bruce Fowler
You could try 'chattr +i' on your session file. ... or just make it read only. But I really would like to track this down and identify what needs to be fixed, so other folks don't fall into this trap. I need a background watcher that can tell me who changes a file and when. I'll try putting

[Bug 978333] Re: xfwm4 is not running after failed shut down

2012-07-05 Thread Bruce Fowler
I've disabled save session on logout and I still see xfwm4 not starting *sometimes*. Maybe one reboot in four, I have to start it manually, or copy in a backed-up xfce4-session file. That file is still being overwritten on logout, again, *sometimes*. Annoying bug, I will post more if I can

[Bug 992232] Re: no libreoffice-report-builder in precise

2012-06-17 Thread Bruce Fowler
Björn, That ppa fixes the problem. Thank you very much for the help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992232 Title: no libreoffice-report-builder in precise To manage notifications

[Bug 992232] Re: no libreoffice-report-builder in precise

2012-06-16 Thread Bruce Fowler
When I do: # add-apt-repository ppa:libreoffice/libreoffice I get: Cannot access PPA (https://launchpad.net/api/1.0/~libreoffice/+archive/libreoffice) to get PPA information, please check your internet connection. So then I try: # ping -c3 https://launchpad.net I get: ping:

[Bug 992232] Re: no libreoffice-report-builder in precise

2012-06-09 Thread Bruce Fowler
Björn, thanks. I'll give it a try... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992232 Title: no libreoffice-report-builder in precise To manage notifications about this bug go to:

[Bug 992232] Re: no libreoffice-report-builder in precise

2012-06-05 Thread Bruce Fowler
It's hard to believe that this bug has been hanging around for over a month and is still of undecided severity and unassigned. It is also hard to believe that it only affects nine users. You can bet that for everyone who found this bug and added their vote, a hundred have said, The heck with