[umbrello] [Bug 358293] New: C++ Code Generation Settings don't change anything

[via KDE Bugzilla]

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

Bug ID: 358293
   Summary: C++ Code Generation Settings don't change anything
   Product: umbrello
   Version: Git
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ryan.nieh...@gmail.com

A few issues with C++ Code Generation Settings:
-Style selection seems to be ignored
-None of the General C++ Language Settings are saved when changed.

Reproducible: Always

Steps to Reproduce:
1.  Goto Settings ->Configure Umbrello...
2.  Select C++ on General tab
3.  Then Code Generation -> Language Settings
4.  Change a few settings, including style and some under subtab General
5.  Apply & Generate Code

Actual Results:  
Settings aren't actually saved
Generated code still uses // comments instead of /* */ when that style is
selected.

Expected Results:  
Going back into settings should reflect every change that was previously made.
Generated code should use /* */ for document when that style is selected.

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Jonathan Doman via KDE Bugzilla]

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

Jonathan Doman  changed:

   What|Removed |Added

 CC||jonathan.do...@gmail.com

--- Comment #23 from Jonathan Doman  ---
I upgraded to plasma-framework 5.18.0-2 and it did not change any behavior for
me. I am *never* able to login through SDDM when breeze theme is used (tried up
to ten times in a row).

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

[Touchpad-KCM] [Bug 357907] Crash eventual crash, often on load

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #12 from Weng Xuetian  ---
Emm, one thing I mistook is that I thought it is in 5.5.3 because of the report
says so. But it's acutally in git.

So this should be fixed by
http://commits.kde.org/plasma-desktop/cda58f0e256d53e66ca44b77fa7307ee670b8313
.

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Arthur Țițeică via KDE Bugzilla]

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

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur.tite...@gmail.com

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

[Akonadi] [Bug 289097] error "Unable to fetch item from backend" when entering IMAP folder

[Dimitrios Glentadakis via KDE Bugzilla]

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

--- Comment #82 from Dimitrios Glentadakis  ---
Yes close. I cannot help, i have switched to lxqt since 2 years

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

[plasmashell] [Bug 358294] Windows just got the upper hand on kde5

[Michael Fox via KDE Bugzilla]

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

Michael Fox  changed:

   What|Removed |Added

 CC||kamijoutouma...@gmail.com

--- Comment #1 from Michael Fox  ---
Now i have read that the reason it was removed is because of the numerous bugs
in it. So is their a bug report that contains all these bugs? If not then why?
Aside from the facts that numerous bugs are in it, how much pain did you have
to go through to think it was a good idea to remove it?

I tbh do not agree with the decision to outright remove a feature everyone uses
in kde4 and now Windows (yes kde5 is getting burned by windows, how sad is
that?).

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

[plasmashell] [Bug 358294] Windows just got the upper hand on kde5

[Michael Fox via KDE Bugzilla]

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

--- Comment #3 from Michael Fox  ---
Oh and then even worse. "Walk through Desktop list" and "Walk Through Desktops"
DO THE EXACT SAME THING?!!

Walk Through Desktops should be the overlay if anything. But at the same time,
WTF drugs were you guys on to make the same function with 2 different names?

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

[drkonqi] [Bug 356722] Useless dialog after "Suggest this crash is related" button pressing

[Werner Lemberg via KDE Bugzilla]

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

Werner Lemberg  changed:

   What|Removed |Added

 CC||w...@gnu.org

--- Comment #1 from Werner Lemberg  ---
I get the same with KDE Frameworks 5.16.0 and Qt 5.5.1 on an openSuSE Leap 42.1
x86_64 box.

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[AJslye via KDE Bugzilla]

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

--- Comment #20 from AJslye  ---
 I'll need to test some more, but today's update in Arch to plasma-framework
5.18.0-2 seems to have fixed this issue. I wonder what they patched or back
ported?

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

[kdenlive] [Bug 358177] Kdenlive-git - Issue with Wipe transition, not working properly. (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #6 from Jesse  ---
Will do. Thanks for looking into it JB!

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

[Baloo] [Bug 358258] Baloo indexing crash

[Werner Lemberg via KDE Bugzilla]

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

Werner Lemberg  changed:

   What|Removed |Added

 CC||w...@gnu.org

--- Comment #1 from Werner Lemberg  ---
[KDE Frameworks 5.16.0, Qt 5.5.1, xcb windowing system]
[openSuSE Leap 42.1]

Well, the Crash Reporting Assistant doesn't handle the `Suggest this crash is
related' button (which is another bug), so I just wanted to say that I get the
same crash every time after KDE is started, without doing something special.

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Raúl Arellano via KDE Bugzilla]

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

