Bug 1102713 - Systems hangs since last night update
Summary: Systems hangs since last night update
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: openSUSE GNOME
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-26 08:43 UTC by Henri Baar
Modified: 2018-08-01 14:18 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
small sys info (20.14 KB, text/plain)
2018-07-26 08:43 UTC, Henri Baar
Details
journalctl -xb (262.60 KB, text/plain)
2018-07-26 13:20 UTC, Henri Baar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Henri Baar 2018-07-26 08:43:34 UTC
Created attachment 778079 [details]
small sys info

Since the complete update this morning, 26/7/2018-07:30 ;

- I reboot my system. 
- Login as a user; GNOME-interface
- Start 'akregator' by clicking the icon
- Systems looks ok for a few seconds
- Move cursor to "Activities" and my systems hangs

It hangs completely, mouse, screen and keyboard. 
It DOESN'T happen with 'chrome' or 'thunderbird'.
I have not tested any other appl yet.

On the att you will find 'uname' and 'pf' at the moment it happends
Comment 1 Tomáš Chvátal 2018-07-26 09:15:34 UTC
Please provide some logs like dmesg or "journalctl -xb" here as well. With what you posted here it is not possible to fix.
Comment 2 Henri Baar 2018-07-26 13:20:23 UTC
Created attachment 778105 [details]
journalctl -xb

- journal started
- selected appl 'akregator'
- waited, nothing happend
- move mouse to "Activities"
- no reaction from the systems. Closing the lit had no result so I powered down the hard way
Comment 3 Henri Baar 2018-07-26 13:21:11 UTC
Added journalctl file
Comment 4 Tomáš Chvátal 2018-08-01 11:06:24 UTC
Since system is still working only UI is stuck and there are tracker/gnome traces in log lets have the gnome team to look at it.
Comment 5 Michiel Janssens 2018-08-01 11:36:25 UTC
Possibly related to bug 1103136
You could try the tests with Firefox that are mentioned in that report.
In case same result, you could try the packages provided there and see if they fix it.

Probably a good thing that you mention:
Tumbleweed snapshot number
xorg-x11-server package version
xorg-x11-server-wayland package version
Comment 6 Henri Baar 2018-08-01 13:26:16 UTC
 Looks like a similar problem, but in my case it freezes as soon as I click the 'Activities' button.

I have found a work-around that works for now; open the same user in 'Plasma' .... Went through all the appl that had problems (in Plasma no problem) ... Logout....... Re-Login using ' gnome' ........ all problems solved.

I restored my environment that I had BEFORE going to 'Plasma' and could reproduce the problem.

So, It looks like there is something going on using 'Gnome' that screws up some local data/cache/memory that causes the problem. It also seems that 'Plasma' is cleaning up.... mmmmmm..... makes you wonder what changed in the rolling update that I did July 25-26

For now I have a work-around.
Comment 7 Atri Bhattacharya 2018-08-01 14:18:40 UTC
(In reply to Henri Baar from comment #6)
>  Looks like a similar problem, but in my case it freezes as soon as I click
> the 'Activities' button.
> 
> I have found a work-around that works for now; open the same user in
> 'Plasma' .... Went through all the appl that had problems (in Plasma no
> problem) ... Logout....... Re-Login using ' gnome' ........ all problems
> solved.
> 
> I restored my environment that I had BEFORE going to 'Plasma' and could
> reproduce the problem.
> 
> So, It looks like there is something going on using 'Gnome' that screws up
> some local data/cache/memory that causes the problem. It also seems that
> 'Plasma' is cleaning up.... mmmmmm..... makes you wonder what changed in the
> rolling update that I did July 25-26
> 
> For now I have a work-around.

Two things, if I may:
* Please do not change the Priority field for a bug report, unless *you* are working on the bug yourself. If you are, please also assign the bug to yourself. Otherwise the Priority field is exclusively the assignee's to change.
* Should you run into the freeze again, please try the suggested fix in bug 1103136#c3. If that works, we will know if you are hitting the same bug.