[plasmashell] [Bug 360958] New: Instant Messaging

[FoxHunter via KDE Bugzilla]

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

Bug ID: 360958
   Summary: Instant Messaging
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: foxhun...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-35-generic x86_64
Distribution: Ubuntu 15.10

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

Every time I open the instant messaging configuration from the taskbar the KDE
taskbar crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9b5258a800 (LWP 23059))]

Thread 12 (Thread 0x7f9b3c0e1700 (LWP 23061)):
#0  0x7f9b4cd4188d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9b50d88bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f9b50d8a74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f9b3ecaaa39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7f9b4d4342be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9b4c5236aa in start_thread (arg=0x7f9b3c0e1700) at
pthread_create.c:333
#6  0x7f9b4cd4ce9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f9b31a70700 (LWP 23063)):
#0  0x7f9b4cd3d44d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9b45b3ff75 in ?? () from
/usr/lib/nvidia-352/tls/libnvidia-tls.so.352.63
#2  0x7f9b49b314e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9b49aedcd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9b49aee190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f9b49aee2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f9b4d66b29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9b4d61175a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9b4d42f3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f9b4fc57f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f9b4d4342be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f9b4c5236aa in start_thread (arg=0x7f9b31a70700) at
pthread_create.c:333
#12 0x7f9b4cd4ce9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f9b2662a700 (LWP 23066)):
#0  0x7f9b49b32884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9b49aed770 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9b49aee11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9b49aee2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9b4d66b29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9b4d61175a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9b4d42f3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9b4fc57f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f9b4d4342be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f9b4c5236aa in start_thread (arg=0x7f9b2662a700) at
pthread_create.c:333
#10 0x7f9b4cd4ce9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f9b1fc67700 (LWP 23070)):
#0  0x7ffd52ffeb7f in clock_gettime ()
#1  0x7f9b4cd5b33d in __GI___clock_gettime (clock_id=,
tp=) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f9b4d4e53a6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f9b4d668d29 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9b4d669295 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9b4d66a67e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9b49aed77d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f9b49aee11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f9b49aee2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f9b4d66b29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f9b4d61175a in
QEventLoop::exec(QFlags) () from

[plasmashell] [Bug 356609] Add options to prefer window icon over application icon

[via KDE Bugzilla]

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

--- Comment #2 from k...@happyjack.org ---
Created attachment 98068
  --> https://bugs.kde.org/attachment.cgi?id=98068=edit
Patch to revert to the desired behavior

For anyone willing to build from source, this patch applies against
plasma-workspace (5.6.0, may work with others) to revert to the desired
behavior of not using launcher icons.  There is no configurability: this
unconditionally uses the window's icon, which is the correct behavior as far as
I'm concerned.

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

[Discover] [Bug 358715] Not Downloading for Updates

[vinothkanna90 via KDE Bugzilla]

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

--- Comment #5 from vinothkanna90  ---
Vlc Problem is after kubuntu update from plasma 4 to plasma 5 this is occuring
.
Distribution like  Send Anywhere software can't to be removed or updated what
to do for that.

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

[krita] [Bug 360785] Fill layers not updating

[caetano via KDE Bugzilla]

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

--- Comment #2 from caetano  ---
Sorry I meant "delete" (I have a french keyboard)

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

[muon] [Bug 360832] Updater NOT SOLVED! Remains in System Tray reporting needed updates after successful update

[EllisIsPfroh via KDE Bugzilla]

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

--- Comment #4 from EllisIsPfroh  ---
@ Nikola Schnelle:

Also worth looking at -> changelog of Plasma 5.6.0

https://www.kde.org/announcements/plasma-5.5.5-5.6.0-changelog.php

