[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#700728: Crash when starting Impress Remote



On Sat, 2013-02-16 at 23:54 +0100, Rene Engelhard wrote:
> tag 700728 + pending
> thanks
> 
> Hi,
> 
> On Sat, Feb 16, 2013 at 06:18:41PM +0000, Ben Hutchings wrote:
> > Selecting the 'Impress Remote' menu item instantly crashes Impress,
> > whether or not I have attempted to connect from the Remote application
> > first.
> 
> Interesting. Works fine here in my sid/amd64 chroot.
> 
> > Running from the console with gdb, I see:
> > 
> > terminate called after throwing an instance of 'std::bad_alloc'
> >   what():  std::bad_alloc
> [ snip ]
> 
> Quickly asked upstream about this today and got the folllowing mail:
> 
> ----- Forwarded message from Michael Meeks <michael.meeks@suse.com> -----
> 
> Date: Sat, 16 Feb 2013 21:55:44 +0000
> From: Michael Meeks <michael.meeks@suse.com>
> To: Rene Engelhard <rene@debian.org>
> Subject: debbug 700728 ...
> Reply-To: michael.meeks@suse.com
> Organization: SUSE
> X-Mailer: Evolution 3.2.3
> 
>         The menu item is practically worthless and disabled in 4.0.1 unless in
> deep experimental mode with the remote enabled - it's basically a
> walking bug ;-)
> 
>         It's also not needed for bluetooth either so ... they should just pair
> in the normal bluetooth way, and then it should be fine to discover
> libreoffice if the tool is enabled.

That didn't work for me either, which is why I thought I might need to
select the menu item first.

First try: in Impress Remote, I select the computer's name (deadeye-0)
on the list under 'Bluetooth'.  It shows 'Attempting to connect to
deadeye-0...' and a spinner for a while and then an error message
'Impress Remote could not connect to .' (sic).  Second try: the spinner
keeps on spinning until the screen blanks.

What information do you need from me to debug this?

Ben.

-- 
Ben Hutchings
Computers are not intelligent.	They only think they are.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: