Public bug reported:
Binary package hint: openoffice.org
After my upgrade to Ubuntu 7.10 I started to experience some very
disturbing appearances of the document recovery.
As an example I tracked down one appearance to the following reproducible
behavior:
- create a new plain text file
I did some more searching and now suppose, this bug is a duplicate of
52902 and 147965.
In addition I attached the file crash.ods for easy reproduction of the
error.
** Attachment added: crash.ods
http://launchpadlibrarian.net/11216683/crash.ods
** This bug has been marked a duplicate of bug
*** This bug is a duplicate of bug 181317 ***
https://bugs.launchpad.net/bugs/181317
This seems to be the same error I experienced at bug 181317, where I
also attached an example file.
** This bug has been marked a duplicate of bug 181317
[Gutsy] calc - faulty display of document recovery
*** This bug is a duplicate of bug 181317 ***
https://bugs.launchpad.net/bugs/181317
This seems to be the same error I experienced at bug 181317, where I
also attached an example file.
** This bug has been marked a duplicate of bug 181317
[Gutsy] calc - faulty display of document recovery
** Summary changed:
- [Gutsy] calc - faulty display of document recovery after closing files
+ [gutsy] calc - faulty display of document recovery after closing files
--
[gutsy] calc - faulty display of document recovery after closing files
https://bugs.launchpad.net/bugs/181317
You received
I have just installed 1.0.4-1feisty2: The bug is still out there
meaning that update-manager suggests to install the vmware-server
package again and again ...
Removing the repository is not really an option for me.
Again: If there is need for additional information, please contact me.
--
I can (still) confirm this issue with all of my machines (all regular
Feisty).
It's special annoying, because that package is so big. You end up
downloading another ~80 MB for nothing, whenever you forget to uncheck
that package at regular update schedules. :(
If there is need for additional
I can confirm that this behaviour seems to be caused by ipw394 in
conjunction with the kill switch:
I have a non-modified Dell Latitude D820 and with no cables attached
(even power) and no media inserted the systems freezes during booting up
as long as WiFi is disabled (kill switch set to ON).
I can confirm this bug and the solution presented by Jon A.:
My system is a Dell Latitude D820 with no cables connected at all. A
boot up with the WiFi switch turned OFF will fail with a freezed splash
screen, the recovery mode shows a Bug: soft lockup detected on CPU#0!
during starting LVM. If I
