Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 48

Thread: Plasma crashes - I think - when resizing desktop widget

  1. #21
    Join Date
    Jan 2009
    Location
    Chesterfield Township, MI USA
    Posts
    82

    Default Re: Plasma crashes - I think - when resizing desktop widget

    Quote Originally Posted by gogalthorp View Post
    Should not have to assuming ALL are pointing to the same version. Mixed version repos will cause problems

    show zypper lr -d

    Note you never said if any other widget shows the problem. I suspect something is broken with it and your current plasma since it also breaks for a different user.
    I didn't try another widget till now. I just tried to resize two other widgets with no problem. I neglected to say that I opened an issue with the Git Hub link provided in a previous post. Still waiting to hear back.

  2. #22
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,140

    Default Re: Plasma crashes - I think - when resizing desktop widget

    Taking your repository list from post #20:

    All looks OK there, assuming that #1 (AMDGPU) is either the correct version or version agnostic. If they were the only repositories active when you upgraded to 15.1 then I wouldn't expect any problems.

    Leap 15.0 was fully up to date immediately prior to your upgrade? The 15.1 system is fully up to date now? If for example you attempt another "zypper dup" zypper reports "Nothing to do".


    Looking at the fragments of logs from post #18:

    I don't think there's much there in this instance that helps. I see nothing that directly implicates the widget and/or plasma crashing.

    You could perhaps try to get more relevant data from the journal by:

    1) Create a new test user - this will have all default KDE settings.
    2) Add the "Simple Weather" plasmoid and configure a location; *don't* at this stage resize the plasmoid.
    3) Switch to a virtual terminal (Ctrl-Alt-F2)
    4) Login as your normal user.
    5) Start real time journal output, entering root password as required.
    Code:
     sudo journalctl -f
    6) Switch back to the Graphics Desktop (Ctrl-Alt-F7)
    7) Make a note of the system time, then resize the Simple Weather plasmoid.

    Plasma now crashes? Yes?

    8) Switch to the virtual terminal again (Ctrl-Alt-F2)

    Look to see what has been logged after the time you noted in step 7.


    Re the bug report you posted against the Simple Weather widget:

    Probably a good idea to add the kde/qt versions you're running - start the (KDE) "Info Centre" and from "About System" use the "Copy to clipboard" button.


    You asked in post #11 "Nobody but me ..." - Whilst it may seem unlikely, that is actually a distinct possibility. 5.1 is quite new, and looking at https://store.kde.org/p/1287571/ the download count is only (at the time of this post) 1443.

    What would have helped is if another forum member running 15.1 was prepared to try the plasmoid to see if they could replicate the issue you have. - Unfortunately, it has to be said, your earlier tone of posting probably discouraged others from helping. Please remember, we're all end users, who try to assist each other.
    Regards, Paul

    Tumbleweed (Snapshot: 20190716) KDE Plasma 5
    Leap 15.0 KDE Plasma 5
    [Non-Tumbling Tumblweed (20150508) KDE 4 - Resurrected]

  3. #23
    Join Date
    Jan 2009
    Location
    Chesterfield Township, MI USA
    Posts
    82

    Default Re: Plasma crashes - I think - when resizing desktop widget

    Quote Originally Posted by tannington View Post
    Taking your repository list from post #20:

    All looks OK there, assuming that #1 (AMDGPU) is either the correct version or version agnostic. If they were the only repositories active when you upgraded to 15.1 then I wouldn't expect any problems.

    Leap 15.0 was fully up to date immediately prior to your upgrade? The 15.1 system is fully up to date now? If for example you attempt another "zypper dup" zypper reports "Nothing to do".


    Looking at the fragments of logs from post #18:

    I don't think there's much there in this instance that helps. I see nothing that directly implicates the widget and/or plasma crashing.

    You could perhaps try to get more relevant data from the journal by:

    1) Create a new test user - this will have all default KDE settings.
    2) Add the "Simple Weather" plasmoid and configure a location; *don't* at this stage resize the plasmoid.
    3) Switch to a virtual terminal (Ctrl-Alt-F2)
    4) Login as your normal user.
    5) Start real time journal output, entering root password as required.
    Code:
     sudo journalctl -f
    6) Switch back to the Graphics Desktop (Ctrl-Alt-F7)
    7) Make a note of the system time, then resize the Simple Weather plasmoid.

    Plasma now crashes? Yes?

    8) Switch to the virtual terminal again (Ctrl-Alt-F2)

    Look to see what has been logged after the time you noted in step 7.


    Re the bug report you posted against the Simple Weather widget:

    Probably a good idea to add the kde/qt versions you're running - start the (KDE) "Info Centre" and from "About System" use the "Copy to clipboard" button.


    You asked in post #11 "Nobody but me ..." - Whilst it may seem unlikely, that is actually a distinct possibility. 5.1 is quite new, and looking at https://store.kde.org/p/1287571/ the download count is only (at the time of this post) 1443.

    What would have helped is if another forum member running 15.1 was prepared to try the plasmoid to see if they could replicate the issue you have. - Unfortunately, it has to be said, your earlier tone of posting probably discouraged others from helping. Please remember, we're all end users, who try to assist each other.
    I will do as you say, BUT let it be known that I did this once before. It's time consuming and I would rather not repeat things as that will ****ing frustrate me even more. Here's a thought: Can a few of you get together and come up with a plan that you all can agree on and present it to me to follow? Obviously this is not a quick fix, and I will get so frustrated with all the fake help that I will just do a fresh install. Doing your repeated laundry list now.

  4. #24
    Join Date
    Jan 2009
    Location
    Chesterfield Township, MI USA
    Posts
    82

    Arrow Re: Plasma crashes - I think - when resizing desktop widget

    Quote Originally Posted by tannington View Post
    Taking your repository list from post #20:

    All looks OK there, assuming that #1 (AMDGPU) is either the correct version or version agnostic. If they were the only repositories active when you upgraded to 15.1 then I wouldn't expect any problems.

    Leap 15.0 was fully up to date immediately prior to your upgrade? The 15.1 system is fully up to date now? If for example you attempt another "zypper dup" zypper reports "Nothing to do".


    Looking at the fragments of logs from post #18:

    I don't think there's much there in this instance that helps. I see nothing that directly implicates the widget and/or plasma crashing.

    You could perhaps try to get more relevant data from the journal by:

    1) Create a new test user - this will have all default KDE settings.
    2) Add the "Simple Weather" plasmoid and configure a location; *don't* at this stage resize the plasmoid.
    3) Switch to a virtual terminal (Ctrl-Alt-F2)
    4) Login as your normal user.
    5) Start real time journal output, entering root password as required.
    Code:
     sudo journalctl -f
    6) Switch back to the Graphics Desktop (Ctrl-Alt-F7)
    7) Make a note of the system time, then resize the Simple Weather plasmoid.

    Plasma now crashes? Yes?

    8) Switch to the virtual terminal again (Ctrl-Alt-F2)

    Look to see what has been logged after the time you noted in step 7.


    Re the bug report you posted against the Simple Weather widget:

    Probably a good idea to add the kde/qt versions you're running - start the (KDE) "Info Centre" and from "About System" use the "Copy to clipboard" button.


    You asked in post #11 "Nobody but me ..." - Whilst it may seem unlikely, that is actually a distinct possibility. 5.1 is quite new, and looking at https://store.kde.org/p/1287571/ the download count is only (at the time of this post) 1443.

    What would have helped is if another forum member running 15.1 was prepared to try the plasmoid to see if they could replicate the issue you have. - Unfortunately, it has to be said, your earlier tone of posting probably discouraged others from helping. Please remember, we're all end users, who try to assist each other.
    I modified the command. I used sudo journalct | tail -n 75 >/home/test/journal.txt and copied the contents of journal.txt here:
    Code:
    Jun 17 18:37:38 Enterprise systemd[21039]: Reached target Sockets.Jun 17 18:37:38 Enterprise systemd[21039]: Reached target Basic System.
    Jun 17 18:37:38 Enterprise systemd[21039]: Reached target Default.
    Jun 17 18:37:38 Enterprise systemd[21039]: Startup finished in 113ms.
    Jun 17 18:37:38 Enterprise systemd[1]: Started User Manager for UID 1000.
    Jun 17 18:37:38 Enterprise login[21037]: pam_unix(login:session): session opened for user trekjunky by LOGIN(uid=0)
    Jun 17 18:37:38 Enterprise login[21037]: LOGIN ON tty2 BY trekjunky
    Jun 17 18:37:56 Enterprise login[21037]: pam_unix(login:session): session closed for user trekjunky
    Jun 17 18:37:56 Enterprise systemd[1]: getty@tty2.service: Service has no hold-off time (RestartSec=0), scheduling restart.
    Jun 17 18:37:56 Enterprise systemd[1]: Stopped Getty on tty2.
    Jun 17 18:37:56 Enterprise systemd[1]: Started Getty on tty2.
    Jun 17 18:37:56 Enterprise systemd-logind[1221]: Session 61 logged out. Waiting for processes to exit.
    Jun 17 18:37:56 Enterprise systemd-logind[1221]: Removed session 61.
    Jun 17 18:37:56 Enterprise systemd[1]: Stopping User Manager for UID 1000...
    Jun 17 18:37:56 Enterprise systemd[21039]: Stopped target Default.
    Jun 17 18:37:56 Enterprise systemd[21039]: Stopped target Basic System.
    Jun 17 18:37:56 Enterprise systemd[21039]: Stopped target Timers.
    Jun 17 18:37:56 Enterprise systemd[21039]: Stopped target Paths.
    Jun 17 18:37:56 Enterprise systemd[21039]: Stopped target Sockets.
    Jun 17 18:37:56 Enterprise systemd[21039]: Closed D-Bus User Message Bus Socket.
    Jun 17 18:37:56 Enterprise systemd[21039]: Reached target Shutdown.
    Jun 17 18:37:56 Enterprise systemd[21039]: Starting Exit the Session...
    Jun 17 18:37:56 Enterprise systemd[21039]: Received SIGRTMIN+24 from PID 21099 (kill).
    Jun 17 18:37:56 Enterprise systemd[21040]: pam_unix(systemd-user:session): session closed for user trekjunky
    Jun 17 18:37:56 Enterprise systemd[1]: Stopped User Manager for UID 1000.
    Jun 17 18:37:56 Enterprise org_kde_powerdevil[19921]: powerdevil: ACTIVE SESSION PATH CHANGED: "/"
    Jun 17 18:37:56 Enterprise org_kde_powerdevil[19921]: powerdevil: Switched to inactive session - leaving unchanged
    Jun 17 18:37:56 Enterprise systemd[1]: Removed slice User Slice of trekjunky.
    Jun 17 18:38:01 Enterprise systemd[1]: Created slice User Slice of root.
    Jun 17 18:38:01 Enterprise systemd[1]: Starting User Manager for UID 0...
    Jun 17 18:38:01 Enterprise systemd-logind[1221]: New session 62 of user root.
    Jun 17 18:38:01 Enterprise systemd[1]: Started Session 62 of user root.
    Jun 17 18:38:01 Enterprise systemd[21100]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
    Jun 17 18:38:01 Enterprise org_kde_powerdevil[19921]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_362"
    Jun 17 18:38:01 Enterprise org_kde_powerdevil[19921]: powerdevil: Current session is now inactive
    Jun 17 18:38:01 Enterprise systemd[21100]: Starting D-Bus User Message Bus Socket.
    Jun 17 18:38:01 Enterprise systemd[21100]: Reached target Timers.
    Jun 17 18:38:01 Enterprise systemd[21100]: Reached target Paths.
    Jun 17 18:38:01 Enterprise systemd[21100]: Listening on D-Bus User Message Bus Socket.
    Jun 17 18:38:01 Enterprise systemd[21100]: Reached target Sockets.
    Jun 17 18:38:01 Enterprise systemd[21100]: Reached target Basic System.
    Jun 17 18:38:01 Enterprise systemd[21100]: Reached target Default.
    Jun 17 18:38:01 Enterprise systemd[21100]: Startup finished in 93ms.
    Jun 17 18:38:01 Enterprise systemd[1]: Started User Manager for UID 0.
    Jun 17 18:38:01 Enterprise login[21098]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
    Jun 17 18:38:01 Enterprise login[21098]: ROOT LOGIN ON tty2
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_359"
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: Current session is now active
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: Can't contact ck
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: We are now into activity  "e6f6527b-7bc0-4199-b9a1-5a4a903059ee"
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: () ()
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: () ()
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: No batteries found, loading AC
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: Activity is not forcing a profile
    Jun 17 18:38:15 Enterprise org_kde_powerdevil[19921]: powerdevil: The profile  "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, or to a configuration problem, or simply the action is not supported
    Jun 17 18:38:16 Enterprise kcminit[21167]: Initializing  "kcm_input" :  "kcminit_mouse"
    Jun 17 18:38:16 Enterprise kcminit[21167]: kcm_input: Using X11 backend
    Jun 17 18:38:16 Enterprise kcminit[21171]: Initializing  "kcm_input" :  "kcminit_mouse"
    Jun 17 18:38:16 Enterprise kcminit[21171]: kcm_input: Using X11 backend
    Jun 17 18:38:16 Enterprise kcminit[21173]: Initializing  "kcm_input" :  "kcminit_mouse"
    Jun 17 18:38:16 Enterprise kcminit[21173]: kcm_input: Using X11 backend
    Jun 17 18:38:16 Enterprise kwin_x11[19826]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36017, resource id: 54525956, major code: 18 (ChangeProperty), minor code: 0
    Jun 17 18:38:16 Enterprise kcminit[21167]: QFileSystemWatcher::removePaths: list is empty
    Jun 17 18:38:16 Enterprise kcminit[21167]: QFileSystemWatcher::removePaths: list is empty
    Jun 17 18:38:16 Enterprise kwin_x11[19826]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36407, resource id: 58720260, major code: 18 (ChangeProperty), minor code: 0
    Jun 17 18:38:16 Enterprise kcminit[21171]: QFileSystemWatcher::removePaths: list is empty
    Jun 17 18:38:16 Enterprise kcminit[21171]: QFileSystemWatcher::removePaths: list is empty
    Jun 17 18:38:16 Enterprise kwin_x11[19826]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36411, resource id: 60817412, major code: 18 (ChangeProperty), minor code: 0
    Jun 17 18:38:16 Enterprise kcminit[21173]: QFileSystemWatcher::removePaths: list is empty
    Jun 17 18:38:16 Enterprise kcminit[21173]: QFileSystemWatcher::removePaths: list is empty
    Jun 17 18:38:24 Enterprise kdeinit5[19793]: Service  "org.kde.StatusNotifierHost-19832" unregistered
    Jun 17 18:38:24 Enterprise kwin_x11[19826]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 37232, resource id: 35651602, major code: 15 (QueryTree), minor code: 0
    Jun 17 18:38:24 Enterprise kwin_x11[19826]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 37254, resource id: 35651640, major code: 15 (QueryTree), minor code: 0
    Jun 17 18:38:28 Enterprise org_kde_powerdevil[19921]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_362"
    Jun 17 18:38:28 Enterprise org_kde_powerdevil[19921]: powerdevil: Current session is now inactive
    A

  5. #25
    Join Date
    Jan 2009
    Location
    Chesterfield Township, MI USA
    Posts
    82

    Default Re: Plasma crashes - I think - when resizing desktop widget

    Well. I ran the suggested updates and guess what? It required a reboot and it broke. I couldn't boot, so the quick fix was to do a fresh install from DVD. I wonder how many times my system will break RIGHT after a suggested update? It must be the 7th time now. I'm seeing a pattern of hate. ANYWAY, my problem with the widget crashing KDE is still a problem. I wonder why others don't have a problem, yet I do? I have problem after problem. TOO ****ING MANY to be chance. And you wonder why I call you hateful jerks!!!! Maybe you aren't the ones programming the updates, but you support what they do to me, so you're hateful jerks. No real help is another hateful clue to your agenda. I see you helping dozens of others within one or two tries. The difference between them and me is you know or can find out exactly what is wrong and tell me how to fix it, but you're so hateful, you leave me to fend for myself.

  6. #26
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,581

    Default Re: Plasma crashes - I think - when resizing desktop widget

    What a jerk I'm done

  7. #27
    Join Date
    Jan 2009
    Location
    Chesterfield Township, MI USA
    Posts
    82

    Default Re: Plasma crashes - I think - when resizing desktop widget

    Quote Originally Posted by gogalthorp View Post
    What a jerk I'm done
    If you didn't hate me, you would have defended yourself, but you hate me so you "take" offense and run away. That's more clues to your agenda. You can act like you care about my opinion and take" offense, but it is faux anger. You needed ANY excuse NOT to help me. Hateful jerk!!!!!! Prove me wrong and fix my problem!!!!! AND not one word about my 7 instances of problems Immediately after applying updates. No "wow" no empathetic "sorry to hear that". Just use ANY excuse to NOT help me.

  8. #28
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,176
    Blog Entries
    3

    Default Re: Plasma crashes - I think - when resizing desktop widget

    Quote Originally Posted by trekjunky View Post
    Here's a thought: Can a few of you get together and come up with a plan that you all can agree on and present it to me to follow?
    If we could easily come up with a plan, we would already have done that.

    The difficulty is that we would first need to understand the problem. And you are not providing enough information that would help us with understanding the problem.
    openSUSE Leap 15.1; KDE Plasma 5;

  9. #29
    Join Date
    Jan 2009
    Location
    Chesterfield Township, MI USA
    Posts
    82

    Default Re: Plasma crashes - I think - when resizing desktop widget

    Quote Originally Posted by nrickert View Post
    If we could easily come up with a plan, we would already have done that.

    The difficulty is that we would first need to understand the problem. And you are not providing enough information that would help us with understanding the problem.
    I would love to present the information you need to understand the problem. I have provided parts of certain logs and the last 75 lines of the results of running the command journalctl.
    As I am not a Linux Administrator, I do not know HOW to find the info you need to help you understand the problem. If you could ask me to run a command and/or copy the contents of a log, I can do that.
    So, far, I have run commands and copied the contents of a logs, AND finally was FORCED to do a re-install of OpenSuSE 15.1 from DVD, ALL of which did nothing to solve my issue so far.
    What else can I do?

    P.S. I would really appreciate any help on this. Because I have had numerous problems in the past that FORCED me to re-install the OS, I am dubious that you will actually help me, but we will see.

  10. #30
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,176
    Blog Entries
    3

    Default Re: Plasma crashes - I think - when resizing desktop widget

    I have read the thread again. And I don't think I can help you.

    The person best able to help you is tannington, who is more into that kind of detail with KDE. But when I read through the thread, I see you complaining that it is consuming too much of your time. Did you ever think about how much time tannington has spent on this?

    I know how tannington installed that widget, because he explained. I still don't know how you installed it, because you have not provided that information.
    openSUSE Leap 15.1; KDE Plasma 5;

Page 3 of 5 FirstFirst 12345 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
  •