Re: GNOME 3.2 beta2 available in gnome-unstable

@wonder That was fast! Thank you so much.

“Never regard study as a duty, but as the enviable opportunity to learn to know the liberating influence of beauty in the realm of the spirit for your own personal joy and to the profit of the community to which your later work belongs.”

Re: GNOME 3.2 beta2 available in gnome-unstable

My GDM (and thus gnome-shell after started) is now at tty2 instead of tty7 or 8. Anybody has idea why it is?

Interestingly, this seems has something to do with the problem I reported sometime ago: xorg use 100% CPU after some time (of order 10 minute or one hour) after start up. I suspect they are related, because

(1) After xorg use 100% CPU on my computer, I cannot switch tty using ctrl+alt+number (before that I can)

(2) Using "ps aux", I can find such a command is run just at the time the xorg problem appears:root 2991 0.0 0.0 6024 712 tty2 Ss+ 15:49 0:00 /sbin/agetty -8 -s 38400 tty2 linux

(3) I cannot suspend when the xorg problem appears. But I can logout and re-login, after that, the xorg problem is gone. At the same time, GDM goes to tty7 or 8.

I didn't find anything strange in log files, either xsession-errors, Xorg.0.log, gdm log, ... But log files can be provided if needed.

and now GDM goes to tty7 as desired. The xorg cpu 100% problem happens randomly previously, thus I don't know whether it's now solved. But in these two weeks I never run several hours without the problem as now. Thus it seems to have been solved also.

Perhaps the GDM problem is because GDM starts too quickly, and something is not ready? Also the xorg CPU 100% problem is completely confusing. They have gone anyway.

Thank wonder and simongmzlj a lot for the suggestions! @simongmzlj: I never modified inittab. It has /sbin/agetty from tty1 to 6.

Re: GNOME 3.2 beta2 available in gnome-unstable

Ensure you start the display manager last in the DAEMONS array, otherwise X will later allocate a tty device which was previously claimed by Getty (see /etc/inittab). Not placing the display manager at the end can cause X crashes, and is therefore unsupported.

Ensure you start the display manager last in the DAEMONS array, otherwise X will later allocate a tty device which was previously claimed by Getty (see /etc/inittab). Not placing the display manager at the end can cause X crashes, and is therefore unsupported.

Re: GNOME 3.2 beta2 available in gnome-unstable

I have an issue with the libwebkit package in extra changing from stable to unstable to support the gnome-unstable repo. you have your repo, if you want to put an unstable package in your unstable repo, by all means go for it, but don't change packages in other repos.

Re: GNOME 3.2 beta2 available in gnome-unstable

aeosynth wrote:

I have an issue with the libwebkit package in extra changing from stable to unstable to support the gnome-unstable repo. you have your repo, if you want to put an unstable package in your unstable repo, by all means go for it, but don't change packages in other repos.

Re: GNOME 3.2 beta2 available in gnome-unstable

aeosynth wrote:

I have an issue with the libwebkit package in extra changing from stable to unstable to support the gnome-unstable repo. you have your repo, if you want to put an unstable package in your unstable repo, by all means go for it, but don't change packages in other repos.

Re: GNOME 3.2 beta2 available in gnome-unstable

Yes, I did peek at the source files. I guess I am a bit confused on how the different repos work together. I started looking into this because I noticed that libwebkit stable has been updated to 1.4.3 - http://webkitgtk.org/?page=download . Is this update going to be ignored, since the trunk pkgbuild has a higher pkgver?

Re: GNOME 3.2 beta2 available in gnome-unstable

aeosynth wrote:

Yes, I did peek at the source files. I guess I am a bit confused on how the different repos work together. I started looking into this because I noticed that libwebkit stable has been updated to 1.4.3 - http://webkitgtk.org/?page=download . Is this update going to be ignored, since the trunk pkgbuild has a higher pkgver?

Re: GNOME 3.2 beta2 available in gnome-unstable

When I login through gdm, if I press enter after typing my password, gdm hangs. But if I click on "Sign in" I'm logged in properly. Anyone else with this issue? This is with the latest updates in gnome-unstable.