tag 698784 + moreinfo thanks Hi,
On Wed, Jan 23, 2013 at 10:59:10AM -0500, Mark A. Hershberger wrote: > 1. Start by executing “lowrite” at the command line This will give you a "command not found" ;) > 2. Click “File” > 3. Notice that the menu is empty. Define empty. > 4. Hover over the thin bar that is displayed — presumably the top and > bottom of the non-existant menu. Ah. This is already broken and the root cause. Yes, it shouldn't crash but a non-existing file menu is bad. :) Which desktop? Do you use some "special" theme? KDE or GNOME? With or without -kde/-gnome installed respectively? > -- System Information: > Debian Release: 7.0 > APT prefers stable > APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, > 'experimental'), (500, 'testing-updates'), (500, 'stable-updates') > Architecture: amd64 (x86_64) Ah, right. You have a wheezy system (most of the packages below are wheezy) which prefers stable (see above) and which even has stuff from *experimental* (see e.g. the 3.6.5~rc2 stuff.) installed. What if you tried on a non-messy system? I will try to reproduce your issue but depends on how messy your system is this might not be reproducible. Besides that - if it's a bug - the vbug would be in core as that is responsible for the menu (obviously, as menu drawing is core stuff, no?) not writer. And *if* it's a bug in the experimental packages for missing breaks: etc it's a bug in *them*, not wheezys 3.5.4... Regards, Rene -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
