| Summary: | GIMP will not start in Mga6-RC of Aug 13 2016 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Maurice Batey <maurice77> |
| Component: | RPM Packages | Assignee: | Shlomi Fish <shlomif> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gimp-2.8.18-1.mga6.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | strace of starting GIMP | ||
Created attachment 8351 [details]
strace of starting GIMP
Output of: strace -o gimp-no-start gimp
This on fresh install of Mga6-rc of Aug.13 2016 on real h/w non-EFI non-GPT nVidia desktop, using cloned Mga5 /home. N.B. If I hide the mba5 .gimp-2.8 directory, Gimp starts normally. Here are the contents of both directories, after hiding the cloned Mga5 directory: ls ~/.gimp-2.8 (constructed during normal Gimp startup) brushes/ curves/ environ/ gfig/ gradients/ levels/ palettes/ pluginrc sessionrc templates/ tmp/ toolrc colorrc dockrc fonts/ gflare/ gtkrc menurc parasiterc plug-ins/ tags.xml themerc tool-options/ unitrc controllerrc dynamics/ fractalexplorer/ gimpressionist/ interpreters/ modules/ patterns/ scripts/ templaterc themes/ tool-presets/ ls ~/.gimp-2.8-mga5 brushes/ dockrc fractalexplorer/ gradients/ menurc patterns/ print-settings templaterc tmp/ unitrc colorrc dynamics/ gfig/ gtkrc modules/ pluginrc scripts/ templates/ tool-options/ controllerrc environ/ gflare/ interpreters/ palettes/ plug-ins/ sessionrc themerc tool-presets/ curves/ fonts/ gimpressionist/ levels/ parasiterc print-page-setup tags.xml themes/ toolrc Assigning to the gimp maintainer CC:
(none) =>
marja11 Hi Maurice, (In reply to Maurice Batey from comment #3) > N.B. If I hide the mba5 .gimp-2.8 directory, Gimp starts normally. > > Here are the contents of both directories, after hiding the cloned Mga5 > directory: > GIMP starts fine here in Mageia 6. What you can try doing is bisecting (see https://en.wikipedia.org/wiki/Bisection_(software_engineering) ) the offending directory tree and its contents until you reach the problematic configuration directive or directives. Please do that and report your findings here. Regards, -- Shlomi > What you can try doing is bisecting (see https://en.wikipedia.org
> /wiki/Bisection_(software_engineering) ) the offending directory tree and its > contents until you reach the problematic configuration directive or directives.
Sounds great, if only someone could explain how to mechanise it!
I will take a look at a manual slog through the set of files...
OK - I've done a visual compare of the list of files in the Mga5 .gimp-2.8 and the ,gimp-2.8 that gets generated by Gimp at startup if none there, and noticed 2 files in the Mga5 version that are not in the generated version: /print-page-setup /print-settings If I delete those 2 files from the Mga5 version and use that as .gimp-2.8, then Gimp does start normally!!! ------------------------------------------ [print-page-setup] PPDName=Letter DisplayName=US Letter Width=215.89999389648438 Height=279.39999389648438 MarginTop=3.1749999999999998 MarginBottom=3.1749999999999998 MarginLeft=3.1749999999999998 MarginRight=3.1749999999999998 Orientation=portrait ------------------------------------------ [meta] major-version=0 minor-version=4 [print-settings] reverse=false print-pages=ranges page-ranges=0 collate=false printer=default page-set=all scale=100 [image-setup] unit=2 center-mode=3 use-full-page=false crop-marks=false ---------------------------------------- I trust this helps sort this out... Hi Maurice, (In reply to Maurice Batey from comment #7) > OK - I've done a visual compare of the list of files in the Mga5 .gimp-2.8 > and the ,gimp-2.8 that gets generated by Gimp at startup if none there, and > noticed 2 files in the Mga5 version that are not in the generated version: > > /print-page-setup > /print-settings > > If I delete those 2 files from the Mga5 version and use that as .gimp-2.8, > then Gimp does start normally!!! > With these two files placed in ~/.gimp-2.8/ with their specified contents, gimp starts perfectly fine here on my mgav6 x86-64 system with Xfce. Can you share the rest of .gimp-2.8-mga5 (you can email it to me at shlomif@shlomifish.org and shlomif@gmail.com ) or do you just want to close this bug out of lack of further interest? Regards, -- Shlomi > ------------------------------------------ > [print-page-setup] > PPDName=Letter > DisplayName=US Letter > Width=215.89999389648438 > Height=279.39999389648438 > MarginTop=3.1749999999999998 > MarginBottom=3.1749999999999998 > MarginLeft=3.1749999999999998 > MarginRight=3.1749999999999998 > Orientation=portrait > ------------------------------------------ > [meta] > major-version=0 > minor-version=4 > [print-settings] > reverse=false > print-pages=ranges > page-ranges=0 > collate=false > printer=default > page-set=all > scale=100 > > [image-setup] > unit=2 > center-mode=3 > use-full-page=false > crop-marks=false > ---------------------------------------- > > I trust this helps sort this out... > Can you share the rest of .gimp-2.8-mga5 (you can email it to me at
> shlomif@shlomifish.org and shlomif@gmail.com )
What mechanism are you thinking of to pass that directory over?
(I can't put the whole thing in Dropbox).
Hi Maurice, sorry for the extremely late reply. (In reply to Maurice Batey from comment #9) > > Can you share the rest of .gimp-2.8-mga5 (you can email it to me at > > shlomif@shlomifish.org and shlomif@gmail.com ) > > What mechanism are you thinking of to pass that directory over? > > (I can't put the whole thing in Dropbox). You can try tarballing it and sending the .tar.xz file over. You can use the following command: tar -cavf my-gimp-dir.tar.xz ~/.gimp-2.8/ Status:
NEW =>
ASSIGNED Done! (In reply to Maurice Batey from comment #11) > Done! Thanks! I got the tarball by email and replace my .gimp-2.8 directory with its contents (temporarily) and GIMP starts perfectly fine with it in my home-dir (except for quite a few GEGL warnings on the command line, but that seems ordinary), and I've ran some operations of it on a sample image successfully. Are you sure it's the right problematic directory ? Well, Shlomi, I've now tried Mga6 GIMP with both its own .gimp-2.8 directory and that of Mga5, and it works in both cases. The only difference since this bug was raised is that gimp-2.8.18-1.mga6.src.rpm has been updated to 2-8.18-3.mga6, so guess the problem had thereby been solved! (In reply to Maurice Batey from comment #13) > Well, Shlomi, I've now tried Mga6 GIMP with both its own .gimp-2.8 directory > and that of Mga5, and it works in both cases. > > The only difference since this bug was raised is that > gimp-2.8.18-1.mga6.src.rpm has been updated to 2-8.18-3.mga6, so guess the > problem had thereby been solved! Thanks! I'm going to close this bug as WORKS FOR ME Then. Status:
ASSIGNED =>
RESOLVED |
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Enter 'gimp' in terminal session (or click on GIMP desktop icon) 2. Nothing happens! In terminal session: $ gimp $ (after 3 seconds)