... has even more fixes for Plasma-Discover (search for bug #347602 there)

 considered finding the KDE-Announcements quite professional & helpful 

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

[muon] [Bug 360832] Updater NOT SOLVED! Remains in System Tray reporting needed updates after successful update

[EllisIsPfroh via KDE Bugzilla]

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

EllisIsPfroh  changed:

   What|Removed |Added

 CC||ellisistf...@yahoo.de

--- Comment #3 from EllisIsPfroh  ---
@ Nikola
 take a look at the changelog of Plasma 5.5 via kde.org Announcements
 - https://www.kde.org/announcements/plasma-5.5.5.php -->
 - https://www.kde.org/announcements/plasma-5.5.4-5.5.5-changelog.php

in addition those bugs are listed there (Plasma-Discover - NOT Discover (which
is for hardware detection)):
https://bugs.kde.org/show_bug.cgi?id=347602
https://bugs.kde.org/show_bug.cgi?id=358359

and you find the commit there too.

best regards

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

[systemsettings] [Bug 360957] New: cannot use anything kde, and cannot open software manager and cannot download kde anything

[Wendi Rafferty via KDE Bugzilla]

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

Bug ID: 360957
   Summary: cannot use anything kde, and cannot open software
manager  and cannot download kde anything
   Product: systemsettings
   Version: 4.11.10
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: kcm_gtk
  Assignee: aleix...@gmail.com
  Reporter: pebble...@ymail.com

the vwhole system  isn't working right

Reproducible: Always

Steps to Reproduce:
1.reinstalled repos
2.updated system
3.added ppa, bu they dont support trusty

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

[kwin] [Bug 360878] ::allowClientActivation should unconditionally return false for unreasonable focus policies

[via KDE Bugzilla]

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

--- Comment #8 from r...@alum.mit.edu ---
Ugh.  Virtual desktop switching is really bad news.  I just don't want the
focus to switch, period.  I'll be installing 5.6.0 shortly.  If it does
actually switch the desktop -- even with mouse follows/under focus -- I'll be
filing a bug against *that*.

Here is the xprop output (5.9.5):

_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE,
_NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT,
_NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN,
_NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 0, 0, 17, 0
_NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 17, 0
_NET_WM_DESKTOP(CARDINAL) = 2
_KDE_NET_WM_ACTIVITIES(STRING) = "a69c2087-1863-4647-8743-f5bcff184776"
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_VERT,
_NET_WM_STATE_MAXIMIZED_HORZ
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x98015e2
bitmap id # of mask for icon: 0x98015e3
window id # of group leader: 0x981
XdndAware(ATOM) = BITMAP
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 1385010480
_NET_WM_ICON(CARDINAL) =Icon (26 x 26):


░▒░  ░▒▒▒░
▒ ░░ ░
▒  ▒░ ░▒▒▒
▒   ▒░ ░▒▒
▒▒░ ░░
▒ ▒░  
▒  ▒░ 
▒   ▒░
▒    ▒
▒    ▒
▒  ▒   ▒  ▒   ▒  ▒
▒    ▒
▒  ▒   ▒  ▒   ▒  ▒
▒  ▓▒▒▓  ▒
▒  ▓   ▒  ▒   ▓  ▒
▒░ ▓▓▓▓ ░▒
▒░  ░▒
▒░  ░▒
▒░  ░▒
▒▒
░░




Icon (16 x 16):
 ░▒▒░  ░▒▒▒ 
 ▒  ░▒  ▒▒▒ 
 ▒   ░▒  ▒▒ 
 ▒░▒  ▒ 
 ▒ ░▒   
 ▒  ░▒  
 ▒  ▒▒▒  ░▒ 
 ▒  ▒  ▒  ▒   ▒ 
 ▒  ▒▒▒   ▒ 
 ▒  ▒  ▒  ▒   ▒ 
 ▒  ▒▒▒   ▒ 
 ▒  ▒  ▒  ▒   ▒ 
 ▒░ ▒▒▒  ░▒ 
 ▒░  ░▒ 
 ▒▒ 
 ▒▒ 


_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 159389149
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_NET_WM_USER_TIME(CARDINAL) = 1477809551
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x98015dc
WM_CLIENT_LEADER(WINDOW): window id # 0x981
_NET_WM_PID(CARDINAL) = 12263
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "rlk-mobile.rlk"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified location: 0, 0
program specified minimum size: 0 by 0
window gravity: Static
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING,
_NET_WM_SYNC_REQUEST
WM_CLASS(STRING) = "libreoffice", "libreoffice-calc"
WM_ICON_NAME(STRING) = "rowing.ods - LibreOffice Calc"
_NET_WM_ICON_NAME(UTF8_STRING) = "rowing.ods - LibreOffice Calc"
WM_NAME(STRING) = "rowing.ods - LibreOffice Calc"
_NET_WM_NAME(UTF8_STRING) = "rowing.ods - LibreOffice Calc"

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

[klipper] [Bug 329174] Lost copied text after close application

[Christos Gourdoupis via KDE Bugzilla]

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

Christos Gourdoupis  changed:

   What|Removed |Added

 CC||xri...@otenet.gr

--- Comment #13 from Christos Gourdoupis  ---
plasma 5.5.5, qt 5.5.1 not using any clipboard facility
Copy some text in kwrite and close it.
Open another instance and paste. Nothing happens.

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

[konsole] [Bug 356223] konsole crashes when external monitor is unplugged

[Marcus Better via KDE Bugzilla]

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

Marcus Better  changed:

   What|Removed |Added

 CC||mar...@better.se

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

[krita] [Bug 360956] New: glitching when using tablet

[via KDE Bugzilla]

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

Bug ID: 360956
   Summary: glitching when using tablet
   Product: krita
   Version: 2.9.11
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: artfullyaudaci...@gmail.com

my pen works fine but the program glitches when I use it, it zooms in all the
way and won't scroll, and now half of the toolbars are gone

Reproducible: Always

Steps to Reproduce:
1. Use intuos tablet
2. Open program
3. Attempt to click anything on the toolbar using tablet and pen instead of
mouse

Actual Results:  
It didn't work? Nothing registered and it glitched more

Expected Results:  
Let me use it instead of crashing, allowed me to access the "file" icon

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

[muon] [Bug 360832] Updater NOT SOLVED! Remains in System Tray reporting needed updates after successful update

[Nikola Schnelle via KDE Bugzilla]

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

Nikola Schnelle  changed:

   What|Removed |Added

 CC||n.schne...@gmail.com

--- Comment #2 from Nikola Schnelle  ---
(In reply to Aleix Pol from comment #1)
> The problem is solved, ask your packagers (Kubuntu?) to apply the fix to the
> packages you use.

Where is the fix for this bug (what commits)?

Kubuntu guys want to include it in 16.04 release.

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

[kwin] [Bug 360878] ::allowClientActivation should unconditionally return false for unreasonable focus policies

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #7 from Thomas Lübking  ---
Ok, please ensure  to test this on 5.6.0 - there's a good chance it's covered
by forementioned patch, but actually™ the virtual desktop should change
alongside the focus and it may be that LO underruns checks to "return" the
focus.

I though might have an idea what changed to cause this. Can you please take an
"xprop" (run it in konsole, click the window and attach the output) of the main
LO window that gets the focus (no matter when. ie. it's not required to have it
steal the focus etc.)

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

[digikam] [Bug 360954] digikam - no spell checking when entering meta data

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
The spell checking is a KDE library only feature, through KTextEdit widget.

In the goal to port step by step to pure Qt5 implementation, KTextEdit have
been replaced by QLineEdit everywhere, which do not provide this feature yet.

Gilles Caulier

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

[digikam] [Bug 360954] no spell checking when entering meta data

[via KDE Bugzilla]

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

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

   What|Removed |Added

Summary|digikam - no spell checking |no spell checking when
   |when entering meta data |entering meta data

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

[digikam] [Bug 360955] digikam - EXIF caption no longer copied to captions area

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
Nothing has changed from this point. in source code. Please provide a sample
image to import and check.

Gilles Caulier

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

[Breeze] [Bug 360953] Audio muted icon difers from full volume icon only by color

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/bree |http://commits.kde.org/plas
   |ze-icons/3c59b969f3044b94e0 |ma-framework/2480582c0c017c
   |8bb958b497a4e82e3eb835  |eb4d5014a86b3808c69e230909

--- Comment #6 from andreas  ---
Git commit 2480582c0c017ceb4d5014a86b3808c69e230909 by andreas kainz.
Committed on 24/03/2016 at 23:36.
Pushed by andreask into branch 'master'.

update audio mute icon

M  +---src/desktoptheme/breeze/icons/audio.svgz

http://commits.kde.org/plasma-framework/2480582c0c017ceb4d5014a86b3808c69e230909

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

[digikam] [Bug 359108] 5 beta 3: interface problem, icons not showing up

[via KDE Bugzilla]

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

--- Comment #15 from caulier.gil...@gmail.com ---
4.14 included a lots of icons in digiKam core. In 5.0, all have been removed,
accordingly with Breeze team meet at Randa event in 2015. 

In fact, in digiKam we will code, not design icons. Breeze team are designers
group.

Gilles Caulier

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

[Breeze] [Bug 360953] Audio muted icon difers from full volume icon only by color

[Kai Uwe Broulik via KDE Bugzilla]

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

--- Comment #5 from Kai Uwe Broulik  ---
That was quick, thanks!

Don't forget the icon in the Breeze plasma theme plasma-framework, though. :)

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

[Breeze] [Bug 360953] Audio muted icon difers from full volume icon only by color

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

 CC||majew...@gmx.net

--- Comment #4 from andreas  ---
*** Bug 355575 has been marked as a duplicate of this bug. ***

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

[Breeze] [Bug 355575] red color of player-volume-muted icon is highly confusing

[andreas via KDE Bugzilla]

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

andreas  changed:

   What|Removed |Added

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

--- Comment #1 from andreas  ---


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

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

[Breeze] [Bug 360953] Audio muted icon difers from full volume icon only by color

[andreas via KDE Bugzilla]

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

--- Comment #3 from andreas  ---
I use the - as in mic-off and camera-off

it's always a pleasure to fix a bug for you kai

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

[frameworks-kwindowsystem] [Bug 359206] kwin takes control over shortcut input and does not allow for "unshifting"

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||kdelibs-b...@kde.org,
   ||thomas.luebk...@gmail.com
Version|5.5.4   |unspecified
Product|kwin|frameworks-kwindowsystem
   Assignee|kwin-bugs-n...@kde.org  |mgraess...@kde.org
  Component|tabbox  |general

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

[Breeze] [Bug 360953] Audio muted icon difers from full volume icon only by color

[Thomas Pfeiffer via KDE Bugzilla]

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

Thomas Pfeiffer  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||colo...@autistici.org

--- Comment #1 from Thomas Pfeiffer  ---
Agreed. Never use color as the only indicator of something.

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

[kmail2] [Bug 204712] Mark DKIM signed messages

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #5 from 1...@gmx-topmail.de ---
It could be added to the message header similar to Spamassassin

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

[digikam] [Bug 360955] New: digikam - EXIF caption no longer copied to captions area

[Knut Hildebrandt via KDE Bugzilla]

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

Bug ID: 360955
   Summary: digikam - EXIF caption no longer copied to captions
area
   Product: digikam
   Version: 5.0.0
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: knut.hildebra...@gmx.de

In the digikam4 series the contents of the EXIF caption field was automatically
copied to the captions area when importing a picture. In digikam-5.0.0beta3
this is not done anymore even though in meta data editor synchronisation with
JFIF comment section as well as XMP and IPTC caption are tagged.

Reproducible: Always

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

[krita] [Bug 360916] I turn greyscale off, and its still on when I choose colors.

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org
 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Boudewijn Rempt  ---
Make sure the image is RGB and so are all layers -- use image/convert
colorspace to make sure. In krita, it's possible for the image to be one
colorspace, and some layers to be another.

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

[digikam] [Bug 360954] New: digikam - no spell checking when entering meta data

[Knut Hildebrandt via KDE Bugzilla]

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

Bug ID: 360954
   Summary: digikam - no spell checking when entering meta data
   Product: digikam
   Version: 5.0.0
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: knut.hildebra...@gmx.de

When entering meta data like title or caption there is no spell check anymore
in the Plasma5 version of digikam. Neither could I find a way to switch it on
or off.  As much as I remember spell checking was offered in the digikam4
series.

Reproducible: Always

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

[kdevelop] [Bug 302510] KDevelop errors out on user-defined string literal operators

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #3 from Kevin Funk  ---
Upstream issue. Patch at http://reviews.llvm.org/D18462

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

[Breeze] [Bug 360950] Missing icons for digiKam

[andreas via KDE Bugzilla]

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

--- Comment #1 from andreas  ---
screenshot if possible please

thanks
andreas k

2016-03-24 20:39 GMT+01:00 Maik Qualmann via KDE Bugzilla <
bugzilla_nore...@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=360950
>
> Bug ID: 360950
>Summary: Missing icons for digiKam
>Product: Breeze
>Version: 5.5.5
>   Platform: openSUSE RPMs
> OS: Linux
> Status: UNCONFIRMED
>   Severity: normal
>   Priority: NOR
>  Component: Icons
>   Assignee: visual-des...@kde.org
>   Reporter: metzping...@gmail.com
> CC: kain...@gmail.com
>
> Hello,
>
> the following icons, which are required by digiKam, are still missing in
> the
> Breeze icon theme:
>
> "image-stack"
> "image-stack-open"
>
> Maik
>
> Reproducible: Always
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
> ___
> Visual-design mailing list
> visual-des...@kde.org
> https://mail.kde.org/mailman/listinfo/visual-design
>

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

[plasmashell] [Bug 357603] Having one activity only (which is renamed from "default" to something else) in conjunction with slideshow desktop preferences and unified output for both HMDI and VGA outpu

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

Version|5.5.3   |5.6.0
   Severity|normal  |major

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

[Breeze] [Bug 360953] New: Audio muted icon difers from full volume icon only by color

[Kai Uwe Broulik via KDE Bugzilla]

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

Bug ID: 360953
   Summary: Audio muted icon difers from full volume icon only by
color
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: k...@privat.broulik.de
CC: kain...@gmail.com

The only difference between the two icons is the one's red and the other's
black.
Please make the muted icon have an X instead of the two waves or something else
to make it obvious it means "muted", especially when used in a rather detached
context as a mute button in the audio settings.

Reproducible: Always

Steps to Reproduce:
1. Open Audi Volume settings
2. Go to "Output Devices"
3.

Actual Results:  
There's a button with a red volume icon on the right

Expected Results:  
There's a button with an obvious *muted* volume icon

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

[kmahjongg] [Bug 353845] Game number in status line wrong when loading a game from disk

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[konsole] [Bug 360816] konsole and dolphin also looses changed settings

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #2 from Wolfgang Bauer  ---
Probably the same as bug#358083.

Does it work if you create a new profile and set that as default?

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

[frameworks-frameworkintegration] [Bug 354204] Checkboxes in QtCreator Wizards are uncheckable

[Steffen Klee via KDE Bugzilla]

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

Steffen Klee  changed:

   What|Removed |Added

 CC||stkl.m...@gmail.com

--- Comment #4 from Steffen Klee  ---
Confirming on Arch:
qtcreator 3.6.0-4
plasma 5.5.5-1
qt 5.5.1-10
frameworkintegration 5.19.0-1

Unsetting KDE_FULL_SESSION wasn't enough, had to unset XDG_CURRENT_DESKTOP also
as a workaround (uninstalling frameworkintegration works, too). Of course this
changes the application's visual appearance.

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

[kmymoney] [Bug 356399] crash while saving file after report change with data loss

[Christian David via KDE Bugzilla]

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

Christian David  changed:

   What|Removed |Added

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

--- Comment #2 from Christian David  ---
Sorry, the patch does not fix the crash. Only the file should not be lost
anymore (hopefully).

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

[kmymoney] [Bug 356399] crash while saving file after report change with data loss

[Christian David via KDE Bugzilla]

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

Christian David  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.0
  Latest Commit||http://commits.kde.org/kmym
   ||oney/8319120b9c810574beb0de
   ||97fc44e49315de058d
 Resolution|--- |FIXED

--- Comment #1 from Christian David  ---
Git commit 8319120b9c810574beb0de97fc44e49315de058d by Christian Dávid.
Committed on 24/03/2016 at 20:30.
Pushed by christiand into branch 'frameworks'.

Changed way of saving files which should fix some bugs

The save operation seems to fail every time - it never changed the
orginal file and never reported any issues. I did not find the exact
reason for this bug but I am quite sure it was caused by an incorret
usage of QSaveFile (under some circumstances close() instead of commit()
was called).

Now KMyMoney creates its own temporary file to write to (if needed).
This also works using KGpgFile, which should fix Bug 356399.

The remove() and rename() operations are not atomic which is not so
good as this could result in dataloss if the first operation fails.
However, this is the best OS independet process I could find.

Errors during writing of compressed files may not be detected. I think
this issue should be fixed upstream.
FIXED-IN: 5.0
REVIEW: 127108

M  +2-2CMakeLists.txt
M  +81   -82   kmymoney/views/kmymoneyview.cpp
M  +1-5kmymoney/views/kmymoneyview.h

http://commits.kde.org/kmymoney/8319120b9c810574beb0de97fc44e49315de058d

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

[plasmashell] [Bug 346740] Shortcuts for several tray icons break plasmashell

[Martin Bednar via KDE Bugzilla]

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

Martin Bednar  changed:

   What|Removed |Added

 CC||seraf...@gmail.com

--- Comment #44 from Martin Bednar  ---
I just hit this  (at least dr Konqui says so)  , also by fast clicking in the
system tray.
First happened by fast switch between klipper and telepathy contact list.
I reproduced it by fast switching between telepathy contact list and klipper
(that worked). Crash occured when I hit the bluetooth icon.

What I think is important is that in the first crash klipper had never been
shown before in this session (and system boot), the same goes for the bluetooth
widget (hadn't been shown before).

Trace :

[Current thread is 1 (Thread 0x7ff586714840 (LWP 14889))]

Thread 20 (Thread 0x7ff5730e6700 (LWP 14895)):
#0  0x7ff581013aed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff584edba92 in poll (__timeout=-1, __nfds=1, __fds=0x7ff5730e5c80)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0xbeeb80, cond=cond@entry=0xbeebc0,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459
#3  0x7ff584edd67f in xcb_wait_for_event (c=0xbeeb80) at
/var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693
#4  0x7ff57503a719 in QXcbEventReader::run (this=0xc01bd0) at
qxcbconnection.cpp:1229
#5  0x7ff58167bb63 in QThreadPrivate::start (arg=0xc01bd0) at
thread/qthread_unix.cpp:331
#6  0x7ff58081e314 in start_thread (arg=0x7ff5730e6700) at
pthread_create.c:333
#7  0x7ff58101c6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7ff56757c700 (LWP 14897)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff570c8df63 in cnd_wait (mtx=0xc54dd0, cond=) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/include/c11/threads_posix.h:159
#2  pipe_semaphore_wait (sema=0xc54dd0) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/src/gallium/auxiliary/os/os_thread.h:259
#3  radeon_drm_cs_emit_ioctl (param=param@entry=0xc549a0) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:680
#4  0x7ff570c8d787 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-/work/mesa-/include/c11/threads_posix.h:87
#5  0x7ff58081e314 in start_thread (arg=0x7ff56757c700) at
pthread_create.c:333
#6  0x7ff58101c6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7ff564f75700 (LWP 14903)):
#0  postEventSourcePrepare (s=0x7ff5600012d0,
timeout=timeout@entry=0x7ff564f74bc4) at kernel/qeventdispatcher_glib.cpp:255
#1  0x7ff57cf4455d in g_main_context_prepare
(context=context@entry=0x7ff56990, priority=priority@entry=0x7ff564f74c48)
at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3442
#2  0x7ff57cf44e30 in g_main_context_iterate
(context=context@entry=0x7ff56990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3820
#3  0x7ff57cf4502c in g_main_context_iteration (context=0x7ff56990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3901
#4  0x7ff58186237b in QEventDispatcherGlib::processEvents
(this=0x7ff568c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7ff58181775b in QEventLoop::exec (this=this@entry=0x7ff564f74d70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7ff58167751a in QThread::exec (this=this@entry=0xd39ae0) at
thread/qthread.cpp:503
#7  0x7ff583d9c548 in QQmlThreadPrivate::run (this=0xd39ae0) at
qml/ftw/qqmlthread.cpp:141
#8  0x7ff58167bb63 in QThreadPrivate::start (arg=0xd39ae0) at
thread/qthread_unix.cpp:331
#9  0x7ff58081e314 in start_thread (arg=0x7ff564f75700) at
pthread_create.c:333
#10 0x7ff58101c6dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7ff55c0a2700 (LWP 14912)):
#0  0x7ff581013aed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7ff57cf44f14 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7ff554002e70, timeout=-1, context=0x7ff554000990) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7ff554000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3835
#3  0x7ff57cf4502c in g_main_context_iteration (context=0x7ff554000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3901
#4  0x7ff58186237b in QEventDispatcherGlib::processEvents
(this=0x7ff5540008c0, 

[neon] [Bug 359502] Installing translate in Neon under kubuntu delete neon and plazma

[CaCO3 via KDE Bugzilla]

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

CaCO3  changed:

   What|Removed |Added

 CC||ca...@ruinelli.ch

--- Comment #3 from CaCO3  ---
If you want to have KDE Neon gain population, I see it as a critical need to
provide it in the local language of the users. Why can not the already existing
translations be used? Even they might not be complete, it still would be better
than nothing

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

[digikam] [Bug 359108] 5 beta 3: interface problem, icons not showing up

[Simon via KDE Bugzilla]

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

--- Comment #14 from Simon  ---
Strangely with digikam 4.14 from debian repo I get all icons and they do 
not look like breeze. And I use tango icon theme, but changing it to 
something different (e.g. gnome) does not change the icons within 
digikam 4.14. Maybe there is some icon magic in the debian package :)

On 24/03/16 20:15, Maik Qualmann via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=359108
>
> --- Comment #13 from Maik Qualmann  ---
> Yes, the icons for Light Table and Editor is still missing in Breeze icon
> theme. I'll report to the Breeze team. The Breeze icon theme is the standard
> for KF5. Only the Breeze icon theme has all the icons needed for digiKam. I 
> see
> the icon theme option in the miscellaneous section at the moment as a
> workaround for not KF5 desktops.
> Which Icon theme use you on the desktop?
>
> Maik
>

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

[frameworks-baloo] [Bug 360946] Baloo should handle lmdb corruption

[Fabian via KDE Bugzilla]

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

--- Comment #1 from Fabian <0ink...@googlemail.com> ---
I should add that starting konsole from krunner is a very easy way to trigger
that code path, which might be an explanation for those bugs (360754, 360727,
etc.)

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

[kate] [Bug 357341] kate .gnupg/secring.gpg crashes kate

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||dav...@gengisdave.org

--- Comment #4 from Dominik Haumann  ---
*** Bug 360797 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 357341] kate .gnupg/secring.gpg crashes kate

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #3 from Dominik Haumann  ---
Trace from current sources, tested with file from bug #360797:
#0  0x748d1e66 in kencodingprober::UnicodeGroupProber::HandleData(char
const*, unsigned int) (this=0x7cc6b0, aBuf=0xd38f90
"\341\001\201P\212u\236\273@\242\346\203\001\254U\203\002\310*\203\003\254F\210\004\210\005\230\004\234\006\201\a\202a\274\362\266J\300\326o\326\210\b\377\023\210\t\377\023\203\025\214\356V\211\021\234\022\210",
, aLen=63) at
frameworks/kcodecs/src/probers/UnicodeGroupProber.cpp:89
#1  0x748d4046 in kencodingprober::nsMBCSGroupProber::HandleData(char
const*, unsigned int) (this=0xa777a0, aBuf=0xda3098 "\341\001", aLen=120)
at frameworks/kcodecs/src/probers/nsMBCSGroupProber.cpp:119
#2  0x748d56eb in kencodingprober::nsUniversalDetector::HandleData(char
const*, unsigned int) (this=0xd42600, aBuf=0xda3098 "\341\001", aLen=120)
at frameworks/kcodecs/src/probers/nsUniversalDetector.cpp:149
#3  0x748c9c22 in KEncodingProber::feed(char const*, int)
(this=0x7fffc010, data=0xda3098 "\341\001", len=120)
at frameworks/kcodecs/src/kencodingprober.cpp:181
#4  0x776cdee8 in Kate::TextLoader::readLine(int&, int&)
(this=0x7fffc120, offset=@0x7fffc18c: 0, length=@0x7fffc188: 0)
at frameworks/ktexteditor/src/buffer/katetextloader.h:266
#5  0x776cb2f0 in Kate::TextBuffer::load(QString const&, bool&, bool&,
int&, bool) (this=
0x7df1e0, filename=..., encodingErrors=@0x7df2a8: false,
tooLongLinesWrapped=@0x7df2a9: false, longestLineLoaded=@0x7df2ac: 0,
enforceTextCodec=false)
at frameworks/ktexteditor/src/buffer/katetextbuffer.cpp:621
#6  0x7777aef3 in KateBuffer::openFile(QString const&, bool)
(this=0x7df1e0, m_file=..., enforceTextCodec=false)
at frameworks/ktexteditor/src/document/katebuffer.cpp:195
#7  0x7775133e in KTextEditor::DocumentPrivate::openFile()
(this=0x7d4cc0) at frameworks/ktexteditor/src/document/katedocument.cpp:2252
#8  0x76f57035 in KParts::ReadOnlyPartPrivate::openLocalFile()
(this=0x7cc280) at frameworks/kparts/src/readonlypart.cpp:187
#9  0x76f56cc2 in KParts::ReadOnlyPart::openUrl(QUrl const&)
(this=0x7d4cc0, url=...) at frameworks/kparts/src/readonlypart.cpp:150
#10 0x77753c44 in KTextEditor::DocumentPrivate::openUrl(QUrl const&)
(this=0x7d4cc0, url=...) at
frameworks/ktexteditor/src/document/katedocument.cpp:2596
#11 0x0041bbf1 in KWrite::loadURL(QUrl const&) (this=0x7398b0, url=...)
at kde/applications/kate/kwrite/kwrite.cpp:202
#12 0x004176e0 in main(int, char**) (argc=2, argv=0x7fffd9a8) at
kde/app

