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

Thread: after suspend and resume from RAM system start from login screen instead of resume screan

  1. #1

    Default after suspend and resume from RAM system start from login screen instead of resume screan

    on my Laptop=Dell latitude E6510, RAM=8Gb, GPU=GT218 NVS 3100M, CPU=i7 Q 720 @ 1.60GHz: host=pla-3-TW, partition=suse2, OS=leap 42.3, DE=plasma 5.11.5, KDE frameworks 5.41.0, KDE applications 17.12.0, Kernel 4.4.104-39-default, nvidia drivers, libreoffice 5.3.5.2-30
    Sometimes, about 1 times on 4, after suspend to RAM and when I resume, the system start, but from login screen asking the password and doing a mess and brake system and force me to reboot, instead of to start from resume screen and going to the saved session correctly, I have two different wallpapers for login and resume so it jumped me to the eyes and so I can see this.
    how can I solve this very annoying bug??
    manythanks, ciao, pier :-)

  2. #2

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    again it happened: this is the screenshot after a resume from RAM, the laptop didn't resume but seems to login again closing all the applications that was opened

  3. #3
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,843
    Blog Entries
    1

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    You seem to have some strange symptoms, but I'm wondering if you might have 'Lock screen on resume' enabled?

    System settings -> Desktop Behaviour -> Screen locking

  4. #4

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    Quote Originally Posted by deano_ferrari View Post
    You seem to have some strange symptoms, but I'm wondering if you might have 'Lock screen on resume' enabled?

    System settings -> Desktop Behaviour -> Screen locking
    ..yes I have 'Lock screen on resume' enabled

  5. #5
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,317
    Blog Entries
    14

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    Issues like the one you're displaying are mostly caused by a mix of incompatible KDE packages. The versions you provide are not Leap's stock versions.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  6. #6

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    Quote Originally Posted by Knurpht View Post
    Issues like the one you're displaying are mostly caused by a mix of incompatible KDE packages. The versions you provide are not Leap's stock versions.
    ...no, it is updated to the last issue but not tumbleweed, this the main things DE=plasma 5.11.95, KDE frameworks 5.42.0, KDE applications 17.12.1, Kernel 4.4.104-39-default, nvidia drivers
    from here:
    Code:
    Type 'zypper help <command>' to get command-specific help.
    pla@pla-3-TW:~> zypper repos
    Repository priorities are without effect. All enabled repositories share the same priority.
    
    #  | Alias                                                | Name                                                 | Enabled | GPG Check | Refresh
    ---+------------------------------------------------------+------------------------------------------------------+---------+-----------+--------
     1 | GNOME:/Apps                                          | GNOME:/Apps                                          | Yes     | (r ) Yes  | Yes     
     2 | KDE:/Applications/KDE_Frameworks5                    | KDE:/Applications/KDE_Frameworks5                    | Yes     | (r ) Yes  | Yes     
     3 | KDE:/Extra                                           | KDE:/Extra                                           | Yes     | (r ) Yes  | Yes     
     4 | KDE:/Frameworks5                                     | KDE:/Frameworks5                                     | Yes     | (r ) Yes  | Yes     
     5 | KDE:/Qt5                                             | KDE:/Qt5                                             | Yes     | (r ) Yes  | Yes     
     6 | Opera_packages_(opera)                               | Opera packages (opera)                               | Yes     | (r ) Yes  | Yes     
     7 | download.nvidia.com-leap                             | nVidia Graphics Drivers                              | Yes     | (r ) Yes  | Yes     
     8 | download.opensuse.org-non-oss                        | Main Repository (NON-OSS)                            | Yes     | (r ) Yes  | Yes     
     9 | download.opensuse.org-non-oss_1                      | Update Repository (Non-Oss)                          | Yes     | (r ) Yes  | Yes     
    10 | download.opensuse.org-oss                            | Main Repository (OSS)                                | Yes     | (r ) Yes  | Yes     
    11 | download.opensuse.org-oss_1                          | Main Update Repository                               | Yes     | (r ) Yes  | Yes     
    12 | google_(chrome)                                      | google (chrome)                                      | Yes     | (r ) Yes  | Yes     
    13 | home:/AndnoVember:/LXQT/_(copyq)                     | home:/AndnoVember:/LXQT/ (copyq)                     | Yes     | (r ) Yes  | Yes     
    14 | home:/wolfi323:/branches:/KDE:/Frameworks5_(beclock) | home:/wolfi323:/branches:/KDE:/Frameworks5 (beclock) | Yes     | (r ) Yes  | Yes     
    15 | openSUSE-Leap-42.3-0                                 | openSUSE-Leap-42.3-0                                 | No      | ----      | ----
    16 | opensuse-guide.org-repo                              | Libdvdcss Repository                                 | Yes     | (r ) Yes  | Yes     
    17 | opera                                                | Opera packages                                       | Yes     | (r ) Yes  | Yes     
    18 | packman.inode.at-suse                                | Packman Repository                                   | Yes     | (r ) Yes  | Yes     
    19 | repo-debug                                           | openSUSE-Leap-42.3-Debug                             | No      | ----      | ----
    20 | repo-debug-non-oss                                   | openSUSE-Leap-42.3-Debug-Non-Oss                     | No      | ----      | ----
    21 | repo-debug-update                                    | openSUSE-Leap-42.3-Update-Debug                      | No      | ----      | ----
    22 | repo-debug-update-non-oss                            | openSUSE-Leap-42.3-Update-Debug-Non-Oss              | No      | ----      | ----
    23 | repo-source                                          | openSUSE-Leap-42.3-Source                            | No      | ----      | ----
    24 | repo-source-non-oss                                  | openSUSE-Leap-42.3-Source-Non-Oss                    | No      | ----      | ----
    25 | suse-Emulators:/Wine                                 | suse-Emulators:/Wine                                 | Yes     | (r ) Yes  | Yes     
    26 | suse-Printing_(hplip_cups)                           | suse-Printing (hplip cups)                           | Yes     | (r ) Yes  | Yes     
    27 | suse-Publishing_(pdfchain)                           | suse-Publishing (pdfchain)                           | Yes     | (r ) Yes  | Yes     
    28 | suse-Virtualization_(virtualbox)                     | suse-Virtualization (virtualbox)                     | Yes     | (r ) Yes  | Yes     
    29 | suse-hardware_(cyanogen)                             | suse-hardware (cyanogen)                             | Yes     | (r ) Yes  | Yes     
    30 | suse-network_(nextcloud)                             | suse-network (nextcloud)                             | Yes     | (r ) Yes  | Yes    
    
    



  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,843
    Blog Entries
    1

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    You could check for package inconsistencies using zypper...
    Code:
    zypper ve --dry-run

  8. #8

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    Quote Originally Posted by deano_ferrari View Post
    You could check for package inconsistencies using zypper...
    Code:
    zypper ve --dry-run
    it seems ok
    Code:
    pla@pla-3-TW:~> zypper ve --dry-run
    Loading repository data...                                                                                                                                  
    Reading installed packages...                                                                                                                               
                                                                                                                                                                
    Dependencies of all installed packages are satisfied.                                                                                                       
    pla@pla-3-TW:~>   
    
    ..or I must be root?

  9. #9
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,843
    Blog Entries
    1

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    That seems to check out ok.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,843
    Blog Entries
    1

    Default Re: after suspend and resume from RAM system start from login screen instead of resume screan

    It is interesting that you mention that resuming fails about 1 in 4 occasions....I've read of a number of reports where those with nvidia hardware and Plasma 5 can't resume successfully at all. These could well be related...

    https://bugs.kde.org/show_bug.cgi?id=382115
    https://bugreports.qt.io/browse/QTBUG-56610?jql=text%20~%20%22nvidia%22

    The conclusion is that Qt needs to correctly use GL_NV_robustness_video_memory_purge to avoid corruption. The KDE developers say this is a Qt problem.
    Last edited by deano_ferrari; 05-Feb-2018 at 14:13.

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
  •