Arch Linux

[umby213]

Salve a tutti... Scopro oggi che Gimp (non lo uso molto quindi non so bene da quando faccia così) è inutilizzabile... crassha qualunque cosa si tenti di fare... il mio sistema è aggiornato e uso [testing], [community-testing], [multilib-testing]... qualcuno ha lo stesso problema?

Codice: Seleziona tutto

┌─(/home/umby)
└─(umberto)-(umby)» gimp
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 10157 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(script-fu:20453): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error


PS.. ho provato anche gimp-devel ma non cambia. Inoltre anche gimp --sync non da output diverso da questo...

[archmat]

Ciao umby io ho gimp 2.6.12 e funziona benissimo.

PS: non ho però alcun repo testing abilitato

[veleno77]

Sono appena passato a gimp-devel 2.7.5 e funziona tranquillamente, ma anche la versione precedente funzionava... errori simili li ho visti in rete in relazione però o a cairo o ai fonts (pango) davano un ulteriore errore su questi due, mentre per il badAllock in rete ho letto si riferisca comunque all'ambiente X.. forse con testing attivato hai qualche problema a farlo funzionare

[umby213]

mmm... ora faccio dei tentativi... per prima cosa downgrade di cairo che la versione in testing è quella con la patch -xcb incorporata

Ps. bella foto veleno

EDIT: ho disabilitato testing, fatto downgrade massiccio, ricompilato cairo-xcb e riavviato... il risultato è lo stesso

[veleno77]

ahahah grazie ... su archlinuxfr c'è cairo-xcb 1.10.2-4 prova ad usare quello, ma non so se dipenda da quello, poi a cosa ti serve quel pacchetto?

[umby213]

cairo-xcb mi serve perchè è una dipendenza fondamentale di awesome... recentemente la patch xcb è entrata a pieno titolo nello sviluppo dell'upstream infatti la versione di cairo in testing sostituisce benissimo cairo-xcb da aur o repo non ufficiali (come archlinuxfr)...

comunque ricapitolando: ora ho disabilitato del tutto testing ma il problema rimane. Inoltre ho anche provato il downgrade di xorg-xserver ma gimp continua a crasshare

Ho riprovato anche gimp-devel... ma l'errore è lo stesso

[veleno77]

hai qualche plugin per sript-fu per caso installato, non so magari provare ad eliminare bene i file di configurazione di gimp nella propria home soprattutto quelli degli script

[umby213]

non so cosa siano gli script-fu.. gimp lo uso davvero poco...
ho provato comunque a eliminale sia ~/.gimp-2.6 e ~/.gimp-2.7...
sempre uguale... ho anche provato a disinstallarlo con tutte le dipendenze e reinstallarlo ma niente... l'errore è sempre quello... può dipendere secondo te dal wm?

[veleno77]

ma quello mi è venuto in mente in base all'ultimo messaggio di errore:

Codice: Seleziona tutto

(script-fu:20453): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error

se dipende dal wm lo vedi subito avvia twm che è installato di default e vedi se li si avvia

[umby213]

proverò... stasera non ho più testa

[umby213]

ho fatto un paio di tentativi (twm e openbox)... l'errore e il crash non dipendono dal WM in uso può essere che manchi una dipendenza?

[4javier]

prova a dare gimp --verbose e posta l'output.

[umby213]

ciao... eccolo...

Codice: Seleziona tutto

┌─(/home/umby)
└─(umberto)-(umby)» gimp --verbose
This is a development version of GIMP.  Debug messages may appear here.

INIT: gimp_load_config
Parsing '/home/umby/.gimp-2.7/unitrc'
Parsing '/etc/gimp/2.0/gimprc'
Parsing '/home/umby/.gimp-2.7/gimprc'
gimp_composite: verbose=no
Processor instruction sets: +mmx +sse +sse2 -3dnow -altivec -vis
Adding theme 'Small' (/usr/share/gimp/2.0/themes/Small)
Adding theme 'Default' (/usr/share/gimp/2.0/themes/Default)
Writing '/home/umby/.gimp-2.7/themerc'
Trying splash '/home/umby/.gimp-2.7/gimp-splash.png' ... failed
Trying splash '/usr/share/gimp/2.0/images/gimp-splash.png' ... OK
INIT: gimp_initialize
INIT: gimp_real_initialize
INIT: gui_initialize_after_callback
INIT: gimp_restore
Parsing '/home/umby/.gimp-2.7/parasiterc'
Loading 'brush factory' data
Loading 'dynamics factory' data
Loading 'pattern factory' data
Loading 'palette factory' data
Loading 'gradient factory' data
Loading fonts
Loading 'tool preset factory' data
Parsing '/home/umby/.gimp-2.7/templaterc'
Parsing '/home/umby/.gimp-2.7/modulerc'
INIT: gui_restore_callback
clipboard: writable pixbuf format: image/png
clipboard: writable pixbuf format: image/tiff
clipboard: writable pixbuf format: image/x-icon
clipboard: writable pixbuf format: image/x-ico
clipboard: writable pixbuf format: image/x-win-bitmap
clipboard: writable pixbuf format: image/bmp
clipboard: writable pixbuf format: image/x-bmp
clipboard: writable pixbuf format: image/x-MS-bmp
clipboard: writable pixbuf format: image/jpeg
Parsing '/etc/gimp/2.0/sessionrc'
Parsing '/home/umby/.gimp-2.7/dockrc'
Parsing '/home/umby/.gimp-2.7/toolrc'
Parsing '/home/umby/.gimp-2.7/contextrc'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-rect-select-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-ellipse-select-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-free-select-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-fuzzy-select-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-by-color-select-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-iscissors-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-foreground-select-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-vector-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-color-picker-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-zoom-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-measure-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-move-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-align-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-crop-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-rotate-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-scale-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-shear-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-perspective-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-flip-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-cage-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-text-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-bucket-fill-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-blend-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-pencil-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-paintbrush-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-eraser-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-airbrush-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-ink-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-clone-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-heal-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-perspective-clone-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-convolve-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-smudge-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-dodge-burn-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-desaturate-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-color-balance-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-hue-saturation-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-colorize-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-brightness-contrast-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-threshold-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-levels-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-curves-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-posterize-tool'
Parsing '/home/umby/.gimp-2.7/tool-options/gimp-gegl-tool'
INIT: gimp_real_restore
Parsing '/home/umby/.gimp-2.7/pluginrc'
Starting extension: 'extension-script-fu'
INIT: gui_restore_after_callback
Parsing '/home/umby/.gimp-2.7/menurc'
Parsing '/home/umby/.gimp-2.7/devicerc'
Parsing '/home/umby/.gimp-2.7/controllerrc'
Parsing '/home/umby/.gimp-2.7/colorrc'
loading menu '/usr/share/gimp/2.0/menus/image-menu.xml' for /image-menubar
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 15510 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(script-fu:14445): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
┌─(/home/umby)
└─(umberto)-(umby)»                                 

