Bug 29719

Summary: SystemSettings->Applications segfaults
Product: Mageia Reporter: w unruh <unruh>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: critical    
Priority: Normal CC: alexreynolds0831, davidwhodgins, lewyssmith, marja11
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: systemsettings-5.20.4-2.mga8 ? CVE:
Status comment:

Description w unruh 2021-12-01 23:48:14 CET
Description of problem:When I click on the Applications item in SystemSettings under Plasma, it crashes. If I run systemsettings5 from the command line, and I click on Applications, I get a segfault


Version-Release number of selected component (if applicable):systemsettings-5.20.4-2.mga8



How reproducible: I've tried it 5 times and each time it has crashed.

Steps to Reproduce:
1.Omen System Settings.
2.Click on Applications


Mageia 8 on XPS13 9310 laptop, updated. Kernel 
5.15.4-server-1.mga8

systemsettings5 
ATTENTION: default value of option vblank_mode overridden by environment.
kf.service.services: KApplicationTrader: mimeType "inode/directory" not found
Segmentation fault (core dumped


output of end of  strace systemsettings5
access("/usr/share/icons/oxygen/base/22x22/animations/system-file-manager.png", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/share/icons/oxygen/base/22x22/apps/system-file-manager.png", F_OK) = 0
statx(AT_FDCWD, "/usr/share/icons/oxygen/base/22x22/apps/l10n", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffe34107780) = -1 ENOENT (No such file or directory)
access("/usr/share/icons/oxygen/base/32x32/actions/system-file-manager.png", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/share/icons/oxygen/base/32x32/animations/system-file-manager.png", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/share/icons/oxygen/base/32x32/apps/system-file-manager.png", F_OK) = 0
statx(AT_FDCWD, "/usr/share/icons/oxygen/base/32x32/apps/l10n", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffe34107780) = -1 ENOENT (No such file or directory)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="\22\0\6\0\f\0@\6\246\1\0\0\320\1\0\0\10\0\0\0\0\0\0\0&\0\2\0#\5\0\0", iov_len=32}], 1) = 32
futex(0x7ffe34107708, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x11b6fd8, FUTEX_WAKE_PRIVATE, 1) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x10} ---
+++ killed by SIGSEGV (core dumped) +++
Comment 1 Dave Hodgins 2021-12-02 01:52:59 CET
ok on my system.

Does the file /usr/share/mime/inode/directory.xml exist? It's from the
package shared-mime-info.

CC: (none) => davidwhodgins

Comment 2 w unruh 2021-12-02 02:37:27 CET
The file existed, but was not readable by "other". I made it readable. Now things are worse. It I run
systemsetting5
the mouse cursor dis appears. If I do alt-ctrl  the SystemSetttings window disappears, then comes back with a black border, and in a few seconds the mouse cursor reappears, but nothing works (ie clicking does not work) for a while. Then it does, and clicking on Applications causes the window to disappear and segfault occurs.
Comment 3 Dave Hodgins 2021-12-02 03:59:50 CET
$ ll /usr/share/mime/inode/directory.xml
-rw-r--r-- 1 root root 2543 Nov 25 17:47 /usr/share/mime/inode/directory.xml
So it should already have been readable by other. The question becomes how did
it lose that permission, and what other files now have the wrong permissions
or other attributes.

Any idea how it lost the permission? If you don't know, then the options are
to go through the output (run as root) "rpm -Va" to figure out which ones
have the wrong attributes (see "man rpm" and search for "format of the output"
for what the characters in the 9 columns mean) or to re-install the system.
Comment 4 w unruh 2021-12-02 04:51:14 CET
Nope, no idea how. But a permission should not cause a segfault, no matter what.

I've done rpm -Va, and looked at M, the mode change from installation, and cansee nothing there that could explain the problem.
Comment 5 w unruh 2021-12-02 04:53:19 CET
Does anyone know what program is run when one clicks on Applications under SystemSettings?
Comment 6 Dave Hodgins 2021-12-02 09:14:52 CET
   4435 dave       20   0  232M  7272  3384 S  0.0  0.0  0:00.22 │  │  └─ bash│/bin/bash
  27104 dave       20   0 1264M  145M  107M S  0.0  0.9  0:00.93 │  │     ├─ systemsettings5
  27109 dave       20   0 1264M  145M  107M S  0.0  0.9  0:00.01 │  │     │  ├─ systemsettings5│QXcbEventQueue
  27110 dave       20   0 1264M  145M  107M S  0.0  0.9  0:00.00 │  │     │  ├─ systemsettings5│QDBusConnection
  27111 dave       20   0 1264M  145M  107M S  0.0  0.9  0:00.01 │  │     │  ├─ systemsettings5│systemset:rcs0
  27112 dave       39  19 1264M  145M  107M S  0.0  0.9  0:00.00 │  │     │  ├─ systemsettings5│systems:disk$0
  27117 dave       20   0 1264M  145M  107M S  0.0  0.9  0:00.04 │  │     │  ├─ systemsettings5│QQmlThread
  27118 dave       20   0 1264M  145M  107M S  0.0  0.9  0:00.00 │  │     │  └─ systemsettings5│QQmlThread