--- Comment #21 from Raúl Arellano  ---
(In reply to AJslye from comment #20)
>  I'll need to test some more, but today's update in Arch to plasma-framework
> 5.18.0-2 seems to have fixed this issue. I wonder what they patched or back
> ported?

Did they updated something? I've been up to 3 days without an issue

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

[plasmashell] [Bug 358294] Windows just got the upper hand on kde5

[Michael Fox via KDE Bugzilla]

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

--- Comment #5 from Michael Fox  ---
Here is a screenshot so you can better understand.
http://az648995.vo.msecnd.net/win/2015/04/Clip3.gif
Which btw came from here
https://blogs.windows.com/windowsexperience/2015/04/16/virtual-desktops-in-windows-10-the-power-of-windowsmultiplied/

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

[valgrind] [Bug 356393] valgrind (vex) crashes because isZeroU happened

[Ankur Srivastava via KDE Bugzilla]

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

Ankur Srivastava  changed:

   What|Removed |Added

 CC||ankur...@gmail.com

--- Comment #2 from Ankur Srivastava  ---
I get a similar crash on Arch. valgrind 3.11

==26955==at 0x5EAAF40: ecp_nistz256_avx2_select_w7 (in
/usr/lib/libcrypto.so.1.0.0)
==26955==by 0x5E7A5CF: EC_POINT_mul (in /usr/lib/libcrypto.so.1.0.0)
==26955==by 0x5E79416: EC_POINT_new (in /usr/lib/libcrypto.so.1.0.0)
==26955==by 0x5E82E89: EC_KEY_generate_key (in /usr/lib/libcrypto.so.1.0.0)
==26955==by 0x78092A4: ssl3_send_client_key_exchange (in
/usr/lib/libssl.so.1.0.0)
==26955==by 0x780CF67: ssl3_connect (in /usr/lib/libssl.so.1.0.0)
==26955==by 0x7817E9B: ssl23_connect (in /usr/lib/libssl.so.1.0.0)
==26955==by 0x6265A03: ??? (in /usr/lib/libcurl.so.4.4.0)
==26955==by 0x6265FB9: ??? (in /usr/lib/libcurl.so.4.4.0)
==26955==by 0x626967F: ??? (in /usr/lib/libcurl.so.4.4.0)
==26955==by 0x622276D: ??? (in /usr/lib/libcurl.so.4.4.0)
==26955==by 0x6248535: ??? (in /usr/lib/libcurl.so.4.4.0)
==26955==by 0x624915C: curl_multi_perform (in /usr/lib/libcurl.so.4.4.0)
==26955==by 0x623FBFA: curl_easy_perform (in /usr/lib/libcurl.so.4.4.0)

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

[dolphin] [Bug 358292] New: Dolphin has non-relevant context menus for KIO Slave locations

[arnav dhamija via KDE Bugzilla]

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

Bug ID: 358292
   Summary: Dolphin has non-relevant context menus for KIO Slave
locations
   Product: dolphin
   Version: 15.08.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: panels: places
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: arnav.dham...@gmail.com

For example, when I access the bluetooth:/ directory in Dolphin, the context
menu in the view shows options for pasting the clipboard contents and for
copying the Send Files option. Such context menus are used for file management,
but they do not make sense in some KIO Slave locations such as this one.

A screenshot showing this can be seen here: http://i.imgur.com/7wEKqB8.jpg?1

Reproducible: Always

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[AJslye via KDE Bugzilla]

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

--- Comment #22 from AJslye  ---
Yes, Arch had a revision 5.18.0-2 update of Plasma-framworks today (2016-01-20)
https://www.archlinux.org/packages/?sort==plasma-framework==

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

[plasmashell] [Bug 358291] Kicker applications model is incomplete (missing entries)

[Pulfer via KDE Bugzilla]

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

--- Comment #1 from Pulfer  ---
Created attachment 96761
  --> https://bugs.kde.org/attachment.cgi?id=96761=edit
Missing separator and "Install & Remove Software" application entry

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

[ark] [Bug 348923] ark crashes on closing if okular is launched by clicking any pdf file residing insode an archive

[Kunal Katyayan via KDE Bugzilla]

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

--- Comment #9 from Kunal Katyayan  ---
I searched my old laptop for the file but did not find it.
Tried repro with few other files but failed.
-Kunal.

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

[plasmashell] [Bug 358294] Windows just got the upper hand on kde5

[Michael Fox via KDE Bugzilla]

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

Michael Fox  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

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

[plasmashell] [Bug 358294] New: Windows just got the upper hand on kde5

[Michael Fox via KDE Bugzilla]

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

Bug ID: 358294
   Summary: Windows just got the upper hand on kde5
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: kamijoutouma...@gmail.com

You know what is extremely sad.
Windows 10 has Virtual Desktops. Guess what it was inspired by. KDE4.
http://itsfoss.com/windows-10-inspired-linux/

And whats even worse is that people on Windows also love this feature. I have
Windows 10 on one hard drive and arch linux on another with KDE4. 

I upgraded to KDE5 because of a feature that was in 5 that i wanted. I saw that
Virtual Desktops was pretty much broken and instantly reverted to KDE4. BTW
that feature that was in KDE5 that i wanted i can't even remember because of
the nightmare that is KDE5 due to the fact it has busted Virtual Desktops and
your telling us to use activities (which even i hate so much i wish it died).

Literally KDE5 just made linux worse than windows even though windows copied
off its predicesor KDE4.

Reproducible: Always

Steps to Reproduce:
1.Set a wallpaper on a desktop / set a new widget on the desktop / try to drag
an application to another desktop
2.Switch a another desktop 
3.Set a wallpaper on a desktop / set a new widget on the desktop / try to drag
an application to another desktop

Actual Results:  
Wallpaper changes for all desktops / widget is set on all desktops / cant drag
an application to another desktop

Expected Results:  
Wallpaper changes for one desktop / widget is set on one desktop / can drag an
application to another desktop

This crap actually made me do 'sudo rm -r /' and reinstall arch linux from
scratch and KDE4 thats how much i hated KDE5.

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

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

[via KDE Bugzilla]

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

shining.sc...@gmail.com changed:

   What|Removed |Added

 CC||shining.sc...@gmail.com

--- Comment #37 from shining.sc...@gmail.com ---
I have this issue too on a dual-screen NVIDIA setup, Archlinux, KF 5.18.0.

I don't know if it's related but everytime I close a window I get a lot of
these lines in journalctl :

> kscreen_backend_launcher[513]: kscreen: Primary output changed from 
> KScreen::Output(Id: 654 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to 
> KScreen::Output(Id: 654 , Name: "DVI-I-1" ) ( "DVI-I-1" )

followed by 

> kscreen.kded: Change detected
> kscreen.kded: Saving current config to file
> ...

Despite that nothing changed, and this happens everytime I close a window.
So I wonder if that's why the config gets messed up at some point.

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

[KScreen] [Bug 355928] kscreen reports change of primary screen without apparent reason

[via KDE Bugzilla]

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

shining.sc...@gmail.com changed:

   What|Removed |Added

 CC||shining.sc...@gmail.com

--- Comment #9 from shining.sc...@gmail.com ---
Same here, NVIDIA dual head, Archlinux, KF 5.18, latest Plasma.

It seems that it triggers everytime I close a window.

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

[plasmashell] [Bug 358294] Windows just got the upper hand on kde5

[Michael Fox via KDE Bugzilla]

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

--- Comment #4 from Michael Fox  ---
By overlay i mean a big ass pager overlay that actually shows minified versions
of the apps in the desktops instead of illegible boxes that you have no idea
which app is which.

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

[Phonon] [Bug 357229] amarok: skips track, jumps to middle of next track, when switching to next song in playlist

[Florian Lindner via KDE Bugzilla]

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

--- Comment #14 from Florian Lindner  ---
It was all FLAC and the artist name (also contained in the filename) was
Downset.

Downset - 11 - Sangre De Mis Manos was played successfully, the next track,
Downset - 12 - Horrifying started from the middle.

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

[drkonqi] [Bug 356722] Useless dialog after "Suggest this crash is related" button pressing

[via KDE Bugzilla]

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

--- Comment #2 from opensuse.lietuviu.ka...@gmail.com ---
Bug still in recent KDE Frameworks 18.0 + KDE Applications 15.12.1 + KDE Plasma
5.5.3

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

[plasmashell] [Bug 358295] New: Plasma crashes on hovering / clicking of windows in the panel (wayland)

[via KDE Bugzilla]

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

Bug ID: 358295
   Summary: Plasma crashes on hovering / clicking of windows in
the panel (wayland)
   Product: plasmashell
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: cobe...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
Hover over window items in the windowswither(?) or clicking windows.
Plasma will then very often crash.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7feaa6dc88c0 (LWP 3817))]

Thread 15 (Thread 0x7fea91de5700 (LWP 3820)):
#0  0x7feaa034e24d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fea9ca43264 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fea9ca4336c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7feaa0c6452b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7feaa0c0e63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7feaa0a3ab1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7feaa0a3f94f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fea9fb554a4 in start_thread (arg=0x7fea91de5700) at
pthread_create.c:334
#8  0x7feaa0356bdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fea8b1db700 (LWP 3827)):
#0  0x7ffd75919c9f in clock_gettime ()
#1  0x7feaa03637d6 in __GI___clock_gettime (clock_id=1, tp=0x7fea8b1daaa0)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7feaa0aeb1a6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7feaa0c620e9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7feaa0c625f5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7feaa0c6398e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fea9ca4288d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fea9ca43193 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fea9ca4336c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7feaa0c6452b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7feaa0c0e63a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7feaa0a3ab1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7feaa3d079a5 in  () at /usr/lib64/libQt5Qml.so.5
#13 0x7feaa0a3f94f in  () at /usr/lib64/libQt5Core.so.5
#14 0x7fea9fb554a4 in start_thread (arg=0x7fea8b1db700) at
pthread_create.c:334
#15 0x7feaa0356bdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fea7cf16700 (LWP 3828)):
#0  0x7fea9fb5b07f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fea839900b3 in thread_function (mtx=0xfcbfd0, cond=0xfcbff8) at
../../../../include/c11/threads_posix.h:159
#2  0x7fea839900b3 in thread_function (sema=0xfcbfd0) at
../../../../src/gallium/auxiliary/os/os_thread.h:259
#3  0x7fea839900b3 in thread_function (init_data=init_data@entry=0xfcbf28)
at lp_rast.c:805
#4  0x7fea8398ff37 in impl_thrd_routine (p=) at
../../../../include/c11/threads_posix.h:87
#5  0x7fea9fb554a4 in start_thread (arg=0x7fea7cf16700) at
pthread_create.c:334
#6  0x7feaa0356bdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fea7c715700 (LWP 3829)):
#0  0x7fea9fb5b07f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fea839900b3 in thread_function (mtx=0xfcc138, cond=0xfcc160) at
../../../../include/c11/threads_posix.h:159
#2  0x7fea839900b3 in thread_function (sema=0xfcc138) at
../../../../src/gallium/auxiliary/os/os_thread.h:259
#3  0x7fea839900b3 in thread_function (init_data=init_data@entry=0xfcc090)
at lp_rast.c:805
#4  0x7fea8398ff37 in impl_thrd_routine (p=) at
../../../../include/c11/threads_posix.h:87
#5  0x7fea9fb554a4 in start_thread (arg=0x7fea7c715700) at
pthread_create.c:334
#6  0x7feaa0356bdd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fea7bf14700 (LWP 3830)):
#0  0x7fea9fb5b07f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185

[kdevelop] [Bug 358296] New: Kdevelop crashes when trying to scp a file by rightclick --> run external script

[Michael Brown via KDE Bugzilla]

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

Bug ID: 358296
   Summary: Kdevelop crashes when trying to scp a file by
rightclick --> run  external script
   Product: kdevelop
   Version: 4.7.1
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: produ...@holotronic.dk

Application: kdevelop (4.7.1)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.3.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
I'm running mostly kde5 plasma desktop with sddm manager login. Had to install
MATE desktop to get desktop to run. This Problem seemed to appear after having
run Caja filemananger (Gnome app ?). Running Ghex has also given som major
display problems and display flickering at shutdown / reboot.
Before latest updates sddm display manager has high probability of crashing
trying to combine a workflow with kdevelop, dolphin (rightclick compress),
konqueror(rightclick kdiff3) and caja(right click Rabbitvcs)...hmmm...

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff1bcb3c940 (LWP 2110))]

Thread 12 (Thread 0x7ff19f15f700 (LWP 2111)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff1b6de7d2a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7ff1b6de7d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7ff1b56fb284 in start_thread (arg=0x7ff19f15f700) at
pthread_create.c:333
#4  0x7ff1b922574d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7ff11da1f700 (LWP 2112)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7ff1b98d7394 in QWaitConditionPrivate::wait (time=1000,
this=0x3b525c0) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=this@entry=0x3b52e78,
mutex=mutex@entry=0x3b52e80, time=time@entry=1000) at
thread/qwaitcondition_unix.cpp:158
#3  0x7ff1b81e4f16 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x3b52e60) at
/build/kdevplatform-Y8NEm6/kdevplatform-1.7.1/language/duchain/duchain.cpp:283
#4  0x7ff1b98d6e4c in QThreadPrivate::start (arg=0x3b52e60) at
thread/qthread_unix.cpp:352
#5  0x7ff1b56fb284 in start_thread (arg=0x7ff11da1f700) at
pthread_create.c:333
#6  0x7ff1b922574d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7ff10f465700 (LWP 2113)):
#0  0x7ff1b921887d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff1b30ad510 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff1b3069cb4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff1b306a170 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff1b306a2dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff1b9a173a6 in QEventDispatcherGlib::processEvents
(this=0x7ff1080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#6  0x7ff1b99e52e1 in QEventLoop::processEvents
(this=this@entry=0x7ff10f464c90, flags=...) at kernel/qeventloop.cpp:149
#7  0x7ff1b99e5655 in QEventLoop::exec (this=this@entry=0x7ff10f464c90,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7ff1b98d4559 in QThread::exec (this=) at
thread/qthread.cpp:538
#9  0x7ff1b98d6e4c in QThreadPrivate::start (arg=0x43bd458) at
thread/qthread_unix.cpp:352
#10 0x7ff1b56fb284 in start_thread (arg=0x7ff10f465700) at
pthread_create.c:333
#11 0x7ff1b922574d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7ff1068f6700 (LWP 2120)):
#0  0x7ff1b921c86d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff1b306a1cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff1b306a2dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff1b9a173a6 in QEventDispatcherGlib::processEvents
(this=0x7ff0fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x7ff1b99e52e1 in QEventLoop::processEvents
(this=this@entry=0x7ff1068f5c90, flags=...) at kernel/qeventloop.cpp:149
#5  0x7ff1b99e5655 in QEventLoop::exec (this=this@entry=0x7ff1068f5c90,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7ff1b98d4559 in QThread::exec (this=) at
thread/qthread.cpp:538
#7  0x7ff1b98d6e4c in QThreadPrivate::start (arg=0x4600c80) at
thread/qthread_unix.cpp:352
#8  0x7ff1b56fb284 in start_thread (arg=0x7ff1068f6700) at
pthread_create.c:333
#9  

[kdevelop] [Bug 358296] Kdevelop crashes when trying to scp a file by rightclick --> run external script

[Michael Brown via KDE Bugzilla]

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

--- Comment #1 from Michael Brown  ---
Well after my second reboot things worked normally again. 
As a side note I was logged in to the same external unit via minicom usb serial
konsole terminal + ssh -X login in different tab.
Logging in in same fashion does not retrigger the bug.
However I'm sure some problems will reappear once I start caja for github
access... or need ghex.

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

[ark] [Bug 348923] ark crashes on closing if okular is launched by clicking any pdf file residing insode an archive

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

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

--- Comment #10 from Elvis Angelaccio  ---
Thanks for checking :)

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

[plasmashell] [Bug 358026] plasma5 does not work over Xdmcp

[via KDE Bugzilla]

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

--- Comment #3 from hil...@mpia-hd.mpg.de ---
i have now remarked another thing:
When i log in locally on the computer, open some windows, like e.g. firefox,
kile, xterm and log out, these settings will be stored. This is normal deafult
behaviour of kde. When relogin these windows will popup automatically on kde
start.

When i come now remotely over Xdmcp, all these windows will popup as well on
startup.
And i can activate a window with the left mouse button.

But still the same behaviour: 
- Executable: plasmashell PID: 26872 Signal: Aborted (6)
- no panel bar
- mouse buttons on the desktop background remain inactive

Does this give somebody a clue?

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

[kmail2] [Bug 340014] kMail crashes when opening a new main window if the original (first) main window has been closed

[Gunter Ohrner via KDE Bugzilla]

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

Gunter Ohrner  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Gunter Ohrner  ---
The feature to be able to open multiple mail windows has simply been removed
from kMail to get rid of bugs like this...

So technically it's not fixed, but it also cannot be reproduced any more...

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

[kmail2] [Bug 290378] Wrong cursor position in editor window after switching sender identity.

[Gunter Ohrner via KDE Bugzilla]

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

Gunter Ohrner  changed:

   What|Removed |Added

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

--- Comment #1 from Gunter Ohrner  ---
Cannot be reproduced any more with kMail 5.0.3 under

KDE Frameworks 5.18.0
Qt 5.5.1 (kompiliert gegen 5.5.1)
Das xcb Fenstersystem

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

[plasmashell] [Bug 358026] plasma5 does not work over Xdmcp

[David Edmundson via KDE Bugzilla]

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

--- Comment #4 from David Edmundson  ---
Plasma shell requires opengl, the rest don't.

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

[kdevplatform] [Bug 358256] New: Un-intuitive git commit dialog when deselecting files

[via KDE Bugzilla]

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

Bug ID: 358256
   Summary: Un-intuitive git commit dialog when deselecting files
   Product: kdevplatform
   Version: 4.90.90
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: git
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: pej...@gmail.com

I have a directory with several modified files. I left-click on the directory
and select git->commit.
I enter a commit message and then un-selects some files that I don't want to
commit with this message.
Then a select commit.

Now I get a confirmation-dialog to commit ALL files, even the ones I
unselected.
If I select continue ALL files get commited.
If I select cancel I get a dialog to commit only the selected files, which is
what I want.

I have several times commited the wrong files due to this behaviour. Kdevelop 4
behaved correctly.

Reproducible: Always

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

[Oxygen] [Bug 358257] New: Please forward port the option "Outline active window title" from KDE4

[Jani-Matti Hätinen via KDE Bugzilla]

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

Bug ID: 358257
   Summary: Please forward port the option "Outline active window
title" from KDE4
   Product: Oxygen
   Version: 5.4.3
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: win deco
  Assignee: hugo.pere...@free.fr
  Reporter: jani-matti.hati...@iki.fi

The Oxygen window decoration in KDE5 has dropped the option "Outline active
window title". This option was absolutely crucial in terms of usability as it
made it trivial to instantly spot the active window even on multi-screen
setups. Currently on KDE5 this is nigh impossible.

Reproducible: Always

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

[Baloo] [Bug 358258] New: Baloo indexing crash

[Georges Sancosme via KDE Bugzilla]

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

Bug ID: 358258
   Summary: Baloo indexing crash
   Product: Baloo
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: geor...@sancosme.net
CC: pinak.ah...@gmail.com

Application: baloo_file (5.16.0)

Qt Version: 5.5.1
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
setting up ntp daemon
time synchronization
login in to owncloud

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc8f463c780 (LWP 1604))]

Thread 2 (Thread 0x7fc7a9675700 (LWP 1880)):
#0  0x7fc8eec13cf0 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc8eebd16a1 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc8eebd1dcf in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc8eebd1f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc8f2dbcd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fc8f2d63d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x00422845 in Baloo::FileContentIndexer::run() (this=0x218bf50) at
/usr/src/debug/baloo-5.16.0/src/file/filecontentindexer.cpp:71
#7  0x7fc8f2b87382 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc8f2b8a32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fc8f11cc0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fc8f219a04d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc8f463c780 (LWP 1604)):
[KCrash Handler]
#6  0x7fc8f2144e19 in __memcpy_sse2_unaligned () at /lib64/libc.so.6
#7  0x7fc8f3455995 in Baloo::IdTreeDB::get(unsigned long long) () at
/usr/lib64/libKF5BalooEngine.so.5
#8  0x7fc8f3452ca0 in Baloo::DocumentUrlDB::getId(unsigned long long,
QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5
#9  0x7fc8f34643e9 in Baloo::Transaction::documentId(QByteArray const&)
const () at /usr/lib64/libKF5BalooEngine.so.5
#10 0x0042a923 in
Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&)
(this=this@entry=0x213d760, tr=tr@entry=0x7ffcb15a3d00, url=...) at
/usr/src/debug/baloo-5.16.0/src/file/metadatamover.cpp:74
#11 0x0042a9dd in Baloo::MetadataMover::removeFileMetadata(QString
const&) (this=0x213d760, file=...) at
/usr/src/debug/baloo-5.16.0/src/file/metadatamover.cpp:66
#12 0x7fc8f2d9573f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#13 0x00434405 in Baloo::PendingFileQueue::removeFileIndex(QString
const&) (this=this@entry=0x21577e0, _t1=...) at
/usr/src/debug/baloo-5.16.0/build/src/file/moc_pendingfilequeue.cpp:217
#14 0x00428bc6 in Baloo::PendingFileQueue::processCache()
(this=0x21577e0) at
/usr/src/debug/baloo-5.16.0/src/file/pendingfilequeue.cpp:89
#15 0x7fc8f2d9573f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#16 0x7fc8f2da2f22 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#17 0x7fc8f2d968bc in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7fc8f2d6618d in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x7fc8f2d65e95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#20 0x7fc8f2dbc77d in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#21 0x7fc8f2dbcad9 in  () at /usr/lib64/libQt5Core.so.5
#22 0x7fc8eebd1c84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#23 0x7fc8eebd1ed8 in  () at /usr/lib64/libglib-2.0.so.0
#24 0x7fc8eebd1f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#25 0x7fc8f2dbcd6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#26 0x7fc8f2d63d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#27 0x7fc8f2d6b8f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#28 0x00417d92 in main(int, char**) (argc=1, argv=) at
/usr/src/debug/baloo-5.16.0/src/file/main.cpp:88

