Adding any layer except Aggregate makes viking freeze

Bug #1255275 reported by Patrick Hetu
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
viking (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Version: 1.4.2-2 (note that the 1.5 release does the same)

When you add a new layer if you click on cancel or ok the popup
doesnt closed and everything become unresponsive.

This is what stace gives:

poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}])
recv(3, "\1\1\220\f\0\0\0\0\206\0\240\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096, 0) = 32
recv(3, 0x9a99728, 4096, 0) = -1 EAGAIN (Resource temporarily unavailable)
recv(3, 0x9a99728, 4096, 0) = -1 EAGAIN (Resource temporarily unavailable)
write(7, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0xb5009c78, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xb5009838, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xb50042c8, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x9a86a10, FUTEX_WAIT_PRIVATE, 2, NULL^C

I also have those warning at statup:

** (viking:21177): WARNING **: Unknown GObject type 'VikWmscMapSource'
(viking:21177): GLib-GObject-WARNING **: g_object_set_valist: construct property "lat-attr" for object 'VikGotoXmlTool' can't be set after construction
(viking:21177): GLib-GObject-WARNING **: g_object_set_valist: construct property "lon-attr" for object 'VikGotoXmlTool' can't be set after construction

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in viking (Ubuntu):
status: New → Confirmed
Revision history for this message
vlc (vlc) wrote :

Here the same on saucy with viking 1.3. I also have the same strace output, but at startup I only get

** (viking:7447): WARNING **: unbuffer not found in PATH

Revision history for this message
Rob Norris (rw-norris) wrote :

On my Ubuntu laptop this occurs when one uses the main menu system and do Layers->New X Layer.

However if you right click on the Top Layer -> New Layer -> New X Layer or click on the + on the bottom left and choose a layer - both these ways of instigating it worked fine for me.

Interestingly it all works fine on my Debian system.

On the Ubuntu program it has an extra thread 'dconf worker' which isn't present in the Debian version. I've yet to determine if that really makes any difference.

Revision history for this message
Rob Norris (rw-norris) wrote :

In fact any dialog created via the Global Main Menu when closed will hang Viking.

I believe this to be a fault of the Unity Desktop.
I have raised the bug here: https://bugs.launchpad.net/unity-gtk-module/+bug/1258669

Running Viking under another Desktop such as LXDE (lubuntu-desktop), solves the issue as the program operates correctly.

There are workarounds to avoid using the Global Menu, so from the command line run it like this:

env UBUNTU_MENUPROXY= viking

or amend the exec statement similiarly in the file /usr/share/applications/viking.desktop to read:
Exec=env UBUNTU_MENUPROXY= viking %F

The latter will fix running Viking via desktop icons.

Revision history for this message
William Hua (attente) wrote :

Hello, thanks for filing this bug, as the one Rob filed is more accurate, I'm marking this as a duplicate of that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.