[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352050

--- Comment #18 from Artur O.  ---
(In reply to Thomas Lübking from comment #16)
> the video is marked private.
> you can also attach it here or send it by mail

Oh sorry confused it with unlisted, its fixed now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352050

--- Comment #17 from Artur O.  ---
(In reply to Thomas Lübking from comment #16)
> the video is marked private.
> you can also attach it here or send it by mail

Oh sorry confused it with unlisted, its fixed now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway

[Constantine via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=75324

Constantine  changed:

   What|Removed |Added

 CC||hi-an...@yandex.ru

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-plasma] [Bug 360542] New: Default system tray icons don't appear after upgrading Kubuntu 15.10 with KDE Neon packages

[Jonathan Frederickson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360542

Bug ID: 360542
   Summary: Default system tray icons don't appear after upgrading
Kubuntu 15.10 with KDE Neon packages
   Product: frameworks-plasma
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: silverskull...@gmail.com

When I log in on my laptop running Kubuntu with the Neon repositories, the
default icons (network manager, battery, etc.) don't appear in the system tray
(nor in the menu next to it containing the hidden items). Furthermore, they
also don't show up in the "Entries" page of the system tray settings window.

I was looking through the logs, and this looks like it might be relevant:

file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/AbstractItem.qml:27:
TypeError: Cannot read property 'top' of null

I get one of those lines in my logs each time I log in.

Reproducible: Always




Laptop is running Kubuntu 15.10 with KDE Neon repositories.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 353975] Black screen on second display.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353975

--- Comment #16 from bk...@gnu.org ---
I'm using 5.5.4.  Settings --> Configure Desktop --> System Settings --> Help
--> About System Settings --> Version.
I think that is too hard.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 353975] Black screen on second display.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353975

bk...@gnu.org changed:

   What|Removed |Added

 CC||bk...@gnu.org

--- Comment #15 from bk...@gnu.org ---
Did somebody forget to test this?  I'd tell you what my KDE version is, but the
cashew has gone missing, too.  I just installed openSUSE Leap 42.1, so maybe
somebody else knows.  I did go to system-settings -> Display-and-Monitor where
it dutifully shows all the correct information about both monitors.  It doesn't
allow me to rotate 90 degrees, though.  (I will need that when my new monitor
arrives, but not today.)

So I'd like my second monitor wall paper back, please.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 360541] New: Low resolution canvas on Surface Pro 4 with OpenGL turned off

[Chris Jones via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360541

Bug ID: 360541
   Summary: Low resolution canvas on Surface Pro 4 with OpenGL
turned off
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: ch...@outlook.com

With OpenGL turned off, the canvas resolution is at 200% instead of 100% when
Windows is set to the default scaling of 200%.  With Windows scaling set to
100% the canvas is displayed correctly at 100% resolution, but this renders the
UI too small.

Note:  I usually find it preferable to turn OpenGL off when using Krita on the
Surface, since drawing is smoother, and the device heats up uncomfortably
(although Krita 3 seems to run quite warm even with OpenGL off, whereas 2.9x
was notably cooler with it off).

Reproducible: Always




krita3-prealpha3-9694dac, Surface Pro4 265GB i5, 8GB RAM, Windows 10

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 360540] New: Unclear what Amarok uses to define Album Artists in id3 tags

[Daniil Vasin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360540

Bug ID: 360540
   Summary: Unclear what Amarok uses to define Album Artists in
id3 tags
   Product: amarok
   Version: 2.8.90 (2.9 beta)
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Metadata Editing and Reading
  Assignee: amarok-bugs-d...@kde.org
  Reporter: danikva...@gmail.com
CC: 123k...@gmail.com

After using id3 to change the albumartist tag to one artist, Amarok still uses
some other way to sort album artists. What does Amarok read as the Album Artist
from the id3 tag?

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution

[Martin Klapetek via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360478

Martin Klapetek  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Martin Klapetek  ---
I think that's actually quite sensible. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

[m00nraker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #26 from m00nraker  ---
Comment #21 is Ok.
#22 to #24 is trash. Don't read ! Sry.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

[m00nraker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #25 from m00nraker  ---
Created attachment 97903
  --> https://bugs.kde.org/attachment.cgi?id=97903=edit
nvidia-settings -q all

output
nvidia-settings -q all

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

[m00nraker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360033

m00nraker  changed:

   What|Removed |Added

  Attachment #97902|0   |1
is obsolete||

--- Comment #24 from m00nraker  ---
Comment on attachment 97902
  --> https://bugs.kde.org/attachment.cgi?id=97902
nvidia-settings -q all

wrong upload

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

[m00nraker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #23 from m00nraker  ---
Comment on attachment 97902
  --> https://bugs.kde.org/attachment.cgi?id=97902
nvidia-settings -q all

export GL_EXT_BLACKLIST=GLX_ARB_create_context

kwin_x11 --replace &  

[1] 3804
test@linux-gss9:~> QXcbConnection: XCB error: 8 (BadMatch), sequence: 820,
resource id: 69206021, major code: 42 (SetInputFocus), minor code: 0
blacklist? false true
OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce Go 7950 GTX/PCIe/SSE2
OpenGL version string:  2.1.2 NVIDIA 304.131
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 304.131
GPU class:  NV40/G70
OpenGL version: 2.1.2
GLSL version:   1.20
X server version:   1.17.2
Linux kernel version:   4.1.15
Requires strict binding:no
GLSL shaders:   limited
Texture NPOT support:   yes
Virtual Machine:no
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 0, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.44882, 0.14882, 0.14882,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.50064, 0.80064, 0.50064,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.05054, 0.05054, 0.35054,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0, 0, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0.4, 0, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 0.5, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0.4, 0.5, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.134646, 0.044646,
0.044646, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.200256, 0.320256,
0.200256, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.02527, 0.02527, 0.17527,
0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.360172, 0.390172,
0.420172, 0.6)
kwin_core: ShaderManager self test failed
kwin_core: Failed to initialize compositing, compositing disabled
QXcbConnection: XCB error: 3 (BadWindow), sequence: 926, resource id: 579,
major code: 3 (GetWindowAttributes), minor code: 0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

[m00nraker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #22 from m00nraker  ---
Created attachment 97902
  --> https://bugs.kde.org/attachment.cgi?id=97902=edit
nvidia-settings -q all

output
nvidia-settings -q all

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

[m00nraker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #21 from m00nraker  ---
Thx for reply and working on that bug-report.
Fail again (blacklist? false true):

export KWIN_GL_EXT_BLACKLIST=GLX_ARB_create_context
kwin_x11 --replace &

QXcbConnection: XCB error: 8 (BadMatch), sequence: 820, resource id: 69206021,
major code: 42 (SetInputFocus), minor code: 0
blacklist? false true
OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce Go 7950 GTX/PCIe/SSE2
OpenGL version string:  2.1.2 NVIDIA 304.131
OpenGL shading language version string: 1.20 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 304.131
GPU class:  NV40/G70
OpenGL version: 2.1.2
GLSL version:   1.20
X server version:   1.17.2
Linux kernel version:   4.1.15
Requires strict binding:no
GLSL shaders:   limited
Texture NPOT support:   yes
Virtual Machine:no
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 0, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 1, 0, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.44882, 0.14882, 0.14882,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.50064, 0.80064, 0.50064,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.05054, 0.05054, 0.35054,
1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(1, 1, 1, 1)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0, 0, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0.4, 0, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0, 0, 0.5, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.3, 0.4, 0.5, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.134646, 0.044646,
0.044646, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.200256, 0.320256,
0.200256, 0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.02527, 0.02527, 0.17527,
0.6)
Pixel was QVector4D(0, 0, 0, 0) expected QVector4D(0.360172, 0.390172,
0.420172, 0.6)
kwin_core: ShaderManager self test failed
kwin_core: Failed to initialize compositing, compositing disabled
QXcbConnection: XCB error: 3 (BadWindow), sequence: 926, resource id: 579,
major code: 3 (GetWindowAttributes), minor code: 0

nvidia-settings -q all
Output in attached file nvidia-output.txt

Another thing:
After I applied your first patch, I injected the debug-output code directly
into glxbackend.cpp, as you suggested. To make sure that everything is ok,
could you maybe upload a complete diff-file for me to apply? (I'm confused
about the "...GlxBackend::initRenderingContext() return false;" in your debug
output code in comment #14). Do not forget that I'm not a software developer
and I haven't many experience in editing source code. So a complete diff file
would be the better choice for me, to make clear, that everything is as it
should be :-) Nevertheless I'm quite sure, that I did it right.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360538] Search bar inactive after using apply button in desktop effects configuration

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360538

--- Comment #3 from Thomas Lübking  ---
Does it show a focus frame (when you click into it)?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeplasma-addons] [Bug 360120] Show Desktop Applet corrupts panel when added to it (spacing issues)

[aka google01103]

https://bugs.kde.org/show_bug.cgi?id=360120

bill p. (aka google01103)  changed:

   What|Removed |Added

 CC||dweeble01...@gmail.com

--- Comment #2 from bill p. (aka google01103)  ---
similar but a bit more bizarre - adding it to the panel (which is centered and
not maximized) causes the panel to move to the top and be left aligned.

as with original poster placing it on the desktop is not problematic

openSUSE Leap 42.1, Plasma 5.5.95, Frameworks 5.20.0, QT 5.5.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360536] The fall apart effect is applied to the task switcher (tabbox)

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360536

--- Comment #2 from hid...@gmx.de ---
thumbnails

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360536] The fall apart effect is applied to the task switcher (tabbox)

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360536

--- Comment #1 from Thomas Lübking  ---
Which tabbox do you use?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session

[Fuchs via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360537

--- Comment #2 from Fuchs  ---
Ignore the last comment, actual issue is the following: 

per default the key triggers keycode 236 (keysym 0x1008ff04,
XF86KbdLightOnOff), which by default in KDE Plasma is configured to toggle the
keyboard light. However, at the same time the keyboard light is changed by the
BIOS. This seems to get plasma / powerdevil in a confused state so it doesn't
stop cycling through them. 

If somehow possible, I highly recommend disabling that default keybinding on
affected thinkpads. If not possible some logic will be needed to avoid that,
because otherwise owners of affected hardware will run into this issue with
recent kernels and KDE plasma, changing their keyboard brightness leading to an
endless cycle  (which, as a side effect, triggers the lovely pop up which won't
disappear either. In short: the session is rendered quite unusable) 

If I can somehow help resolving this issue  (xev or dbus monitor logs or
whatnot): let me know. 

Workaround for me: disable that keybinding in systemsettings.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360538] Search bar inactive after using apply button in desktop effects configuration

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360538

--- Comment #2 from hid...@gmx.de ---
I cannot edit the text, but there is also no graphical feedback of the bar
being disabled, i.e. it's not greyed out.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

[Simon via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

Simon  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 354823] Plasma crashes on multiscreen setup activation

[Dennis Schridde via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=354823

Dennis Schridde  changed:

   What|Removed |Added

 CC||devuran...@gmx.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

[Simon via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

--- Comment #8 from Simon  ---
This is embarrassing, sorry for wasting your time and thanks for your 
patience:
I used git://anongit.kde.org/digikam instead of using the 
software-compilation repo. Using the software-repo this problem 
disappears (and would have never come up in the first place).
This "bug" can be closed.

On 14/03/16 22:42, Maik Qualmann via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360528
>
> --- Comment #7 from Maik Qualmann  ---
> Please look here:
> https://www.digikam.org/download?q=download/GIT
>
> Maik
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session

[Fuchs via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360537

--- Comment #1 from Fuchs  ---
Looking at the code so far, my best guess would be that it tries to round (with
the very limited amount of steps, 0,1,2) and horribly fails, which never lets
it rest at a certain value. If that is the case, I hope the logic can be
adapted to cope with that. Otherwise someone needs to dig a bit further.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360538] New: Search bar inactive after using apply button in desktop effects configuration

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360538

Bug ID: 360538
   Summary: Search bar inactive after using apply button in
desktop effects configuration
   Product: kwin
   Version: 5.5.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: hid...@gmx.de

When using the "Desktop Effects" configuration menu, using the apply button
renders the filter unusable. One can select its text but not edit it.

Reproducible: Always

Steps to Reproduce:
1. Open "Desktop Effects" configuration
2. Make a change to the configuration
3. Hit apply
4. Try to edit the filter

Actual Results:  
Filter is not editable.

Expected Results:  
Filter should be editable

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 360537] New: Keyboard Backlight endless loop when changed, only inside plasma session

[Fuchs via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360537

Bug ID: 360537
   Summary: Keyboard Backlight endless loop when changed, only
inside plasma session
   Product: Powerdevil
   Version: 5.5.95
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: deve...@fuchsnet.ch

I have a thinkpad T430 which recently gained a better keyboard backlight
driver. 
It works in a VT both with the keyboard shortcut (FN+Space) or via dbus,
however, it breaks when inside a Plasma 5 session, as there is an endless loop
of the backlight cycling between the 3 states. 

qdbus --system org.freedesktop.UPower /org/freedesktop/UPower/KbdBacklight
org.freedesktop.UPower.KbdBacklight.GetBrightness   
0

qdbus --system org.freedesktop.UPower /org/freedesktop/UPower/KbdBacklight
org.freedesktop.UPower.KbdBacklight.GetMaxBrightness
2


Reproducible: Always

Steps to Reproduce:
0. Have a Thinkpad T430  (other models might be affected too, I don't have any)
1. Be in a Plasma 5 session
2. Change the Keyboard backlight, either via keyboard, via dbus or via the
battery plasmoid

Actual Results:  
Brightness endlessly cycles through possible states

Expected Results:  
Brightness is set correctly, as it is when switching to a VT

Plasma is 5.6 Beta, Qt is 5.5.1,  Kernel is 4.5 

Any information on how I could debug and solve this is appreciated.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360536] The fall apart effect is applied to the task switcher (tabbox)

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360536

hid...@gmx.de changed:

   What|Removed |Added

 CC||hid...@gmx.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360536] New: The fall apart effect is applied to the task switcher (tabbox)

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360536

Bug ID: 360536
   Summary: The fall apart effect is applied to the task switcher
(tabbox)
   Product: kwin
   Version: 5.5.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: tabbox
  Assignee: kwin-bugs-n...@kde.org
  Reporter: hid...@gmx.de

When the fall apart effect is enabled, it also is used when the task switcher
disappears after use.

Reproducible: Always

Steps to Reproduce:
1. Enable fall apart effect
2. Use task switcher such that its overlay is shown
3. Select a window

Actual Results:  
Fall apart effect is applied to the switcher.

Expected Results:  
The effect should probably not be applied since a user will not expect it and
be distracted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360140] Deleted uses the direct window type, but doesn't perform hack resolutions

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360140

--- Comment #14 from hid...@gmx.de ---
Disabling those extensions (I just used fade from the kcmkwin assuming it is
kwin4_effect_fade) makes the effect appear only once and in full length (which
it didn't before, it was two times very quick and short).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 360535] New: Crash on add to favorites

[Ric via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360535

Bug ID: 360535
   Summary: Crash on add to favorites
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ricardo.adams...@gmail.com

Application: lancelot (1.9.5)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-38-generic x86_64
Distribution: Linux Mint 17.3 Rosa

-- Information about the crash:
- What I was doing when the application crashed:
For years, the lancelot launchers crashes when I add a application to
favorites. Note: this only happens it the favorites column is full. A manual
resizing of the laucher is required before adding a new item to prevent the
crash. Otherwise the menu crashes every time. thanks

The crash can be reproduced every time.

-- Backtrace:
Application: Lancelot (lancelot), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f62c020b800 (LWP 28389))]

Thread 3 (Thread 0x7f629c9a1700 (LWP 28390)):
#0  0x7f62bc57e82d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f62adc6ff75 in ?? () from
/usr/lib/nvidia-352/tls/libnvidia-tls.so.352.63
#2  0x7f62b400bc10 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f62b3fcab14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f62b3fcaf7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f62b3fcb0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f62bcd067be in QEventDispatcherGlib::processEvents
(this=0x7f62980008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#7  0x7f62bccd80af in QEventLoop::processEvents
(this=this@entry=0x7f629c9a0da0, flags=...) at kernel/qeventloop.cpp:149
#8  0x7f62bccd83a5 in QEventLoop::exec (this=this@entry=0x7f629c9a0da0,
flags=...) at kernel/qeventloop.cpp:204
#9  0x7f62bcbd4c5f in QThread::exec (this=this@entry=0xbcc640) at
thread/qthread.cpp:537
#10 0x7f62bccb9823 in QInotifyFileSystemWatcherEngine::run (this=0xbcc640)
at io/qfilesystemwatcher_inotify.cpp:265
#11 0x7f62bcbd732f in QThreadPrivate::start (arg=0xbcc640) at
thread/qthread_unix.cpp:349
#12 0x7f62b48eb182 in start_thread (arg=0x7f629c9a1700) at
pthread_create.c:312
#13 0x7f62bc58d47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f6292d6b700 (LWP 28391)):
#0  0x7f62b48ee7ee in __pthread_mutex_unlock_usercnt (decr=1,
mutex=0x7f628c000a80) at pthread_mutex_unlock.c:57
#1  __GI___pthread_mutex_unlock (mutex=0x7f628c000a80) at
pthread_mutex_unlock.c:310
#2  0x7f62b400c9b1 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f62b3fca680 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f62b3fcaf03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f62b3fcb0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f62bcd067be in QEventDispatcherGlib::processEvents
(this=0x7f628c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#7  0x7f62bccd80af in QEventLoop::processEvents
(this=this@entry=0x7f6292d6ada0, flags=...) at kernel/qeventloop.cpp:149
#8  0x7f62bccd83a5 in QEventLoop::exec (this=this@entry=0x7f6292d6ada0,
flags=...) at kernel/qeventloop.cpp:204
#9  0x7f62bcbd4c5f in QThread::exec (this=this@entry=0xbb42e0) at
thread/qthread.cpp:537
#10 0x7f62bccb9823 in QInotifyFileSystemWatcherEngine::run (this=0xbb42e0)
at io/qfilesystemwatcher_inotify.cpp:265
#11 0x7f62bcbd732f in QThreadPrivate::start (arg=0xbb42e0) at
thread/qthread_unix.cpp:349
#12 0x7f62b48eb182 in start_thread (arg=0x7f6292d6b700) at
pthread_create.c:312
#13 0x7f62bc58d47d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f62c020b800 (LWP 28389)):
[KCrash Handler]
#6  size (this=) at /usr/include/qt4/QtCore/qlist.h:98
#7  size (this=) at /usr/include/qt4/QtCore/qlist.h:137
#8  Lancelot::Models::Applications::contextActivate (this=0x1, index=1,
context=0x2329480) at ../../../libs/lancelot-datamodels/Applications.cpp:307
#9  0x7f62bf24bd64 in Lancelot::ActionListViewItemFactory::itemContext
(this=0x226afa0, sender=sender@entry=0x22ee9b0, mouseCoordinate=, mouseCoordinate@entry=true) at
../../../libs/lancelot/widgets/ActionListView.cpp:621
#10 0x7f62bf24be76 in Lancelot::ActionListViewItem::contextMenuEvent
(this=0x22ee9b0, event=0x7ffdbcef7620) at
../../../libs/lancelot/widgets/ActionListView.cpp:109
#11 0x7f62bda2f655 in QGraphicsItem::sceneEvent (this=0x22ee9c0,
event=0x7ffdbcef7620) at graphicsview/qgraphicsitem.cpp:6725
#12 0x7f62bda567aa in QGraphicsScene::contextMenuEvent 

[kwin] [Bug 360140] Deleted uses the direct window type, but doesn't perform hack resolutions

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360140

--- Comment #13 from Thomas Lübking  ---
I could not reproduce any double invocation.

Does it remain if you disable:

kwin4_effect_fade
blur
contrast

-- 
You are receiving this mail because:
You are watching all bug changes.

[umbrello] [Bug 350287] Not possible to cancel paste on tree view

[Ralf Habacker via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350287

--- Comment #1 from Ralf Habacker  ---
The problem is that in UMLPackage::addObject(UMLObject *pObject) canceling the
dialog did not breaks the loop. An additional problem is that canceling is not
propagated to higher levels in the call tree.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360140] Deleted uses the direct window type, but doesn't perform hack resolutions

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360140

--- Comment #12 from hid...@gmx.de ---
Created attachment 97901
  --> https://bugs.kde.org/attachment.cgi?id=97901=edit
Urxvt xprop

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360140] Deleted uses the direct window type, but doesn't perform hack resolutions

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360140

--- Comment #11 from hid...@gmx.de ---
Glad to see there is some issue resolved in the core code now, I just stumbled
upon this issue while trying some settings.
I don't think it's need anymore but I attached the xprop of a urxvt window
anyway.
Will the fix also resolve the effect being applied twice?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 360488] dolphin with >=kde-frameworks-5.20 crashes when copy+paste file in same directory

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360488