Possible duplicates by query: bug 357941, bug 357919, bug 355876, bug 355633,
bug 355371.

Reported using DrKonqi

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

[kdevplatform] [Bug 358256] Un-intuitive git commit dialog when deselecting files

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Kevin Funk  ---
Isn't that the same issue you reported earlier?
https://bugs.kde.org/show_bug.cgi?id=14

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

[kwin] [Bug 358259] New: Please bring back custom button spacing from KDE4

[Jani-Matti Hätinen via KDE Bugzilla]

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

Bug ID: 358259
   Summary: Please bring back custom button spacing from KDE4
   Product: kwin
   Version: 5.4.3
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jani-matti.hati...@iki.fi

With kwin/KDE5 it's no longer possible to customise the spacing between the
buttons in the window title. This used to be an excellent usability aid in KDE4
as it allowed one to clearly separate the window close button from the
maximise/minimise buttons and thus greatly reducing the chances of a mis-click.


Reproducible: Always

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

[Akonadi] [Bug 358267] New: Incoming mail moved to Trash immediately

[Arthur Schiwon via KDE Bugzilla]

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

Bug ID: 358267
   Summary: Incoming mail moved to Trash immediately
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: bli...@arthur-schiwon.de
CC: kdepim-b...@kde.org, vkra...@kde.org

Incoming email is was suddenly started to be moved to the trash. This happened
recently already, so I decided to setup a new Imap resource. All worked not
round but okish, until three days later I also found my incoming mails being
moved to trash. 

It happens with my corporate email account. That is served by a Kerio mail
server. The admin could confirm that my client was moving the mails to trash.

This first time it happened some time earlier in January. I did not have issues
like that before. Very likely it started after KDE Releases Frameworks 5.18.0
and KDE Releases Applications 15.12.1 releases.

Akonadi 5.1.51
Using KMail 5.5.1
I am using Antergos, it takes Akonadi etc. directly from Arch repositories.

Reproducible: Sometimes

Steps to Reproduce:
1. Configure an IMAP resource (against a Kerio mailserver)
2. Use it for couple of days
3. If you wonder why there are no new mail in your inbox, check trash

Actual Results:  
You will find unread emails in your trash that should be in Inbox instead

Expected Results:  
Email stay in Inbox

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

[skrooge] [Bug 358195] broken dependencies after KDE update

[Scarlett Clark via KDE Bugzilla]

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

Scarlett Clark  changed:

   What|Removed |Added

 CC||sgcl...@kubuntu.org

--- Comment #5 from Scarlett Clark  ---
Looks like timo-jyrinki uploaded new qt packages. Seems by the error this is
where you want to start looking.

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #4 from David Edmundson  ---
Tested here, I can't reproduce. 

That SDDM bug is tracked on another bug.

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

[kate] [Bug 357097] kate v.15.08.3 segfaults when saving a new file

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #5 from Weng Xuetian  ---
Git commit cda58f0e256d53e66ca44b77fa7307ee670b8313 by Weng Xuetian.
Committed on 20/01/2016 at 18:44.
Pushed by xuetianweng into branch 'master'.

remove the duplicate m_touchpadOffAtom member.

m_touchpadOffAtom is already in XlibTouchpad, which makes ctor of
SynapticsTouchpad initialize wrong atom.

M  +1-1kcms/touchpad/src/backends/x11/synapticstouchpad.h

http://commits.kde.org/plasma-desktop/cda58f0e256d53e66ca44b77fa7307ee670b8313

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #5 from Nils  ---
Created attachment 96755
  --> https://bugs.kde.org/attachment.cgi?id=96755=edit
Hacking KDE session locker by closing the lid several times

So here the full log about my successful KDE hacking by closing the lid. :)

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

[frameworks-modemmanager-qt] [Bug 358261] SMS messages list is not update when calling ModemManager::ModemMessaging::createMessage

[Lamarque V . Souza via KDE Bugzilla]

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

--- Comment #1 from Lamarque V. Souza  ---
Hi, MMQt API is assynchronous and MMQt needs to receive signals from
ModemManager to update the message list. That is probably not happening because
you are doing everything in synchronous mode. Try adding the line below after
*before* step 7 and check if your example works:

// Include QCoreApplication if compiler complains about qApp not defined.
qApp->processEvents();

That will make Qt process any pending event (like ModemManager's signal to
update the message list).

If that works then you need to update your code to work in asynchronous mode.
Using processEvent() must be avoided since it is a costly method call.

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

[frameworks-modemmanager-qt] [Bug 358261] SMS messages list is not update when calling ModemManager::ModemMessaging::createMessage

[Jan Grulich via KDE Bugzilla]

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

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com

--- Comment #4 from Jan Grulich  ---
Using signals and slots is the way how to use both MMQT and NMQT properly. Do
not pay attention that much to the example, I was lazy to write a proper one
and that one you see was created just as a testing code for sending sms.

If you want any help with MMQT API just contact us on
kde-hardware-de...@kde.org mailing list and we will be more than happy to help
you and don't worry about your english, most of us are not native speakers (I'm
from Czech Republic and Lamarque is from Brazil too).

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

[krita] [Bug 357796] Two clicks needed to open Edit Brush Settings if not closed with "X"

[Glenn S via KDE Bugzilla]

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

--- Comment #3 from Glenn S  ---
Above comment can be deleted. This was sent by email when I couldn't log in to
KDE. have now managed to get in...

My Brush Editor is NOT docked to the toolbar (is there a way to do that?) and
so it DOES have a Close button.
And, no, if I have the Editor open and then start to paint on the canvas the
Editor closes.


- I did later learn from Boudewijn in an email that the Brush Editor can be
docked and undocked and that it shouldn't be closing even if undocked. Adding
this here in case anyone else encounters similar problem.

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

[kdenlive] [Bug 358180] Kdenlive-git - Have "Wipe" effect start with the "Linear_x.png" image file? Should start as a "wipe" transition, not dissolve. Also consider changing "Image file" text in trans

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit f9e36da881f90a0bdb842f9edfa9bdbb99fcbc5c by Jean-Baptiste Mardelle.
Committed on 20/01/2016 at 18:32.
Pushed by mardelle into branch 'master'.

Use linear_x as default luma for wipe, rename "Image File" to "Wipe Method"

M  +8-5src/effectslist/initeffects.cpp

http://commits.kde.org/kdenlive/f9e36da881f90a0bdb842f9edfa9bdbb99fcbc5c

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

[umbrello] [Bug 358269] New: Impossible to change color of sequence diagram messages

[Ralf Habacker via KDE Bugzilla]

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

Bug ID: 358269
   Summary: Impossible to change color of sequence diagram
messages
   Product: umbrello
   Version: unspecified
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de

In sequence diagrams it is possible to change the color of objects, but not for
messages.

Reproducible: Always

Steps to Reproduce:
1. start umbrello
2. add a sequence diagram
3. add two objects and a message between them

Actual Results:  
There is no property dialog or context menu for changing the message line
color.


Expected Results:  
There should be a property dialog or context menu entry for changing the
message line color.

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

[umbrello] [Bug 358272] New: No color change for communication diagram messages possible

[Ralf Habacker via KDE Bugzilla]

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

Bug ID: 358272
   Summary: No color change for communication diagram messages
possible
   Product: umbrello
   Version: 2.18.0 (KDE Applications 15.12.0)
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de

For communication diagram messages there is a context menu entry to change the
line color, but a changed color is not applied to the message.

Reproducible: Always

Steps to Reproduce:
1. start umbrello
2. add a communication diagram
3. add two objects and a message
4. Select message and right click on 'line color' to change the color
5. enter a different color
6. press ok 


