YaST Partitioner does not start

flightman · June 4, 2011, 5:40pm

Hi all,

I have a problem with YaST Partitioner. When I launch it, a window opens, a dialog (to confirm that I know what I am doing) pop-ups, I choose “Yes”, the application starts to initialize, and after 0.5-1s the window is closed without any error message. Does anybody know how to at least find out what is wrong? … or how to launch it from command line to get some output?

fli.
OpenSUSE 11.3

jdmcdaniel3 · June 4, 2011, 5:55pm

Hi all,

I have a problem with YaST Partitioner. When I launch it, a window opens, a dialog (to confirm that I know what I am doing) pop-ups, I choose “Yes”, the application starts to initialize, and after 0.5-1s the window is closed without any error message. Does anybody know how to at least find out what is wrong? … or how to launch it from command line to get some output?

fli.
OpenSUSE 11.3
If the program used to work, but now it does not, it could be corrupted in some way. You could install gparted from the contrib repository and see if that helps. Is it possible you have a new partition that the partitioner does not understand? For instance I used to have issues with USB 3 drives in openSUSE 11.3 until I updated the kernel. You could also do the same thing by installing openSUSE 11.4.

Thank You,

martin_helm · June 4, 2011, 6:40pm

flightman wrote:

>
> Hi all,
>
> I have a problem with YaST Partitioner. When I launch it, a window
> opens, a dialog (to confirm that I know what I am doing) pop-ups, I
> choose “Yes”, the application starts to initialize, and after 0.5-1s the
> window is closed without any error message. Does anybody know how to at
> least find out what is wrong? … or how to launch it from command line
> to get some output?
>
> fli.
> OpenSUSE 11.3
>
You could do a test and see if you get a usable error message by running the
yast module from the command line


su -
yast2 disk

martin_helm · June 4, 2011, 6:43pm

Just if you are interested, to see which modules you can directly run


/sbin/yast2 -l # or /sbin/yast -l for the ncurses, should give the same

you do not need to be root to show that list.

flightman · June 5, 2011, 2:34pm

Just an update, here is the output from command line:

yast2 disk
process 19099: arguments to dbus_message_iter_append_basic() were incorrect, assertion "*bool_p == 0 || *bool_p == 1" failed in file dbus-message.c line 2541.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
YaST got signal 6 at YCP file Storage.ycp:3
/sbin/yast2: řádek 399: 19099 Neúspěšně ukončen (SIGABRT)        $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

martin_helm · June 5, 2011, 2:53pm

flightman wrote:

>
> Just an update, here is the output from command line:
>
>
> Code:
> --------------------
> yast2 disk
> process 19099: arguments to dbus_message_iter_append_basic() were
> incorrect, assertion “*bool_p == 0 || *bool_p == 1” failed in file
> dbus-message.c line 2541. This is normally a bug in some application
> using the D-Bus library. D-Bus not built with -rdynamic so unable to
> print a backtrace YaST got signal 6 at YCP file Storage.ycp:3
> /sbin/yast2: řádek 399: 19099 Neúspěšně ukončen (SIGABRT)
> $ybindir/y2base $module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS
> --------------------
>
Unfortunately this does not really tell me much. Did you use “su -”? The “-”
is essential. Otherwise hopefully someone else has an idea.

As a workaround what about using the ncurses interface of yast for the
moment, just call “yast disk” instead of “yast2 disk” in a terminal?

robin_listas · June 5, 2011, 3:20pm

On 2011-06-05 14:53, martin_helm wrote:

> Unfortunately this does not really tell me much. Did you use “su -”? The “-”
> is essential. Otherwise hopefully someone else has an idea.

Dunno. Recent updates?

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

flightman · June 8, 2011, 2:47pm

After update to 11.4, everything works.

jdmcdaniel3 · June 8, 2011, 11:54pm

After update to 11.4, everything works.
So good to hear you were able to solve your problem by installing/upgrading to openSUSE 11.4. Thanks for letting us know of your success.

Thank You,