Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #197261 > unrolled thread

Gimp broken in Debian Sid?

Back to article view | Back to linux.debian.user

Contents

  Gimp broken in Debian Sid? Thierry Rascle <thierr26@free.fr> - 2018-07-06 08:00 +0200
    Re: Gimp broken in Debian Sid? Joe <joe@jretrading.com> - 2018-07-06 08:40 +0200
      Re: Gimp broken in Debian Sid? Thierry Rascle <thierr26@free.fr> - 2018-07-07 00:10 +0200
        Re: Gimp broken in Debian Sid? Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-07-07 00:50 +0200
          Re: Gimp broken in Debian Sid? Thierry Rascle <thierr26@free.fr> - 2018-07-07 18:10 +0200
            Re: Gimp broken in Debian Sid? Thierry Rascle <thierr26@free.fr> - 2018-07-08 16:30 +0200
    Re: Gimp broken in Debian Sid? Michael Wagner <wagner_m_bremen@web.de> - 2018-07-06 22:20 +0200
      Re: Gimp broken in Debian Sid? Ben Caradoc-Davies <ben@transient.nz> - 2018-07-07 04:40 +0200
        Re: Gimp broken in Debian Sid? Thierry Rascle <thierr26@free.fr> - 2018-07-07 17:40 +0200
          Re: Gimp broken in Debian Sid? Ben Caradoc-Davies <ben@transient.nz> - 2018-07-08 00:40 +0200
            Re: Gimp broken in Debian Sid? Thierry Rascle <thierr26@free.fr> - 2018-07-08 17:30 +0200

#197261 — Gimp broken in Debian Sid?

Hi,

I'm using Debian Sid. Gimp does not seem to work any more (the user
interface does not show up). I've tried in Xmonad and in Openbox.

I have no idea what causes this. I don't see any error message.

Does anyone else have the same problem ?

Thanks!

Thierry

[toc] | [next] | [standalone]

#197263

On Fri, 6 Jul 2018 07:58:41 +0200
Thierry Rascle <thierr26@free.fr> wrote:

> Hi,
> 
> I'm using Debian Sid. Gimp does not seem to work any more (the user
> interface does not show up). I've tried in Xmonad and in Openbox.
> 
> I have no idea what causes this. I don't see any error message.
> 
> Does anyone else have the same problem ?
> 
> Thanks!
> 
> Thierry
> 

No. 2.10 behaves differently, and I find the toolbox much harder to
use, as I only use GIMP occasionally, but it's working. My sid is up to
date, but of course will be very different from your sid.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#197296

On Fri, 6 Jul 2018 07:33:16 +0100
Joe <joe@jretrading.com> wrote:

> On Fri, 6 Jul 2018 07:58:41 +0200
> Thierry Rascle <thierr26@free.fr> wrote:
> 
> > Hi,
> > 
> > I'm using Debian Sid. Gimp does not seem to work any more (the user
> > interface does not show up). I've tried in Xmonad and in Openbox.
> > 
> > I have no idea what causes this. I don't see any error message.
> > 
> > Does anyone else have the same problem ?
> > 
> > Thanks!
> > 
> > Thierry
> >   
> 
> No. 2.10 behaves differently, and I find the toolbox much harder to
> use, as I only use GIMP occasionally, but it's working. My sid is up
> to date, but of course will be very different from your sid.
> 

Yes, I noticed that the toolbox has changed with 2.10 two months ago.
There was also a new issue with the gimp-ufraw plugin, forcing the user
to use the standalone ufraw application instead. But Gimp was usable.

Now it is totally unusable for me. A 'ps -ef' shows a gimp process
running but I don't see any windows in any workspace. A 'xwininfo -tree
-root' does not list any Gimp windows. Launching Gimp from a terminal
does not give any error message.

-- 
Thierry

[toc] | [prev] | [next] | [standalone]

#197298

On 7/6/18, Thierry Rascle <thierr26@free.fr> wrote:
> On Fri, 6 Jul 2018 07:33:16 +0100
> Joe <joe@jretrading.com> wrote:
>
>> On Fri, 6 Jul 2018 07:58:41 +0200
>> Thierry Rascle <thierr26@free.fr> wrote:
>>
>> > Hi,
>> >
>> > I'm using Debian Sid. Gimp does not seem to work any more (the user
>> > interface does not show up). I've tried in Xmonad and in Openbox.
>> >
>> > I have no idea what causes this. I don't see any error message.
>> >
>> > Does anyone else have the same problem ?
>> >
>> > Thanks!
>> >
>> > Thierry
>> >
>>
>> No. 2.10 behaves differently, and I find the toolbox much harder to
>> use, as I only use GIMP occasionally, but it's working. My sid is up
>> to date, but of course will be very different from your sid.
>>
>
> Yes, I noticed that the toolbox has changed with 2.10 two months ago.
> There was also a new issue with the gimp-ufraw plugin, forcing the user
> to use the standalone ufraw application instead. But Gimp was usable.
>
> Now it is totally unusable for me. A 'ps -ef' shows a gimp process
> running but I don't see any windows in any workspace. A 'xwininfo -tree
> -root' does not list any Gimp windows. Launching Gimp from a terminal
> does not give any error message.