d...@kaosx.us changed:

   What|Removed |Added

 CC||d...@kaosx.us

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360500] Unable to enter the same value in the No. field for more than 1 transaction.

[allan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360500

--- Comment #4 from allan  ---
On 14/03/16 18:45, Christian David via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360500
>
> Christian David  changed:
>
> What|Removed |Added
> 
>   CC||christian-da...@web.de
>
> --- Comment #3 from Christian David  ---
> In void TransactionEditor::slotNumberChanged(const QString& txt):
>
> Why do you use loadText() and not setText() in you patch?

There are two separate routines involved, and one was using loadText() 
and the other setText(). I couldn't see any reason for the difference, 
and just decided to use loadText().

> However, the loadText() seems unnecessary to me.

In the routine you refer to, then, yes, it does seem unnecessary, but 
not so in void TransactionEditor::assignNextNumber().  The first one 
there is necessary.

Allan

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360033] Cannot enable compositing with OpenGL GLX

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360033

--- Comment #20 from Thomas Lübking  ---
Ok, despite the wrong output (the debug output should have been
GLX_ARB_create_context_robustness) is confusion, the problem is not related to
the robust contexts.

Since we now have the neat feature to blacklist stuff at will, let's try legacy
context creation.

export KWIN_GL_EXT_BLACKLIST=GLX_ARB_create_context
kwin_x11 --replace &

