1 |
I recently had to revert back to xorg-server 1.2.0-r1 to regain the |
2 |
ability to use gnome-terminal (or any terminal in gnome) In my case the |
3 |
system was still rock solid, but the terminals just disappeared, and |
4 |
would not re-appear using any of the icons/menus. I didn't (still |
5 |
don't) know how to use a virtual terminal(Ctrl-Alt-F1-F6) to open a |
6 |
window in the X terminal so, reverted it went. |
7 |
|
8 |
Wish I could offer more assistance. |
9 |
|
10 |
|
11 |
|
12 |
On Sat, 2007-03-17 at 07:14 -0700, Wil Reichert wrote: |
13 |
> > I run KDE here, don't even have GNOME installed as for me as a power |
14 |
> > user, GNOME's dumb-down-everything-by-removing-most-choices-as-too- |
15 |
> > complex policy drives me right up one wall and down the other! (I'm with |
16 |
> > Linus on that one, it seems!) I'm running kwin, with composite |
17 |
> > functionality enabled (only window semi-transparency, not the other |
18 |
> > stuff) as I mentioned above. |
19 |
> Never could get over the UI, didn't seem intuitive to me for whatever |
20 |
> reason. Been following KDE 4 development, look pretty spiffy. |
21 |
> Probably give it a shot again once it goes alpha. Could be mistaken |
22 |
> but it almost seems like the gnome folk are more concerned about their |
23 |
> release schedule than innovating new features. |
24 |
> |
25 |
> > Anyway, this build doesn't have the patches applied, and exa works fine |
26 |
> > once again. |
27 |
> I think an exa update was one of the main additions in 1.3, the other |
28 |
> being the randr 1.2 code. |
29 |
> |
30 |
> > If you've not already done so and the lack of gnome-terminal is serious |
31 |
> > for you, of course there are quite a few other alternatives, xterm being |
32 |
> > the generic one, naturally. |
33 |
> > |
34 |
> > Thinking about your bug, perhaps you have the reverse problem to mine, as |
35 |
> > konsole (compare to gnome-terminal) did run here but as I said, with |
36 |
> > issues (blanking and the like). You might dig out the AIGLX patches from |
37 |
> > 1.2.0-r1 and see if they still apply cleanly to 1.2.99.901. If they do, |
38 |
> > try that and see if your problem still exists. Take a look at the ebuild |
39 |
> > but I /think/ all you have to do is list the appropriate patches in a |
40 |
> > PATCHES= line, copying the ones from the line in the ~arch version |
41 |
> > to .901 in your overlay. A single bit of editing, not too hard. (I was |
42 |
> > going to try building without those patches here, but never got around to |
43 |
> > it before seeing your post mentioning the new version, so tried it |
44 |
> > instead.) |
45 |
> > |
46 |
> > If that fixes your problem, then it's likely those patches may have to be |
47 |
> > hooked to a USE flag of some sort, so people can apply them or not |
48 |
> > depending on the hardware and software they run. |
49 |
> > |
50 |
> > Something else that /might/ be worth trying. Enable (or disable, if you |
51 |
> > have it enabled) USE=xcb, and do an emerge -N world to rebuild anything |
52 |
> > using that flag. xcb is a new and lighter alternative to Xlib. Xlib can |
53 |
> > render to it for anything not yet migrated to xcb yet, and that's what |
54 |
> > most X clients are using if xcb is enabled at this point, xlib thru xcb. |
55 |
> > |
56 |
> > I decided to try enabling it at the same time I upgraded to xorg-server |
57 |
> > 1.2.99.901, and one of the things that got rebuilt as a result was cairo, |
58 |
> > which of course is what GTK+ now uses for rendering, and GNOME of course |
59 |
> > in turn uses GTK+. (I do have GTK+ merged, as a pan dependency, but no |
60 |
> > GNOME.) |
61 |
> > |
62 |
> > What I'm thinking is that xcb might bypass whatever issue you are having, |
63 |
> > particularly if it's a deprecated xlib call that's no longer working, |
64 |
> > since xcb is newer and presumably written with AIGLX and similar new |
65 |
> > technologies in mind, where xlib has a lot of compatibility cruft left |
66 |
> > over from long ago versions. I've seen the difference that makes in xaa/ |
67 |
> > exa, xlib/xcb could well make a similar difference. |
68 |
> > |
69 |
> > So anyway, please update if you try any of the suggestions above, whether |
70 |
> > or not they work, or if you get it working again otherwise. I'm always |
71 |
> > interested in finding out if my guesses were correct or not, as it's very |
72 |
> > useful info the next time something similar comes up. |
73 |
> |
74 |
> A couple of emerge -e world's later.... |
75 |
> |
76 |
> metacity - gnome-terminal starts fine, <CTRL><SHIFT>T creates a new tab |
77 |
> beryl - gnome-terminal starts fine, <CTRL><SHIFT>T crashes it as before |
78 |
> |
79 |
> I'll chalk this one up to either stupidity on my part or the beryl svn |
80 |
> code I'm using is conflicting with the new driver / server code. No |
81 |
> big, some breakage is to be expected running ~arch & live code. FWIW, |
82 |
> I'm using XAA and have xcb enabled. EXA makes little difference on my |
83 |
> system, haven't had a chance to see what recompiling w/out xcb will |
84 |
> do. The next rc build should be hitting portage soon, I'll probably |
85 |
> just wait & see if that does some magic. Or breaks more stuff =) |
86 |
> |
87 |
> Wil |
88 |
> -- |
89 |
> gentoo-amd64@g.o mailing list |
90 |
> |
91 |
|
92 |
-- |
93 |
gentoo-amd64@g.o mailing list |