1 |
Merged Qt 3.1. Konsole crashing badly every time I start it. |
2 |
Everything else is fine. If I start from an xterm it says: |
3 |
|
4 |
Qt: Locales not supported on X server |
5 |
_KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root |
6 |
DCOPServer up and running. |
7 |
Qt: Locales not supported on X server |
8 |
KCrash: crashing.... crashRecursionCounter = 2 |
9 |
KCrash: Application Name = konsole path = <unknown> pid = 6317 |
10 |
Qt: Locales not supported on X server |
11 |
|
12 |
The message about locales was there earlier as well, but it did not |
13 |
effect anything. Any idea what to do? |
14 |
|
15 |
Thanks in advance. -- Viktor |
16 |
|
17 |
|
18 |
On Sun, Dec 01, 2002 at 03:47:12PM +0200, Dan Armak wrote: |
19 |
> -----BEGIN PGP SIGNED MESSAGE----- |
20 |
> Hash: SHA1 |
21 |
> |
22 |
> On Sunday 01 December 2002 08:25, Viktor Lakics wrote: |
23 |
> > Dear Devs, |
24 |
> > |
25 |
> > With the console (aka. Linux) font in konsole I get garbled chars |
26 |
> > (line drawing chars) in mutt and mc. I found some hints in the |
27 |
> > konsole-dev list as to solving this problem. Apparently this bug is |
28 |
> > associated with qt-3.05 not picking the right character to test the |
29 |
> > line drawing char capability of a font (apparently the "console" |
30 |
> > font does not have this char what qt-3.05 picks). Qt-3.04 claimed |
31 |
> > to be working, but it is not in portage and I do not want to mess |
32 |
> > with my kde on a production machine... |
33 |
> > |
34 |
> > Could anyone test that when we upgrade to kde-3.1, qt-3.1 will fix |
35 |
> > this bug? Would KDE-3.04 or KDE-3.1 work with qt-3.04? What would be |
36 |
> > the way to install qt-4.04 from sources without messing up my kde? |
37 |
> |
38 |
> The best way would be for you to test qt 3.1 right now, it's in portage and |
39 |
> working very nicely. It's a clean upgrade from 3.0.5 (no recompiles or |
40 |
> anything required) and you can go back to 3.0.5 easily afterwards if you want |
41 |
> to - it's just a question of compile time either way. |
42 |
> |
43 |
> I do have to say that the problems described in kde bug #44993 don't seem to |
44 |
> be gone, but that is from a cursory perusal of the code (I can't reproduce |
45 |
> the bug itself) so it's really best for you to test. Everyone will likely be |
46 |
> upgrading to qt 3.1.0 in a few days anyway. |
47 |
> |
48 |
> As for qt 3.0.4, if you really want it, just copy the latest 3.0.5 ebuild to a |
49 |
> qt-3.0.4.ebuild and it should work. (You may have to disable the Korean patch |
50 |
> though.) |
51 |
> |
52 |
> > |
53 |
> > Bugs mentioned (konsole-dev): |
54 |
> > |
55 |
> > http://bugs.kde.org/show_bug.cgi?id=44993 |
56 |
> > http://bugs.kde.org/show_bug.cgi?id=45250 |
57 |
> > |
58 |
> > Relevant bug in bugzilla-Gentoo: |
59 |
> > |
60 |
> > http://bugs.gentoo.org/show_bug.cgi?id=11063 |
61 |
> > |
62 |
> > Thanks in advance. -- Viktor |
63 |
> > |
64 |
> > -- |
65 |
> > gentoo-dev@g.o mailing list |
66 |
> |
67 |
> - -- |
68 |
> Dan Armak |
69 |
> Gentoo Linux developer (KDE) |
70 |
> Matan, Israel |
71 |
> Public GPG key: http://www.gentoo.org/~danarmak/danarmak-gpg-public.key |
72 |
> -----BEGIN PGP SIGNATURE----- |
73 |
> Version: GnuPG v1.2.1 (GNU/Linux) |
74 |
> |
75 |
> iD8DBQE96hLkUI2RQ41fiVERAkeqAJ9OoZAxvvfhl/8C/GvSQD0WGczJ4wCfT4nI |
76 |
> XcAk5QNjKIqBTprMlVL+hDg= |
77 |
> =Yzdh |
78 |
> -----END PGP SIGNATURE----- |
79 |
> |
80 |
> |
81 |
> -- |
82 |
> gentoo-dev@g.o mailing list |
83 |
> |
84 |
|
85 |
-- |
86 |
gentoo-dev@g.o mailing list |