reassign 746286 libreoffice found 746286 1:3.5.4+dfsg2-0+deb7u2 severity 746286 important tag 746286 + moreinfo tag 746286 + unreproducible thanks
On Sat, Apr 26, 2014 at 02:58:32AM -0700, Mark Hedges wrote: > Package: libreoffice-writer Probably not, save and recovery is a central component.... (so -core. For overview "libreoffice" is probably better...) > Version: 1:3.5.4+dfsg2-0+deb7u2 Try something not ancient, please. This version will not receive updates except security and REALLY critical ones _when they are non-intrusive_. Even if this counted (whcih I argue against) as such, it probably will be a intrusive change. And bugs on it will be ignored unless they also are in 4.2.x. > Tonight for several hours, I worked on an odt document that I have > added to for several months. > > Something went screwy with Spotify. No controls responded. > tty0 showed segfaults. I logged in as root at ran `/etc/init.d/gdm3 stop`. So you stopped X, too in a hard way. You or GNOME/GDdm were not telliong LO to save, was it? > Started gdm3, then double clicked on the document. A dialog opened. Probably the usual "it crashed? you want to recover". > > I thought "I'd better make a backup copy of the corrupted file first." > I could not click outside the dialog so I clicked cancel. Then you didn't recover. And then you wonder why you didn't get what was there? > Minor setback, but nevertheless irreplaceable data, or replaceable > only in the sense that I vaguely remember what I wrote... not sure. > It's "important" to me. Ah, and because it's important to you you file it as "critical". Sure. Just to remember you: *YOU* have choosen to NOT do recovery. > I think most people by clicking "cancel" would not intend to proceed > with backup or wipe out the backup file. I think mostz people will want recovery. For me it's not a bug, sorry. Except maybe the autosave and backup thingy didn't work exactly good in 3.5.x, no idea. But that's not critical and yoou might want to file a correct(!) bug report on a version which will get any "normal" bug fixing attention or upstream support. ThTa#s not even the case anymore for 4.1.x beginning end of May... Regards, Rene -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