If that fails as well, please attach (do NOT post it ;-) the output of
"nvidia-settings -q all"


---
Sorry for the delay.

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.

[Walter Rudametkin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356853

Walter Rudametkin  changed:

   What|Removed |Added

 CC||rudamet...@gmail.com

--- Comment #13 from Walter Rudametkin  ---
Patch works for me.

However, I've also got this bug regarding focus being off and shortcuts not
working if mouse is above Yakuake when it appears:
https://bugs.kde.org/show_bug.cgi?id=360234

Maybe they are related ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360534] Digikam crashes every time I try to start Editor

[Uffe via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360534

--- Comment #3 from Uffe  ---
Hi
1. GDG backtrace is attached in this case
2. v.3.5.0 is the latest there is in "Programcentral for Ubuntu" and I'm not a
guru in Unix so download and compile on my own hasn't been a success so far.
I've downloaded Digikam several times but have not the slightest idea how to
install it after decompressed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 360234] Cursor not in focus while Yakuake it is

[Walter Rudametkin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360234

Walter Rudametkin  changed:

   What|Removed |Added

 CC||rudamet...@gmail.com

--- Comment #6 from Walter Rudametkin  ---
Same problem here. If mouse is above Yakuake when it appears focus is wrong and
copy/paste shortcuts don't work.

If the display animation is set around 130ms the problem goes away. That is,
the terminal appears with a slow animation speed, the cursor block shows as if
it is not focused, but the shortcuts continue work and the terminal is properly
focused. If I speed up the animation, to around ~90ms, it's hit and miss. At
0ms (my prefered speed), copy/paste never works right.

It looks like there are a couple of focus bugs that appeared recently. Maybe
they are all related ?
https://bugs.kde.org/show_bug.cgi?id=356853

Regards,

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360534] Digikam crashes every time I try to start Editor

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360534

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||caulier.gil...@gmail.com
 Resolution|--- |BACKTRACE

