[kwin] [Bug 380800] New: High CPU usage with 'Destkop Effects' enabled

[Steven Haigh]

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

Bug ID: 380800
   Summary: High CPU usage with 'Destkop Effects' enabled
   Product: kwin
   Version: 5.9.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: net...@crc.id.au
  Target Milestone: ---

This output of 'top' is grabbed from just moving the mouse around over the top
of the system settings dialog.

top - 12:28:24 up 2 min,  2 users,  load average: 0.67, 0.28, 0.10
Tasks: 287 total,   2 running, 284 sleeping,   0 stopped,   1 zombie
%Cpu(s):  9.7 us,  3.0 sy,  0.0 ni, 87.0 id,  0.0 wa,  0.2 hi,  0.2 si,  0.0 st
KiB Mem : 10228404 total,  8320700 free,  1099032 used,   808672 buff/cache
KiB Swap:  5181436 total,  5181436 free,0 used.  8807936 avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
 1861 netwiz20   0  988516 154128  92760 R  49.2  1.5   0:16.39
systemsettings5
  988 root  20   0  291872  70384  44240 S  23.3  0.7   0:15.02 Xorg
 1318 netwiz20   0 3365896 141000  87728 S  10.0  1.4   0:15.30 kwin_x11
 1333 netwiz20   0 4571460 420064 159660 S   4.3  4.1   0:12.64 plasmashell
 1024 root -51   0   0  0  0 S   1.0  0.0   0:00.64
irq/40-nvidia
8 root  20   0   0  0  0 S   0.3  0.0   0:00.05 rcu_sched
  492 root  20   0   0  0  0 S   0.3  0.0   0:00.05
btrfs-transacti
  887 root  20   0  789412  18016  15060 S   0.3  0.2   0:00.19
NetworkManager
 1885 netwiz20   0  756992  68836  58156 S   0.3  0.7   0:00.49 konsole

Disabling the desktop effects via "Alt-Shift-F12" will cause this behaviour to
stop immediately.

# rpm -qa | grep kwin | sort
kf5-kwindowsystem-5.34.0-1.fc26.x86_64
kwin-5.9.5-2.fc26.x86_64
kwin-common-5.9.5-2.fc26.x86_64
kwin-libs-5.9.5-2.fc26.x86_64

# rpm -qa | grep nvidia | sort
akmod-nvidia-381.22-2.fc26.x86_64
kmod-nvidia-4.11.3-300.fc26.x86_64-381.22-2.fc26.x86_64
nvidia-driver-381.22-6.fc26.x86_64
nvidia-driver-cuda-libs-381.22-6.fc26.x86_64
nvidia-driver-libs-381.22-6.fc26.x86_64
nvidia-libXNVCtrl-381.22-1.fc26.x86_64
nvidia-settings-381.22-1.fc26.x86_64

Am more than happy to do more debug as required.

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

[khelpcenter] [Bug 380798] There is something wrong with the paintbucket feature

[bugzilla_noreply]

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

--- Comment #1 from leonbelmont...@gmail.com ---
https://drive.google.com/file/d/0BzsXaMQKj7OfbHhMNHRobDUzdEU/view?usp=sharing
Here is the link since it exceeded file size

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

[kscreenlocker] [Bug 380526] Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)

[Michael Palimaka]

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

Michael Palimaka  changed:

   What|Removed |Added

 CC||kensing...@gentoo.org

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

[konsole] [Bug 380799] New: Konsole remembers window size across launches, but not position

[Nate Graham]

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

Bug ID: 380799
   Summary: Konsole remembers window size across launches, but not
position
   Product: konsole
   Version: 17.04.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Linux distro: openSUSE Tumbleweed
Plasma version: 5.10
Konsole version: 17.04.1

Steps to reproduce:
1. Open Konsole
2. Move and resize the window
3. Close Konsole
4. Open Konsole again


Expected results:
Upon being re-opened, Konsole should create a window the same size as the
previously closed one, and in the same position.


Actual results:
The window size is remembered, but not the location; the new window always
spawns at 0,0.


Additional information:
I know that I can set a special rule to force it to remember a certain location
(and I do), but this shouldn't be necessary; the position should be remembered
by default, automatically.

Also, I read in https://bugs.kde.org/show_bug.cgi?id=100962 Apparently it is
the intended behavior that KDE applications remember their size but not
position across launches. That was written 12 years ago, so maybe that's no
longer the policy? If it, would like to propose a change. Having both size and
position be remembered is the way most users expect things to work.

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

[konsole] [Bug 380799] Konsole remembers window size across launches, but not position

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[khelpcenter] [Bug 380798] New: There is something wrong with the paintbucket feature

[bugzilla_noreply]

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

Bug ID: 380798
   Summary: There is something wrong with the paintbucket feature
   Product: khelpcenter
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kde-doc-engl...@kde.org
  Reporter: leonbelmont...@gmail.com
  Target Milestone: ---

Every time when I isolate layer 5 to paintbucket the left part of the left eye
(from the viewers point of view) white it turns the whole frog the same color
even when I close all the corners. It seems to be some kind of bug.

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

[plasma-nm] [Bug 380797] New: Cannot set MTU of wired connection

[Neil Rickert]

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

Bug ID: 380797
   Summary: Cannot set  MTU of wired connection
   Product: plasma-nm
   Version: 5.10.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: nwr10cst-os...@yahoo.com
  Target Milestone: ---

I attempted to set MTU for wired connection to 1472 (recommended for IPv6 via
6rd).

Note: this is also reported as Bug 1042542 for opensuse
(bugzilla.opensuse.org).

In the client, I made the change, then clicked "Okay" (or "Apply").  I expected
a connection definition file (probably "Wired connection 1") to be save in
"/etc/NetworkManager/system-connections" with the changed setting.  Instead,
nothing happened.  I rebooted, and the MTU was still 1500.

I also have Gnome desktop installed.  I tried using the Gnome NetworkManager
client, and changing the MTU there worked as expected (while logged into
Gnome).

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

[kscreenlocker] [Bug 380526] Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)

[bugzilla_noreply]

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

fl...@mailoo.org changed:

   What|Removed |Added

 CC||fl...@mailoo.org

--- Comment #3 from fl...@mailoo.org ---
I can confirm this. However, I'm using custom shortcuts (e.g. Meta+S for pause)
and they are not working on the lock screen (can't test Media Control keys as I
don't have them).

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

[kscreenlocker] [Bug 380526] Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
Not much of a workaround, but restarting X restores proper control of the media
playback keys.

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

[kdeconnect] [Bug 380527] New: Mouse input jitters after waking device from sleep

[Maxim Therrien]

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

Bug ID: 380527
   Summary: Mouse input jitters after waking device from sleep
   Product: kdeconnect
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: acersp...@gmail.com
  Target Milestone: ---

kdeconnect v1.6.4
KDE Neon 5.10.0

On my Huawei Nova Plus, locking the phone and unlocking it (via the fingerprint
sensor, if it matters) while in the kdeconnect app showing the touchpad, trying
to use the touchpad will result in heavy mouse jitter until the app is
restarted.

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

[kscreenlocker] [Bug 380526] Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
Once this problem has manifested, if you lock the screen again, the media
playback keys work from the lock screen itself! So it seems like whatever is
grabbing control of the media keys for the lock screen isn't giving up that
control once the lock screen goes away.

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

[krita] [Bug 380418] GUI is out of alignment with the main Krita window once a document is opened

[Steve]

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

--- Comment #6 from Steve  ---
I have created a new account and Krita still has the same problem for the new
user.

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

[kscreenlocker] [Bug 380526] Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kscreenlocker] [Bug 380526] New: Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)

[Nate Graham]

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

Bug ID: 380526
   Summary: Media playback buttons no longer work after locking
and unlocking the screen (Regression in 5.10)
   Product: kscreenlocker
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: pointedst...@zoho.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

Linux distro: openSUSE Tumbleweed
Plasma version 5.10

Just updated to KDE Plasma 5.10, from 5.9.5. Now, activating the screen locker
disables my media keys. This is a significant regression, and probably related
to the work done to make media playback controls appear on the lock screen.

Steps to reproduce
1. Open any MPRIS-compatible music player (tried Amarok and Lollypop)
2. Start playing a song
3. Use your keyboard's built-in media playback keys and verify that they work
4. Lock the screen using any method (suspend, manual locking- makes no
difference)
5. Unlock the screen
6. Use your keyboard's media keys again

Expected results
The media keys should still work.

Actual results:
The Media keys no longer work.

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

[kwin] [Bug 380524] Downloaded window decoration are broken with Nvidia drivers

[Jesse]

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

Jesse  changed:

   What|Removed |Added

  Component|aurorae |activities

--- Comment #2 from Jesse  ---
I tried building kwin previous to that commit Rik mentioned, and indeed, it
brings back the decoration and fixes the glitched listing in system settings.

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

