Discussion:
Trouble starting yast2 from terminal
(too old to reply)
Robert Schweikert
2011-03-08 21:35:58 UTC
Permalink
Hi,

After upgrading to 11.4 via "zypper dup" I am unable to start "yast2"
from a terminal window. I am getting the following error:

**
GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed:
(connection->initialization_error == NULL)


I am logged into a GNOME session as regular user, then start a terminal
session, su, and then run "yast2"

I can produce the problem on 2 machines. This is a big annoyance on one
machine since I cannot start YaST from the slab menu as it does not
display (677900).

Any thoughts? Did the upgrade process miss a package?

I filed 677911


Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
Novell-IBM Software Integration Center LINUX
Tech Lead
***@novell.com
***@ca.ibm.com
781-464-8147

Novell
Making IT Work As One
Nelson Marques
2011-03-08 23:21:18 UTC
Permalink
Try:

xdg-su -c "/sbin/YaST2"


NM

On Tue, Mar 8, 2011 at 9:35 PM, Robert Schweikert
Post by Robert Schweikert
Hi,
After upgrading to 11.4 via "zypper dup" I am unable to start "yast2"
**
(connection->initialization_error == NULL)
I am logged into a GNOME session as regular user, then start a terminal
session, su, and then run "yast2"
I can produce the problem on 2 machines. This is a big annoyance on one
machine since I cannot start YaST from the slab menu as it does not
display (677900).
Any thoughts? Did the upgrade process miss a package?
I filed 677911
Robert
--
Robert Schweikert                           MAY THE SOURCE BE WITH YOU
Novell-IBM Software Integration Center                LINUX
Tech Lead
781-464-8147
Novell
Making IT Work As One
--
--
nelson marques
***@gmail.com
Robert Schweikert
2011-03-08 23:33:46 UTC
Permalink
Post by Nelson Marques
xdg-su -c "/sbin/YaST2"
Thanks that works. I'll add it as a work around to the bug.

Robert
Post by Nelson Marques
NM
On Tue, Mar 8, 2011 at 9:35 PM, Robert Schweikert
Post by Robert Schweikert
Hi,
After upgrading to 11.4 via "zypper dup" I am unable to start "yast2"
**
(connection->initialization_error == NULL)
I am logged into a GNOME session as regular user, then start a terminal
session, su, and then run "yast2"
I can produce the problem on 2 machines. This is a big annoyance on one
machine since I cannot start YaST from the slab menu as it does not
display (677900).
Any thoughts? Did the upgrade process miss a package?
I filed 677911
Robert
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
Novell-IBM Software Integration Center LINUX
Tech Lead
781-464-8147
Novell
Making IT Work As One
--
--
Robert Schweikert MAY THE SOURCE BE WITH YOU
Novell-IBM Software Integration Center LINUX
Tech Lead
***@novell.com
***@ca.ibm.com
781-464-8147

Novell
Making IT Work As One
Nelson Marques
2011-03-08 23:36:39 UTC
Permalink
On Tue, Mar 8, 2011 at 11:33 PM, Robert Schweikert
Post by Robert Schweikert
Post by Nelson Marques
xdg-su -c "/sbin/YaST2"
Thanks that works. I'll add it as a work around to the bug.
Robert,

The behavior you mentioned has been always around in 11.3 for me. Any
attempt like 'sudo YaST2' produced it... that was the only way I found
to start YaST2 from a command line ;)

Glad it helped. Peace,

NM
Post by Robert Schweikert
Robert
Post by Nelson Marques
NM
On Tue, Mar 8, 2011 at 9:35 PM, Robert Schweikert
Post by Robert Schweikert
Hi,
After upgrading to 11.4 via "zypper dup" I am unable to start "yast2"
**
(connection->initialization_error == NULL)
I am logged into a GNOME session as regular user, then start a terminal
session, su, and then run "yast2"
I can produce the problem on 2 machines. This is a big annoyance on one
machine since I cannot start YaST from the slab menu as it does not
display (677900).
Any thoughts? Did the upgrade process miss a package?
I filed 677911
Robert
--
Robert Schweikert                           MAY THE SOURCE BE WITH YOU
Novell-IBM Software Integration Center                LINUX
Tech Lead
781-464-8147
Novell
Making IT Work As One
--
--
Robert Schweikert                           MAY THE SOURCE BE WITH YOU
Novell-IBM Software Integration Center                LINUX
Tech Lead
781-464-8147
Novell
Making IT Work As One
--
--
nelson marques
***@gmail.com
Vincent Untz
2011-03-10 09:47:34 UTC
Permalink
Post by Robert Schweikert
I am logged into a GNOME session as regular user, then start a terminal
session, su, and then run "yast2"
Use "su -", not "su". I'm actively wondering if there's any reason to
keep the "su" default behavior around. It just keeps harming us again
and again.