It's all part of systemsettings5, so "rpm -q -l systemsettings" shows which
files are part of it, though as a kde plasma program it will also use various
qt libs.
Comment 7 w unruh 2021-12-02 21:52:52 CET
The system is rapidly decaying. The mouse arrow will disappear for seconds at a time (up to 10 sec). If I click on the clock at the bottom right of the taskbar, up will come a black screen with white blotches on it-- certainly not a calendar. At times the popup explanations of an icon will have lost many of their letters
(Bluetooth will be Bl   t o th and all of the icons on the bottom right will display the same kind of nonsense. windows will disappear for 5 sec at a time and then reappear

I tried to use xfce instead of plasma, but all I got was a black screen with a mouse cursor on it. I had to do alt-ctrl-F2 log in and killed the xfce program to recover. And this all seems to be getting steadily worse.
Logging in has big pauses in it, and the desktop may flash.
It is hard to imagine this as a hardware problem. I have no idea how to track this down, but it is making this computer almost unuseable.
Comment 8 Dave Hodgins 2021-12-02 22:31:19 CET
Can you boot a live iso to see if it works with that hardware?
Comment 9 w unruh 2021-12-04 00:12:26 CET
I tried another user on the system, and they also have problems. I tried the live distribution briefly and it seemed not to have the problems. But that may be that I did not try long enough ( although the problems start showing up pretty quickly.
It really seems to be a graphics problem-- maybe the graphics driver, maybe the kernel modules. (I have also used my spare / system to reinstall the un-updated Mga 8 on it, and again did not seem to have the problem. Of course it is a much stripped down version since I have not insatalled all of the programs which I have on my system onto that one. I have installed chrome, and it seemed to be fine.
Comment 10 w unruh 2021-12-05 07:16:14 CET
Very strange. I did a new installation ( without update) of Mga8 onto a separate partition. That installation has none of the problems. while the old installation keeps having the same problesm-- getting worse if anything. It really seems that the updating of the system is causing the problems. So it does not appear to be hardware, but software. The fresh install also does not have the problem with the sddm flashing back to the console for 2 seconds about 5 seconds after it first displays. Ie almost all of my problems seem to be caused by the same thing.
Comment 11 Lewis Smith 2021-12-05 20:08:38 CET
I also confirm that this does not happen on my system, fully up-to-date including Plasma.
It is curious how you suffer so many problems unique to yourself. Dave's suggestion to try the Plasma Live ISO was sound: you did, and it seemed not to have the problem; which, when it happens, is immediate.
The problematic system seems rather sick. For "almost unuseable" read "unuseable". Has it ever worked properly? Can you describe its degradation?

CC: (none) => lewyssmith

Comment 12 w unruh 2021-12-05 21:58:19 CET
One big difference was that I upgraded and MGA7 install then. as I recall it did work more or less OK at the beginning. There were two weirdnesses which began very near the initial upgrade-- one was that sddm logon screen would show for about 3-5 sec, but then flash to the console, and then after about a second show the console for about 1 second,before I could enter the password for myself. The second was that I would get lines on the screen, especially if chrome was running, where pixel lines were displaced. I have seen the latter happen on a konsole screen visible peeking out from the sides of Chrome  screen.  But more recently things have degenerated badly (eg this bug report). So far I have not seen either the sddm flashing or the other problems mentioned here on the new instalel. But I have not updated it.
Comment 13 Dave Hodgins 2021-12-06 04:51:34 CET
See if turning off "Enable compositor on startup" in systemsettings5 under
Hardware/Display and Monitor/Compositor, and restarting the system has any
effect.
Comment 14 w unruh 2021-12-06 06:11:02 CET
It was already off (uncheckmarked)
Weirdly enough things are getting worse and worse in the version which was the update to Mga7. Meanwhile, the new installation is still working, except for the pixels on lines being messed up.)
Comment 15 Dave Hodgins 2021-12-06 22:57:28 CET
Have you installed updates from the testing repos? There are some there that
haven't been assigned to qa yet, that in their present form cause problems.

On one install where I have the testing repos enabled as updates repos, in
/etc/urpmi/skip.list, I currently have ...
lib64wx_baseu3.1_5
lib64wx_gtk3u_core3.1_5
Comment 16 w unruh 2021-12-07 00:55:54 CET
Nope. just the  release and the updates for core, nonfree and tainted.
Comment 17 Marja Van Waes 2022-04-22 12:54:16 CEST
@ w unruh

Maybe this report should be closed as OLD? It seems an issue that only affected one Mageia installation of no one else than you, there was an unexplained permission issue, too, and that installation became more and more unstable, didn't it?

Status: NEW => UNCONFIRMED
CC: (none) => marja11
Ever confirmed: 1 => 0

Comment 18 sturmvogel 2022-06-12 22:01:55 CEST
Based on Marjas comment 17 and no response from w unruh: Closing as OLD.

Resolution: (none) => OLD
Status: UNCONFIRMED => RESOLVED

Comment 19 Alex Reynolds 2023-07-03 03:40:51 CEST Comment hidden (spam)

CC: (none) => alexreynolds0831