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

Bug#596573: [openoffice.org] crash with X-Error if KDE file selector tries to show preview of a Gimp file



Hi,

On Mon, Sep 13, 2010 at 11:39:35PM +0200, Rene Engelhard wrote:
> Hmm. Interesting. It works in my "normal" sid, but neither in a i386 chroot nor
> in a amd64 one (I get warnings about dbus and kded though).

And the 3.3 which worked in my "normal" sid doesn't work in the chroot either...
I also tried vanilla upstream 3.3 built with kde4 enabled. same story.

Talking with our KDE maintainers about this problem didn't result in an immediate
solution either, except that debugging this inside a chroot is completely difficult,
(no dbus, no kded working, ..). But it seems it boils down to:

0:32 < svuorela> _rene_: I'm a bit unsure, actually. the more I read the kfile code, the more puzzled I get ... were there any stderr output ?
00:32 < svuorela> but well. p fileModule()
00:32 < _rene_> except that dbus and kded ones?
00:33 < svuorela> yeah
00:33 < _rene_> let me try again
00:33 -!- funkyHat (Matt Wheeler) [~m@funkyhat.org] has joined #debian-devel
00:34 < pinotree> svuorela: looks like it cannot load the filemodule, although that is provided in libkfile4 (which is a dep of ooo-kde)
00:37 -!- spectra [~spectra@189.42.2.103] has quit [Quit: spectra]
00:37 < svuorela> hmm... yeah.
00:39 < svuorela> _rene_: is s_module a nullpointer or something valid ?
00:39 -!- cortana [~sam@92.14.183.195] has quit [Ping timeout: 480 seconds]
00:40 -!- chrisccoulson_ [~chr1s@82.132.248.191] has quit [Ping timeout: 480 seconds]
00:41 < _rene_> print s_module
00:41 < _rene_> $1 = (class KAbstractFileModule *) 0x0
00:41 < svuorela> okay.
00:41 -!- angelabad [~angel@4.85-87-84.dynamic.clientes.euskaltel.es] has quit [Quit: Ex-Chat]
00:42 < svuorela> I agree with pinotree, although I have no clue about the 'why' or 'how to fix'
00:42 < svuorela> and given that s_module is a nullpointer, a segfault looks reasonable. I can't figure out why s_module is null.

which also results in all  those dbus and kded warnings printed on console.

No idea whether that's your case, but do those work? do you get any of those warnings? Are you sure your KDE/KDE environemnt is correct?

Othewise: simply no idea, and as long as it doesn't happen on "normal" systems (asked SuSE to try it too
and it worked for  them too) I would just tag this + unreproducible...

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  rene@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70



Reply to: