Results 1 to 7 of 7

Thread: how do i trackdown a crash in y2controlcenter?

  1. #1

    Default how do i trackdown a crash in y2controlcenter?

    christopher@SCOOTER:/usr/lib/YaST2/bin> su -c /usr/lib/YaST2/bin/y2controlcenter
    Password:
    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
    Segmentation fault (core dumped)
    christopher@SCOOTER:/usr/lib/YaST2/bin>


  2. #2

    Default Re: how do i trackdown a crash in y2controlcenter?

    also when i use kdesu within kde, it dies silently on start

    christopher@SCOOTER:/usr/lib/YaST2/bin> kdesu /usr/lib/YaST2/bin/y2controlcenter
    christopher@SCOOTER:/usr/lib/YaST2/bin>

    this also happens from kde GUI as well, when i click on yast in Application menu, i get the kdesu dialog then the yast controlcenter dies silently on start

  3. #3
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,196
    Blog Entries
    15

    Default Re: how do i trackdown a crash in y2controlcenter?

    Hi
    Any particular reason your running it like that? The /sbin/yast2 script sets up environment variables etc. If you look at the desktop file is starts with;
    Code:
    /usr/bin/xdg-su -c /sbin/yast2
    Try your command with the xdg-su -c instead....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #4

    Default Re: how do i trackdown a crash in y2controlcenter?

    for troubleshooting i ran the app like normal and wanted to track down why yast crashed, so i tracked down how it worked, what is interesting running the individual yast utilities do not crash only the control center does

  5. #5
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,196
    Blog Entries
    15

    Default Re: how do i trackdown a crash in y2controlcenter?

    Quote Originally Posted by chrisf8262012 View Post
    for troubleshooting i ran the app like normal and wanted to track down why yast crashed, so i tracked down how it worked, what is interesting running the individual yast utilities do not crash only the control center does
    Hi
    No crashes here on GNOME with YaST control center... bug report time then
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  6. #6
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,448
    Blog Entries
    2

    Default Re: how do i trackdown a crash in y2controlcenter?

    Quote Originally Posted by chrisf8262012 View Post
    christopher@SCOOTER:/usr/lib/YaST2/bin> su -c /usr/lib/YaST2/bin/y2controlcenter
    Password:
    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
    Segmentation fault (core dumped)
    christopher@SCOOTER:/usr/lib/YaST2/bin>

    I see the same warning about wrong permissions displayed but instead of a segmentation fault am able to launch what is likely a read-only Yast2.

    I guess the real question might be why you're launching the y2controlcenter specifically instead of launching Yast2?
    For instance the following launches with no errors or warnings for me (after providing password)
    Code:
    su -c yast2
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,448
    Blog Entries
    2

    Default Re: how do i trackdown a crash in y2controlcenter?

    Quote Originally Posted by tsu2 View Post
    I see the same warning about wrong permissions displayed but instead of a segmentation fault am able to launch what is likely a read-only Yast2.

    I guess the real question might be why you're launching the y2controlcenter specifically instead of launching Yast2?
    For instance the following launches with no errors or warnings for me (after providing password)
    Code:
    su -c yast2
    TSU
    Slight modification,
    Only after I closed Yast2 did the warning write to stdout.

    But, as I described for me it's only a warning and did not prevent Yast2 from launching or functioning properly.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

Posting Permissions

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