Ubuntu and GIMP crash, where to start?

random110 · 05-16-2015, 08:12 PM

I don't know where to start searching for a solution to this problem. I am having frequent crashes in GIMP which is a problem for me as I do art and design work, not to mention I am screencasting!

1 - The computer I'm using is specifically built for linux, namely ubuntu, so I will assume that the hardware and drivers are the best they can be.

2 - When GIMP crashes I look in syslog and see varied reports including segfault or kernel problems.

3 - There doesn't seem to be a specific error log for GIMP???

I haven't had need or desire to file a bug report in many years, I am not sure where I should go for help to make this problem stop.

The usual culprit was reported as "segfault" in syslog, and now I can not even open an image without a crash followed by the following in syslog.

Code:

May 16 21:01:11 dream-gears kernel: [327960.470955]       Tainted: P           OE 3.16.0-37-generic #51~14.04.1-Ubuntu
May 16 21:01:11 dream-gears kernel: [327960.470956] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 16 21:01:11 dream-gears kernel: [327960.470958] gimp-2.8        D ffff88026ec130c0     0 17614   2258 0x00000004
May 16 21:01:11 dream-gears kernel: [327960.470962]  ffff8801b6153b38 0000000000000086 ffff88021a06dbb0 ffff8801b6153fd8
May 16 21:01:11 dream-gears kernel: [327960.470965]  00000000000130c0 00000000000130c0 ffff88022a5d4750 ffff8800362f9a00
May 16 21:01:11 dream-gears kernel: [327960.470968]  ffff88024b414000 ffff8801b6153b60 ffff8800362f9ae0 ffff8800362f9a00
May 16 21:01:11 dream-gears kernel: [327960.470971] Call Trace:
May 16 21:01:11 dream-gears kernel: [327960.470978]  [<ffffffff817691a9>] schedule+0x29/0x70
May 16 21:01:11 dream-gears kernel: [327960.470984]  [<ffffffff812c0965>] __fuse_request_send+0x115/0x280
May 16 21:01:11 dream-gears kernel: [327960.470989]  [<ffffffff810b4e50>] ? prepare_to_wait_event+0x100/0x100
May 16 21:01:11 dream-gears kernel: [327960.470993]  [<ffffffff812c0ae2>] fuse_request_send+0x12/0x20
May 16 21:01:11 dream-gears kernel: [327960.470997]  [<ffffffff812c4d24>] fuse_dentry_revalidate+0x194/0x350
May 16 21:01:11 dream-gears kernel: [327960.471003]  [<ffffffff811deb7d>] lookup_fast+0x26d/0x2c0
May 16 21:01:11 dream-gears kernel: [327960.471007]  [<ffffffff811e17b9>] link_path_walk+0x1d9/0x8a0
May 16 21:01:11 dream-gears kernel: [327960.471012]  [<ffffffff8132bc5b>] ? apparmor_file_alloc_security+0x5b/0x180

Although after a reboot, I'm sure that all will be fine again, but I would rather not have a crash "ever", if that is possible.

any advice, random feedback or commentary all appreciated.

frankbell · 05-16-2015, 09:35 PM

What is the make/model computer and what version of the GIMP?

Have you looked in /var/log/messages?

Edit: Also, is there any pattern to (that is, what are you doing when) the GIMP crashes?

ardvark71 · 05-16-2015, 09:48 PM

Hi...

Also, would you open a terminal and post the results of...

Code:

lspci -nnk

Thanks!

random110 · 05-16-2015, 09:53 PM

Quote:

Originally Posted by frankbell

What is the make/model computer and what version of the GIMP?

Have you looked in /var/log/messages?

1 - It's a System76 Bonobo (https://system76.com/laptops/bonobo) just bought a month ago.

2 - Gimp 2.8.14 which is latest I believe. I did update if from 2.8.10 (or earlier) after the crashes started, which stopped crashing significantly, but I did still have a crash after the upgrade.

3 - I have also had a lot of crashes in Chrome, so I went back to Firefox which seems stable, at least much more than Chrome.

4 - When Gimp crashes, all other software seems fine.

5 - There is no /var/log/messages in my system....? plenty of other logs, but not this one...

random110 · 05-16-2015, 09:56 PM

Quote:

Originally Posted by ardvark71

Hi...

Also, would you open a terminal and post the results of...

Code:

lspci -nnk

Thanks!

Sure, here it is! Thanks.

Code:

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller [8086:0c04] (rev 06)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06)
	Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: mei_me
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5)
	Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d5)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5)
	Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [8086:8c18] (rev d5)
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller [8086:8c4b] (rev 05)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:13d8] (rev a1)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:0fbb] (rev a1)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: snd_hda_intel
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5289] (rev 01)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: rtsx_pci
03:00.2 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0a)
	Subsystem: CLEVO/KAPOK Computer Device [1558:0376]
	Kernel driver in use: r8169
