reassign 581309 openbox
tags 581309 - unreproducible
thanks

Hi Tomas,

I reassign this bug to openbox instead.

Cheers,
Balint

2010/5/24 Tomáš Vondra <[email protected]>:
> Thank you for the reply, for it enabled me to use Wireshark :-)
> The key was trying it with Fvwm. I use LXDE - lxsession, lxpanel and openbox.
> When Openbox is launched from command line and Wireshark is launched
> next, openbox crashes saying "Unable to parse color #......" and "This
> image bit depth (8) is currently unhandled".
> When started from lxsession, it probably gets restarted when it crashes.
> Wireshark then stays on the output of "ps", but its window is not
> visible.
> My best hypothesis is that it can't paint the icon on the title bar.
> Shall I submit it as a bug of openbox?
> Yours sincerely, Tomas
>
>
...
>> Hi,
>>
>> I tried to reproduce your problem, running tightvncserver and fvwm on
>> a fully updated Squeeze system.
>> I saw the "Xlib:  extension "RANDR" ... message, but Wireshark started 
>> properly.
>>
>> Could you please collect a coredump and attach a backtrace using the
>> wireshark-dbg package available from wireshark 1.2.8-1?
>>
>> Thanks,
>> Balint
>>
>> 2010/5/12 Tomas Vondra <[email protected]>:
>> > Package: wireshark
>> > Version: 1.2.7-1
>> > Severity: normal
>> >
>> >
>> > When I try to start Wireshark in an 8-bit tightvnc display, the screen 
>> > flickers, all windows move down a little, but Wireshark doesn't open.
>> > Works OK on 16 or 24-bit display.
>> > The message "Xlib:  extension "RANDR" missing on display ":1.0"." can be 
>> > seen in both cases, no other errors or log entries.
>> >
>> >
>> > -- System Information:
>> > Debian Release: squeeze/sid
>> >  APT prefers testing
>> >  APT policy: (500, 'testing')
>> > Architecture: i386 (i686)
>> >
>> > Kernel: Linux 2.6.31.10tA (SMP w/2 CPU cores)
>> > Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
>> > Shell: /bin/sh linked to /bin/bash
...



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to