Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Yast qt version seg faults

  1. #1

    Default Yast qt version seg faults

    running "kdesu yast --qt" opens the request for password window but nothing happens

    running just "yast2" in Konsole produces
    /usr/sbin/yast2: line 440: 7556 Segmentation fault $y2ccbin $Y2UI_ARGS "$@"
    running a specific module produces
    >yast2 --qt sw_single
    YaST got signal 11 at file /usr/share/YaST2/modules/Wizard.rb:836
    /usr/sbin/yast2: line 440: 8430 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
    running "yast2 --qt" as root in Konsole works fine, the gtk version works fine

    This happened after my system got borked after an update and I fixed it by doing an upgrade from the 13.2 dvd. I had no choice as the system booted into a black screen and whatever msgs displayed couldn't be read, the grub screen did not display either

    Tried reinstalling all Yast and QT packages, running it as a different user and un-installing librpoxy1-config-kde4 (it was mentioned in a search result)

    running 13.2, KDE 4.14.3

    thanks,
    openSUSE Leap 42.1 x64, Plasma 5 & KDE 4.14.x, pretty current proprietary Nvidia drivers (self-compiled)

  2. #2

    Default Re: Yast qt version seg faults

    addendum - the section of Yast2 that ends on line 440

    Code:
     elif test $module != "menu" && other_tools_are_conflicting "$@" ; then    exit_code=1
    else
        # In case YaST has to be restarted, create this file
        # and exit. Script that creates the file should also
        # remove it itself.
        case "$module" in
        # special cases
        menu) REDO_FILE=/var/lib/YaST2/restart_menu ;;
        online_update) REDO_FILE=/var/lib/YaST2/selected_patches.ycp ;;
        # all other cases when YaST has to be restarted
        *) REDO_FILE=/var/lib/YaST2/restart_yast ;;
        esac
        snapshot_pre $module
        #  break out on errors, #343258
        while [ $exit_code = 0 ]; do
        $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
        exit_code=$?
        if [ -z "$REDO_FILE" -o ! -f "$REDO_FILE" ]; then
            break
        fi
    openSUSE Leap 42.1 x64, Plasma 5 & KDE 4.14.x, pretty current proprietary Nvidia drivers (self-compiled)

  3. #3
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Yast qt version seg faults

    On 2015-01-08 02:46, google01103 wrote:
    >
    > running "kdesu yast --qt" opens the request for password window but
    > nothing happens
    >
    > running just "yast2" in Konsole produces
    >> /usr/sbin/yast2: line 440: 7556 Segmentation fault $y2ccbin
    >> $Y2UI_ARGS "$@"


    As plain user? It should not work.

    > running "yast2 --qt" as root in Konsole works fine, the gtk version
    > works fine


    Then I see no problem >:-)


    > This happened after my system got borked after an update and I fixed it
    > by doing an upgrade from the 13.2 dvd. I had no choice as the system
    > booted into a black screen and whatever msgs displayed couldn't be read,
    > the grub screen did not display either
    >
    > Tried reinstalling all Yast and QT packages, running it as a different
    > user and un-installing librpoxy1-config-kde4 (it was mentioned in a
    > search result)


    Run this:

    Code:
    rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \
    %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \
    %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \
    | sort | cut --fields="2-" | tee rpmlist \
    | egrep -v "openSUSE.13\.2" | less -S
    And examine the results. Any entry is suspect of not belonging to 13.2.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  4. #4

    Default Re: Yast qt version seg faults

    Quote Originally Posted by robin_listas View Post
    On 2015-01-08 02:46, google01103 wrote:
    >
    > running "kdesu yast --qt" opens the request for password window but
    > nothing happens
    >
    > running just "yast2" in Konsole produces
    >> /usr/sbin/yast2: line 440: 7556 Segmentation fault $y2ccbin
    >> $Y2UI_ARGS "$@"


    As plain user? It should not work.
    Yes, it should.
    But it should show a warning that it will not show all entries when run as normal user, and then only show a few.

    It definitely shouldn't segfault...

    Regarding the problem:
    Try running "xauth -b" (as user) and then just quit by entering 'q'.

    If that doesn't help, please post the last lines of /var/log/YaST2/y2log after it segfaults:
    Code:
    sudo tail /var/log/YaST2/y2log
    Strange though that it would work as root (I suppose you mean you log in to the GUI as root, right?). This should rule out an installation problem.
    Maybe some graphics driver issue? (insufficient permissions perhaps)
    What does "glxinfo | grep render" say when running it as user? (you might have to install Mesa-demo-x to get output)
    Last edited by wolfi323; 08-Jan-2015 at 04:07.

  5. #5

    Default Re: Yast qt version seg faults

    Quote Originally Posted by wolfi323 View Post
    Yes, it should.
    But it should show a warning that it will not show all entries when run as normal user, and then only show a few.

    It definitely shouldn't segfault...

    Regarding the problem:
    Try running "xauth -b" (as user) and then just quit by entering 'q'.
    Code:
     xauth -b
    Attempting to break locks on authority file /home/smiley/.Xauthority
    Using authority file /home/smiley/.Xauthority

    Quote Originally Posted by wolfi323 View Post
    If that doesn't help, please post the last lines of /var/log/YaST2/y2log after it segfaults:
    Code:
    sudo tail /var/log/YaST2/y2log
    The tail is not from the "yast2" command based on time stamp


    Quote Originally Posted by wolfi323 View Post
    Strange though that it would work as root (I suppose you mean you log in to the GUI as root, right?). This should rule out an installation problem.
    No, I was running it in a root Konsole session and it works fine, BUT logging in as root and it also seg faults -


    Quote Originally Posted by wolfi323 View Post
    Maybe some graphics driver issue? (insufficient permissions perhaps)
    What does "glxinfo | grep render" say when running it as user? (you might have to install Mesa-demo-x to get output)
    Code:
    glxinfo | grep renderdirect rendering: Yes
    OpenGL renderer string: GeForce GT 430/PCIe/SSE2
        GL_KHR_debug, GL_KTX_buffer_region, GL_NVX_conditional_render, 
        GL_NV_blend_square, GL_NV_compute_program5, GL_NV_conditional_render, 
        GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 
        GL_KHR_debug, GL_KTX_buffer_region, GL_NVX_conditional_render, 
        GL_NV_blend_square, GL_NV_compute_program5, GL_NV_conditional_render, 
        GL_NV_parameter_buffer_object2, GL_NV_path_rendering, 
        GL_OES_element_index_uint, GL_OES_fbo_render_mipmap,
    openSUSE Leap 42.1 x64, Plasma 5 & KDE 4.14.x, pretty current proprietary Nvidia drivers (self-compiled)

  6. #6

    Default Re: Yast qt version seg faults

    Quote Originally Posted by google01103 View Post
    The tail is not from the "yast2" command based on time stamp
    So it crashes before it is even opening the log.

    No, I was running it in a root Konsole session and it works fine, BUT logging in as root and it also seg faults -
    So it works inside the _user_'s X session if you run it via "su -", but not with kdesu, right?

    Code:
    glxinfo | grep renderdirect rendering: Yes
    Looks ok. But if it doesn't work inside an X session running as root either, it's definitely not permissions related.

    One question: when it works, what widget style does it have? (you can best see that inside some module, how the checkboxes look like)

    This crash could be caused by a mismatch of Qt5 and libKF5Style5 versions, which would make each Qt5 application crash when trying to use KDE's styles (breeze, oxygen). Running it via "su -" might imply different settings (because of the different environment), and cause it to use the built-in "Fusion" style instead (and therefore not crash).

    Does uninstalling libKF5Style5 (and ignoring the dependencies) help?
    The main negative side-effect of this would just be that all Qt5/KF5 apps would use Fusion instead of Breeze or Oxygen, you don't have to fear breaking your system by trying that.
    Last edited by wolfi323; 08-Jan-2015 at 06:01.

  7. #7

    Default Re: Yast qt version seg faults

    Quote Originally Posted by wolfi323 View Post
    So it crashes before it is even opening the log.


    So it works inside the _user_'s X session if you run it via "su -", but not with kdesu, right?
    correct

    Quote Originally Posted by wolfi323 View Post
    Looks ok. But if it doesn't work inside an X session running as root either, it's definitely not permissions related.

    One question: when it works, what widget style does it have? (you can best see that inside some module, how the checkboxes look like)
    I run Oxygen
    Quote Originally Posted by wolfi323 View Post
    This crash could be caused by a mismatch of Qt5 and libKF5Style5 versions, which would make each Qt5 application crash when trying to use KDE's styles (breeze, oxygen). Running it via "su -" might imply different settings (because of the different environment), and cause it to use the built-in "Fusion" style instead (and therefore not crash).

    Does uninstalling libKF5Style5 (and ignoring the dependencies) help?
    The main negative side-effect of this would just be that all Qt5/KF5 apps would use Fusion instead of Breeze or Oxygen, you don't have to fear breaking your system by trying that.
    Confused - I'm running KDE4 not 5
    openSUSE Leap 42.1 x64, Plasma 5 & KDE 4.14.x, pretty current proprietary Nvidia drivers (self-compiled)

  8. #8

    Default Re: Yast qt version seg faults

    Quote Originally Posted by google01103 View Post
    I run Oxygen
    In YaST?
    I mean the widget style btw, not the window decorations.

    Confused - I'm running KDE4 not 5
    But YaST is using Qt5. And if libKF5Style5 is installed, it will try to use Breeze by default even when running on KDE4.

    If you don't have libKF5Style5 installed at all, this is probably not the problem, of course.

  9. #9

    Default Re: Yast qt version seg faults

    Originally Posted by wolfi323
    This crash could be caused by a mismatch of Qt5 and libKF5Style5 versions, which would make each Qt5 application crash when trying to use KDE's styles (breeze, oxygen). Running it via "su -" might imply different settings (because of the different environment), and cause it to use the built-in "Fusion" style instead (and therefore not crash).

    Does uninstalling libKF5Style5 (and ignoring the dependencies) help?
    The main negative side-effect of this would just be that all Qt5/KF5 apps would use Fusion instead of Breeze or Oxygen, you don't have to fear breaking your system by trying that.


    Yup - that's the issue, so I should lock libKF5Style5 ? strange didn't have this until I un-borked the system, of course this isn't my only new issue from the un-borking (you might find a new post on the KDE5 thread if I can't figure it out
    )

    thanks (a bunch)
    openSUSE Leap 42.1 x64, Plasma 5 & KDE 4.14.x, pretty current proprietary Nvidia drivers (self-compiled)

  10. #10

    Default Re: Yast qt version seg faults

    Quote Originally Posted by google01103 View Post
    Yup - that's the issue, so I should lock libKF5Style5 ?
    No, just install the correct one that is built against the Qt5 you have installed.

    IOW, if you have Qt5 5.4.0 from the KDE:Qt5 repo, you need libKF5Style5 from KDE:Frameworks5.
    If you have Qt5 5.3.2 from the standard 13.2 repos, you also need the libKF5Style5 from the standard 13.2 repos.

    libKF5Style5 (i.e. KDE's Qt5 platform plugin) uses some private internal Qt APIs that have changed between 5.3 and 5.4.
    Other desktop plugins (lxqt-libqtplugin e.g.) have the same "issue".

    The reason why YaST crashed when running via kdesu or in root's KDE session, but not when run via "su -", is that Qt5 checks via a certain environment variable on which desktop it is running and loads the corresponding plugin then. If you run it in KDE (doesn't matter whether it's KDE4 or Plasma5) this variable is set to "KDE" and so the KDE platform plugin (libKF5Style5) is loaded to get KDE's settings etc.
    If you run "su -" (this is done by the root Konsole session, have a look at the profile...), the environment gets reset completely, so Qt5 cannot detect that it is running inside KDE and doesn't load that plugin.

    strange didn't have this until I un-borked the system, of course this isn't my only new issue from the un-borking (you might find a new post on the KDE5 thread if I can't figure it out )
    If another issue was Plasma5 or all other KF5 applications crashing, then it was most likely caused by the same problem, and should be fixed now...
    Last edited by wolfi323; 08-Jan-2015 at 07:36.

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •