Am 30.11.2012 12:29, schrieb Andrew Haley:
Fixed thusly, We'll see what the AWT devs say.
Thanks a lot for the patch and sorry for all the trouble with
reproducibility!
I haven't been able to reproduce the crash with this patch applied, so I
would assume the problem is really fixed.
Ignaz
Hi Andrew,
On Fri, 2012-11-30 at 11:29 +, Andrew Haley wrote:
> Fixed thusly, We'll see what the AWT devs say.
Thanks so much; sorry it took such an awkward setup to debug.
ATB,
Michael.
--
michael.me...@suse.com <><, Pseudo Engineer, itinerant idiot
___
On 11/24/2012 06:02 PM, Michael Meeks wrote:
> Sorry to bother you; just visiting some friends at Munich hosting a
> hack-fest; and they have an interesting problem with OpenJDK. It -seems-
> that even though we initialise X with XInitThreads - before Java gets
> involved and all has worked
On 11/30/2012 10:17 AM, Stephan Bergmann wrote:
> On 11/29/2012 05:36 PM, Andrew Haley wrote:
>> On 11/29/2012 04:34 PM, Michael Meeks wrote:
>>> If you want java working, it is necessary to run javaldx, which finds
>>> the JRE and sets the right LD_LIBRARY_PATH nastiness to make that work
>>>
On 11/29/2012 05:36 PM, Andrew Haley wrote:
On 11/29/2012 04:34 PM, Michael Meeks wrote:
If you want java working, it is necessary to run javaldx, which finds
the JRE and sets the right LD_LIBRARY_PATH nastiness to make that work
(IIRC), and that is now spawned by the ooquickstart.
Aha
On 29/11/12 16:42, Andrew Haley wrote:
> On 11/29/2012 03:09 PM, Andrew Haley wrote:
>> Got it! Only seems to happen if I'm using KDE as a local login. I was
>> running it remotely on an XFCE desktop.
>
> Please help: I can't figure out how to run this program from the commend
> line. I need to
On 29/11/12 17:35, Andrew Haley wrote:
> On 11/29/2012 04:27 PM, Michael Stahl wrote:
>> On 29/11/12 16:42, Andrew Haley wrote:
>> try:
>>
>> cd /usr/lib64/libreoffice/program/
>> gdb --args ./soffice.bin
>>
>> if it exits with 0121 (81) it just initialized something, re-run it.
>>
>> of course eas
On 11/29/2012 04:34 PM, Michael Meeks wrote:
> If you want java working, it is necessary to run javaldx, which finds
> the JRE and sets the right LD_LIBRARY_PATH nastiness to make that work
> (IIRC), and that is now spawned by the ooquickstart.
Aha! I'm going to need to tweak that to use th
On 11/29/2012 04:27 PM, Michael Stahl wrote:
> On 29/11/12 16:42, Andrew Haley wrote:
>> On 11/29/2012 03:09 PM, Andrew Haley wrote:
>>> Got it! Only seems to happen if I'm using KDE as a local login. I was
>>> running it remotely on an XFCE desktop.
>>
>> Please help: I can't figure out how to r
Hi Andrew,
On Thu, 2012-11-29 at 15:42 +, Andrew Haley wrote:
> Please help: I can't figure out how to run this program from the commend
> line. I need to start it in gdb, with no wrapper scripts.
Sorry about that, if you poke the soffice wrapper there is a
--backtrace option in rece
Hi,
On 11/29/2012 04:22 PM, Miklos Vajna wrote:
> On Thu, Nov 29, 2012 at 03:42:25PM +, Andrew Haley
> wrote:
>> Please help: I can't figure out how to run this program from the commend
>> line. I need to start it in gdb, with no wrapper scripts.
>
> Either locate soffice.bin in the rpm
Hi Andrew,
On Thu, Nov 29, 2012 at 03:42:25PM +, Andrew Haley wrote:
> Please help: I can't figure out how to run this program from the commend
> line. I need to start it in gdb, with no wrapper scripts.
Either locate soffice.bin in the rpm package, or run 'libreoffice
--backtrace' that wil
On 11/29/2012 03:09 PM, Andrew Haley wrote:
> On 11/28/2012 10:45 AM, Ignaz Forster wrote:
>> Hi Andrew,
>>
>> we are currently creating a minimal Java test extension; in the meantime
>> you could also use the WollMux extension to reproduce the problem:
>>
>> - Download
>> http://wollmux.googleco
On 11/28/2012 10:45 AM, Ignaz Forster wrote:
> Hi Andrew,
>
> we are currently creating a minimal Java test extension; in the meantime
> you could also use the WollMux extension to reproduce the problem:
>
> - Download
> http://wollmux.googlecode.com/files/wollmux-11.10a-manual_installation.zip
Am 28.11.2012 19:04, schrieb Andrew Haley:
I wonder if there's something you've been doing that I haven't.
I don't think I did anything special...
To be sure I reproduced the problem at home (this time with a single
core CPU) using the Fedora Live CD:
- Download 64-bit Fedora 17 KDE Spin
-
Hi Andrew,
we are currently creating a minimal Java test extension; in the meantime
you could also use the WollMux extension to reproduce the problem:
- Download
http://wollmux.googlecode.com/files/wollmux-11.10a-manual_installation.zip
- Extract the file WollMux.oxt
- Install the plugin: un
On 11/28/2012 04:52 PM, Ignaz Forster wrote:
> Am 28.11.2012 13:33, schrieb Andrew Haley:
>> On 11/28/2012 10:45 AM, Ignaz Forster wrote:
>>> - Download
>>> http://wollmux.googlecode.com/files/wollmux-11.10a-manual_installation.zip
>>> - Extract the file WollMux.oxt
>>> - Install the plugin: unopkg
Am 28.11.2012 13:33, schrieb Andrew Haley:
On 11/28/2012 10:45 AM, Ignaz Forster wrote:
- Download
http://wollmux.googlecode.com/files/wollmux-11.10a-manual_installation.zip
- Extract the file WollMux.oxt
- Install the plugin: unopkg add /path/to/WollMux.oxt (or, if unopkg
isn't installed, use T
On 11/28/2012 10:45 AM, Ignaz Forster wrote:
> Hi Andrew,
>
> we are currently creating a minimal Java test extension; in the meantime
> you could also use the WollMux extension to reproduce the problem:
>
> - Download
> http://wollmux.googlecode.com/files/wollmux-11.10a-manual_installation.zip
On 11/28/2012 10:45 AM, Ignaz Forster wrote:
> Now just open Tools -> Extension Manager a few times. It usually crashes
> the second time the dialog comes up...
I have a very poor internet connection at the moment, and it's going to take
a long time to install KDE. I'll let you know.
Andrew.
_
Hi,
On 11/24/2012 06:02 PM, Michael Meeks wrote:
> It seems to me that X's global error handler is the primary design
> drop-off here; there should be one per display (?). Having said that - I
> wonder if there is some nice way we can clobber Java's XError handler
> entirely, and/or stop it
Hi Andrew,
Sorry to bother you; just visiting some friends at Munich hosting a
hack-fest; and they have an interesting problem with OpenJDK. It -seems-
that even though we initialise X with XInitThreads - before Java gets
involved and all has worked well for a long time; that (as of recent
22 matches
Mail list logo
