Loading Profile...
X Window System Error
INFO sL.a | connection tries: 2, SEARCH 88.198.58.21
The program 'Wuala' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1978 error_code 11 request_code 146 minor_code 5)
(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.)
The program 'Wuala' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1978 error_code 11 request_code 146 minor_code 5)
(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.)
5
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Get Satisfaction loves Zappos because they care about customer service.
-
Inappropriate?there is a method to send an automated bugreport/errorreport to the wuala servers from within the wuala client.
on the win32 (windows) client at least as long the wuala gui process is running and not crashed you simultaneously press "ctrl + alt + x" and wuala gets closed, writes a bugreport and uploads it to the wuala servers....
maybe you can repro your behaviour and send some bugreports from wuala. dont know if ctrl+alt+x works on X though.... you might try it....
although insufficient resources might also be some ram/memory problem or other resources problem of your operating system.
what kinda hardware/software config do you have / run?
x on what operating system? what graphics hardware? what drivers, ram, hardware, and so on?
cheers. -
Inappropriate?Sorry, I forgot to mention a few things:
Running Ubuntu 7.10/x68; 1G Ram; IBM Thinkpad
I get the error mentioned above right when starting wuala and it crashes with this message. So there's no way of sending a bug report from within the program. -
Inappropriate?Same Problem also in Ubuntu 7.10
The program 'Wuala' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1423 error_code 11 request_code 147 minor_code 5)
(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.)
Yesterday it has work normal but today it won't get open.
I'm writing from switzerland!
Can it be this?
http://people.debian.org/~terpstra/me...
I’m little frustrated
-
Inappropriate?hmm so it might be a bug in the x subsystem of ubuntu in relation to x-programs in general? did you try to search the internet for this "badalloc" and "ubuntu" errors in general. maybe you find other people running other apps on ubuntu who have these crashes with their applications....
http://www.google.com/search?hl=en&q=...
maybe you also need to open some bugreport with the ubuntu/x people too.
you might also try to change the packages on ubuntu, running a different x-server or other modules to see when wuala crashes exactly with what x-packages installed and so on.
try to narrow down the source of the bug with the help of installing/changing your x-subsystems packages, other window managers and so on.
maybe even graphics drivers, acceleration turned off/on and so on.
cheers and good luck. -
Inappropriate?Solution on gutsy:
Downgrade to pre. version
wget http://launchpadlibrarian.net/9590664...
sudo dpkg -i xserver-xorg-core_1.3.0.0.dfsg-12ubuntu8_i386.deb
found on this site:
https://bugs.launchpad.net/ubuntu/+so...
I’m very happy
1 person says
this solves the problem
-
-
Inappropriate?I think you have the same problem like the ubuntu's.
Your bug:
http://bugs.debian.org/cgi-bin/bugrep...
Fix:
http://lists.debian.org/debian-securi...
in the xorg.conf put that:
Section "Extensions"
Option "MIT-SHM" "no"
EndSection
1 person says
this solves the problem
-
-
Inappropriate?btw: The purpose of ctrl-alt-x is to find out about performance problem. It sends a report about what is happening right at the moment of pressing the combination. It is very unlikely to "catch" a bug this way as it is already over after the crash. :) However, if Wuala is using lots of CPU cycles when you think it shouldn't ctrl-alt-x is useful to shut it down and give us a hint about possible performance problems.
EMPLOYEE
