[klipper] [Bug 362727] When Keepassx clears clipboard with password, he stays in Klipper

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
I'm sorry, but that is just not possible from a technical point of view. In the
days before becoming the maintainer of klipper and understanding how this
technically works I reported a similar bug 156547.

Technically that's just not possible. We don't get a signal "don't save this
password", we just get a "hey the new clipboard content is an empty string". We
don't have any meta information about the clipboard content. We don't know that
it is a password, we don't know which application send it, and so on.

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

[krita] [Bug 362134] Alternative shortcuts breaks primary shortcuts in Krita 3.0 alpha.

[Tyson Tan via KDE Bugzilla]

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

--- Comment #6 from Tyson Tan  ---
Yes, it's fixed. Thank you everyone!

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

[krita] [Bug 362730] New: Instant preview makes Ctrl+LMB color picking unresponsive

[Tyson Tan via KDE Bugzilla]

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

Bug ID: 362730
   Summary: Instant preview makes Ctrl+LMB color picking
unresponsive
   Product: krita
   Version: 3.0 Beta
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: OpenGL Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: tyson...@mail.com

In Krita 3.0 Beta, when Instant preview is enabled, Ctrl+LMB to pick color is
not very responsive. I often need to keep Ctrl+LMB pressed down, wait for a
second until a new color is picked. This pretty much makes Ctrl+LMB color
picking useless.

It gets more obvious when:
1) the picture is big;
2) a big brush stroke was just applied (and probably still not finish drawing);
3) a brush stroke was just undone.

It feels like Qt OpenGL queue congestion to me.

Instant Preview is causing so much problem now:
1) Undo/Redo has visual glitches;
2) This bug;
3) Overall slowdown and more.

Are these normal by design for enabling instant preview? Or they are issues to
be addressed?

Reproducible: Always

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

[kdevelop] [Bug 333759] "Variables" tool view sometimes not in sync with Frame Stack view

[Aetf via KDE Bugzilla]

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

Aetf <7437...@gmail.com> changed:

   What|Removed |Added

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

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

[okular] [Bug 341734] request for: save multi-tab session as named session, select session from menu in new instance

[Gaba via KDE Bugzilla]

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

--- Comment #2 from Gaba  ---
Has there been any advances on this feature? It would be extremely helpful for
those of us that open multiple documents to work at once.

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

[okular] [Bug 341734] request for: save multi-tab session as named session, select session from menu in new instance

[Gaba via KDE Bugzilla]

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

Gaba  changed:

   What|Removed |Added

 CC||gabrielper...@gmail.com

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

[frameworks-baloo] [Bug 362333] baloo_file Closed Unexpectedly a short while after starting KDE

[Steve Youngs via KDE Bugzilla]

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

--- Comment #1 from Steve Youngs  ---
I seem to have found a way around this.

`balooctl status' was telling me that there wasn't any files indexed which made
me think that this bug was biting pretty early in the process and it wasn't
even getting to the initial indexing stage.  I tentatively tried 'balooctl
index somedir/*' and that gave me a few files in the index.

I then decided (probably foolishly) that if I could manually index one
directory, why not do the whole dang lot, so...

  $ find ${HOME} -type d -exec sh -c 'balooctl index {}/*' \;

That took a LONG time, I can't tell you exactly how long because I stopped it
after it went beyond 24 hours!  And it hit a few bumps along the way.  Had a
few of

"ASSERT failure in PositionDB::put: "MDB_MAP_FULL: Environment mapsize limit
reached", file /usr/src/kde/kf5src/frameworks/baloo/src/engine/positiondb.cpp,
line 80 "

At this point I had just on 170K files in the index (indexer wasn't running). 
I crossed my fingers and restarted KDE.  The bug hit just like always.  Then it
occurred to me that the bug was preventing the initial indexing, but I had
pretty much done that manually now.  ~/.config/baloofilerc hinted that the
initial indexing had not been done.  So maybe all I had to do was change the
config...

  $ sed -i 's/\(first run=\)true/\1false/' ~/.config/baloofilerc

More finger crossing, another KDE restart.  This time... success!  Didn't get
the crash, and baloo seems to be functioning properly.  Searching via krunner,
or baloosearch is working just how I'd expect.  balooshow is returning good
info.  New files are getting added to the index automatically, likewise deleted
files are being removed.

  $ balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexed 170229 / 170229 files
Current size of index is 1,021.54 MiB

I am now happy and this bug is no longer affecting me.

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

[plasma-nm] [Bug 362729] New: Cannot connect to OpenConnect VPN with username/password

[Joe via KDE Bugzilla]

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

Bug ID: 362729
   Summary: Cannot connect to OpenConnect VPN with
username/password
   Product: plasma-nm
   Version: 5.6.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: jchevar...@gmail.com
CC: lu...@kde.org

I am having trouble using plasma-nm to connect to an openconnect VPN. The
connection works fine when using the command line openconnect. It is
username/password auth based (so just url/gateway + username/password). When
connecting via plasma-nm, I do not get an authentication popup to enter my
credentials. 

>From the connection log on the GUI (note IP/endpoints are redacted):

POST https://x.y.z/
Attempting to connect to server 1.1.1.1:443
SSL negotiation with x.y.z
Connected to HTTPS on x.y.z
Got HTTP response: HTTP/1.1 302 Found
GET https://x.y.z/
Attempting to connect to server 1.1.1.1:443
SSL negotiation with x.y.z
Connected to HTTPS on x.y.z
Got HTTP response: HTTP/1.1 302 Found
GET https://x.y.z/dana-na/auth/url_default/welcome.cgi
SSL negotiation with x.y.z
Connected to HTTPS on x.y.z
XML response has no "auth" node



Reproducible: Always

Steps to Reproduce:
1. Create new openconnect VPN connection
2. Enter Gateway of x.y.z
3. Save
4. Go to Connect
5. Press connect button
6. Connection Error

Actual Results:  
Notification Popup:  Necessary secrets for the VPN connection were not
provided.

In log: XML response has no "auth" node

Expected Results:  
I would expect a username/password authentication dialog to popup and then have
the VPN Connection created.

I am on Arch Linux with the latest testing packages - QT 5.6.0, Frameworks
5.21.0, Plasma 5.6.3.

Both networkmanager and networkmanager-openconnect are version 1.2.0.

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

[frameworks-plasma] [Bug 355592] IconItem does not support non-square icons

[Kethen Chui via KDE Bugzilla]

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

--- Comment #11 from Kethen Chui  ---
Created attachment 98801
  --> https://bugs.kde.org/attachment.cgi?id=98801=edit
screenshot

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

[Phonon] [Bug 337276] fully-qualified audio notifications no longer play

[Rex Dieter via KDE Bugzilla]

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

--- Comment #16 from Rex Dieter  ---
Did test notifications from 'kcmshell4 kcmnotify' both relative and full path
audio is fine, so nevermind

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

[Phonon] [Bug 337276] fully-qualified audio notifications no longer play

[Rex Dieter via KDE Bugzilla]

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

--- Comment #15 from Rex Dieter  ---
See also:
knotifyconfig : https://git.reviewboard.kde.org/r/127829/
knotifications: https://git.reviewboard.kde.org/r/127830

Harald, may related kde4 components (like kdelibs/libknotifyconfig) need fixing
too?

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

[frameworks-plasma] [Bug 355592] IconItem does not support non-square icons

[Kethen Chui via KDE Bugzilla]

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

--- Comment #10 from Kethen Chui  ---
Problem exists in a fresh install of ubuntu 16.04
Plasma 5.5.5

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

[plasmashell] [Bug 362679] Preview in folder view stretched and not recognizable

[Kethen Chui via KDE Bugzilla]

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

Kethen Chui  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Kethen Chui  ---
Just found a confirmed bug under a different product

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

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

[frameworks-plasma] [Bug 355592] IconItem does not support non-square icons

[Kethen Chui via KDE Bugzilla]

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

Kethen Chui  changed:

   What|Removed |Added

 CC||scootaloo...@gmail.com

--- Comment #9 from Kethen Chui  ---
*** Bug 362679 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 362728] list of Mails in a folder not readable (white on white)

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #1 from Herr Schmidt  ---
Created attachment 98800
  --> https://bugs.kde.org/attachment.cgi?id=98800=edit
Here you can see clearly that the titles of all mails in that folder are not
shown.

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

[dolphin] [Bug 362689] SMB protocol. Dolphin replaces hostname to some IP address.

[SGBNFF via KDE Bugzilla]

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

SGBNFF  changed:

   What|Removed |Added

Summary|SMB protocol. Dolphin   |SMB protocol. Dolphin
   |replaces NetBIOS name to|replaces hostname to some
   |some IP address.|IP address.

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

[kmail2] [Bug 362728] New: list of Mails in a folder not readable (white on white)

[Herr Schmidt via KDE Bugzilla]

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

Bug ID: 362728
   Summary: list of Mails in a folder not readable (white on
white)
   Product: kmail2
   Version: 5.1.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Dear maintainers,

I can't use the program, as in the folderview (right from the treeview and
above the actual mail) the titles etc. are shown white on white. I will add a
picture on which you can see what I mean. 

These are mails from a Icedove import. But I suggest that this has something to
do with kwin or system settings due to strange behaviour regardings graphics
throughout the whole distro. Please have a look at my bug reports #362723,
#362720.

Thanks for your work, by the way!

Reproducible: Always




Thinkpad T560

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

[kmymoney4] [Bug 361876] Poor database performance after update

[via KDE Bugzilla]

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

--- Comment #8 from lp.allar...@gmail.com ---
I performed a quick performance benchmark on the database server:

Running the test with following options:
Number of threads: 8

Doing OLTP test.
Running mixed OLTP test
Doing read-only test
Using Special distribution (12 iterations,  1 pct of values are returned in 75
pct cases)
Using "BEGIN" for starting transactions
Using auto_inc on the id column
Threads started!
Time limit exceeded, exiting...
(last message repeated 7 times)
Done.

OLTP test statistics:
queries performed:
read:373534
write:   0
other:   53362
total:   426896
transactions:26681  (444.61 per sec.)
deadlocks:   0  (0.00 per sec.)
read/write requests: 373534 (6224.50 per sec.)
other operations:53362  (889.21 per sec.)

Test execution summary:
total time:  60.0103s
total number of events:  26681
total time taken by event execution: 479.8500
per-request statistics:
 min:  0.83ms
 avg: 17.98ms
 max: 60.14ms
 approx.  95 percentile:  29.97ms

Threads fairness:
events (avg/stddev):   3335.1250/12.10
execution time (avg/stddev):   59.9812/0.00


I am relying on the DB devs to tell me if this is considered acceptable for
usage with KMM..

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

[kwin] [Bug 362711] Opening firefox with custom shortcut Meta+N keeps Alt-key locked

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #4 from Thomas Lübking  ---
firefox is a shellscript, calling the actual binary (usually in /usr/lib,
/usr/lib/firefox/firefox-bin ?)

you can use xdotool to search window IDs or list them all w/ "xwininfo -root
-tree"

for "offline" inspection, you'll require remote access (ssh), so you can
inspect the system w/o altering the state
The alternative would be sth. like
   sleep 20; xev -event keyboard -id `xdotool search -onlyvisible -class
