This is odd, nothing about the map view has ever been changed since the initial release. Maybe this is a distribution-specific problem?

I never used Ubuntu, so I simply setup a "blank" Ubuntu 22.04 LTS virtual machine to try it out.

I couldn't install kgeotag using the default package repos, so I suppose it's not yet official part of Ubuntu 22.04. Thus, I compiled it from git.

I had to install the following packages:

cmake build-essential extra-cmake-modules qtbase5-dev libkf5coreaddons-dev libkf5i18n-dev libkf5xmlgui-dev libkf5crash-dev libkf5doctools-dev libkf5kexiv2-dev libmarble-dev

After that, I could compile and install kgeotag without a problem. Also, the map is shown as expected.

Thus, this seems to be a packaging problem. Please contact the package maintainer about this, this is not an upstream bug!

PS: On https://community.kde.org/KGeoTag you can find documentation about how to compile KGeoTag from sources.

Thanks for the quick answer.
I have a very basic Linux profeciency.
Is this something I can reproduce or am I just left waiting for the 
package maintainer to act ?


On 2023-07-29 21:08, Tobias Leupold wrote:
> https://bugs.kde.org/show_bug.cgi?id=472777
> 
> Tobias Leupold <tl@stonemx.de> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>          Resolution|---                         |DOWNSTREAM
>              Status|REPORTED                    |RESOLVED
> 
> --- Comment #2 from Tobias Leupold <tl@stonemx.de> ---
> I never used Ubuntu, so I simply setup a "blank" Ubuntu 22.04 LTS 
> virtual
> machine to try it out.
> 
> I couldn't install kgeotag using the default package repos, so I 
> suppose it's
> not yet official part of Ubuntu 22.04. Thus, I compiled it from git.
> 
> I had to install the following packages:
> 
> cmake build-essential extra-cmake-modules qtbase5-dev 
> libkf5coreaddons-dev
> libkf5i18n-dev libkf5xmlgui-dev libkf5crash-dev libkf5doctools-dev
> libkf5kexiv2-dev libmarble-dev
> 
> After that, I could compile and install kgeotag without a problem. 
> Also, the
> map is shown as expected.
> 
> Thus, this seems to be a packaging problem. Please contact the package
> maintainer about this, this is not an upstream bug!

It's not too hard to build it manually.

First, you install the needed dependencies:

    sudo apt install cmake build-essential extra-cmake-modules qtbase5-dev libkf5coreaddons-dev libkf5i18n-dev libkf5xmlgui-dev libkf5crash-dev libkf5doctools-dev libkf5kexiv2-dev libmarble-dev

Then, you download the sources:

    git clone https://invent.kde.org/graphics/kgeotag.gi t

Then enter he sources and create a build directory:

    cd kgeotag
    mkdir build
    cd build

Then configure and build the sources:

    cmake ..
    make

And then install it:

    make install

That's it ;-)

Oh,a space slipped in. It's of course

git clone https://invent.kde.org/graphics/kgeotag.git

Thank you very much for the step-by-step.
Must I first uninstall the current kgeotag ?


On 2023-07-30 11:13, Tobias Leupold wrote:
> https://bugs.kde.org/show_bug.cgi?id=472777
> 
> --- Comment #5 from Tobias Leupold <tl@stonemx.de> ---
> It's not too hard to build it manually.
> 
> First, you install the needed dependencies:
> 
>     sudo apt install cmake build-essential extra-cmake-modules 
> qtbase5-dev
> libkf5coreaddons-dev libkf5i18n-dev libkf5xmlgui-dev libkf5crash-dev
> libkf5doctools-dev libkf5kexiv2-dev libmarble-dev
> 
> Then, you download the sources:
> 
>     git clone https://invent.kde.org/graphics/kgeotag.gi t
> 
> Then enter he sources and create a build directory:
> 
>     cd kgeotag
>     mkdir build
>     cd build
> 
> Then configure and build the sources:
> 
>     cmake ..
>     make
> 
> And then install it:
> 
>     make install
> 
> That's it ;-)

Well, the problem in manually installing software is that the package manager doesn't know about this. Probably, it's better to first uninstall the packaged version. You can also keep the build directory so that you can run a "make uninstall" later, this will remove the self-compiled version.

However if you do have an installed version, you can also run the local built one (it will find the files that need to be in defined places).

Just run ./bin/kgeotag from inside your build directory. No need to install it globally in this case.

PS: If you respond to bugzilla via email, don't cite the message you respond to. This will all end up in the online view, cf. https://bugs.kde.org/show_bug.cgi?id=472777 ;-)