And here the valgrind trace for the same file:
==26843== Conditional jump or move depends on uninitialised value(s)
==26843==at 0x8137D93: kencodingprober::UnicodeGroupProber::HandleData(char
const*, unsigned int) (UnicodeGroupProber.cpp:84)
==26843==by 0x813A045: kencodingprober::nsMBCSGroupProber::HandleData(char
const*, unsigned int) (nsMBCSGroupProber.cpp:119)
==26843==by 0x813B6EA:
kencodingprober::nsUniversalDetector::HandleData(char const*, unsigned int)
(nsUniversalDetector.cpp:149)
==26843==by 0x812FC21: KEncodingProber::feed(char const*, int)
(kencodingprober.cpp:181)
==26843==by 0x4EF8EE7: Kate::TextLoader::readLine(int&, int&)
(katetextloader.h:266)
==26843==by 0x4EF62EF: Kate::TextBuffer::load(QString const&, bool&, bool&,
int&, bool) (katetextbuffer.cpp:621)
==26843==by 0x4FA5EF2: KateBuffer::openFile(QString const&, bool)
(katebuffer.cpp:195)
==26843==by 0x4F7C33D: KTextEditor::DocumentPrivate::openFile()
(katedocument.cpp:2252)
==26843==by 0x5A9A034: KParts::ReadOnlyPartPrivate::openLocalFile()
(readonlypart.cpp:187)
==26843==by 0x5A99CC1: KParts::ReadOnlyPart::openUrl(QUrl const&)
(readonlypart.cpp:150)
==26843==by 0x4F7EC43: KTextEditor::DocumentPrivate::openUrl(QUrl const&)
(katedocument.cpp:2596)
==26843==by 0x41BBF0: KWrite::loadURL(QUrl const&) (kwrite.cpp:202)
==26843== 
==26843== Conditional jump or move depends on uninitialised value(s)
==26843==at 0x8137E1F: kencodingprober::UnicodeGroupProber::HandleData(char
const*, unsigned int) (UnicodeGroupProber.cpp:85)
==26843==by 0x813A045: kencodingprober::nsMBCSGroupProber::HandleData(char
const*, unsigned int) (nsMBCSGroupProber.cpp:119)
==26843==by 0x813B6EA:
kencodingprober::nsUniversalDetector::HandleData(char const*, unsigned int)
(nsUniversalDetector.cpp:149)
==26843==by 0x812FC21: KEncodingProber::feed(char const*, int)
(kencodingprober.cpp:181)
==26843==by 0x4EF8EE7: Kate::TextLoader::readLine(int&, int&)
(katetextloader.h:266)
==26843==by 0x4EF62EF: Kate::TextBuffer::load(QString const&, bool&, bool&,
int&, bool) (katetextbuffer.cpp:621)
==26843==by 0x4FA5EF2: KateBuffer::openFile(QString const&, bool)
(katebuffer.cpp:195)
==26843==by 0x4F7C33D: KTextEditor::DocumentPrivate::openFile()
(katedocument.cpp:2252)