[plasma-pa] [Bug 380525] sox synth can not play white noise

[AppAraat]

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

--- Comment #1 from AppAraat <4xr6ah+4wznsmksoi...@sharklasers.com> ---
I made a thread on Reddit:
https://www.reddit.com/r/kde/comments/6735s4/neon_ue_audio_issues_cant_connect_to_pulseaudio/

Therein, I've documented the output of the following commands:


└─$ speaker-test

speaker-test 1.1.0

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
shm_open() failed: No such file or directory
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Protocol
error

Playback open error: -111,Connection refused

---

└─$  pactl list 
shm_open() failed: No such file or directory
Connection failure: Protocol error

---

So this sounds like it's a much bigger issue than sox not being able to play
white noise.

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

[plasma-pa] [Bug 380525] New: sox synth can not play white noise

[AppAraat]

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

Bug ID: 380525
   Summary: sox synth can not play white noise
   Product: plasma-pa
   Version: 5.10.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: 4xr6ah+4wznsmksoi...@sharklasers.com
CC: plasma-b...@kde.org
  Target Milestone: ---

# Overview:
play -n synth whitenoise gain -6
This command outputs white noise. Requires sox to be installed and it might be
loud (provided it works as intended). I use this command for various purposes,
including testing of audio output devices and further signal path.

# Steps to reproduce:
1) Download and install the package called sox
2) In the terminal, run "play -n synth whitenoise gain -6" (without the quotes)


# Actual results:

Terminal output:

shm_open() failed: No such file or directory
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Protocol
error

play FAIL formats: can't open output file `default': snd_pcm_open error:
Connection refused

Audio output: Nothing.


# Expected results:

Terminal output:

  Encoding: n/a   
  Channels: 1 @ 32-bit   
 Samplerate: 48000Hz  
Replaygain: off 
 Duration: unknown  

In:0.00% 00:00:02.05 [00:00:00.00] Out:98.3k [ =|= ]   Clip:0   

Audio output: White noise.


# Build Date & Platform:
I first experienced this around 2017.04.23, not sure what date it was but I
believe it was still on Plasma 5.9.4

# Additional information:

Hardware: Lenovo X230 with i5-3360m CPU.

└─$  sudo lspci -vvv -s '00:1b.0'
[sudo] password for me: 
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family
High Definition Audio Controller (rev 04)
Subsystem: Lenovo 7 Series/C210 Series Chipset Family High Definition
Audio Controller
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

[kwin] [Bug 380524] Downloaded window decoration are broken with Nvidia drivers

[Rik Mills]

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

Rik Mills  changed:

   What|Removed |Added

Version|unspecified |5.10.0

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

[kwin] [Bug 380524] Downloaded window decoration are broken with Nvidia drivers

[Rik Mills]

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

Rik Mills  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||rikmi...@kubuntu.org

--- Comment #1 from Rik Mills  ---
Had the same issue in Kubuntu 5.10 packages with a Nvidia box.

Reverting:


https://cgit.kde.org/kwin.git/commit/?h=Plasma/5.10=bfbcd0197181657d5dfac953ad77dd3de2ee7e92
 

seems to at least return the decorations to a working state (I don't use hidpi
on that machine).

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

[kwin] [Bug 380524] New: Downloaded window decoration are broken with Nvidia drivers

[Jesse]

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

Bug ID: 380524
   Summary: Downloaded window decoration are broken with Nvidia
drivers
   Product: kwin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: aurorae
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jesse...@gmail.com
  Target Milestone: ---

Created attachment 105870
  --> https://bugs.kde.org/attachment.cgi?id=105870=edit
downloaded themes are listed like that

Custom window decorations are broken. Only the default ones -- Plasma, Plastik
and Oxygen -- work. The downloaded themes are listed with glitches in system
settings (see attachment). And, when applying one of the downloaded theme, the
window decoration disappears. This issue seems to happen only with Nvidia cards
with proprietary drivers (not sure if it works with nouveau).

How to reproduce:
1. Install Nvidia proprietary drivers
2. Open system settings and download a custom window decoration theme (like Arc
KDE, for example)
3. The downloaded theme is listed with glitches (without the window buttons, or
a black rectangle, etc, depending on the theme)
4. Try applying the downloaded theme and the window decoration disappears


I tried looking at the kwin output in the terminal when switching to a broken
theme, but I don't think it's relevant:
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/jesse/.local/share",
"/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-effect.desktop, tried ("/home/jesse/.local/share",
"/usr/local/share", "/usr/share")

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

[krunner] [Bug 380523] New: Krunner se cerró cuando intenté ejecutar Kate

[Víctor]

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

Bug ID: 380523
   Summary: Krunner se cerró cuando intenté ejecutar Kate
   Product: krunner
   Version: 5.10.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: mrvi...@gmail.com
  Target Milestone: ---

Application: krunner (5.10.0)

Qt Version: 5.8.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Suele pasar bastante a menudo. Cuando acabo de cerrar una aplicación y acto
seguido busco otra se detiene. Tampoco es demasiado molesto, pero es algo que
hay que arreglar ;)

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd79134a7c0 (LWP 1633))]

Thread 15 (Thread 0x7fd73d7fa700 (LWP 2171)):
#0  0x7fd78a8fe39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd78d23821b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd761ed71d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fd761edb9d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fd761ed6263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fd761ed9249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fd78d236e9c in  () at /usr/lib/libQt5Core.so.5
#7  0x7fd78a8f8297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fd78cb4925f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7fd73dffb700 (LWP 2170)):
#0  0x7fd78a8fe39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd78d23821b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd761ed71d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fd761edb9d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fd761ed6263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fd761ed9249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fd78d236e9c in  () at /usr/lib/libQt5Core.so.5
#7  0x7fd78a8f8297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fd78cb4925f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fd73e7fc700 (LWP 2169)):
#0  0x7fd78a8fe39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd78d23821b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd761ed71d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fd761edb9d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fd761ed6263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fd761ed9249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fd78d236e9c in  () at /usr/lib/libQt5Core.so.5
#7  0x7fd78a8f8297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fd78cb4925f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fd73effd700 (LWP 2168)):
#0  0x7fd78a8fe39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd78d23821b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd761ed71d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fd761edb9d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fd761ed6263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fd761ed9249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fd78d236e9c in  () at /usr/lib/libQt5Core.so.5
#7  0x7fd78a8f8297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fd78cb4925f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fd73f7fe700 (LWP 2167)):
#0  0x7fd78a8fe39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd78d23821b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd761ed71d0 in

[kdevelop] [Bug 380516] Debuging - Registers

[Baron Leonardo]

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

--- Comment #2 from Baron Leonardo  ---
yes, all the registers

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

[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities

[bugzilla_noreply]

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

ludo...@gmx.com changed:

   What|Removed |Added

 CC||ludo...@gmx.com

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

[ksmserver] [Bug 373274] ksmserver eats memory and does not lock screen

[bugzilla_noreply]

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

ludo...@gmx.com changed:

   What|Removed |Added

 CC||ludo...@gmx.com

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

[kwin] [Bug 380440] [since Plasma 5.10.0] "Switch desktop on edge" when moving windows not working

[Rik Mills]

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

Rik Mills  changed:

   What|Removed |Added

 CC||rikmi...@kubuntu.org
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Rik Mills  ---
I see the same issue on both Kubuntu and KDE Neon 5.10 packages.

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

[digikam] [Bug 380521] Show only assigned leafmost tags of hierarchical tags

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|Thumbnails  |Tags

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

[digikam] [Bug 380512] digikam crashes when trying to geotag a picture

[bugzilla_noreply]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Yves,

Report this problem to your Linux team. Exiv2 0.25 must be updated 0.26.

Gilles Caulier

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

[neon] [Bug 380509] lock screen doesn't accept password, timeout to suspend doesn't suspend

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 380522] New: Plasma crasched by systemstart

[Peter G]

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

Bug ID: 380522
   Summary: Plasma crasched by systemstart
   Product: plasmashell
   Version: 5.5.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: partis...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.1.39-56-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: i have only startet the
computer and the only what i see was the error box plasma is crasht in 6
inentical threads.
This error comes in the last 3 times when i probing the computer starting.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3c8fb4f7c0 (LWP 2018))]

