| Summary: | Gimp lockup on launch, problem with mypaint brushes (renaming /usr/share/mypaint-data fixes the issue) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | M D <crxssi> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | geiger.david68210, marja11, pterjan, shlomif, thierry.vignaud |
| Version: | 7 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gimp-2.10.10-1.mga7, mypaint-brushes-1.3.0-2.mga7 | CVE: | |
| Status comment: | |||
|
Description
M D
2019-08-03 18:32:37 CEST
(In reply to M D from comment #0) > If I try to remove the "mypaint-brushes" rpm, it will force removing all of > GIMP. If I manually rename /usr/share/mypaint-data then gimp will load > normally. Why would a gimp rpm have a dependency on mypaint brushes? And, > of course, why does this cause gimp to runaway? mypaint-brushes its a require for GIMP, thats why gimp its working for me, what desktop are you using? Provide output of this rpm -qa|grep mypaint rpm -qa|grep gimp
katnatek
2019-08-03 21:47:45 CEST
Keywords:
(none) =>
NEEDINFO Mageia 7.1 lib64mypaint1.3_0-1.3.0-8.mga7 mypaint-brushes-1.3.0-2.mga7 ufraw-gimp-0.22-11.mga7 lib64gimp2.0_0-2.10.10-1.mga7 gimp-python-2.10.10-1.mga7 gimp-data-extras-2.0.2-10.mga7 gimp-plugin-gmic-2.5.7-1.mga7 gimp-help-en-2.8.2-6.mga7 gimp-2.10.10-1.mga7 Keywords:
NEEDINFO =>
(none) (In reply to M D from comment #2) > Mageia 7.1 > > lib64mypaint1.3_0-1.3.0-8.mga7 > mypaint-brushes-1.3.0-2.mga7 > > ufraw-gimp-0.22-11.mga7 > lib64gimp2.0_0-2.10.10-1.mga7 > gimp-python-2.10.10-1.mga7 > gimp-data-extras-2.0.2-10.mga7 > gimp-plugin-gmic-2.5.7-1.mga7 > gimp-help-en-2.8.2-6.mga7 > gimp-2.10.10-1.mga7 Oh, Plasma/KDE 5 (with several other desktops installed but never used/launched) (In reply to M D from comment #3) > Oh, Plasma/KDE 5 (with several other desktops installed but never > used/launched) Do you have some Gtk Desktop like GNOME of Xfce?, try to launch gimp from one of them I can't reproduce, is not a missing require neither a conflict with plugins (In reply to katnatek from comment #4) > Do you have some Gtk Desktop like GNOME of Xfce?, try to launch gimp from > one of them Yes. I just logged out and tried Xfce. Gimp will get stuck exactly the same way. Sometimes the splash window is solid gray, sometimes not. Doesn't matter which user I try, either. (In reply to M D from comment #5) > (In reply to katnatek from comment #4) > > > Do you have some Gtk Desktop like GNOME of Xfce?, try to launch gimp from > > one of them > > Yes. I just logged out and tried Xfce. Gimp will get stuck exactly the > same way. Sometimes the splash window is solid gray, sometimes not. > Doesn't matter which user I try, either. Including a new user who has no settings.... Hi M D, If you reinstall mypaint-brushes with: urpmi --replacepkgs mypaint-brushes Does the bug then occur again? CC:
(none) =>
marja11, shlomif, thierry.vignaud (In reply to Marja Van Waes from comment #7) > Hi M D, > > If you reinstall mypaint-brushes with: > > urpmi --replacepkgs mypaint-brushes > > Does the bug then occur again? Yes, unfortunately it does. Maybe a rights issue, provide output of ls -la /home (In reply to katnatek from comment #9) > Maybe a rights issue, provide output of > > ls -la /home I have the same problem if I run gimp as root. Its a clean install or an upgrade from mga 6? What image do you use for make the install? Also do you have freespace? df -h (In reply to katnatek from comment #11) > Its a clean install or an upgrade from mga 6? > What image do you use for make the install? It was a clean install on bare metal of Mageia 7.1. >Also do you have freespace? About 786GB. Ryzen 3700x, X570 chipset, 32GB RAM. (In reply to M D from comment #8) > (In reply to Marja Van Waes from comment #7) > > Hi M D, > > > > If you reinstall mypaint-brushes with: > > > > urpmi --replacepkgs mypaint-brushes > > > > Does the bug then occur again? > > Yes, unfortunately it does. And if you reinstall all gimp and mypaint-brushes packages that you have? Assigning to our Gimp maintainer, btw, if reinstalling gimp etc also doesn't work then he might know what to do or how to better debug this. @ katnatek Thanks for your help so far :-) Assignee:
bugsquad =>
shlomif urpmi --replacepkgs gimp-2.10.10-1.mga7 gimp-data-extras-2.0.2-10.mga7 gimp-help-en-2.8.2-6.mga7 gimp-plugin-gmic-2.5.7-1.mga7 gimp-python-2.10.10-1.mga7 lib64gimp2.0_0-2.10.10-1.mga7 ufraw-gimp-0.22-11.mga7 No change in behavior.... same problem... (In reply to M D from comment #15) > urpmi --replacepkgs gimp-2.10.10-1.mga7 gimp-data-extras-2.0.2-10.mga7 > gimp-help-en-2.8.2-6.mga7 gimp-plugin-gmic-2.5.7-1.mga7 > gimp-python-2.10.10-1.mga7 lib64gimp2.0_0-2.10.10-1.mga7 > ufraw-gimp-0.22-11.mga7 > > No change in behavior.... same problem... gimp works fine in vbox in an mga 7.1 x64 xfce install (from the livedvd) - out of the box. Your issue may be hardware related and noone else can reproduce it. (In reply to Shlomi Fish from comment #16) > (In reply to M D from comment #15) > > urpmi --replacepkgs gimp-2.10.10-1.mga7 gimp-data-extras-2.0.2-10.mga7 > > gimp-help-en-2.8.2-6.mga7 gimp-plugin-gmic-2.5.7-1.mga7 > > gimp-python-2.10.10-1.mga7 lib64gimp2.0_0-2.10.10-1.mga7 > > ufraw-gimp-0.22-11.mga7 > > > > No change in behavior.... same problem... > > gimp works fine in vbox in an mga 7.1 x64 xfce install (from the livedvd) - > out of the box. Your issue may be hardware related and noone else can > reproduce it. Although new, this system has otherwise been very stable- running 24x7 for over a week now. I will try a live version of a different distro (not in a VM), and also boot into Mageia 5 (I have a hard drive with a previous install) and see if it is repeatable. Might take me a while before I have time. Thanks Well, that was interesting. I had to find a live distro that was updated enough to run on an AMD Ryzen 9/3000 system. I selected Fedora 30 Cinnamon respin 20190809. Booted the live distro, set repos, downloaded and installed GIMP. Gimp 2.10.8-5 Kernel 5.2.6-200 It locks up in exactly the same way and at exactly the same spot.... on trying to load mybrushes! So this looks to be upstream and/or something with this new hardware (that somehow doesn't affect ANY other program). Should I report this to Gimp? Re-assigning globally due to change to no specific maintainer. CC:
(none) =>
geiger.david68210, pterjan 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) =>
OLD |