[dolphin] [Bug 360952] New: Trash view: Add "Time of deletion" column

[Gregor Mi via KDE Bugzilla]

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

Bug ID: 360952
   Summary: Trash view: Add "Time of deletion" column
   Product: dolphin
   Version: 15.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: codestr...@posteo.org

Currently, in the trash view it is not possible to see when a certain file was
deleted. See also https://bugs.kde.org/show_bug.cgi?id=153492

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

[dolphin] [Bug 309264] Don't show "Move to trash" in removable devices and show "Delete" instead

[Gregor Mi via KDE Bugzilla]

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

Gregor Mi  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||codestr...@posteo.org

--- Comment #1 from Gregor Mi  ---
I tried this with current Plasma and dolphin version:

1. connect an USB hard drive
2. create a file there
3. delete the file
4a. the file is shown in Dolphin's trash view alongside other files from the
local hard drive
4b. the Path column shows the origin of the file

Can you confirm this?

Especially for big files I noticed that the behaviour of moving the file which
the user wants to delete from USB drive to local trash is time consuming and
maybe not expected. On the one hand, it is good to have the file recoverable,
on the other hand the user could be asked what to when the file selection
exceeds a certain size (maybe starting with 10 MB).

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

[Breeze] [Bug 360950] New: Missing icons for digiKam

[Maik Qualmann via KDE Bugzilla]

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

Bug ID: 360950
   Summary: Missing icons for digiKam
   Product: Breeze
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: metzping...@gmail.com
CC: kain...@gmail.com

Hello,

the following icons, which are required by digiKam, are still missing in the
Breeze icon theme:

"image-stack"
"image-stack-open"

Maik

Reproducible: Always

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

[Touchpad-KCM] [Bug 360943] Can't customize touchpad's configuration

[Rajeesh K V via KDE Bugzilla]

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

Rajeesh K V  changed:

   What|Removed |Added

 CC||rajeeshknamb...@gmail.com

--- Comment #1 from Rajeesh K V  ---
Hi,

The reason these options greyed out is you (or the distribution) is
using/installed the 'new' libinput touchpad driver. The package name is usually
xorg-x11-drv-libinput.
Libinput is the unified touchpad driver for X.org and Wayland; but it exposes
only few configurable options compared to the 'old'/previous synaptics driver
(package xorg-x11-drv-synaptics).
If you want all the options to be individually configured, simply remove
libinput driver and install synaptics driver.

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

[kwordquiz] [Bug 360940] Cannot save file

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Thanks for the investigation. The fix was applied to libkeduvocdocument.

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

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

[libkeduvocdocument] [Bug 349610] Cannot save files

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||michael.g...@gmail.com

--- Comment #13 from Christoph Feck  ---
*** Bug 360940 has been marked as a duplicate of this bug. ***

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

[digikam] [Bug 359108] 5 beta 3: interface problem, icons not showing up

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #13 from Maik Qualmann  ---
Yes, the icons for Light Table and Editor is still missing in Breeze icon
theme. I'll report to the Breeze team. The Breeze icon theme is the standard
for KF5. Only the Breeze icon theme has all the icons needed for digiKam. I see
the icon theme option in the miscellaneous section at the moment as a
workaround for not KF5 desktops.
Which Icon theme use you on the desktop?

Maik

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

[plasmashell] [Bug 360949] New: Taskbar disappears because Plasmashell quits unexpectedly

[Alan Aversa via KDE Bugzilla]

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

Bug ID: 360949
   Summary: Taskbar disappears because Plasmashell quits
unexpectedly
   Product: plasmashell
   Version: 5.5.5
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ave...@email.arizona.edu
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.6 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was opening FireFox, and then plasmashell quit (taskbar disappeared)

- Unusual behavior I noticed:
None

- Custom settings of the application:
Nothing special that I know of.

The crash can be reproduced sometimes.

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

Thread 8 (Thread 0x7f0a947a6700 (LWP 5123)):
#0  0x7f0aa3ba930d in poll () at /lib64/libc.so.6
#1  0x7f0aa9f4f102 in  () at /usr/lib64/libxcb.so.1
#2  0x7f0aa9f50c8f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f0a965c34b9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f0aa47b1f3f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f0aa2f1a684 in start_thread () at /lib64/libpthread.so.0
#6  0x7f0aa3bb4efd in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f0a91756700 (LWP 5146)):
#0  0x7f0a9f00a7e9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f0a9efc7916 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0a9efc7a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0aa49d5c3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f0aa497ff5a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f0aa47ad13c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f0aa8a365d5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f0aa47b1f3f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f0aa2f1a684 in start_thread () at /lib64/libpthread.so.0
#9  0x7f0aa3bb4efd in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f0a80934700 (LWP 5148)):
#0  0x7f0a9efc4b61 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f0a9efc6f1b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f0a9efc7883 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f0a9efc7a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f0aa49d5c3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f0aa497ff5a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f0aa47ad13c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f0aa8a365d5 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f0aa47b1f3f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f0aa2f1a684 in start_thread () at /lib64/libpthread.so.0
#10 0x7f0aa3bb4efd in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f0a7adcc700 (LWP 5149)):
#0  0x7f0a9efc4b27 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f0a9efc731a in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f0a9efc78f8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f0a9efc7a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f0aa49d5c3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f0aa497ff5a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f0aa47ad13c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f0aa8a365d5 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f0aa47b1f3f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f0aa2f1a684 in start_thread () at /lib64/libpthread.so.0
#10 0x7f0aa3bb4efd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f0a794c1700 (LWP 5151)):
#0  0x7f0aa2f2036f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0aab8091c4 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f0aab809209 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f0aa2f1a684 in start_thread () at /lib64/libpthread.so.0
#4  0x7f0aa3bb4efd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f09f289e700 (LWP 5229)):
#0  0x7f0aa3ba930d in poll () at /lib64/libc.so.6
#1  0x7f0a9efc7954 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f0a9efc7a5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f0aa49d5c3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f0aa497ff5a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f0aa47ad13c in QThread::exec() () at 