firefox` | grep state
to program the inspection before causing the situation.
(no guarantee that the search will find exactly one window, better check that
w/ FF running)

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

[kwin] [Bug 362711] Opening firefox with custom shortcut Meta+N keeps Alt-key locked

[via KDE Bugzilla]

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

--- Comment #3 from g...@netcologne.de ---
It is difficult to run the xev command on the firefox window without modifying
its state. How do I get the window-id? I only know xwininfo for this. Running
xev with the window id does not display anything then. But for this I have to
change between firefox and konsole, so this might not be the original state
anymore.

How can I check which gtk version firefox is using? Running ld on the
executable does not work:
ld /usr/lib/firefox/firefox
ld: warning: cannot find entry symbol _start; not setting start address

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

[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored

[David Jarvie via KDE Bugzilla]

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

--- Comment #20 from David Jarvie  ---
Git commit af320ed5599cb0737c0601e26126c39e64780de0 by David Jarvie.
Committed on 05/05/2016 at 22:08.
Pushed by djarvie into branch 'master'.

Fix KDateTime::isValid() for ClockTime values

Fix KDateTime::isValid() wrongly returning invalid for an instance
which is specified in ClockTime, if the date/time is invalid in the
local time zone. Bug was due to QDateTime::isValid() working
differently in Qt4 and Qt5.

REVIEW: 127629

M  +16   -0autotests/kdatetimetest.cpp
M  +11   -1src/kdecore/kdatetime.cpp

http://commits.kde.org/kdelibs4support/af320ed5599cb0737c0601e26126c39e64780de0

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

[frameworks-kdoctools] [Bug 357428] kf5-kdoctools: several issues with kdoctools_install()

[Luigi Toscano via KDE Bugzilla]

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

Luigi Toscano  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||luigi.tosc...@tiscali.it
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #3 from Luigi Toscano  ---
Apologize for the long delay. 
I think that what you hit is a problem with the structure of the directories.
You used 
translations//docs/*.docbook 
but it should be
translations//docs//*.docbook 

See the example tests/kdoctools_install-test/ inside the kdoctools source
directory, and/or the comments in the KF5DocToolsMacros.cmake file.

With that structure, it works both when doc translations are "mixed" with
interface translations, and when they are in separate directories (tested back
to 5.16).

Does it work for you?

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

[klipper] [Bug 362727] New: When Keepassx clears clipboard with password, he stays in Klipper

[via KDE Bugzilla]

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

Bug ID: 362727
   Summary: When Keepassx clears clipboard with password, he stays
in Klipper
   Product: klipper
   Version: 5.6.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasma-widget
  Assignee: mgraess...@kde.org
  Reporter: svadk...@gmail.com

When KeePassX clears clipboard with password, he stays in Klipper window even
through i can't paste it anymore without select it in Klipper.
Option "Prevent empty clipboard" is turned off.

Reproducible: Always

Steps to Reproduce:
1.copy password from Keepassx
2.wait, before Keepassx clear clipboard

Actual Results:  
I can't paste password in text field, but password still visible in Klipper
window and i can select it from here (by first selecting another item), and
then paste.

Expected Results:  
Clipboard should be cleared everywhere.

Keepassx version 2.0.2

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

[kcalc] [Bug 360105] Doesn't start with Qt 5.6

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kcal
   ||c/2678cb9c7a07381e3ffb8a210
   ||7946cec53bf5909
 Status|CONFIRMED   |RESOLVED
   Version Fixed In||16.04.1

--- Comment #17 from Elvis Angelaccio  ---
Git commit 2678cb9c7a07381e3ffb8a2107946cec53bf5909 by Elvis Angelaccio.
Committed on 05/05/2016 at 21:47.
Pushed by elvisangelaccio into branch 'Applications/16.04'.

Fix invisible main window with Qt 5.6

Since Qt 5.6, the minimum size property seems to default to an empty size,
so it can't be used to set a fixed size for the main window.

A better approach is to tell the layout() to use a fixed size.

This change also exposed a redundant horizontal spacer in the .ui code, which
is now removed.
FIXED-IN: 16.04.1
REVIEW: 127847

M  +1-1kcalc.cpp
M  +0-13   kcalc.ui

http://commits.kde.org/kcalc/2678cb9c7a07381e3ffb8a2107946cec53bf5909

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

[plasmashell] [Bug 361751] "Loading of providers from file: http://download.kde.org/ocs/providers.xml failed" (no proxy set)

[via KDE Bugzilla]

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

--- Comment #4 from r...@isaeff.net ---
Nevermind, there was a script that changed proxy settings.

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

[kontact] [Bug 362726] New: KOrganizer crashed after trying to make a task from inside the KMail tab

[Herr Schmidt via KDE Bugzilla]

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

Bug ID: 362726
   Summary: KOrganizer crashed after trying to make a task from
inside the KMail tab
   Product: kontact
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Application: kontact (5.1.3)
 (Compiled from sources)
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 tried to make a task inside kmail (there is a bar below to do this) after I
applied it crashed.



Before that I tried to make a new task in the task part of Korganizer and this
task did never show up there. It only was shown as a link in the overview tab.
But the link lead me into the nothingness of tasks...

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc2256b1940 (LWP 14322))]

Thread 49 (Thread 0x7fc21bfff700 (LWP 14324)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23cbb788b in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7fc23d45483c ) at wtf/FastMalloc.cpp:2825
#2  0x7fc23cbb78c9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0x7fc23d45483c ) at
wtf/FastMalloc.cpp:1993
#3  0x7fc23897a6fa in start_thread (arg=0x7fc21bfff700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 48 (Thread 0x7fc1d9079700 (LWP 14325)):
#0  0x7fc23814d340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc23814f84b in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc23815024b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc23815042c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc23f477a9b in QEventDispatcherGlib::processEvents
(this=0x7fc1d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fc23f41edea in QEventLoop::exec (this=this@entry=0x7fc1d9078c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fc23f23b8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fc23f24084e in QThreadPrivate::start (arg=0x1ed49e0) at
thread/qthread_unix.cpp:331
#8  0x7fc23897a6fa in start_thread (arg=0x7fc1d9079700) at
pthread_create.c:333
#9  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 47 (Thread 0x7fc1d2b24700 (LWP 14326)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23c8c5a74 in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x7fc2205ba058) at heap/BlockAllocator.cpp:139
#2  0x7fc23cbe7541 in WTF::wtfThreadEntryPoint(void*) () at
wtf/ThreadingPthreads.cpp:195
#3  0x7fc23897a6fa in start_thread (arg=0x7fc1d2b24700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 46 (Thread 0x7fc1d2323700 (LWP 14327)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23c8c6aa3 in JSC::GCThread::gcThreadMain (this=0x1ed1690) at
heap/GCThread.cpp:81
#2  0x7fc23cbe7541 in WTF::wtfThreadEntryPoint(void*) () at
wtf/ThreadingPthreads.cpp:195
#3  0x7fc23897a6fa in start_thread (arg=0x7fc1d2323700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 45 (Thread 0x7fc1d1b22700 (LWP 14328)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23c8c6aa3 in JSC::GCThread::gcThreadMain (this=0x1ed36d0) at
heap/GCThread.cpp:81
#2  0x7fc23cbe7541 in WTF::wtfThreadEntryPoint(void*) () at
wtf/ThreadingPthreads.cpp:195
#3  0x7fc23897a6fa in start_thread (arg=0x7fc1d1b22700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 44 (Thread 0x7fc1d1321700 (LWP 14329)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc23c8c6aa3 in JSC::GCThread::gcThreadMain (this=0x20c8c20) at
heap/GCThread.cpp:81
#2  0x7fc23cbe7541 in WTF::wtfThreadEntryPoint(void*) () at
wtf/ThreadingPthreads.cpp:195
#3  0x7fc23897a6fa in start_thread (arg=0x7fc1d1321700) at
pthread_create.c:333
#4  0x7fc23e940b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 43 (Thread 0x7fc1b7381700 (LWP 14330)):
#0  

[krunner] [Bug 362725] New: Plasma crashes on sddm auto login

[Denis via KDE Bugzilla]

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

Bug ID: 362725
   Summary: Plasma crashes on sddm auto login
   Product: krunner
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: lloe...@gmail.com

Application: krunner (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 was trying to start my plasma!!! Only that and nothing more!

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Possible duplicates by query: bug 362621, bug 362534, bug 362377, bug 362265,
bug 362088.

Reported using DrKonqi

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

[ark] [Bug 362690] compress folder to tar.gz is not correct

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||16.04.1
  Latest Commit||http://commits.kde.org/ark/
   ||846febf951f8a6d31a325ca4b39
   ||56afece68be01
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Elvis Angelaccio  ---
Git commit 846febf951f8a6d31a325ca4b3956afece68be01 by Elvis Angelaccio.
Committed on 05/05/2016 at 20:33.
Pushed by elvisangelaccio into branch 'Applications/16.04'.

addtoarchive: drop extension only when present

AddToArchive currently tries to drop the extension from any filename,
even if there is no extension in it. We now exploit the mimetype
detected-by-extension: if it's the default mimetype,
then the filename is just a string with some dots but no valid extension.
Otherwise the filename has an actual extension, which we discard.

A testcase is added to reproduce the issue.
FIXED-IN: 16.04.1

Differential Revision: D1541

M  +6-0autotests/kerfuffle/addtoarchivetest.cpp
A  +1-0autotests/kerfuffle/data/test-3.4.0/testfile1.txt
M  +7-2kerfuffle/addtoarchive.cpp

http://commits.kde.org/ark/846febf951f8a6d31a325ca4b3956afece68be01

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

[frameworks-plasma] [Bug 349669] Tooltip jumps to top of screen after clicking on quick launch icon

[Mark via KDE Bugzilla]

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

Mark  changed:

   What|Removed |Added

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

--- Comment #8 from Mark  ---
(In reply to Marco Martin from comment #7)
> is still happening on Plasma 5.6?

It seems to be working fine now. Thank you for taking care and closing this
issue.

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #6 from Herr Schmidt  ---
Created attachment 98799
  --> https://bugs.kde.org/attachment.cgi?id=98799=edit
Due to this bug some boxes are almost unreadable. This is on ixquick.de

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

[kontact] [Bug 362724] New: enable calendar

[manuel fernández via KDE Bugzilla]

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

Bug ID: 362724
   Summary: enable calendar
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: m...@xanum.uam.mx

Application: kontact (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:

Enable / disable calendar
when pressed radio button, the crash happens

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa543615940 (LWP 7453))]

Thread 27 (Thread 0x7fa51e5e2700 (LWP 7455)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa53ec3488b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa53ec348c9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa53a9f76fa in start_thread (arg=0x7fa51e5e2700) at
pthread_create.c:333
#4  0x7fa5409bdb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fa4db043700 (LWP 7456)):
#0  0x7fa53a1cce8c in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa53a1cd380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa53a1cd42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa5414f4a9b in QEventDispatcherGlib::processEvents
(this=0x7fa4d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fa54149bdea in QEventLoop::exec (this=this@entry=0x7fa4db042c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fa5412b88a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fa5412bd84e in QThreadPrivate::start (arg=0xf74e60) at
thread/qthread_unix.cpp:331
#7  0x7fa53a9f76fa in start_thread (arg=0x7fa4db043700) at
pthread_create.c:333
#8  0x7fa5409bdb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 25 (Thread 0x7fa4d8bb5700 (LWP 7457)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa53e942a74 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa53ec64541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa53a9f76fa in start_thread (arg=0x7fa4d8bb5700) at
pthread_create.c:333
#4  0x7fa5409bdb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 24 (Thread 0x7fa4d3fff700 (LWP 7458)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa53e943aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa53ec64541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa53a9f76fa in start_thread (arg=0x7fa4d3fff700) at
pthread_create.c:333
#4  0x7fa5409bdb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 23 (Thread 0x7fa4d37fe700 (LWP 7459)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa53e943aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa53ec64541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa53a9f76fa in start_thread (arg=0x7fa4d37fe700) at
pthread_create.c:333
#4  0x7fa5409bdb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7fa4d2ffd700 (LWP 7460)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa53e943aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fa53ec64541 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fa53a9f76fa in start_thread (arg=0x7fa4d2ffd700) at
pthread_create.c:333
#4  0x7fa5409bdb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7fa4b93a5700 (LWP 7461)):
#0  0x7fa5409b1e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa53a1cd31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa53a1cd42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa5414f4a9b in QEventDispatcherGlib::processEvents
(this=0x7fa4b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fa54149bdea in QEventLoop::exec (this=this@entry=0x7fa4b93a4c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fa5412b88a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fa5412bd84e in QThreadPrivate::start (arg=0x130cd30) at

[Discover] [Bug 362723] text overlaps and is not readable

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #1 from Herr Schmidt  ---
Created attachment 98798
  --> https://bugs.kde.org/attachment.cgi?id=98798=edit
Muon Discover graphical/text failure

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

[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support

[via KDE Bugzilla]

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

svadk...@gmail.com changed:

   What|Removed |Added

 CC||svadk...@gmail.com

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

[Discover] [Bug 362723] New: text overlaps and is not readable

[Herr Schmidt via KDE Bugzilla]

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

Bug ID: 362723
   Summary: text overlaps and is not readable
   Product: Discover
   Version: 5.6.2
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

The texts of the main examples are overlapping and therefore not readable. See
Picture. 

Reproducible: Always

Steps to Reproduce:
1. Start the program. ;)

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

[krita] [Bug 362722] regression in "Create from clipboard window

[RJ via KDE Bugzilla]

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

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

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

[krita] [Bug 362722] New: regression in "Create from clipboard window

[RJ via KDE Bugzilla]

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

Bug ID: 362722
   Summary: regression in "Create from clipboard window
   Product: krita
   Version: 3.0 Beta
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: ogldel...@mail.ru

Krita can't get Width and Height from clipboard image and paste it in
corresponding fields.

Reproducible: Always

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #5 from Herr Schmidt  ---
Created attachment 98797
  --> https://bugs.kde.org/attachment.cgi?id=98797=edit
firefox and textboxes are still dark

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

[krita] [Bug 362721] Ability to use Edit -> Paste option without create canvas

[RJ via KDE Bugzilla]

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

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

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

[krita] [Bug 362721] New: Ability to use Edit -> Paste option without create canvas

[RJ via KDE Bugzilla]

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

Bug ID: 362721
   Summary: Ability to use Edit -> Paste option without create
canvas
   Product: krita
   Version: 3.0 Beta
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: ogldel...@mail.ru

Just copy image from somewhere to clipboard and try to paste it with menu
Edit->Paste.
I think this should work like in other graphics programs.

Reproducible: Always

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #4 from Herr Schmidt  ---
Created attachment 98796
  --> https://bugs.kde.org/attachment.cgi?id=98796=edit
back

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #3 from Herr Schmidt  ---
Created attachment 98795
  --> https://bugs.kde.org/attachment.cgi?id=98795=edit
switching back

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #2 from Herr Schmidt  ---
Created attachment 98794
  --> https://bugs.kde.org/attachment.cgi?id=98794=edit
after first switch

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

[systemsettings] [Bug 362720] desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

[Herr Schmidt via KDE Bugzilla]

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

--- Comment #1 from Herr Schmidt  ---
Created attachment 98793
  --> https://bugs.kde.org/attachment.cgi?id=98793=edit
starting point

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

[plasmashell] [Bug 361531] Clicking notification popup no longer hides it

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #3 from Kai Uwe Broulik  ---
This commit broke the action buttons, when I just click the action it will not
trigger, instead the MEL will eat the event off the button and just close the
notification. If I press and hold the button it works.

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

[systemsettings] [Bug 362720] New: desktop appearance: switching between theme Breeze and ~ dark mixes up in Dada-style

[Herr Schmidt via KDE Bugzilla]

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

Bug ID: 362720
   Summary: desktop appearance: switching between theme Breeze and
~ dark mixes up in Dada-style
   Product: systemsettings
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_desktopthemedetails
  Assignee: jamboar...@gmail.com
  Reporter: wettererschein...@bb-goettingen.de
CC: plasma-b...@kde.org

If I switch the desktop appearance theme (Erscheinungsbild; first entry) from
Breeze to Breeze dark, apply it only some things like the control bar
(Kontrollleiste; below of the screen with start button etc.) get dark. When I
switch back to Breeze again it results in a mixed theme with a somewhat lighter
grey control bar but dark windows. Only if after this step I just click on
Breeze dark (without applying) and click back to Breeze and apply (which then
is possible although it is supposed to be the actual theme) the colors change
to the light theme again. But the Boxes (text input) inside a Website like this
are still black. And Firefox stays dark (although only standard theme is
installed).

Reproducible: Always

Steps to Reproduce:
Systemsettings - Desktop Design (Arbeitsbereich Design; first entry) -
Appearance (Erscheinungsbild; first entry)
1. Switch from Breeze to Breeze dark and apply
2. Switch back to Breeze and apply.
3. Click on Breeze dark, click back on Breeze and then apply



Thinkpad T560

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

[dolphin] [Bug 362719] New: Dolphin crash when I drag a file for copy it / Dolphin falla cuando arrastro un archivo para copiarlo

[Angel via KDE Bugzilla]

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

Bug ID: 362719
   Summary: Dolphin crash when I  drag a file for copy it /
Dolphin falla cuando arrastro un archivo para copiarlo
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: angelbravosa...@gmail.com

Application: dolphin (15.12.3)

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:

App crash occurred when I tried to copy a file dragging it between two open
tabs.

La aplicación falla cuando traté de copiar un archivo arrastrándolo entre dos
pestañas abiertas.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb7b89b28c0 (LWP 5699))]

Thread 3 (Thread 0x7fb7b59ff700 (LWP 5700)):
#0  0x7fb7ca264e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb7be9d2c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fb7be9d48d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fb7b8383629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fb7c4e3684e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb7c15e46fa in start_thread (arg=0x7fb7b59ff700) at
pthread_create.c:333
#6  0x7fb7ca270b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fb7aa4a0700 (LWP 5703)):
#0  0x7fb7ca2609cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb7c0a9c6c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb7c0a58e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb7c0a592c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb7c0a5942c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb7c506da9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb7c5014dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb7c4e318a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb7c4e3684e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fb7c15e46fa in start_thread (arg=0x7fb7aa4a0700) at
pthread_create.c:333
#10 0x7fb7ca270b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fb7b89b28c0 (LWP 5699)):
[KCrash Handler]
#6  0x7fb7c501734f in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb7c5b1a03c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7fb7c5b1f516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7fb7c501762b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fb7c5019a26 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fb7c506d673 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fb7c0a59127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7fb7c0a59380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x7fb7c0a5942c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x7fb7c506da7f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7fb7c5014dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fb7c501ce8c in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7fb7ca590e2b in kdemain (argc=1, argv=) at
/build/dolphin-HvGmRr/dolphin-15.12.3/src/main.cpp:150
#19 0x7fb7ca18a830 in __libc_start_main (main=0x400710 ,
argc=1, argv=0x7fff579fccd8, init=, fini=,
rtld_fini=, stack_end=0x7fff579fccc8) at ../csu/libc-start.c:291
#20 0x00400749 in _start ()

Possible duplicates by query: bug 362637, bug 362619, bug 362527, bug 362460,
bug 362355.

Reported using DrKonqi

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

[plasmashell] [Bug 361751] "Loading of providers from file: http://download.kde.org/ocs/providers.xml failed" (no proxy set)

[via KDE Bugzilla]

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

--- Comment #3 from r...@isaeff.net ---
I have the same problem in Kubuntu 16.04, can't load widgets or backgrounds for
several days with message "Loading of providers from file:
http://download.kde.org/ocs/providers.xml failed". Internet connection is ok,
no proxy settings.

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

[plasmashell] [Bug 361751] "Loading of providers from file: http://download.kde.org/ocs/providers.xml failed" (no proxy set)

[via KDE Bugzilla]

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

r...@isaeff.net changed:

   What|Removed |Added

 CC||r...@isaeff.net

--- Comment #2 from r...@isaeff.net ---
I ha

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

[kwin] [Bug 362718] Systemsettings 5.5.5 crashes when Switching between two menu items

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---
No, this is just bug #354164
It was thought fixed for 5.4.3 but see
https://bugs.kde.org/show_bug.cgi?id=354164#c10

One cannot work around that "somehow" (and the new memory allocator in 5.6 has
just different bugs, so expect similar crashes with other backtraces after an
update. Maybe less often.)

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

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

[kwin] [Bug 354164] Going twice to effects kcm in systemsettings causes abort

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||wettererscheinung@bb-goetti
   ||ngen.de

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

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

[kgpg] [Bug 340802] The export option "Sauberer Schlüssel" is not documented

[Rolf Eike Beer via KDE Bugzilla]

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

--- Comment #4 from Rolf Eike Beer  ---
It means that just the key itself is exported including it's subkeys, but
excluding all signatures.

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

[kgpg] [Bug 340802] The export option "Sauberer Schlüssel" is not documented

[Martin Schröder via KDE Bugzilla]

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

--- Comment #3 from Martin Schröder  ---
(In reply to Rolf Eike Beer from comment #2)
> Not yet. Patches are welcome.

Hard to do since I don't know what the option does. Surely a developer knows?

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

[systemsettings] [Bug 362718] New: Systemsettings 5.5.5 crashes when Switching between two menu items

[Herr Schmidt via KDE Bugzilla]

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

Bug ID: 362718
   Summary: Systemsettings 5.5.5 crashes when Switching between
two menu items
   Product: systemsettings
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: wettererschein...@bb-goettingen.de

Application: systemsettings5 (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:
Bug #354164 sounds similar, but there it stated that the error is solved in
Version 4.x (I don't remember exactly). So as I am using Version 5.5.5 it can't
be the same bug, no?

Every time I go to the desktop settings and switch several times (not only
twice as in the other bug) between some entries after 6-12 changes it crashes.

- Unusual behavior I noticed:
* Switching between Breeze and Breeze-dark doesn't work properly. This results
in a mixup between the two and the layout changes every time I click on the
other theme, click back to the active theme and apply the "change".
* Plasma crashed two or three times without me being able to tell why or in
which situation.
* Grafics are disturbed (Some texts inside a button are longer than the button,
in Discover the descriptions of the top presented items above are not readable
because the overlap outside of the boxes, Ubuntu Software Center shows white
text on white background which makes it unusable)
* Theres a cracking noise out of the speakers after login, when initialising
KDE.

The crash can be reproduced every time.

-- Backtrace:
Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff1193da8c0 (LWP 11271))]

Thread 5 (Thread 0x7ff107abc700 (LWP 11272)):
#0  0x7ff115af0e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff1137d8c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7ff1137da8d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7ff109e0e629 in QXcbEventReader::run (this=0x1f054f0) at
qxcbconnection.cpp:1253
#4  0x7ff1161e684e in QThreadPrivate::start (arg=0x1f054f0) at
thread/qthread_unix.cpp:331
#5  0x7ff112f626fa in start_thread (arg=0x7ff107abc700) at
pthread_create.c:333
#6  0x7ff115afcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7ff0ed2e8700 (LWP 11281)):
#0  0x7ff112a4093f in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff112a4124b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff112a4142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff11641da9b in QEventDispatcherGlib::processEvents
(this=0x7ff0e01619d0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ff1163c4dea in QEventLoop::exec (this=this@entry=0x7ff0ed2e7ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ff1161e18a4 in QThread::exec (this=this@entry=0x49f4670) at
thread/qthread.cpp:503
#6  0x7ff114b603c5 in QQmlThreadPrivate::run (this=0x49f4670) at
qml/ftw/qqmlthread.cpp:141
#7  0x7ff1161e684e in QThreadPrivate::start (arg=0x49f4670) at
thread/qthread_unix.cpp:331
#8  0x7ff112f626fa in start_thread (arg=0x7ff0ed2e8700) at
pthread_create.c:333
#9  0x7ff115afcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7ff0e7009700 (LWP 11282)):
#0  0x7ff112a40d38 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff112a412c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff112a4142c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff11641da9b in QEventDispatcherGlib::processEvents
(this=0x7ff0dc038220, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ff1163c4dea in QEventLoop::exec (this=this@entry=0x7ff0e7008ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ff1161e18a4 in QThread::exec (this=this@entry=0x2618cd0) at
thread/qthread.cpp:503
#6  0x7ff114b603c5 in QQmlThreadPrivate::run (this=0x2618cd0) at
qml/ftw/qqmlthread.cpp:141
#7  0x7ff1161e684e in QThreadPrivate::start (arg=0x2618cd0) at
thread/qthread_unix.cpp:331
#8  0x7ff112f626fa in start_thread (arg=0x7ff0e7009700) at
pthread_create.c:333
#9  0x7ff115afcb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7ff0eefe6700 (LWP 11285)):
#0  0x7ff112a85a49 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff112a403f4 in g_main_context_release () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff112a412d6 in ?? () 

[kmail2] [Bug 362717] Message list: Header only show subject, content shows sender

[Pascal d'Hermilly via KDE Bugzilla]

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

Pascal d'Hermilly  changed:

   What|Removed |Added

Summary|Header only show subject,   |Message list: Header only
   |content shows sender|show subject, content shows
   ||sender

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

[kmail2] [Bug 362717] Header only show subject, content shows sender

[Pascal d'Hermilly via KDE Bugzilla]

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

--- Comment #1 from Pascal d'Hermilly  ---
Created attachment 98792
  --> https://bugs.kde.org/attachment.cgi?id=98792=edit
screenshot

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

[kmail2] [Bug 362717] New: Header only show subject, content shows sender

[Pascal d'Hermilly via KDE Bugzilla]

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

Bug ID: 362717
   Summary: Header only show subject, content shows sender
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: pas...@dhermilly.dk

It sounds crazy, but I cant get a sane layout from the message list in my
inbox.
The only header of the list says subject, but below I see names of senders.
Those can be expanded to show subject lines but I have no idea when they are
from.
What I want is just a list of emails sorted by date: from, subject, date, size.
I have tried to right click the message list header. The right fields are
there. When I clcik Adjust column sizes nothing happens. I've tried pulling
them to the size to resize. Nothing helps
I've used KDE since 2004 and is used to using this kind of interface... (It's
been some years since using kmail, but that shouldn't matter to this).


Reproducible: Always

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

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #60 from Thomas Lübking  ---
This is not a bug in KDE (let alone KWin)

The bug exists in every Qt 5.5 version. Older Qt versions have randr related
sefaults in QtQuick (will affect plasmashell, kwin and everything else that has
QML bits) and so does at least Qt 5.6.0 (unstashed by the restorage of the pre
5.5 behavior to prevent these crashes)

Ubuntu could likely "backport" this in Qt - while the resolving commit is a bit
bigger, the breaking one is just (afaics pretty much unmotivated other than the
broken anyway QtQuick part) 
http://code.qt.io/cgit/qt/qtbase.git/commit/src/plugins/platforms/xcb/qxcbconnection.cpp?id=51ada7734ad780178ecced11e0dff454dfc2e5f2

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

[plasmashell] [Bug 362716] New: Plasma crash on Enter key (Konsole)

[Jason via KDE Bugzilla]

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

Bug ID: 362716
   Summary: Plasma crash on Enter key (Konsole)
   Product: plasmashell
   Version: 5.5.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jasonbailey1...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.3)

Qt Version: 5.5.1
Frameworks Version: 5.21.0
Operating System: Linux 4.5.0-3-default x86_64
Distribution: "openSUSE Tumbleweed (20160422) (x86_64)"

-- Information about the crash:
I was working in a Konsole window, and when I pressed Enter, Plasma crashed. I
have Plasma desktop effects enabled and partial transparency within the Konsole
window, which I suspect was a part of the cause for the crash. 

I can't seem to replicate the problem from within Konsole specifically, but I
have experienced other seemingly random Plasma crashes. Doesn't seem to happen
if I disable desktop effects.

The crash does not seem to be reproducible.

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

Thread 8 (Thread 0x7fd6ba4d8700 (LWP 5256)):
#0  0x7fd6ca3c807d in poll () at /lib64/libc.so.6
#1  0x7fd6cf2a43f2 in  () at /usr/lib64/libxcb.so.1
#2  0x7fd6cf2a5fc7 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fd6bc628dd9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fd6caab591f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fd6c9bc9424 in start_thread () at /lib64/libpthread.so.0
#6  0x7fd6ca3d0add in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fd6b35ef700 (LWP 5310)):
#0  0x7fd6ca3c807d in poll () at /lib64/libc.so.6
#1  0x7fd6c6aaf364 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fd6c6aaf46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fd6cacda40b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fd6cac8453a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd6caab0adc in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fd6cdd820e5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fd6caab591f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fd6c9bc9424 in start_thread () at /lib64/libpthread.so.0
#9  0x7fd6ca3d0add in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7fd6a6177700 (LWP 5311)):
#0  0x7fd6c6af26a9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fd6c6aaef26 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fd6c6aaf3c8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fd6c6aaf46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fd6cacda40b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fd6cac8453a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fd6caab0adc in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fd6cdd820e5 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fd6caab591f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fd6c9bc9424 in start_thread () at /lib64/libpthread.so.0
#10 0x7fd6ca3d0add in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fd6a48d6700 (LWP 5312)):
#0  0x7fd6c6aac5a9 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7fd6c6aae92b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fd6c6aaf293 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fd6c6aaf46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fd6cacda40b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fd6cac8453a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fd6caab0adc in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fd6cdd820e5 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fd6caab591f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fd6c9bc9424 in start_thread () at /lib64/libpthread.so.0
#10 0x7fd6ca3d0add in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fd69ef40700 (LWP 5317)):
#0  0x7fd6c9bcf03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fd6d05413d4 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fd6d0541419 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fd6c9bc9424 in start_thread () at /lib64/libpthread.so.0
#4  0x7fd6ca3d0add in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fd6174ca700 (LWP 5331)):
#0  0x7fd6c6af26a9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fd6c6aaf268 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fd6c6aaf46c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fd6cacda40b in

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

[Michael Butash via KDE Bugzilla]

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

Michael Butash  changed:

   What|Removed |Added

 CC||mich...@butash.net

--- Comment #59 from Michael Butash  ---
Is a backport possible for 16.04 ubuntu users not likely to see this in lts
until 18.04?

Sadly, kde4 was terrible with unfixed bugs for setting up xrandr geometry as
well that made it unusable when relying on radeon modules, upgraded to 5 (and
16.04 to do so), was massively better, but affected by this now as well it
seems.  Going back to 4 really isn't an option being left unresolved too.

I'm using 3x displays, 48" 4k samsung tv's as my desk monitors, which don't do
dpms keepalive over hdmi cables it seems.  Rather they shut off/down, and "go
away" on the wire to the video card and xrandr, leaving it without a native
display, or your "dummy display" concept it seem to keep it sane when it has
none.  Waking up the displays, and thus xrand + kde figuring out where to put
things back to, is an entire crapshoot now whether it 1) lives perfect, 2)
lives broken needing xrandr fixing, 3) needs sddm restart from different tty,
or 4) needs rebooted as nothing wakes it up.  Feels windoze-y now.

Oddly, it doesn't always crash kwin, and sometimes recovers perfectly.  Other
times not so much, but its very random sadly.  

I've created xrandr scripts myself and with arandr to deal with it when kde5 as
a whole decides to go weird, but it's also seeming to have identity issues with
what is the "primary" display as well, as it seems to change upon these events
which is really primary, or which primary is really linked to which monitor
index.  Sometimes I just have to try setting the primary monitor randomly to
figure out which it thinks is currently actually display 2 for example.

SDDM also has recovery issues with are likely to be related but their own
beast, yet systemic of the fact no one seems to actually test kde with multiple
monitors extensively.  I was using kde4 happily with amd blob drivers and 6x
1080p montiors that did the setup itself for years, but using radeon now (with
4.x kernels that amd doesn't support yet for blob), which now works 2000x
better, breaks this with xrandr quirks like this.

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

[Akonadi] [Bug 362715] New: Imap constant refresh of IMAP directory

[Michael Butash via KDE Bugzilla]

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

Bug ID: 362715
   Summary: Imap constant refresh of IMAP directory
   Product: Akonadi
   Version: 15.12
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: mich...@butash.net
CC: kdepim-b...@kde.org, vkra...@kde.org

I'd upgraded from 14.04 ubuntu to 16.04, and with it kde5.  I've been
attempting to migrate from thunderbird to kmail, but tying in my primary
account, began noticing it having problems with constantly synching,
particularly one directory.  I get a count mismatch every time, and it just
starts over, which happens to be some 26k messages from some perpetual customer
spam in the past year.

Starting and stopping akonadi from cli, I see it hitting the same directory
constantly that the local count mismatch doesn't match, tries again, over and
over:

log_imapresource: Detected inconsistency in local cache, we're missing some
messages. Server:  26320  Local:  25004
log_imapresource: Refetching complete mailbox.

It begins its fetch, gets to the end:

...
Received:  11 In total:  24989  Wanted:  25098
Received:  11 In total:  25000  Wanted:  25098
Wrote 4357 bytes to 
"/home/$dir/.local/share/akonadi/file_db_data/26/1088326_r813"
finished
localListDone:  false  deliveryDone:  true
localListDone:  true  deliveryDone:  true
Nothing to do
Received:  0 Removed:  0 In total:  0  Wanted:  -1
finished
...
Received:  0 Removed:  0 In total:  0  Wanted:  -1
finished
log_imapresource: Detected inconsistency in local cache, we're missing some
messages. Server:  25098  Local:  25004
log_imapresource: Refetching complete mailbox.
25098
Received:  4 In total:  4  Wanted:  25098

... and starts over, again and again, collecting tons of email headers in a
steady 15mbps suck.

Watching my bandwidth, it generates a good 14mbps or so of traffic, and this
has been going on for a week or so, so amazed someone hasn't shut me down yet.

Thunderbird handles this directory just fine, not sure why kmail has this
issue, or obscurely related to some other component I'm not finding.

I'd even moved the items at a webmail level into another directory, and the
problem persisted. I suspect the imap server (godaddy, go figure) really is
doing something bad like not indexing them properly, or missing indices
perhaps, but akonadi:imap is misbehaving epically like a thrashing child
hogging a good clip of bandwidth someone is paying for (yay for unlimited
bandwidth on cable still here).

I'm going to largely purge that directory, but wanted to see if I could offer
anything to help fix this before doing so, but mostly it seems behavioral with
akonadi imap collector not knowing when to stop after x failed attempts at the
same intensive collection routine.

This also seems to cause email not to be actually commited, as I seem to not
always get all mail, and not always send all mail.  It's very spotty, but I'll
notice usually mail will stop and start collecting at odd intervals, presumably
as a result of this folder constantly refreshing as a priority.

Reproducible: Always

Steps to Reproduce:
1. Create an imap account with bad indices in its imap folder email counts
(pulls 25k emails, server reports 26k).
2. Start Akonadi from command line with akonadictl, watching the imap
collection on the errant folder as it pulls headers, finds mismatch, tries
again.
3. Watch Akonadi incessantly try to get the proper count in futility, using all
of your bandwidth constantly.

Actual Results:  
Akonadi never completes polling the folder, just trying over and over, using a
very large amount of bandwidth constantly and perpetually until akonadi is
force shutdown.

Expected Results:  
* Recover from a bad index automatically (if possible)
* Offer to correct bad index on server (if possible)
* Exit and give error condition of unstable directory structure, server problem
* Simply ignore the index being bad, grab what it can grab, and poll emails
normally around the bad index (seems to be thunderbird behaviour)

I've left this to be somewhat broken, but the fact that kde5 is a bit unstable
with multi-monitor support still means I restart often, which respawns akonadi
until I notice bandwidth usage being excessive and kill it again.  I can
provide better debug, but again, seems more just methodical fixes needed to be
agreed upon.

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

[clazy] [Bug 360374] Check for QString::left(1) mis-use.

[Sergio Martins via KDE Bugzilla]

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

Sergio Martins  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/claz
   ||y/bb1c95331786149d0682be676
   ||53a725366358f0f

--- Comment #3 from Sergio Martins  ---
Git commit bb1c95331786149d0682be67653a725366358f0f by Sergio Martins.
Committed on 05/05/2016 at 19:16.
Pushed by smartins into branch 'master'.

Introduce qstring-left check

Warns when using QString::left(1) or QString::left(0).
The former should be replaced by at(0), the later shouldn't be used
and is probably a typo.

M  +1-0CMakeLists.txt
M  +1-0README
A  +4-0checks/README-qstring-left
A  +64   -0checks/qstring-left.cpp [License: LGPL (v2+)]
A  +39   -0checks/qstring-left.h [License: LGPL (v2+)]
M  +5-5tests/clazy/test_requested_checks.sh.expected
A  +7-0tests/qstring-left/config.json
A  +13   -0tests/qstring-left/main.cpp [License: UNKNOWN]  *
A  +2-0tests/qstring-left/main.cpp.expected

The files marked with a * at the end have a non valid license. Please read:
http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are
listed at that page.


http://commits.kde.org/clazy/bb1c95331786149d0682be67653a725366358f0f

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

[krita] [Bug 362691] Krita crashes on opening file after changing LUT Management settings in docker

[Bartje via KDE Bugzilla]

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

--- Comment #4 from Bartje  ---
ok, thanks for the tip :-)

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2016-05-05 14:10 GMT+02:00 wolthera via KDE Bugzilla <
bugzilla_nore...@kde.org>:

> https://bugs.kde.org/show_bug.cgi?id=362691
>
> --- Comment #3 from wolthera  ---
> BTW, you can fix up your krita by looking for the kritarc file in config,
> and
> then editing it with gedit or kate or whatever. Search for OCIO and set
> ocio
> enabled to 'false'.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[krita] [Bug 362714] New: going to frame 1, krita closes when onion skin is activated

[Zkoyllar via KDE Bugzilla]

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

Bug ID: 362714
   Summary: going to frame 1, krita closes when onion skin is
activated
   Product: krita
   Version: 3.0 Beta
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: kokoroasak...@gmail.com

The program closes whenever I activate the onion skin and go to the first
frame. 

Steps I follow. 
Go to timeline


Reproducible: Always

Steps to Reproduce:
1.I create first frame. 
2.I create second frame. 
3.Activate onion skin.
4.Go to first frame. 
5.Krita closes without showing any kind of message. 

Actual Results:  
Krita closes.

Expected Results:  
Allow to see frame one when onion skin is activated. 

This has happened since the lastest 3 builds for windows.

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

[kwin] [Bug 362711] Opening firefox with custom shortcut Meta+N keeps Alt-key locked

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #2 from Thomas Lübking  ---
kglobalaccel at best.
xev -event keyboard -id  | grep state
Alt should be 8 (but that can vary) ie. 
echo $(( & 0x8))

should print 8, otherwuse FF believes the Alt key is pressed while there's no
such indication from the window system.

Stupid question: are both FF versions the same gtk or is one Gtk2 and the other
Gtk3?

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

[plasmashell] [Bug 362713] New: Crash when right-clicking on a taskmanager entry that disappeared after the click

[Raman Gupta via KDE Bugzilla]

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

Bug ID: 362713
   Summary: Crash when right-clicking on a taskmanager entry that
disappeared after the click
   Product: plasmashell
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: rocketra...@gmail.com
CC: plasma-b...@kde.org

- What I was doing when the application crashed:

I had right-clicked on a taskbar entry for a Skype phone call. The Skype call
had disconnected just before my right-click, and therefore the taskbar entry
was about to disappear. When the taskbar entry disappeared, Plasma crashed.

Application: plasmashell (5.5.5)

Qt Version: 5.6.0
Operating System: Linux 4.4.7-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"


Reproducible: Always

Steps to Reproduce:
1. Call on Skype
2. Call the Skype Call Testing Service
3. Hangup
4. Before the Skype Phone taskmanager entry disappears, right-click on it
5. Wait for the crash

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

[plasmashell] [Bug 362713] Crash when right-clicking on a taskmanager entry that disappeared after the click

[Raman Gupta via KDE Bugzilla]

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

--- Comment #1 from Raman Gupta  ---
Created attachment 98790
  --> https://bugs.kde.org/attachment.cgi?id=98790=edit
plasmashell kcrash output

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

[kstars] [Bug 361646] KStars hogs CPU until unusable

[Rob via KDE Bugzilla]

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

--- Comment #20 from Rob  ---
Ah, yes, got it now, testing...

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

[krunner] [Bug 358348] krunner crashes when doing a simple search

[Przemek Tomczyk via KDE Bugzilla]

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

--- Comment #6 from Przemek Tomczyk  ---
Well, it seems it works only for a while. After Baloo index removed (and
re-created itself) I'm getting  this:

Thread 8 (Thread 0x7f91c67fc700 (LWP 22430)):
[KCrash Handler]
#6  0x7f91e186eb44 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#7  0x7f91e186fd34 in mdb_txn_begin () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#8  0x7f91e1ee901e in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#9  0x7f91e1ed7ff2 in Baloo::Query::exec() () from
/usr/lib/x86_64-linux-gnu/libKF5Baloo.so.5
#10 0x7f91e20f8edf in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#11 0x7f91e20f9853 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#12 0x7f91eb9cbf40 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () from
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5
#13 0x7f91eb7af7e0 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#14 0x7f91eb7ae330 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#15 0x7f91eb7addda in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#16 0x7f920c91c7fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7f920a49c454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#18 0x7f920c240eed in clone () from /lib/x86_64-linux-gnu/libc.so.6

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

[korganizer] [Bug 360934] Korganiser does not show reminders

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[ark] [Bug 362690] compress folder to tar.gz is not correct

[Elvis Angelaccio via KDE Bugzilla]

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

--- Comment #2 from Elvis Angelaccio  ---
The problem is in AddToArchive::detectBaseName().

We use QFileInfo::completeSuffix() on a path like "foo/test-3.4.0", which is
why the last digit is dropped.

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

[krita] [Bug 362712] New: Crash when switching OpenGL on/off

[via KDE Bugzilla]

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

Bug ID: 362712
   Summary: Crash when switching OpenGL on/off
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: OpenGL Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: elk...@yahoo.com

Happens on Win 7 64-bit SP1 and Linux Mint 17 LTS 64-bit

Krita 3.00-Beta-Master, two most recent builds
windows: 962bfe1 and f989682 
linux: 37389d5-x86_64 and e413f10-x86_64

Win krita-opengl.txt:  NVIDIA Corporation, GeForce GTX 750 Ti/PCIe/SSE2, 4.5.0
NVIDIA 364.72

Reproducible: Always

Steps to Reproduce:
1.Have an image open in Krita. The crash does NOT occur if there are no images
open.
2.Go to Settings>Configure Krita>Display 
3.Change OpenGL from on to off or from off to on.
4.Click OK to exit preferences

Actual Results:  
Krita crashes

Expected Results:  
Close preferences without crashing

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

[kwin] [Bug 362711] Opening firefox with custom shortcut Meta+N keeps Alt-key locked

[via KDE Bugzilla]

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

--- Comment #1 from g...@netcologne.de ---
Oh, an additional information: On my main PC in the office I am running the
last LTS kubuntu with KDE4 (IIRC version 14.04). On this PC the problem does
not occur. This is the reason why I think it might have to do with KDE5?

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

[kwin] [Bug 362711] New: Opening firefox with custom shortcut Meta+N keeps Alt-key locked

[via KDE Bugzilla]

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

Bug ID: 362711
   Summary: Opening firefox with custom shortcut Meta+N keeps
Alt-key locked
   Product: kwin
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: g...@netcologne.de

I do not know if this is an KDE oder firefox issue. Also I do not know which
component I should report this to. But I have the hope that someone has an idea
how to solve this?

II have defined a custom shortcut in the KDE system-settings:
"Meta+N" with action "/usr/bin/firefox --browser"

This opens a new firefox window by pressing the left Windows key together with
"n". I am using this since many years and because of working in the area of the
web I open many firefox windows each day.

Since some weeks (I think it did start already before upgrading from kubuntu
15.10 to 16.04, but I am not quite sure) I have the problem that a freshly
opened firefox window behaves like if the alt-key still was pressed. So if I
want to type something in the autofocused location bar that e.g. is starting
with "e", the "Edit" menu of firefox is opened instead of inserting the "e"
into the location bar. I have to press the escape key first, before I can work
with the firefox window normally.

Reproducible: Sometimes

Steps to Reproduce:
1. Define the mentioned custom hotkey in the system-settings
2. Press left windows key + "n".
3. A firefox window opens.
4. type something into the location bar (an URL or a search word, etc.)


Actual Results:  
Sometimes (very often), but not always you cannot type into the location bar.
Instead you are opening different menu items or other functionalities like you
were holding the alt-key pressed while typing.

Expected Results:  
The typed characters should show up in the location bar.

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

[ark] [Bug 362690] compress folder to tar.gz is not correct

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Elvis Angelaccio  ---
Confirming, thanks for the report.

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

[plasmashell] [Bug 362432] plasmashell crashed when right clicked tray volume icon

[Wolfgang Bauer via KDE Bugzilla]

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

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||wba...@tmo.at

--- Comment #2 from Wolfgang Bauer  ---
Looks related to bug#360968 I think...

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

[KScreen] [Bug 362708] The display preferences settings always unset when you removed the vga cable or restarts the system.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |se...@kde.org
Product|systemsettings  |KScreen
  Component|general |common

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

[kio-extras] [Bug 362709] kio_sftp.cpp:1239]: (style) Suspicious condition

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |default
Version|Git |unspecified
Product|kde |kio-extras
   Assignee|unassigned-b...@kde.org |plasma-de...@kde.org

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

[kmail2] [Bug 362710] New: Message list view does not show any text (invisible sender, subject, date etc)

[Dan Dart via KDE Bugzilla]

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

Bug ID: 362710
   Summary: Message list view does not show any text (invisible
sender, subject, date etc)
   Product: kmail2
   Version: 5.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: k...@dandart.co.uk

Once I set up my kmail, the message list view just shows invisible / missing
text for subject/from/date.
Tried to look at other inboxes ut same for every one.

Reproducible: Always

Steps to Reproduce:
1. View message list

Actual Results:  
Blank/invisible/missing subject/sender/date

Expected Results:  
Present subject/sender/date

I have updated my kernel to 4.6 but surely that won't have done it?
Ubuntu 16.04 upgraded from 15.10 using do-release-upgrade.

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

[kmail2] [Bug 362710] Message list view does not show any text (invisible sender, subject, date etc)

[Dan Dart via KDE Bugzilla]

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

--- Comment #1 from Dan Dart  ---
Created attachment 98789
  --> https://bugs.kde.org/attachment.cgi?id=98789=edit
Message list shown to me

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

[kcalc] [Bug 360105] Doesn't start with Qt 5.6

[Elvis Angelaccio via KDE Bugzilla]

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

--- Comment #16 from Elvis Angelaccio  ---
(In reply to Antonio Rojas from comment #15)
> Patch works fine here. It seems to create some excessive margin to the left
> of the buttons, but no big deal.

Yeah, there was an unnecessary horizontal spacer in the layout. I updated the
patch, should be fixed now.

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

[kcalc] [Bug 360105] Doesn't start with Qt 5.6

[Antonio Rojas via KDE Bugzilla]

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

--- Comment #15 from Antonio Rojas  ---
Patch works fine here. It seems to create some excessive margin to the left of
the buttons, but no big deal.

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

[kde] [Bug 362709] New: kio_sftp.cpp:1239]: (style) Suspicious condition

[via KDE Bugzilla]

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

Bug ID: 362709
   Summary: kio_sftp.cpp:1239]: (style) Suspicious condition
   Product: kde
   Version: Git
  Platform: RedHat RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: dcb...@hotmail.com

../../../kioslave/sftp/kio_sftp.cpp:1239]: (style) Suspicious condition
(assignment + comparison); Clarify expression with parentheses.

Source code is

} else if ((errorCode = writeToFile(fd, filedata.constData(),
filedata.size()) != 0)) {

Suggest new code

} else if ((errorCode = writeToFile(fd, filedata.constData(),
filedata.size())) != 0) {


Reproducible: Always

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

[kcalc] [Bug 360105] Doesn't start with Qt 5.6

[Elvis Angelaccio via KDE Bugzilla]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 CC||elvis.angelac...@kdemail.ne
   ||t

--- Comment #14 from Elvis Angelaccio  ---
Fix in https://git.reviewboard.kde.org/r/127847/

Please test it as soon as possible (deadline for 16.04.1 bugfixes is 23:59 UTC
of today).

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

[kwin] [Bug 362694] Mix of radiobuttons and checkboxes in desktop-effects dialog

[via KDE Bugzilla]

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

--- Comment #4 from slartibar...@gmail.com ---
Yes, agreed.
Still this makes way more sense to group those items into a 'magnifiers' group,
for example.

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

[krita] [Bug 359642] [UC-LOGIC] Tablet Pressure sensitivity not working

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 CC||dimul...@gmail.com

--- Comment #4 from Dmitry Kazakov  ---
Hi, AndeOn!

Could I ask you to get me a special debugging info for this tablet? Just
download any AppImage copy of Krita 3.0, and run it in terminal using this
line. You tablet should be connected at the moment. 

QT_LOGGING_RULES='qt.qpa.input.devices.debug=true'
./krita3-.appimage

You will see alot of lines like that:

qt.qpa.input.devices: XInput version 2.2 is available and Qt supports 2.2 or
greater
...
qt.qpa.input.devices: input device  Aiptek
qt.qpa.input.devices:has 7 buttons
qt.qpa.input.devices:it's a keyboard
qt.qpa.input.devices:has valuator "Abs X" recognized? true
qt.qpa.input.devices:has valuator "Abs Y" recognized? true
qt.qpa.input.devices:has valuator "Abs Wheel" recognized? true
qt.qpa.input.devices:has valuator "Abs Pressure" recognized? true
qt.qpa.input.devices:has valuator "Abs Tilt X" recognized? true
qt.qpa.input.devices:has valuator "Abs Tilt Y" recognized? true
qt.qpa.input.devices:has valuator "Abs Misc" recognized? false
qt.qpa.input.devices:has valuator "Rel Vert Wheel" recognized? true
qt.qpa.input.devices:it's a tablet with pointer type "pen"
qt.qpa.input.devices:it's a scrolling device

Please attach this output to the bugreport.

And for a case if your tablet is not recognized by the Qt, please also attach
the output of xinput command:

xinput list


When you do this, we will be able to make a testing build for you to make your
tablet work fine.

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

[krita] [Bug 361920] "Save File" Dialog Box not appearing upon closing program with multiple views of the same file open

[David REVOY via KDE Bugzilla]

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

--- Comment #2 from David REVOY  ---
Reproduced in Krita 2.9.7 too. This bug is not a 3.0 regression.

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

[Discover] [Bug 362538] Misaligned GUI elements

[Ettore Atalan via KDE Bugzilla]

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

--- Comment #7 from Ettore Atalan  ---
(K)Ubuntu packages.

URL: https://launchpad.net/ubuntu/xenial/+source/plasma-discover

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

[systemsettings] [Bug 362708] New: The display preferences settings always unset when you removed the vga cable or restarts the system.

[Rumbler via KDE Bugzilla]

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

Bug ID: 362708
   Summary: The display preferences settings always unset when you
removed the vga cable or restarts the system.
   Product: systemsettings
   Version: 5.6.3
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: rumbler.so...@rellcom.com.br

Whenever I enter the system with the cable connected vga or not, or retreat to
vga cable and reconnect it again the setting screens is fully unset, In my
preferences monitors have the standard laptop and a second LCD monitor
connected by a vga cable, the laptop screen is the default screen and your
desktop has the Folder Visualisation layout showing the directory / home /
Rumbler / Desktop and has a standard lower panel and a certain wallpaper. The
external monitor has a desktop with a desktop layout without nehum panel and a
different wallpaper laptop screen, this monitor is a laptop screen left. When I
remove the vga cable to use the laptop off my desk laptop desktop is without
the lower wallpaper panel becomes the external monitor and it changed the
layout of the desktop. If I reconnect the vga cable it changes again, but it's
always random, sometimes the panel goes to the laptop screen sometimes appears
on the external monitor, that is ruin because every time I turn off the system
leave the desk have to reconfigure the entire desktop environment.

Reproducible: Always

Steps to Reproduce:
1.Restart the system.
2. Remove the VGA cable.
3.Place the VGA cable with open Kde.

Actual Results:  
The layout scheme of the areas of work on both monitors are reversed.

Expected Results:  
To remain as set for me.

Application
System: Slackware 14:02
Version of KDE Plasma: 5.6.3
KDE Frameworks Version: 5.21.0
Qt Version: 5.6.0
Kernel Version: 4.4.8
type of operating system: 64-bit

'Hardware'
Processors 4 x Intel Core i3-3227U CPU @ 1.90GHz
Memory: RAM 7.6 GiB

This is my system, I do not have more information as it does not present infirm
error message with or log in the system. if they have any command or way to get
information about this defect just tell me that fasso here and return more
information.

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

[systemsettings] [Bug 362708] The display preferences settings always unset when you removed the vga cable or restarts the system.

[Rumbler via KDE Bugzilla]

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

Rumbler  changed:

   What|Removed |Added

 CC||rumbler.so...@rellcom.com.b
   ||r

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

[kgpg] [Bug 340802] The export option "Sauberer Schlüssel" is not documented

[Martin Schröder via KDE Bugzilla]

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

--- Comment #1 from Martin Schröder  ---
Ping. Anybody working on this?

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

[frameworks-knotifications] [Bug 353062] Freeze/failure to start when "show tray icon" is enabled

[Ahmad Samir via KDE Bugzilla]

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

Ahmad Samir  changed:

   What|Removed |Added

 CC||ahmadsamir3...@gmail.com

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

[krita] [Bug 362525] Advanced color selector configuration dialog unusable on HiDPI

[Ilya V . Portnov via KDE Bugzilla]

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

--- Comment #7 from Ilya V. Portnov  ---
Advanced color selector configuration dialog became much better with today
update from lime ppa. Thanks!

I also have (maybe related) similar problem with brush settings dialog on
hidpi. Should I create separate ticket for that?

-- 
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 #6 from Aleix Pol  ---
What packages are you running? What distro?

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

[krita] [Bug 362502] canvas is not updated when changing the zoom level with intuos' tablet pen.

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

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

--- Comment #4 from wolthera  ---
I am sorry, but you are best off using the nvidea card for Krita then.

The non-openGL canvas is slow as molasses, which is why we implemented an
OpenGL accelerated canvas to begin with. We can't do much to improve it anymore
:/

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

[krita] [Bug 361653] Show Painting Assistants has no effect

[Camille Bissuel via KDE Bugzilla]

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

--- Comment #4 from Camille Bissuel  ---
Sorry for the duplicate… was working for me on 2.9, but is not on 3.0 under
Antergos (Arch linux).

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

[krita] [Bug 362134] Alternative shortcuts breaks primary shortcuts in Krita 3.0 alpha.

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

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

--- Comment #5 from wolthera  ---
It seems fixed here. Resolving this for now.

Tyson, if you still come across it, don't hesitate to reopen.

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

[krita] [Bug 362488] "Restore Defaults" button in preferences not working

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/1168cfb82b81ac802a63ef6bd
   ||f1f804a3db2ec71
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Dmitry Kazakov  ---
Git commit 1168cfb82b81ac802a63ef6bdf1f804a3db2ec71 by Dmitry Kazakov.
Committed on 05/05/2016 at 14:01.
Pushed by dkazakov into branch 'master'.

Fix restoring default on the general Settings tab

Fixes T2415

M  +1-2libs/ui/dialogs/kis_dlg_preferences.cc

http://commits.kde.org/krita/1168cfb82b81ac802a63ef6bdf1f804a3db2ec71

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

[dolphin] [Bug 362707] New: Dolphin crashed when copying

[via KDE Bugzilla]

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

Bug ID: 362707
   Summary: Dolphin crashed when copying
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: pedron.alexan...@gmail.com

Application: dolphin (15.12.3)

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 was sliding a file from one
tab to another to copy from a folder to another when it crashed. I had three or
four folders opened in a single window.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f16014e28c0 (LWP 13291))]

Thread 2 (Thread 0x7f15f4c43700 (LWP 13293)):
#0  0x7f16142fe9cd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f160ab3a6c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f160aaf6e04 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f160aaf72c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f160aaf742c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f160f10ba9b in QEventDispatcherGlib::processEvents
(this=0x7f15f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f160f0b2dea in QEventLoop::exec (this=this@entry=0x7f15f4c42d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f160eecf8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7f160eed484e in QThreadPrivate::start (arg=0x2368420) at
thread/qthread_unix.cpp:331
#9  0x7f160b6826fa in start_thread (arg=0x7f15f4c43700) at
pthread_create.c:333
#10 0x7f161430eb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f16014e28c0 (LWP 13291)):
[KCrash Handler]
#6  QObject::~QObject (this=0x2b97f50, __in_chrg=) at
kernel/qobject.cpp:907
#7  0x7f1612bef6d9 in KIO::JobUiDelegate::~JobUiDelegate (this=0x2b97f50,
__in_chrg=) at ../../../src/widgets/jobuidelegate.cpp:57
#8  0x7f16105f6d3e in KJob::~KJob (this=0x2b99370, __in_chrg=) at ../../../src/lib/jobs/kjob.cpp:64
#9  0x7f16123d8e09 in KIO::CopyJob::~CopyJob (this=0x2b99370,
__in_chrg=) at ../../../src/core/copyjob.cpp:290
#10 0x7f160f0e4ec0 in QObject::event (this=0x2b99370, e=) at
kernel/qobject.cpp:1230
#11 0x7f160fbb805c in QApplicationPrivate::notify_helper
(this=this@entry=0x1d4d3e0, receiver=receiver@entry=0x2b99370,
e=e@entry=0x2d28f20) at kernel/qapplication.cpp:3716
#12 0x7f160fbbd516 in QApplication::notify (this=0x7ffdfae0b5e0,
receiver=0x2b99370, e=0x2d28f20) at kernel/qapplication.cpp:3499
#13 0x7f160f0b562b in QCoreApplication::notifyInternal
(this=0x7ffdfae0b5e0, receiver=0x2b99370, event=event@entry=0x2d28f20) at
kernel/qcoreapplication.cpp:965
#14 0x7f160f0b7a26 in QCoreApplication::sendEvent (event=0x2d28f20,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#15 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x1d4b870) at
kernel/qcoreapplication.cpp:1593
#16 0x7f160f0b7f08 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1451
#17 0x7f160f10b673 in postEventSourceDispatch (s=0x1d83510) at
kernel/qeventdispatcher_glib.cpp:271
#18 0x7f160aaf7127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f160aaf7380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f160aaf742c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f160f10ba7f in QEventDispatcherGlib::processEvents (this=0x1d839a0,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#22 0x7f160f0b2dea in QEventLoop::exec (this=this@entry=0x7ffdfae0b4b0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#23 0x7f160f0bae8c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#24 0x7f160f5fec3c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1542
#25 0x7f160fbb4495 in QApplication::exec () at kernel/qapplication.cpp:2976
#26 0x7f161462ee2b in kdemain (argc=1, argv=) at
/build/dolphin-HvGmRr/dolphin-15.12.3/src/main.cpp:150
#27 0x7f1614228830 in __libc_start_main (main=0x400710 ,
argc=1, argv=0x7ffdfae0b768, init=, fini=,
rtld_fini=, stack_end=0x7ffdfae0b758) at ../csu/libc-start.c:291
#28 0x00400749 in _start ()

Possible duplicates by query: bug 350668.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all 

[krita] [Bug 362704] Can't hide Assistant Previews with the "View" menu

[wolthera via KDE Bugzilla]

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

wolthera  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||griffinval...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #1 from wolthera  ---


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

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

[krita] [Bug 361653] Show Painting Assistants has no effect

[wolthera via KDE Bugzilla]

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

--- Comment #3 from wolthera  ---
that's weird, both options are working here on ubuntu 16.04 with master git
3991551

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