Thread 7 (Thread 0x7f3bc700 (LWP 2037)):
#0  0x7f3c8904cbfd in poll () at /lib64/libc.so.6
#1  0x7f3c85729e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3c85729f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3c89979d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3c89920d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3c8974261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3c8d5f2282 in  () at /usr/lib64/libQt5Quick.so.5
#7  0x7f3c8974732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f3c5bbd7700 (LWP 2034)):
#0  0x7f3c8885a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3c8f22586b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f3c8f225899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f3c615c4700 (LWP 2033)):
#0  0x7f3c89048ccd in read () at /lib64/libc.so.6
#1  0x7f3c811d4073 in  () at /usr/lib64/tls/libnvidia-tls.so.375.39
#2  0x7f3c8576ab60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f3c8572 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f3c85729df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f3c85729f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f3c89979d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f3c89920d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f3c8974261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f3c8ca56e18 in  () at /usr/lib64/libQt5Qml.so.5
#10 0x7f3c8974732f in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f3c62d6f700 (LWP 2032)):
#0  0x7f3c8904cbfd in poll () at /lib64/libc.so.6
#1  0x7f3c85729e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3c85729f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3c89979d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3c89920d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3c8974261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3c8ca56e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f3c8974732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f3c6e8cb700 (LWP 2031)):
#0  0x7f3c8904cbfd in poll () at /lib64/libc.so.6
#1  0x7f3c85729e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f3c85729f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f3c89979d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f3c89920d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f3c8974261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f3c8ca56e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f3c8974732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f3c888560a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3c8905502d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f3c78981700 (LWP 2022)):
#0  0x7f3c8904cbfd in poll () at /lib64/libc.so.6
#1  0x7f3c8dfa0422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f3c8dfa200f in xcb_wait_for_event () at 

[kio] [Bug 379093] Spectacle logs user out of the system when user clicks Export image > Share > Save as

[David Faure]

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

David Faure  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kio
   ||/aafa5b7bbc89301c478f8089d6
   ||738a4c5896bcac

--- Comment #6 from David Faure  ---
Git commit aafa5b7bbc89301c478f8089d6738a4c5896bcac by David Faure.
Committed on 03/06/2017 at 20:17.
Pushed by dfaure into branch 'master'.

Use "data" as filename when copying data urls

M  +13   -0autotests/jobtest.cpp
M  +1-0autotests/jobtest.h
M  +2-1src/core/copyjob.cpp

https://commits.kde.org/kio/aafa5b7bbc89301c478f8089d6738a4c5896bcac

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

[digikam] [Bug 380521] Show only assigned leafmost tags of hierarchical tags

[Simon]

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

Simon  changed:

   What|Removed |Added

 CC||freisi...@gmail.com

--- Comment #1 from Simon  ---
You can set parents, children or both automatically. Right click in the tags
area, choose "Toggle Auto".

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

[digikam] [Bug 380521] New: Show only assigned leafmost tags of hierarchical tags

[Jaakko Luttinen]

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

Bug ID: 380521
   Summary: Show only assigned leafmost tags of hierarchical tags
   Product: digikam
   Version: 5.4.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Thumbnails
  Assignee: digikam-de...@kde.org
  Reporter: jaakko.lutti...@iki.fi
  Target Milestone: ---

I really like hierarchical tags. Let's assume I have the following hierarchy:

- Parent
  - Child1
  - Child2