ps è gimp-devel questo

[4javier]

prova gimp --debug-handlers

[umby213]

sia gimp che gimp-devel danno questo output...

Codice: Seleziona tutto

┌─(/home/umby)
└─(umberto)-(umby)» gimp --debug-handlers
/usr/lib/gimp/2.0/plug-ins/help-browser: error while loading shared libraries: libwebkitgtk-1.0.so.0: cannot open shared object file: No such file or directory

(gimp:15569): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 48459 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(script-fu:15758): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
gimp --debug-handlers  6,37s user 2,25s system 56% cpu 15,144 total
┌─(/home/umby)
└─(umberto)-(umby)»     

il primo errore sparisce installando libweckit... ma chrassha comunque

[4javier]

gimp --stack-trace-mode always

[umby213]

sempre il solito

Codice: Seleziona tutto

┌─(/home/umby)
└─(umberto)-(umby)» gimp --stack-trace-mode always
/usr/lib/gimp/2.0/plug-ins/help-browser: error while loading shared libraries: libwebkitgtk-1.0.so.0: can

(gimp:16395): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 18524 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(script-fu:16402): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
┌─(/home/umby)
└─(umberto)-(umby)»   

[4javier]

gimp --debug-handlers --stack-trace-mode always

[umby213]

sempre uguale

Codice: Seleziona tutto

┌─(/home/umby)
└─(umberto)-(umby)» gimp --debug-handlers --stack-trace-mode always
/usr/lib/gimp/2.0/plug-ins/help-browser: error while loading shared libraries: libwebkitgtk-1.0.so.0: can

(gimp:17224): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 17809 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(script-fu:17228): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
┌─(/home/umby)
└─(umberto)-(umby)»   

[4javier]

controlla se per caso qualcosa di inerente l'errore è finita nel log di xorg.
Ma perchè continua a darti l'errore su libwebkit?

[umby213]

ok controllo... l'errore di libwebkit me lo da perchè non ce l'ho installato...

[umby213]

Ho lanciato X dirigendo l'output su un file e il risultato è:

Codice: Seleziona tutto

X.Org X Server 1.12.1
Release Date: 2012-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.3.1-1-ARCH x86_64
Current Operating System: Linux umberto 3.3.1-1-ARCH #1 SMP PREEMPT Tue Apr 3 06:46:17 UTC 2012 x86_64
Kernel command line: root=/dev/sda2 ro radeon.agpmode=4
Build Date: 14 April 2012  07:09:45AM
 
Current version of pixman: 0.24.4
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 14 13:57:46 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

** (process:9497): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:9497): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:9497): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'

** (process:9496): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'

** (process:9496): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'

** (process:9496): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
[main.py:init_keys_events:154] Xlib backend needs python-xlib 0.15rc1 or higher

[main.py:init_notify:169] org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files
Exception AttributeError: "Notification instance has no attribute 'last_id'" in <bound method Notification.__del__ of <volti.notification.Notification instance at 0x190d128>> ignored
tint2 : nb monitor 1, nb monitor used 1, nb desktop 7
W: awesome: xerror:809: X error: request=ConfigureWindow, error=BadAlloc
xinit: connection to X server lost

waiting for X server to shut down XIO:  fatal IO error 11 (Risorsa temporaneamente non disponibile) on X server ":0"
      after 1291 requests (1291 known processed) with 0 events remaining.
real transparency off.... depth: 24
xRandr: Found crtc's: 2
xRandr: Linking output LVDS with crtc 0
icon with depth: 32
icon with depth: 32
E: awesome: a_xcb_io_cb:214: X server connection broke
Server terminated successfully (0). Closing log file.

xinit: unexpected signal 1


L'errore è evidentemente di Awesome, infatti ora gimp non crasha su twm... non so perchè.. anche riabilitando testing su twm sembra andare.. su awesome no... faccio ora qualche tentativo "liberando" completamente gimp dalle rigorose regole del tiling di awesome... non vorrei fosse quello


Edit: ho risolto... in pratica non avevo nessuna "rules" per gimp in rc.lua e questo lo faceva crashare. È bastato aggiungerla e ora va tutto bene...

[4javier]

Sono contento che tu abbia risolto. In realtà anzichè redirigere lo stderr, avresti potuto anche consultare una console reale. Ma così probabilmente è più comodo.

[umby213]

infatti l'ho "rediretto" per postarlo qui... comunque è una cosa stranissima questa... basta un rules a caso per non farlo crashare... mah...