[plasmashell] [Bug 360948] New: Plasma crash

[Alan Aversa via KDE Bugzilla]

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

Bug ID: 360948
   Summary: Plasma crash
   Product: plasmashell
   Version: 5.5.5
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ave...@email.arizona.edu
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.6 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:
I was switching desktops, but I'm not sure if this triggered the crash. It's
crashed unexpectedly before, too, and it doesn't seem to be related to what I'm
doing.

- Unusual behavior I noticed:
None
- Custom settings of the application:
Unknown

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

Thread 8 (Thread 0x7fda57bee700 (LWP 25080)):
#0  0x7fda66ff130d in poll () at /lib64/libc.so.6
#1  0x7fda6d397102 in  () at /usr/lib64/libxcb.so.1
#2  0x7fda6d398c8f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fda59a0b4b9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fda67bf9f3f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fda66362684 in start_thread () at /lib64/libpthread.so.0
#6  0x7fda66ffcefd in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fda54b9e700 (LWP 25122)):
#0  0x7fda62452804 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fda6240ef70 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fda6240f883 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fda6240fa5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fda67e1dc3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fda67dc7f5a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fda67bf513c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fda6be7e5d5 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fda67bf9f3f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fda66362684 in start_thread () at /lib64/libpthread.so.0
#10 0x7fda66ffcefd in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fda43d12700 (LWP 25123)):
#0  0x7fda6240cb20 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7fda6240ef1b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fda6240f883 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fda6240fa5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fda67e1dc3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fda67dc7f5a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fda67bf513c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fda6be7e5d5 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fda67bf9f3f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fda66362684 in start_thread () at /lib64/libpthread.so.0
#10 0x7fda66ffcefd in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fda422a9700 (LWP 25124)):
#0  0x7fda62452804 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fda6240ef70 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fda6240f883 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fda6240fa5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fda67e1dc3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fda67dc7f5a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fda67bf513c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fda6be7e5d5 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fda67bf9f3f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fda66362684 in start_thread () at /lib64/libpthread.so.0
#10 0x7fda66ffcefd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fda4090e700 (LWP 25125)):
#0  0x7fda6636836f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fda6ec511c4 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fda6ec51209 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fda66362684 in start_thread () at /lib64/libpthread.so.0
#4  0x7fda66ffcefd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fda39cf2700 (LWP 25128)):
#0  0x7fda66ff130d in poll () at /lib64/libc.so.6
#1  0x7fda6240f954 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fda6240fa5c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fda67e1dc3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fda67dc7f5a in
QEventLoop::exec(QFlags) () at

[kdeconnect] [Bug 360745] Cannot pair with android phone nor samsung galaxy tab.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|FIXED   |WORKSFORME

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

[krita] [Bug 360916] I turn greyscale off, and its still on when I choose colors.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |general
   Assignee|kdepim-b...@kde.org |krita-bugs-n...@kde.org
Product|Akonadi |krita

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

[krdc] [Bug 360947] New: KRDC crashed when I connected with VNC to another PC

[via KDE Bugzilla]

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

Bug ID: 360947
   Summary: KRDC crashed when I connected with VNC to another PC
   Product: krdc
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: uwol...@kde.org
  Reporter: wodenc...@gmail.com

Application: krdc (4.14.13)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.0-35-generic x86_64
Distribution: Ubuntu 15.10

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

I was attempting to connect with KRDC using VNC to a computer on the network
who uses KRFB to expose the computer as a VNC server. After I clicked "Connect"
within KRDC from the client computer, KRDC crashed.

-- Backtrace:
Application: KRDC (krdc), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f12c1a00840 (LWP 4595))]

Thread 3 (Thread 0x7f12ab4fc700 (LWP 4596)):
#0  0x7f12bfae4589 in qt_gettime () at tools/qelapsedtimer_unix.cpp:150
#1  0x7f12bfbcb0a5 in QTimerInfoList::updateCurrentTime
(this=0x7f12a40030e0) at kernel/qeventdispatcher_unix.cpp:354
#2  QTimerInfoList::timerWait (this=0x7f12a40030e0, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#3  0x7f12bfbc98dc in timerSourcePrepareHelper (src=,
timeout=0x7f12ab4fbb74) at kernel/qeventdispatcher_glib.cpp:143
#4  0x7f12bfbc99a5 in timerSourcePrepare (source=,
timeout=) at kernel/qeventdispatcher_glib.cpp:176
#5  0x7f12bb62477d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f12bb62511b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f12bb6252fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f12bfbca20e in QEventDispatcherGlib::processEvents
(this=0x7f12a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#9  0x7f12bfb980d1 in QEventLoop::processEvents
(this=this@entry=0x7f12ab4fbd40, flags=...) at kernel/qeventloop.cpp:149
#10 0x7f12bfb98445 in QEventLoop::exec (this=this@entry=0x7f12ab4fbd40,
flags=...) at kernel/qeventloop.cpp:204
#11 0x7f12bfa874f9 in QThread::exec (this=this@entry=0x21667a0) at
thread/qthread.cpp:538
#12 0x7f12bfb78133 in QInotifyFileSystemWatcherEngine::run (this=0x21667a0)
at io/qfilesystemwatcher_inotify.cpp:265
#13 0x7f12bfa89d1c in QThreadPrivate::start (arg=0x21667a0) at
thread/qthread_unix.cpp:349
#14 0x7f12bbd0f6aa in start_thread (arg=0x7f12ab4fc700) at
pthread_create.c:333
#15 0x7f12bd8f7e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f12a9fea700 (LWP 4658)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f12bfa8a286 in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x7f129c05afa0) at
thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=,
mutex=mutex@entry=0x7f129c05aeb0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f12bfa86063 in QSemaphore::acquire (this=this@entry=0x7f12a9fe99f0,
n=n@entry=1) at thread/qsemaphore.cpp:144
#4  0x7f12bfbae168 in QMetaObject::activate (sender=0x1aba140, m=, local_signal_index=, argv=) at
kernel/qobject.cpp:3541
#5  0x7f12ad79b483 in ?? () from /usr/lib/kde4/krdc_vncplugin.so
#6  0x7f12ad79ef50 in ?? () from /usr/lib/kde4/krdc_vncplugin.so
#7  0x7f12ad581205 in HandleRFBServerMessage () from
/usr/lib/x86_64-linux-gnu/libvncclient.so.1
#8  0x7f12ad79e7f4 in ?? () from /usr/lib/kde4/krdc_vncplugin.so
#9  0x7f12bfa89d1c in QThreadPrivate::start (arg=0x1aba140) at
thread/qthread_unix.cpp:349
#10 0x7f12bbd0f6aa in start_thread (arg=0x7f12a9fea700) at
pthread_create.c:333
#11 0x7f12bd8f7e9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f12c1a00840 (LWP 4595)):
[KCrash Handler]
#6  0x7f12be7c6033 in qt_fetchPixel<(QImage::Format)7>
(scanLine=0x7f12a97e9910 "", x=888) at painting/qdrawhelper.cpp:382
#7  0x7f12be7c84d2 in qt_fetchUntransformed<(QImage::Format)7>
(buffer=0x7ffe7a6e5420, data=0x2013390, y=, x=,
length=) at painting/qdrawhelper.cpp:515
#8  0x7f12be7c8d21 in blend_untransformed_generic<(SpanMethod)0>
(count=, spans=0x7ffe7a6e7800, userData=0x2013390) at
painting/qdrawhelper.cpp:3633
#9  0x7f12be7b560d in qt_span_fill_clipped (spanCount=spanCount@entry=113,
spans=0x7ffe7a6e8078, spans@entry=0x7ffe7a6e7cf0,
userData=userData@entry=0x2013390) at painting/qpaintengine_raster.cpp:4385
#10 0x7f12be7b3363 in fillRect_normalized (r=...,
data=data@entry=0x2013390, pe=pe@entry=0x20130a0) at
painting/qpaintengine_raster.cpp:1494
#11 0x7f12be7b8b64 in QRasterPaintEngine::drawImage (this=0x217ff60, r=...,

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

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

valdi...@gmail.com changed:

   What|Removed |Added

 CC||valdi...@gmail.com

--- Comment #35 from valdi...@gmail.com ---
With Qt 5.6.0 it's much better: so far I never got it to crash that hard that
the whole session is crashed, but plasma (plasmashell) is still crashes, even
in KDE 5.6.0.


#0  0x760da270 in Plasma::Applet::actions() const () from
/usr/lib/libKF5Plasma.so.5
#1  0x004460ce in ?? ()
#2  0x0044625f in ?? ()
#3  0x71c74bae in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#4  0x76da43bf in
KScreen::Output::apply(QSharedPointer const&) () from
/usr/lib/libKF5Screen.so.7
#5  0x76d85f85 in
KScreen::Config::apply(QSharedPointer const&) () from
/usr/lib/libKF5Screen.so.7
#6  0x76d91fa6 in
KScreen::ConfigMonitor::Private::updateConfigs(QSharedPointer
const&) ()
   from /usr/lib/libKF5Screen.so.7
