Description of problem: [ 1177.645531] drakconf[7461]: segfault at 51 ip 00007f56fb7a2130 sp 00007ffe56389c60 error 4 in libgobject-2.0.so.0.6000.2[7f56fb78a000+31000] [ 1177.645539] Code: 89 44 24 5c 41 f6 44 24 18 10 74 56 89 c1 48 8b 05 3d 45 03 00 48 85 c0 74 48 48 89 da eb 0b 0f 1f 00 48 8b 00 48 85 c0 74 38 <48> 3b 50 08 75 f2 3b 48 10 75 ed 8b 74 24 58 3b 70 14 75 e4 c7 40 This is from dmesg on my ipc3 with "RIP: 0010:ext4_set_page_dirty+0x3e/0x50" gdb info: /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.6000.2-gdb.py /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.6000.2-gdb.pyc /usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.6000.2-gdb.pyo /usr/share/systemtap/tapset/x86_64/libgobject-2.0.so.0.6000.2.stp Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
The currently released package is glib2.0-2.60.2-1.mga7.src.rpm You are reporting on glib2.0-2.60.2-1.1.mga7.src.rpm which was presumably in core/updates_testing. The version there for testing is now glib2.0-2.60.2-1.2.mga7.src.rpm ; it has a bug associated with it: https://bugs.mageia.org/show_bug.cgi?id=25276 I have already asked you that if you want to play with packages you find in updates_testing, please: - only do so if you see them listed in http://madb.mageia.org/tools/updates - add your comments to the bug associated with the update. Packages in updates_testing not listed are *not* valid for complaints if you choose to try them. These repos are often used as a store for forthcoming but not finalised updates. So you are welcome to add your comments to the bug for this update cited above - after updating the package; but please say what you were doing. Was this a one-off thing, or does it happen consistently. Oh - and please do join QA.
Resolution: (none) => INVALIDStatus: NEW => RESOLVEDCC: (none) => lewyssmith
Not so fast. I have had this problem with glib2.0-2.60.2-1.2.mga7.src.rpm Several times in matter of facts. In the beginning it was a mystery. I could enter the root password at the request of the MCC window. Then I re-installed the boot loader and MCC crashed. After some time I could, again, enter the root password. I then discovered that the same thing happened after the update of the many libreoffice packages. My IPC3 box has an mSATA SSD mounted on a FM-USB3 card. I had the, possibly mistaken, idéa that the content of the SSD is copied to the faster RAM, and that this takes some time. My firefox is also very jerky to the extend that I cannot use it. My real motive was to get firefox to work properly. My next idéa was that the i7 processors possibly overheated while waiting for the slow SSD. To test this theory I used the command: cpupower frequency-set -g powersave I do not know how the IPC3 hardware work, but this command made firefox working without any jerks, and I can enter the root pasword in MCC. I am using firefox to enter these lines. This shows that crashes can be caused by many things.
> My IPC3 box has an mSATA SSD mounted on a FM-USB3 card. > I used the command: > # cpupower frequency-set -g powersave > this command made firefox working without any jerks > and I can enter the root pasword [consistently] in MCC OK, thanks for the fuller explanation. Your original description of the bug was not helpful (and my response to it was reasonable); what you say now is. So I have re-opened the bug. At least you are now using the latest (yet to be tested & released) glib2.0-2.60.2-1.2. Can you say that the problems noted in c2 only arose after the glib2.0 update [pending]. What happens if you downgrade it? I have amended the bug summary on this assumption; please change it if you can better define the issue. I have posted your last comment on bug 25726, which I had asked you to do. If you have anything to add, please do so on that bug. ----- Assigning directly to tmb in the hope you understand the technicalities.
Resolution: INVALID => (none)Status: RESOLVED => REOPENEDAssignee: bugsquad => tmbSource RPM: glib2.0-2.60.2-1.1.mga7.src.rpm => glib2.0-2.60.2-1.2.mga7.src.rpmSummary: drakconf[7461]: segfault at 51 ip 00007f56fb7a2130 sp 00007ffe56389c60 error 4 in libgobject-2.0.so.0.6000.2[7f56fb78a000+31000] => MCC crashes and very slow Firefox after glib2.0 update on IPC3 system
*** Bug 25740 has been marked as a duplicate of this bug. ***
Well, this problem seems to be solved on my hardware using the command: "cpupower frequency-set -g powersave" But, I am not absolutely certain why it works. Why does the chromium browser work without this command? The advantage of my hardware is that it has no moving parts.
I am giving up. The plasma shell crashed after printing to my HP network printer. I am moving to a gnome session. It does not require the cpupower command. I have run out of idéas.
That the problem might be Plasma related is weird. Please do report back with your Gnome experience - or with any other desktops. > The advantage of my hardware is that it has no moving parts No discs, I suppose you mean; or 'spinning rust' as some call them. This has been a trend for a long time. But no processor fan?
Exactly. No processor fan. I forgot to mention that I had processor overheating. That was another reason for trying "cpupower frequency-set -g powersave" I have the impression that it happened after the introduction of gcc-8.3.1-0.20191101.1.mga7 Could it be a broblem for my "missing CPU-fan" hardware? Also, there used to be a yellow notification when the HP-printer stopped. That one has dissapeared. Also, hplip-3.19.5-1.mga7, used by gnome, was build 2019-05-14. with the old version of gcc-8.3.1 It is fine for me to use "-g powersave" if I could figure out, why it hangs after printing. lp text-file works fine. The problem happens while printing from within firefox. Firefox works fine as I am typing this comment. I shall make some further tests with the plasma desktop.
Actually, the CPUs are not overheating. I have installed Psensor. When idle it is about 39C, when working it is around 50C. This is with the plasma desktop. I did reinstal the driver for my Hewlett-Packard HP Color LaserJet CP3525. In the beginning firefox was a bit slow, but printing worked without crashing. This was before I installed Psensor, so I am not sure if the processor overheated. Something else might have been running.
I have now tried the IceWM. Firefox is even faster, and the printing works fine. I am still not sure what went wrong in the first place. I have only reinstalled the HP printer driver.
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Resolution: (none) => OLDStatus: REOPENED => RESOLVED