(The crash itself is a known bug, filed upstream already, see
https://bugzilla.novell.com/show_bug.cgi?id=655751 and
https://bugzilla.gnome.org/show_bug.cgi?id=635694)

Vincent
--
Les gens heureux ne sont pas pressés.
Rajko M.
2011-03-14 03:18:59 UTC
Permalink
Post by Vincent Untz
Post by Robert Schweikert
I am logged into a GNOME session as regular user, then start a terminal
session, su, and then run "yast2"
Use "su -", not "su". I'm actively wondering if there's any reason to
keep the "su" default behavior around. It just keeps harming us again
and again.
It is just like keeping minefield in the house.
It strikes from time to time and makes you (us) busy with "bugs".
Post by Vincent Untz
Vincent
--
Regards,
Rajko
pistazienfresser (see profile)
2011-03-15 11:16:53 UTC
Permalink
To: opensuse-***@opensuse.org
CC: opensuse-***@opensuse.org
= http://lists.opensuse.org/opensuse-factory/2011-03/msg00298.html

Am 10/03/11 10:47, schrieb Vincent Untz:
[...]
Post by Vincent Untz
Use "su -", not "su". I'm actively wondering if there's any reason to
keep the "su" default behavior around. It just keeps harming us again
and again.
[...]
Post by Vincent Untz
Vincent
Hi Vincent, hi Frank, hello all,

I think this should at least be reflected in the documentation.
But there is used the su program without even mentioning the login shell
( --log/ -l/ -) option:

Reference > Chapter 21. Shell Basics > 21.4. Becoming Root > 21.4.1.
Using su
http://doc.opensuse.org/products/opensuse/openSUSE/opensuse-reference/cha.new.bash.html#sec.new.bash.root

I rate the hole reworking and expand the printed/book like manuals was a
great operation (that should be mentioned in the 'highlights' article of
11.4). But maybe it some background (like: su versus su- ; what are
gnomesu, kdesu, gksu, gksudo, xdg-su -c "[command]", ....like?) and
explanations could be done in the wiki (at least as an unstable/stage
version before including it/parts of it to the manuals)?

Compare also:
on the su/su - issue
http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/455279-after-zypper-dup-11-4-most-graphical-yast-modules-do-not-start-via-yast.html#post2302930
and following
http://forums.opensuse.org/english/other-forums/community-fun/opensuse-wiki-discussions/447159-updated-http-en-opensuse-org-sdb-alsa-update-need-review-approval.html#post2302873
and following

On the basics and concepts of security
http://lists.opensuse.org/opensuse-doc/2011-03/msg00001.html and following


Regards
Martin
(pistazienfresser)
--
- Martin Seidler
- openSUSE profile: https://users.opensuse.org/show/pistazienfresser
pistazienfresser (see profile)
2011-03-26 08:21:18 UTC
Permalink
Post by pistazienfresser (see profile)
= http://lists.opensuse.org/opensuse-factory/2011-03/msg00298.html
[...]
Post by Vincent Untz
Use "su -", not "su". I'm actively wondering if there's any reason to
keep the "su" default behavior around. It just keeps harming us again
and again.
[...]
Post by Vincent Untz
Vincent
Hi Vincent, hi Frank, hello all,
I think this should at least be reflected in the documentation.
But there is used the su program without even mentioning the login shell
[...]
Now filled as bugreport against the Documentation:
Novell's bugzilla:
Bug 682726 - Reference suggests only "su" instead of "su -"/su -l/su
--login "make the shell a login shell"
https://bugzilla.novell.com/show_bug.cgi?id=682726

Regards
Martin
--
- Martin Seidler
- openSUSE profile: https://users.opensuse.org/show/pistazienfresser
pistazienfresser (see profile)
2011-03-15 12:16:50 UTC
Permalink
Post by Vincent Untz
Post by Robert Schweikert
I am logged into a GNOME session as regular user, then start a terminal
session, su, and then run "yast2"
Use "su -", not "su". I'm actively wondering if there's any reason to
keep the "su" default behavior around. It just keeps harming us again
and again.
(The crash itself is a known bug, filed upstream already, see
https://bugzilla.novell.com/show_bug.cgi?id=655751 and
https://bugzilla.gnome.org/show_bug.cgi?id=635694)
Vincent
May this this behavior also be connected to that issue or should I file
a separate bugreport in the next days?:

For myself I would just do a complete new install of 11.4 GM but there
are at least two other users in that thread reporting that they are
having that problem after doing the zypper dup process (one from 11.3):

Thread: After zypper dup to 11.4 , most of the (graphical) YaST modules
do not start via YaST
http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/455279-after-zypper-dup-11-4-most-graphical-yast-modules-do-not-start-via-yast.html

Regards
Martin
(pistazienfresser)
--
- Martin Seidler
- openSUSE profile: https://users.opensuse.org/show/pistazienfresser
jdd
2011-03-15 14:30:15 UTC
Permalink
Post by Vincent Untz
Use "su -", not "su". I'm actively wondering if there's any reason to
keep the "su" default behavior around. It just keeps harming us again
and again.
there was a discussion, years ago, because the suse default was changed

may I quote the yast qt interface have no problem?

jdd
--
http://www.dodin.net
http://www.dailymotion.com/video/xgxog7_clip-l-ombre-et-la-lumiere-3-bad-pigeons_music

pistazienfresser (see profile)
2011-03-16 20:52:00 UTC
Permalink
Post by jdd
Post by Vincent Untz
Use "su -", not "su". I'm actively wondering if there's any reason to
keep the "su" default behavior around. It just keeps harming us again
and again.
there was a discussion, years ago, because the suse default was changed
Do not know if openSUSE should use another default than other
distributions. Maybe debugging the documentation and maybe updating it
with an explanation would be sufficient.
Post by jdd
may I quote the yast qt interface have no problem?
jdd
I have installed KDE and LXDE. In both the graphical yast is able to
start its modules. Also an user wrote in the forums that he was able to
use KDE as a workaround.

Regards
Martin
(pistazienfresser)
--
- Samsung X20 Pentium M 740 (1730 MHz) Intel 915GM 1400x1050
- openSUSE profile: https://users.opensuse.org/show/pistazienfresser
Continue reading on narkive:
Loading...