If I tag an image with Child2, I would expect that Parent tag is implicitly
given too. I suppose that's optional in digikam, so be it. But in Thumbnails
view, I wouldn't want to see any parent tags of a chosen child tag. So in my
example, the thumbnail view would show only Child2 tag, but not Parent tag
(even though it's assigned too). Because I'm using the hierarchies a lot and
sometimes rather deep, I get a huge amount of tag labels in each image although
I have only chosen perhaps 1-3 leaf tags. This is really annoying.

I don't quite understand the use case for assigning a child tag but not its
parents. But I guess some people like to do that and they probably want then to
see all the assigned tags. I would rather assign the parent tags implicitly but
only show the assigned leaf tags (or assigned tags which have no assigned child
tags). So I would hope there at least would be an option for Thumbnails view to
hide those tags that have child tags that have been assigned too.

I hope I was able to describe this clearly. Does this make sense to you?

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

[kdevelop] [Bug 380516] Debuging - Registers

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #1 from Sven Brauch  ---
Do they show up in e.g. "info all-registers" in gdb?

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

[partitionmanager] [Bug 380520] Worng swap partition used space

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

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

--- Comment #1 from Andrius Štikonas  ---
Update to newer version. 3.0.x is available  in Kubuntu.

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

[partitionmanager] [Bug 380520] New: Worng swap partition used space

[Avi Sand]

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

Bug ID: 380520
   Summary: Worng swap partition used space
   Product: partitionmanager
   Version: 1.2.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: avis...@gmail.com
  Target Milestone: ---

Created attachment 105869
  --> https://bugs.kde.org/attachment.cgi?id=105869=edit
Screen shoot

The swap partition used space is taken from the ext4 one.

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

[QtCurve] [Bug 380519] Building without KDE integration fails.

[Yichao Yu]

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

Yichao Yu  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/qtc
   ||urve/392e1db034708efb5921ac
   ||4577588f959f99fb27
 Resolution|--- |FIXED

--- Comment #1 from Yichao Yu  ---
Git commit 392e1db034708efb5921ac4577588f959f99fb27 by Yichao Yu.
Committed on 03/06/2017 at 19:08.
Pushed by yuyichao into branch 'master'.

Add missing  include when KDE integration is disabled.

M  +1-0qt5/style/qtcurve.cpp

https://commits.kde.org/qtcurve/392e1db034708efb5921ac4577588f959f99fb27

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

[QtCurve] [Bug 380519] New: Building without KDE integration fails.

[Antonio Rojas]

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

Bug ID: 380519
   Summary: Building without KDE integration fails.
   Product: QtCurve
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: qt5
  Assignee: yyc1...@gmail.com
  Reporter: aro...@archlinux.org
CC: h...@kde.org
  Target Milestone: ---

Building version 1.9 for Qt5 with QTC_QT5_ENABLE_KDE=false fails:

/build/qtcurve/src/qtcurve-1.9.0/qt5/style/qtcurve.cpp: In member function
‘void QtCurve::Style::disconnectDBus()’:
/build/qtcurve/src/qtcurve-1.9.0/qt5/style/qtcurve.cpp:706:18: error: invalid
use of incomplete type ‘class QDebug’
 qWarning() << Q_FUNC_INFO << this << "Disconnecting from" <<
bus.name() << "/" << bus.baseService();
  ^

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

[kdepim] [Bug 380487] messagelib master branch fails to build

[Sandro Knauß]

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

Sandro Knauß  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/mes
   ||sagelib/bbf8602af9045d1bb52
   ||ac4f0babc52a276c48560
   Version Fixed In||5.5.45

--- Comment #2 from Sandro Knauß  ---
Git commit bbf8602af9045d1bb52ac4f0babc52a276c48560 by Sandro Knauß.
Committed on 03/06/2017 at 18:59.
Pushed by knauss into branch 'master'.

Fix 380487 - messagelib master branch fails to build

inline not in private header
FIXED-IN: 5.5.45

M  +1-1messageviewer/src/messagepartthemes/default/defaultrenderer_p.h

https://commits.kde.org/messagelib/bbf8602af9045d1bb52ac4f0babc52a276c48560

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

[digikam] [Bug 380512] digikam crashes when trying to geotag a picture

[Simon]

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

Simon  changed:

   What|Removed |Added

 CC||freisi...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.6.0

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

[digikam] [Bug 380512] digikam crashes when trying to geotag a picture

[Yves Gänssinger]

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

--- Comment #3 from Yves Gänssinger  
---
You were right about my Exiv2 version. 

The digiKam 5.6.0 pre release Linux AppImage bundle does not crash in the same
circumstances. 

So this issue seems to be resolved already.

Thanks for the quick response.

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

[digikam] [Bug 380507] Menu items missing

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.6.0
 Resolution|--- |FIXED

--- Comment #1 from caulier.gil...@gmail.com ---
Definitively, this problem is solved since digiKam 5.x. The problem is due to
use a plugin architecture for image editor which can be lost with some
incompatible environnement variables under Linux.

Please try 5.6.0 pre release Linux AppImage bundle. The plugin architecture in
Image Editor is fully removed. All tools are included as well in Image editor.

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Note : to run showfoto with AppImage, just pass the right CLI arguments to the
bundle :

$ ./digikam-5.6.0-01-x86-64.appimage help
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
digiKam AppImage bundle CLI options:
 without option : run digiKam.
  : run Showfoto instead digiKam.
 : run digiKam into GDB.
   : run Showfoto into GDB.
  : show this help.


Gilles Caulier

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

[konsole] [Bug 380518] New: Konsole does not create profiles by default

[Andrew Brouwers]

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

Bug ID: 380518
   Summary: Konsole does not create profiles by default
   Product: konsole
   Version: 17.04.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: abrouw...@gmail.com
  Target Milestone: ---

On a default arch linux install (konsole 17.04.1), I noticed some really odd
behavior around profiles.  First, there weren't any populated profiles by
default.  I had to create one manually; upon making some changes, the list of
profiles was still only my newly created default (after closing and re-opening
konsole several times).  However, after making deeper changes (to fonts, hiding
scroll bar), konsole create 4 new profiles, and had changed the default to
Profile 4.  As a result, most of my settings were made to this profile, even
though I had my default profile selected prior to making changes.

In summary, something odd is going on; there appears to be no default profile
upon first use, and some setting change appears to cause them to get created,
and blindly change over to using it.  

This is re-creatable with a new user.

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

[digikam] [Bug 380512] digikam crashes when trying to geotag a picture

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|general |Metadata-Engine
 CC||caulier.gil...@gmail.com

--- Comment #2 from caulier.gil...@gmail.com ---
It crash in Exiv2 shared library.

I suspect that you use Exiv2 0.25. New Exiv2 0.26 released few week ago solve a
lots of crash.

Please try to reproduce the problem with digiKam 5.6.0 pre release Linux
AppImage bundle which os compiled with Exiv2 0.26...

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[krita] [Bug 380517] New: Program hangs if another action performed during save

[bugzilla_noreply]

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

Bug ID: 380517
   Summary: Program hangs if another action performed during save
   Product: krita
   Version: 3.1.3-rc
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bentontram...@gmail.com
  Target Milestone: ---

When saving a file and doing the following when the save dialog box is open,
Krita will become non-reponsive.
- Click anywhere on the screen.
- Click on another open program window


The result
- The program must be manually terminated
- All work up until the last save is lost.  The autosave does not work.

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

[Breeze] [Bug 379010] Dark breeze icons missing (never appear)

[Walddys Emmanuel Dorrejo Céspedes]

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

--- Comment #5 from Walddys Emmanuel Dorrejo Céspedes  
---
(In reply to andreas from comment #4)
> can you please explain the issue I can't get it.

On Opensuse (42.2 or Tumbleewed), go to "Configure Desktop >> Icons >> Select
Breeze Dark >> click Apply" , nothing change, the icons system stay like normal
breeze, this bug appear since opensuse 13.2 and tumbleweed snapshot of that
time.

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

[digikam] [Bug 374783] Window location is not restored correctly after restart

[bugzilla_noreply]

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

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

   What|Removed |Added

Version|5.4.0   |5.6.0

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

[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager

[bugzilla_noreply]

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

azr...@googlemail.com changed:

   What|Removed |Added

 CC||azr...@googlemail.com

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

[krita] [Bug 380486] No default favorite brushes selected

[Boudewijn Rempt]

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

--- Comment #5 from Boudewijn Rempt  ---
> My thinking is that it could be good to have the popup remember the last tag?
> But if a least doesn't start empty is a major improvement.

That's what it's supposed to do...

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

[kdevelop] [Bug 380516] New: Debuging - Registers

[Baron Leonardo]

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

Bug ID: 380516
   Summary: Debuging - Registers
   Product: kdevelop
   Version: 5.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: CPP Debugger
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: mohamedayman.f...@zoho.com
CC: niko.s...@gmail.com
  Target Milestone: ---

I tried to debug ARM Cortex-M4 architecture using KDevelop.
After lots of trying to make it works, not all the registers appear in the the
Register view, the floating-point registers only shown up !!
here is the configuration I used to make debugging works
target remote :
b main
set remote hardware-breakpoint-limit 6
set remote hardware-watchpoint-limit 4
monitor reset halt
monitor reset init`

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

[plasmashell] [Bug 380515] New: Crash upon deleting a second panel

[Vishnu]

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

Bug ID: 380515
   Summary: Crash upon deleting a second panel
   Product: plasmashell
   Version: 5.9.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: vishn...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.5)

Qt Version: 5.8.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:

I'd created a second panel and then removed it

- Unusual behavior I noticed:

The screen flickered wildly; I use redshift, and the red-ness was reset to
day-light levels and it took ~10secs for redshift to bring it back to normal
again

- Custom settings of the application:

I had just a while back add the line `iconSize=2` to the
`.config/plasma-org.kde.plasma.desktop-appletsrc` at :
[Containments][49][General]

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7f8bbd3fc0 (LWP 4125))]

Thread 17 (Thread 0x7f7e7dffb700 (LWP 8241)):
#0  0x7f7f847df756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7f8592550b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7eca54f1d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f7eca5539d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f7eca54e263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f7eca551249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f7f85924658 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f7f847d92e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f7f8523754f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f7e7e7fc700 (LWP 8240)):
#0  0x7f7f847df756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7f8592550b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7eca54f1d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f7eca5539d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f7eca54e263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f7eca551249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f7f85924658 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f7f847d92e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f7f8523754f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f7e7effd700 (LWP 8239)):
#0  0x7f7f847df756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7f8592550b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7eca54f1d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f7eca5539d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f7eca54e263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f7eca551249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f7f85924658 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f7f847d92e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f7f8523754f in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f7e7f7fe700 (LWP 8238)):
#0  0x7f7f847df756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7f8592550b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7eca54f1d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f7eca5539d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f7eca54e263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f7eca551249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f7f85924658 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f7f847d92e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f7f8523754f in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f7e7700 (LWP 8237)):
#0  0x7f7f847df756 in 

[kactivitymanagerd] [Bug 380510] kactivitymanagerd bug using QtCurve widget style

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Antonio Rojas  ---


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

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

[QtCurve] [Bug 363753] crash-at-exit in QtCurve::Style::disconnectDBus

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||tuxoli...@gmail.com

--- Comment #71 from Antonio Rojas  ---
*** Bug 380510 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 380512] digikam crashes when trying to geotag a picture

[Yves Gänssinger]

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

--- Comment #1 from Yves Gänssinger  
---
I want to add that digikam also crashes when trying to simply edit the metadata
of that picture (CTRL+SHIFT+M).

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

[neon] [Bug 380509] lock screen doesn't accept password, timeout to suspend doesn't suspend

[Roland Vet]

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

Roland Vet  changed:

   What|Removed |Added

 CC||vet.rol...@gmail.com

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

[Discover] [Bug 380514] KDE Discover doesn't make adequate use of user reviews

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[Discover] [Bug 380514] New: KDE Discover doesn't make adequate use of user reviews

[Nate Graham]

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

Bug ID: 380514
   Summary: KDE Discover doesn't make adequate use of user reviews
   Product: Discover
   Version: 5.10.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

Discover in 5.10 supports user reviews, yay! But they're totally buried in the
UI, not displayed in a manner that really makes them useful.

Two changes are required to make them useful:

1. Display each application's average star rating alongside its icon and
description, both in the application list, and the detail view.
2. Display all user reviews underneath the description in the detail view;
don't make the user click "Show Comments..." They aren't comments anyway;
they're reviews.

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

[digikam] [Bug 374783] Window location is not restored correctly after restart

[Bill Goodman]

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

--- Comment #5 from Bill Goodman  ---
(In reply to caulier.gilles from comment #4)
> This problem is reproducible with current 5.6.0 pre release installer for
> Windows ?
> 
> https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

I just installed the 5.6.0 pre release and tested on Windows 7. The behavior is
the same.

On launch, the size of the window is remembered correctly, but the position of
the upper left corner seems to always be the same. In my case, on a 1980x1200
screen the upper left corner is always placed at [x=630, y=315].

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

[kirigami] [Bug 380511] Commit e0a623414cfb34df8e3ae717d720f7a0f952b2c8 broke scrolling behavior for mice, and touchpads, and touchscreens

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Commit  |Commit
   |e0a623414cfb34df8e3ae717d72 |e0a623414cfb34df8e3ae717d72
   |0f7a0f952b2c8 worsened  |0f7a0f952b2c8 broke
   |scrolling behavior for both |scrolling behavior for
   |mice and touchpads  |mice, and touchpads, and
   ||touchscreens

--- Comment #1 from Nate Graham  ---
Also, now touch doesn't work at all. Drags don't work because the initial
finger down movement is interpreted as a click, and no scrolling ever happens.

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

[Discover] [Bug 377895] Window sizes < 1201 pixels wide obscure the ability to go back to the app list

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #4 from Nate Graham  ---
I see in 5.10 that there is now a "Close description" button, but this isn't
adequate for several reasons:

1. It's in the wrong place: it should be at the top, not the bottom. Back
buttons go on top as a standard UI convention.
2. It has an arrow the points to the right, not the left. Back buttons always
point to the left.
3. Only the arrow is clickable, not the text. The click/touch area is very
small.
4. The text "Close description" is ambiguous. It should just be a regular back
button with the word "Back".

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

[neon] [Bug 380513] New: Removal of neon-desktop when uninstalling vlc

[Gabriel]

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

Bug ID: 380513
   Summary: Removal of neon-desktop when uninstalling vlc
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages Dev Edition [stable]
  Assignee: neon-b...@kde.org
  Reporter: gabriellasarosal...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

Created attachment 105868
  --> https://bugs.kde.org/attachment.cgi?id=105868=edit
command

When running the command: sudo apt remove vlc or sudo apt remove --purge vlc.
Apt selects neon-desktop packages instead of vlc.

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

[digikam] [Bug 380512] New: digikam crashes when trying to geotag a picture

[bugzilla_noreply]

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

Bug ID: 380512
   Summary: digikam crashes when trying to geotag a picture
   Product: digikam
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: kde-bugs.20.muellerme...@spamgourmet.com
  Target Milestone: ---

Application: digikam (5.5.0)

Qt Version: 5.8.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

1. Marked two pictures: one of them ("Picture_A") I knew had a location set,
the other one ("Picture_B") had no location set
2. Open Geotagging-dialog with CTRL+SHIFT+G
3. Copied location from Picture_A
4. Inserted the location to Picture_B
5. Clicked on "Apply" button

digikam crashed

The location must have been written to Picture_B, since after a restart of
digikam, Picture_B contained the location. 


- Additional information:
I suspect that the Exif metadata of that particular picture "Picture_B" was
corrupted. 
What lead me to this theory was the fact that digikam did not crash, when I had
removed all MetaData from Picture_B before trying to write the new geotag to
Picture_B.

I can supply you with the "Picture_B" as needed.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2a229f55c0 (LWP 5453))]

Thread 49 (Thread 0x7f2922058700 (LWP 5613)):
#0  0x7f2a18acb39d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2a1eb7d4d3 in QWaitCondition::wait(QReadWriteLock*, unsigned long)
() at /usr/lib/libQt5Core.so.5
#2  0x7f2a1a2d8b7b in QtAV::BlockingQueue::take() () at
/usr/lib/libQtAV.so.1
#3  0x7f2a1a3425b8 in QtAV::ExtractThread::run() () at
/usr/lib/libQtAV.so.1
#4  0x7f2a1eb7be9c in  () at /usr/lib/libQt5Core.so.5
#5  0x7f2a18ac5297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f2a1de7725f in clone () at /usr/lib/libc.so.6

Thread 48 (Thread 0x7f2902fe5700 (LWP 5602)):
#0  0x7f2a18acb6cc in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2a1eb7d0d8 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2a1eb785b4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f2a1eb7be9c in  () at /usr/lib/libQt5Core.so.5
#4  0x7f2a18ac5297 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f2a1de7725f in clone () at /usr/lib/libc.so.6

Thread 47 (Thread 0x7f29027e4700 (LWP 5601)):
[KCrash Handler]
#6  0x7f2a1ddbd670 in raise () at /usr/lib/libc.so.6
#7  0x7f2a1ddbed00 in abort () at /usr/lib/libc.so.6
#8  0x7f2a1ddb645a in __assert_fail_base () at /usr/lib/libc.so.6
#9  0x7f2a1ddb64d2 in  () at /usr/lib/libc.so.6
#10 0x7f2a1801c91e in  () at /usr/lib/libexiv2.so.14
#11 0x7f2a18017072 in  () at /usr/lib/libexiv2.so.14
#12 0x7f2a18017b07 in  () at /usr/lib/libexiv2.so.14
#13 0x7f2a18017072 in  () at /usr/lib/libexiv2.so.14
#14 0x7f2a1801c5bb in  () at /usr/lib/libexiv2.so.14
#15 0x7f2a18017072 in  () at /usr/lib/libexiv2.so.14
#16 0x7f2a18017b07 in  () at /usr/lib/libexiv2.so.14
#17 0x7f2a18017072 in  () at /usr/lib/libexiv2.so.14
#18 0x7f2a18034d9c in  () at /usr/lib/libexiv2.so.14
#19 0x7f2a18022f3d in  () at /usr/lib/libexiv2.so.14
#20 0x7f2a17fb45c6 in Exiv2::ExifParser::encode(std::vector >&, unsigned char const*, unsigned int,
Exiv2::ByteOrder, Exiv2::ExifData const&) () at /usr/lib/libexiv2.so.14
#21 0x7f2a17fcf0df in  () at /usr/lib/libexiv2.so.14
#22 0x7f2a17fd04a9 in Exiv2::JpegBase::writeMetadata() () at
/usr/lib/libexiv2.so.14
#23 0x7f2a2115162e in  () at /usr/lib/libdigikamcore.so.5.5.0
#24 0x7f2a21153cf8 in  () at /usr/lib/libdigikamcore.so.5.5.0
#25 0x7f2a2114c61f in Digikam::MetaEngine::save(QString const&) const () at
/usr/lib/libdigikamcore.so.5.5.0
#26 0x7f2a2118f784 in Digikam::DMetadata::save(QString const&) const () at
/usr/lib/libdigikamcore.so.5.5.0
#27 0x7f2a21636a56 in Digikam::GPSImageItem::saveChanges() () at
/usr/lib/libdigikamcore.so.5.5.0
#28 0x7f2a1e82f808 in Digikam::ImageGPS::saveChanges() () at
/usr/lib/libdigikamdatabase.so.5.5.0
#29 0x7f2a2164bf8f in  () at /usr/lib/libdigikamcore.so.5.5.0
#30 0x7f2a2164e2e7 in  () at /usr/lib/libdigikamcore.so.5.5.0
#31 0x7f2a2164ecb5 in  () at /usr/lib/libdigikamcore.so.5.5.0
#32 0x7f2a14106bad in QtConcurrent::ThreadEngineBase::run() () at
/usr/lib/libQt5Concurrent.so.5
#33 0x7f2a1eb78371 in  () at /usr/lib/libQt5Core.so.5
#34 0x7f2a1eb7be9c in  () at 

[kirigami] [Bug 380511] Commit e0a623414cfb34df8e3ae717d720f7a0f952b2c8 worsened scrolling behavior for both mice and touchpads

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

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

[kirigami] [Bug 380511] Commit e0a623414cfb34df8e3ae717d720f7a0f952b2c8 worsened scrolling behavior for both mice and touchpads

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=376910

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

[kirigami] [Bug 380511] New: Commit e0a623414cfb34df8e3ae717d720f7a0f952b2c8 worsened scrolling behavior for both mice and touchpads

[Nate Graham]

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

Bug ID: 380511
   Summary: Commit e0a623414cfb34df8e3ae717d720f7a0f952b2c8
worsened scrolling behavior for both mice and
touchpads
   Product: kirigami
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: pointedst...@zoho.com
  Target Milestone: Not decided

Commit e0a623414cfb34df8e3ae717d720f7a0f952b2c8 was introduced to fix
https://bugs.kde.org/show_bug.cgi?id=376910. Before this commit, scrolling with
a mouse wheel was fine, but scrolling with a touchpad resulted in acceleration
being continuously increased.

With commit e0a623414cfb34df8e3ae717d720f7a0f952b2c8, scrolling with both a
mouse wheels and a touchpad results in the view scrolling one line at a time at
a constant speed.

For a mouse wheel, this is far too slow and ignores the systemwide setting
(System Settings > Input Devices > Mouse > Advanced > Mouse wheel scrolls by).

For a touchpad, this is still *effectively* too slow; it should scroll in
one-pixel increments, but with the speed determined by the speed of the finger
motion.

You can see the problem in Discover on a machine with Kirigami 2.1. The
scrolling behavior is poor for both input devices.


It was mentioned in https://bugs.kde.org/show_bug.cgi?id=376910 that the
QuickControls ScrollView has the correct behavior for both devices out of the
box in QT 5.9 onwards. QT 5.9 was just released a few days ago:
http://blog.qt.io/blog/2017/05/31/qt-5-9-released/

Maybe we should redirect our effort to use QT 5.9 which has appropriate
behavior rather than try to fix it manually and stay with an old QT version.

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

[kirigami] [Bug 380511] Commit e0a623414cfb34df8e3ae717d720f7a0f952b2c8 worsened scrolling behavior for both mice and touchpads

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kactivitymanagerd] [Bug 380510] kactivitymanagerd bug using QtCurve widget style

[Chris]

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

Chris  changed:

   What|Removed |Added

 CC||tuxoli...@gmail.com

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

[kactivitymanagerd] [Bug 380510] New: kactivitymanagerd bug using QtCurve widget style

[Chris]

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

Bug ID: 380510
   Summary: kactivitymanagerd bug using QtCurve widget style
   Product: kactivitymanagerd
   Version: 5.10.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: tuxoli...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Since I updated Plasma to version 5.10, the following error has popped up every
time I log in:

Executable: kactivitymanagerd PID: 2147 Signal: Segmentation fault (11) Time:
03/06/2017 16:34:17

Application: kactivitymanagerd (kactivitymanagerd), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2bc9412180 (LWP 2147))]

Thread 2 (Thread 0x7f2bbc785700 (LWP 2150)):
#0  0x7f2bc6cf12bd in poll () from /usr/lib/libc.so.6
#1  0x7f2bc64ae8e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f2bc64b0679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f2bbf31c1d9 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f2bc73e8e9c in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f2bc5929297 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f2bc6cfb25f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f2bc9412180 (LWP 2147)):
[KCrash Handler]
#6  0x7f2bc73e0d47 in QMutex::lock() () from /usr/lib/libQt5Core.so.5
#7  0x7f2bc7f3deb7 in ?? () from /usr/lib/libQt5DBus.so.5
#8  0x7f2bc7f3ef1c in QDBusConnection::sessionBus() () from
/usr/lib/libQt5DBus.so.5
#9  0x7f2baf61b0c8 in ?? () from /usr/lib/qt/plugins/styles/qtcurve.so
#10 0x7f2baf620210 in ?? () from /usr/lib/qt/plugins/styles/qtcurve.so
#11 0x7f2baf6202a9 in ?? () from /usr/lib/qt/plugins/styles/qtcurve.so
#12 0x7f2baf653558 in ?? () from /usr/lib/qt/plugins/styles/qtcurve.so
#13 0x7f2baf653619 in ?? () from /usr/lib/qt/plugins/styles/qtcurve.so
#14 0x7f2bc75c2e07 in ?? () from /usr/lib/libQt5Core.so.5
#15 0x7f2bc75b3a62 in ?? () from /usr/lib/libQt5Core.so.5
#16 0x7f2bc75b3ba9 in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7f2bc7602a83 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#18 0x7f2bc83768b9 in ?? () from /usr/lib/libQt5Widgets.so.5
#19 0x7f2bc6c44298 in __run_exit_handlers () from /usr/lib/libc.so.6
#20 0x7f2bc6c442ea in exit () from /usr/lib/libc.so.6
#21 0x7f2bc90b685f in
KDBusService::KDBusService(QFlags, QObject*) ()
from /usr/lib/libKF5DBusAddons.so.5
#22 0x00408e7d in ?? ()
#23 0x7f2bc6c2e43a in __libc_start_main () from /usr/lib/libc.so.6
#24 0x004090da in _start ()

Although that error appears, Plasma seems to work well.
Switching to a non-QtCurve widget style (such as Fusion or default Breeze)
solves the issue.

Is anyone facing the same situation?

Cheers,
Chris

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

[neon] [Bug 380509] New: lock screen doesn't accept password, timeout to suspend doesn't suspend

[Kirk Job Sluder]

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

Bug ID: 380509
   Summary: lock screen doesn't accept password, timeout to
suspend doesn't suspend
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: kirkjobslu...@fastmail.fm
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

New behavior since upgrading to Neon 10.5.0 earlier last week. Suspend timeout
set in System Settings > Hardware > Power Management doesn't suspend. The lock
screen activates after 10 minutes of idle time. Lock screen refuses to accept
passwords. Running sudo loginctl unlock-sessions unlocks the session. 

The problem only happens when triggered by a Power Management timeout. Manually
locking the screen and suspending does not trigger the problem. The problem
persists through multiple reboots. 

Steps to reproduce:

1. Set screen dim and suspend timeout on Energy Saving control panel.
2. Wait for timeout.
3. Attempt to login.

Bug appears on my desktop machine using Nvidia Drivers. I can't reproduce the
problem on a laptop using stock Intel drivers. Suggestions for where to look in
the logs for this would be helpful.

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

[Breeze] [Bug 380508] Using the Breeze icon theme for LibreOffice results in small icons always being used even when large ones should be used--and are available (visible in Task Switcher with Large I

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

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

[Breeze] [Bug 380508] Using the Breeze icon theme for LibreOffice results in small icons always being used even when large ones should be used--and are available (visible in Task Switcher with Large I

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
Created attachment 105867
  --> https://bugs.kde.org/attachment.cgi?id=105867=edit
`xprop` output

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

[Breeze] [Bug 380508] Using the Breeze icon theme for LibreOffice results in small icons always being used even when large ones should be used--and are available (visible in Task Switcher with Large I

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
Created attachment 105866
  --> https://bugs.kde.org/attachment.cgi?id=105866=edit
Task Switcher showing ugly pixellated icons for LibreOffice programs

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

[Breeze] [Bug 380508] New: Using the Breeze icon theme for LibreOffice results in small icons always being used even when large ones should be used--and are available (visible in Task Switcher with La

[Nate Graham]

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

Bug ID: 380508
   Summary: Using the Breeze icon theme for LibreOffice results in
small icons always being used even when large ones
should be used--and are available (visible in Task
Switcher with Large Icons)
   Product: Breeze
   Version: 5.10.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: pointedst...@zoho.com
CC: kain...@gmail.com
  Target Milestone: ---

Linux distribution: openSUSE Tumbleweed
Desktop environment: KDE Plasma 5.10
LibreOffice version: 5.3.3.2

Steps to reproduce
1. Use the Large Icons Task Switcher style (System Settings > Window Management
> Task Switcher > Visualization > Large Icons
2. Install LibreOffice
3. Install the breeze icon theme ('libreoffice-icon-theme-breeze' package in
openSUSE)
4. Tell LibreOffice to use the Breeze icon theme (LibreOffice > Tools > Options
> LibreOffice/View > Icon Style > Breeze)
5. Restart LibreOffice
6. Hit alt-tab to bring up the Task Switcher


Expected results:
- The Task Switcher viewer shows nice pretty large icons for all programs


Actual results:
- All programs except for LibreOffice programs have nice icons; LibreOffice
programs have ugly pixellated small icons that come from e.g.
/usr/share/libreoffice/share/config/images_breeze.zip/res/odg_16_8.png


Reproducibility:
- Only happens when using the Breeze icon theme in LibreOffice. If you change
the theme to Oxygen (LibreOffice > Tools > Options > LibreOffice/View > Icon
Style > Oxygen a correct large icon is shown in the Task Switcher.


Additional information:
I've attached the output of `xprop` on an affected LibreOffice window. It shows
that a small icon is used for the large icon sizes.

There are already many perfectly nice large icons available on the system,
including one within the Breeze theme icon set itself:
/usr/share/libreoffice/share/config/images_breeze.zip/res/*128.png
/usr/share/icons/breeze/apps/48/libreoffice-*.svg
/usr/share/icons/hicolor/256x256/apps/libreoffice-*.png

One of these should be shown instead--probably the first.

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

[Breeze] [Bug 380508] Using the Breeze icon theme for LibreOffice results in small icons always being used even when large ones should be used--and are available (visible in Task Switcher with Large I

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[clazy] [Bug 378999] clazy pre-built binary on Windows doesn't work on 32-bit

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Sergio Martins  ---
Works with the -m32 switch

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

[clazy] [Bug 379248] AlpineLinux: Option 'help-list' registered more than once!

[Sergio Martins]

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

Sergio Martins  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED

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

[digikam] [Bug 196672] Add new option to setup global preference about default album dating

[Jaakko Luttinen]

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

--- Comment #8 from Jaakko Luttinen  ---
I just came up with a very simple solution that would be sufficient for me.
Instead of needing to modify anything about album date framework, just add a
few options to View -> Sort Albums:

-> By Oldest Image Date
-> By Average Image Date
-> By Newest Image Date

in addition to the existing options:

-> By Folder
-> By Category
-> By (Album) Date

And if the choice is persistent between sessions, that would be just the
sufficient and perfect solution for me. Thus, this would still keep album date
system as it is now, but still allows users to "ignore" that value and sort
based on the album contents. What do you think?

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

[digikam] [Bug 380507] New: Menu items missing

[bugzilla_noreply]

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

Bug ID: 380507
   Summary: Menu items missing
   Product: digikam
   Version: 4.14.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: showfoto
  Assignee: digikam-de...@kde.org
  Reporter: k...@manuscripts.org.uk
  Target Milestone: ---

Since my upgrade from Ubuntu 16.04 to 16.10 some menu items have no options:
Colour, Enhance, Decorate, and Filters have just a blank black vertical bar,
where there used to be a series of options. The "Transform" menu item has some
options (e.g. rotate and flip) but not others (e.g. resize)

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

[okular] [Bug 380506] New: crashing on an annotated document loses new annotations

[bugzilla_noreply]

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

Bug ID: 380506
   Summary: crashing on an annotated document loses new
annotations
   Product: okular
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: azr...@googlemail.com
  Target Milestone: ---

1. Open a PDF file
2. make some annotation
3. save as... to create a new PDF containing the annotations
4. close & reopen okular
5. open the new PDF file
6. make some annotation
7.1. close okular: it asks to save or discard the new annotation (after
)
7.2. crash okular (a bug, or simulate with SIGKILL/kill -9): the new annotation
is lost

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

[kscreenlocker] [Bug 380491] kscreenlocker_greet incorrect behaviour after pressing enter key with empty password

[bugzilla_noreply]

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

tobias.ert...@gmail.com changed:

   What|Removed |Added

 CC||tobias.ert...@gmail.com

--- Comment #2 from tobias.ert...@gmail.com ---
I think I've encountered the same issue.
Version: 5.10.0

I noticed that I am unable to unlock the lockscreen after the screen went off.

I can unlock the lockscreen with my password without any problem:
- If I lock the screen using ctrl+alt+L.
- If I put the computer in standby and wake it up again.

I cannot unlock the lockscreen (error: "Unlocking failed"):
- If I wait until the screen goes off and wake it up (sometimes using enter).

However, I can always use "loginctl unlock-session" to unlock from another tty.
Downgrading kscreenlocker to 5.9.5 fixes the issue.

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

[okular] [Bug 315552] Allow save annotations directly to original pdf file

[bugzilla_noreply]

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

azr...@googlemail.com changed:

   What|Removed |Added

 CC||azr...@googlemail.com

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

[forum.kde.org] [Bug 380505] New: Navigation menu Does not work in Safari

[Christopher Yeleighton]

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

Bug ID: 380505
   Summary: Navigation menu Does not work in Safari
   Product: forum.kde.org
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: forum-ad...@kde.org
  Reporter: giecr...@stegny.2a.pl
  Target Milestone: ---

There is a navigation bar at the bottom of each page, and that bar contains a
menu that allows you to go Home and to various other KDE places.  The menu
opens all right but tapping on the links has no effect‭‭ (Safari/iOS).  The
bottom bar is invisible in the Reader mode, which is available on the home page
of the forum (but not when you are viewing a topic).

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

[skrooge] [Bug 380460] skrooge 2.8.1 problème intégration fichier skrooge.skg [ERR-10001]: no such table: main.vm_budget_tmp Impossible d'exécuter l'instruction

[Stephane MANKOWSKI]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/skr
   ||ooge/48173d89837c09fa62d927
   ||3fd9d98dbe4827d140

--- Comment #3 from Stephane MANKOWSKI  ---
Git commit 48173d89837c09fa62d9273fd9d98dbe4827d140 by Stephane Mankowski.
Committed on 03/06/2017 at 15:14.
Pushed by smankowski into branch 'master'.

Failure when loading file from skrooge 1.12

M  +1-0CHANGELOG
M  +1-0skgbankmodeler/skgdocumentbank.cpp
A  +---tests/input/skgtestmigration/version_1.12.skg
M  +4-0tests/skgbankmodelertest/skgtestmigration.cpp

https://commits.kde.org/skrooge/48173d89837c09fa62d9273fd9d98dbe4827d140

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

[frameworks-kconfig] [Bug 380504] race when building python bindings

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

   Assignee|matt...@mjdsystems.ca   |steve...@gmail.com

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

[frameworks-kconfig] [Bug 380504] New: race when building python bindings

[Antonio Rojas]

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

Bug ID: 380504
   Summary: race when building python bindings
   Product: frameworks-kconfig
   Version: 5.34.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matt...@mjdsystems.ca
  Reporter: aro...@archlinux.org
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Building kconfig with python bindings fails about 50% of the times due to a
race condition

sip: Unable to find file "conversioncheck.sip"
make[2]: ***
[src/gui/CMakeFiles/sip_generated_KConfigGui_files.dir/build.make:65:
src/gui/pybuild/PyKF5/KConfigGui/unifiedKConfigGui.cpp] Error 1
make[1]: *** [CMakeFiles/Makefile2:4009:
src/gui/CMakeFiles/sip_generated_KConfigGui_files.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs

Would be nice if there was a way to make sure that the sip file has been
generated before trying to use it.

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

[Discover] [Bug 380496] Discover crashes upon opening

[CDK]

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

--- Comment #5 from CDK  ---
Yep. Problem went away after installing flatpack.

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

[krita] [Bug 380486] No default favorite brushes selected

[Quiralta]

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

Quiralta  changed:

   What|Removed |Added

 CC||rjquira...@gmail.com

--- Comment #4 from Quiralta  ---
In linux I notice this happens mostly after restarting a session on the DE,
usually (although not every single time) Krita remembers the last tag used
after reopening it within a session, especially when opening existing kra file.

My thinking is that it could be good to have the popup remember the last tag?
But if a least doesn't start empty is a major improvement.

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

[kscreenlocker] [Bug 372275] New session breaks login screen locker

[Maximilian Hartert]

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

Maximilian Hartert  changed:

   What|Removed |Added

 CC||max.hart...@it-top.de

--- Comment #5 from Maximilian Hartert  ---
I am not shure if it is the same problem, since it does not involve a new
session (I think).

But lately my lock screen is broken too. The normal log in works fine. But once
I lock my system or let it lock due to inactivity, I have to reboot the system.

It also tells me to put in "loginctl unlock-sessions", which does not help.
Currently I am on KDE 5.10, that is running on neon stable dev.

I don't know since when I have this problem, but it can't be that long. Usually
I won't lock my system at home, since I don't need to.

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

[plasmashell] [Bug 380385] Plasma crashes soon after login

[bugzilla_noreply]

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

bucko.jak...@gmail.com changed:

   What|Removed |Added

 CC||bucko.jak...@gmail.com

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

[plasmashell] [Bug 380385] Plasma crashes soon after login

[bugzilla_noreply]

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

--- Comment #1 from bucko.jak...@gmail.com ---
Created attachment 105865
  --> https://bugs.kde.org/attachment.cgi?id=105865=edit
New crash information added by DrKonqi

plasmashell (5.10.0) using Qt 5.7.1

- What I was doing when the application crashed:
I was using widescreen on notebook
- Unusual behavior I noticed:
widgets was freezing and walpaper was gone

-- Backtrace (Reduced):
#6  0x7fdac19168de in TaskManager::TasksModel::data (this=0x31ecb30,
proxyIndex=..., role=268) at /workspace/build/libtaskmanager/tasksmodel.cpp:924
#7  0x7fdb74082749 in QSortFilterProxyModel::data (this=,
index=..., role=268) at itemmodels/qsortfilterproxymodel.cpp:1975
#8  0x7fdac7eec0f1 in Plasma::SortFilterModel::get
(this=this@entry=0x31f07f0, row=) at
/workspace/build/src/declarativeimports/core/datamodel.cpp:198
#9  0x7fdac7f0b5db in Plasma::SortFilterModel::qt_static_metacall
(_o=_o@entry=0x31f07f0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=6, _a=_a@entry=0x7fffd38856b0) at
/workspace/build/obj-x86_64-linux-gnu/src/declarativeimports/core/moc_datamodel.cpp:172
#10 0x7fdac7f0d428 in Plasma::SortFilterModel::qt_metacall (this=0x31f07f0,
_c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fffd38856b0) at
/workspace/build/obj-x86_64-linux-gnu/src/declarativeimports/core/moc_datamodel.cpp:300

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

[Discover] [Bug 380043] discover freezes till all updates/packages are installed . should also show progress bar

[bugzilla_noreply]

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

--- Comment #3 from kehar...@gmx.com ---
Hello aleix i ve attached a screenshot of discover to show the problem. 
i downloaded the opera browser deb package from their website . double 
clicking on it opened it in discover. as you can see in the bottom left 
corner it just displays " tasks 0%" and below it " installing"  during 
the whole install process. The progress bars move randomly ( sometimes 
going backwards a little) and non linearly.During the whole install 
process Discover sort of becomes unresponsive. with no way of knowing 
how much time is left or what the real progress in the installation or 
update is left. This becomes especially more apparent while installing 
large programs ( eg a browser or libre office)

The problem with it taking forever to load icons and icon themes in the 
plasma addons section in Discover seems to have been fixed.(the icon 
themes section wouldnt even load at all before)


Thank you



On 05/22/2017 06:57 AM, Aleix Pol wrote:
> https://bugs.kde.org/show_bug.cgi?id=380043
>
> Aleix Pol  changed:
>
> What|Removed |Added
> 
>   Resolution|--- |WAITINGFORINFO
>   Status|UNCONFIRMED |NEEDSINFO
>
> --- Comment #1 from Aleix Pol  ---
> Do you always get such freeze when updating? Or only when updating certain
> kinds of assets?
>

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

[kwin] [Bug 380404] something in the update from 5.27 to 5.34 broke focus

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

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

[krusader] [Bug 267756] Rename tab or add prefix to tab label

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kru
   ||sader/aba436eda41f42628ae56
   ||ed6c12cdb93010df948

--- Comment #1 from Alex Bikadorov  ---
Git commit aba436eda41f42628ae56ed6c12cdb93010df948 by Alexander Bikadorov.
Committed on 03/06/2017 at 13:31.
Pushed by abikadorov into branch 'master'.

Changes to panel tab label

* added host if not empty
* special label on startup when dir does not exist
* fix crash when [panel not visible]+[non existing dir]+[show full path]

FIXED: [ 267756 ] Rename tab or add prefix to tab label

M  +56   -78   krusader/paneltabbar.cpp
M  +1-1krusader/paneltabbar.h

https://commits.kde.org/krusader/aba436eda41f42628ae56ed6c12cdb93010df948

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

[kdepim] [Bug 380487] messagelib master branch fails to build

[Luca Beltrame]

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

Luca Beltrame  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||lbeltr...@kde.org
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Luca Beltrame  ---
Breaks on OpenSUSE as well.

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

[systemsettings] [Bug 379324] Deleting System-Fonts causes a freeze of systemsettings

[bugzilla_noreply]

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

martin@gmx.de changed:

   What|Removed |Added

Version|5.9.5   |5.10.0

--- Comment #3 from martin@gmx.de ---
This bug also occurs with Plasma 5.10.
If any further information is necessary or helpful to confirm this bug, please
let me know.

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

[digikam] [Bug 256361] SlideShow use low resolution previews instead of full resolution images

[JF JOLIMAITRE]

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

JF JOLIMAITRE  changed:

   What|Removed |Added

 CC||j...@aliceadsl.fr

--- Comment #26 from JF JOLIMAITRE  ---
Hi,
I'm surprised this problem is considered solver. I encounter this (low
resolution output when "Embedded preview loads full-sized images" is not
selected), both on DK 4.14 and 5.5.

Jean-Fred

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

[plasmashell] [Bug 380503] New: Plasma can't start and always crashes at startup

[Johan]

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

Bug ID: 380503
   Summary: Plasma can't start and always crashes at startup
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: pin...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.8.0-36-generic i686
Distribution: Ubuntu 16.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Just startup Kubuntu
- Unusual behavior I noticed:
No desktop appeared
- Custom settings of the application:
None: default install of Kubuntu 16.04.2 (fresh install)

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb1ac1800 (LWP 1252))]

Thread 8 (Thread 0xa1313b40 (LWP 1515)):
#0  0xb76f4ce5 in __kernel_vsyscall ()
#1  0xb76f4979 in __vdso_clock_gettime ()
#2  0xb4d38142 in __GI___clock_gettime (clock_id=1, tp=0xa1312f04) at
../sysdeps/unix/clock_gettime.c:115
#3  0xb509c338 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#4  0xb522b232 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#5  0xb522b754 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6  0xb522cd19 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#7  0xb43bf5db in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb43c0024 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb43c0254 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb522d964 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#11 0xb51d27a3 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#12 0xb51d2bfa in QEventLoop::exec(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#13 0xb4ff8f1d in QThread::exec() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#14 0xa1841980 in KCupsConnection::run() () from
/usr/lib/i386-linux-gnu/libkcupslib.so
#15 0xb4ffe43b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#16 0xb4bd3295 in start_thread (arg=0xa1313b40) at pthread_create.c:333
#17 0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 7 (Thread 0xa9285b40 (LWP 1344)):
#0  0xb43bcf00 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb43bf9f0 in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb43c00b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb43c0254 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb522d964 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#5  0xb51d27a3 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6  0xb51d2bfa in QEventLoop::exec(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#7  0xb4ff8f1d in QThread::exec() () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#8  0xb6c4a7a9 in ?? () from /usr/lib/i386-linux-gnu/libQt5Quick.so.5
#9  0xb4ffe43b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#10 0xb4bd3295 in start_thread (arg=0xa9285b40) at pthread_create.c:333
#11 0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 6 (Thread 0xaa950b40 (LWP 1333)):
#0  0xb76f4ce5 in __kernel_vsyscall ()
#1  0xb4bd8a6c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xb4d3764d in __pthread_cond_wait (cond=0xb76648d0, mutex=0xb76648b8) at
forward.c:149
#3  0xb752ca2c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#4  0xb752ca6c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#5  0xb4bd3295 in start_thread (arg=0xaa950b40) at pthread_create.c:333
#6  0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 5 (Thread 0xaba78b40 (LWP 1302)):
#0  0xb4406488 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb43bfa65 in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb43c00b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb43c0254 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb522d964 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#5  0xb51d27a3 in
QEventLoop::processEvents(QFlags) () from
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6  0xb51d2bfa in QEventLoop::exec(QFlags) ()
from 

[krita] [Bug 380502] New: Text tool crash

[bugzilla_noreply]

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

Bug ID: 380502
   Summary: Text tool crash
   Product: krita
   Version: 3.1.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: deadindeptf...@gmail.com
  Target Milestone: ---

Application: krita (3.1.3)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.8.0-53-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed: Typed some text, highlighted
it, then went to the Tool Options docker panel. Clicked on the list of fonts
and used the mouse scroll wheel to scroll down the list. Krita shuts down.

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdeda4fe900 (LWP 10133))]

Thread 5 (Thread 0x7fde929c1700 (LWP 10146)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fdeeb6429fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0xa00cb70) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0xa00c7b0,
mutex=mutex@entry=0xa00c7a8, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fdeec3104ba in QFileInfoGatherer::run (this=0xa00c798) at
dialogs/qfileinfogatherer.cpp:217
#4  0x7fdeeb641b48 in QThreadPrivate::start (arg=0xa00c798) at
thread/qthread_unix.cpp:368
#5  0x7fdee5093754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#6  0x7fdee57856ba in start_thread (arg=0x7fde929c1700) at
pthread_create.c:333
#7  0x7fdeead3882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fde931c2700 (LWP 10145)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fdeeb6429fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x99385b0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=mutex@entry=0x9938590,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fdeeb63be56 in QSemaphore::tryAcquire (this=0x9931c40, n=n@entry=1,
timeout=timeout@entry=-1) at thread/qsemaphore.cpp:220
#4  0x7fdee8efbb63 in KisTileDataSwapper::waitForWork
(this=this@entry=0x7fdee93d5a80 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at
/workspace/build/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#5  0x7fdee8efbd5a in KisTileDataSwapper::run (this=0x7fdee93d5a80
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at
/workspace/build/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#6  0x7fdeeb641b48 in QThreadPrivate::start (arg=0x7fdee93d5a80 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at
thread/qthread_unix.cpp:368
#7  0x7fdee5093754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#8  0x7fdee57856ba in start_thread (arg=0x7fde931c2700) at
pthread_create.c:333
#9  0x7fdeead3882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fde939c3700 (LWP 10144)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fdeeb6429fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x9938340) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x9931c28,
mutex=mutex@entry=0x9931c20, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fdeeb63bbab in QSemaphore::acquire (this=this@entry=0x7fdee93d5a50
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+16>,
n=n@entry=1) at thread/qsemaphore.cpp:143
#4  0x7fdee8ee24ee in KisTileDataPooler::waitForWork (this=0x7fdee93d5a40
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
/workspace/build/libs/image/tiles3/kis_tile_data_pooler.cc:165
#5  0x7fdee8ee2caa in KisTileDataPooler::run (this=0x7fdee93d5a40
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
/workspace/build/libs/image/tiles3/kis_tile_data_pooler.cc:187
#6  0x7fdeeb641b48 in QThreadPrivate::start (arg=0x7fdee93d5a40 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#7  0x7fdee5093754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#8  0x7fdee57856ba in start_thread (arg=0x7fde939c3700) at
pthread_create.c:333
#9  0x7fdeead3882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fdecdd49700 (LWP 10135)):
#0  0x7fdeead2cb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  

[Touchpad-KCM] [Bug 377208] "Invert scroll direction" controls "Tap-and-drag lock" setting in Touchpad settings (on Wayland)

[Szymon Łągiewka]

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

--- Comment #3 from Szymon Łągiewka  ---
Still happening on Plasma 5.10 (Qt 5.8.0 in my system).

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

[Touchpad-KCM] [Bug 377208] "Invert scroll direction" controls "Tap-and-drag lock" setting in Touchpad settings (on Wayland)

[Szymon Łągiewka]

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

Szymon Łągiewka  changed:

   What|Removed |Added

 CC||bugs-...@lagiewka.pl

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

[kscreenlocker] [Bug 380501] New: Dead keys are ignored in password input box

[Feufochmar]

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

Bug ID: 380501
   Summary: Dead keys are ignored in password input box
   Product: kscreenlocker
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: feufochmar...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

Since I updated to plasma 5.10.0 yesterday, the dead keys stopped working when
I use them in the password field of kscreenlocker. For instance, when typing
the dead key "^" followed by a "o", I'm getting a "o" inputted instead of "ô",
as if the dead key was not used.

The dead keys still work in other KDE applications like kate or konsole. They
also work in the desktop search/execute input box. Since I'm using a console
login, I don't know if the logging screen is also affected by this problem.

I'm using a french layout (fr oss).

My password containing accented characters, I use the dead keys to input them.
Fortunately for me, I can input the ones I need in another way with the layout
I use.
However, someone using accented characters in their password may not be able to
unlock their screen if their layout does not provide other ways to input them
than using dead keys.

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