Actual Results:  
The color of the message does not change.


Expected Results:  
The color should be applied to the message widget.

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

[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC|hugo.pere...@free.fr|

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

[plasmashell] [Bug 358262] New: time dataEngine has empty Local source

[abulak via KDE Bugzilla]

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

Bug ID: 358262
   Summary: time dataEngine has empty Local source
   Product: plasmashell
   Version: 5.5.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: DataEngines
  Assignee: plasma-b...@kde.org
  Reporter: abu...@gmail.com

This results in no clock shown in sddm and default plasma clock.

I have no idea how to debug it;
using systemd;

timedatectl:
  Local time: Wed 2016-01-20 16:43:37 CET
  Universal time: Wed 2016-01-20 15:43:37 UTC
RTC time: Wed 2016-01-20 15:43:37
   Time zone: Europe/Warsaw (CET, +0100)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

/etc/localtime points where it should (/usr/share/zoneinfo/Europe/Warsaw

Reproducible: Always

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

[Breeze] [Bug 357587] The new selection marker is hard to notice

[miklos via KDE Bugzilla]

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

--- Comment #3 from miklos  ---
(In reply to andreas from comment #2)
> hi miklos this is not a breeze issue it's an breeze design guideline. all
> icons use a 1px thin line. for dolphin it would be possible to use emblem
> icons they are designed for overlay stuff.

It's not an icon, it's a control. Controls need to be easily visible (well, so
do icons...). Just take a look at the folder view plasmoid to see how it's done
right.

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[Raúl Arellano via KDE Bugzilla]

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

--- Comment #17 from Raúl Arellano  ---
Note that this is not happening in ALL intel graphics (i have a netbook with an
intel atom / gma950 i think)

@David Edmundson .. I think so, Now I realize that I always have that
Xorg.0.log in /var/log even when it does not happens (i changed sddm theme a
couple days ago and still have same error with todays date)

In the test, i login with no error but nothings happens. here's the output

raul ~ $ sddm-greeter --theme /usr/share/sddm/themes/breeze/ --test-mode
[12:06:05.242] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop"
[12:06:05.243] (II) GREETER: Reading from
"/usr/share/wayland-sessions/plasmawayland.desktop"
[12:06:05.243] (EE) GREETER: Socket error:  "QLocalSocket::connectToServer:
Invalid name"
[12:06:06.134] (II) GREETER: Adding view for "VGA1" QRect(0,0 1920x1080)
[12:06:06.391] (II) GREETER: Overwriting existing old cached entry due to
collision.
[12:06:08.459] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop"
[12:06:08.459] (WW) GREETER: QIODevice::write (QLocalSocket): device not open
^C
raul ~ $ sudo sddm-greeter --theme /usr/share/sddm/themes/breeze/ --test-mode
Contraseña: 

Put my password (i don't have more users), hit enter, login button and password
textbox sets to gray, and nothing happens

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

[frameworks-modemmanager-qt] [Bug 358261] SMS messages list is not update when calling ModemManager::ModemMessaging::createMessage

[Daniel via KDE Bugzilla]

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

--- Comment #3 from Daniel  ---
Adding 

qApp->processEvents();
qApp->processEvents();

instead of just one, make the things work.

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

[systemsettings] [Bug 358171] Breeze theme breaks sddm - login screen presented three times

[soee via KDE Bugzilla]

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

soee  changed:

   What|Removed |Added

 CC||kont...@soee.pl

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

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

[gene smith via KDE Bugzilla]

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

--- Comment #36 from gene smith  ---
(In reply to Dmitry from comment #29)
> (In reply to gene smith from comment #28)
> > Well, guess I spoke too soon. Today the problem happened again on KDE
> > startup. Will try it set to run script on "Pre-KDE startup" for a while and
> > see if that makes a difference.
> 
> You'right it should start as soon as possible. Also it's better to disable
> kscreen daemon in kde system settings / startup / services.

Have been running the autostart script with "Pre-KDE startup" and with KScreen2
turned off since my previous comment and have seen no problems with screen
configuration.

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

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

[Jan via KDE Bugzilla]

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

--- Comment #17 from Jan  ---
This is still present:
Akonadi 5.0.51
kmail2 5.0.3

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

[ark] [Bug 341187] Crash closing embedded ark [in Ark::Part::~Part]

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||k...@opensource.sf-tec.de

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

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

[ark] [Bug 346667] Crash when closing archive in archive while it is still extracting

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Elvis Angelaccio  ---


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

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

[kscreenlocker] [Bug 358125] the lock-up can be pass through without typing password

[Nils via KDE Bugzilla]

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

--- Comment #6 from Nils  ---
@David Edmundson, 

So I have tested it again on my updated computer and it has not been long
before I have been successfully logged in as root on my computer without typing
any password by just closing the lid several times. 
The people outside looked me like I was crazy. :D

Cheers,

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

[dolphin] [Bug 354868] Odd behavior with dark color themes, jarring alternating row colors, hard to see text.

[Eric Francis via KDE Bugzilla]

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

Eric Francis  changed:

   What|Removed |Added

 CC||aird...@gmail.com

--- Comment #1 from Eric Francis  ---
You may need to close and reopen dolphin (all instances?) for the change to
fully take effect.
You might also check in the Colors tab in the Colors settings page, in Color
set: View, what the Normal Background and Alternate Background are set to. 
They should be similar colors 

I'm using KDE 4.14.13 and while I observe that dolphin doesn't always update
all of the rows immediately when changing the color scheme, after closing and
reopening it, all of the rows do update.

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

[kresources] [Bug 266378] Sogo: "Unable to retrieve items"

[Arthur Schiwon via KDE Bugzilla]

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

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

--- Comment #4 from Arthur Schiwon  ---
I have not seen this for quite a while now.

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

[Akonadi] [Bug 289097] error "Unable to fetch item from backend" when entering IMAP folder

[Arthur Schiwon via KDE Bugzilla]

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

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

--- Comment #81 from Arthur Schiwon  ---
I have not seen this for quite some time now. Probably fixed meanwhile, as
suggested by Dimitrios. Close?

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

[kdevelop] [Bug 358270] New: KDevelop crashed openning a project with css

[Edward Kigwana via KDE Bugzilla]

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

Bug ID: 358270
   Summary: KDevelop crashed openning a project with css
   Product: kdevelop
   Version: 4.90.90
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: edwardw...@gmail.com

Application: kdevelop (4.90.90)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.3.3 x86_64
Distribution (Platform): Gentoo Packages

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

Opening a session. Parsing project triggers crash.

I had https://github.com/nwjs/nw.js.git as a cmake external project. So just
clone it into any project's build dir or src such that the css parser gets
tasked to parse it  and thats it. There is no way to recover without moving the
cloned folder ot of the project.

kdevplatform: 55a80426005d6b9d8949209dd1009333b96cc843
kdevelop: 6be8bc2a3f5b1a7836685ea53b751e6db285fb5c
kdev-css: 375248c99c1179937dbf5a8a119504a456e84c41

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f8e62207800 (LWP 26621))]

Thread 17 (Thread 0x7f8e60c01700 (LWP 26622)):
#0  0x7f8e7abe63ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8e6f52aac2 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7f8e6f52c72f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f8e62110cb9 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f8e7b2c3ed2 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f8e74582444 in start_thread (arg=0x7f8e60c01700) at
pthread_create.c:334
#6  0x7f8e7abef36d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7f8e525d0700 (LWP 26623)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8e5b5e4373 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f8e5b5e3ac7 in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f8e74582444 in start_thread (arg=0x7f8e525d0700) at
pthread_create.c:334
#4  0x7f8e7abef36d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f8e47203700 (LWP 26626)):
#0  pthread_cond_timedwait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f8e7b2c4518 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f8e78d063c8 in KDevelop::DUChainPrivate::CleanupThread::run() ()
from /usr/lib64/libKDevPlatformLanguage.so.10
#3  0x7f8e7b2c3ed2 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f8e74582444 in start_thread (arg=0x7f8e47203700) at
pthread_create.c:334
#5  0x7f8e7abef36d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f8e44db2700 (LWP 26627)):
#0  0x7f8e7abe63ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8e73bdaeec in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f8e73bdaffc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8e7b4bbd5c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f8e7b46d90a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f8e7b2bf524 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f8e7b2c3ed2 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f8e74582444 in start_thread (arg=0x7f8e44db2700) at
pthread_create.c:334
#8  0x7f8e7abef36d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f8e3bfff700 (LWP 26629)):
#0  pthread_cond_timedwait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f8e7b2c4518 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f8e7b2c1354 in QThreadPoolThread::run() () from
/usr/lib64/libQt5Core.so.5
#3  0x7f8e7b2c3ed2 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#4  0x7f8e74582444 in start_thread (arg=0x7f8e3bfff700) at
pthread_create.c:334
#5  0x7f8e7abef36d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f8e2e1bb700 (LWP 26646)):
#0  0x7f8e7b4ba171 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#1  0x7f8e7b4ba565 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib64/libQt5Core.so.5
#2  0x7f8e7b4bb8ac in timerSourcePrepareHelper(GTimerSource*, int*) () from

[Breeze] [Bug 358271] New: Some selectboxes are missing shadows and are hard to click

[Märt Rang via KDE Bugzilla]

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

Bug ID: 358271
   Summary: Some selectboxes are missing shadows and are hard to
click
   Product: Breeze
   Version: 5.5.3
  Platform: Kubuntu Packages
   URL: https://i.gyazo.com/126227833d24ca6331864e8b09a99be3.p
ng
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: rang...@gmail.com

Some selectboxes are behaving weird, they are missing shadows (as seen on
provided url) and if I click to open them, they don't want to stay open (they
open and close instantly). These issues are seen mostly on audio profile
selection and on desktop settings layout selection. Was a problem on earlier
release too.

Reproducible: Always

Steps to Reproduce:
1. Open audio volume settings
2. Select Configuration tab
3. Try to change Profile

Actual Results:  
Selectbox closes instantly. After several clicks, it is displayed normally. If
I hold mouse button down, then it is possible to select an item. Shadow is
missing too.

Expected Results:  
It should act identically to other selectboxes on the system.

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

[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

[gene smith via KDE Bugzilla]

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

gene smith  changed:

   What|Removed |Added

 CC||g...@chartertn.net

--- Comment #12 from gene smith  ---
Created attachment 96756
  --> https://bugs.kde.org/attachment.cgi?id=96756=edit
1st konsole bad (contains background image), subsequent konsoles OK

Just noticed this happening recently. Only on secondary monitor, 1st konsole
instance is bad and then subsequent konsole instances are OK. But no problems
with konsole if 1st instance appears on the "primary" monitor (monitor
containing the panel at the bottom).
Just an additional confirmation of the bug.

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

[kdevplatform] [Bug 358256] Un-intuitive git commit dialog when deselecting files

[via KDE Bugzilla]

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

--- Comment #2 from pej...@gmail.com ---
Yes it is. I missed i reported it earlier. Still annoying.
Den 20 jan 2016 16:07 skrev "Kevin Funk via KDE Bugzilla" <
bugzilla_nore...@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=358256
>
> Kevin Funk  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |WAITINGFORINFO
>  Status|UNCONFIRMED |NEEDSINFO
>
> --- Comment #1 from Kevin Funk  ---
> Isn't that the same issue you reported earlier?
> https://bugs.kde.org/show_bug.cgi?id=14
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[frameworks-modemmanager-qt] [Bug 358261] New: SMS messages list is not update when calling ModemManager::ModemMessaging::createMessage

[Daniel via KDE Bugzilla]

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

Bug ID: 358261
   Summary: SMS messages list is not update when calling
ModemManager::ModemMessaging::createMessage
   Product: frameworks-modemmanager-qt
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: daniel...@gmail.com
CC: lamar...@kde.org, lukas.ti...@merlin.cz

In order to send SMS using the modemmanagerqt api it is necessary to first
create a message, after that find that message in SMS list and then send.

After creating a message using QDBusPendingReply
ModemManager::ModemMessaging::createMessage(const Message ) the message
list accessible from ModemManager::Sms::List
ModemManager::ModemMessaging::messages() is not modified and didn't contains
the new message recently created.

Reproducible: Always

Steps to Reproduce:
1. Get a valid instance of a ModemDevice: ModemManager::ModemDevice::Ptr
modemdevice;
2. Get the messaging interface: ModemManager::ModemMessaging::Ptr messaging =
modemdevice->messagingInterface();
3. Create a valid message: ModemManager::ModemMessaging::Message msg;
msg.number = "validnumber";
msg.text = "Hello World!";
4. Try to create a message: QDBusPendingReply sms =
messaging->createMessage(msg);
5. Wait for pending reply: sms.waitForFinished();
6. Check the validity of the reply: if ( sms.isValid() )
7. Iterate over the list of valid sms messages: ModemManager::Sms::List
messages = messaging->messages();
Q_FOREACH (ModemManager::Sms::Ptr sms, messages) {
qDebug() << "   " << sms->number() << sms->text() << sms->uni();
}
8. The new created message will not present in the list.

Actual Results:  
The new created message will not present in the list.

Expected Results:  
The new created message will present in the list.

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

[Breeze] [Bug 357587] The new selection marker is hard to notice

[andreas via KDE Bugzilla]

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

--- Comment #4 from andreas  ---
As I work for breeze and oxygen I can offer you this solution. Please change
the icon name to emblem-add and emblem-remove. I will push the icons in
breeze-icons and oxygen-icons.

thanks

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

[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.0.0
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #36 from Kevin Funk  ---
This is fixed by:

commit 14df9ba1a88e41193bf65f9d87f2849747f664b3
Author: Kevin Funk 
Date:   Wed Jan 20 09:25:18 2016 +0100

TopContextDynamicData: Fix bug in loadPartialData

Detected using ASAN

Regression introduced by 49e4b656f0e54bff882f03efe04feedff5994ed1

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

[drkonqi] [Bug 358260] New: Drkonqi crashed during bugreport filling process

[Germano Massullo via KDE Bugzilla]

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

Bug ID: 358260
   Summary: Drkonqi crashed during bugreport filling process
   Product: drkonqi
   Version: 5.5.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: germano.massu...@gmail.com

Drkonqi crashed while I was reporting a Plasma crash
Hereunder the backtrace

Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f04c4ac38c0 (LWP 24583))]

Thread 2 (Thread 0x7f04ab446700 (LWP 24584)):
#0  0x7f04bfc6afdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f04ba667272 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f04ab445c00) at /usr/include/bits/poll2.h:46
#2  0x7f04ba667272 in _xcb_conn_wait (c=c@entry=0x55f812268b60,
cond=cond@entry=0x55f812268ba0, vector=vector@entry=0x0, count=count@entry=0x0)
at xcb_conn.c:459
#3  0x7f04ba668ee7 in xcb_wait_for_event (c=0x55f812268b60) at xcb_in.c:693
#4  0x7f04ade18da9 in QXcbEventReader::run() (this=0x55f81227bb90) at
qxcbconnection.cpp:1255
#5  0x7f04c08733de in QThreadPrivate::start(void*) (arg=0x55f81227bb90) at
thread/qthread_unix.cpp:331
#6  0x7f04be42660a in start_thread (arg=0x7f04ab446700) at
pthread_create.c:334
#7  0x7f04bfc76a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f04c4ac38c0 (LWP 24583)):
[KCrash Handler]
#6  0x7f04c2306f11 in
QDBusAbstractInterface::asyncCallWithArgumentList(QString const&,
QList const&) (this=) at
../../src/corelib/tools/qscopedpointer.h:135
#7  0x7f04c2306f11 in
QDBusAbstractInterface::asyncCallWithArgumentList(QString const&,
QList const&) (p=...) at ../../src/corelib/global/qglobal.h:983
#8  0x7f04c2306f11 in
QDBusAbstractInterface::asyncCallWithArgumentList(QString const&,
QList const&) (this=) at qdbusabstractinterface.h:148
#9  0x7f04c2306f11 in
QDBusAbstractInterface::asyncCallWithArgumentList(QString const&,
QList const&) (this=0x0, method=..., args=...) at
qdbusabstractinterface.cpp:502
#10 0x7f04c35b29c4 in KWallet::Wallet::isOpen(QString const&) (wallet=...,
this=) at
/usr/src/debug/kwallet-5.18.0/x86_64-redhat-linux-gnu/src/api/KWallet/kwallet_interface.h:146
#11 0x7f04c35b29c4 in KWallet::Wallet::isOpen(QString const&) (name=...) at
/usr/src/debug/kwallet-5.18.0/src/api/KWallet/kwallet.cpp:366
#12 0x55f811d873be in BugzillaLoginPage::openWallet()
(this=this@entry=0x55f81260e610) at
/usr/src/debug/plasma-workspace-5.5.3/drkonqi/bugzillaintegration/reportassistantpages_bugzilla.cpp:177
#13 0x55f811d8a39a in BugzillaLoginPage::walletLogin()
(this=0x55f81260e610) at
/usr/src/debug/plasma-workspace-5.5.3/drkonqi/bugzillaintegration/reportassistantpages_bugzilla.cpp:187
#14 0x7f04c0a8f888 in QSingleShotTimer::timerEvent(QTimerEvent*)
(a=0x7ffefcacebd0, r=, this=) at
../../src/corelib/kernel/qobject_impl.h:124
#15 0x7f04c0a8f888 in QSingleShotTimer::timerEvent(QTimerEvent*)
(this=0x55f8127ada50) at kernel/qtimer.cpp:315
#16 0x7f04c0a84113 in QObject::event(QEvent*) (this=0x55f8127ada50,
e=) at kernel/qobject.cpp:1261
#17 0x7f04c173941c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55f812259bc0, receiver=receiver@entry=0x55f8127ada50,
e=e@entry=0x7ffefcaceeb0) at kernel/qapplication.cpp:3716
#18 0x7f04c173e8e6 in QApplication::notify(QObject*, QEvent*)
(this=0x7ffefcacf2f0, receiver=0x55f8127ada50, e=0x7ffefcaceeb0) at
kernel/qapplication.cpp:3499
#19 0x7f04c0a5473b in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=0x7ffefcacf2f0, receiver=0x55f8127ada50,
event=event@entry=0x7ffefcaceeb0) at kernel/qcoreapplication.cpp:965
#20 0x7f04c0aa9ccd in QTimerInfoList::activateTimers()
(event=0x7ffefcaceeb0, receiver=) at
../../src/corelib/kernel/qcoreapplication.h:224
#21 0x7f04c0aa9ccd in QTimerInfoList::activateTimers()
(this=0x55f8122c2270) at kernel/qtimerinfo_unix.cpp:637
#22 0x7f04c0aaa1d1 in timerSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at kernel/qeventdispatcher_glib.cpp:177
#23 0x7f04bd9f5e3a in g_main_context_dispatch (context=0x7f04a40016f0) at
gmain.c:3154
#24 0x7f04bd9f5e3a in g_main_context_dispatch
(context=context@entry=0x7f04a40016f0) at gmain.c:3769
#25 0x7f04bd9f61d0 in g_main_context_iterate
(context=context@entry=0x7f04a40016f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3840
#26 0x7f04bd9f627c in g_main_context_iteration (context=0x7f04a40016f0,
may_block=may_block@entry=1) at gmain.c:3901
#27 0x7f04c0aaaecb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55f812259600, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#28 

