[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#416444: xserver-xorg: crash, maybe font related



Toni Mueller wrote:
> while browsing the font list in OOo 2.1 Writer (manually fetched from
> openoffice.org, not the Debian package), my X server crashed, along with
> my window manager (fvwm) and all other apps which depend on X. This was
> in .xsession-errors:
>
> [FVWM][convert_charsets]: WARNING -
>         Invalid byte sequence during conversion from UTF-8 to ISO-8859-1
> [FVWM][convert_charsets]: WARNING -
>         Invalid byte sequence during conversion from UTF-8 to ISO-8859-1
> [FVWM][convert_charsets]: WARNING -
>         Invalid byte sequence during conversion from UTF-8 to ISO-8859-1
> [FVWM][convert_charsets]: WARNING -
>         Invalid byte sequence during conversion from UTF-8 to ISO-8859-1
> [FVWM][convert_charsets]: WARNING -
>         Invalid byte sequence during conversion from UTF-8 to ISO-8859-1
>   

Are you sure these warnings appeared just before the crash? Do you get
such warning right now while he server is not crashing?

Do you have any way to reproduce this? If so, you should try to get a
backtrace with gdb. And also test with a more recent Xserver.

> (amongst other apps' messages while dying). There was nothing in
> /var/log/* I could identify as to being related to the crash.
>   

Not even a backtrace at the end of Xorg.0.log? It is going to be hard to
debug then...

> My locale is set to de_DE.utf8. I logged in via SSH from a different
> machine and tried to reboot the machine by running "shutdown -r now"
> (with appropriate rights), but the machine just froze hard and didn't
> come up again. After a while, I pressed the reset button - the keyboard
> was as dead as could be - to have a reboot, and on reboot, the system
> was saying something along "replaying file system transaction log", and
> "cleaning orphaned inode xyz", several times.
>   

That's quite common when the system crashes without syncing/unmounting
any filesystem.

> Tagging 'important' because it could be related to UTF-8, and it caused
> data loss. Not tagging 'grave' because it happened only once so far.
>   

Good choice :)

Brice




Reply to: