Results 1 to 3 of 3

Thread: Yast2 package manager (Qt) doesn't save settings

  1. #1

    Default Yast2 package manager (Qt) doesn't save settings

    On openSUSE 11.4 (and if I recall, even on 11.3), the Yast2 package manager (Qt version) does not persistently save settings upon exiting. For example, if I enable "Cleanup deleted packages" and disable "Show -devel packages", they are reset upon exiting and restarting the package manager. This was not the case under the GNOME version of Yast2's package manager.


    Here is what it looks like before I exit, either with "Accept" or "Save and exit":



    Here is what it looks like after I run the package manager again:




    yast2-control-center-2.20.2-1.3.1.x86_64
    yast2-control-center-qt-2.20.2-1.3.1.x86_64

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

    Default Re: Yast2 package manager (Qt) doesn't save settings

    On 2011-10-24 16:56, flansuse wrote:
    >
    > On openSUSE 11.4 (and if I recall, even on 11.3), the Yast2 package
    > manager (Qt version) does not persistently save settings upon exiting.
    > For example, if I enable *"Cleanup deleted packages"* and disable *"Show
    > -devel packages"*, they are reset upon exiting and restarting the
    > package manager. This was not the case under the GNOME version of
    > Yast2's package manager.


    Then report as bug in bugzilla.

    --
    Cheers / Saludos,

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

  3. #3

    Default Re: Yast2 package manager (Qt) doesn't save settings

    Quote Originally Posted by robin_listas View Post
    Then report as bug in bugzilla.
    I should have wrote it in my initial post, but this is more of an "anyone else?" question before I submit a bug report. The last two times I reported a bug about openSUSE on Novell's Bugzilla: one was not picked up until recently (won't matter anyone, since 11.3 is losing support upon 12.1's release), and the other bug was eventually patched much, much later to the point that it didn't really matter anymore, due to the 18-month support cycle.

    That's why I favor forums first, then bug reports second. Someone might be familiar with an issue and know a quick fix or workaround.

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
  •