[plasmashell] [Bug 358264] New: Network monitor sometimes swaps colors for uplink/downlink

[miklos via KDE Bugzilla]

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

Bug ID: 358264
   Summary: Network monitor sometimes swaps colors for
uplink/downlink
   Product: plasmashell
   Version: 5.4.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Monitor
  Assignee: notm...@gmail.com
  Reporter: mtm...@freemail.hu

Normally the green bar is for uplink and the blue on top of it is for downlink,
but I noticed that sometimes their roles are swapped for a short duration. It
usually does this when there is a burst of high uplink traffic, and next time
there is traffic, it's normal again. If I have multiple network monitor applets
running, they all do this together.

Reproducible: Always

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

[kdevplatform] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]

[Kevin Funk via KDE Bugzilla]

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

--- Comment #37 from Kevin Funk  ---
Backported to 1.7 branch; will be part of 1.7.3.

commit c8fa1a6ba1f2226918597df091060b1c205f1a4f
Author: Kevin Funk 
Date:   Wed Jan 20 09:25:18 2016 +0100

TopContextDynamicData: Fix bug in loadPartialData

Detected using ASAN

Regression introduced by 49e4b656f0e54bff882f03efe04feedff5994ed1

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

[krita] [Bug 357796] Two clicks needed to open Edit Brush Settings if not closed with "X"