04:00.0 Network controller [0280]: Intel Corporation Wireless 3160 [8086:08b3] (rev 83)
	Subsystem: Intel Corporation Dual Band Wireless-AC 3160 [8086:0070]
	Kernel driver in use: iwlwifi

frankbell · 05-16-2015, 10:02 PM

If there is no /var/log/messages in your system, it's because Ubuntu has decided to call it something else. I've noticed in Mint, which I am running on one computer, that canonical (you will pardon the expression) names of log files have been changed for as far as I can see no good reason.

What is the output of

Code:

ls /var/log

For comparison purposes, here is what I get on this here Slackware computer:

Code:

$ ls /var/log
ConsoleKit      cron.3   dmesg      maillog.3   packages          secure.1   spooler.3  vbox-install.log
Xorg.0.log      cron.4   faillog    maillog.4   pm-powersave.log  secure.2   spooler.4  vbox-uninstall.log
Xorg.0.log.old  cups     httpd      messages    removed_packages  secure.3   syslog     wtmp
btmp            debug    iptraf-ng  messages.1  removed_scripts   secure.4   syslog.1
btmp.1          debug.1  lastlog    messages.2  sa                setup      syslog.2
cron            debug.2  maillog    messages.3  samba             spooler    syslog.3
cron.1          debug.3  maillog.1  messages.4  scripts           spooler.1  syslog.4
cron.2          debug.4  maillog.2  nfsd        secure            spooler.2  uucp

Aside: The reason I've purchased my native Linux computers from Zareason is that I was able to get them without Ubuntu. Ubuntu lost me with Unity, but that's just me.

random110 · 05-16-2015, 10:11 PM

Quote:

Originally Posted by frankbell

If there is no /var/log/messages in your system, it's because Ubuntu has decided to call it something else. I've noticed in Mint, which I am running on one computer, that canonical (you will pardon the expression) names of log files have been changed for as far as I can see no good reason.
...

It seems Ubuntu has removed /messages and now puts all /messages content in with syslog. (ref: http://askubuntu.com/questions/51265...r-log-messages)

But here is output of ls anyway:

Code:

alternatives.log    gpu-manager.log           pm-powersave.log.1
alternatives.log.1  hp                        pm-suspend.log
apache2             installer                 pm-suspend.log.1
apt                 kern.log                  prime-offload.log
auth.log            kern.log.1                prime-supported.log
auth.log.1          kern.log.2.gz             samba
auth.log.2.gz       kern.log.3.gz             speech-dispatcher
auth.log.3.gz       kern.log.4.gz             syslog
auth.log.4.gz       lastlog                   syslog.1
boot.log            lightdm                   syslog.2.gz
ConsoleKit          mysql                     syslog.3.gz
cups                mysql.err                 syslog.4.gz
dist-upgrade        mysql.log                 syslog.5.gz
dmesg               mysql.log.1.gz            syslog.6.gz
dmesg.0             mysql.log.2.gz            syslog.7.gz
dmesg.1.gz          mysql.log.3.gz            udev
dmesg.2.gz          mysql.log.4.gz            unattended-upgrades
dmesg.3.gz          mysql.log.5.gz            upstart
dmesg.4.gz          mysql.log.6.gz            wtmp
dpkg.log            mysql.log.7.gz            wtmp.1
dpkg.log.1          nvidia-prime-upstart.log  Xorg.0.log
fontconfig.log      oem-config.log            Xorg.0.log.old
fsck                pm-powersave.log

John VV · 05-17-2015, 01:31 AM

so MORE than just gimp is crashing

then it is not a issue with Gimp but with your operating system or hardware

did you recently UPGRADE major versions of ubuntu ?

Quote:

Gimp 2.8.14 which is latest I believe. I did update if from 2.8.10 (or earlier) after the crashes started, which stopped crashing significantly, but I did still have a crash after the upgrade.

how did you go about this ?

for "the Gimp" I build the current stable AND the current development nightly ( the odd number 2.9)

random110 · 05-17-2015, 01:56 AM

Quote:

Originally Posted by John VV

so MORE than just gimp is crashing

...

On the whole, everything seems to be working fine, in fact when Chrome was crashing, I genuinely felt as though that was Chrome's own fault. Firefox has been running stable to support that theory.

I did not, and will not do a major upgrade, I am sticking with 14.04 because of the trailing "LTS" in its title, as I don't like to reinstall OS'es from scratch every 6 months after breaking them.

excuse my sarcasm please.

I installed the latest Gimp, which will not come through 14.04 packaging system, by adding a PPA to my repos.

Gimp was previously crashing MUCH MORE often before the update to 2.8.14, now it seems to be better but I had this sudden crash today in the middle of a screencast video (very frustrating and much work lost) and so I wanted to investigate and hopefully fix this problem once and for all.

I hope that answers all of your questions, and feel free to ask more. And do you think I should register a bug? Or can we not determine at this point whether it is Gimp or Ubuntu?

syg00 · 05-17-2015, 02:15 AM

No good guessing - open a bug against Ubuntu. They'll want that trace.