Bug 24680 - qgis : vector layer problem
Summary: qgis : vector layer problem
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Dimitrios Glentadakis
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2019-04-17 12:34 CEST by eric gerbier
Modified: 2019-04-20 07:19 CEST (History)
2 users (show)

See Also:
Source RPM: qgis-3.4.6-3.mga7.src.rpm
CVE:
Status comment:


Attachments

Description eric gerbier 2019-04-17 12:34:38 CEST
Description of problem:
when adding a vector layer, qgis is blocked, only way to recover is to kill the process

Version-Release number of selected component (if applicable):
qgis-3.4.6-3.mga7
python3-qgis-3.4.6-3.mga7

How reproducible:


Steps to Reproduce:
1. rm -rf .local/share/QGIS
2. qgis
3. Click on button [Let's get started!]
4. select menu : Layer->Add layer->Add Vector Layer
5. Click on [Cancel] button
Window 'Coordinate Reference System Selector' is deleted and create again immedialtly

Only way to is 'pkill qgis'

When Click on [Cancel] button, on STDOUT the messages are:
src/gui/qgsmapcanvas.cpp:2191 : (mapToolDestroyed) [7256ms] maptool destroyed
src/core/qgsdatasourceuri.cpp:59 : (QgsDataSourceUri) [47ms] = expected after parameter name, skipping text '/usr/share/qgis/resources/data/world_map.qml'
src/gui/qgsmapcanvas.cpp:363 : (setLayersPrivate) [4ms] Layers have changed, refreshing
src/gui/qgsmapcanvas.cpp:494 : (refresh) [1ms] CANVAS refresh - invalid settings -> nothing to do
src/gui/qgsmaptool.cpp:92 : (activate) [0ms] Cursor has been set
src/gui/qgsmapcanvas.cpp:494 : (refresh) [531ms] CANVAS refresh - invalid settings -> nothing to do
Comment 1 David GEIGER 2019-04-17 13:09:03 CEST
I think it would be better to report upstream, this is not a mageia specific bug.

CC: (none) => geiger.david68210

Comment 2 Marja Van Waes 2019-04-20 07:19:40 CEST
(In reply to David GEIGER from comment #1)
> I think it would be better to report upstream, this is not a mageia specific
> bug.

Eric, after reporting it upstream, please come back here and give a link to the upstream bug report.

(Already assigning to our registered qgis maintainer, when a patch or fixed version becomes available upstream, he can use it for Mageia)

Assignee: bugsquad => dglent
Keywords: (none) => UPSTREAM
CC: (none) => marja11


Note You need to log in before you can comment on or make changes to this bug.