--- Comment #1 from caulier.gil...@gmail.com ---
1/ We need a GDB backtrace to investiguate.

2/ Update your digiKam version to last 4.14.0 and try again 3.5.0 is very old.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360534] New: Digikam crashes every time I try to start Editor

[Uffe via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360534

Bug ID: 360534
   Summary: Digikam crashes every time I try to start Editor
   Product: digikam
   Version: 3.5.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Raw-Workflow
  Assignee: digikam-de...@kde.org
  Reporter: maila...@gmail.com

Every time I click on the "Editorbutton" on a marked picture in "Previewmode"
taken by a Nikon D3300, Digikam crashes and close down. I also have a D90 and a
D600 but none of them causes any problem for Digikam.

Reproducible: Always

Steps to Reproduce:
The crash can be reproduced every time just clicking the Editorbutton

Actual Results:  
Digikam crashes and close down


Application: digikam (3.5.0)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.13.0-79-lowlatency x86_64
Distribution: Ubuntu 14.04.4 LTS

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 359831] Glide effect doesn't filter minimized windows

[Federico via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359831

--- Comment #2 from Federico  ---
Thank you very much for the fix :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 359831] Glide effect doesn't filter minimized windows

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359831

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Thomas Lübking  ---
diff --git a/effects/glide/glide.cpp b/effects/glide/glide.cpp
index 76016b0..885364c 100644
--- a/effects/glide/glide.cpp
+++ b/effects/glide/glide.cpp
@@ -212,6 +212,8 @@ bool GlideEffect::isGlideWindow(EffectWindow* w)
 {
 if (effects->activeFullScreenEffect())
 return false;
+if (!w->isVisible())
+return false;
 if (w->data(IsGlideWindow).toBool())
 return true;
 if (m_atom.isValid() && !w->readProperty( m_atom, m_atom, 32 ).isNull())

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

--- Comment #7 from Maik Qualmann  ---
Please look here:
https://www.digikam.org/download?q=download/GIT

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

--- Comment #5 from Maik Qualmann  ---
Do you have remove the build directory and run the bootstrap.linux script
again?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

[Simon via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

--- Comment #4 from Simon  ---
That gave the same result. You are right about the Qt installation. I 
only installed the packages that were necessary for cmake to run without 
errors. Therefore I was missing the qtpaths binary file for qt5, I only 
had a wrapper binary by qtchooser. Installing qttools5-dev-tools 
provides the necessary file and now the output is correct:

(stretch-digikam5)simon@simon-x220-deb:/usr$ qtpaths --plugin-dir
/usr/lib/x86_64-linux-gnu/qt5/plugins

I uninstalled, recompiled and installed digikam but the plugin files are 
stilled installed in lib/x86_64-linux-gnu/plugins/.

On 14/03/16 20:36, Maik Qualmann via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360528
>
> --- Comment #3 from Maik Qualmann  ---
> Then should "qtpaths --writable-path HomeLocation" also do not work? DigiKam
> uses QStandardPaths to find folders and datas. This has to work, otherwise
> digiKam will not work properly. I think something is wrong with your Qt
> installation.
>
> Maik
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[umbrello] [Bug 360533] New: Mouse-Zoom should keep current mouse pointer at the same point on diagram

[Xtra Coder via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360533

Bug ID: 360533
   Summary: Mouse-Zoom should keep current mouse pointer at the
same point on diagram
   Product: umbrello
   Version: 2.18.2 (KDE Applications 15.12.2)
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: xtraco...@gmail.com

Mouse zoom works in a 'somewhat' unpredictable manner.

Reproducible: Always

Steps to Reproduce:
1. Create new diagram, add 'Class1' into top-left part of diagram, 'Class2' -
bottom-right
2. Put mouse pointer exactly to top-left corner of 'Class1'. Scroll mouse
in-and-out - at huge zoom Class1 goes off-screen
3. Put mouse pointer exactly to bottom-right corner of 'Class2'. Scroll mouse
in-and-out - Class2 goes off-screen.

Actual Results:  
See 'Steps to Reproduce'.

Additionally to that - after zooming to min/max value - mouse zoom does not
return to 100%, it will be 107% - not a major problem, but is slightly
unexpected.

Expected Results:  
Zooming with mouse in 'Steps to Reproduce' should keep mouse pointer exactly at
top-left corner for 'Class1' and bottom-right corner for 'Class2'.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lokalize] [Bug 360532] New: Does not find missing PO if folder not there

[Frederik Schwarzer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360532

Bug ID: 360532
   Summary: Does not find missing PO if folder not there
   Product: lokalize
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: project management
  Assignee: sha...@ukr.net
  Reporter: schwar...@kde.org

Hi,

if, for example, the folder
templates/playground-multimedia
contains a POT file but the folder
de/playground-multimedia
does not yet exist, Lokalize does not show me the missing PO file in the
Project Overview.

This happens mainly when using git-svn for managing KDE translations because
git-svn removed empty folders but might bite others in different setups as
well.

Regards

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[umbrello] [Bug 360531] New: Line Styles are not correctly created initially and restored from file

[Xtra Coder via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360531

Bug ID: 360531
   Summary: Line Styles are not correctly created initially and
restored from file
   Product: umbrello
   Version: 2.18.2 (KDE Applications 15.12.2)
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: xtraco...@gmail.com

When 'dependency' line is initially created, after creation - it is always 1px
width solid line. After opening line properties and changing any Line Style
property, e.g. color, and clicking 'OK' - line is redrawn correctly (note:
'Apply' does work correctly).

After saving and reopening of the file - all lines are again displayed as '1px
solid'.


Reproducible: Always

Steps to Reproduce:
1. Go to 'Settings' -> 'Configure Umbrello URL Modeller' -> 'User Interface':
Set Custom line color (green) and width (4px)
2. Add 2 Classes to diagram and draw 'Dependency' between them
3. Open line props, set line color to 'blue'
4. Click 'Apply'
5. Click 'OK'
6. Save and Close file
7. Reopen File

Actual Results:  
2. Line is created as '1px solid red'
4. upon 'Apply' only arrow style of line is changed, moreover - end arrow is
drawn using 'dashed' style and therefore it is not symmetric - one side is
longer than the other side
7. After reopening all lines are 'solid'


Expected Results:  
2. line should be created with the style in currently line settings (see
'Settings' -> 'Configure Umbrello URL Modeller' -> 'User Interface')
4. 'Apply' should have same result as 'OK', but without closing the dialog
7. 'dependency' lines should be 'dashed'

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution

[Mircea Kitsune via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360478

--- Comment #2 from Mircea Kitsune  ---
(In reply to Martin Klapetek from comment #1)

I'm not sure what the best solution is either. I can only say as a user that
the current behavior is problematic, and I think we need a way to prevent
applications from accidentally breaking the desktop when changing the display
resolution. I'm inclined toward remembering each widget's positioning per
resolution though.

Example: Your screen is set to the standard resolution of say 1600 x 1200. You
add a new plasmoid to the desktop, so its scale and position are stored under
the 1600 x 1200 field. Now a game sets the display to 1024 x 768; If it's the
first time this happens, we automatically reposition the plasmoid and store the
new shape in the 1024 x 768 field... whereas if the field already exists, we
simply move it to the existing shape for this resolution. If the user ever
resizes or repositions a plasmoid, we drop all cached resolutions except for
the current one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 360530] New: Kontact crashed when clicking link in eMail

[rainer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360530

Bug ID: 360530
   Summary: Kontact crashed when clicking link in eMail
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kdeb...@munin-soft.de

Application: kontact (5.1.2)

Qt Version: 5.5.1
Operating System: Linux 4.4.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160307) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I viewed an HTML-eMail in Kontact than I clicked on the link to switch to HTML
view.
After that I started a new Firefox window on the same desktop, switched back to
contact and clicked on a link in the eMail. The document was not opened in
Firefox.
Restarting Kontact and re-doing these step led to a successful opening of the
target page in Firefox.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc7b7c47900 (LWP 2213))]

Thread 24 (Thread 0x7fc7997b0700 (LWP 2237)):
#0  0x7fc7b48d349d in poll () at /lib64/libc.so.6
#1  0x7fc7ae047432 in  () at /usr/lib64/libxcb.so.1
#2  0x7fc7ae049007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fc79b8fee29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc7b51da94f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fc7adc234a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7fc7b48dbded in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7fc7925cf700 (LWP 2239)):
#0  0x7fc7adc2907f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc7b24752ab in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b24752e9 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7adc234a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc7b48dbded in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7fc74d38d700 (LWP 2247)):
#0  0x7fc7ad44b554 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc7ad40736e in g_main_context_acquire () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc7ad408165 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc7ad40839c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc7b53ff52b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fc7b53a961a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fc7b51d5b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fc7b51da94f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc7adc234a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc7b48dbded in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7fc740611700 (LWP 2265)):
#0  0x7fc7adc2907f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc7b2183754 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b24a4131 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7adc234a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc7b48dbded in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7fc737fff700 (LWP 2266)):
#0  0x7fc7adc2907f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc7b2184783 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b24a4131 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7adc234a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc7b48dbded in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7fc73fdf1700 (LWP 2267)):
#0  0x7fc7adc2907f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc7b2184783 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b24a4131 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7adc234a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc7b48dbded in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7fc73f5f0700 (LWP 2268)):
#0  0x7fc7adc2907f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc7b2184783 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b24a4131 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7adc234a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc7b48dbded in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7fc73edef700 (LWP 2269)):
#0  0x7fc7adc2907f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc7b2184783 in  () at /usr/lib64/libQt5WebKit.so.5
#2  0x7fc7b24a4131 in  () at /usr/lib64/libQt5WebKit.so.5
#3  0x7fc7adc234a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc7b48dbded in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7fc73e5ee700 (LWP 2270)):
#0  0x7fc7adc2907f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  

[krita] [Bug 344685] Tablet intermittently unresponsive.

[Boudewijn Rempt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=344685

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||b...@valdyas.org

--- Comment #1 from Boudewijn Rempt  ---
Hi,

Thanks for your report. Unfortunately we don't have test hardware to try and
reproduce the issue. But we did rewrite tablet input support for 3.0, so could
you give the 3.0 pre-alpha 3 a try?
http://files.kde.org/krita/3/windows/krita3-prealpha3-9694dac.zip

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 330952] Incorrect interest value in a loan account

[Christian David via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=330952

Christian David  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||christian-da...@web.de
 Resolution|--- |INVALID

--- Comment #25 from Christian David  ---
The date can be set on the "details" sheet. Changing it in the last step may
change other settings from other steps. So deactivating it should be okay.

As you requested I mark this bug resolved. Please feel free to reopen it if
necessary.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

--- Comment #3 from Maik Qualmann  ---
Then should "qtpaths --writable-path HomeLocation" also do not work? DigiKam
uses QStandardPaths to find folders and datas. This has to work, otherwise
digiKam will not work properly. I think something is wrong with your Qt
installation.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360485] digikam rescans image collection after change of time zone

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360485

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
If the time zone is changed, the modification date of files is changed.
Therefore digiKam starts a rescan.

date -r test.jpg  => Fr 20. Nov 22:41:35 CET 2015
timedatectl set-timezone America/New_York
date -r test.jpg  => Fr 20. Nov 16:41:35 EST 2015
timedatectl set-timezone Europe/Berlin
date -r test.jpg  => Fr 20. Nov 22:41:35 CET 2015

I see at the moment is no easy way to change this. Date / time store in DB as
UTC and only users visible entries convert to local date / time?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

[Simon via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

--- Comment #2 from Simon  ---
This results in
qtpaths: could not find a Qt installation of ''

On 14/03/16 19:48, Maik Qualmann via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=360528
>
> Maik Qualmann  changed:
>
> What|Removed |Added
> 
>   CC||metzping...@gmail.com
>
> --- Comment #1 from Maik Qualmann  ---
> Digikam uses "qtpaths --plugin-dir" to find the plugin directory. Which
> directory is displayed with "qtpaths --plugin-dir"?
>
> Maik
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 331137] git->Show Differences closes file

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=331137

--- Comment #5 from pej...@gmail.com ---
It works for me too. Maybe time to close this bug

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation in Polish

[NSLW via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360129

--- Comment #16 from NSLW  ---
(In reply to allan from comment #15)
> > > I know no Polish financial terms.  If the Buy list contains a correct 
> > > Polish
> > > term, then that I presume was added by the translator.  A possible
> > > explanation is that at line 161 (in my version) of investprocessing.cpp 
> > > the
> > > following appears - "m_buyList += i18nc("verb", "buy");  //   
> > >   
> > > some basic entries in case rc file missing".  It may be that that was when
> > > the translation for Buy was added.  However, the next line is similar for
> > > the Sell operation, and that was not translated apparently.
> > 
> > All terms are and were translated.
> 
> In the rc file snippet you attached, only Buy and Reinvdiv have content.

That's right and that also shows that KMM has bug inside.
Please see translation progress of KMM to Polish to know that it is translated
fully 
http://l10n.kde.org/stats/gui/trunk-kf5/team/pl/extragear-office/

Please read also what I wrote you about the bug I'm seeing
> > After the patch my csvimporterrc is
> > filled out automatically with all the data whereas before the patch only
> > BuyParam and ReinvdivParam were filled out.

And finally please see into code of investprocessing.cpp

BuyParam and  ReinvdivParam are assigned like this

QStringList list = profilesGroup.readEntry("BuyParam", QStringList());
if (!list.isEmpty()) {
  m_buyList = list;
}


whereas other parameters and it includes SellParam is assigned like this


m_sellList = profilesGroup.readEntry("SellParam", QStringList());


and that's the reason why you don't see SellParam in rc file and not the
missing translation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] Digikam looks for digikamimageplugins in different directory than they were installed to

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Digikam uses "qtpaths --plugin-dir" to find the plugin directory. Which
directory is displayed with "qtpaths --plugin-dir"?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

[Alexey Chernov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355275

Alexey Chernov <4er...@gmail.com> changed:

   What|Removed |Added

 CC||4er...@gmail.com

--- Comment #51 from Alexey Chernov <4er...@gmail.com> ---
Sorry for being too late, I faced this issue while porting Kopete to KF5 and
fixed it with some minor commit:
https://quickgit.kde.org/?p=kopete.git=commit=0f259ada3a4646b0230d6870ff185adfcb3b1085.

To my investigation on this crash, it seems to be not due to the deletion order
itself, but because of reparenting KHTML's view() subpart from previous parent
specified in ctor call to QSplitter which leads to double deletion of the
widget. I didn't dig into details, but in my toy application with KParts this
is not preproducible without KHTML. Given that specifying parent for widget
which gets reparented in a couple of lines doesn't change things too seriously,
I just removed this specification. In general, it seems that there's some issue
with parent changing and double deletion. @Alex Merry probably have more
details on this, maybe he has some ideas about the actual cause according to
this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352050

--- Comment #16 from Thomas Lübking  ---
the video is marked private.
you can also attach it here or send it by mail

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360500] Unable to enter the same value in the No. field for more than 1 transaction.

[Christian David via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360500

Christian David  changed:

   What|Removed |Added

 CC||christian-da...@web.de

--- Comment #3 from Christian David  ---
In void TransactionEditor::slotNumberChanged(const QString& txt): 

Why do you use loadText() and not setText() in you patch?
However, the loadText() seems unnecessary to me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360391] Auto-hiding panel does not return

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360391

--- Comment #6 from christ...@whoop.org ---
Martin, the problem is absolute ... speeds, directions, etc make no difference.
Once the panel disappears, there's no way to get it back.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360391] Auto-hiding panel does not return

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360391

--- Comment #5 from christ...@whoop.org ---
Created attachment 97899
  --> https://bugs.kde.org/attachment.cgi?id=97899=edit
My ~/.config/plasma-org.kde.plasma.desktop-appletsrc

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360391] Auto-hiding panel does not return

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360391

--- Comment #4 from christ...@whoop.org ---
Thanks for the follow-ups, guys. For plasma's version, let me know what
specific commands I can help with. Here are the relevant packages:

plasma-breeze-5.5.4-1.fc23.x86_64
plasma-breeze-5.5.5-1.fc23.x86_64
plasma-breeze-common-5.5.4-1.fc23.noarch
plasma-breeze-common-5.5.5-1.fc23.noarch
plasma-desktop-5.5.5-1.fc23.x86_64
plasma-desktop-doc-5.5.5-1.fc23.noarch
plasma-milou-5.5.5-1.fc23.x86_64
plasma-pa-5.5.5-1.fc23.x86_64
plasma-pk-updates-0.2-7.20160216git.fc23.x86_64
plasma-systemsettings-5.5.5-1.fc23.x86_64
plasma-workspace-5.5.5-2.fc23.x86_64
plasma-workspace-common-5.5.4-2.fc23.x86_64
plasma-workspace-common-5.5.5-2.fc23.x86_64
plasma-workspace-drkonqi-5.5.5-2.fc23.x86_64
plasma-workspace-geolocation-5.5.5-2.fc23.x86_64
plasma-workspace-geolocation-libs-5.5.5-2.fc23.x86_64
plasma-workspace-libs-5.5.5-2.fc23.x86_64

Here's the xrandr output:

$ xrandr -q
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 531mm x 299mm
   1920x1080 60.00*+
   1280x1024 75.0260.02
   1152x864  75.00
   1024x768  75.0360.00
   800x600   75.0060.32
   640x480   75.0059.94
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-D-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis)
531mm x 299mm
   1920x1080 60.00*+
   1280x1024 75.0260.02
   1152x864  75.00
   1024x768  75.0360.00
   800x600   75.0060.32
   640x480   75.0059.94

I'm attaching the Plasma config file.

-- 
You are receiving this mail because:
You are watching all bug changes.

[muon] [Bug 360529] New: in muon changelog has disappeared

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360529

Bug ID: 360529
   Summary: in muon changelog has disappeared
   Product: muon
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: p...@free.fr
CC: echidna...@kubuntu.org, sit...@kde.org

Previoulsly we could see the changelog for each package update, now muon only
show liste of package updates, but I am unable to display the attached
changelog. Is this a missing feature ?

Reproducible: Always

Steps to Reproduce:
wait for muon updater to alert on updates
click on muon updater on tray
discover show available updates

Actual Results:  
We have the list of pending possible package updates but not the changelog of
each updates

Expected Results:  
to be able ti see the changelog upon a click somewhere in the package update
line

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 360528] New: Digikam looks for digikamimageplugins in different directory than they were installed to

[Simon via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360528

Bug ID: 360528
   Summary: Digikam looks for digikamimageplugins in different
directory than they were installed to
   Product: digikam
   Version: 5.0.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: setup
  Assignee: digikam-de...@kde.org
  Reporter: freisi...@gmail.com

I compiled digikam5 from git commit 1b9a889. Digikam shows errors on startup
indicating that it did not find the digikamimageplugins
(digikamimageplugin_transform, ...). These files are installed into
lib/x86_64-linux-gnu/plugins/ while digikam searches for these files per
default (no QT_PLUGIN_PATH set) in lib/x86_64-linux-gnu/qt5/plugins/. Adding
the first path to the env variable QT_PLUGIN_PATH fixes this. Digikam should
install these files into lib/x86_64-linux-gnu/qt5/plugins/.


Reproducible: Always

Steps to Reproduce:
1. compile and install digikam (debug)
2. run digikam, look at stdout/stderr

Actual Results:  
Imageplugins are not found:

Error loading plugin "digikamimageplugin_color" "The shared library was not
found." 
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
digikam.general: ImagePluginLoader: createInstance returned 0 for 
"ImagePlugin_Colour"  ( "digikamimageplugin_color" )  with error:  "The shared
library was not found."
Error loading plugin "digikamimageplugin_decorate" "The shared library was not
found." 
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
digikam.general: ImagePluginLoader: createInstance returned 0 for 
"ImagePlugin_Decorate"  ( "digikamimageplugin_decorate" )  with error:  "The
shared library was not found."
Error loading plugin "digikamimageplugin_enhance" "The shared library was not
found." 
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
digikam.general: ImagePluginLoader: createInstance returned 0 for 
"ImagePlugin_Enhance"  ( "digikamimageplugin_enhance" )  with error:  "The
shared library was not found."
Error loading plugin "digikamimageplugin_fxfilters" "The shared library was not
found." 
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
digikam.general: ImagePluginLoader: createInstance returned 0 for 
"ImagePlugin_FxFilters"  ( "digikamimageplugin_fxfilters" )  with error:  "The
shared library was not found."
Error loading plugin "digikamimageplugin_transform" "The shared library was not
found." 
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin") 
The environment variable QT_PLUGIN_PATH might be not correctly set
digikam.general: ImagePluginLoader: createInstance returned 0 for 
"ImagePlugin_Transform"  ( "digikamimageplugin_transform" )  with error:  "The
shared library was not found."


Expected Results:  
Imageplugins found and loaded.

-- 
You are receiving this mail because:
You are watching all bug changes.

[khelpcenter] [Bug 250956] suggestion for 'What's this?" text

[Marcel Martin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=250956

--- Comment #2 from Marcel Martin  ---
Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kio] [Bug 360488] dolphin with >=kde-frameworks-5.20 crashes when copy+paste file in same directory

[Hrvoje Senjan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360488

Hrvoje Senjan  changed:

   What|Removed |Added

 CC||hrvoje.sen...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 359142] powerdevil ignores "even when external monitor connected" option

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359142

--- Comment #2 from gajdos.mi...@gmail.com ---
I can't see that message in battery monitor.

Observation (with version 5.5.5):
power on with lid closed, external monitor connected
login
switch activities without screen deliberately locking
explicitly lock screen
bad behaviour reintroduced

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.

[Artur O . via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=352050

--- Comment #15 from Artur O.  ---
(In reply to Thomas Lübking from comment #14)
> How fast do you move windows?
> You'll have 250ms to get it across the active area (20px on either side of
> the edge) - otherwise the indicator is still created.

Not so slow, just a regular drag; here is a video I tried to do:
https://www.youtube.com/watch?v=Exa8UwPiP1U=youtu.be 

There is no indicator shown etc but it still feels and shows the stutter when
dragging.

Best Regards

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-frameworkintegration] [Bug 357859] Use Noto as default monospace font

[Elvis Angelaccio via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357859

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||jose...@email.it

--- Comment #1 from Elvis Angelaccio  ---
*** Bug 358532 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-frameworkintegration] [Bug 358532] Use Noto Mono as default fixed-size font

[Elvis Angelaccio via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358532

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kdemail.ne
   ||t
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Elvis Angelaccio  ---


*** This bug has been marked as a duplicate of bug 357859 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 360510] oxygen5-icon-theme error processing archive

[Jonathan Riddell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360510

Jonathan Riddell  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 360510] oxygen5-icon-theme error processing archive

[Jonathan Riddell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360510

Jonathan Riddell  changed:

   What|Removed |Added

 CC||j...@jriddell.org

--- Comment #2 from Jonathan Riddell  ---
oxygen-icon-theme now replaces/breaks old libkdepim5

We don't have a build of kdepim which is compatible with this version of
oxygen-icons yet.

This means it'll be held back if you have kdepim installed.  You can force it
to be installed with  apt install oxygen5-icon-theme  which will uninstall
kdepim

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-solid] [Bug 346153] Plasma Crash During Kparted NTFS Format

[Simon Andric via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346153

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[ksmserver] [Bug 357412] KDE user swap crash

[Wolfgang Bauer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357412

Wolfgang Bauer  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||wba...@tmo.at

--- Comment #5 from Wolfgang Bauer  ---
I'd say this is the same as Bug#357413, actually reported by the same person at
nearly the same time... ;-)

*** This bug has been marked as a duplicate of bug 357413 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[Touchpad-KCM] [Bug 331706] Scrolling is too sensitive

[Igor Poboiko via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=331706

Igor Poboiko  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 CC||igor.pobo...@gmail.com
 Status|RESOLVED|REOPENED

--- Comment #23 from Igor Poboiko  ---
I can confirm I also experience this regression with recent update (Plasma
5.5.95). Setting it to 80 via "synclient VertScrollDelta=80
HorizScrollDelta=80" gives desired result, but it is impossible to set these
values via UI.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-solid] [Bug 346517] Plasmashell crashed after starting gparted

[Simon Andric via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=346517

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360492] KDE Plasma Crashed

[Martin Klapetek via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360492

Martin Klapetek  changed:

   What|Removed |Added

 CC||benk...@gmail.com

--- Comment #1 from Martin Klapetek  ---
*** Bug 359282 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 360527] New: Konsole after manual closing

[Vladyslav via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360527

Bug ID: 360527
   Summary: Konsole after manual closing
   Product: konsole
   Version: 15.12.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: aders1...@gmail.com

Application: konsole (15.12.2)

Qt Version: 5.5.1
Frameworks Version: 5.20.0
Operating System: Linux 4.4.3-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160307) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I have installed updates(libKFStyle-5.20.0 from KDE5 repository for OpenSUSE
Tumbleweed) and when I closed konsole window, message about crash appeared.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f09acf95c58 in raise () at /lib64/libc.so.6
#7  0x7f09acf970aa in abort () at /lib64/libc.so.6
#8  0x7f09acfd46ca in  () at /lib64/libc.so.6
#9  0x7f09acfda016 in malloc_printerr () at /lib64/libc.so.6
#10 0x7f09acfda7fe in _int_free () at /lib64/libc.so.6
#11 0x7f09a964a49c in QMetaCallEvent::~QMetaCallEvent() () at
/usr/lib64/libQt5Core.so.5
#12 0x7f09a964a4e9 in QMetaCallEvent::~QMetaCallEvent() () at
/usr/lib64/libQt5Core.so.5
#13 0x7f09a9622707 in QCoreApplication::removePostedEvents(QObject*, int)
() at /usr/lib64/libQt5Core.so.5
#14 0x7f09a964c62a in QObjectPrivate::~QObjectPrivate() () at
/usr/lib64/libQt5Core.so.5
#15 0x7f09a964c759 in QObjectPrivate::~QObjectPrivate() () at
/usr/lib64/libQt5Core.so.5
#16 0x7f09a9654888 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#17 0x7f099949adc9 in QXcbConnection::~QXcbConnection() () at
/usr/lib64/libQt5XcbQpa.so.5
#18 0x7f099949c766 in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#19 0x7f099949c879 in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#20 0x7f09a9b5a783 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
at /usr/lib64/libQt5Gui.so.5
#21 0x7f09aa2fdc39 in QApplicationPrivate::~QApplicationPrivate() () at
/usr/lib64/libQt5Widgets.so.5
#22 0x7f09a9654888 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#23 0x7f09aa2ff8a9 in QApplication::~QApplication() () at
/usr/lib64/libQt5Widgets.so.5
#24 0x7f09ad32e719 in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#25 0x7f09acf81610 in __libc_start_main () at /lib64/libc.so.6
#26 0x004007f9 in _start ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 360526] New: Gwenview needs a long time to close when viewing a kdeconnect sftp image directly

[Nicolas Frattaroli via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360526

Bug ID: 360526
   Summary: Gwenview needs a long time to close when viewing a
kdeconnect sftp image directly
   Product: gwenview
   Version: Git (add output of "git log -1 --oneline" to
description)
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: kdeb...@fratti.ch
CC: myr...@kde.org

When opening an image which is accessed over kdeconnect's sftp functionality by
either double-clicking the file in Dolphin or opening it directly by passing it
as a parameter to gwenview on the command line, gwenview will need a long time
to close when the X on the window is hit. Long enough to trigger the KDE hung
application dialogue.

Surprisingly, if one navigates to said folder from within gwenview and opens an
image, gwenview shuts down just fine.

It seems that gwenview might be waiting on some redundant filesystem operation
to complete when closing.

Version information:
gwenview:
$ git log -1 --oneline
c8edede SVN_SILENT made messages (after extraction)
kdeconnect:
kdeconnect 0.9.g-1

Reproducible: Always

Steps to Reproduce:
1. Install kdeconnect on an Android phone and on your desktop.
2. Enable "Remote filesystem browser"
3. Browse the remote filesystem of your phone with dolphin
4. From within dolphin, open an image on your phone in gwenview
5. Click on the close window button.

Actual Results:  
gwenview needs around 20 seconds to close the window

Expected Results:  
gwenview closes instantly

This seems to not happen with things mounted over sshfs.

I have not tried reproducing with SFTP mounts other than kdeconnect's.
Both devices are connected to wifi.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation in Polish

[allan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360129

allan  changed:

   What|Removed |Added

 CC|agande...@gmail.com |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation in Polish

[allan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360129

allan  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #15 from allan  ---
(In reply to NSLW from comment #14)
> (In reply to allan from comment #13)
> > What I'm not sure about just now is whether, once the user has chosen to
> > make a substitution, that new term is added to the resource file
> > automatically.  It's a few ears since I wrote that code.
> 
> That's worth checking. That might be a second bug.

I'll check.
> 
> > I know no Polish financial terms.  If the Buy list contains a correct Polish
> > term, then that I presume was added by the translator.  A possible
> > explanation is that at line 161 (in my version) of investprocessing.cpp the
> > following appears - "m_buyList += i18nc("verb", "buy");  // 
> > some basic entries in case rc file missing".  It may be that that was when
> > the translation for Buy was added.  However, the next line is similar for
> > the Sell operation, and that was not translated apparently.
> 
> All terms are and were translated.

In the rc file snippet you attached, only Buy and Reinvdiv have content.
> 
> > I would suggest that you include both noun and verb versions for Sell in
> > your resource file.
> 
> I already have them and it works for me.
> 
> > > As it is now was also misleading to me, to today although I'm an fresh
> > > KMyMoney user :) and translator, so maybe another suggestion will sound
> > > better to an layman:
> > > "Type of operation as in financial statement"
> > > 
> > That does sound more understandable, although it would have to be added to
> > every transaction type.
> 
> I think you're right, is there any problem for it to be added to every
> transaction type?

Only in terms of bloat.  However, if I create a single string, I can refer to
that instead of using the full version.

> 
> > > > So, apart from the fee query, are you now in business?
> > > 
> > > After manually editing csvimporterrc file, fee is imported just right for
> > > all operations. What do you mean by me being in business?
> > 
> > Apologies for that.  I'm extremely impressed by the general level of
> > knowledge of English shown by the users, and developers, and I forget myself
> > sometimes and lapse into the vernacular.  "being in business" is used to
> > indicate that a problem has been solved and normal service may be resumed. 
> > I hope it didn't cause offence.
> 
> No, none at all. You've suggested me a workaround and it worked for me as
> expected.
> 
> > So far as your suggested patch is concerned, I'm not sure of its purpose. 
> > The Subject is "[PATCH] Read operation's type explicitly as QStringList",
> > and in it you add a number of QStringList definitions, which are already
> > included in investprocessing.h, c. line 164.
> 
> I think that after my patch, every variable is defined anew locally, which I
> think is not clean way to do this and doesn't remove the source of the
> problem, but it works flawlessly.  After the patch my csvimporterrc is
> filled out automatically with all the data whereas before the patch only
> BuyParam and ReinvdivParam were filled out.
> I tell you what, I'm going to see into the problem once again soon and I
> will try to find its source, cause I really want it to see it fixed.
> 
> > Oh, and just as a post script, I've added "in Polish" to the bug heading, as
> > the import operation is otherwise as expected.
> 
> I would say "in non-English"

Well, we don't know of any other problem, and it seems to depend on
translation, so I think I'll stick with the current version.  It can always be
edited if needed in the future.

> 
> Łukasz

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 331137] git->Show Differences closes file

[Francis Herne via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=331137

Francis Herne  changed:

   What|Removed |Added

 CC||francis.he...@yahoo.co.uk

--- Comment #4 from Francis Herne  ---
This doesn't happen (AFAICT) with KDevelop 4.90.91 or current 5.0 branch. The
tab remains open when leaving the diff view.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360443] Kwin freezes -- mouse moves but nothing else works

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360443

--- Comment #12 from Thomas Lübking  ---
(In reply to Raman Gupta from comment #11)

> So to summarize, the desired setting should be
> "OpenGL 2.0" with "GLX" for maximum compatibility with QT.

Bingo.
(Though I consider crossing of EGL & GLX far worse reg. sync races than GL2 &
GL3)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360466] When a PyQt5 application uses move() to set the position of the main window KDE offsets the window position

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360466

Thomas Lübking  changed:

   What|Removed |Added

  Component|general |core

--- Comment #1 from Thomas Lübking  ---
"Depends" - you can expect "x,y" to be the final position of *your* window, not
the framed window.
However, I've no idea what PyQt is doing behind the scenes, can you attach a
simple testcase (to inspect what's going on)?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360500] Unable to enter the same value in the No. field for more than 1 transaction.

[allan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360500

allan  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
   Version Fixed In||4.8
  Latest Commit||dc5109988fbf1f732525e6a6ec1
   ||93903b472b632

--- Comment #2 from allan  ---
I think the intention in clearing the cell contents may have been to assist the
user to enter the required value, perhaps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360129] CSV Importer doesn't recognize sell operation in Polish

[NSLW via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360129

--- Comment #14 from NSLW  ---
(In reply to allan from comment #13)
> What I'm not sure about just now is whether, once the user has chosen to
> make a substitution, that new term is added to the resource file
> automatically.  It's a few ears since I wrote that code.

That's worth checking. That might be a second bug.

> I know no Polish financial terms.  If the Buy list contains a correct Polish
> term, then that I presume was added by the translator.  A possible
> explanation is that at line 161 (in my version) of investprocessing.cpp the
> following appears - "m_buyList += i18nc("verb", "buy");  // 
> some basic entries in case rc file missing".  It may be that that was when
> the translation for Buy was added.  However, the next line is similar for
> the Sell operation, and that was not translated apparently.

All terms are and were translated.

> I would suggest that you include both noun and verb versions for Sell in
> your resource file.

I already have them and it works for me.

> > As it is now was also misleading to me, to today although I'm an fresh
> > KMyMoney user :) and translator, so maybe another suggestion will sound
> > better to an layman:
> > "Type of operation as in financial statement"
> > 
> That does sound more understandable, although it would have to be added to
> every transaction type.

I think you're right, is there any problem for it to be added to every
transaction type?

> > > So, apart from the fee query, are you now in business?
> > 
> > After manually editing csvimporterrc file, fee is imported just right for
> > all operations. What do you mean by me being in business?
> 
> Apologies for that.  I'm extremely impressed by the general level of
> knowledge of English shown by the users, and developers, and I forget myself
> sometimes and lapse into the vernacular.  "being in business" is used to
> indicate that a problem has been solved and normal service may be resumed. 
> I hope it didn't cause offence.

No, none at all. You've suggested me a workaround and it worked for me as
expected.

> So far as your suggested patch is concerned, I'm not sure of its purpose. 
> The Subject is "[PATCH] Read operation's type explicitly as QStringList",
> and in it you add a number of QStringList definitions, which are already
> included in investprocessing.h, c. line 164.

I think that after my patch, every variable is defined anew locally, which I
think is not clean way to do this and doesn't remove the source of the problem,
but it works flawlessly.  After the patch my csvimporterrc is filled out
automatically with all the data whereas before the patch only BuyParam and
ReinvdivParam were filled out.
I tell you what, I'm going to see into the problem once again soon and I will
try to find its source, cause I really want it to see it fixed.

> Oh, and just as a post script, I've added "in Polish" to the bug heading, as
> the import operation is otherwise as expected.

I would say "in non-English"

Łukasz

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360391] Auto-hiding panel does not return

[Martin Klapetek via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360391

Martin Klapetek  changed:

   What|Removed |Added

 CC||mklape...@kde.org

--- Comment #3 from Martin Klapetek  ---
Also what if you try approaching the screen edge with various speeds?
Is there any velocity that would reliably show the panel?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360443] Kwin freezes -- mouse moves but nothing else works

[Raman Gupta via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360443

--- Comment #11 from Raman Gupta  ---
(In reply to Martin Gräßlin from comment #9)
> yes please try whether it still happens with GLX.

So far it hasn't happened again even with EGL... too bad (sort of) this wasn't
easier to reproduce :-(

> Also give a try to use an
> OpenGL 2 (compat) instead of a core profile. Similar argument: Qt doesn't
> use a core context so it might be better to also use a compat context in
> KWin.

Ok, this means changing the "Rendering backend" in the compositor settings to
"OpenGL 2.0" right? So to summarize, the desired setting should be "OpenGL 2.0"
with "GLX" for maximum compatibility with QT.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution

[Martin Klapetek via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360478

Martin Klapetek  changed:

   What|Removed |Added

 CC||mklape...@kde.org

--- Comment #1 from Martin Klapetek  ---
Thanks for the report

> plasmoids should not be automatically rearranged when applications
temporarily change the resolution (the user doesn't explicitly change it
in the display settings)

But we don't know that. All goes through various levels and roundtrips
to the display server, in the end Plasma receives only "screen resolution
changed". Plasma cannot know if that is a legitimate request or just
a temporary change.

I'll leave this open for others to comment, but I don't think this is (easily)
fixable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney4] [Bug 360500] Unable to enter the same value in the No. field for more than 1 transaction.

[allan via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360500

--- Comment #1 from allan  ---
Created attachment 97898
  --> https://bugs.kde.org/attachment.cgi?id=97898=edit
Fix for bug 306500

This is a trivial patch, and with developer time being scarce, I see no point
in going via reviewboard.
Unless I hear to the contrary, I propose to push it in about a week, in order
to, hopefully, make it into rev 4.8.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360466] When a PyQt5 application uses move() to set the position of the main window KDE offsets the window position

[Martin Klapetek via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360466

Martin Klapetek  changed:

   What|Removed |Added

   Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org
   Target Milestone|1.0 |---
 CC||mklape...@kde.org
  Component|general |general
Product|plasmashell |kwin

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-plasma] [Bug 360457] WindowThumnail renders with QSGTexture::Nearest on at least intel chips

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360457

Thomas Lübking  changed:

   What|Removed |Added

 CC||mgraess...@kde.org
Summary|Thumbnail Scaling with  |WindowThumnail renders with
   |"Accurate" filter not work  |QSGTexture::Nearest on at
   ||least intel chips

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 359282] Plasma Crash on search

[Martin Klapetek via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359282

Martin Klapetek  changed:

   What|Removed |Added

 CC||mklape...@kde.org
 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Martin Klapetek  ---
I'll close this as duplicate of 360492, simply because the other
bug has better backtrace.

*** This bug has been marked as a duplicate of bug 360492 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360443] Kwin freezes -- mouse moves but nothing else works

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360443

--- Comment #10 from Thomas Lübking  ---
(In reply to Raman Gupta from comment #8)

> Two reasons: 1) Kwin/plasma starts doing weird things when I start turning
> monitors on and off and as I recall, windows don't always go back to where
> they were when everything is on again



That one might be resolved with Qt 5.6

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-plasma] [Bug 357895] Regression: KDE Plasma with KF 5.18 crash, if mouse repeatedly hovers over TaskManager

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357895

--- Comment #50 from Martin Gräßlin  ---
*** Bug 360496 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.