[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #33 from Martin Gräßlin  ---
> This is a default install of OpenSUSE 42.1 in a VM. Hardware graphics 
> acceleration is not an option

Hardware graphics acceleration in VM is nowadays an option. VMware, VBox, KVM
all support hardware acceleration.

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

[kaddressbook] [Bug 357228] KAddressbook crashes on startup with configured CardDav

[via KDE Bugzilla]

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

acc-kde-b...@flambda.de changed:

   What|Removed |Added

 CC||acc-kde-b...@flambda.de

--- Comment #3 from acc-kde-b...@flambda.de ---
Hi,

I have the same problem.
My kaddressbook also segfauls on start after I added my owncloud server as a
CardDav ressource.

[foo@bar ~]$ kaddressbook 
Reusing existing ksycoca
Recreating ksycoca file
("/home/foo/.cache/ksycoca5_de_+6h1liriCVqWUwGigtKuJxLfSpc=", version 303)
Still in the time dict (i.e. deleted files) ("apps")
Menu "cisco-anyconnect-dart.menu" not found.
modified: "/usr/share/applications/lstopo.desktop"
akonadi.collectionattributetable   OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation  OK
akonadi.collectiontableOK
akonadi.flagtable  OK
akonadi.mimetypetable  OK
akonadi.parttable  OK
akonadi.parttypetable  OK
akonadi.pimitemflagrelationOK
akonadi.pimitemtable   OK
akonadi.pimitemtagrelation OK
akonadi.relationtable  OK
akonadi.relationtypetable  OK
akonadi.resourcetable  OK
akonadi.schemaversiontable OK
akonadi.tagattributetable  OK
akonadi.tagremoteidresourcerelationtable   OK
akonadi.tagtable   OK
akonadi.tagtypetable   OK
Saving
akonadicore_log: Socket error occurred: "QLocalSocket::connectToServer: Invalid
name"
akonadicore_log: Socket error occurred: "QLocalSocket::connectToServer: Invalid
name"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
Speicherzugriffsfehler (Speicherabzug geschrieben) (German for Segfault)

I am using Arch Linux with kaddressbook 5.2.0

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

[ktorrent] [Bug 362607] New: KTorrent default folder locations are changed to an incorrect path therefore ignored when opening .torrent files or magnet links

[Rodrigo Orihuela via KDE Bugzilla]

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

Bug ID: 362607
   Summary: KTorrent default folder locations are changed to an
incorrect path therefore ignored when opening .torrent
files or magnet links
   Product: ktorrent
   Version: 5.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: rodriorihu...@gmail.com

KTorrent changes the default folder locations seen in the configuration to an
incorrect path, e. g. /home/rodrigo/ to file:/home/rodrigo and therefore are
ignored when I open .torrent files or magnet links.

If I enter a new location, KTorrent changes it to an incorrect path adding the
file: to the new one.

Changing the values of completeDir=, saveDir=, tempDir= and torrentCopyDir= in
~/.config/ktorrentrc solves this, but if you apply any changes in "Configure
KTorrent", the paths are gonna be broken again.

Reproducible: Always

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

[Touchpad-KCM] [Bug 351920] Touchpad Three Fingers setting not working

[via KDE Bugzilla]

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

--- Comment #1 from kevincm...@hotmail.com ---
Still not working on 16.04. Also, the Corners settings on the same application
window aren't working.

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

[korganizer] [Bug 358106] [REGRESSION] Allow week to start on Monday

[sparhawk via KDE Bugzilla]

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

--- Comment #8 from sparhawk  ---
I just found this today. Not only is it incorrect to force Australians to
"start" their week on a Sunday, it's fairly evenly split across the whole
world.

https://i.imgur.com/fRzalMT.png

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

[kmail2] [Bug 358529] Message viewing window stuck on Retrieving Folder Contents

[Randy Barlow via KDE Bugzilla]

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

Randy Barlow  changed:

   What|Removed |Added

 CC||ra...@electronsweatshop.com

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

[kmail2] [Bug 361486] Unable to fetch item from backend (collection -1)

[Randy Barlow via KDE Bugzilla]

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

Randy Barlow  changed:

   What|Removed |Added

 CC||ra...@electronsweatshop.com

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

[telepathy] [Bug 360739] RFE: Support for OMEMO

[Randy Barlow via KDE Bugzilla]

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

Randy Barlow  changed:

   What|Removed |Added

URL||https://bugs.freedesktop.or
   ||g/show_bug.cgi?id=93090

--- Comment #2 from Randy Barlow  ---
Thank you for the pointer Martin! I searched that bug tracker and someone had
already filed that request, so I'll paste it here for others:

https://bugs.freedesktop.org/show_bug.cgi?id=93090

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

[krita] [Bug 362571] Clicking outside of Color Adjustment Curves window AND outside of image area, using Wacom intuos pro pen, leads to Krita hanging

[via KDE Bugzilla]

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

kritau...@biketrials.com changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from kritau...@biketrials.com ---
Hi,

I tried the 3.0 beta, and the issue appears to have been fixed.

Keep up the excellent work, and best of luck with the 3.0 release. 

Thanks!

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

[krita] [Bug 362606] New: Hanvon GraphicPal tablet isn't recognized unless after clicking away

[Adam Martinez via KDE Bugzilla]

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

Bug ID: 362606
   Summary: Hanvon GraphicPal tablet isn't recognized unless after
clicking away
   Product: krita
   Version: 2.9.11
  Platform: MS Windows
   URL: https://drive.google.com/file/d/0B9eeBgPwiaieaTlHRmlQe
ldzWTg/view?usp=sharing
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: madman6...@live.com

I'm trying Krita, but it doesn't seem to recognize my Hanvon GraphicPal 0504 as
a tablet. It notices the cursor, but the only way I can draw in it is if I've
clicked outside of the window then clicked back into Krita, and even then, it's
not really controllable and only temporary.

Reproducible: Always

Steps to Reproduce:
1. Plug in Hanvon GraphicPal 0504.
2. Open Krita.
3. Attempt to draw in Krita using tablet.

Actual Results:  
The tablet wasn't recognized except after clicking away.

Expected Results:  
I should've been able to draw in Krita with my tablet, complete with pressure
sensitivity support.

The tablet model appear to be somewhat old.

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

[plasma-nm] [Bug 352326] Plasma nm applet keeps spinning even after wifi network is connected

[Markus S . via KDE Bugzilla]

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

Markus S.  changed:

   What|Removed |Added

 CC||kamika...@web.de

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

[plasma-nm] [Bug 352934] At login, the spinning wifi animation is broken, it stays static. But all the following connection are animated properly.

[Markus S . via KDE Bugzilla]

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

Markus S.  changed:

   What|Removed |Added

 CC||kamika...@web.de

--- Comment #2 from Markus S.  ---
(In reply to Kai Uwe Broulik from comment #1)
> Looks like a
> Qt bug that it doesn't recover once we have a window.

Which Qt bug ID is it?

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

[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[via KDE Bugzilla]

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

--- Comment #5 from nsane...@gmail.com ---
(In reply to nsane457 from comment #4)
> I have this problem on Gentoo.  I think the problem might have something to
> do with the su dolphin picking up the wrong HOME path.
> 
> Delete all the .slave-socket files and try prefixing the 'dolphin' command
> with 'HOME=/root'.
> 
> i.e., something like this on the command line:
> 
> kdesu HOME=/root dolphin
> 
> and see if that is a viable workaround .  I've been running it on and off
> over the past hour and no new .slave-socket files have been created.

Never mind.  They show up after logging-in again.

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

[dolphin] [Bug 356098] feauture request: move *.slave-socket files to tmp folder...

[via KDE Bugzilla]

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

nsane...@gmail.com changed:

   What|Removed |Added

 CC||nsane...@gmail.com

--- Comment #4 from nsane...@gmail.com ---
I have this problem on Gentoo.  I think the problem might have something to do
with the su dolphin picking up the wrong HOME path.

Delete all the .slave-socket files and try prefixing the 'dolphin' command with
'HOME=/root'.

i.e., something like this on the command line:

kdesu HOME=/root dolphin

and see if that is a viable workaround .  I've been running it on and off over
the past hour and no new .slave-socket files have been created.

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

[systemsettings] [Bug 362605] kcm_plasmasearch "Folder" search plugin uses a 48px icon

[Uri Herrera via KDE Bugzilla]

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

Uri Herrera  changed:

   What|Removed |Added

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

--- Comment #1 from Uri Herrera  ---
Looks liked it was a cache issue. I've cleared the directories and reboot my
system the icon is shown properly now.

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

[plasmashell] [Bug 362128] Task manager restored to wrong screen

[Daniel Lichtenberger via KDE Bugzilla]

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

--- Comment #2 from Daniel Lichtenberger  ---
I still have this issue, but I noticed that the commit I mentioned was not part
of 5.6.2 and does not seem to be related to my problem.

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

[Discover] [Bug 362538] Misaligned GUI elements

[Aleix Pol via KDE Bugzilla]

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

--- Comment #2 from Aleix Pol  ---
Hi,
I cannot reproduce. Can you please check the console output for errors?

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

[systemsettings] [Bug 362605] New: kcm_plasmasearch "Folder" search plugin uses a 48px icon

[Uri Herrera via KDE Bugzilla]

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

Bug ID: 362605
   Summary: kcm_plasmasearch "Folder" search plugin uses a 48px
icon
   Product: systemsettings
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: uri_herr...@nitrux.in

This KCM uses 32px icons in its list next to the description of the search
plugins. The "Folder" plugin however uses a 48px icon and scales it to 32px
resulting in a blurry icon.

Reproducible: Always

Steps to Reproduce:
1. Open System Settiungs
2. Go to the Search KCM
3. Change the 48px icon to something else, the plugin changes the icon

Actual Results:  
The "Folder" plugin however uses a 48px icon and scales it to 32px.

Expected Results:  
The "Folder" plugin  uses a 32px icon.

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

[plasmashell] [Bug 349676] Lost ability to configure multiple holiday regions

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.7
 Status|CONFIRMED   |RESOLVED
  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/e8c5a28df28d2d
   ||66e8eaee47550425941e3e7ade

--- Comment #3 from Martin Klapetek  ---
Git commit e8c5a28df28d2d66e8eaee47550425941e3e7ade by Martin Klapetek.
Committed on 03/05/2016 at 00:20.
Pushed by mklapetek into branch 'master'.

Revert "Revert all of the Calendar-agenda changes"

This reverts commit 697aaf8067ebac4c649895e57eff73a5f071b430
and brings back the agenda part of calendar.

REVIEW: 127734
Related: bug 357642
FIXED-IN: 5.7

M  +25   -5applets/digital-clock/package/contents/config/config.qml
M  +3-0applets/digital-clock/package/contents/config/main.xml
M  +157  -12   applets/digital-clock/package/contents/ui/CalendarView.qml
M  +1-6applets/digital-clock/package/contents/ui/configAppearance.qml
A  +72   -0applets/digital-clock/package/contents/ui/configCalendar.qml
[License: GPL (v2/3)]
M  +5-1applets/digital-clock/package/contents/ui/main.qml

http://commits.kde.org/plasma-workspace/e8c5a28df28d2d66e8eaee47550425941e3e7ade

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

[plasmashell] [Bug 357642] Calendar no longer highlights holidays like Bank Holidays, Christmas, New Year

[Martin Klapetek via KDE Bugzilla]

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

Martin Klapetek  changed:

   What|Removed |Added

   Version Fixed In||5.7
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/e8c5a28df28d2d
   ||66e8eaee47550425941e3e7ade
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Martin Klapetek  ---
Git commit e8c5a28df28d2d66e8eaee47550425941e3e7ade by Martin Klapetek.
Committed on 03/05/2016 at 00:20.
Pushed by mklapetek into branch 'master'.

Revert "Revert all of the Calendar-agenda changes"

This reverts commit 697aaf8067ebac4c649895e57eff73a5f071b430
and brings back the agenda part of calendar.

REVIEW: 127734
Related: bug 349676
FIXED-IN: 5.7

M  +25   -5applets/digital-clock/package/contents/config/config.qml
M  +3-0applets/digital-clock/package/contents/config/main.xml
M  +157  -12   applets/digital-clock/package/contents/ui/CalendarView.qml
M  +1-6applets/digital-clock/package/contents/ui/configAppearance.qml
A  +72   -0applets/digital-clock/package/contents/ui/configCalendar.qml
[License: GPL (v2/3)]
M  +5-1applets/digital-clock/package/contents/ui/main.qml

http://commits.kde.org/plasma-workspace/e8c5a28df28d2d66e8eaee47550425941e3e7ade

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

[KScreen] [Bug 362586] Crash when plugging in HDMI

[Sebastian Kügler via KDE Bugzilla]

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

--- Comment #1 from Sebastian Kügler  ---
Thanks for the report!

The backtrace doesn't really help here, to debug this further, I'd need some
additional information and the config files kscreen creates (these can
hopefully give us a pointer why the kded module crashes.

Could you paste the contents of the files in ~/.local/share/kscreen/ here?

Could you paste the output of "kscreen-console outputs"?

Could you enable detailed logging by putting this into your
~/.config/QtProject/qtlogging.ini

[Rules]
kscreen.kded=true

and then reproduce the crash with by stopping and restarting kded5 from a
terminal, so you get its output:

kquitapp kded5
kded5

(as your normal user).

In order to work around the crash on your system, so you can use it, try moving
the files in ~/.local/share/kscreen/ out of the way (keep backups, just in
case), if it still crashes (it probably will) disable the "KScreen 2" module in
System Settings > Startup and Shutdown > Background Services from Startup
Services.

Thanks for the help!

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

[kdev-python] [Bug 362515] Segfault in code completion

[Sven Brauch via KDE Bugzilla]

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

--- Comment #5 from Sven Brauch  ---
It looks a bit like the context gets deleted by something else. I wonder why
this started happening only now ...

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

[kdev-python] [Bug 362515] Segfault in code completion

[Francis Herne via KDE Bugzilla]

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

--- Comment #4 from Francis Herne  ---
More backtrace:


Thread 9 "KDevelop::Compl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa59be700 (LWP 13247)]
0x7fff88056020 in ?? ()
(gdb) bt full
#0  0x7fff88056020 in ?? ()
No symbol table info available.
#1  0x7fffa5a0081f in Python::ExpressionVisitor::ExpressionVisitor
(this=0x7fffa0040c60, ctx=) at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/duchain/expressionvisitor.cpp:70
No locals.
#2  0x7fffa5c73969 in Python::visitorForString (str=...,
context=context@entry=0x7fff880b2240, scanUntil=..., scanUntil@entry=...)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:84
builder = {m_problems =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{ = {
  static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}, 
  static pyInitLock = { = {d_ptr = {_q_value = {_M_b =
{_M_p = 0x0, }}
tmpAst = {value = 0x7fffa0051e50, d = 0x7fffa008e580}
v = 
#3  0x7fffa5c77947 in
Python::PythonCodeCompletionContext::functionCallItems
(this=this@entry=0x7fffa0043080) at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:144
resultingItems =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= { = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}
functionCalled = 0x0
v = std::unique_ptr containing
0x74dc7ee0 
lock = {m_lock = 0x74dc7ee0 , m_locked =
89, m_timeout = 32767}
__PRETTY_FUNCTION__ = "Python::PythonCodeCompletionContext::ItemList
Python::PythonCodeCompletionContext::functionCallItems()"
current = 0x74dc9d40 
calltips = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{ = {static _S_alignment = 4, 
_M_i = -1}, }}}, alloc = 0, begin = 0,
end = 0, array = {0x0}}, d = 0x74dc9d40 }, d =
0x74dc9d40 }}
calltipItems =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= { = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}
#4  0x7fffa5c7cb28 in Python::PythonCodeCompletionContext::completionItems
(this=0x7fffa0043080, abort=@0x42aa2d0: false, fullCompletion=)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:574
resultingItems =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= { = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}
__PRETTY_FUNCTION__ = "virtual
QList
Python::PythonCodeCompletionContext::completionItems(bool&, bool)"
#5  0x7fffa5c7c992 in Python::PythonCodeCompletionContext::completionItems
(this=this@entry=0x7fffa003bf20, abort=@0x42aa2d0: false,
fullCompletion=fullCompletion@entry=false)
at
/tmp/yaourt-tmp-flh/aur-kdevelop-python3-git/src/kdev-python/codecompletion/context.cpp:564
resultingItems =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= { = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x74dc9d40
}, d = 0x74dc9d40 }}
__PRETTY_FUNCTION__ = "virtual
QList
Python::PythonCodeCompletionContext::completionItems(bool&, bool)"
#6  0x72408d24 in KDevelop::CodeCompletionWorker::computeCompletions
(this=0x42aa2b0, context=..., position=..., followingText=...,
contextRange=..., contextText=...)
at
/home/flh/projects/src/kdevplatform/language/codecompletion/codecompletionworker.cpp:167
items =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= { = {
static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x2a21aa0}, d =
0x2a21aa0}}
tree =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value
= { = {

[drkonqi] [Bug 355807] Dialog to mark report as related does nothing

[via KDE Bugzilla]

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

olipro...@gmail.com changed:

   What|Removed |Added

 CC||olipro...@gmail.com

--- Comment #13 from olipro...@gmail.com ---
I'm also experiencing this in a fresh, standard install of Kubuntu 16.04, with
the constant random crashes of plasmashell, I cannot join my report to an
existing one.

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

[systemsettings] [Bug 362601] Information about your System

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID
 CC||cf...@kde.org

--- Comment #1 from Christoph Feck  ---
Please ask for help in a forum of your distribution.

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

[frameworks-baloo] [Bug 362566] Random crash while maximizing openbox

[Alexander Potashev via KDE Bugzilla]

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

Alexander Potashev  changed:

   What|Removed |Added

  Component|General |general
Product|Baloo   |frameworks-baloo
Version|unspecified |5.18.0
 CC||aspotas...@gmail.com

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

[plasmashell] [Bug 361753] Activities marked “stopped” without reason

[Denis Kuplyakov via KDE Bugzilla]

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

--- Comment #4 from Denis Kuplyakov  ---
(In reply to Ivan Čukić from comment #3)
> What happens if you do it for the stopped one, and not the starting one?

It is now Running and showing correctly in Win-Q and Win-Tab.

$ kamd_listactivities
Service version: 6.2.0
[RUNNING] de709d6c-3d25-45af-9699-197cb2371fbd Technosphere
(preferences-activities)
[RUNNING] 2fcababc-b090-4846-932e-79887cc431b7 VideoTracking
(preferences-activities)
[STARTING] 3eff8dee-079c-49e8-ba76-0fb7d83feb6c Диплом (Написание диплома и
презентации, )
[CURRENT] 8947586a-ed78-472e-a2e3-14de917ccc54 Стандратная
(preferences-activities)

Little offtopic: it seems string [Stopped] is showing in black in konsole and
isn't visible on black background

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

[digikam] [Bug 362595] it crashes on startup

[David Portabella via KDE Bugzilla]

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

--- Comment #2 from David Portabella  ---
sure. how i get it?

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

[digikam] [Bug 362595] it crashes on startup

[via KDE Bugzilla]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
We need a  debugger backtrace please...

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

[telepathy] [Bug 353901] Add support for Facebook chat using Whatsapp-purple

[acidrums4 via KDE Bugzilla]

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

--- Comment #2 from acidrums4  ---
(In reply to acidrums4 from comment #1)
> I guess everyone here knows this, but on the remote case someone don't:
> there's also a facebook plugin for bitlbee that is working right now
> (https://github.com/bitlbee/bitlbee-facebook). Maybe the solution hadn't
> necessarily involve the purple mechanism. I don't know which of them would
> be more reliable, but it's just to have the bitlbee one in mind.
> 
> I agree too about this and the whatsapp thing (As far as I know, Bitlbee is
> planning to support Whatsapp on its core, and there's some python plugin for
> it since a few months) are holding me back to use KTP, since I of the
> services it supports I just have GTalk/Hangouts. And seems many people are
> in this situation, too.

Oh, and seems someone was doing a Telepathy-Qt connection manager for KTP
already, but abandoned:

https://github.com/WeedBilbaoGaming/KtP-facebook-GraphAPI

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

[telepathy] [Bug 353901] Add support for Facebook chat using Whatsapp-purple

[acidrums4 via KDE Bugzilla]

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

acidrums4  changed:

   What|Removed |Added

 CC||acidru...@gmail.com

--- Comment #1 from acidrums4  ---
I guess everyone here knows this, but on the remote case someone don't: there's
also a facebook plugin for bitlbee that is working right now
(https://github.com/bitlbee/bitlbee-facebook). Maybe the solution hadn't
necessarily involve the purple mechanism. I don't know which of them would be
more reliable, but it's just to have the bitlbee one in mind.

I agree too about this and the whatsapp thing (As far as I know, Bitlbee is
planning to support Whatsapp on its core, and there's some python plugin for it
since a few months) are holding me back to use KTP, since I of the services it
supports I just have GTalk/Hangouts. And seems many people are in this
situation, too.

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

[akregator] [Bug 357495] Akregator krashes when loading some Slashdot articles

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX
 CC||mon...@kde.org

--- Comment #6 from Laurent Montel  ---
4.14 is too old version
now we use qtwebengine not khtml

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

[kcharselect] [Bug 362603] Segmentation fault when search field cleared via backspace

[Bryan Elliott via KDE Bugzilla]

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

--- Comment #6 from Bryan Elliott  ---
(In reply to Bryan Elliott from comment #1)
> Created attachment 98752 [details]
> First part of core dump parchive
> 
> Extract with the others using:
> 
> par2 r core.xz.par2
> xz -d core.xz

Done as a par2, as the upload limit was something like 80k smaller than the
core dump would fit into.

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

[kcharselect] [Bug 362603] Segmentation fault when search field cleared via backspace

[Bryan Elliott via KDE Bugzilla]

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

--- Comment #5 from Bryan Elliott  ---
Created attachment 98756
  --> https://bugs.kde.org/attachment.cgi?id=98756=edit
vol31+10

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

[kcharselect] [Bug 362603] Segmentation fault when search field cleared via backspace

[Bryan Elliott via KDE Bugzilla]

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

--- Comment #4 from Bryan Elliott  ---
Created attachment 98755
  --> https://bugs.kde.org/attachment.cgi?id=98755=edit
vol21+10

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

[kcharselect] [Bug 362603] Segmentation fault when search field cleared via backspace

[Bryan Elliott via KDE Bugzilla]

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

--- Comment #3 from Bryan Elliott  ---
Created attachment 98754
  --> https://bugs.kde.org/attachment.cgi?id=98754=edit
vol11+10

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

[kcharselect] [Bug 362603] Segmentation fault when search field cleared via backspace

[Bryan Elliott via KDE Bugzilla]

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

--- Comment #2 from Bryan Elliott  ---
Created attachment 98753
  --> https://bugs.kde.org/attachment.cgi?id=98753=edit
vol00+11

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

[kcharselect] [Bug 362603] Segmentation fault when search field cleared via backspace

[Bryan Elliott via KDE Bugzilla]

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

--- Comment #1 from Bryan Elliott  ---
Created attachment 98752
  --> https://bugs.kde.org/attachment.cgi?id=98752=edit
First part of core dump parchive

Extract with the others using:

par2 r core.xz.par2
xz -d core.xz

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

[umbrello] [Bug 361491] composition and aggregation toolbar icons are incorrect

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|REOPENED|RESOLVED

--- Comment #16 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #15)
> (In reply to Ralf Habacker from comment #12)
> > on another system with opensuse Leap 42.1 (KF5 based) I have, so I would 
> > say it is somehow related with KF5 libraries, but cannot say why and where.
> 
> umbrello5 on opensuse Leap 42.1 uses breeze icons
> https://build.opensuse.org/package/show/KDE:Frameworks5/breeze5-icons, which
> contains swapped svg icon. Git source is from
> https://quickgit.kde.org/?p=breeze-icons.
> git=tree=b628eb33870953f30f18b3b464cd1f3be4c793af=9ec402757e62bae12102
> d8a8851e9e5989e3645a=icons%2Factions%2F22

The kf5 related variant of the icon swapping bug is not a umbrello bug handled
by this bug tracker nor could be fixed at umbrello git repo. A bug report
and/or patch need to be filed at
https://phabricator.kde.org/project/profile/33/.

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

[kactivitymanagerd] [Bug 358516] KActivities: Database can not be opened in WAL mode. Check the SQLite version (required >3.7.0).

[Ivan Čukić via KDE Bugzilla]

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

--- Comment #11 from Ivan Čukić  ---
Cool, glad it got fixed, though it would be nicer if we knew the reason why
sqlite refused to create a wal database.

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

[kate] [Bug 362604] New: Kate on Windows doesn't recognize UTF-8 encoding, even using BOM

[Cristian Adam via KDE Bugzilla]

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

Bug ID: 362604
   Summary: Kate on Windows doesn't recognize UTF-8 encoding, even
using BOM
   Product: kate
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: encoding
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: cristian.a...@gmx.net

Installed Kate version 16.07.70 on Windows 10 and opened an UTF-8 encoded text
file.

File  was showing the pretty UTF-8 characters in ISO-8859-1 encoding.

Set the fallback encoding to UTF-8. Reopened the file, same story.

Clicked on adding the UTF-8 BOM to the file. Reopened the file, same story.

UTF-8 files are default also on Windows. I've created that text file using
Notepad++. I was at least expecting BOM to work. It didn't.

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

[akregator] [Bug 357495] Akregator krashes when loading some Slashdot articles

[Borden Rhodes via KDE Bugzilla]

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

Borden Rhodes  changed:

   What|Removed |Added

Product|kontact |akregator
  Component|general |internal browser

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

[kontact] [Bug 357495] Akregator krashes when loading some Slashdot articles

[Borden Rhodes via KDE Bugzilla]

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

--- Comment #5 from Borden Rhodes  ---
Created attachment 98751
  --> https://bugs.kde.org/attachment.cgi?id=98751=edit
Another crash dump. Not happening as often now, but still happening

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

[okular] [Bug 362446] Okular crashed wen open document with cyrillic characterset

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |INVALID

--- Comment #6 from Albert Astals Cid  ---
So you're using old poppler and it crashes and in a system with a newer poppler
it works. Update the old poppler.

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

[umbrello] [Bug 361491] composition and aggregation toolbar icons are incorrect

[Ralf Habacker via KDE Bugzilla]

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

--- Comment #15 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #12)
> on another system with opensuse Leap 42.1 (KF5 based) I have, so I would say 
> it is somehow related with KF5 libraries, but cannot say why and where.

umbrello5 on opensuse Leap 42.1 uses breeze icons
https://build.opensuse.org/package/show/KDE:Frameworks5/breeze5-icons, which
contains swapped svg icong. Git source is from
https://quickgit.kde.org/?p=breeze-icons.git=tree=b628eb33870953f30f18b3b464cd1f3be4c793af=9ec402757e62bae12102d8a8851e9e5989e3645a=icons%2Factions%2F22

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

[kcharselect] [Bug 362603] New: Segmentation fault when search field cleared via backspace

[Bryan Elliott via KDE Bugzilla]

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

Bug ID: 362603
   Summary: Segmentation fault when search field cleared via
backspace
   Product: kcharselect
   Version: v1.11
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: lai...@kde.org
  Reporter: fordi...@gmail.com

Testing sequence

1. Start kcharselect
* Expectation: User presented with application default view - in my case,
"European Alphabets / Basic Latin" - PASS
2. Focus the text box with the placeholder, "Enter a search term or character
here"
* Expectation: User is presented with carat, and can enter text - PASS
3. Type a search, e.g., "gamma"
* Expectation: As user types past three letters, set of characters from the
unicode spaces whose metadata match the search are placed into the character
list below - PASS
4. Tap [backspace] until the field is empty
* Expectation: As user removes letters, set of characters from the unicode
spaces whose metadata match the search are placed into the character list below
- PASS
* Expectation: As user removes third-to-last letter, user is returned to
the application default view - FAIL
* Actual result: Character list remains in searched state
* Expectation: As user removes last letter, placeholder is restored - FAIL
* Actual result: Application exits; only output is `Segmentation fault
(core dumped)`

Environment details:

* Distribution: Ubuntu 16.04
* uname: Linux 4.4.0-21-lowlatency
* kcharselect --version: 1.12
* kcharselect depndencies:
* libc6:  2.23-0ubuntu3
* libkf5configcore5:  5.18.0-0ubuntu1
* libkf5configgui5:  5.18.0-0ubuntu1
* libkf5configwidgets5:  5.18.0-0ubuntu1
* libkf5coreaddons5:  5.18.0-0ubuntu1
* libkf5i18n5:  5.18.0-0ubuntu1
* libkf5widgetsaddons5:  5.18.0-0ubuntu1
* libkf5xmlgui5:  5.18.0-0ubuntu1
* libqt5core5a:  5.5.1+dfsg-16ubuntu7
* libqt5gui5:  5.5.1+dfsg-16ubuntu7
* libqt5gui5-gles: n/a
* libqt5widgets5:  5.5.1+dfsg-16ubuntu7
* libstdc++6:  5.3.1-14ubuntu2

Cursory look at core dump (attached):

gdb `which kcharselect`
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kcharselect...(no debugging symbols
found)...done.
(gdb) core core
[New LWP 13816]
[New LWP 13817]
[New LWP 13818]
[New LWP 13819]
[New LWP 13821]
[New LWP 13820]
[New LWP 13822]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `kcharselect'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7ff5e5a3d51d in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
[Current thread is 1 (Thread 0x7ff5e6cb18c0 (LWP 13816))]

libQt5Widgets.so.5 belongs to Ubuntu package libqt5widgets5.  Without a trace
it's not clear it's at fault.

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

[plasmashell] [Bug 311799] Notification progress indicator makes Xorg eat up CPU

[Carsten Pfeiffer via KDE Bugzilla]

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

Carsten Pfeiffer  changed:

   What|Removed |Added

 CC||pfeif...@kde.org

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

[korgac] [Bug 362602] Kubuntu crashes on KMenu - Leave - New Session

[via KDE Bugzilla]

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

--- Comment #1 from koffeinfried...@gmail.com ---
Additional Info from kern.log:

May  2 21:33:00 x220 kernel: [ 7514.057372] [ cut here
]
May  2 21:33:00 x220 kernel: [ 7514.057422] WARNING: CPU: 3 PID: 1853 at
/build/linux-yplzxd/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1326
drm_wait_one_vblank+0x1b5/0x1c0 [drm]()
May  2 21:33:00 x220 kernel: [ 7514.057424] vblank wait timed out on crtc 0
May  2 21:33:00 x220 kernel: [ 7514.057494] Modules linked in: pci_stub
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm
binfmt_misc nls_iso8859_1 uvcvideo videobuf2_vmalloc videobuf2_memops
videobuf2_v4l2 videobuf2_core v4l2_common videodev media intel_rapl
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul
crc32_pclmul arc4 iwldvm mac80211 aesni_intel aes_x86_64 lrw gf128mul
glue_helper ablk_helper cryptd snd_hda_codec_hdmi snd_hda_codec_conexant
snd_hda_codec_generic input_leds joydev iwlwifi serio_raw snd_seq_midi
snd_seq_midi_event cfg80211 snd_hda_intel thinkpad_acpi snd_hda_codec nvram
snd_hda_core snd_hwdep snd_rawmidi snd_pcm mei_me mei snd_seq lpc_ich shpchp
snd_seq_device snd_timer snd soundcore mac_hid coretemp parport_pc ppdev lp
parport autofs4 i915 i2c_algo_bit psmouse drm_kms_helper syscopyarea
sysfillrect sysimgblt ahci e1000e fb_sys_fops sdhci_pci libahci drm sdhci ptp
pps_core wmi fjes video
May  2 21:33:00 x220 kernel: [ 7514.057515] CPU: 3 PID: 1853 Comm: Xorg
Tainted: G   OE   4.4.0-22-generic #38-Ubuntu
May  2 21:33:00 x220 kernel: [ 7514.057517] Hardware name: LENOVO
4293AF4/4293AF4, BIOS 8DET56WW (1.26 ) 12/01/2011
May  2 21:33:00 x220 kernel: [ 7514.057523]  0286 18b28fdd
8802114ff990 813e9c73
May  2 21:33:00 x220 kernel: [ 7514.057527]  8802114ff9d8 c0081b10
8802114ff9c8 81080fb2
May  2 21:33:00 x220 kernel: [ 7514.057530]  88021036e800 
 00066e17
May  2 21:33:00 x220 kernel: [ 7514.057531] Call Trace:
May  2 21:33:00 x220 kernel: [ 7514.057543]  []
dump_stack+0x63/0x90
May  2 21:33:00 x220 kernel: [ 7514.057551]  []
warn_slowpath_common+0x82/0xc0
May  2 21:33:00 x220 kernel: [ 7514.057556]  []
warn_slowpath_fmt+0x5c/0x80
May  2 21:33:00 x220 kernel: [ 7514.057564]  [] ?
finish_wait+0x55/0x70
May  2 21:33:00 x220 kernel: [ 7514.057593]  []
drm_wait_one_vblank+0x1b5/0x1c0 [drm]
May  2 21:33:00 x220 kernel: [ 7514.057600]  [] ?
wake_atomic_t_function+0x60/0x60
May  2 21:33:00 x220 kernel: [ 7514.057674]  []
intel_atomic_commit+0x43a/0x6f0 [i915]
May  2 21:33:00 x220 kernel: [ 7514.057713]  [] ?
drm_atomic_add_affected_connectors+0x27/0xf0 [drm]
May  2 21:33:00 x220 kernel: [ 7514.057746]  []
drm_atomic_commit+0x37/0x60 [drm]
May  2 21:33:00 x220 kernel: [ 7514.057766]  []
drm_fb_helper_pan_display+0x1de/0x240 [drm_kms_helper]
May  2 21:33:00 x220 kernel: [ 7514.057840]  []
intel_fbdev_pan_display+0x1a/0x60 [i915]
May  2 21:33:00 x220 kernel: [ 7514.057849]  []
fb_pan_display+0xcf/0x160
May  2 21:33:00 x220 kernel: [ 7514.057856]  []
bit_update_start+0x20/0x50
May  2 21:33:00 x220 kernel: [ 7514.057869]  []
fbcon_switch+0x3b0/0x640
May  2 21:33:00 x220 kernel: [ 7514.057874]  []
redraw_screen+0x1ac/0x2a0
May  2 21:33:00 x220 kernel: [ 7514.057878]  [] ?
sock_sendmsg+0x38/0x50
May  2 21:33:00 x220 kernel: [ 7514.057881]  []
complete_change_console+0x3f/0xe0
May  2 21:33:00 x220 kernel: [ 7514.057883]  []
vt_ioctl+0x710/0x12f0
May  2 21:33:00 x220 kernel: [ 7514.057917]  [] ?
drm_ioctl+0x189/0x540 [drm]
May  2 21:33:00 x220 kernel: [ 7514.057923]  []
tty_ioctl+0x35f/0xc40
May  2 21:33:00 x220 kernel: [ 7514.057931]  [] ?
handle_mm_fault+0xcdd/0x1820
May  2 21:33:00 x220 kernel: [ 7514.057936]  []
do_vfs_ioctl+0x29f/0x490
May  2 21:33:00 x220 kernel: [ 7514.057942]  [] ?
__do_page_fault+0x1b4/0x400
May  2 21:33:00 x220 kernel: [ 7514.057945]  []
SyS_ioctl+0x79/0x90
May  2 21:33:00 x220 kernel: [ 7514.057953]  []
entry_SYSCALL_64_fastpath+0x16/0x71
May  2 21:33:00 x220 kernel: [ 7514.057969] ---[ end trace 2b77d28725f2d89e
]---

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

[plasmashell] [Bug 361753] Activities marked “stopped” without reason

[Ivan Čukić via KDE Bugzilla]

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

--- Comment #3 from Ivan Čukić  ---
What happens if you do it for the stopped one, and not the starting one?

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

[kdenlive] [Bug 362591] git master: extract leaves group unmovable (immobile)

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit 8e6f71e815c590180b76e89b5d0d976f1516f375 by Jean-Baptiste Mardelle.
Committed on 02/05/2016 at 19:53.
Pushed by mardelle into branch 'master'.

Fix bug in group move

M  +15   -12   src/timeline/abstractgroupitem.cpp
M  +1-0src/timeline/customtrackview.cpp

http://commits.kde.org/kdenlive/8e6f71e815c590180b76e89b5d0d976f1516f375

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

[clazy] [Bug 362587] Don't warn for detach on QSequentialIterable and QAssociativeIterable

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/claz
   ||y/8384d74e37e1dcea80a2c9cf5
   ||24b9c0ef3be34d3
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Sergio Martins  ---
Git commit 8384d74e37e1dcea80a2c9cf524b9c0ef3be34d3 by Sergio Martins.
Committed on 02/05/2016 at 19:50.
Pushed by smartins into branch 'master'.

range-loop: Don't warn for non implicitly shared classes

M  +1-1checks/range-loop.cpp
M  +5-1tests/range-loop/main.cpp

http://commits.kde.org/clazy/8384d74e37e1dcea80a2c9cf524b9c0ef3be34d3

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

[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

[Tom Mittelstädt via KDE Bugzilla]

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

--- Comment #111 from Tom Mittelstädt  ---
Metko exactly describes  the behavior here.

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

[korgac] [Bug 362602] New: Kubuntu crashes on KMenu - Leave - New Session

[via KDE Bugzilla]

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

Bug ID: 362602
   Summary: Kubuntu crashes on KMenu - Leave - New Session
   Product: korgac
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: koffeinfried...@gmail.com

Application: korgac (5.1.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to change the session using KMenu - Leave - New Session, tried it
three times, because...
- Unusual behavior I noticed:
...after hitting it the first time, Kubuntu crashes totally (no virtual tty, no
reisub worked, had to hard reset).

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer Reminder Daemon (korgac), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f75ef985940 (LWP 5697))]

Thread 4 (Thread 0x7f75e4608700 (LWP 5710)):
#0  0x7f7604c3e9cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f75fe0c86c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f75fe084e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f75fe0852c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f75fe08542c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f7605785a9b in QEventDispatcherGlib::processEvents
(this=0x7f75d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f760572cdea in QEventLoop::exec (this=this@entry=0x7f75e4607c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f76055498a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7f760554e84e in QThreadPrivate::start (arg=0xa76290) at
thread/qthread_unix.cpp:331
#9  0x7f75fe5a66fa in start_thread (arg=0x7f75e4608700) at
pthread_create.c:333
#10 0x7f7604c4eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f75e3e07700 (LWP 5711)):
#0  0x7f75fe0c9a49 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f75fe0848b9 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f75fe08524b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f75fe08542c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f7605785a9b in QEventDispatcherGlib::processEvents
(this=0x7f75dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f760572cdea in QEventLoop::exec (this=this@entry=0x7f75e3e06c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f76055498a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f760554e84e in QThreadPrivate::start (arg=0xa4cd70) at
thread/qthread_unix.cpp:331
#8  0x7f75fe5a66fa in start_thread (arg=0x7f75e3e07700) at
pthread_create.c:333
#9  0x7f7604c4eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f75e2dcf700 (LWP 5893)):
#0  0x7f75fe08494a in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f75fe08524b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f75fe08542c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7605785a9b in QEventDispatcherGlib::processEvents
(this=0x7f75d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f760572cdea in QEventLoop::exec (this=this@entry=0x7f75e2dcec80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f76055498a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f760554e84e in QThreadPrivate::start (arg=0xdcd750) at
thread/qthread_unix.cpp:331
#7  0x7f75fe5a66fa in start_thread (arg=0x7f75e2dcf700) at
pthread_create.c:333
#8  0x7f7604c4eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f75ef985940 (LWP 5697)):
[KCrash Handler]
#6  0x7f76092d8c90 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5
#7  0x7f76092d4894 in
KCalCore::Calendar::setupRelations(QSharedPointer const&)
() from /usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5
#8  0x7f7609312bac in
KCalCore::MemoryCalendar::addIncidence(QSharedPointer
const&) () from /usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5
#9  0x7f7609cace9e in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiCalendar.so.5
#10 0x7f7609cba6f8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiCalendar.so.5
#11 0x7f7609cbba22 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5AkonadiCalendar.so.5
#12 0x7f760575de4f in QtPrivate::QSlotObjectBase::call (a=0x7ffcff8752a0,

[krita] [Bug 362600] Incorrect hue values of the colours displayed by Krita (splashscreen/interface/canvas) while using mesa

[LeStr4wberry via KDE Bugzilla]

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

LeStr4wberry  changed:

   What|Removed |Added

 CC||strawbe...@fejm.pl

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

[systemsettings] [Bug 362601] New: Information about your System

[Roland Schmidt via KDE Bugzilla]

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

Bug ID: 362601
   Summary: Information about your System
   Product: systemsettings
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: roland-schmid...@gmx.de

If i try to install or choose a display driver, there are no drivers list and i
cant use open gl because my display driver is not set properly.
I Use a Aspire V5-552g with Radeon Dual graphics hd 8750m.

Please Help

Reproducible: Always

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

[krita] [Bug 362600] New: Incorrect hue values of the colours displayed by Krita (splashscreen/interface/canvas) while using mesa

[LeStr4wberry via KDE Bugzilla]

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

Bug ID: 362600
   Summary: Incorrect hue values of the colours displayed by Krita
(splashscreen/interface/canvas) while using mesa
   Product: krita
   Version: 3.0 Beta
  Platform: Ubuntu Packages
   URL: http://imgur.com/iiBSNOT
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: strawbe...@fejm.pl

What is the problem: 
When using the most recent mesa drivers (Mesa 11.3.0-devel) the hue values of
the colours displayed by Krita, including the overview window and the splash
screen, seem to have been swapped. The whites/black/grays are not affected. The
way the canvas is affected depends on whether or not the OpenGL is turned on. 

Canvas behaviour with OpenGL turned on: 
- when an existing image is opened, the colours are displayed correctly, but
the overview window has their hue value swapped. The colour selector tool
displays the opposite colour from the one on the canvas (but if one attempts to
paint with the chosen colour, it is actually the right one; i.e. you pick a
blue colour, the selector tool seems to have picked a reddish colour, but if
you draw a line, it is in fact blue). 
- if you pick colours via the colour selector dockers, you end up painting with
a colour opposite in hue from the intended one.
Screenshot: 
http://imgur.com/RAKiVs5

Canvas behaviour with OpenGL turned off:
- when an existing image is opened, the colors are "swapped". Everything else
happens exactly the same as when OpenGL is turned on.
Screenshots: 
http://imgur.com/HhTBvTN
http://imgur.com/rjcpAIm

Is OCIO enabled: no, enabling/disabling doesn't affect the issue in any way.

Krita versions affected: only the appimage alpha/beta releases. The most recent
stable release (2.9.11) displays colours correctly. 

Is any other software affected?:  No, as far as I can tell. Tested:
GIMP/Pixeluvo/MyPaint/Inkscape/Karbon/etc..

Reproducible: Always

Steps to Reproduce:
1. Fresh install.
2. Install drivers from either the Oibaf or Padoka repository.
3. Start Krita (an appimage version).

Executing ppa-purge restores the colours to normal.

Actual Results:  
The hue values of colours displayed is the opposite from the correct one.

Expected Results:  
Correctly display colours.

System specs:
CPU: Pentium G2030
GPU: AMD HD 7770
RAM: 8GB
System: Xubuntu 15.10
Kernel: 4.5.0-040500-generic
Drivers: open source
OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE (DRM 2.43.0, LLVM 3.9.0)
OpenGL core profile version string: 4.2 (Core Profile) Mesa 11.3.0-devel
(padoka PPA)

The issue started occuring roughly at the time when the drivers in the Oibaf
and Padoka repositories started shipping Mesa 11.3.0-devel. It is present both
when using the drivers from the Oibaf repository and the Padoka repository.
Sadly, I don't have enough time to compile mesa from git to check for issues
there.

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

[digikam] [Bug 362023] Extremely slow metadata writing via maintenance

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #13 from Maik Qualmann  ---
This is are long waiting times, up to 5 seconds until a scan is completed for
one image. Disabling the scanning does not help, he would be rescheduled in any
case. Modification date or file size have changed and need to be updated in the
DB. Writing to the SQLite DB is the time problem. The SQLite DB to put on an
SSD drive is strongly recommended. Here are a few measured values, writing of
one image information in the DB this include read new information from image
(images on HDD - EXT4):

HDD:
SQLite: 180-270ms
internal MySQL: 40-70ms

SSD:
SQLite: 30-60ms

Are the images on an NTFS partition? Is also here the SQLite DB?

Maik

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

[kdepim] [Bug 362599] Some kmail filters are not applied

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Laurent Montel  ---
4.14.10 is a very old version (5.2 was released 2 weeks ago)
and this bug is fixed from long time.

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

[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

[Hatto Von Hatzfeld via KDE Bugzilla]

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

Hatto Von Hatzfeld  changed:

   What|Removed |Added

 CC||ha...@salesianer.de

--- Comment #110 from Hatto Von Hatzfeld  ---
May be related: https://bugs.kde.org/show_bug.cgi?id=362599

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

[kmail2] [Bug 357670] KMail 16.04.0: Composer auto-completion fails on first try

[via KDE Bugzilla]

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

--- Comment #7 from andreas.sturmlech...@gmail.com ---
Also happens for me in Applications 16.04.0 / Qt 5.5.1. The interesting bit: No
matter how often I retry to type in the name, via select+overwrite, it does not
work. If I use backspace to remove all but the first character, then type
again, it does not work. Only if I use backspace to get back to 'position 0'
does it then spawn the auto-completion popup as I begin to type again.

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

Weng Xuetian  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #12 from Weng Xuetian  ---
I'm afraid this is not completely fixed yet.

If I use region selection, the actual selected image is not the correct one.
It's clipped to 1/4 of the top-left of selected region on my screen setup. Can
you check it again? I think the clip region also need to be scaled.

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

[kdepim] [Bug 362599] Some kmail filters are not applied

[Hatto Von Hatzfeld via KDE Bugzilla]

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

Hatto Von Hatzfeld  changed:

   What|Removed |Added

 CC||ha...@salesianer.de

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

[Spectacle] [Bug 357022] Region selection screen does not take into account device pixel ratio

[Weng Xuetian via KDE Bugzilla]

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

--- Comment #13 from Weng Xuetian  ---
Comment 12 is based on Applications/16.04 branch.

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

[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time

[Joachim Wagner via KDE Bugzilla]

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

--- Comment #32 from Joachim Wagner  ---
(In reply to Martin Gräßlin from comment #30)
> According to the backtrace: you are using llvmpipe, which means OpenGL is
> emulated on the CPU. Of course that's not going to be efficient.

This is a default install of OpenSUSE 42.1 in a VM. Hardware graphics
acceleration is not an option. I've a few VMs and I'd like keep runlevel 5 as
it's handy to have a graphical login on occasions.

On a machine with hardware graphics acceleration, if the screen is re-drawn as
soon as the previous drawing is finished, this will still be a huge waste of
power on the GPU (not visible in the CPU usage stats of "top"). A simple way to
check this (without a power meter) may be to check how often per second the
screen is re-drawn.

Ideas for workarounds (in no particular order):
 (0) I tried setting screen energy saving to 2 minutes in KDE system settings
and locking the screen (rather than logging out) hoping that re-drawing would
stop after 2 minutes. No success. 
 (1) Send SIGSTOP/SIGCONT as needed (seems to work but have to remember why the
login screen is frozen)
 (2) Pick brains of cgroups expert how to apply cpu.cfs_period_us and
cpu.cfs_quota_us to this situation
 (3) Check source code and add sleep(0.02) in the re-drawing loop
 (4) Lower the blinking frequency of the cursor (if this is what causes the
re-drawing)
 (5) Learn how to configure a non-KDE login screen in OpenSUSE that can still
start KDE
 (6) Find out whether kscreenlocker can show a simple framebuffer-based login
screen

To the gdb experts here: Can I easily find out how often the screen is re-drawn
and how, for example by obtaining a list of functions and how often they have
been called in the last second or since the last query?

Any suggestions?

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

[kdeconnect] [Bug 362596] shared clipboard between two pc's and phone cause plasma UI freeze and app to crash

[via KDE Bugzilla]

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

--- Comment #2 from ghost53...@gmail.com ---
PC A and PC B , were connected with wired LAN, phone was on wifi.

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

[plasmashell] [Bug 362598] New: plasma-desktop crashes every start after upgrade from kubuntu 15.10 (from 15.04)

[Robert Auch via KDE Bugzilla]

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

Bug ID: 362598
   Summary: plasma-desktop crashes every start after upgrade from
kubuntu 15.10 (from 15.04)
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ra...@totalnetsolutions.net
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I had completed a "do-release-upgrade" from Kubuntu 15.10.  The week previous I
had upgraded from Kubuntu 15.04 via the same process.  When I log in as my main
user, plasma-desktop crashes, and will not restart.
- Custom settings of the application:
I have deleted ~/.config/plasma* and the problem still exists. I'm going to go
through other .config/kde and related files.

This *may* be related to bumblebee configuration, since I saw an error about
nvidia_340, but can't find where that error went.

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".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7f5de2c15900 (LWP 9066))]

Thread 7 (Thread 0x7f5dc33ea700 (LWP 9071)):
#0  0x7f5ddd32ce8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5dda0c231c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5dda0c242c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5dddc59a9b in QEventDispatcherGlib::processEvents
(this=0x7f5dbc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f5dddc00dea in QEventLoop::exec (this=this@entry=0x7f5dc33e9ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f5ddda1d8a4 in QThread::exec (this=this@entry=0x1888530) at
thread/qthread.cpp:503
#6  0x7f5de02c53c5 in QQmlThreadPrivate::run (this=0x1888530) at
qml/ftw/qqmlthread.cpp:141
#7  0x7f5ddda2284e in QThreadPrivate::start (arg=0x1888530) at
thread/qthread_unix.cpp:331
#8  0x7f5ddcb0f6fa in start_thread (arg=0x7f5dc33ea700) at
pthread_create.c:333
#9  0x7f5ddd338b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f5db9930700 (LWP 9075)):
#0  0x7f5ddd3289cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5dd5ec7f45 in ?? () from
/usr/lib/nvidia-340/tls/libnvidia-tls.so.340.96
#2  0x7f5dda1056c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5dda0c1e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f5dda0c22c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f5dda0c242c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f5dddc59a9b in QEventDispatcherGlib::processEvents
(this=0x7f5db40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7f5dddc00dea in QEventLoop::exec (this=this@entry=0x7f5db992fca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7f5ddda1d8a4 in QThread::exec (this=this@entry=0x19be830) at
thread/qthread.cpp:503
#9  0x7f5de02c53c5 in QQmlThreadPrivate::run (this=0x19be830) at
qml/ftw/qqmlthread.cpp:141
#10 0x7f5ddda2284e in QThreadPrivate::start (arg=0x19be830) at
thread/qthread_unix.cpp:331
#11 0x7f5ddcb0f6fa in start_thread (arg=0x7f5db9930700) at
pthread_create.c:333
#12 0x7f5ddd338b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f5db308f700 (LWP 9076)):
#0  0x7ffe643de9a9 in ?? ()
#1  0x7ffe643decd5 in clock_gettime ()
#2  0x7f5ddd346fb6 in __GI___clock_gettime (clock_id=1,
tp=tp@entry=0x7f5db308ea10) at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f5dddad2c16 in qt_clock_gettime (ts=0x7f5db308ea10, clock=) at tools/qelapsedtimer_unix.cpp:105
#4  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#5  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#6  0x7f5dddc57529 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f5dac002ed0) at kernel/qtimerinfo_unix.cpp:84
#7  0x7f5dddc57a95 in QTimerInfoList::timerWait (this=0x7f5dac002ed0,
tm=...) at kernel/qtimerinfo_unix.cpp:381
#8  0x7f5dddc58e7e in timerSourcePrepareHelper (timeout=0x7f5db308eae4,
src=) at kernel/qeventdispatcher_glib.cpp:127
#9  timerSourcePrepare (source=, timeout=0x7f5db308eae4) at
kernel/qeventdispatcher_glib.cpp:160
#10 0x7f5dda0c18ad in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 

[plasmashell] [Bug 361753] Activities marked “stopped” without reason

[Denis Kuplyakov via KDE Bugzilla]

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

--- Comment #2 from Denis Kuplyakov  ---
Hello Ivan!

Maybe my output also can be helpfull.  Problematic activity is the one that
[STARTING].

Here is the output:

21:17:31  ~/tmp 
$ source kamd-functions 

 21:17:34  ~/tmp 
$ kamd_listactivities 
Service version: 6.2.0
[STOPPED] de709d6c-3d25-45af-9699-197cb2371fbd Technoblabla
(preferences-activities)
[RUNNING] 2fcababc-b090-4846-932e-79887cc431b7 VideoTracking
(preferences-activities)
[STARTING] 3eff8dee-079c-49e8-ba76-0fb7d83feb6c Диплом (Написание диплома и
презентации, )
[CURRENT] 8947586a-ed78-472e-a2e3-14de917ccc54 Стандратная
(preferences-activities)

 21:17:39  ~/tmp 
$ qdbus org.kde.ActivityManager /ActivityManager/Activities StartActivity
3eff8dee-079c-49e8-ba76-0fb7d83feb6c


 21:18:41  ~/tmp 
$ kamd_listactivities 
Service version: 6.2.0
[STOPPED] de709d6c-3d25-45af-9699-197cb2371fbd Technblabla
(preferences-activities)
[RUNNING] 2fcababc-b090-4846-932e-79887cc431b7 VideoTracking
(preferences-activities)
[STARTING] 3eff8dee-079c-49e8-ba76-0fb7d83feb6c Диплом (Написание диплома и
презентации, )
[CURRENT] 8947586a-ed78-472e-a2e3-14de917ccc54 Стандратная
(preferences-activities)

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

[kdeconnect] [Bug 362596] shared clipboard between two pc's and phone cause plasma UI freeze and app to crash

[via KDE Bugzilla]

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

--- Comment #1 from ghost53...@gmail.com ---
Created attachment 98749
  --> https://bugs.kde.org/attachment.cgi?id=98749=edit
Journalctl logs of pc A and pc B.

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

[systemsettings] [Bug 362597] New: QWidget::paintEngine: Should no longer be called

[Peter C . Trenholme via KDE Bugzilla]

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

Bug ID: 362597
   Summary: QWidget::paintEngine: Should no longer be called
   Product: systemsettings
   Version: 5.6.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: ptrenho...@gmail.com

QWidget::paintEngine: Should no longer be called displayed when systemsettings5
is invoked from a command line:

$ systemsettings5 
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called

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

[kwin] [Bug 361935] Desktop Effects were restarted due to a graphics reset...

[PGillespie via KDE Bugzilla]

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

--- Comment #12 from PGillespie  ---
//wtf is so hard to understand about "the graphics reset messages do not
describe the process crash"?//

And as to wtf's so hard about it? I'm not a developer/programmer or hacker. I'm
a builder and writer who used to work as a tech support technician in the early
1990's when Windows vs. DOS was still open to debate. So yeah, it's hard to
understand. 

I've spent several hours this morning contributing my time reporting
bugs/problems I'm experiencing with KDE/Kubuntu 16.04, having very little
knowledge beyond the GUI. Nonetheless, I'm trying to educate myself in the use
of gdb and bug reporting so that I waste less of my time and yours.  

FYI: I enabled dri3 and used sna. Didn't help. And Intel microcode is
installed. 

"it's not a bug at all - kwin noticed that your gpu too a nap and restarts the
compositor."

Or doesn't. How this isn't a bug is beyond me. So it's perfectly normal for
KDE's compositor to crash? 

Okay.

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

[kdeconnect] [Bug 362596] New: shared clipboard between two pc's and phone cause plasma UI freeze and app to crash

[via KDE Bugzilla]

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

Bug ID: 362596
   Summary: shared clipboard between two pc's and phone cause
plasma UI freeze and app to crash
   Product: kdeconnect
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: ghost53...@gmail.com

After copying something to clipboard on PC A my plasmashell froze. I was unable
to right click on the desktop or bring up  krunner with ALT + F2 to start an
app, alt-tab still continued to work. All other programs still worked, firefox
did not freeze nor konsole or hexchat that was open at the time. I could not
copy and paste. I tried to stop and start plasmashell but it did not work,
instead I was left with a blank desktop no panel showed up.  

The logs showed QXcbClipboard: SelectionRequest too old, and 
QXcbClipboard::setMimeData: Cannot set X11 selection owner. 

On PC  B I noticed the lock screen froze as well, used loginctl to unlock it
and the dekstop was also frozen. The android app crashed as well. 



Reproducible: Always

Steps to Reproduce:
1. Pair PC A to phone
2. Pair PC B to phone
3. Pair PC B to PC A
4. Copy text to clipboard.
5. wait and watch logs as they get filled with an error and plasma shell
freezes 

Actual Results:  
Plasmashell and krunner freeze unable to open or be used. 

Expected Results:  
Plasmashell should not crash and krunner should still function 

On both pc's the log shows the same error at the same time, there is a 1 minute
difference in hw clock between the two. so the logs should be treated as the
same time frame because they are.

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

[umbrello] [Bug 173777] import from java code don't read abstract classes

[Enzo Cappa via KDE Bugzilla]

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

--- Comment #2 from Enzo Cappa  ---
This bug is more than 7 years old.  I don't know if it's still valid, and I'm
not using umbrello anymore. I can't provide any further feedback. Feel free to
close it if nobody else is interested.

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

[okular] [Bug 362446] Okular crashed wen open document with cyrillic characterset

[Theodor Mueller via KDE Bugzilla]

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

--- Comment #5 from Theodor Mueller  ---
on he working system the following libraries from poppler are installed 
libpoppler-glib.so.8 -> libpoppler-glib.so.8.6.0
libpoppler-glib.so.8.6.0
libpoppler-qt4.so.4 -> libpoppler-qt4.so.4.4.0
libpoppler-qt4.so.4.4.0
libpoppler.so.46 -> libpoppler.so.46.0.0
libpoppler.so.46.0.0
the version of ocular on that system is 0.21.3
the version of KDE is 4.14.9
the distribution is opensuse 42.1
teh kernel is 4.1.20-11-default

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

[amarok] [Bug 362497] Amarok plante

[cisco via KDE Bugzilla]

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

--- Comment #2 from cisco  ---
   Hello, 

I remind you that Amarok was working perfectly before the update, so nothing
manquait.
The updates planted Amarok.Cordialement.

cisco.

> From: bugzilla_nore...@kde.org
> To: kid_ci...@hotmail.com
> Subject: [amarok] [Bug 362497] Amarok plante
> Date: Sat, 30 Apr 2016 10:25:59 +
> 
> https://bugs.kde.org/show_bug.cgi?id=362497
> 
> Myriam Schweingruber  changed:
> 
>What|Removed |Added
> 
>  Status|UNCONFIRMED |NEEDSINFO
>  Resolution|--- |BACKTRACE
>Platform|Compiled Sources|Mageia RPMs
> 
> --- Comment #1 from Myriam Schweingruber  ---
> What did you remove in your upgrades? The crash report is unfortunately
> unusable, as it does not have debugging symbols for Amarok and its
> dependencies. Please install those and provide a better backtrace. See also
> https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Mageia
> 
> FWIW: the problem is unlikely to be in Amarok, as it happened after upgrades
> you performed, and nothing was upgraded recently in either Amarok or its
> dependencies. Please check you really have all mandatory dependencies,
> especially the correct Phonon and phonon backend packages for a KDE4 based
> application. The Qt5 versions will not work.
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
   =

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

[krita] [Bug 361911] Overriding hotkeys won't work (conflict of new hotkey with old one)

[ocumo via KDE Bugzilla]

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

ocumo  changed:

   What|Removed |Added

 CC||yhcdr-devst...@yahoo.com

--- Comment #3 from ocumo  ---
I can confirm that this problem is happening in
krita-3.0-Beta-master-no_gmic-4336582-x86_64.appimage running in Kubuntu 16.04
.

It doesn't seem to be possible to override default shortcuts, even creating new
templates, saving or loading other existing templates that are working in Krita
stable otherwise.

In addition, maybe a minor thing, but in the above mentioned 3.0 pre version,
there is no  'Configure Shortcuts' in the 'Settings' menu as it exists in Krita
stable.   If that would be a design decision rather than a bug, then it would
be another topic, but then the "Ambiguous shortcut detected" dialog that pops
up when we are trying to override an existing one, has to be updated, as its
current text is:
Ambiguous shortcut detected
The key sequence 'W' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.

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

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

[Xapient via KDE Bugzilla]

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

--- Comment #47 from Xapient  ---
i just testet qt5.6.0 - still the same..  plasma thinks the sleeping screen is
gone forever .. 
i cant reproduce this everytime..  

tried to reconfigure the screens but nothing ...  only restarting plasma helps

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

[kleopatra] [Bug 322966] Problem with Kleopatra 2.1.1 on Ubuntu 13.04 | Result of self-test at program start: unexpected error

[Vincent Fortier via KDE Bugzilla]

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

Vincent Fortier  changed:

   What|Removed |Added

 CC||th0...@gmail.com

--- Comment #7 from Vincent Fortier  ---
I believe the issue is still on-going:
https://bugs.launchpad.net/kubuntu-ppa/+bug/684902

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

[krita] [Bug 352381] A request for zoom and radial blur option in blur filter.

[Adam Druzd via KDE Bugzilla]

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

Adam Druzd  changed:

   What|Removed |Added

 CC||adam.dr...@gmail.com

--- Comment #3 from Adam Druzd  ---
As I said on g+ group I too like to have this filter...

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

[kmail2] [Bug 78629] MS Exchange mail support

[Krzysztof Nowicki via KDE Bugzilla]

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

--- Comment #56 from Krzysztof Nowicki  ---
Do you have a GitHub account?

I can raise this as a bug and we'll continue over there rather than trashing
this bug report with irrelevant comments.

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

[kdevelop] [Bug 344192] Crash while trying to save a file as an already open file

[deoakshay via KDE Bugzilla]

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

deoakshay  changed:

   What|Removed |Added

 CC||ad...@mail.csuchico.edu

--- Comment #5 from deoakshay  ---
Hello everyone, I am a beginner in open source development and would like to
contribute. I was wondering if I could contribute to this bug?

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

[KScreen] [Bug 351256] Way to distinguish more monitors with the same vendor/model label

[Jason Tibbitts via KDE Bugzilla]

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

--- Comment #3 from Jason Tibbitts  ---
Yes, of course I can see that the description changes down below when I click
each one, and to be honest because I have to do this so often I have remembered
exactly which one in the stack needs to be dragged where.  But it did, sadly,
take me a while to figure out how to tell them apart.

I'm sure this is a rather simple fix, but I haven't done any C++ work since
that class I took in 1987.

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

[umbrello] [Bug 361491] composition and aggregation toolbar icons are incorrect

[Ralf Habacker via KDE Bugzilla]

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

--- Comment #14 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #13)
> Illegal icon group:  7
I remember sawing this warnings in older kdelibs version which may indicate an
icon cache issue also for 2.16.0

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

[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?

[PGillespie via KDE Bugzilla]

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

--- Comment #4 from PGillespie  ---
Okay. I attached GDB to plasmashell and the appropriate PID. I suspended and
resumed twice while GDB was attached. 

The KDE panel locked up after the second suspend. Had to kill GDB and restart
plasmashell in order use it. The backtrace follows:

 Thread 16 (Thread 0x7fa84861e700 (LWP 8524)):
#0  0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa85bacfc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fa85bad18d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fa84a76c629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fa85810084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8571ed6fa in start_thread (arg=0x7fa84861e700) at
pthread_create.c:333
#6  0x7fa857a16b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fa845e10700 (LWP 8525)):
#0  0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa8547a031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8547a042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa858337a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa8582dedea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8580fb8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa85a9a33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa85810084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa8571ed6fa in start_thread (arg=0x7fa845e10700) at
pthread_create.c:333
#9  0x7fa857a16b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fa83664c700 (LWP 8526)):
#0  0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa8547a031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8547a042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa858337a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa8582dedea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8580fb8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa85a9a33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa85810084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
---Type  to continue, or q  to quit---
#8  0x7fa8571ed6fa in start_thread (arg=0x7fa83664c700) at
pthread_create.c:333
#9  0x7fa857a16b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fa82700 (LWP 8527)):
#0  0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa8547a031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8547a042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa858337a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa8582dedea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8580fb8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa85a9a33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa85810084e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa8571ed6fa in start_thread (arg=0x7fa82700) at
pthread_create.c:333
#9  0x7fa857a16b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fa82edf6700 (LWP 8528)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa85cd48bd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa85cd48c19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa8571ed6fa in start_thread (arg=0x7fa82edf6700) at
pthread_create.c:333
#4  0x7fa857a16b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7fa79ed45700 (LWP 8532)):
#0  0x7fa857a0ae8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa8547a031c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa8547a042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa858337a7f in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa8582dedea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa8580fb8a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa85b329ed6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  

[umbrello] [Bug 361491] composition and aggregation toolbar icons are incorrect

[Ralf Habacker via KDE Bugzilla]

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

--- Comment #13 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #12)
> on another system with opensuse Leap 42.1 (KF5 based) I have,
> so I would say it is somehow related with KF5 libraries, but cannot say why 
> and where.
> running umbrello from framework-branches returns 

Illegal icon group:  7
Illegal icon group:  7
Illegal icon group:  7
Illegal icon group:  7
Illegal icon group:  7
Overwriting existing old cached entry due to collision.

The last message comes from icon cache, in source
kcoreaddons/src/lib/caching/kshareddatacache.cpp:1478

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

[kmail2] [Bug 78629] MS Exchange mail support

[Vincent Fortier via KDE Bugzilla]

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

--- Comment #55 from Vincent Fortier  ---
Tried it, would have been to simple :)

I removed/recreated the kmail config and also tried the following
https://docs.kde.org/trunk5/en/kdepim/kmail/clean-start-after-a-failed-migration.html
Also tried streaming notifications vs pool every x.y mins.
Still no folders and no luck sadly.

Starting kmail from a console gets the following output:
$ kmail
"KMail Kernel ETM"
()
""
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
"/subscriber/kmail2_17230_Rt0qZi"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
"/subscriber/kmail2_17230_6rPTQz"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
"/subscriber/kmail2_17230_G17QQ6"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
"/subscriber/kmail2_17230_BzULk8"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
"/subscriber/kmail2_17230_dMPgUN"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
"/subscriber/kmail2_17230_VBMxvj"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
"/subscriber/kmail2_17230_ZB5RQu"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
"/subscriber/kmail2_17230_4JGo60"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
this does not work on a KActionCollection containing actions!
done
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
org.kde.akonadi.ETM: GEN true false false
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM:
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
Connected to "Akonadi" , using protocol version 52
Server says: "Not Really IMAP server"
"/subscriber/kmail2_17230_NLIKyV"
connectToServer "/tmp/akonadi-fortierv.BQzl2m/akonadiserver.socket"
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4538
Could not resolve property : linearGradient4588
Could not resolve property : linearGradient4554
Could not resolve property : linearGradient4572
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : linearGradient4532
Could not resolve property : linearGradient4582
Could not resolve property : linearGradient4566
Could not resolve property : linearGradient4548
Could not resolve property : 

[kdevelop] [Bug 360539] Projects Toolbar hidden state is not saved

[deoakshay via KDE Bugzilla]

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

deoakshay  changed:

   What|Removed |Added

 CC||ad...@mail.csuchico.edu

--- Comment #3 from deoakshay  ---
Hello I am willing to contribute for this? Has this been solved or can I work
on it?

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

[digikam] [Bug 362595] New: it crashes on startup

[David Portabella via KDE Bugzilla]

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

Bug ID: 362595
   Summary: it crashes on startup
   Product: digikam
   Version: 4.13.0
  Platform: Other
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: david.portabe...@gmail.com

OSX 10.10.5. 
package: brew
$ brew install Caskroom/cask/digikam

I start Digikam, it scans the files, the main GUI appears. it crashes.


Reproducible: Always

Steps to Reproduce:
Start Digikam, it scans the files, the main GUI appears. it crashes.

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

[krita] [Bug 361581] Brush tool options do not load on startup or while opening new file

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||dimul...@gmail.com
 Resolution|--- |FIXED

--- Comment #2 from Dmitry Kazakov  ---
Fixed in https://phabricator.kde.org/rKRITA3ea697da75d9

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

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

[Xapient via KDE Bugzilla]

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

--- Comment #46 from Xapient  ---
is this the same bug and reason for this behaviour? 

https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1548766

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

[dolphin] [Bug 362594] New: xubuntu 16.4 no tool tips in dolphin 4

[jp-willm via KDE Bugzilla]

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

Bug ID: 362594
   Summary: xubuntu 16.4 no tool tips in dolphin 4
   Product: dolphin
   Version: 4.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: tooltip
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: jp.wi...@gmail.com

We use dolphin4 in xubuntu but we can not upgrade to 16.4 because there are no
tool tips in dolphin4

Reproducible: Always

Steps to Reproduce:
1. hower mouse cursor over the icons 
2. 
3.

Actual Results:  
no too tips (meta data, exif data's)

Expected Results:  
pop up showing picture information (exif data's)

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

[krita] [Bug 361701] Hand cursor won't go away if mirroring is turned off

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Dmitry Kazakov  ---
The bug has been fixed by my recent commit:
https://phabricator.kde.org/rKRITA3d152322866a

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

[kaddressbook] [Bug 356995] Unable to move or copy Contacts between Folders or Address Books

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
   Version Fixed In||5.2.1
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Laurent Montel  ---
fixed in 5.2.1

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

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

[Xapient via KDE Bugzilla]

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

--- Comment #45 from Xapient  ---
well.. it is no displayport issue either..  i'm using dvi and hdmi ports and
the same thing happens..

a monitor goes to sleep (or is turned off) and plasma says bye bye (on
dualscreen it sometimes happens that one of the two screens still shows the
background and is reacting to rightclick.. that's the weirdest thing of all - a
partial crash? )


i'm really stuck here..  on 3 notebooks and 8 dell machines i testet the newest
version there is no problem at all...

so what exactly is the reason for this bug ? !  and why didn't it happen on
kubuntu 15.10 ?

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

[plasmashell] [Bug 359919] plasma-org.kde.plasma.desktop-appletsrc not updated when removing activities

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

   Assignee|ivan.cu...@kde.org  |k...@davidedmundson.co.uk
  Component|Activity Switcher   |general

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

[dolphin] [Bug 362593] New: allow terminal to be placed in right pane

[via KDE Bugzilla]

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

Bug ID: 362593
   Summary: allow terminal to be placed in right pane
   Product: dolphin
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: panels: terminal
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: w...@ahill.io

The terminal is an awesome feature in Dolphin, truly, very awesome!  But the
limitation of only top/bottom placement is unfortunate, it significantly limits
what I can use that terminal pane for.  Dolphin could be a great little command
center for me if its terminal was more useful, but right now the terminal is
about 4X wider than it is tall and it's just not efficient use of space; the
documents I want to edit don't fit in the space unless I resize it and make the
normal GUI view unusably small, resizing the pane big to small to big every
time is so cumbersome that I just don't utilize the Dolphin and its terminal
very much.  But I want to.  I *really* want to.  Can you please allow the
terminal to be docked in the right pane?

I believe this is the line:
https://github.com/KDE/dolphin/blob/master/src/dolphinmainwindow.cpp#L1211

Reproducible: Always

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

[frameworks-kactivities] [Bug 360339] Plasma Crash on startup

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
 Ever confirmed|0   |1

-- 
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

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

   Assignee|ivan.cu...@kde.org  |k...@davidedmundson.co.uk
 CC||bhus...@gmail.com
  Component|Activity Switcher   |general

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

[plasmashell] [Bug 361753] Activities marked “stopped” without reason

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Ivan Čukić  ---
Hi Tommi,

Can you do the following, so that we can see what is going on here. Go to
https://quickgit.kde.org/?p=kactivities.git=blob=f4951063216d995695240abe117369c61c84d078=e476be5250a369e899d1b1c9775671d3a245b7f9=contrib%2Fzsh%2Fkamd-functions
and download that file. It defines a couple of nice convenient functions for
ZSH (it might need minor modifications to be used with BASH, I haven't tried).

Open konsole, and do
source kamd-functions
and then, in the same konsole session:
kamd_listactivities

It should show all the activities, along with their states. Copy the id of one
of the stopped ones, and try to start it from the terminal:
qdbus org.kde.ActivityManager /ActivityManager/Activities StartActivity
PASTE_THE_ID_HERE

Then run kamd_listactivities again. Did anything change?

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

[frameworks-kactivities] [Bug 361658] kactivitymanage segfault (libQt5Sql.so.5.4.2) when running nomachines in KDE (other desktops work)

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

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

--- Comment #1 from Ivan Čukić  ---
Dear Morgan,

Your X11 session crashes - I would guess it is a driver issue triggered by
nomachine and kwin (or plasma, since it is also now a heavy opengl user).

ActivityManager just seems like a culprit since it gets terminated by the
session that crashes, and then a QtSQL bug gets triggered making kamd crash.

Anyhow, I'd advise you to try starting nomachine without compositing enabled in
kwin, or even trying to temporarily replace kwin with whatever windowing
manager lxde uses *inside* the plasma session.

An alternative could be to use lxde, and start a few kde applications
(including plasma) in order to try to triage what exactly triggers the crash.

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

[kmail2] [Bug 362572] Microformat adoption

[Laurent Montel via KDE Bugzilla]

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

--- Comment #4 from Laurent Montel  ---
I want a real example :)
Not a example from potential application :)

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