#7  0x76d93e71 in
KScreen::ConfigMonitor::Private::edidReady(QDBusPendingCallWatcher*) () from
/usr/lib/libKF5Screen.so.7
#8  0x71c74bae in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#9  0x72a86e1f in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from
/usr/lib/libQt5DBus.so.5
#10 0x72a86f18 in ?? () from /usr/lib/libQt5DBus.so.5
#11 0x71c75659 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#12 0x72df968c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#13 0x72dfe8f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#14 0x71c48518 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#15 0x71c4a3da in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#16 0x71c9d883 in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7fffeda0dd87 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#18 0x7fffeda0dfe0 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x7fffeda0e08c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#20 0x71c9dcab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#21 0x71c466fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#22 0x71c4eb7c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#23 0x0041c176 in ?? ()
#24 0x712c7710 in __libc_start_main () from /usr/lib/libc.so.6
#25 0x0041c2d9 in _start ()

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

[amarok] [Bug 360921] Amarok doesn't play music when i click on play or space bar

[EricH via KDE Bugzilla]

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

--- Comment #7 from EricH  ---
Ok, thank you

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

[frameworks-baloo] [Bug 360946] New: Baloo should handle lmdb corruption

[Fabian via KDE Bugzilla]

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

Bug ID: 360946
   Summary: Baloo should handle lmdb corruption
   Product: frameworks-baloo
   Version: unspecified
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Engine
  Assignee: m...@vhanda.in
  Reporter: 0ink...@googlemail.com
CC: pinak.ah...@gmail.com

When ~/.local/share/baloo/index, baloo will crash. The reason for this is that
in both positiondb.cpp and postingdb.cpp mdb_get is expected to either return
MDB_SUCCESS (0) or  to return MDB_NOTFOUND. However, in case of database
corruption mdb_get returns MDB_PAGE_NOTFOUND, as can be seen in the backtrace
below. Note that silently ignoring this error will not work, as further
database operations will yield MDB_BAD_TXN (Transaction cannot recover - it
must be aborted).


ASSERT failure in PositionDB::iter: "MDB_PAGE_NOTFOUND: Requested page not
found", file /home/fabian/projects/baloo/src/engine/positiondb.cpp, line 173

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffc00aa700 (LWP 15679)]
0x7457f5f8 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0  0x7457f5f8 in raise () from /usr/lib/libc.so.6
#1  0x74580a7a in abort () from /usr/lib/libc.so.6
#2  0x74d07391 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1610
#3  QMessageLogger::fatal (this=this@entry=0x7fffc00a8b60, 
msg=msg@entry=0x74fb5fa0 "ASSERT failure in %s: \"%s\", file %s, line
%d") at global/qlogging.cpp:784
#4  0x74d02721 in qt_assert_x (where=, what=, file=, 
line=) at global/qglobal.cpp:3002
#5  0x7fffc02df51c in Baloo::PositionDB::iter (this=0x7fffc00a8c60,
term=...)
at /home/fabian/projects/baloo/src/engine/positiondb.cpp:173
#6  0x7fffc02e84fa in Baloo::Transaction::postingIterator
(this=0x7fffc00a98b0, query=...)
at /home/fabian/projects/baloo/src/engine/transaction.cpp:312
#7  0x7fffc07449f3 in Baloo::SearchStore::constructQuery
(this=0x7fffc00a99c0, tr=0x7fffc00a98b0, term=...)
at /home/fabian/projects/baloo/src/lib/searchstore.cpp:283
#8  0x7fffc0743cc7 in Baloo::SearchStore::constructQuery
(this=0x7fffc00a99c0, tr=0x7fffc00a98b0, term=...)
at /home/fabian/projects/baloo/src/lib/searchstore.cpp:163
#9  0x7fffc0743cc7 in Baloo::SearchStore::constructQuery
(this=0x7fffc00a99c0, tr=0x7fffc00a98b0, term=...)
at /home/fabian/projects/baloo/src/lib/searchstore.cpp:163
#10 0x7fffc074346d in Baloo::SearchStore::exec (this=0x7fffc00a99c0,
term=..., offset=0, limit=10, 
sortResults=true) at /home/fabian/projects/baloo/src/lib/searchstore.cpp:75
#11 0x7fffc0731466 in Baloo::Query::exec (this=0x7fffc00a9b40)
at /home/fabian/projects/baloo/src/lib/query.cpp:210
#12 0x7fffc0963710 in SearchRunner::match (this=this@entry=0x10aa080,
context=..., type=..., category=...)
at
/chakra/core/plasma-workspace/src/plasma-workspace-5.6.0/runners/baloo/baloosearchrunner.cpp:99
#13 0x7fffc09644c9 in SearchRunner::match (this=0x10aa080, context=...)
at
/chakra/core/plasma-workspace/src/plasma-workspace-5.6.0/runners/baloo/baloosearchrunner.cpp:164
#14 0x7fffd802b2d8 in Plasma::AbstractRunner::performMatch (this=0x10aa080,
localContext=...)
at /chakra/core/krunner/src/krunner-5.20.0/src/abstractrunner.cpp:131
#15 0x7fffcfdeffd0 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from /usr/lib/libKF5ThreadWeaver.so.5
#16 0x7fffcfdeeb70 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from /usr/lib/libKF5ThreadWeaver.so.5
#17 0x7fffcfdee67a in ThreadWeaver::Thread::run() () from
/usr/lib/libKF5ThreadWeaver.so.5
#18 0x74d1f238 in QThreadPrivate::start (arg=0x10bbef0) at
thread/qthread_unix.cpp:340
#19 0x72884464 in start_thread () from /usr/lib/libpthread.so.0
#20 0x7463512d in clone () from /usr/lib/libc.so.6


Reproducible: Always

Steps to Reproduce:
1. Corrupt your database
2. Cause a query
3.

Actual Results:  
In debug mode, the assertion is triggered. In release mode,  the cast will be
UB. This manifests in a traceback similar to #355280, as the data is corrupted.

Expected Results:  
Baloo handles the crash gracefully. Ideally, it would try to repair the
database or at least evict the bad data.

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

[frameworks-ktexteditor] [Bug 356110] Line spacing not adjusted to font in printouts

[Dominik Haumann via KDE Bugzilla]

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

--- Comment #2 from Dominik Haumann  ---
Fixed for the next Frameworks release - thanks for good report :)

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

[frameworks-ktexteditor] [Bug 356110] Line spacing not adjusted to font in printouts

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/ktex
   ||teditor/c1cba0174025fe8f277
   ||9ed30ce859b05914eba4b
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Dominik Haumann  ---
Git commit c1cba0174025fe8f2779ed30ce859b05914eba4b by Dominik Haumann.
Committed on 24/03/2016 at 17:10.
Pushed by dhaumann into branch 'master'.

printing: use font size from selected printing schema

M  +21   -7src/printing/printpainter.cpp
M  +4-5src/printing/printpainter.h

http://commits.kde.org/ktexteditor/c1cba0174025fe8f2779ed30ce859b05914eba4b

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

[krita] [Bug 360905] I lost the Tool Options after a crash I can't recover it

[waric via KDE Bugzilla]

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

--- Comment #7 from waric  ---
Created attachment 98066
  --> https://bugs.kde.org/attachment.cgi?id=98066=edit
step 4 : you can't go back by pressing TAB again

to fix the problem, I have to delete krita's files in my profil folder

C:\Users\\AppData\Roaming\krita

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

[Discover] [Bug 360920] Applications not showing up in their category

[Thomas Pfeiffer via KDE Bugzilla]

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

--- Comment #2 from Thomas Pfeiffer  ---
The whole application category definition is just a mess.
Still we shouldn't fix it by excluding certain categories. RKWard and R, for
example, do it right by having only the Science & Math category assigned to
them but not the Education category.
If applications use "Education" which are far more scientific than educational,
what we should do instead is ask them to remove "education".

So yes, please remove the exclusion.

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

[frameworks-ktexteditor] [Bug 335079] Invisible underscore charactere

[via KDE Bugzilla]

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

--- Comment #12 from m_loui...@yahoo.com ---
Regarding comment in the duplicates:
This is not a problem in the fonts. It is normal that some characters extend
above the ascent or below the descent, because these are defined for a
"typical" character. You'll find that most fonts have characters extending
above their ascent (look at the range U+00C0 to U+00DD).
The Java FontMetrics class got it right: it defines getAscent and getMaxAscent.
Some characters may extend above the former, but the second is an absolute
limit. I didn't find an equivalent in QFontMetrics.

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

[plasmashell] [Bug 360945] New: Crash while entering after suspend

[Peter Jespersen via KDE Bugzilla]

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

Bug ID: 360945
   Summary: Crash while entering after suspend
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: flywh...@illogical.dk
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
The P5 crashed when entering the shell after having been in suspend mode for w
few hours .

The crash can be reproduced sometimes.

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

