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

Thread: GNOME finally broken

  1. #1

    Default GNOME finally broken

    Now I cannot ignore it anymore. GNOME got broken for me and I have no idea why or when.

    I got used to GNOME because of its simplicity yet some few couple of visual effects. KDE is just too much for me.

    First, this exact issue got worse: I open any file with any GNOME application (gedit, the pdf viewer however it's called, etc) then reboot. This now *always* causes to generate a new recently-used.xbel.xxxxxx (being the x's any alphanumeric combination, capitals included) aside previous ones and the original recently-used.xbel. ALWAYS. Open any file -no modifying even needed- then reboot system. That's all!
    For now I left "Usage and History" disabled in Privacy settings then shutdown. I'm no longer at the place until tomorrow.
    And don't give me "change to LXDE" or similar because all of them are GTK+3 based DEs thus using the same infamous recently-used.xbel thing.

    Second, prior to realizing the above issue I did a zypper up then rebooted. Did stuff, then shutdown PC. When wanting to shutdown or reboot, in the shutdown menu -with options shutdown, reboot, suspend- now also appears the checkbox "Install pending updates". How is this possible!? I just did a system update!

    And please don't throw me the "make a new user" stuff because that's no option for me

  2. #2
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,317

    Default Re: GNOME finally broken

    On Thu, 11 Jan 2018 01:46:02 +0000, F style wrote:

    > And please don't throw me the "make a new user" stuff because that's no
    > option for me


    That's an option for troubleshooting - I'd say give that a try and see if
    that user works OK. That helps narrow down whether it's a software issue
    or a config issue.

    That's a useful troubleshooting step, and I'd highly recommend it as a
    first step in diagnosing what's going wrong.

    Jim
    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  3. #3

    Default Re: GNOME finally broken

    Mother******.........................

    Created a new user, doesn't happen the problem.

    But worse is, even with the History disabled it still happens in my user!

    I try to recall it happened since kernel update to 4.4.103?

    Any help please?
    I already know almost no one cares about GNOME because they have KDE, but hey, there are some of us that still struggle with GNOME!

  4. #4

    Default Re: GNOME finally broken

    If I logout first before shutting down/rebooting problem doesn't happen, just the original recently-used.xbel remains. But if I shutdown directly problem happens. This is definitely a wrong behavior that I did not have before.

    Also, if creating a new text file instead of opening one, by just opening gedit and not saving anything, problem doesn't happen.

  5. #5
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,317

    Default Re: GNOME finally broken

    On Thu, 11 Jan 2018 16:06:02 +0000, F style wrote:

    > Created a new user, doesn't happen the problem.
    >
    > But worse is, even with the History disabled it still happens in my
    > user!
    >
    > I try to recall it happened since kernel update to 4.4.103?
    >
    > Any help please?
    > I already know almost no one cares about GNOME because they have KDE,
    > but hey, there are some of us that still struggle with GNOME!


    I use GNOME, but I don't have issues, either (but I don't care about
    document history - I find it useful).

    But if it doesn't happen with the new user, then it's not the kernel
    update - it's something in the user's GNOME configuration settings. I'd
    probably use:

    gconftool-2 --dump /

    As both users and then compare the outputs to see what's different.

    Jim
    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  6. #6
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,317

    Default Re: GNOME finally broken

    On Thu, 11 Jan 2018 16:56:02 +0000, F style wrote:

    > If I logout first before shutting down/rebooting problem doesn't happen,
    > just the original recently-used.xbel remains. But if I shutdown directly
    > problem happens. This is definitely a wrong behavior that I did not have
    > before.


    That sounds like a bug. You should log it at bugzilla.opensuse.org.



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  7. #7

    Default Re: GNOME finally broken

    Checked /var/log/zypp/history file. Out of probably concerning updates:

    On Dec 8 2017 gnome version got updated from 3.20.1 to 3.20.2.
    On Jan 3 2018 kernel got updated from 4.4-92 to 4.4-103, and evince and nautilus-evince got updated as well.
    Yesterday kernel got updated to 4.4-104, the meltdown/spectre update.
    No gedit updates...

    Truth to be told I cannot tell at all whether problem was already there prior to yesterday's update; I had deleted all recently-used.xbel files and never opened gedit nor evince at all until yesterday after the update. But I can remember I didn't have the problem during all or almost all December 2017 in general.
    Think a kernel update could really influence over GNOME stuff?

    @hendersj:
    You don't care about document history, so you probably didn't actually test. Not complaining, just trying to reason.
    Also, created the user but forgot to test intensively. I just posted what I supposed. Already deleted the user.
    By the way, do you know why I always ask for others to please file the bugs? Because my user has been banned from bugzilla for a while already. Not going to enter in details.

  8. #8

    Default Re: GNOME finally broken

    Noticed something else.

    Long before the problem, I did see one behavior though: scenario where there are no recently-used.xbel files at all initially. Open a file with gedit or evince. A recently-used.xbel is created. I delete it, then reboot. After reboot the file has appeared again, though if deleting it and rebooting again it does not appear after reboot this time.

    Now, starting with same scenario with no initial xbel files, open a file with gedit or evince, xbel file gets generated, I log out then log in back, delete xbel file, reboot, and this time xbel file has not appeared again. I'll never know if this would have worked as well before...

    Still, any help or ideas?

  9. #9
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,317

    Default Re: GNOME finally broken

    On Thu, 11 Jan 2018 17:56:01 +0000, F style wrote:

    > You don't care about document history, so you probably didn't actually
    > test. Not complaining, just trying to reason.


    You're right, I didn't test - I gave you a solid way to determine what
    the problem was and how you might go about getting it addressed.

    What you do with that information is ultimately up to you. I can use my
    decades of experience in troubleshooting problems to guide you, but you
    need to do some of the lifting here. You can reproduce the problem at
    will - so there's no need for me to.

    A kernel update *would not* affect GNOME. I've suggested how you can get
    this addressed - instead of taking random guesses that it's a kernel
    update that's causing you the problem, follow my suggestions and you'll
    narrow the problem down appropriately.

    Root cause analysis - break the problem into smaller parts, identify
    which part isn't working, and divide again if necessary. Taking random
    shots at parts of the system that have no relevance isn't going to get
    you to a solution - but it will get you to frustration.

    Jim
    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  10. #10

    Default Re: GNOME finally broken

    And how can I *effectively* create a new test user and then delete it after tests the perfect way? I.e., test user leaving absolute no trace after being deleted, as if never had existed.

    This **** lap rig may be not exactly mine, but it's the one that I was assigned and the one I better use at part time job at place. Hope you can understand...

Page 1 of 2 12 LastLast

Posting Permissions

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