open dsp: Device or resource busy
[New Thread 1166059840 (LWP 8018)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47658634372016 (LWP 7957)]
XQueryExtension (dpy=0x0, name=0x2b5862345f11 "MIT-SHM",
major_opcode=0x7fff4c5db9c4, first_event=0x7fff4c5db9c8,
first_erro
this ist the output of: sudo update-alternatives --config java
Es gibt 2 Alternativen, die »java« bereitstellen.
Auswahl Alternative
---
1/usr/bin/gij-wrapper-4.1
*+2/usr/lib/jvm/java-6-sun/jre/bin/java
Drücken Sie die
I am unable to reproduce this. have you ran "sudo update-alternatives
--config java" without the " and choose the newest java you have (should
be 6.0 or 1.6 same version)?
--
[FEISTY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED]
https://bugs.launchpad.net/bugs/113590
You received this bug
** Attachment added: "gdb-firefox.log"
http://librarian.launchpad.net/7881244/gdb-firefox.log
--
[FEISTY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED]
https://bugs.launchpad.net/bugs/113590
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
Alexander,
first of all, thank y for spending time to try to find the error;
-call youtube.com
-allow javascript for youtube.com with extention "noscript" temporary
-allow javascript for doubleclick.net with extention "noscript"
temporary
-search a film e.g. "loremo"
-message shown:
Hello, you e
Com,
as it appears you can somehow reproduce this crash, can you try to
figure out a way to reproduce this reliably? e.g. by a step-by-step
instruction? That would help us a lot to tackle this problem.
Thanks,
- Alexander
--
[FEISTY] firefox crashed [EMAIL PROTECTED] [EMAIL PROTECTED]
https:
perhaps this gbd.log may help some developer - hopefully;
the output does not correspond to the coredump above (because gbd was
installed after the first crash, when i report the bug), but i think the
repeated crash of firefox is under the same circumstances (only my
opinion as newbie- i have no e
Thank you for the bug report however this report lacks information we
need to investigate it further. Of course this is not your fault, but
the coredump attached to your report doesn't provide useful information
for us. For this reason, we are now going to close the bug - please feel
free to reopen