[Glenn S via KDE Bugzilla]

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

--- Comment #2 from Glenn S  ---
I am unable to respond to this. My login to KDE is not being accepted - despite
the fact I KNOW I am entering correct login. When attempting to reset password
I am NOT being sent the reset email!!
 Glenn Slingsby
www.thirddimensionjewellery.com  

On Wednesday, January 20, 2016 6:33 AM, Boudewijn Rempt via KDE Bugzilla
 wrote:


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

Boudewijn Rempt  changed:

          What    |Removed                    |Added

                CC|                            |b...@valdyas.org

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

I'm not sure I've understood the report correctly. Here, 

* I don't have a close button on the brush editor if it's attached to the
toolbar
* if it's detached, it doesn't hide on painting, but stays on top.

So I'm a bit puzzled.

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

[kwin] [Bug 358259] Please bring back custom button spacing from KDE4

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---


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

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

[kwin] [Bug 348393] Style -> Win Deco: No option to add 'Spacer' to Title Bar

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||jani-matti.hati...@iki.fi

--- Comment #2 from Thomas Lübking  ---
*** Bug 358259 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 358263] New: Cannot set first day of week in calendar

[miklos via KDE Bugzilla]

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

Bug ID: 358263
   Summary: Cannot set first day of week in calendar
   Product: plasmashell
   Version: 5.4.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Calendar
  Assignee: mklape...@kde.org
  Reporter: mtm...@freemail.hu
CC: plasma-b...@kde.org

It should be possible to set this independently of the current locale, just as
it was until KDE 4. Please don't go the Gnome way.

Reproducible: Always

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

[korganizer] [Bug 358265] New: Can't select AM while setting Start/Due time for a To-do

[Abhishek Batra via KDE Bugzilla]

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

Bug ID: 358265
   Summary: Can't select AM while setting Start/Due time for a
To-do
   Product: korganizer
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: todoview
  Assignee: korganizer-de...@kde.org
  Reporter: abhshk.b...@gmail.com

While trying to create a new To-do KOrganizer does not allow changing to an AM
time for Start/Due time.

Steps to reproduce:

1. Click "New To-do".
2. Deselect "All Day"
3. Try to set time to AM.

The above steps are valid if current time is in PM. Yet to try out what happens
when the current time is AM.

Regards,
Abhishek

Reproducible: Always

Steps to Reproduce:
1. Click "New To-do".
2. Deselect "All Day"
3. Try to set time to AM.

Actual Results:  
Time doesn't change to AM

Expected Results:  
I should be able to select an AM time.

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

[valgrind] [Bug 357833] Valgrind is broken on recent linux kernel

[Ivo Raisr via KDE Bugzilla]

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

--- Comment #7 from Ivo Raisr  ---
Hi Mark, Thank you for providing the fix also for Solaris.
It works ok on Solaris 12, regression tests passed.

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

[frameworks-modemmanager-qt] [Bug 358261] SMS messages list is not update when calling ModemManager::ModemMessaging::createMessage

[Daniel via KDE Bugzilla]

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

--- Comment #2 from Daniel  ---
Even using the qApp->processEvents(); as you suggested, the message list was
not updated after that.

But as you warned me that I am using in a synchronous mode, I changed the way
to use, now I am using signal/slots and I connected the signal
ModemManager::ModemMessaging::messageAdded in a custom slot and this signal is
emitted OK and I can access the recently created message using the messages
property (ModemManager::Sms::List messages = messaging->messages()). It means
that the list contains the recently added message inside the slot called by the
signal.

Probably I am misusing the framework MMQt. I based my code in the source code
of the example folder. In the truth that example didn't work for me. Running
the example the message did not sent. Is the example running for you?

If you like I can contribute with the MMQt in order to provide more examples.

Thanks in advance. (Sorry for my english, I am from Brazil).

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

[kdevplatform] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

  Component|general |language
   Target Milestone|4.7.2   |---
Version|4.6.60  |1.7.2
Product|kdevelop|kdevplatform

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

[kate] [Bug 358266] New: After trying to reload a session, kate doesn't display anything at all

[via KDE Bugzilla]

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

Bug ID: 358266
   Summary: After trying to reload a session, kate doesn't display
anything at all
   Product: kate
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: sessions
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: lea_pre...@hotmail.fr

I opened Kate, tried to reload a session containing multiple files and a
splitted view, and nothing was displayed at all (the whole window is gray
except for the menu). The issue doesn't go away when restarting Kate.

Reproducible: Didn't try

Steps to Reproduce:
1. Save a session with multiple files and a splitted view
2. Close Kate
3. Open Kate and reload the previous session

Actual Results:  
Nothing is displayed and Kate is unusable.

Expected Results:  
Open the session.

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

[kwin] [Bug 358259] Please bring back custom button spacing from KDE4

[Jani-Matti Hätinen via KDE Bugzilla]

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

--- Comment #2 from Jani-Matti Hätinen  ---
Created attachment 96752
  --> https://bugs.kde.org/attachment.cgi?id=96752=edit
An example of a KDE4 setup with clearly separated buttons

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

[kdevelop] [Bug 334487] Crash during background parsing [operator(), loadPartialData, KDevelop::TopDUContextDynamicData::loadImports]

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In|5.0.0   |1.7.3

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

