Re: openshot: X Window System error
On Sun, 01 May 2016, G.Paulo wrote: > Agora, a parte curiosa: isto ocorre no Gnome e no KDE. Porém, ao rodar o > programa sob o Fluxbox, esta mensagem não aparece e o programa roda > normalmente! > > Buscando pela internet, achei várias coisas, mas em geral, neste caso, as > soluções são sempre associadas a temas do Gnome. Alterando esses temas, > porém, não dá resultado. Alem disso, certamente temas do Gnome não deveriam > afetar o KDE. Temas GTK afetam. Verifique isso. > Finalmente, a razão de insistir no Gnome é que o laptop é de uso de uma > criança. Usar o Fluxbox, nesse caso, seria exigir demais. É exatamente o contrário... criança aprende sem frescura. Adulto é que tem a mente engessada e hábitos arraigados. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Fwd: openshot: X Window System error
-- Forwarded message -- From: Rodolfo <rof20...@gmail.com> Date: 2016-05-01 13:36 GMT-04:00 Subject: Re: openshot: X Window System error To: "G.Paulo" <linu...@terra.com.br> O programa não conseguiu obter recursos para rodar, pode ser um bug no programa, pode ser pouca memória utilizada para o mesmo, dei uma olhada no fórum do launchpad e um cara postou 2 possíveis soluções: Thanks for the bug report and the testing. This is a tough one. This is not a common error, and infact, I have never seen it before. I did some research on the error, and it looks like an issue with your xorg setup, or possibly a video card driver issue. I have 2 suggestions: 1) try disabling desktop effects (although I doubt that will fix it) 2) look for an updated video card driver (probably not in the repository) If both of those don't work, you might need to post a bug report with Ubuntu or the Xorg project. I found this same error message being reported on many different video players (such as Mplayer, Xine, VLC, etc...). So, I don't think it's anything unique to OpenShot, ya know. Gook luck! Um outro usuário falou que a primeira solução funcionou -> https://answers.launchpad.net/openshot/+question/75010 Outro fórum pede pra desabilidar o compiz, mas o cara adicionou duas linhas no xorg.conf: Hi. It is a bug in Xorg. Edit the file /etc/X11/Xorg.conf. Reach the section "device" and add those lines: Option "Videoram" "65536" Option "Cachelines" "1980" then halt and restart x server Link: https://forums.opensuse.org/showthread.php/389147-X-Error-of-failed-request-BadAlloc-%28insufficient-resources Em 1 de maio de 2016 12:03, G.Paulo <linu...@terra.com.br> escreveu: > Saudações. > > Tenho tido problemas para executar o programa openshot numa instalação > Jessie num laptop Asus. Busco alguma ajuda entre vocês. Eis o caso: ao > comando > $ openshot > obtenho uma longa série de mensagens, codecs e formats e, finalmente, vem > a mensagem fatal: > > The program 'openshot' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadAlloc (insufficient resources for operation)'. > (Details: serial 25 error_code 11 request_code 151 minor_code 19) > (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.) > > > Agora, a parte curiosa: isto ocorre no Gnome e no KDE. Porém, ao rodar o > programa sob o Fluxbox, esta mensagem não aparece e o programa roda > normalmente! > > Buscando pela internet, achei várias coisas, mas em geral, neste caso, as > soluções são sempre associadas a temas do Gnome. Alterando esses temas, > porém, não dá resultado. Alem disso, certamente temas do Gnome não deveriam > afetar o KDE. > > Um ponto que talvez seja relevante é a quantidade de memória livre. No > caso do Fluxbox, há uns 3 Gb livre. No caso do Gnome e KDE, há um pouco > menos: > $ free -h > total used free sharedbuffers cached > Mem: 3.8G 1.8G 2.0G19M76M 1.0G > -/+ buffers/cache: 710M 3.1G > Swap: 7.7G 0B 7.7G > > A instalação em questão é um Jessie: > uname -a > Linux flaminia 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux > > Uma outra instalação Jessie num laptop Toshiba funciona normalmente. > > Finalmente, a razão de insistir no Gnome é que o laptop é de uso de uma > criança. Usar o Fluxbox, nesse caso, seria exigir demais. > > []'s, G.Paulo. > >
openshot: X Window System error
Saudações. Tenho tido problemas para executar o programa openshot numa instalação Jessie num laptop Asus. Busco alguma ajuda entre vocês. Eis o caso: ao comando $ openshot obtenho uma longa série de mensagens, codecs e formats e, finalmente, vem a mensagem fatal: The program 'openshot' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 25 error_code 11 request_code 151 minor_code 19) (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.) Agora, a parte curiosa: isto ocorre no Gnome e no KDE. Porém, ao rodar o programa sob o Fluxbox, esta mensagem não aparece e o programa roda normalmente! Buscando pela internet, achei várias coisas, mas em geral, neste caso, as soluções são sempre associadas a temas do Gnome. Alterando esses temas, porém, não dá resultado. Alem disso, certamente temas do Gnome não deveriam afetar o KDE. Um ponto que talvez seja relevante é a quantidade de memória livre. No caso do Fluxbox, há uns 3 Gb livre. No caso do Gnome e KDE, há um pouco menos: $ free -h total used free sharedbuffers cached Mem: 3.8G 1.8G 2.0G19M76M 1.0G -/+ buffers/cache: 710M 3.1G Swap: 7.7G 0B 7.7G A instalação em questão é um Jessie: uname -a Linux flaminia 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux Uma outra instalação Jessie num laptop Toshiba funciona normalmente. Finalmente, a razão de insistir no Gnome é que o laptop é de uso de uma criança. Usar o Fluxbox, nesse caso, seria exigir demais. []'s, G.Paulo.
Re: X Window System error
Have sence, but, emelfm (the 1) work fine to, so it it gtk. But mtpaint not use gtk+ or gtk2. All point to the X server :( Kailash Kalyani cogió un teclado y escribió: I just update debian6 to 7 and bad surprises: lazaro@utopian:~$ mtpaint The program 'mtpaint' received an X Window System error. This probably reflects a bug in the program. lazaro@utopian:~$ emelfm2 (emelfm2:3422): Gtk-CRITICAL **: gtk_tree_store_iter_next: assertion `iter- user_data != NULL' failed The program 'emelfm2' received an X Window System error. lazaro@utopian:~$ geany The program 'geany' received an X Window System error. This probably reflects a bug in the program. I'm using: lazaro@utopian:~$ ps fax|grep Xf 13474 tty1 S 3:02 /usr/X11/bin/Xfbdev -screen 1024x768x32 -t 1 -mouse /dev/ psaux,5,4 ttys7 An ancient X server due my OLDER computer. I can't use Xorg, so please, I shall be very glad resolving this problem. Geany and emelfm2 two are not from debian's repo and their ALL WAYS was working to me without problems. I guest the problem is with GTK+ i libgtk1.2 - The GIMP Toolkit set of widgets for X i A libgtk1.2-common - Common files for the GTK+ library i A libgtk2.0-0 - GTK+ graphical user interface library i libgtk2.0-bin - programs for the GTK+ graphical user interface library i libgtk2.0-common - common files for the GTK+ graphical user interface libra lazaro@utopian:~$ gimp -v GIMP version 1.2.3 work fine... the problem is not old or new applications... Hi Lazaro, Based on your inputs it may be that the GTK version dependencies may be causing this. GIMP works and GTK was built for GIMP, so that's not surprising. Based on some reading, it appears that GIMP 1.2.x was built around GTK 1.2 https://git.gnome.org/browse/gimp/commit/?h=gimp-1-2id= 61cf583747fbb3b4306bf085b85b1f67e627778c And you seem to have gtk 1.2 installed in part at least. As the other programs were previously working, the new GTK errors might indicate a change in the libraries? If so, then knowing the versions of your other apps would help determine which GTK version they were based on. What do you think? Kailash -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130524085318.gd12...@magnox.lex-sa.cu
RE: X Window System error
I just update debian6 to 7 and bad surprises: lazaro@utopian:~$ mtpaint The program 'mtpaint' received an X Window System error. This probably reflects a bug in the program. lazaro@utopian:~$ emelfm2 (emelfm2:3422): Gtk-CRITICAL **: gtk_tree_store_iter_next: assertion `iter-user_data != NULL' failed The program 'emelfm2' received an X Window System error. lazaro@utopian:~$ geany The program 'geany' received an X Window System error. This probably reflects a bug in the program. I'm using: lazaro@utopian:~$ ps fax|grep Xf 13474 tty1 S 3:02 /usr/X11/bin/Xfbdev -screen 1024x768x32 -t 1 -mouse /dev/psaux,5,4 ttys7 An ancient X server due my OLDER computer. I can't use Xorg, so please, I shall be very glad resolving this problem. Geany and emelfm2 two are not from debian's repo and their ALL WAYS was working to me without problems. I guest the problem is with GTK+ i libgtk1.2 - The GIMP Toolkit set of widgets for X i A libgtk1.2-common- Common files for the GTK+ library i A libgtk2.0-0 - GTK+ graphical user interface library i libgtk2.0-bin - programs for the GTK+ graphical user interface library i libgtk2.0-common- common files for the GTK+ graphical user interface libra lazaro@utopian:~$ gimp -v GIMP version 1.2.3 work fine... the problem is not old or new applications... Hi Lazaro, Based on your inputs it may be that the GTK version dependencies may be causing this. GIMP works and GTK was built for GIMP, so that's not surprising. Based on some reading, it appears that GIMP 1.2.x was built around GTK 1.2 https://git.gnome.org/browse/gimp/commit/?h=gimp-1-2id=61cf583747fbb3b4306bf085b85b1f67e627778c And you seem to have gtk 1.2 installed in part at least. As the other programs were previously working, the new GTK errors might indicate a change in the libraries? If so, then knowing the versions of your other apps would help determine which GTK version they were based on. What do you think? Kailash
X Window System error
I just update debian6 to 7 and bad surprises: lazaro@utopian:~$ mtpaint The program 'mtpaint' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 1280 error_code 1 request_code 135 minor_code 33) (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.) lazaro@utopian:~$ emelfm2 (emelfm2:3422): Gtk-CRITICAL **: gtk_tree_store_iter_next: assertion `iter-user_data != NULL' failed The program 'emelfm2' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 469 error_code 1 request_code 135 minor_code 33) (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.) lazaro@utopian:~$ geany The program 'geany' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 1115 error_code 132 request_code 135 minor_code 10) (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.) I'm using: lazaro@utopian:~$ ps fax|grep Xf 13474 tty1 S 3:02 /usr/X11/bin/Xfbdev -screen 1024x768x32 -t 1 -mouse /dev/psaux,5,4 ttys7 An ancient X server due my OLDER computer. I can't use Xorg, so please, I shall be very glad resolving this problem. Geany and emelfm2 two are not from debian's repo and their ALL WAYS was working to me without problems. I guest the problem is with GTK+ i libgtk1.2 - The GIMP Toolkit set of widgets for X i A libgtk1.2-common- Common files for the GTK+ library i A libgtk2.0-0 - GTK+ graphical user interface library i libgtk2.0-bin - programs for the GTK+ graphical user interface library i libgtk2.0-common- common files for the GTK+ graphical user interface libra lazaro@utopian:~$ gimp -v GIMP version 1.2.3 work fine... the problem is not old or new applications... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130519020339.GA2664@utopian
Re: mozilla-[firefox|thunderbird]: 'firefox-bin' received an X Window System error und BadPixmap (invalid Pixmap parameter)-Fehlermeldungen bei backports
Sehr geehrter Herr Heil, ich beziehe mich auf Ihren Beitrag zur debian.user.german-Liste vom 19.4.2004 (http://lists.debian.org/debian-user-german/2004/07/msg01777.html). Ich habe jetzt dasselbe Problem, habe aber in der Liste (und sonst) keine Lösung gefungen. Würden Sie mir mitteilen, wie Sie das Problem gelöst haben? Falls ja, Danke im Voraus. Georg Pfeiffer -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: mozilla-[firefox|thunderbird]: 'firefox-bin' received an X Window System error und BadPixmap (invalid Pixmap parameter)-Fehlermeldungen bei backports
* Georg Pfeiffer wrote: ich beziehe mich auf Ihren Beitrag zur debian.user.german-Liste vom 19.4.2004 (http://lists.debian.org/debian-user-german/2004/07/msg01777.html). Ich habe jetzt dasselbe Problem, habe aber in der Liste (und sonst) keine Lösung gefungen. Würden Sie mir mitteilen, wie Sie das Problem gelöst haben? Na, die Loesung steht doch in der Mail. KDE ist offenbar das Problem, wir hatten dazu auch schon eine Diskussion auf der backports.org Mailingliste. Norbert -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
mozilla-[firefox|thunderbird]: 'firefox-bin' received an X Window System error und BadPixmap (invalid Pixmap parameter)-Fehlermeldungen bei backports
Hallo Debian-User,
die beiden einzigsten backports, die ich unter meinem Woody-System
verwende, sind:
mozilla-firefox 0.9.1-3.backports.org.1
mozilla-thunderbird 0.6-1.backports.org.1
Nun beobachte ich folgende Abstürze (thunderbird stürzt mit der gleichen
Fehlermeldung ab), sobald ich unter firefox z.B. Edit / Preferences / Advanced
(reproduzierbar) aufrufe:
$ mozilla-firefox
[...]
(firefox-bin:17051): Gdk-CRITICAL **: file gdkpixmap-x11.c: line 218
(gdk_bitmap_create_from_data): assertion `window == NULL || GDK_IS_WINDOW (window)'
failed
(firefox-bin:17051): Gdk-CRITICAL **: file gdkpixmap-x11.c: line 218
(gdk_bitmap_create_from_data): assertion `window == NULL || GDK_IS_WINDOW (window)'
failed
(firefox-bin:17051): Gdk-CRITICAL **: file gdkpixmap-x11.c: line 218
(gdk_bitmap_create_from_data): assertion `window == NULL || GDK_IS_WINDOW (window)'
failed
The program 'firefox-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
(Details: serial 6421 error_code 4 request_code 56 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.)
Das Interessante an der Sache ist, dass diese Abstürze nur unter *KDE2*
(Standard-KDE in Woody) auftreten. In *icewm* konnte ich dieses Verhalten
nicht feststellen.
Dieses Verhalten beobachte ich bei firefox erst nach meinem heutigen Update auf
0.9.1-3 (von 0.8) -- bei thunderbird schon seit einer ganzen Weile (ab
0.6).
Output von strace:
[...]
write(2, \n(firefox-bin:17287): Gdk-CRITIC..., 161
(firefox-bin:17287): Gdk-CRITICAL **: file gdkpixmap-x11.c: line 218
(gdk_bitmap_create_from_data): assertion `window == NULL || GDK_IS_WINDOW (window)'
failed
) = 161
write(3, [EMAIL PROTECTED]@\3[EMAIL PROTECTED]..., 632) = 632
read(3, \0\4\315 [EMAIL PROTECTED]..., 32) = 32
open(/usr/X11R6/lib/X11/XErrorDB, O_RDONLY) = 27
fstat64(27, {st_mode=S_IFREG|0644, st_size=33792, ...}) = 0
read(27, ! $Xorg: XErrorDB,v 1.3 2000/08/..., 33792) = 33792
close(27) = 0
write(2, The program \'firefox-bin\' receiv..., 568The program 'firefox-bin'
received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
(Details: serial 8397 error_code 4 request_code 56 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.)
) = 568
unlink(/home/heiko/.firefox/default/3dv973mo.slt/lock) = 0
write(9, [EMAIL PROTECTED]@\f\10\01081\10\01004\10\10\370..., 148) = 148
rt_sigprocmask(SIG_SETMASK, NULL, [RTMIN], 8) = 0
rt_sigsuspend([] unfinished ...
--- SIGRTMIN (Real-time signal 0) ---
... rt_sigsuspend resumed ) = -1 EINTR (Interrupted system call)
sigreturn() = ? (mask now [RTMIN])
wait4(17323, NULL, __WCLONE, NULL) = 17323
munmap(0x40883000, 8192)= 0
munmap(0x4085d000, 8192)= 0
_exit(1)
Meine .firefox-configs habe ich auch schon mal weggeschrieben - hat
nichts genutzt.
Über Hinweise und Tipps zu diesem Thema würde ich mich sehr freuen.
Danke...
Gruss Heiko
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
