You are not logged in.
Does this depend on anything from testing?
Offline
@wonder, thanks for your work - again.
Anyway, I tried to login with autologin enabled and it just hangs up, gnome-shell doesn't start. After deletenig relevant lines in /etc/gdm/custom.conf it works. Does anyone have this issue?
The closest bug I found: https://bugzilla.gnome.org/show_bug.cgi?id=650575
Offline
I haven't enabled testing-repo, only the gnome-unstable one. GDM works for me as well as Sushi (not on OOo documents thought). Empathy integration is much better. Didn't like Tracker to be started without my consent. Now the following package have also been upgraded from gnome-unstable but they don't seem to work:
- gnome-shell-extension-alternative-status-menu 3.1.91-0.20111107
- gnome-shell-extension-drive-menu 3.1.91-0.20111107
- gnome-shell-extension-places-menu 3.1.91-0.20111107
- gnome-shell-extension-system-monitor 3.1.91-0.20111107
- gnome-shell-extension-xrandr-indicator 3.1.91-0.2011110
Offline
wonder wrote:~/.xsession-errors
your log is full of mess, i wonder why you have so many problems. here is how a log is supposed to be http://paste.xinu.at/dSY6/
Give what you have. To someone, it may be better than you dare to think.
Offline
I haven't enabled testing-repo, only the gnome-unstable one. GDM works for me as well as Sushi (not on OOo documents thought). Empathy integration is much better. Didn't like Tracker to be started without my consent. Now the following package have also been upgraded from gnome-unstable but they don't seem to work:
- gnome-shell-extension-alternative-status-menu 3.1.91-0.20111107
- gnome-shell-extension-drive-menu 3.1.91-0.20111107
- gnome-shell-extension-places-menu 3.1.91-0.20111107
- gnome-shell-extension-system-monitor 3.1.91-0.20111107
- gnome-shell-extension-xrandr-indicator 3.1.91-0.2011110
Have you tried editing the metadata.json files for those extensions and placing the version number for the new gnome-shell version?
Offline
Empathy integration is much better.
But it doesn't memorize the autoconnexion to Facebook and forgot totally the MSN account settings (i have to recreate it each time i launch Empathy...)
Now the following package have also been upgraded from gnome-unstable but they don't seem to work:
- gnome-shell-extension-xrandr-indicator 3.1.91-0.2011110
Works for me (but totally useless, imho)
The dock extension is also available but doesn't work...
Last edited by jaco (2011-09-12 19:01:56)
Offline
alphazo wrote:Empathy integration is much better.
But it doesn't memorize the autoconnexion to Facebook and forgot totally the MSN account settings (i have to recreate it each time i launch Empathy...)
didn't I say to report all functionality bugs upstream? the whole point of providing this repo is to help upstream to polish this release.
i'm lucky that we still have users who know what are they doing instead of only crying all loud
https://bugs.freedesktop.org/show_bug.cgi?id=40740
Last edited by wonder (2011-09-12 19:14:04)
Give what you have. To someone, it may be better than you dare to think.
Offline
didn't I say to report all functionality bugs upstream?
Yes, provided i'm sure it's a bug related to upstream, not on my own side (my previous pb with GDM wasn't related to upstream, for example, but to my own configuration or to the Arch Linux pam configuration, i don't know...).
Furthermore, from a "logical" point of vue, i can't imagine that Empathy cannot store my MSN account nor autoconnect to FB (two different problems) as it works perfectly with my Google account. So i want to be sure it's not my fault before report it... And i'm not crying loud
But you're right : i should have first browse the known Empathy problems. At least, it explains why my Google account is considered special.
Last edited by jaco (2011-09-12 19:21:48)
Offline
well, if is a problem with our gdm pam modules, tell me about it. on the other hand, don't try to investigate more about your empathy/accounts problem. It's already reported and i pasted the link, it's related to telepathy-mission-control not to empathy
Give what you have. To someone, it may be better than you dare to think.
Offline
well, if is a problem with our gdm pam modules, tell me about it. on the other hand, don't try to investigate more about your empathy/accounts problem. It's already reported and i pasted the link, it's related to telepathy-mission-control not to empathy
As i wrote it above, the gdm-password pam file seems to consider that all user uid are >= 1000. That's probably the case when we use standard tools to create accounts, but it fails if we change the uid for some reason (for my own, my user account was 500 to be in sync with my NFS server...).
Offline
Have you tried editing the metadata.json files for those extensions and placing the version number for the new gnome-shell version?
Well the above packages come straight from gnome-unstable. Metadata.json files already contain the right version number.
Offline
I'm still waiting that bug report to be fixed to make python2/python3 version installable in parallel. If this won't happen, i think i'll split the pkgconfig files out in separate packages instead of conflicting the main packages.(this is what opensuse and fedora do right now)
There's no file/directory conflict between python-gobject and python2-gobject from gnome-unstable.
https://gist.github.com/1212658
So, because gnome2 (dependencies) and gnome3 are going to co-exist for a while, I too think that splitting the packages (and, most importantly removing the conflict) is the way to go. We may thus save the time OpenSUSE and Fedora developers put on deciding about this.
“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.”
Offline
@Shanto well it is, you just did a diff between python-gobject and python2-gobject and the files that are the same are exclude.
the files conflicting are:
/usr/include/pygobject-3.0/pygobject.h (easy to split, file matches
/usr/lib/pkgconfig/pygobject-3.0.pc (not easy because the content is different)
and docs (easy to split)
python-gobject and python2-gobject have nothing to do with gnome2
Give what you have. To someone, it may be better than you dare to think.
Offline
@wonder thanks for (re)shedding some light there. I keep doing strange things when running on caffaine. Wrong pastes, wrong set of packages and whatnot.
python-gobject and python2-gobject have nothing to do with gnome2
You will find it hard to believe, but python2 and python3, which share very similar situation with gnome2 and gnome3, are what I intended to write. My hand just betrayed.
/usr/lib/pkgconfig/pygobject-3.0.pc (not easy because the content is different)
I too was looking at that bug report earlier today. For a while, the time it's taking (9 days?) made me think that we may have to go ahead on our own this time. At the worst case, we cannot keep this hanging for 3.2.1+, can we?
How about removing this line altogether (and unify the .pc) until we get a better recommendation from GNOME team?
overridesdir=${exec_prefix}/lib/python2.7/site-packages/gi/overrides
With my limited knowledge and research, this variable is not of much use right now. And, even if it becomes useful in future, it must not have hard-coded reference to python as it is. Not for Arch at the very least.
Lastly, I must mention, until this conflict gets resolved, several heavy-weight Gnome3/3.2 complements, such as gnome-tweak-tool and gnome-shell-system-monitor, remains broken (one or the other) for 3.2. Not much fun!
“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.”
Offline
gnome-tweak-tool broken? works fine. i hope you didn't use -f to solve conflicts. gi files are not in python2-gobject2 anymore but in python2-gobject
Give what you have. To someone, it may be better than you dare to think.
Offline
wonder wrote:well, if is a problem with our gdm pam modules, tell me about it. on the other hand, don't try to investigate more about your empathy/accounts problem. It's already reported and i pasted the link, it's related to telepathy-mission-control not to empathy
As i wrote it above, the gdm-password pam file seems to consider that all user uid are >= 1000. That's probably the case when we use standard tools to create accounts, but it fails if we change the uid for some reason (for my own, my user account was 500 to be in sync with my NFS server...).
i just tried to replicate this. works fine if i change the uid in gdm-password. also i tried to list the username in gdm list by changing the minimal uid in /etc/login.defs and works fine as well(don't forget to kill accountsservice daemon.
Give what you have. To someone, it may be better than you dare to think.
Offline
i just tried to replicate this. works fine if i change the uid in gdm-password.
Well... It was my first idea. But, then, i've realized that a future update could overwrite this setting: that's why i've chosen to stick with the "normal" uid scheme and to change it on the nfs server side...
Offline
Anyway, I tried to login with autologin enabled and it just hangs up, gnome-shell doesn't start. After deletenig relevant lines in /etc/gdm/custom.conf it works.
Fixed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=658899
Offline
@wonder I said either (not both) breaks. Here's how.
$ yaourt -S gnome-shell-extension-system-monitor
...
$ system-monitor-applet-config
Traceback (most recent call last):
File "/usr/bin/system-monitor-applet-config", line 32, in <module>
from gi.repository import Gtk, Gio, Gdk
ImportError: No module named gi.repository
This extension expects python3 gi modules which comes with python-gobject. So, if I go ahead to install python-gobject (preceeded by removing the conflicted python2-gobject), gnome-shell-system-monitor appears to work, but all other packages which depend on python2-gobject, including gnome-tweak-tool and gedit, breaks. Hope I made it clear this time.
“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.”
Offline
As promised multiple times on forums, GNOME 3.2 beta2 was just released and guess what? We got it!
[...]
NVIDIA users be aware that xorg-server 1.11 from testing is incompatible with the current nvidia driver, even with IgnoreABI. You can switch to nouveau or add xf86-input-evdev xf86-input-synaptics xorg-server-common xorg-server to Ignorepkg.
Does Gnome 3.2 beta 2 need xorg-server 1.11?
If not, then does Gnome 3.2 beta 2 need anything else from [testing]? I'd rather not go with the testing repo just to try gnome beta, but I'd be willing to put my gnome config at risk. I'm running xfce most of the time lately, anyway.
Last edited by dhave (2011-09-14 03:49:35)
Offline
@dhave you can skip enabling testing for now
Give what you have. To someone, it may be better than you dare to think.
Offline
@ Thanos:
I had the same problem, and I solved it by uninstalling everything concerned with gnome, and then installing it again. Don't know where the problem was, but now I 'm falling in love with my new desktop!
May be I had autologin turned on,and it created some problems...but really have no idea.
Offline
Epiphany appears to require networkmanager to be running to work.
Previously I was getting
(epiphany:10633): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
which traced to ephy_network_manager_get_state ()
Starting the networkmanager service immediately fixes this issue.
Offline
@dmotd, sounds like a bug. now they are using dbus to detect if networkmanager is present or not. Care to report it?
Give what you have. To someone, it may be better than you dare to think.
Offline
@dhave you can skip enabling testing for now
Thanks, wonder. I went ahead and did the update to gnome-unstable. So far, so good. No probs with gdm.
Offline