I'm using Debian Unstable, but I assume it's the same issue.
Checking the system logs (e.g. via dmesg) reveals entries along the
lines of:
audit: type=1400 audit(1606596824.706:63): apparmor="DENIED"
operation="mknod" profile="/usr/sbin/gpsd" name="/tmp/gpsfake-5064.sock"
pid=5065 comm="gpsd" req
This was probably fixed in Viking 1.6.1 by commit
SHA:38597a6d6510251f81a1f6cab16c3d3e2555dbda
** Changed in: viking (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Viking doesn't set any colours for fonts (be they background, foreground
or in tooltips), they are all inherited from the system desktop
settings/theme.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
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
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 th
Unfortunately in version Viking 1.3.* (and I think all the 1.* versions)
if you load a GPX file or a KML file and then perform File->Save or use
the toolbar Save button - Viking will save the current data in it's own
internal format - overwriting whatever file the data was loaded from.
The work ar
** Changed in: viking (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096477
Title:
Viking does not write files readable by viking itself
To manage notif
PS Where does is say that "Viking states to read all these formats and
it states to write all these formats" ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096477
Title:
Viking does not write file
This looks like the incorrect curl usage crash:
http://sourceforge.net/tracker/?func=detail&aid=3206628&group_id=83870&atid=570954
This is fixed in from version 1.2 onwards.
** Bug watch added: SourceForge.net Tracker #3206628
http://sourceforge.net/support/tracker.php?aid=3206628
--
You rec
I think I should mention 1.3.2.1 only contains bug fixes and important
stability fixes over the basic 1.3 version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064112
Title:
Please Update to Upstea
** Changed in: viking (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/831041
Title:
viking crashes after some time
To manage notifications about this bug g
** Changed in: viking (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/445374
Title:
viking crashes when I want to download the maps around a track
To
Is any one closing such really old bugs that aren't relevant any more?
** Changed in: viking (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/437603
Title:
** Changed in: viking (Ubuntu)
Status: New => Fix Released
** Also affects: viking via
http://sourceforge.net/support/tracker.php?aid=2880741
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: viking (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921695
Title:
viking crashed with SIGABRT in g_assertion_message()
To manage no
*** This bug is a duplicate of bug 583056 ***
https://bugs.launchpad.net/bugs/583056
I'm convinced this is a GTK bug.
Search the web for "gtk_file_system_model_sort: assertion failed: (r ==
n_visible_rows)" produces lots of hits across various programs.
Such as:
https://bugs.launchpad.net/ub
Public bug reported:
Please Update to Upsteam Release 1.3.2.1
http://sourceforge.net/projects/viking/files/viking/1.3.2/viking-1.3.2.1.tar.gz/download
** Affects: viking (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
I think is fixed upstream by this commit:
"Fix crashing on opening multiple files after a .vik file is opened."
http://viking.git.sourceforge.net/git/gitweb.cgi?p=viking/viking;a=commit;h=08812b09d0bb6062a68b8aa90e6f07c78fd83923
Unfortunately you'll have to wait until Version 1.3 is released and
Point 1 about creating a layer when there is no data - this iss fixed in
Natty (0.9.94-3)
Point 2, also in Natty (0.9.94-3), there is rudimentary USB device
detection.
Indeed, your 'Garmin' (what device exactly is it?) may not actually
communicate via the Garmin GPS protocol, and you can simply b
Fixed upstream and is in version 0.9.96.
Here is the patch:
-- src/terraservermapsource.c --
index 7fb9472..efeb9d0 100644
@@ -187,7 +187,8 @@ _coord_to_mapcoord ( VikMapSource *self, const VikCoord
*src, gdouble xmpp, gdou
Terrase
20 matches
Mail list logo
