vinagre crashed with signal 5 in vinagre_utils_get_builder()

See also Bug 422364

Unmarking as duplicate of Bug 422054, since that one is not visible.

this bug is already fixed upstream (since 28th Aug)

Confirming that the upstream patch works. I've build the .deb locally.

Hi Noel,

Im linux-noob. I do think I understand what youre saying though. So then
it's either my medication :P or that launchpad site is unintuitive.
Or maybe Im just stupid.
Abyhow, could you please explain how I follow this bug-report "upstream";
https://bugs.launchpad.net/bugs/422234

kind regards
/h

2009/9/6 Noel J. Bergman <email address hidden>

> Confirming that the upstream patch works. I've build the .deb locally.
>
> --
> vinagre crashed with signal 5 in vinagre_utils_get_builder()
> https://bugs.launchpad.net/bugs/422234
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Vinagre: VNC client for GNOME: Fix Released
> Status in “vinagre” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: vinagre
>
> Vinagre crashes when I click on connect
>
> ProblemType: Crash
> Architecture: i386
> CheckboxSubmission: 48a5398b7fdba0364e52d65ed9ab0575
> CheckboxSystem: f7e8b2058e73d899cd2bf5b9df7c26dc
> Date: Mon Aug 31 22:43:25 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/vinagre
> NonfreeKernelModules: nvidia
> Package: vinagre 2.27.91-0ubuntu1
> ProcCmdline: vinagre
> ProcEnviron:
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-6.26-generic
> Signal: 5
> SourcePackage: vinagre
> StacktraceTop:
> vinagre_utils_get_builder ()
> vinagre_connect ()
> vinagre_cmd_machine_connect ()
> g_cclosure_marshal_VOID__VOID ()
> g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
> Title: vinagre crashed with signal 5 in vinagre_utils_get_builder()
> Uname: Linux 2.6.31-6-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>

--
 --> --> --> --> --> --> -->
aphorism.
Nazi punks think they're playing punk,
just like pedophiles think they're having sex.

Håkan, if you look at the top of this page, you'll see that there are two listings. "Vinagre: VNC client for GNOME", which is marked "Fix Released"; and "vinagre (Ubuntu)", which is marked "triaged".

Basically, the bug is already fixed "upstream", where development happens, and we're just waiting for that to filter down to Ubuntu. Why this hasn't been done by Robert Ancell, who wrote the patch; Emilio Pozuelo Monfort, who is listed as the current maintainer; or Jonh Wendell, the primary author, is a mystery to me.

In the meantime, I am attaching a debdiff, in the hopes that it helps move this process along. This is done as a proper patch, using the patch system.

Adding again, remembering to click the "patch" checkbox this time.

OK, after talking with folks on IRC, I've subscribed Ubuntu Main Sponsors.

Hi Noel,
thank you very much for the explanation. Its been ten years since I was
involved in *any *software development phase and that was under ms.
Hoping to contribute a little by running pre-releases and creating bugs. Im
good at breaking things. ;)

Again, thanx for the help and maybe Ill get into the swing of things a
little from here.

kind regards
/Håkan

2009/9/6 Noel J. Bergman <email address hidden>

> Adding again, remembering to click the "patch" checkbox this time.
>
> ** Attachment added: "Incorporates *only* Robert Ancell's approved patch
> from upstream (marked as a patch this time)"
> http://launchpadlibrarian.net/31395594/LP422234.debdiff
>
> --
> vinagre crashed with signal 5 in vinagre_utils_get_builder()
> https://bugs.launchpad.net/bugs/422234
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Vinagre: VNC client for GNOME: Fix Released
> Status in “vinagre” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: vinagre
>
> Vinagre crashes when I click on connect
>
> ProblemType: Crash
> Architecture: i386
> CheckboxSubmission: 48a5398b7fdba0364e52d65ed9ab0575
> CheckboxSystem: f7e8b2058e73d899cd2bf5b9df7c26dc
> Date: Mon Aug 31 22:43:25 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/vinagre
> NonfreeKernelModules: nvidia
> Package: vinagre 2.27.91-0ubuntu1
> ProcCmdline: vinagre
> ProcEnviron:
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-6.26-generic
> Signal: 5
> SourcePackage: vinagre
> StacktraceTop:
> vinagre_utils_get_builder ()
> vinagre_connect ()
> vinagre_cmd_machine_connect ()
> g_cclosure_marshal_VOID__VOID ()
> g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
> Title: vinagre crashed with signal 5 in vinagre_utils_get_builder()
> Uname: Linux 2.6.31-6-generic i686
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
>

--
 --> --> --> --> --> --> -->
aphorism.
Nazi punks think they're playing punk,
just like pedophiles think they're having sex.

Noel, tomorrow vinagre 2.27.92 tarball will be released, and it will get updated into karmic.

That's the point of having development releases, to get things tested, reported and fixed during the cycle.

IMO there's no need to worry and create patches of things that were fixed upstream and will sure reach downstream (ubuntu) in the next release.

Hi all,

Ive been without sleep for too long now (not linux related) and I did not realise that I was mailing to this buglist.
I would like to say that I am sorry for any problems or inconveniences I have created as well as for spamming this list.
Sorry guys. I usually dont make the same mistakes twice so with any luck... :)

-peace
/Håkan

> tomorrow vinagre 2.27.92 tarball will be released, and it will get updated into karmic

Good to know. :-)

But in the meantime, for the past week, anyone testing on Karmic had a broken VNC client with no functionality, unless they fixed it them-self or installed an alternative. So in my view, either the update should have been rolled back, or the rather trivial fix put in place.

Noel,

Karmic is a development release. Things are broken now and then. If you can not live with that for a week then you should not be running development releases.
By the way, the alternative 'xvnc4viewer' is right there in repositories and just one click away. :-)

This bug was fixed in the package vinagre - 2.27.92-0ubuntu1

---------------
vinagre (2.27.92-0ubuntu1) karmic; urgency=low

  * New upstream version
    Features and Fixes
    - Removed duplicated names in the UI file, avoiding crashes (lp: #422234)
    - Show IP addresses of avahi-discovered machines instead of names
    - Handle GConf errors in preferences

 -- Sebastien Bacher <email address hidden> Mon, 07 Sep 2009 14:07:27 +0200

I'm well aware of Karmic's status. Have spent more time running development builds than release builds for more than two years. And *I* can (and did) build my own. But I also care and respect all of those who can't. I think that PulseAudio, Network Manager, Transmission, and others have the right idea: one (or sometimes more) PPA is built regularly, people test early and often, and what goes into the main repository has been better vetted.