[kdevelop] [Bug 269369] Kdevelop4 +PHP crashs, while Loading Project [KDevelop::Declaration::indexedType, KDevelop::isPublicBaseClassInternal]

[Milian Wolff via KDE Bugzilla]

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

--- Comment #22 from Milian Wolff  ---
we'll release it this week. sorry for the delay, please stay tuned.

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

[Phonon] [Bug 358274] New: Phonon's VLC backend failed to start

[via KDE Bugzilla]

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

Bug ID: 358274
   Summary: Phonon's VLC backend failed to start
   Product: Phonon
   Version: 4.8.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: sit...@kde.org
  Reporter: second_adr...@gmx.de
CC: myr...@kde.org, romain.per...@gmail.com

Everytime I start Amarok this notification appears:
"Phonon's VLC backend failed to start.
This usually means a problem with your VLC installation, please report a bug
with your distributor."

I'm not sure whether I'm right with the bug on this site. But actually I don't
know the right place reporting this.

Maybe this information can help you:
Fehlerdiagnose für Amarok

Amarok-Version: 2.8.0
KDE-Version: 4.14.9
Qt-Version: 4.8.6
Phonon-Version: 4.8.1
Phonon-Backend: VLC (0.8.0)
PulseAudio: Ja

Amarok-Skripte:
Amarok Script Console 1.0 (angehalten)
Lyricwiki .2 (läuft)
Free Music Charts 1.6.0 (angehalten)
Librivox.org 1.0 (läuft)
Cool Streams 1.0 (angehalten)
Edit Lyricwiki 0.2 (läuft)

Amarok-Module:
Audio-CD-Sammlung (aktiviert)
DAAP-Sammlung (deaktiviert)
MTP-Sammlung (aktiviert)
MySQLServer-Sammlung (aktiviert)
MySQLe-Sammlung (aktiviert)
Sammlung auf iPod, iPad und iPhone (aktiviert)
UPnP-Sammlung (deaktiviert)
Universelle Massenspeicher-Sammlung (aktiviert)
Ampache (deaktiviert)
Jamendo (aktiviert)
Last.fm (deaktiviert)
MP3-Musikladen (deaktiviert)
MP3tunes (deaktiviert)
Magnatune-Online-Shop (deaktiviert)
Podcast-Verzeichnis (aktiviert)
gpodder.net (deaktiviert)

Reproducible: Always

Steps to Reproduce:
1. start Amarok
2.
3.

Actual Results:  
This notification occurs:
"Phonon's VLC backend failed to start.
This usually means a problem with your VLC installation, please report a bug
with your distributor."

Expected Results:  
Amarok starting and playing music.

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

[kdenlive] [Bug 358177] Kdenlive-git - Issue with Wipe transition, not working properly. (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #4 from Jesse  ---
Created attachment 96758
  --> https://bugs.kde.org/attachment.cgi?id=96758=edit
Example of wipe issue (the black color behind the text in this example should
be showing the helicopter, not a black solid.

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

[Breeze] [Bug 358271] Some comboboxes are missing shadows and are hard to click

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #1 from Martin Klapetek  ---
Created attachment 96757
  --> https://bugs.kde.org/attachment.cgi?id=96757=edit
Screenshot

Thanks for the report

Reattaching the screenshot here; for future reference, always please attach
screenshots directly to bug reports rather than posting external links.

Thanks

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

[kdenlive] [Bug 358177] Kdenlive-git - Issue with Wipe transition, not working properly. (video example included)

[Jesse via KDE Bugzilla]

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

--- Comment #3 from Jesse  ---
Looks like it's 90% fixed! For video clips, it works like a charm; wipes clean,
and does a linear wipe right off the bat.

One more issue. When applying to title clips (could be because title clips have
an alpha channel/transparent background), but when a title clip is over a video
clip, and you put the Wipe transition on the beginning of the title clip, the
background during the wipe is black until it reaches the end of the yellow
transition block, then the transparency returns to normal (see screenshot I'm
about to attach).

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

[amarok] [Bug 358225] Amarok does not react when clicking on play

[via KDE Bugzilla]

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

--- Comment #2 from second_adr...@gmx.de ---
Thank you very much for your reply!

I visited some sites (like http://opensuse-guide.org/codecs.php) and read some
articles and installed the codecs. But nothing changes!
Unfortunately I am not sure whether I've really installed all necessary codecs,
but I think so. 

Then I tried to change the phonon-backend form gstreamer to vlc. I got another
error (http://opensuse-guide.org/codecs.php).

FWIW: I can play MP3-files with kaffeine.

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

[Breeze] [Bug 358271] Some comboboxes are missing shadows and are hard to click

[Antonis G . via KDE Bugzilla]

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

Antonis G.  changed:

   What|Removed |Added

 CC||gaanto...@civil.auth.gr

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

[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame

[Cristiano da Cunha Duarte via KDE Bugzilla]

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

Cristiano da Cunha Duarte  changed:

   What|Removed |Added

 CC||cunh...@gmail.com

--- Comment #13 from Cristiano da Cunha Duarte  ---
(In reply to maldun.finsterschreck from comment #11)
> After disabling the Compositor, konsole opens normally.

Same behaviour here with FC23 KDE 5. With Compositor disabled (Shift+Alt+F12),
konsole opens normally on the second monitor.

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

[Breeze] [Bug 358271] Some comboboxes are missing shadows and are hard to click

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

Summary|Some selectboxes are|Some comboboxes are missing
   |missing shadows and are |shadows and are hard to
   |hard to click   |click
 CC||mklape...@kde.org

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

[kate] [Bug 358273] New: Ruby singleton class

[MASAKI]

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

Bug ID: 358273
   Summary: Ruby singleton class
   Product: kate
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: y...@reasonset.net

Ruby's singleton class syntax like

class <

[umbrello] [Bug 358272] No color change for communication diagram messages possible

[Ralf Habacker via KDE Bugzilla]

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

--- Comment #1 from Ralf Habacker  ---
It turns out that the implementation  sets up the line color of the
AssociationWidget's class member m_nameWidget, which is never used.

void AssociationWidget::slotMenuSelection(QAction* action)
{

// if it's a collaboration message we now just use the code in
floatingtextwidget
// this means there's some redundant code below but that's better than
duplicated code
if (isCollaboration() && sel != ListPopupMenu::mt_Delete) {
m_nameWidget->slotMenuSelection(action);
return;
}

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

[krita] [Bug 358130] mouse won't work on canvas after using a tablet

[via KDE Bugzilla]

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

--- Comment #2 from katearche...@yandex.ru ---
(In reply to Boudewijn Rempt from comment #1)
> Hi,
> 
> Thanks for your report. Which type of tablet are you using?

wacom intuos tablet, cth-680, driver 3.5.0.1(28.04.2015)

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

[kdenlive] [Bug 358185] Kdenlive-git - Title editor, shows greenish overlay after clicking "Show Background", but only the first time.

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #4 from wegwerf-1-...@gmx.de ---
Noticed that too when toyed around with title clips.

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

[amarok] [Bug 358225] Amarok does not react when clicking on play

[Myriam Schweingruber via KDE Bugzilla]

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

--- Comment #3 from Myriam Schweingruber  ---
Well, Kaffeine doesn't sue Phonon, so can't be compared here. Depending on your
Phonon version, you need either the codecs for gstreamer 0.10 or 1.x, which
exact version of the phonon-backend-gstreamer do you have?
It would also be helpful to know which exact KDE release you are using, and
which desktop...

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

[plasmashell] [Bug 356655] auto / show / hide setting in systray does not stick across reboot for xembed icons

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #2 from Wolfgang Bauer  ---
(In reply to David Edmundson from comment #1)
> Heh, not surprising this doesn't work.
> 
> At one point I had it use the title as a unique idenitifier, but apparently
> this caused problems for Wine apps where that wasn't set and apps simply
> didn't appear.
> I'm not sure what any possible fix here would be.

Sorry for asking/suggesting the obvious.
But wouldn't it be possible to use the title, and only fall back to the
windowId when the title is empty?
Would at least fix this problem for most (non-wine) xembed icons I suppose.

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

[bugs.kde.org] [Bug 358275] New: Browse and My Bugs should show REOPEN status by default

[Olivier Churlaud via KDE Bugzilla]

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

Bug ID: 358275
   Summary: Browse and My Bugs should show REOPEN status by
default
   Product: bugs.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sysad...@kde.org
  Reporter: oliv...@churlaud.com
CC: she...@kde.org

Currently the reopen bugs are not shown, so 

1) I keep adding bugs already known (it's time consuming for the devs)
2) I never find them back without doing a advanced research.

Maybe other tags should be added, but this one, definitely.

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