A half-baked memory is coming back about Thunar giving me ghost
instances in unstable or Sid, I don't remember which..

I can't quite remember, but it was something about Thunar wasn't being
properly shut down when I rebooted. Yeah, I know, I don't know if
Thunar was still open when I rebooted or if it wasn't completely
shutting down and then the reboot still didn't finish the shut down
process on top of that.

I think I learned that because Thunar wasn't coming coming up for me
in a similar way as is being described here about GIMP. However it was
happening is why there was a "ghost" lingering in the background *for
me*. I never got around to reporting a bug, and it eventually resolved
itself via some one or another upgrades back then (maybe a couple
years ago?).

With respect to dealing with that ghost, I have two things I do in
these kinds of instances. The first one I do is kill that ghost
instance then relaunch the problem program from within a terminal
window. Sometimes you get lucky and see a bunch of error messages that
can possibly help solve the problem.

The second thing I do... out of exasperation... is purge the problem
program THEN secondarily ALSO PURGE all the various dependency
packages. Apt-get is very neighborly about presenting that dependency
list when a user is trying to upgrade or install just after having
purged a primary package.

There's also a remove option instead of purge that may be more
appropriate. I just like the sound of *PURGE IT!* and have never had
any problems going that route. :)

The reason I purge instead of "install --reinstall" is because
"install --reinstall" *ONLY* reinstalls the specifically named
package, i.e. *no dependencies*. There may be an option that triggers
the reinstallation of dependencies, too, but I've never encountered it
(yet).

I just went into "man apt-get" for a second. That reminded me that
users sometimes have good luck simply deleting existing config files
and NOT the whole program.

Those config files are the kind found in our /home directories unless
we've defined them to set up some place else. They're sometimes
(often?) only visible if we toggle CTRL+H on and off in our favorite
file managers.

If that seems like a friendly option, I'd make a backup copy of the
files I intend to delete just in case that doesn't work/turns out to
be a wasted effort. Moving those out of the way while simultaneously
making a backup is as simple as renaming the file or entire folder. We
can call them anything we want, but I tend to like to rename mine with
the date last used as a point of reference.

One of the things I've learned while deliberately pushing my copies to
the limit here is that there can be upgrade/downgrade(/crossgrade)
incompatibility problems with those config files. I learned that while
working through problems with the Opera-Beta browser.

Once the config file(s) became "contaminated" with new features while
older features started falling by the wayside, that's when I first
started seeing the problems AND then tied OTHER problems to how config
files MIGHT cause our programs' success and failures over a very
extended period of time...

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#197323

On Fri, 6 Jul 2018 18:44:20 -0400
Cindy-Sue Causey <butterflybytes@gmail.com> wrote:


> 
> With respect to dealing with that ghost, I have two things I do in
> these kinds of instances. The first one I do is kill that ghost
> instance then relaunch the problem program from within a terminal
> window. Sometimes you get lucky and see a bunch of error messages that
> can possibly help solve the problem.

Even after killing the instance or after rebooting, Gimp still doesn't
work. No error message on the command line.

> 
> The second thing I do... out of exasperation... is purge the problem
> program THEN secondarily ALSO PURGE all the various dependency
> packages. Apt-get is very neighborly about presenting that dependency
> list when a user is trying to upgrade or install just after having
> purged a primary package.

I've tried purging Gimp and some dependencies, and then reinstalling
Gimp but it still doesn't work:

    apt-get purge ufraw gimp gimp-data gimp-ufraw libgimp2.0 \
        libgimp2.0-dev libgimp2.0-doc

    apt-get autoremove

    apt-get install gimp

I have two Debian sid installations: One main installation (on my
internal hard drive) and a secondary installation (on an external USB
hard drive). I dist-upgrade those two installations almost
simultaneously, approximately once a week. So they're like twins. I
don't use Gimp regularly on the secondary installation but I've
verified: it's also affected by the problem.

I will probably end up doing a system reinstall on the external
hard drive and see what happens.

Thank you all anyway for your help!

-- 
Thierry

[toc] | [prev] | [next] | [standalone]

#197348

On Sat, 7 Jul 2018 18:04:31 +0200
Thierry Rascle <thierr26@free.fr> wrote:


> I've tried purging Gimp and some dependencies, and then reinstalling
> Gimp but it still doesn't work:
> 
>     apt-get purge ufraw gimp gimp-data gimp-ufraw libgimp2.0 \
>         libgimp2.0-dev libgimp2.0-doc
> 
>     apt-get autoremove
> 
>     apt-get install gimp

