[opensuse-factory] Tumbleweed - Review of the week 2018/06
Dear Tumbleweed users and hackers, Finally back to getting the weekly review done on Friday. Week 6 is coming to an end and Tumbleweed delivered 5 snapshots in this time (0202, 0203, 0205, 0206 and 0207). Sone issues did slip past our QA system and sadly some users were hit by issues. More about that further down. The five snapshots delivered those updates: * Many yast fixes/changes, as detailed in the yast sprint review * Mesa 18.0.0 – responsible for the issues mentioned initially * NetworkManager 1.10.2 * ncurses 6.1 * LibreOffice 6.0.0.3 (RC3) * sqlite3.22.0 * KDE Plasma 5.12.0 * Linux kernel 4.15.1 * Mozilla Firefox 58.0.1 And those things are in the makings: * Linux Kernel 4.15.2 * GLIBC 2.27, with deprecation of sunrpc * Freetype 2.9 * VLC 3.0.0 Now some words about the issues of the last week: Mesa 18 (rc) was delivered to the users in snapshot 0203. After a few reports, it became apparent that Mesa is writing invalid cache data on the disk, which after being read, causes issues like white screens and such. The number of boots varied and openQA did not catch this – even though we do have reboots in the system tests too, this was not sufficient to trigger the failures. As soon as the problem was identified, a fix was prepared and published in the update channel and finally in the 0206 snapshot. Unfortunately, at that point, the saved disk cache was already invalid and users were forced to clean it out manually (remove ~/.cache of the user and also /usr/lib/sddm/.cache) At this point I’d like to thank all the users reporting the issue, the developers working on fixing the issue and the entire community to help each other out to find the right solutions for the problems found Cheers, Dominique
Am 09.02.2018 um 19:26 schrieb Dominique Leuenberger / DimStar:
Dear Tumbleweed users and hackers,
[...] Now some words about the issues of the last week: Mesa 18 (rc) was delivered to the users in snapshot 0203. After a few reports, it became apparent that Mesa is writing invalid cache data on the disk, which after being read, causes issues like white screens and such. The number of boots varied and openQA did not catch this – even though we do have reboots in the system tests too, this was not sufficient to trigger the failures. As soon as the problem was identified, a fix was prepared and published in the update channel and finally in the 0206 snapshot. Unfortunately, at that point, the saved disk cache was already invalid and users were forced to clean it out manually (remove ~/.cache of the user and also /usr/lib/sddm/.cache)
I am puzzled, because with the update to TW20180207 I am experiencing the above-mentioned issue (white sddm, black desktop) again (after TW20180206). How come? Regards, Frank -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Same black desktop with cursor arrow here after zypper dup and clearing .cache and /usr/lib/sddm/.cache. On Fri, Feb 9, 2018 at 10:44 AM, Frank Krüger <fkrueger@mailbox.org> wrote:
Am 09.02.2018 um 19:26 schrieb Dominique Leuenberger / DimStar:
Dear Tumbleweed users and hackers,
[...] Now some words about the issues of the last week: Mesa 18 (rc) was delivered to the users in snapshot 0203. After a few reports, it became apparent that Mesa is writing invalid cache data on the disk, which after being read, causes issues like white screens and such. The number of boots varied and openQA did not catch this – even though we do have reboots in the system tests too, this was not sufficient to trigger the failures. As soon as the problem was identified, a fix was prepared and published in the update channel and finally in the 0206 snapshot. Unfortunately, at that point, the saved disk cache was already invalid and users were forced to clean it out manually (remove ~/.cache of the user and also /usr/lib/sddm/.cache)
I am puzzled, because with the update to TW20180207 I am experiencing the above-mentioned issue (white sddm, black desktop) again (after TW20180206). How come?
Regards, Frank -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 02/10/2018 02:53 AM, Chuck Davis wrote:
Same black desktop with cursor arrow here after zypper dup and clearing .cache and /usr/lib/sddm/.cache.
Try backing up kwinrc in your .config directory, i.e. mv ~/.config/kwinrc ~/.config/kwinrc.bak and try again. My system was set to XRender as the Compositor (Backend=XRender), which messed up my desktop. When mine locked up, going go a tty was interesting, as at first I thought some crazy language had gotten installed, but now realize it was probably garbage. Display of what was typed was unreadable, but things executed OK, so I could reboot. I tried to reenable XRender (rather than OpenGl 2.0), and still crashes. So something has changed with XRender as well as the cache problem. HTH, Joe -- Joe Morris Registered Linux user 231871 running openSUSE Tumbleweed x86_64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne pátek 9. února 2018 19:53:41 CET, Chuck Davis napsal(a):
Same black desktop with cursor arrow here after zypper dup and clearing .cache and /usr/lib/sddm/.cache.
I had black screen with 20180207. Removal of ~/.cache and reboot helped.
On Fri, Feb 9, 2018 at 10:44 AM, Frank Krüger <fkrueger@mailbox.org> wrote:
Am 09.02.2018 um 19:26 schrieb Dominique Leuenberger / DimStar:
Now some words about the issues of the last week: Mesa 18 (rc) was delivered to the users in snapshot 0203. After a few reports, it became apparent that Mesa is writing invalid cache data on the disk, which after being read, causes issues like white screens and such. The number of boots varied and openQA did not catch this – even though we do have reboots in the system tests too, this was not sufficient to trigger the failures. As soon as the problem was identified, a fix was prepared and published in the update channel and finally in the 0206 snapshot. Unfortunately, at that point, the saved disk cache was already invalid and users were forced to clean it out manually (remove ~/.cache of the user and also /usr/lib/sddm/.cache)
I am puzzled, because with the update to TW20180207 I am experiencing the above-mentioned issue (white sddm, black desktop) again (after TW20180206). How come? -- Vojtěch Zeisek https://trapa.cz/
participants (5)
-
Chuck Davis -
Dominique Leuenberger / DimStar -
Frank Krüger -
Joe Morris -
Vojtěch Zeisek