Thread 21 (Thread 0x7f913bd03700 (LWP 1855)):
#0  0x7f914a2cebbd in poll () at /lib64/libc.so.6
#1  0x7f914f217422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f914f21900f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f913e4863c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f914a9c732f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f9149ad80a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f914a2d6fed in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f9138cb4700 (LWP 1878)):
#0  0x7f914a2cebbd in poll () at /lib64/libc.so.6
#1  0x7f91469afe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f91469aff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f914abf9d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f914aba0d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f914a9c261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f914dcd4df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f914a9c732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f9149ad80a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f914a2d6fed in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f9125e27700 (LWP 1886)):
#0  0x7f914a2a8d4d in nanosleep () at /lib64/libc.so.6
#1  0x7f914a2d0974 in usleep () at /lib64/libc.so.6
#2  0x7f912b62a9d0 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#3  0x7f912acf9512 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#4  0x7f912acf9565 in  () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
#5  0x7f9149ad80a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f914a2d6fed in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f911700 (LWP 1889)):
#0  0x7f914a2cebbd in poll () at /lib64/libc.so.6
#1  0x7f91469afe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f91469aff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f914abf9d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f914aba0d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f914a9c261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f914dcd4df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f914a9c732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f9149ad80a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f914a2d6fed in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f911ec48700 (LWP 1890)):
#0  0x7f914a2cebbd in poll () at /lib64/libc.so.6
#1  0x7f91469afe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f91469aff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f914abf9d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f914aba0d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f914a9c261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f914dcd4df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f914a9c732f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f9149ad80a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f914a2d6fed in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f911d3be700 (LWP 1894)):
#0  0x7f9149adc03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f915049c86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f915049c899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f9149ad80a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f914a2d6fed in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f91167c4700 (LWP 1900)):
#0  0x7f91469f1d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f91469af4a0 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f91469afd80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f91469aff7c in 

[frameworks-ktexteditor] [Bug 335079] Invisible underscore charactere

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|WORKSFORME  |---

--- Comment #11 from Dominik Haumann  ---
Still an issue, and definitely valid. One day we need to fix this through
multi-pass painting (first background, then other overlays, and latest text).
Needs large change in the renderer, though.

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

[frameworks-ktexteditor] [Bug 335079] Invisible underscore charactere

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||zh...@outlook.com

--- Comment #10 from Dominik Haumann  ---
*** Bug 359742 has been marked as a duplicate of this bug. ***

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

[frameworks-ktexteditor] [Bug 359742] "_" can't be dispalyed if there are some chinese chars in the same line

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
Known issue: since the painting is line-based fonts whose characters exceed the
lower or upper bound of their own line height draw in the area of neighboring
lines. When neighboring lines are drawn, these parts are lost. Mostly a problem
in the fonts, but then again, would be nice, if Kate could handle it correctly.

You can try other fonts, like Noto Sans mono for instance, or change the font
size, that also sometimes helps.

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

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

[frameworks-ktexteditor] [Bug 335079] Invisible underscore charactere

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||pip@gmx.com

--- Comment #9 from Dominik Haumann  ---
*** Bug 360555 has been marked as a duplicate of this bug. ***

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

[frameworks-ktexteditor] [Bug 360555] Highlighting of spelling errors not shown with some font families when used at smaller sizes.

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
Known issue: since the painting is line-based fonts whose characters exceed the
lower or upper bound of their own line height draw in the area of neighboring
lines. When neighboring lines are drawn, these parts are lost. Mostly a problem
in the fonts, but then again, would be nice, if Kate could handle it correctly.

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

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

[krita] [Bug 360905] I lost the Tool Options after a crash I can't recover it

[waric via KDE Bugzilla]

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

--- Comment #8 from waric  ---
Warning : before to do all these steps, delete your own krita's files in your
profil folder

C:\Users\\AppData\Roaming\krita\*.*

Maybe only on the first use

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

[krita] [Bug 360905] I lost the Tool Options after a crash I can't recover it

[waric via KDE Bugzilla]

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

--- Comment #6 from waric  ---
Created attachment 98065
  --> https://bugs.kde.org/attachment.cgi?id=98065=edit
step 3 : start tape a police name and press TAB

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

[krita] [Bug 360905] I lost the Tool Options after a crash I can't recover it

[waric via KDE Bugzilla]

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

--- Comment #5 from waric  ---
Created attachment 98064
  --> https://bugs.kde.org/attachment.cgi?id=98064=edit
step 2 : on tool options, use backspace to delete the text properties

I used the key backspace to delete the text of the police name on Text
Properties field

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

[krita] [Bug 360905] I lost the Tool Options after a crash I can't recover it

[waric via KDE Bugzilla]

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

--- Comment #4 from waric  ---
Created attachment 98063
  --> https://bugs.kde.org/attachment.cgi?id=98063=edit
step 1 : create a new document

step 1 :
create a news document use the text tool to put a text

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

[kate] [Bug 347474] bottom of lines with Chinese characters are not displayed correctly.

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #3 from Dominik Haumann  ---
Known issue: since the painting is line-based fonts whose characters exceed the
lower or upper bound of their own line height draw in the area of neighboring
lines. When neighboring lines are drawn, these parts are lost. Mostly a problem
in the fonts, but then again, would be nice, if Kate could handle it correctly.

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

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

[frameworks-ktexteditor] [Bug 353730] Characters extending above the font's ascent are not taken into account in the draw algorithm

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

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

--- Comment #1 from Dominik Haumann  ---
Known issue: since the painting is line-based fonts whose characters exceed the
lower or upper bound of their own line height draw in the area of neighboring
lines. When neighboring lines are drawn, these parts are lost. Mostly a problem
in the fonts, but then again, would be nice, if Kate could handle it correctly.

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

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

[frameworks-ktexteditor] [Bug 335079] Invisible underscore charactere

[Dominik Haumann via KDE Bugzilla]

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

Dominik Haumann  changed:

   What|Removed |Added

 CC||emil.vanh...@gmail.com

--- Comment #8 from Dominik Haumann  ---
*** Bug 347474 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 360905] I lost the Tool Options after a crash I can't recover it

[waric via KDE Bugzilla]

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

--- Comment #3 from waric  ---
Created attachment 98062
  --> https://bugs.kde.org/attachment.cgi?id=98062=edit
dockers settings before bug

that is just before to do something

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

[konqueror] [Bug 360944] New: document source created but can't be opened

[UserXYZ via KDE Bugzilla]

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

Bug ID: 360944
   Summary: document source created but can't be opened
   Product: konqueror
   Version: 4.14.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: apru...@gmail.com

Whenever I want to see a web page source, Konqueror gives something like:

Invalid file /tmp/kde-root/konquerorN19138.html: Key file contains line
'www.domain.com' which is not a key-value
pair, group, or comment

if I try to open the simplest web page.

On a more complicated one, which has JS in it as well, the error looks like:

Invalid file /tmp/kde-root/konquerorC19138.html: Key file does not start with a
group

All of /tmp/kde-root/xxxyyyzzz.html files are created and have the proper HTML
source in them, but Konqueror can't open them.

I tried fiddling file associations to havet hem opened in Kate, Kwrite or
anything else, but it does not change the situation - as if the Konqueror does
not even send the html files to the associated application after it creates
them.

And yes, I am working as root, but even if I'm working as a regular user, same
thing happens.
File permissions are OK, 600, and the owner is the one starting the Konqueror.

The OS is Fedora 23, i386, updated.

Reproducible: Always

Steps to Reproduce:
1. open some web page
2. open document source (Ctrl+U)


Actual Results:  
Error dialog with described errors show with only OK button.

Expected Results:  
Should open default html editor or something normal...

This is going on for a long time now, at least from KDE 4.0.x, but with
different errors - before it complained that it can't open the created html
file with the source or some other weird error - I can't take it any longer,
that's why I'm reporting the bug.

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

[krita] [Bug 360905] I lost the Tool Options after a crash I can't recover it

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #2 from Boudewijn Rempt  ---
I'm sorry, I can still not reproduce the issue. On pressing Tab again, I get
all the dockers back, including tool options. Could you make a screenshot of
the tool options docker just before pressing tab for me?

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

[Touchpad-KCM] [Bug 360943] Can't customize touchpad's configuration

[Antoine via KDE Bugzilla]

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

Antoine  changed:

   What|Removed |Added

   Severity|grave   |normal

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

[krita] [Bug 360328] G'mic doesn't work

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 from Boudewijn Rempt  ---
Closing then.

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

[Touchpad-KCM] [Bug 360943] New: Can't customize touchpad's configuration

[Antoine via KDE Bugzilla]

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

Bug ID: 360943
   Summary: Can't customize touchpad's configuration
   Product: Touchpad-KCM
   Version: 5.5.5
  Platform: Mageia RPMs
   URL: https://framapic.org/h7WImV12C25W/e8LIEkq6QSFA.png
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: kcm
  Assignee: rajeeshknamb...@gmail.com
  Reporter: antoine.dumon...@gmail.com

Morning,

As you can see on the screenshot, all options are greyed out into panel of
Touchpad configuration. That is the same comportment for taps | scrolling | 
Pointer motion and others.
It's not possible to configure any option

Mouse (using touchpad) is working as usual, double toes for a right clic, etc.
but no configuration are possible. Nothing crash.

I'm using plasma-desktop 5.6.

Cheers,

Antoine

P.S. Please apologize my language, it's not my native language.

Reproducible: Always

Steps to Reproduce:
1. Open your plasma session ;
2. Go on System Setting > Hardware > Touchpad ;
3. See that all options are greyed out.

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

[Touchpad-KCM] [Bug 360943] Can't customize touchpad's configuration

[Nicolas L . via KDE Bugzilla]

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

Nicolas L.  changed:

   What|Removed |Added

 CC||k...@nicolaslecureuil.fr

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

[bindings] [Bug 360844] perlqt fails to build with GCC 6

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[plasmashell] [Bug 360942] New: Misplaced tooltips after 2 screen size changes

[Laurent Bonnaud via KDE Bugzilla]

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

Bug ID: 360942
   Summary: Misplaced tooltips after 2 screen size changes
   Product: plasmashell
   Version: 5.6.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: l.bonn...@laposte.net
CC: bhus...@gmail.com, plasma-b...@kde.org

After plugging and un-plugging a video projector with lower resolution, all
tooltips are placed in the wrong place.


Reproducible: Always

Steps to Reproduce:
1. Connect a video projector with lower resolution.
2. Setup both screens in "clone" mode. The plasma desktop is then reduced in
size.
3. Unplug the projector.
4. The plasma desktop is restored to its previous size.