I've done this purge / autoremove / install sequence again, adding a
purge of the configuration files of absolutely all uninstalled packages
on my system after the autoremove, without success.

> 
> I have two Debian sid installations: One main installation (on my
> internal hard drive) and a secondary installation (on an external USB
> hard drive). I dist-upgrade those two installations almost
> simultaneously, approximately once a week. So they're like twins. I
> don't use Gimp regularly on the secondary installation but I've
> verified: it's also affected by the problem.
> 
> I will probably end up doing a system reinstall on the external
> hard drive and see what happens.

I've done a fresh install of Debian stable + dist-upgrade to Sid on my
external hard drive and Gimp works on this installation.


-- 
Thierry

[toc] | [prev] | [next] | [standalone]

#197292

[Multipart message — attachments visible in raw view] — view raw

On Jul 06, 2018 um 07:58:41, Thierry Rascle wrote:
> I'm using Debian Sid. Gimp does not seem to work any more (the user
> interface does not show up). I've tried in Xmonad and in Openbox.
> 
> I have no idea what causes this. I don't see any error message.
> 
> Does anyone else have the same problem ?
> 
Hello Thierry,

I'm using Debian Testing with gimp 2.10.2-1 from unstable and it works.

Michael

[toc] | [prev] | [next] | [standalone]

#197304

On 07/07/18 08:13, Michael Wagner wrote:
> On Jul 06, 2018 um 07:58:41, Thierry Rascle wrote:
>> I'm using Debian Sid. Gimp does not seem to work any more (the user
>> interface does not show up). I've tried in Xmonad and in Openbox.
>> I have no idea what causes this. I don't see any error message.
>> Does anyone else have the same problem ?
> Hello Thierry,
> I'm using Debian Testing with gimp 2.10.2-1 from unstable and it works.
> Michael

Same working for me under Xfce.

There have been a bunch of styling changes in 2.10.

Thierry, what desktop theme are you using? You could try moving your 
~/.config/GIMP/2.10 out of the way in case it has fallen down and cannot 
get up.

Do you get any error messages if you start gimp at the command line?

Kind regards,

-- 
Ben Caradoc-Davies <ben@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

[toc] | [prev] | [next] | [standalone]

#197322

On Sat, 7 Jul 2018 14:33:37 +1200
Ben Caradoc-Davies <ben@transient.nz> wrote:

> On 07/07/18 08:13, Michael Wagner wrote:
>  [...]  
>  [...]  
>  [...]  
> 
> Same working for me under Xfce.
> 
> There have been a bunch of styling changes in 2.10.
> 
> Thierry, what desktop theme are you using? You could try moving your 
> ~/.config/GIMP/2.10 out of the way in case it has fallen down and
> cannot get up.
> 
> Do you get any error messages if you start gimp at the command line?
> 
> Kind regards,
> 

After removing ~/.config/GIMP/2.10, Gimp still doesn't work. And
there's no message on the command line, even when using the --verbose
option.

-- 
Thierry

[toc] | [prev] | [next] | [standalone]

#197329

On 08/07/18 03:36, Thierry Rascle wrote:
> After removing ~/.config/GIMP/2.10, Gimp still doesn't work. And
> there's no message on the command line, even when using the --verbose
> option.

I would use ltrace to see where it is hanging:

ltrace -tt -n4 -S gimp

You will need to install ltrace and likely the debug packages for 
wherever it is hanging.

Kind regards,

-- 
Ben Caradoc-Davies <ben@transient.nz>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

[toc] | [prev] | [next] | [standalone]

#197350

On Sun, 8 Jul 2018 10:37:10 +1200
Ben Caradoc-Davies <ben@transient.nz> wrote:

> I would use ltrace to see where it is hanging:
> 
> ltrace -tt -n4 -S gimp
> 
> You will need to install ltrace and likely the debug packages for 
> wherever it is hanging.

ltrace -tt -n4 -S /usr/bin/gimp outputs a lot lines and the last one is
like:

10:01:04.820439     SYS_futex(0x7f8d0648a9d0, 0, 6356, 0

strace -f /usr/bin/gimp also outputs a lot lines and the last ones are
like:

[pid  6789] futex(0x7f1d25b6b9d0, FUTEX_WAIT, 6791, NULL <unfinished ...>
[pid  6791] futex(0x7f1d3d401968, FUTEX_WAIT_PRIVATE, 2, NULL

'ps aux' tells me that one of the pid is gimp, and the other one is not
existing. So it could be that Gimp is just waiting for a dead process.
I don't know how to identify this dead process.

I looked for a way to force Gimp to run on a single thread and Google
pointed me to this URL:

https://superuser.com/questions/692138/how-to-force-a-process-to-run-on-a-single-thread-only-with-numactl

So I tried:

numactl --physcpubind=+1 /usr/bin/gimp

and Gimp works :-)

Of course I still don't know what the root cause of the problem is...

Many many thanks for your help and suggestions :-)

-- 
Thierry

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web