Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#585534: zsh as login shell breaks parts of gnome-session

4 views
Skip to first unread message

henry atting

unread,
Jun 11, 2010, 9:40:02 AM6/11/10
to

Package: gnome-session
Version: 2.30.0-1
Severity: important

-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-session depends on:
ii gnome-panel 2.30.0-1 launcher and docking facility for
ii gnome-session-bin 2.30.0-1 The GNOME Session Manager - Minima
ii gnome-session-common 2.30.0-1 Common files for the GNOME session
ii gnome-settings-daemon 2.30.1-1 daemon handling the GNOME session
ii metacity 1:2.30.1-1 lightweight GTK+ window manager
ii nautilus 2.30.1-1 file manager and graphical shell f
ii policykit-1-gnome 0.96-2 GNOME authentication agent for Pol

Versions of packages gnome-session recommends:
ii gnome-power-manager 2.30.1-1 power management tool for the GNOM

Versions of packages gnome-session suggests:
pn desktop-base <none> (no description available)
ii gnome-keyring 2.30.1-2 GNOME keyring services (daemon and
pn gnome-user-guide <none> (no description available)

-- no debconf information
Package: gnome-session
Version: 2.30.0-1
Severity: important

When zsh used as login shell certain part of a gnome-session won't work.
All windows are attached to the left upper corner and only a root cursor
is displayed.
A test with other window managers eg. awesome revealed that this problem
solely occurrs with metacity as wm.

-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-session depends on:
ii gnome-panel 2.30.0-1 launcher and docking facility for
ii gnome-session-bin 2.30.0-1 The GNOME Session Manager - Minima
ii gnome-session-common 2.30.0-1 Common files for the GNOME session
ii gnome-settings-daemon 2.30.1-1 daemon handling the GNOME session
ii metacity 1:2.30.1-1 lightweight GTK+ window manager
ii nautilus 2.30.1-1 file manager and graphical shell f
ii policykit-1-gnome 0.96-2 GNOME authentication agent for Pol

Versions of packages gnome-session recommends:
ii gnome-power-manager 2.30.1-1 power management tool for the GNOM

Versions of packages gnome-session suggests:
pn desktop-base <none> (no description available)
ii gnome-keyring 2.30.1-2 GNOME keyring services (daemon and
pn gnome-user-guide <none> (no description available)

-- no debconf information

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Josselin Mouette

unread,
Jun 11, 2010, 9:40:03 AM6/11/10
to
Le vendredi 11 juin 2010 à 15:27 +0200, henry atting a écrit :
> When zsh used as login shell certain part of a gnome-session won't work.
> All windows are attached to the left upper corner and only a root cursor
> is displayed.
> A test with other window managers eg. awesome revealed that this problem
> solely occurrs with metacity as wm.

This sounds indeed like metacity not starting;
How did you test other window managers? By setting $WINDOW_MANAGER?

Do you have any relevant output in .xsession-errors?

Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “If you eat pasta without sauce, it is nothing
`- short of communism.” -- Marie

henry atting

unread,
Jun 11, 2010, 11:50:02 AM6/11/10
to
On Fr, Jun 11 2010, Josselin Mouette wrote:

> Le vendredi 11 juin 2010 à 15:27 +0200, henry atting a écrit :
>> When zsh used as login shell certain part of a gnome-session won't work.
>> All windows are attached to the left upper corner and only a root cursor
>> is displayed.
>> A test with other window managers eg. awesome revealed that this problem
>> solely occurrs with metacity as wm.
>
> This sounds indeed like metacity not starting;
> How did you test other window managers? By setting $WINDOW_MANAGER?

Mmh, I did not test them in a gnome-session. To choose I have these
lines in ~/.xinitirc

case "$1" in
urxvt) exec /usr/bin/urxvt;;
dwm) exec /usr/bin/dwm;;
awe) exec /usr/bin/awesome;;
gno) exec /usr/bin/gnome-session
esac


> Do you have any relevant output in .xsession-errors?

No, after quitting gnome-session .xsession-errors remains empty.

henry


--
http://literaturlatenight.de

Josselin Mouette

unread,
Jun 12, 2010, 2:10:01 AM6/12/10
to
Le vendredi 11 juin 2010 à 17:42 +0200, henry atting a écrit :
> > How did you test other window managers? By setting $WINDOW_MANAGER?
>
> Mmh, I did not test them in a gnome-session. To choose I have these
> lines in ~/.xinitirc
>
> case "$1" in
> urxvt) exec /usr/bin/urxvt;;
> dwm) exec /usr/bin/dwm;;
> awe) exec /usr/bin/awesome;;
> gno) exec /usr/bin/gnome-session
> esac
>
>
> > Do you have any relevant output in .xsession-errors?
>
> No, after quitting gnome-session .xsession-errors remains empty.

Sorry but I can’t reproduce that here. There must be something wrong in
a script of yours.

Cheers,
--
.''`. Josselin Mouette
: :' :

`. `' “If you behave this way because you are blackmailed by someone,
`- […] I will see what I can do for you.” -- Jörg Schilling

signature.asc

henry atting

unread,
Jun 12, 2010, 3:10:02 AM6/12/10
to
On Sa, Jun 12 2010, Josselin Mouette wrote:

> Le vendredi 11 juin 2010 à 17:42 +0200, henry atting a écrit :
>> > How did you test other window managers? By setting $WINDOW_MANAGER?
>>
>> Mmh, I did not test them in a gnome-session. To choose I have these
>> lines in ~/.xinitirc
>>
>> case "$1" in
>> urxvt) exec /usr/bin/urxvt;;
>> dwm) exec /usr/bin/dwm;;
>> awe) exec /usr/bin/awesome;;
>> gno) exec /usr/bin/gnome-session
>> esac
>>
>>
>> > Do you have any relevant output in .xsession-errors?
>>
>> No, after quitting gnome-session .xsession-errors remains empty.
>
> Sorry but I can’t reproduce that here. There must be something wrong in
> a script of yours.

Mmh, I don't see what script, normally I start with startx and an empty
.xinitrc.

Anyway, as far as I am concerned this bug can be closed, I switched back
to awesome again which works flawlessly.

Thanks a lot

0 new messages