Actual Results:  
Tooltips are now displayed as if the desktop had its reduced size.

Expected Results:  
Tooltips should be displayed according to the restored screen size.

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

[plasmashell] [Bug 360942] Misplaced tooltips after 2 screen size changes

[Laurent Bonnaud via KDE Bugzilla]

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

--- Comment #1 from Laurent Bonnaud  ---
Created attachment 98059
  --> https://bugs.kde.org/attachment.cgi?id=98059=edit
Virtual desktop tooltip

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

[frameworks-knotifications] [Bug 358589] Regression: Left click on system tray icon is not seen under XFCE (KDE 4.14 works)

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||rdie...@math.unl.edu

--- Comment #12 from Rex Dieter  ---
My findings testing this patch with pidgin running on plasma-5.5.5:

* stock pidgin systray icon reacts to left click now
* pidgin-indicator icon (which presumably uses SNI), does nothing on left click

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

[plasmashell] [Bug 360942] Misplaced tooltips after 2 screen size changes

[Laurent Bonnaud via KDE Bugzilla]

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

--- Comment #3 from Laurent Bonnaud  ---
Created attachment 98061
  --> https://bugs.kde.org/attachment.cgi?id=98061=edit
K menu is unusable

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

[plasmashell] [Bug 360942] Misplaced tooltips after 2 screen size changes

[Laurent Bonnaud via KDE Bugzilla]

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

--- Comment #2 from Laurent Bonnaud  ---
Created attachment 98060
  --> https://bugs.kde.org/attachment.cgi?id=98060=edit
Systray tooltip

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

[plasmashell] [Bug 360941] New: Plasma Crashing when trying to connect to Telegram using Telepathy

[via KDE Bugzilla]

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

Bug ID: 360941
   Summary: Plasma Crashing when trying to connect to Telegram
using Telepathy
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: grossmann-nikl...@arcor.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-34-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
When trying to connect to the telegram network using telepathy inside Kubuntu,
Plasma crashes

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8083887800 (LWP 1573))]

Thread 11 (Thread 0x7f806ed65700 (LWP 1575)):
#0  0x7f807e03088d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f8082077bd2 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f808207974f in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f80710afa39 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7f807e7232be in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f807d8126aa in start_thread (arg=0x7f806ed65700) at
pthread_create.c:333
#6  0x7f807e03be9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f8067fff700 (LWP 1577)):
#0  0x7f807e03088d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f807addd1ec in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f8060003070, timeout=, context=0x7f806990) at
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:4135
#2  0x7f807addd1ec in g_main_context_iterate
(context=context@entry=0x7f806990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3835
#3  0x7f807addd2fc in g_main_context_iteration (context=0x7f806990,
may_block=1) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3901
#4  0x7f807e95a29b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f807e90075a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f807e71e3d4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f8080f46f85 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f807e7232be in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f807d8126aa in start_thread (arg=0x7f8067fff700) at
pthread_create.c:333
#10 0x7f807e03be9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f805d14e700 (LWP 1580)):
#0  0x7f8083849660 in _dl_update_slotinfo (req_modid=1) at dl-tls.c:622
#1  0x7f80838498cc in update_get_addr (ti=0x7f807eb37718) at dl-tls.c:801
#2  0x7f807e722202 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f807e9597fa in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f807addc77d in g_main_context_prepare
(context=context@entry=0x7f8058000990, priority=priority@entry=0x7f805d14dc70)
at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3442
#5  0x7f807addd11b in g_main_context_iterate
(context=context@entry=0x7f8058000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3820
#6  0x7f807addd2fc in g_main_context_iteration (context=0x7f8058000990,
may_block=1) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3901
#7  0x7f807e95a29b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f807e90075a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f807e71e3d4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f8080f46f85 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f807e7232be in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f807d8126aa in start_thread (arg=0x7f805d14e700) at
pthread_create.c:333
#13 0x7f807e03be9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f8056852700 (LWP 1584)):
#0  0x7f807adda2c8 in g_source_iter_next (iter=iter@entry=0x7f8056851bf0,
source=source@entry=0x7f8056851be8) at
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:952
#1  0x7f807addcb4a in g_main_context_check
(context=context@entry=0x7f8048000990, max_priority=2147483647,
fds=fds@entry=0x7f8048003070, n_fds=n_fds@entry=1) at
/build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3661
#2  0x7f807addd190 in 

[kwin] [Bug 359206] kwin takes control over shortcut input and does not allow for "unshifting"

[via KDE Bugzilla]

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

--- Comment #3 from jat...@gmail.com ---
Thanks again for the confirmation, Thomas.

Should I file a different bug so this reaches the right person, or will this
one suffice? This has been quite an aggravating problem and would love to help
get it fixed.

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

[Discover] [Bug 360920] Applications not showing up in their category

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Aleix Pol  ---
That's what our categories file looks like:
  
Education
applications-education

  
Education

  Science

  

  

We can decide to drop the "Not Science" part, I'm guessing it was done so that
Education doesn't get too crowded with "grown-ups" stuff by having a whole
Science category.

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

[Discover] [Bug 358715] Not Downloading for Updates

[Aleix Pol via KDE Bugzilla]

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

--- Comment #4 from Aleix Pol  ---
Please report issues with VLC to the VLC community. Please focus here on what's
the problems you have with Discover.

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

[Discover] [Bug 360919] An application without description leaves the "Review" button hanging in mid-air

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/disc
   ||over/534553506115a4edf70327
   ||52fcb555e33a18a8b2
 Resolution|--- |FIXED

--- Comment #2 from Aleix Pol  ---
Git commit 534553506115a4edf7032752fcb555e33a18a8b2 by Aleix Pol.
Committed on 24/03/2016 at 14:18.
Pushed by apol into branch 'Plasma/5.6'.

Fall back to PackageKit when AppStream doesn't have information

Backends shouldn't ever offer empty descriptions anyway.

M  +10   -2libdiscover/backends/PackageKitBackend/AppPackageKitResource.cpp

http://commits.kde.org/discover/534553506115a4edf7032752fcb555e33a18a8b2

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

[plasma-nm] [Bug 360668] No visible mini-icon and strange tooltip

[Laurent Bonnaud via KDE Bugzilla]

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

--- Comment #3 from Laurent Bonnaud  ---
Created attachment 98058
  --> https://bugs.kde.org/attachment.cgi?id=98058=edit
screenshot

Here it is (sorry I forgot the upload it).

The screenshot is from the day I reported the problem.
Today, with more recent packages, the mini-icon is visible, but I still get the
 element.

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

[kwordquiz] [Bug 360940] Cannot save file

[via KDE Bugzilla]

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

michael.g...@gmail.com changed:

   What|Removed |Added

Version|unspecified |0.9.2

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

[kwordquiz] [Bug 360940] New: Cannot save file

[via KDE Bugzilla]

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

Bug ID: 360940
   Summary: Cannot save file
   Product: kwordquiz
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: pe...@peterandlinda.com
  Reporter: michael.g...@gmail.com

When trying to save or saveas a file, an error occurs and the file is not
saved.

Reproducible: Always


Actual Results:  
Error: The file is not writable

or: The file is locked by another process.

Expected Results:  
The file is saved.

The error occurs on Kubuntu 15.10 and did not occur in 12.04.

FIX: use url.toLocalFile() instead of url in save method

With the patch below the source compiles and saving files is again possible.

diff --git a/src/kwordquiz.cpp b/src/kwordquiz.cpp
index ccbc5ef..e655d93 100644
--- a/src/kwordquiz.cpp
+++ b/src/kwordquiz.cpp
@@ -919,7 +919,7 @@ bool KWordQuizApp::saveDocAsFileName(KEduVocDocument
*document)
   else {
 if (m_dirWatch->contains(document->url().toLocalFile()))
   m_dirWatch->removeFile(document->url().toLocalFile());
-result = document->saveAs(url, KEduVocDocument::Automatic);
+result = document->saveAs(url.toLocalFile(),
KEduVocDocument::Automatic);
 if (result == KEduVocDocument::NoError) {
   m_dirWatch->addFile(url.path());
   fileOpenRecent->addUrl(url);

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

[kmail2] [Bug 360910] KMail shows PGP/MIME encrypted content as attachment, does not offer to decrypt.

[Sandro Knauß via KDE Bugzilla]

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

Sandro Knauß  changed:

   What|Removed |Added

Version|4.14.10 |Git (master)
 Status|UNCONFIRMED |CONFIRMED
   Platform|Debian testing  |Debian unstable
 Ever confirmed|0   |1

--- Comment #2 from Sandro Knauß  ---
Okay I now see the problem.

Applemail structues the mail differnently:

multipart/mixed
   -> application/pgp-encrypted
   -> application/octet-stream

normal MIME encrypted mails have a structure like this:

multipart/encrypted
   -> application/pgp-encrypted
   -> application/octet-stream

And mimetreeparser do not react only on the mimetype multipart/encrypted and
not at  application/pgp-encrypted.

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

[kdevelop] [Bug 302510] KDevelop errors out on user-defined string literal operators

[Kevin Funk via KDE Bugzilla]

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

Kevin Funk  changed:

   What|Removed |Added

 CC||kf...@kde.org
  Component|Language Support: CPP   |Language Support: CPP
   ||(Clang-based)
   Target Milestone|--- |5.0.0

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

[kdevelop] [Bug 308556] Variadic macro support missing

[Kevin Funk via KDE Bugzilla]

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

--- Comment #13 from Kevin Funk  ---
The Clang supersedes the own parser; we're not going to revive the old one.
Thus I think this is the correct resolution.

We've also done that for all other reports.

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