[kate] [Bug 357463] Untranslated point in menu

[Burkhard Lueck via KDE Bugzilla]

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

Burkhard Lueck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME
 CC||lu...@hube-lueck.de

--- Comment #2 from Burkhard Lueck  ---
The string is translated in kubuntu-16.04-beta2-desktop-amd64 and in recent
master compilied from surces.

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

[krita] [Bug 356058] Krita Animation Beta - Frame Ranges Cannot Be Selected With Graphic Tablet Stylus

[via KDE Bugzilla]

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

sayantan.chaudhuri+...@gmail.com changed:

   What|Removed |Added

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

--- Comment #7 from sayantan.chaudhuri+...@gmail.com ---
I just tested with the 3.0 Alpha AppImage [
krita3-prealpha3-de0d43d-x86_64.appimage ] and this behavior is no longer
present. 

Frame-range selection with a stylus now works as expected.

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

[kmail2] [Bug 361196] crash when one add new mail account because KDE wallet is off

[Laurent Montel via KDE Bugzilla]

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

--- Comment #3 from Laurent Montel  ---
Ok thanks for info.
I see the checkbox I disabled it.
But I can't reproduce it.
Perhaps there was a fix in kwallet in new package.
I will continue to investigate

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

[frameworks-kdelibs4support] [Bug 339569] QObject::tr calls in src/kdecore/kcmdlineargs.cpp

[Burkhard Lueck via KDE Bugzilla]

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

Burkhard Lueck  changed:

   What|Removed |Added

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

--- Comment #1 from Burkhard Lueck  ---
Fixed by Montel Laurent
Mon, 30 Nov 2015 05:52:32 + (06:52 +0100) 

https://quickgit.kde.org/?p=kdelibs4support.git=commit=f483b4107c83d86f9639278b3f5c70726f1eae32

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

[plasmashell] [Bug 361222] System tray is unavailable with error message in task bar

[James E . Jones via KDE Bugzilla]

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

--- Comment #3 from James E. Jones  ---
(In reply to Demian Lizandro Biscocho from comment #2)
> Got the same issue. Running Kubuntu 15.10 with Neon repositories. Installing
> qml-module-qtqml-models2 solved the issue. Run "apt-get install
> qml-module-qtqml-models2" on terminal.

Fixed it for me!

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

[plasmashell] [Bug 361222] System tray is unavailable with error message in task bar

[Demian Lizandro Biscocho via KDE Bugzilla]

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

Demian Lizandro Biscocho  changed:

   What|Removed |Added

 CC||demian.bisco...@gmail.com

--- Comment #2 from Demian Lizandro Biscocho  ---
Got the same issue. Running Kubuntu 15.10 with Neon repositories. Installing
qml-module-qtqml-models2 solved the issue. Run "apt-get install
qml-module-qtqml-models2" on terminal.

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

[plasmashell] [Bug 361250] Plasma randomly freezes and eventually crashes and restarts

[Kott via KDE Bugzilla]

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

Kott  changed:

   What|Removed |Added

 CC||k...@kott.no-ip.biz

--- Comment #1 from Kott  ---
The same, but crashes are very rare. And I don't know how to investigate this.
I've tried to clean .cache
https://forum.kde.org/viewtopic.php?f=289=124690=328672=plasmashell+freeze#p328672

I've tried to change plasma theme, thought there is bug in them
https://bugs.kde.org/show_bug.cgi?id=360173

I've tried empty ~/ dir (I don't want to reinstall my system)

I used minimal set of plasmoids: start menu, pager, icon-tasks, tray, clock. No
luck.
Yes I can connect to plasmashell via gdb or dbus, but for what? These freezes
are Very annoying, much more than any other issues.

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

[Breeze] [Bug 361249] GTK 3.20.x compatibility

[via KDE Bugzilla]

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

scionicspec...@gmail.com changed:

   What|Removed |Added

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

--- Comment #5 from scionicspec...@gmail.com ---


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

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

scionicspec...@gmail.com changed:

   What|Removed |Added

 CC||fadem...@gmail.com

--- Comment #4 from scionicspec...@gmail.com ---
*** Bug 361249 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 346858] Sliders for minimum/maximu width of panel is not visible

[Gordon via KDE Bugzilla]

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

Gordon  changed:

   What|Removed |Added

 CC||gor...@dickens.com

--- Comment #5 from Gordon  ---
@Ivan,  any chance that you will fix this problem in the Slim Glow theme for
Plasma 5 any time soon?  I really like the Slim Glow Theme and I think that
this is the only issue using it with Plasma 5.

Thanks,

Gordon Dickens

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

[dolphin] [Bug 278236] Cannot drag file onto chromium upload form input

[mrcl via KDE Bugzilla]

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

mrcl  changed:

   What|Removed |Added

 CC||mrcl...@gmail.com

--- Comment #21 from mrcl  ---
I confirm this problem here as well.
Drag and drop from Dolphin doesn't work with emacs either.

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

[plasmashell] [Bug 361228] little box around filenames is missing with Plasma 5.6

[FabiB via KDE Bugzilla]

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

--- Comment #3 from FabiB  ---
Created attachment 98184
  --> https://bugs.kde.org/attachment.cgi?id=98184=edit
bad readability on 4 backgrounds

Mostly black+white things. so many "normal" anime/manga backgrounds gives us
hard readability on many screens.

i'm also a little shoked that you even tried this... after all this
translucenty, blurry things on windows and KDE Plamsa 1 that makes it hard to
read text somewhere. after all Plasma distros are choosing a more "solid" dark
plasma theme instead of the translucent white(exept for KaOS, who choose a
solid, white one and some who only ship vanilla packages). it should be clear
that nobody wants this, but a always good readable thing like it finally was
with the last versions of kde plasma
:(

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

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

--- Comment #12 from Jack  ---
Well, if you don't have a backup copy of the small database before fixing, then
capturing the fixes is no longer an option.

Different sizes of databases containing the same content does not surprise me
too much - there are lots of local configuration issues like block size,
minimum table size, ... (I'm mainly guessing, but I do have some database
background.)

Unfortunately, it sounds like running a debugger would be too difficult for
you.  The simple explanation is that you run the debugger, and it runs
KMyMoney.  If it has the right information (source code and debugging symbols
compiled in) then you can watch how it runs in the source code, and can set
breakpoints (places it just stops for further instructions instead of just
going on.)  It can be very useful for a developer, as you can also examine the
value of variables, so if you know where it blows up, you can set a breakpoint
a few lines earlier, or before it calls that function, and explore the state of
things right before the problem.  Unfortunately, it is not something to learn
quickly.  

One thing I just thought of - can you reinstall an earlier  version, where you
were not getting the crash?  If so, you might be able to save as a file, or
even as an anonymized file.  Then you could try the new version, or submit the
anonymized file to the developers.  (An anonymized file changes all account
numbers and all actual financial values - changing them to random values.)

I suppose it would be helpful if we could replicate the consistency checks as
sql queries, but I'm not sure how difficult that would be.  Maybe one of the
developers who works specifically on the database back end can make a
suggestion.

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

[Baloo] [Bug 361259] New: baloo crashes

[John theFish via KDE Bugzilla]

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

Bug ID: 361259
   Summary: baloo crashes
   Product: Baloo
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: j...@c5magic.co.uk
CC: pinak.ah...@gmail.com

Application: baloo_file_extractor (5.19.0)

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

-- Information about the crash:
It happens every time I power on and login.
(I hope I remembered the name above correctly)

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc9684b88c0 (LWP 1780))]

Thread 2 (Thread 0x7fc9512c2700 (LWP 1843)):
#0  0x7fc964a67fdd in poll () at /lib64/libc.so.6
#1  0x7fc95f11c272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7fc95f11dee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7fc954634da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7fc9656703de in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7fc963b7960a in start_thread () at /lib64/libpthread.so.0
#6  0x7fc964a73a4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fc9684b88c0 (LWP 1780)):
[KCrash Handler]
#5  0x7fc94b49a818 in Exiv2::ValueType::toFloat(long) const () at /lib64/libexiv2.so.14
#6  0x7fc94b87c2c8 in (anonymous namespace)::toVariantDouble(Exiv2::Value
const&) [clone .constprop.49] () at
/usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
#7  0x7fc94b87db85 in
KFileMetaData::Exiv2Extractor::add(KFileMetaData::ExtractionResult*,
Exiv2::ExifData const&, KFileMetaData::Property::Property, char const*,
QVariant::Type) [clone .constprop.43] () at
/usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
#8  0x7fc94b87e1e1 in
KFileMetaData::Exiv2Extractor::extract(KFileMetaData::ExtractionResult*) () at
/usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
#9  0x5608d6c66513 in Baloo::App::index(Baloo::Transaction*, QString
const&, unsigned long long) ()
#10 0x5608d6c6700f in Baloo::App::processNextFile() ()
#11 0x7fc96588c888 in QSingleShotTimer::timerEvent(QTimerEvent*) () at
/lib64/libQt5Core.so.5
#12 0x7fc965881113 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#13 0x7fc96653641c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#14 0x7fc96653b8e6 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#15 0x7fc96585173b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#16 0x7fc9658a6ccd in QTimerInfoList::activateTimers() () at
/lib64/libQt5Core.so.5
#17 0x7fc9658a7209 in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#18 0x7fc9633e0e3a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#19 0x7fc9633e11d0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#20 0x7fc9633e127c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#21 0x7fc9658a7eaf in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#22 0x7fc96584eeca in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#23 0x7fc965856fac in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#24 0x5608d6c659d5 in main ()

Reported using DrKonqi

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

--- Comment #11 from lp.allar...@gmail.com ---
I just noticed:  the tables "kmmKeyValuePairs" are 64kb in the copied DB, and
2MB in the original DB, and tables "kmmSplits" are 4.9MB in the original DB and
4MB in the copied DB...

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

--- Comment #10 from lp.allar...@gmail.com ---
Hello Jack,  I was too quick on the "OK button" and did not have time to
carefully read what was fixed when saving to a flat file.

I'd like to try to manually fix whats wrong in the large database but where to
start!?

It does run a consistency check automatically when saving to a file.

I setup a copy of the problematic DB in MySQL (replicated the entire DB). 
Strange thing, the original and copy have different sizes! Weird.  Anyways, now
I can mess with the copy as we need to find the culprit.

For the debugger, you lost me there!

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

[kdelibs] [Bug 347917] knotify crash on openSUSE because of mismatch in vlc version

[Christoph Feck via KDE Bugzilla]

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

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

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

[amarok] [Bug 361113] Amarok crashes on start

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Christoph Feck  ---


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

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

[kdelibs] [Bug 347917] knotify crash on openSUSE because of mismatch in vlc version

[Christoph Feck via KDE Bugzilla]

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

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

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

[Phonon] [Bug 361111] digikam doesn't start

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE

--- Comment #2 from Christoph Feck  ---


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

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

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

--- Comment #9 from Jack  ---
I'm pretty much guessing here, but if you can capture the 27 errors that were
fixed in the smaller version, can you make those corrections manually on the
larger version? If so, you might get farther in then saving the larger one as a
file.  

Am I correct that it crashes either running the consistency check on the larger
database, and also crashes trying to save that database as a file, probably
because it runs the consistency check.  If so, I would try to figure out from
the backtrace (perhaps running in a debugger?) and try to trap the error, so
although it may not correct the error, it wont just abort.  That may also show
you what it is choking on, and you might be able to fix it manually.  I don't
know if the Claydoh repository includes a version with debug symbols, but if
so, that would produce more useful backtraces and be easier to run in a
debugger.

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

[korganizer] [Bug 361258] New: kontact calendar should not attempt to open wallet when groupware is not configured

[via KDE Bugzilla]

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

Bug ID: 361258
   Summary: kontact calendar should not attempt to open wallet
when groupware is not configured
   Product: korganizer
   Version: 15.12.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: r...@alum.mit.edu

When creating a new event in my calendar, kontact opens the kde wallet.  I
don't have any groupware configured (I just use this as a personal calendar),
so this event won't be published anywhere, so there's no reason to open the
wallet.

Reproducible: Always

Steps to Reproduce:
1. Open kontact/calendar
2. Click somewhere to create event
3. Watch prompt for wallet password

Actual Results:  
Get prompted for wallet password

Expected Results:  
Event editor opens without opening wallet.

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

--- Comment #8 from lp.allar...@gmail.com ---
I did a few tests:

created a new flat file (.kmy) and consistency check does not crash with
4.7.2..good
created a new database file with 4.7.2, consistency check does not crash
either. good
Consistency check does crash on my two existing pre-4.7.2 databases

I saved one of the crashing databases (the smaller one) to a flat file, then
ran the consistency check.  First when saving, it said that there was some 27
errors that were fixed, then saved.

I tried to do the same thing with the larger DB, it crashes when saving to a
.kmy file.  I suspect there are really lots of errors in that DB. 

Now how can I fix those without hosing the entire DB?

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

[kde] [Bug 361257] New: Colorscheme and other settings should not be copied into kdeglobals

[Ivan Shapovalov via KDE Bugzilla]

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

Bug ID: 361257
   Summary: Colorscheme and other settings should not be copied
into kdeglobals
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: inte...@intelfx.name

Currently, when one selects a KDE color scheme in systemsettings, it
effectively has its contents _copied_ into kdeglobals. Instead, the color
scheme name in [General]/ColorScheme could be used to lookup the color scheme
file and read it in run-time, but it isn't so.

This is scripting-unfriendly.

Reproducible: Always

Steps to Reproduce:
1. Set a non-default color scheme via systemsettings
2. Open kdeglobals in editor, remove all sections like [ColorEffects:*],
[Colors:*], [DesktopIcons], [DialogIcons] (but not [General])
3. Open any application

Actual Results:  
Default color scheme is used.

Expected Results:  
Color scheme is looked up using [General]/ColorScheme config key, read in
runtime and applied

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

[kmymoney4] [Bug 361246] Kmymoney won't start

[Jack via KDE Bugzilla]

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

--- Comment #3 from Jack  ---
As Allan pointed out (although it was only to the mailing list, not to the bug)
you are running a frameworks version of KMyMoney.  This has not yet been
released, and it is not really ready for production use.  4.7.2 is the most
recent official release, but it still uses kdelibs, not frameworks.  I'm not
sure why they chose to package this version (from git - not released) since it
obviously doesn't work.  The frameworks version is still under development, but
there is not yet a proposed timeline for release.

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

[plasmashell] [Bug 361200] Plasmashell Signal: Illegal Instruction - On KUBUNTU 16.04 Beta2 - During Install - Under Hyper-V

[Harrison via KDE Bugzilla]

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

--- Comment #1 from Harrison  ---
Installed Kubuntu 15.10 under Hyper-V on Intel E3-1275-v5 & chipset C236 and
everything worked fine.

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

[plasmashell] [Bug 361223] plasmashell hangs up after a day of inactivity

[Alexander Potashev via KDE Bugzilla]

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

--- Comment #1 from Alexander Potashev  ---
Judging by frozen digital clock widget, plasmashell hung up after either 1 hour
or 25 hours of inactivity. But I believe it was 25 hours because I never saw
plasmashell hanging up overnight on the same Fedora 23 system.

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

[konsole] [Bug 350845] 'konsole' instead of 'Konsole' in menu entries

[André Marcelo Alvarenga via KDE Bugzilla]

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

André Marcelo Alvarenga  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from André Marcelo Alvarenga  ---
Capitalized in 15.12.3 version.

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

[konsole] [Bug 350843] Konsole don't load translated "Split View" string

[André Marcelo Alvarenga via KDE Bugzilla]

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

André Marcelo Alvarenga  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from André Marcelo Alvarenga  ---
Works for me now.
Version: 15.12.3

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

[konsole] [Bug 350844] Untranslated string in message dialog

[André Marcelo Alvarenga via KDE Bugzilla]

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

--- Comment #5 from André Marcelo Alvarenga  ---
(In reply to Burkhard Lueck from comment #4)
> Please try again with updated packages, thanks for reporting

Works for me too.

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

[konsole] [Bug 361256] New: Close/exit konsole on bash crash/termination

[via KDE Bugzilla]

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

Bug ID: 361256
   Summary: Close/exit konsole on bash crash/termination
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: w...@obsidian-studios.com

There are many times I want to end a bash terminal session without recording my
history. I use kill -9 $BASHPID to exit bash and not save my history. I do that
so often I have an alias for it, bye. Every time I do this on konsole, instead
of konsole closing/exiting, I get a message in red "Warning: Program
'/bin/bash' crashed."

Reproducible: Always

Steps to Reproduce:
1. Open konsole
2. kill -9 $BASHPID
3. manually close the konsole window

Actual Results:  
Once bash crashes ( is killed ) and I must manually close the konsole window.

Expected Results:  
Konsole would close/exit upon bash crash. That way when I do kill -9 $BASHPID,
it closes the window entirely. Which is what I want to happen in addition to
not saving history. I am done with that terminal window entirely.

There really is no benefit to keeping the window open after bash crashes. Maybe
for scrollback history, but in my case I specifically do not care about the
history. Thus not wanting bash to record it to file. There is nothing more that
can be done in that window. You cannot resume or restart the crashed/killed
bash session.

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

[krita] [Bug 360972] Brush Editor is too large for smaller screens

[prijatelj via KDE Bugzilla]

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

--- Comment #2 from prijatelj  ---
I was testing some of the G'MIC filters when I bumped into this bug. It has a
work around (cmd+Q and then hit cancel), but definitely something not appeasing
for OSX users.  And your work around of right click and selecting detach does
not work. I get into the bug, right click, select detach, and it appears
nothing happens. This is because the top bar that appears when detached, is
still out of the user's visible and intractable space After selecting detach, I
attempt to drag the box away from the top, but to no avail. (Can only click and
drag is I see the bar, which I do not)

All OSX applications never go above or cover up the top menu bar. The only time
it should ever disappear is when in full screen mode, but then the user should
be able to put their mouse at the top of screen and it reappears. In this case
the box covers it and makes it inaccessible entirely, as well as unmovable,
because I suspect the top of this box is what you click to drag and move it
around, which is why the detach does not work, as far as I know. If I am
incorrect and you can click anywhere (that does not invoke an action, ie.
hitting a button) in the box to drag it, then that does not work in OSX either.

Also, I am uncertain if this may simply be a "smaller screen" problem, I think
it would be a problem in all systems. My laptop has a 13.3-inch (2560 x 1600)
screen. Despite actual size, I'm pretty sure that's either an average or above
average screen resolution. I also am more certain it is not limited to smaller
screen sizes, because the brush editor popup appears up there no matter the
location of the actual main program window. And that means that even if marked
as attached to toolbar, its not acting like expected when stated to be attached
to the toolbar. By this I mean, I would expect the popup to appear underneath
the krita toolbar,  but instead it appears statically at the top. This is most
likely an error simply in when it is called to appear, it is not taking into
account the relative location of the tool bar, and also when stated to be
detached I doubt it takes into consideration the location of the system menu
bar.

If I have free time in summer, I will attempt to handle this bug, since it is
mac specific. My studies end and I get free time starting at May 8th. The Krita
tasks will begin then. ;)

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

[dolphin] [Bug 361255] New: dolphin crash

[via KDE Bugzilla]

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

Bug ID: 361255
   Summary: dolphin crash
   Product: dolphin
   Version: 15.12.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: joecold...@yahoo.com

Application: dolphin (15.12.3)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.6 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed: The crash occurred when I
simply clicked the "x" in the upper right hand corner to close out the program,
nothing more. I am running on a VM and that might have something to do with it.

-- Backtrace:
Application: Dolphin (dolphin), signal: Floating point exception
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f62b4aa3f49 in pthread_barrier_destroy () at /lib64/libpthread.so.0
#7  0x7f62a551e8ef in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#8  0x7f62a5529fd1 in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#9  0x7f62a51e19af in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#10 0x7f62a51e1a55 in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#11 0x7f62a51dff3f in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#12 0x7f62b440b092 in  () at /usr/lib64/libGL.so.1
#13 0x7f62b43ee026 in  () at /usr/lib64/libGL.so.1
#14 0x7f62b43ee0a9 in  () at /usr/lib64/libGL.so.1
#15 0x7f62b43ee1fe in  () at /usr/lib64/libGL.so.1
#16 0x7f62b6fb88b2 in XCloseDisplay () at /usr/lib64/libX11.so.6
#17 0x7f62aa0dd126 in QXcbConnection::~QXcbConnection() () at
/usr/lib64/libQt5XcbQpa.so.5
#18 0x7f62aa0dd489 in QXcbConnection::~QXcbConnection() () at
/usr/lib64/libQt5XcbQpa.so.5
#19 0x7f62aa0dee26 in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#20 0x7f62aa0def39 in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#21 0x7f62b94174e3 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
at /usr/lib64/libQt5Gui.so.5
#22 0x7f62b9bf6509 in QApplicationPrivate::~QApplicationPrivate() () at
/usr/lib64/libQt5Widgets.so.5
#23 0x7f62b8a67fb8 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#24 0x7f62b9bf8179 in QApplication::~QApplication() () at
/usr/lib64/libQt5Widgets.so.5
#25 0x7f62c02d50f6 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#26 0x7f62b7b7f7d0 in __libc_start_main () at /lib64/libc.so.6
#27 0x00400b49 in _start ()

Reported using DrKonqi

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

[konsole] [Bug 361254] New: konsole crash

[via KDE Bugzilla]

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

Bug ID: 361254
   Summary: konsole crash
   Product: konsole
   Version: 15.12.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: joecold...@yahoo.com

Application: konsole (15.12.3)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.6 x86_64
Distribution (Platform): Slackware Packages

-- Information about the crash:
- What I was doing when the application crashed:opened konsole in
/home/downloads/ (using dolphin) and then started pkgtool (slackware program)
to install a program. The program installed and then returned to a prompt. When
I closed out the konsole then the bug report tool popped up saying konsole had
crashed. Was able to reproduce/get the same results. Right click in the
downloads folder/select open terminal from the menu/type pkgtool at the
prompt/install program/close out konsole by using the mouse and clicking the
"x"/bug report pops up saying konsole crashed.

-- Backtrace:
Application: Konsole (konsole), signal: Floating point exception
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f2a01b63f49 in pthread_barrier_destroy () at /lib64/libpthread.so.0
#7  0x7f29ee2ba8ef in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#8  0x7f29ee2c5fd1 in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#9  0x7f29edf7d9af in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#10 0x7f29edf7da55 in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#11 0x7f29edf7bf3f in  () at /usr/lib64/xorg/modules/dri/swrast_dri.so
#12 0x7f2a01905092 in  () at /usr/lib64/libGL.so.1
#13 0x7f2a018e8026 in  () at /usr/lib64/libGL.so.1
#14 0x7f2a018e80a9 in  () at /usr/lib64/libGL.so.1
#15 0x7f2a018e81fe in  () at /usr/lib64/libGL.so.1
#16 0x7f2a02f0f8b2 in XCloseDisplay () at /usr/lib64/libX11.so.6
#17 0x7f29f71eb126 in QXcbConnection::~QXcbConnection() () at
/usr/lib64/libQt5XcbQpa.so.5
#18 0x7f29f71eb489 in QXcbConnection::~QXcbConnection() () at
/usr/lib64/libQt5XcbQpa.so.5
#19 0x7f29f71ece26 in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#20 0x7f29f71ecf39 in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#21 0x7f2a055344e3 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
at /usr/lib64/libQt5Gui.so.5
#22 0x7f2a05d13509 in QApplicationPrivate::~QApplicationPrivate() () at
/usr/lib64/libQt5Widgets.so.5
#23 0x7f2a0503afb8 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#24 0x7f2a05d15179 in QApplication::~QApplication() () at
/usr/lib64/libQt5Widgets.so.5
#25 0x7f2a0bc32719 in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#26 0x7f2a041527d0 in __libc_start_main () at /lib64/libc.so.6
#27 0x00400ae9 in _start ()

Reported using DrKonqi

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

[valgrind] [Bug 361253] [s390x] ex_clone.c:42: undefined reference to `pthread_create'

[dann frazier via KDE Bugzilla]

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

dann frazier  changed:

   What|Removed |Added

 CC||da...@dannf.org

--- Comment #1 from dann frazier  ---
Created attachment 98183
  --> https://bugs.kde.org/attachment.cgi?id=98183=edit
Move -lpthread to end of linker command line

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

[valgrind] [Bug 361253] New: [s390x] ex_clone.c:42: undefined reference to `pthread_create'

[dann frazier via KDE Bugzilla]

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

Bug ID: 361253
   Summary: [s390x] ex_clone.c:42: undefined reference to
`pthread_create'
   Product: valgrind
   Version: 3.11 SVN
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: da...@dannf.org

'make regtest' on trunk currently fails on Ubuntu 16.04/s390x.

gcc -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector   -m64  
-lpthread  -o ex_clone ex_clone.o  
ex_clone.o: In function `main':
/home/ubuntu/valgrind/none/tests/s390x/ex_clone.c:42: undefined reference to
`pthread_create'
/home/ubuntu/valgrind/none/tests/s390x/ex_clone.c:57: undefined reference to
`pthread_join'
collect2: error: ld returned 1 exit status
Makefile:1324: recipe for target 'ex_clone' failed



Reproducible: Always

Steps to Reproduce:
1. Install Ubuntu 16.04 on an s390x system
2. svn clone svn://svn.valgrind.org/valgrind/trunk valgrind
3. cd valgrind; ./autogen.sh; ./configure; make regtest


Actual Results:  
gcc -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector   -m64  
-lpthread  -o ex_clone ex_clone.o  
ex_clone.o: In function `main':
/home/ubuntu/valgrind/none/tests/s390x/ex_clone.c:42: undefined reference to
`pthread_create'
/home/ubuntu/valgrind/none/tests/s390x/ex_clone.c:57: undefined reference to
`pthread_join'
collect2: error: ld returned 1 exit status
Makefile:1324: recipe for target 'ex_clone' failed

Expected Results:  
Successful build.

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

[muon] [Bug 361252] New: my updatmanager wil not work

[Zonnebloem via KDE Bugzilla]

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

Bug ID: 361252
   Summary: my updatmanager wil not work
   Product: muon
   Version: unspecified
  Platform: Ubuntu Packages
OS: other
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: toewijd...@xs4all.nl
CC: aleix...@kde.org, sit...@kde.org

update manager does not work

i got problems men i installed hp lip for hp laserjet p1102w

zentyal i can not configure it?

Reproducible: Always

Steps to Reproduce:
1. try to install zentyal 
2.
3.

Actual Results:  
does not work

Expected Results:  
i can not update

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

[digikam] [Bug 354364] Crash of DNG converter

[via KDE Bugzilla]

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

--- Comment #32 from jon33...@yahoo.co.uk ---
(In reply to D. van Aken from comment #31)
> I tried the workaround given by jon33040. Unfortunately, it does not work
> for my system (Kubuntu 15.10, KDE Plasma version 5.4.2 with Digikam 4.12.0).

Running digikam from the command line with this recipe will print the
directories where it is looking for process-working.png. You can then try
copying process-working.png to one of those directories.

strace -f -e access digikam |& grep process-working | grep -v /usr/

What it prints on my laptop is the following;

pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0
[pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0
[pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0
[pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0
[pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0
[pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0
[pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0
[pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0
[pid 10844]
access("/home/jon/.kde/share/apps/digikam/toolbar/process-working.png", R_OK) =
0

and so on

Hence the directory in the work-around in comment 29.

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

[digikam] [Bug 354364] Crash of DNG converter

[D . van Aken via KDE Bugzilla]

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

--- Comment #31 from D. van Aken  ---
I tried the workaround given by jon33040. Unfortunately, it does not work for
my system (Kubuntu 15.10, KDE Plasma version 5.4.2 with Digikam 4.12.0).

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

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

[Rog131 via KDE Bugzilla]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #3 from Rog131  ---
Same as the https://bugs.kde.org/show_bug.cgi?id=361249 ?

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

[Breeze] [Bug 361249] GTK 3.20.x compatibility

[Rog131 via KDE Bugzilla]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #4 from Rog131  ---
Same as the https://bugs.kde.org/show_bug.cgi?id=361066 ?

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

[kwin] [Bug 361241] Double click to maximize does not work in some situations

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Thomas Lübking  ---
Looking at the patch, I seem to have messed it on resolving a merge conflict
(wrong indentention/linebreak and it actually doesn't make any sense the way it
is)

@Martin, better don't wait for me to push this.



diff --git a/abstract_client.cpp b/abstract_client.cpp
index b323030..aab929f 100644
--- a/abstract_client.cpp
+++ b/abstract_client.cpp
@@ -1406,14 +1406,13 @@ bool
AbstractClient::processDecorationButtonPress(QMouseEvent *event, bool ignor
 const quint64 interval = m_decoration.doubleClickTimer.elapsed();
 m_decoration.doubleClickTimer.invalidate();
 if (interval >
QGuiApplication::styleHints()->mouseDoubleClickInterval()) {
-m_decoration.doubleClickTimer.invalidate(); // expired -> new
first click and pot. init
+m_decoration.doubleClickTimer.start(); // expired -> new first
click and pot. init
 } else {
 Workspace::self()->performWindowOperation(this,
options->operationTitlebarDblClick());
 dontMoveResize();
 return false;
 }
-}
- else {
+} else {
 m_decoration.doubleClickTimer.start(); // new first click and pot.
init, could be invalidated by release - see below
 }
 }

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

[Akonadi] [Bug 357179] Moving an email to a collection without remote ID keeps copy in old collection

[Simon Andric via KDE Bugzilla]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[plasmashell] [Bug 361251] New: Plasma Crashes when main/only monitor auto turns off/suspends

[bugzy via KDE Bugzilla]

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

Bug ID: 361251
   Summary: Plasma Crashes when main/only monitor auto turns
off/suspends
   Product: plasmashell
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugzylit...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
After some inactivity, my monitor on my desktop initiates the powersave feature
and turns off the screen to conserve power. Whenever I return and login, plasma
has crashed along with ksm server and a bunch of other services.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f4c27f15940 (LWP 16973))]

Thread 7 (Thread 0x7f4c074b5700 (LWP 16985)):
#0  0x7f4c1f8ecfdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4c25da7272 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f4c074b4b80) at /usr/include/bits/poll2.h:46
#2  0x7f4c25da7272 in _xcb_conn_wait (c=c@entry=0x562fe55c8080,
cond=cond@entry=0x562fe55c80c0, vector=vector@entry=0x0, count=count@entry=0x0)
at xcb_conn.c:459
#3  0x7f4c25da8ee7 in xcb_wait_for_event (c=0x562fe55c8080) at xcb_in.c:693
#4  0x7f4c09ddfda9 in QXcbEventReader::run() (this=0x562fe55d2250) at
qxcbconnection.cpp:1255
#5  0x7f4c204f53de in QThreadPrivate::start(void*) (arg=0x562fe55d2250) at
thread/qthread_unix.cpp:331
#6  0x7f4c1ec3060a in start_thread (arg=0x7f4c074b5700) at
pthread_create.c:334
#7  0x7f4c1f8f8a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f4c04a64700 (LWP 16995)):
#0  0x7f4c1f8ecfdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4c1ae1016c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f4bf8003070, timeout=, context=0x7f4bf8000990) at
gmain.c:4135
#2  0x7f4c1ae1016c in g_main_context_iterate
(context=context@entry=0x7f4bf8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f4c1ae1027c in g_main_context_iteration (context=0x7f4bf8000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f4c2072cecb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4bf80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f4c206d3eca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4c04a63c60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f4c204f0434 in QThread::exec() (this=this@entry=0x562fe56a05f0) at
thread/qthread.cpp:503
#7  0x7f4c2483e9b5 in QQmlThreadPrivate::run() (this=0x562fe56a05f0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7f4c204f53de in QThreadPrivate::start(void*) (arg=0x562fe56a05f0) at
thread/qthread_unix.cpp:331
#9  0x7f4c1ec3060a in start_thread (arg=0x7f4c04a64700) at
pthread_create.c:334
#10 0x7f4c1f8f8a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f4bfcc38700 (LWP 17001)):
#0  0x7f4c1f8ecfdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4c1ae1016c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f4bf0002e70, timeout=, context=0x7f4bf990) at
gmain.c:4135
#2  0x7f4c1ae1016c in g_main_context_iterate
(context=context@entry=0x7f4bf990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f4c1ae1027c in g_main_context_iteration (context=0x7f4bf990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f4c2072cecb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4bf8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f4c206d3eca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4bfcc37c60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f4c204f0434 in QThread::exec() (this=this@entry=0x562fe58ff560) at
thread/qthread.cpp:503
#7  0x7f4c2483e9b5 in QQmlThreadPrivate::run() (this=0x562fe58ff560) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7f4c204f53de in QThreadPrivate::start(void*) (arg=0x562fe58ff560) at
thread/qthread_unix.cpp:331
#9  0x7f4c1ec3060a in start_thread (arg=0x7f4bfcc38700) at
pthread_create.c:334
#10 0x7f4c1f8f8a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f4bf5428700 (LWP 17030)):
#0  0x7f4c1f8ecfdd in poll () at 

[Breeze] [Bug 361249] GTK 3.20.x compatibility

[via KDE Bugzilla]

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

cross1...@gmail.com changed:

   What|Removed |Added

 CC||cross1...@gmail.com

--- Comment #3 from cross1...@gmail.com ---
confirm

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

[Breeze] [Bug 361249] GTK 3.20.x compatibility

[Jacobtey via KDE Bugzilla]

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

Jacobtey  changed:

   What|Removed |Added

 CC||jacob...@gmail.com

--- Comment #2 from Jacobtey  ---
confirm

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

[Breeze] [Bug 361249] GTK 3.20.x compatibility

[varlesh via KDE Bugzilla]

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

varlesh  changed:

   What|Removed |Added

 CC||varl...@gmail.com

--- Comment #1 from varlesh  ---
+1

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

[plasmashell] [Bug 361250] New: Plasma randomly freezes and eventually crashes and restarts

[Santiago de Leon via KDE Bugzilla]

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

Bug ID: 361250
   Summary: Plasma randomly freezes and eventually crashes and
restarts
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sdeleo...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- Unusual behavior I noticed:

This happens to me every day without any particular triggers that I can
identify. The taskbar freezes. I can't click or get mouseover feedback from:
the Pager widget; any of the task widgets at the bottom right of my task
manager; the Application Menu (launcher). Sometimes, actions on the folder
views in my desktop are also disabled.

When the plasma environment is frozen I can still use yakuake or krunner to
fire up programs. I can also switch between windows and Virtual Desktops with
my usual hotkeys.

The programs I have up most of the time are PyCharm, VirtualBox/Vagrant,
Firefox, Chrome, Thunderbird, Slack, the hangouts taskbar widget and Amarok.

This all started when I installed a fresh copy of Leap (I kept my home folder
but overwrote previous OS, which was OpenSUSE 13.2). This random bug is really
wrecking my experience with Leap.

The crash can be reproduced sometimes.

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

Thread 6 (Thread 0x7fc7ecd05700 (LWP 2049)):
#0  0x7fc7ff402bbd in poll () at /lib64/libc.so.6
#1  0x7fc7fbae3e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc7fbae3f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc7ffd2dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc7ffcd4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc802e08df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc7ffafb32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc7ff40afed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fc7db8f7700 (LWP 2051)):
#0  0x7fc7ff402bbd in poll () at /lib64/libc.so.6
#1  0x7fc7fbae3e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc7fbae3f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc7ffd2dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc7ffcd4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc802e08df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc7ffafb32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc7ff40afed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc7da092700 (LWP 2053)):
#0  0x7fc7fbae1254 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc7fbae344b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc7fbae3d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc7fbae3f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc7ffd2dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fc7ffcd4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fc802e08df8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fc7ffafb32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fc7ff40afed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fc7d3fff700 (LWP 2064)):
#0  0x7fc7fec1003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc8055d086b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fc8055d0899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc7ff40afed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fc7d0ebd700 (LWP 2110)):
#0  0x7fc7fec10e8b in pthread_getspecific () at /lib64/libpthread.so.0
#1  0x7fc7fbb09400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc7fbae2ecc in g_main_context_acquire () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc7fbae3d25 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fc7fbae3f7c in g_main_context_iteration () at

[kmymoney4] [Bug 361246] Kmymoney won't start

[via KDE Bugzilla]

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

--- Comment #2 from demianx...@yahoo.it ---
Il 31/03/2016 21:49, Jack via KDE Bugzilla ha scritto:
> https://bugs.kde.org/show_bug.cgi?id=361246
>
> --- Comment #1 from Jack  ---
> What version of KDE do you have installed?  I'm very curious about the 
> KBanking
> message - I don't use it myself, but in my case, I do see "KMyMoney kbanking
> plugin loaded, and I'm still using Qt4.  Can you do from a command line "ldd
> `which kmymoney` | grep -i qt" and post the results?
>
My KDE environnement  is :Frameworks 5.20.0, Plasma 5.5.5 
 and KDE 
Applications 15.12.2 ( Kaos Linux x86_64)

The Kmymoney version is

4.100.7-7 according to details found in Pacman

Sorry but the command line

"ldd
`which kmymoney` | grep -i qt"

didn't work




4.100.7-7

Versione



4.100.7-7

Versione



4.100.7-7

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

[Akonadi] [Bug 339378] Ask the password with connectivity problem

[Albert Astals Cid via KDE Bugzilla]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #4 from Albert Astals Cid  ---
That's really not "a new version", it's like 2 years old

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

[kmail2] [Bug 361196] crash when one add new mail account because KDE wallet is off

[RJ via KDE Bugzilla]

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

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

--- Comment #2 from RJ  ---
Created attachment 98181
  --> https://bugs.kde.org/attachment.cgi?id=98181=edit
Here it is.

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

[krunner] [Bug 345750] The currency conversion doesn't show proper values

[Robert Munteanu via KDE Bugzilla]

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

Robert Munteanu  changed:

   What|Removed |Added

 CC||robert.munte...@gmail.com

--- Comment #10 from Robert Munteanu  ---
Also happens with Plasma 5.5.5.2 on openSUSE Tumbleweed x86_64. I always get
the '0' result.

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

[kmymoney4] [Bug 361246] Kmymoney won't start

[Jack via KDE Bugzilla]

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

--- Comment #1 from Jack  ---
What version of KDE do you have installed?  I'm very curious about the KBanking
message - I don't use it myself, but in my case, I do see "KMyMoney kbanking
plugin loaded, and I'm still using Qt4.  Can you do from a command line "ldd
`which kmymoney` | grep -i qt" and post the results?

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

[Breeze] [Bug 361249] GTK 3.20.x compatibility

[via KDE Bugzilla]

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

fadem...@gmail.com changed:

   What|Removed |Added

 CC||fadem...@gmail.com

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

[Breeze] [Bug 361249] New: GTK 3.20.x compatibility

[via KDE Bugzilla]

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

Bug ID: 361249
   Summary: GTK 3.20.x compatibility
   Product: Breeze
   Version: 5.6.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: scionicspec...@gmail.com
  Reporter: fadem...@gmail.com

Breeze GTK3 theme need to be fixed for new major changes in release GTK3
3.20.x.

Reproducible: Always

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

[plasmashell] [Bug 360544] Copy or cut item from desktop containment does not work by keyboard shortcut

[via KDE Bugzilla]

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

--- Comment #5 from gy...@gmx.net ---
Now, with Plasma updated to 5.6.1 this issue is somehow solved on Netrunner
Rolling.
Copy / cut & paste by keyboard from the folderview containment works again.

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

[plasmashell] [Bug 359764] Panel doesn't allow resizing

[mozart reina via KDE Bugzilla]

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

mozart reina  changed:

   What|Removed |Added

 CC||urban.yoga.journeys@gmail.c
   ||om

--- Comment #9 from mozart reina  ---
I have the same issue, my WM is XMonad.

http://pastebin.com/RMVMhtyp

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

[plasmashell] [Bug 358001] Plasmoids does not use antialiasing when are rotated.

[João Vidal da Silva via KDE Bugzilla]

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

João Vidal da Silva  changed:

   What|Removed |Added

 CC||joao.vidal.si...@gmail.com

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

[kfile] [Bug 361248] New: wrong sorting in file open dialog - not consistent behaviour

[Janet via KDE Bugzilla]

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

Bug ID: 361248
   Summary: wrong sorting in file open dialog - not consistent
behaviour
   Product: kfile
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: bugzi...@kerridis.de

My language settings are German. In dolphin I have chosen to NOT let it sort my
files "natural". 
It sorts e.g. 18872, 2016-01, 201601375, 50359 - which is exactly what I
expect.
Gwenview and Konsole also sort files correctly 18872, 2016-01, 201601375,
50359... one digit after the other.

But the file open dialog sorts 2016-01, 18872, 50359, 201601375,... 
which means it pools the single digits into multi-digit numbers i.e. uses that
sorting that is called "natural" in Plasma. 

When I alter some file I append a digit - 201601 e.g. gets the variants 2016011
2016012 etc. and I need them to be shown together. But in the file dialog I
cannot find anything because the files which belong together are in absoulutely
different positions. 

In systemsettings I have set the sorting to C, everything else is German.

Can you please make the file dialog respect the user chosen sorting so that
everything is consistent?

Reproducible: Always



Expected Results:  
No "natural" sorting of files in file open dialog when sorting is C or dolphin
is configured to not use "natural" sorting - or provide some option to get rid
of "natural" sorting in file open dialog. Every file listers should be
consistent in sorting (and in my case preferably not "natural"). 

I have KF 5.18-5.19, applications show 15.08-15.12 and plasma elements are from
5.5.3 to 5.5.5... So it's hard for me to tell which version I am using...

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

[plasmashell] [Bug 361247] Plasma crash when screen turn on

[Radek via KDE Bugzilla]

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

--- Comment #2 from Radek  ---
Screen is Philips HDMI TV set.

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

[plasmashell] [Bug 361247] Plasma crash when screen turn on

[Radek via KDE Bugzilla]

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

Radek  changed:

   What|Removed |Added

 CC||rdebie...@yahoo.pl

--- Comment #1 from Radek  ---
(In reply to Radek from comment #0)
> Application: plasmashell (5.6.1)
> 
> Qt Version: 5.6.0
> Frameworks Version: 5.20.0
> Operating System: Linux 4.1.15-8-default x86_64
> Distribution: "openSUSE Leap 42.1 (x86_64)"
> 
> -- Information about the crash:
> - What I was doing when the application crashed:
> 1. Turn screen off.
> 2. Turn screen on.
> plasmashell crash always
> 
> The crash can be reproduced every time.
> 
> -- Backtrace:
> Application: Plazma (plasmashell), signal: Segmentation fault
> Using host libthread_db library "/lib64/libthread_db.so.1".
> [Current thread is 1 (Thread 0x7f62bd1cb800 (LWP 1973))]
> 
> Thread 11 (Thread 0x7f62a5f69700 (LWP 1975)):
> #0  0x7f62b66dabbd in poll () at /lib64/libc.so.6
> #1  0x7f62bb609422 in  () at /usr/lib64/libxcb.so.1
> #2  0x7f62bb60b00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
> #3  0x7f62a88ef979 in  () at /usr/lib64/libQt5XcbQpa.so.5
> #4  0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
> #5  0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
> #6  0x7f62b66e2fed in clone () at /lib64/libc.so.6
> 
> Thread 10 (Thread 0x7f629fdf5700 (LWP 1976)):
> #0  0x7f62b66ef622 in __libc_disable_asynccancel () at /lib64/libc.so.6
> #1  0x7f62b66d6c99 in read () at /lib64/libc.so.6
> #2  0x7f62ae880073 in  () at /usr/lib64/tls/libnvidia-tls.so.361.28
> #3  0x7f62b2e05b60 in  () at /usr/lib64/libglib-2.0.so.0
> #4  0x7f62b2dc4999 in g_main_context_check () at
> /usr/lib64/libglib-2.0.so.0
> #5  0x7f62b2dc4df8 in  () at /usr/lib64/libglib-2.0.so.0
> #6  0x7f62b2dc4f7c in g_main_context_iteration () at
> /usr/lib64/libglib-2.0.so.0
> #7  0x7f62b6fe83fb in
> QEventDispatcherGlib::processEvents(QFlags)
> () at /usr/lib64/libQt5Core.so.5
> #8  0x7f62b6f9604b in
> QEventLoop::exec(QFlags) () at
> /usr/lib64/libQt5Core.so.5
> #9  0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
> #10 0x7f62b7d53095 in  () at /usr/lib64/libQt5DBus.so.5
> #11 0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
> #12 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
> #13 0x7f62b66e2fed in clone () at /lib64/libc.so.6
> 
> Thread 9 (Thread 0x7f629e5b7700 (LWP 2000)):
> #0  0x7f62b66d6c8d in read () at /lib64/libc.so.6
> #1  0x7f62ae880073 in  () at /usr/lib64/tls/libnvidia-tls.so.361.28
> #2  0x7f62b2e05b60 in  () at /usr/lib64/libglib-2.0.so.0
> #3  0x7f62b2dc4999 in g_main_context_check () at
> /usr/lib64/libglib-2.0.so.0
> #4  0x7f62b2dc4df8 in  () at /usr/lib64/libglib-2.0.so.0
> #5  0x7f62b2dc4f7c in g_main_context_iteration () at
> /usr/lib64/libglib-2.0.so.0
> #6  0x7f62b6fe83fb in
> QEventDispatcherGlib::processEvents(QFlags)
> () at /usr/lib64/libQt5Core.so.5
> #7  0x7f62b6f9604b in
> QEventLoop::exec(QFlags) () at
> /usr/lib64/libQt5Core.so.5
> #8  0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
> #9  0x7f62ba0cd4d8 in  () at /usr/lib64/libQt5Qml.so.5
> #10 0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
> #11 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
> #12 0x7f62b66e2fed in clone () at /lib64/libc.so.6
> 
> Thread 8 (Thread 0x7f628dc29700 (LWP 2006)):
> #0  0x7f62b2dea400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
> #1  0x7f62b2dc4f6d in g_main_context_iteration () at
> /usr/lib64/libglib-2.0.so.0
> #2  0x7f62b6fe83fb in
> QEventDispatcherGlib::processEvents(QFlags)
> () at /usr/lib64/libQt5Core.so.5
> #3  0x7f62b6f9604b in
> QEventLoop::exec(QFlags) () at
> /usr/lib64/libQt5Core.so.5
> #4  0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
> #5  0x7f62ba0cd4d8 in  () at /usr/lib64/libQt5Qml.so.5
> #6  0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
> #7  0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
> #8  0x7f62b66e2fed in clone () at /lib64/libc.so.6
> 
> Thread 7 (Thread 0x7f6287fff700 (LWP 2008)):
> #0  0x7f62b66dabbd in poll () at /lib64/libc.so.6
> #1  0x7f62b2dc4e64 in  () at /usr/lib64/libglib-2.0.so.0
> #2  0x7f62b2dc4f7c in g_main_context_iteration () at
> /usr/lib64/libglib-2.0.so.0
> #3  0x7f62b6fe83fb in
> QEventDispatcherGlib::processEvents(QFlags)
> () at /usr/lib64/libQt5Core.so.5
> #4  0x7f62b6f9604b in
> QEventLoop::exec(QFlags) () at
> /usr/lib64/libQt5Core.so.5
> #5  0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
> #6  0x7f62ba0cd4d8 in  () at /usr/lib64/libQt5Qml.so.5
> #7  0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
> #8  0x7f62b5ee40a4 in start_thread () at 

[dolphin] [Bug 339866] Dolphin search displays "Invalid protocol" error.

[via KDE Bugzilla]

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

k...@xtronics.com changed:

   What|Removed |Added

 CC||k...@xtronics.com

--- Comment #22 from k...@xtronics.com ---
This bug should be updated for a fix - 

"Invalid Protocol" is not a useful error string - the error should do a little
testing and inform that either baloo is not installed or that indexing is not
complete.


Error messages should tell the user something that can help.

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

[plasmashell] [Bug 361247] New: Plasma crash when screen turn on

[Radek via KDE Bugzilla]

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

Bug ID: 361247
   Summary: Plasma crash when screen turn on
   Product: plasmashell
   Version: 5.6.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rdebie...@yahoo.pl
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.1)

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

-- Information about the crash:
- What I was doing when the application crashed:
1. Turn screen off.
2. Turn screen on.
plasmashell crash always

The crash can be reproduced every time.

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

Thread 11 (Thread 0x7f62a5f69700 (LWP 1975)):
#0  0x7f62b66dabbd in poll () at /lib64/libc.so.6
#1  0x7f62bb609422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f62bb60b00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f62a88ef979 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f62b66e2fed in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f629fdf5700 (LWP 1976)):
#0  0x7f62b66ef622 in __libc_disable_asynccancel () at /lib64/libc.so.6
#1  0x7f62b66d6c99 in read () at /lib64/libc.so.6
#2  0x7f62ae880073 in  () at /usr/lib64/tls/libnvidia-tls.so.361.28
#3  0x7f62b2e05b60 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f62b2dc4999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f62b2dc4df8 in  () at /usr/lib64/libglib-2.0.so.0
#6  0x7f62b2dc4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f62b6fe83fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#8  0x7f62b6f9604b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#9  0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#10 0x7f62b7d53095 in  () at /usr/lib64/libQt5DBus.so.5
#11 0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
#12 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
#13 0x7f62b66e2fed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f629e5b7700 (LWP 2000)):
#0  0x7f62b66d6c8d in read () at /lib64/libc.so.6
#1  0x7f62ae880073 in  () at /usr/lib64/tls/libnvidia-tls.so.361.28
#2  0x7f62b2e05b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f62b2dc4999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f62b2dc4df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f62b2dc4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f62b6fe83fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f62b6f9604b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f62ba0cd4d8 in  () at /usr/lib64/libQt5Qml.so.5
#10 0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f62b66e2fed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f628dc29700 (LWP 2006)):
#0  0x7f62b2dea400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
#1  0x7f62b2dc4f6d in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f62b6fe83fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f62b6f9604b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f62ba0cd4d8 in  () at /usr/lib64/libQt5Qml.so.5
#6  0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f62b66e2fed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f6287fff700 (LWP 2008)):
#0  0x7f62b66dabbd in poll () at /lib64/libc.so.6
#1  0x7f62b2dc4e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f62b2dc4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f62b6fe83fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f62b6f9604b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f62b6dd25da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f62ba0cd4d8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f62b6dd7079 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f62b5ee40a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f62b66e2fed in clone () 

[frameworks-kio] [Bug 360488] dolphin with >=kde-frameworks-5.20 crashes when copy+paste file in same directory

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[okular] [Bug 357526] Annotation can not be saved automatically for a specific PDF file.

[Chris via KDE Bugzilla]

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

Chris  changed:

   What|Removed |Added

 CC||inkbottle...@gmail.com

--- Comment #2 from Chris  ---
I've got the same problem with this file:
https://www.adobe.com/products/postscript/pdfs/PLRM.pdf

The problem might be related to that comment:
https://bugs.kde.org/show_bug.cgi?id=151614#c168

We still autosave annotations internally as usual, unless the PDF document
contains existing embedded annotations and it's not encrypted. In this case,
you'll be shown a warning ("Your annotation changes will not be saved
automatically. Use File -> Save As... or your changes will be lost once the
document is closed") and a "Do you want to save your annotation changes or
discard them?" prompt on document close.


If it were the case, I have no way to know if the file does have embedded
annotations, it wouldn't actually be a bug.

However this saving of annotations in external XML files is very, very
convenient because it provides both persistent annotations and unmodified
original file, and the fact that it's not possible for some files is a
hindrance.

The status could be changed to confirmed and the importance to wishlist (if
it's actually the non buggy behavior described above).

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

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

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/digi
   ||kam/d3a20a0cd682dddcc6f9ff8
   ||f5990028232d845b5
   Version Fixed In||5.0.0

--- Comment #22 from Maik Qualmann  ---
Git commit d3a20a0cd682dddcc6f9ff8f5990028232d845b5 by Maik Qualmann.
Committed on 31/03/2016 at 19:12.
Pushed by mqualmann into branch 'master'.

use alternative icons as a workaround for image-stack and image-stack-open
FIXED-IN: 5.0.0

M  +2-1NEWS
M  +2-2libs/widgets/itemview/itemviewimagedelegate.cpp
M  +1-1utilities/advancedrename/common/tooltipcreator.cpp
M  +1-1utilities/assistants/firstrun/openfilepage.cpp

http://commits.kde.org/digikam/d3a20a0cd682dddcc6f9ff8f5990028232d845b5

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

[krita] [Bug 358422] Deleted layer content reappears after select.

[Raghavendra kamath via KDE Bugzilla]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

--- Comment #13 from Raghavendra kamath  ---
yes I experience this issue in linux as well in latest 3.0
there is one more way to trigger that update problem

1. open krita
2. add a new paint layer
3. draw something on that new layer
4. then select a portion with rectangle selection

you'll notice all the white area has turned into checker board

a work around is to switch the visibility of bottom most layer on and off ,
then it doesn't happen again unless you restart krita.

A discussion on IRC - 
boud suggested that this may be a layer stack update issue or may be a
miscalculation of bottom layer -
" that sounds like it's caused by not correctly calculating the bottom
layer size, which is empty but has a default color
  that's something we've been breaking since 2004 "

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

[kmymoney4] [Bug 361246] New: Kmymoney won't start

[via KDE Bugzilla]

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

Bug ID: 361246
   Summary: Kmymoney won't start
   Product: kmymoney4
   Version: 4.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: demianx...@yahoo.it

The program won't start , dedicated cpu usage goes to 25% but nothing happens:
it's stuck until I kill the process.
I tried reinstalling it to no avail. 
My .kmy file is ok because I can open it with a Windows Kmymoney.
So I tried the console with -n here is the output:
ger@ger-pc ~]$ kmymoney -n
KMyMoney ofximport plugin loaded
onlineTask available "org.kmymoney.creditTransfer.sepa"
KMyMoney reconciliation report plugin loaded
Skip loading KBanking until ported to Qt5
KMyMoney iCalendar plugin loaded
KMyMoney csvexport plugin loaded
KMyMoney csvimport plugin loaded
KMyMoney printcheck plugin loaded
"syntax error, unexpected PLUS, expecting ']'"
"syntax error, unexpected PLUS, expecting ']'"
"syntax error, unexpected PLUS, expecting ']'"
"syntax error, unexpected PLUS, expecting ']'"

I am currently using Kaos distribution
ger@ger-pc ~]$ uname -a
Linux ger-pc 4.4.5-1 #1 SMP PREEMPT Thu Mar 10 02:22:47 UTC 2016 x86_64
GNU/Linux




Reproducible: Always

Steps to Reproduce:
1.Launch the program either by clicking the icon or the kmy file
2.
3.

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

[krita] [Bug 356058] Krita Animation Beta - Frame Ranges Cannot Be Selected With Graphic Tablet Stylus

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #6 from Boudewijn Rempt  ---
But also with 3.0?

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

[kdenlive] [Bug 361244] git master - In light of new brand logo, consider changing color of timeline position cursor to match new logo cursor?

[Jesse via KDE Bugzilla]

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

--- Comment #1 from Jesse  ---
After getting some feedback from the mailing list, I admit, the orange color
for the new logo does look a little faded on both color themes. But perhaps a
more vibrant tint would work?

Again, it's just a design opinion. I thought a few accent coloring to the more
unique functions, like the timeline cursor, would be a nice artistic gesture
:). (and I do mean few accents -- too much, as discussed in earlier bugs,
wouldn't work on a functional level. It'd be too much.)

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

[krita] [Bug 358422] Deleted layer content reappears after select.

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

Version|2.9.10  |3.0 Alpha
   Severity|normal  |grave

--- Comment #12 from Boudewijn Rempt  ---
Raghukamath and Sven Langkamp can also reproduce this issue, and I can
reproduce it another way: 

20:56:11 < raghukamath> boud you can check it by just creating a layer then
draw something and then draw a rectangle selection

this is probably a layer stack update issue.

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

[krita] [Bug 358422] Deleted layer content reappears after select.

[Sven Langkamp via KDE Bugzilla]

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

Sven Langkamp  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||sven.langk...@gmail.com
 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #11 from Sven Langkamp  ---
I can confirm with 3.0 master

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

[kate] [Bug 361217] Kate crashes when no files are open and "Open recent" function is used

[Lukasz via KDE Bugzilla]

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

Lukasz  changed:

   What|Removed |Added

 CC||dolo...@outlook.com

--- Comment #1 from Lukasz  ---
Cannot reproduce with version 15.12.3

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

[krita] [Bug 356669] [WACOM INTUOS] random lines appear as you draw

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|Brush engine|tablet support
 CC||b...@valdyas.org
Summary|random lines appear as you  |[WACOM INTUOS] random lines
   |draw|appear as you draw

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

[krita] [Bug 356774] unwanted dots on strokes (possibly just with stabilizer)

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Component|Tools   |tablet support
 CC||b...@valdyas.org
   Platform|Windows CE  |MS Windows
 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #4 from Boudewijn Rempt  ---
Hm,

I've never seen such blobs in 2.9, and only sometimes in 3.0. Which brand of
tablet are you using?

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

[krita] [Bug 358422] Deleted layer content reappears after select.

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #10 from Boudewijn Rempt  ---
Hi Piotr,

Thanks for you effort. I can see it happen in your video. If this happens every
time for you, could you download the 3.0 pre-alpha and see if that still shows
the issue? Could you also try to disable opengl in settings/configure
krita/display and see if that makes a difference?

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

[krita] [Bug 358543] Krita can't bind shortcuts to mouse clicks generated with xdotool or xte.

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

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

Thanks for your report. I'm sorry, but I haven't had a chance to setup a way to
test this issue. It could be in our code, it could be in Qt... It might even
just work out of the box with the development version of Krita 3.0, because
that uses a different way to talk to the x server.

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

[plasmashell] [Bug 361245] New: Problemas ao alternar entre redes wi-fi

[Antonio via KDE Bugzilla]

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

Bug ID: 361245
   Summary: Problemas ao alternar entre redes wi-fi
   Product: plasmashell
   Version: 5.6.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: antonio.jr.sso...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.1)

Qt Version: 5.6.0
Frameworks Version: 5.20.0
Operating System: Linux 4.4.5-1-ARCH x86_64
Distribution: "Arch Linux"

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

- Unusual behavior I noticed:

- Custom settings of the application:

-Desktop Environment crashed after network wi-fi changes, and this problem
always happend, but i don't know what to do.

The crash can be reproduced every time.

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

Thread 10 (Thread 0x7fdf0f9b0700 (LWP 1092)):
#0  0x7fdf1ffe4c3d in poll () from /usr/lib/libc.so.6
#1  0x7fdf24fe2ae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fdf24fe4757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fdf112d2a99 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7fdf0dd84700 (LWP 1093)):
#0  0x7fdf1c466003 in ?? () from /usr/lib/libglib-2.0.so.0
#1  0x7fdf1c4684ab in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7fdf1c468eab in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fdf1c46908c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fdf208fccab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fdf208a56fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fdf206cefe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fdf2168fa55 in ?? () from /usr/lib/libQt5DBus.so.5
#8  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7fdf07fff700 (LWP 1109)):
#0  0x7fdf1ffe4c3d in poll () from /usr/lib/libc.so.6
#1  0x7fdf1c468f7c in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fdf1c46908c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fdf208fccab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fdf208a56fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fdf206cefe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fdf23a71915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7fdef9a1e700 (LWP 1117)):
#0  0x7fdf1ffe4c3d in poll () from /usr/lib/libc.so.6
#1  0x7fdf1c468f7c in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fdf1c46908c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fdf208fccab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fdf208a56fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fdf206cefe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fdf23a71915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7fdef3dc7700 (LWP 1124)):
#0  0x7fdf1c467f76 in g_main_context_acquire () from
/usr/lib/libglib-2.0.so.0
#1  0x7fdf1c468e35 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fdf1c46908c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fdf208fccab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fdf208a56fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fdf206cefe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fdf23a71915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7fdef2581700 (LWP 1127)):
#0  0x7fdf1f7ed03f in pthread_cond_wait@@GLIBC_2.3.2 () from

[krita] [Bug 358611] Assistant tool force lines to position not that one mouse is pointing

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #5 from Boudewijn Rempt  ---
Should we make magnetism a checkbox, instead of a slider?

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

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

[Systemadministrator via KDE Bugzilla]

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

--- Comment #34 from Systemadministrator  ---
I confirm, it works now.
Thanks a lot! :-)

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

[krita] [Bug 358718] When at min width, tools docker UI overlaps timeline docker

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Boudewijn Rempt  ---
Yes, it's kind of related -- and we cannot do much about it, it's a problem in
Qt, I'm afraid.

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

[krita] [Bug 359859] Selection tool imprecise when disabling anti-aliasing

[Boudewijn Rempt via KDE Bugzilla]

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

--- Comment #2 from Boudewijn Rempt  ---
Created attachment 98180
  --> https://bugs.kde.org/attachment.cgi?id=98180=edit
sel2.png

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

[kdenlive] [Bug 361244] git master - In light of new brand logo, consider changing color of timeline position cursor to match new logo cursor?

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||snd.no...@gmail.com

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

[kdenlive] [Bug 361244] git master - In light of new brand logo, consider changing color of timeline position cursor to match new logo cursor?

[Jesse via KDE Bugzilla]

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

Jesse  changed:

   What|Removed |Added

 CC||jesse.dub...@gmail.com

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

[kdenlive] [Bug 361244] New: git master - In light of new brand logo, consider changing color of timeline position cursor to match new logo cursor?

[Jesse via KDE Bugzilla]

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

Bug ID: 361244
   Summary: git master - In light of new brand logo, consider
changing color of timeline position cursor to match
new logo cursor?
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: jesse.dub...@gmail.com

With the new logo that Farid made, I thought it would be a nice benefit to
associate the new logo with the program. I made some mock-ups of the program
with the cursor in the timeline changed to the color to match the logo. It
seems to look pretty well, IMHO:

https://www.dropbox.com/s/a0xu5zvf8kv8k2f/kdenlive%20new%20cursor%20color%20-%20breeze%20dark.jpg?dl=0

https://www.dropbox.com/s/kfqhqtof48rchos/kdenlive%20new%20cursor%20color%20-%20breeze%20light.jpg?dl=0



Reproducible: Always




Suggested using Kdenlive 16.07.70 git master build from the kdenlive-master ppa
for Ubuntu; Ubuntu 16.04 beta x64.

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

[krita] [Bug 360663] The progress bar shown on the layer doesn't get cleared after operation is completed , instead it gets stuck at 0% thus hiding the layer icons

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[krita] [Bug 360671] [WACOM CINTIQ] crash when touching the cintiq with the stylus

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #2 from Boudewijn Rempt  ---
Fixed in the meantime by Fazek.

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

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

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/bae990ecaeacb9a67ea8a68b4
   ||d4bcc78c1e597ef
 Status|UNCONFIRMED |RESOLVED

--- Comment #9 from Boudewijn Rempt  ---
Git commit bae990ecaeacb9a67ea8a68b4d4bcc78c1e597ef by Boudewijn Rempt.
Committed on 31/03/2016 at 18:21.
Pushed by rempt into branch 'master'.

I'm still not sure how this sequence of events can make the option
docker disappear, but at least it can be made to reappear now.

M  +3-0libs/ui/KisMainWindow.cpp
M  +0-1libs/widgets/KoToolDocker.cpp

http://commits.kde.org/krita/bae990ecaeacb9a67ea8a68b4d4bcc78c1e597ef

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

[frameworks-bluez-qt] [Bug 357720] Bluetooth not enabled after suspend but shown as powered

[David Rosca via KDE Bugzilla]

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

--- Comment #9 from David Rosca  ---
disabled - blocked by rfkill
enabled - !disabled = not blocked by rfkill
offline - enabled and there is a bluetooth adapter (one or more) and this
bluetooth adapter is powered off

I'm sorry I didn't fix this issue yet, I was hoping that it will be fixed with
Qt 5.6 (QtDBus moved to own thread) because the issue occurs only in
plasmashell and not eg. in bluedevil-wizard. In other words, I think the issue
only occurs when there is significant dbus traffic. But it wasn't fixed, so
I'll need to add workaround.
I hope I'll make the fix for 5.21.

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

[kdenlive] [Bug 360613] git master - when removing a title clip from the Project Bin - and it's also in the timeline - Kdenlive doesn't remove the affine transition

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #2 from Jean-Baptiste Mardelle  ---
Git commit ce04b7bf84d84561acc9d1a6f929792784232d28 by Jean-Baptiste Mardelle.
Committed on 31/03/2016 at 18:18.
Pushed by mardelle into branch 'Applications/16.04'.

When deleting a title clip, also remove automatic transition

M  +14   -2src/timeline/customtrackview.cpp

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

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

[plasmashell] [Bug 361243] New: crash when changing screen resolution

[ekle via KDE Bugzilla]

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

Bug ID: 361243
   Summary: crash when changing screen resolution
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: k...@eklenet.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-towo.1-siduction-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
changing screen resolution and disabled external monitor

The crash can be reproduced sometimes.

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

Thread 8 (Thread 0x7fb2d09d4700 (LWP 3575)):
#0  0x7fb2e04b3e4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb2e4566382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fb2e4567ff7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fb2d1ccb789 in QXcbEventReader::run (this=0x2057d70) at
qxcbconnection.cpp:1230
#4  0x7fb2e0b987fe in QThreadPrivate::start (arg=0x2057d70) at
thread/qthread_unix.cpp:331
#5  0x7fb2dfcbc454 in start_thread (arg=0x7fb2d09d4700) at
pthread_create.c:334
#6  0x7fb2e04bcedd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fb2c9fed700 (LWP 3603)):
#0  0x7fb2e04b3e4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb2dd26132c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb2dd26143c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb2e0dcfa5b in QEventDispatcherGlib::processEvents
(this=0x7fb2c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fb2e0d76d6a in QEventLoop::exec (this=this@entry=0x7fb2c9fecc60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fb2e0b93854 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fb2e3426105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fb2e0b987fe in QThreadPrivate::start (arg=0x212d7f0) at
thread/qthread_unix.cpp:331
#8  0x7fb2dfcbc454 in start_thread (arg=0x7fb2c9fed700) at
pthread_create.c:334
#9  0x7fb2e04bcedd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fb2c27c3700 (LWP 3632)):
#0  0x7fb2dd2a5a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb2dd260d59 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb2dd2612d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb2dd26143c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb2e0dcfa5b in QEventDispatcherGlib::processEvents
(this=0x7fb2bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fb2e0d76d6a in QEventLoop::exec (this=this@entry=0x7fb2c27c2c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fb2e0b93854 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fb2e3426105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fb2e0b987fe in QThreadPrivate::start (arg=0x232e110) at
thread/qthread_unix.cpp:331
#9  0x7fb2dfcbc454 in start_thread (arg=0x7fb2c27c3700) at
pthread_create.c:334
#10 0x7fb2e04bcedd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fb2bb674700 (LWP 4981)):
#0  0x7fb2e04b3e4d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fb2dd26132c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb2dd26143c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb2e0dcfa5b in QEventDispatcherGlib::processEvents
(this=0x7fb2b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fb2e0d76d6a in QEventLoop::exec (this=this@entry=0x7fb2bb673c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fb2e0b93854 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fb2e3426105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fb2e0b987fe in QThreadPrivate::start (arg=0x231b4b0) at
thread/qthread_unix.cpp:331
#8  0x7fb2dfcbc454 in start_thread (arg=0x7fb2bb674700) at
pthread_create.c:334
#9  0x7fb2e04bcedd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fb2b9d75700 (LWP 4982)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb2e57d31c4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  

[frameworks-bluez-qt] [Bug 357720] Bluetooth not enabled after suspend but shown as powered

[Robin Green via KDE Bugzilla]

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

--- Comment #8 from Robin Green  ---
I don't understand why there needs to be 3 bluetooth states: enabled, disabled,
and "offline" (the latter implying the applet is disabled but the control panel
is not). Is it something in the Bluetooth spec? If not, what purpose does it
serve, other than to annoy people?

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

[kdenlive] [Bug 357026] very often randomly crashing - imposibility to working

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #6 from Jean-Baptiste Mardelle  ---
The titler crash was fixed in MLT's current git version, and will be part of
MLT 0.6.2 that is not released yet. We recommend that you use our official
Ubuntu PPA's:

https://launchpad.net/~kdenlive/+archive/ubuntu/kdenlive-stable

This provides latest stable version of Kdenlive with recent git version of MLT
/ Freior and should fix the titler crash.

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

[krita] [Bug 361130] Layer Style: Stroke effect with big size doesn't follow correctly layer content shape

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||b...@valdyas.org
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Boudewijn Rempt  ---
Hi Aurélien,

Thanks for your report and for the test file. Together I can confirm the issue.

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

[krita] [Bug 361130] Layer Style: Stroke effect with big size doesn't follow correctly layer content shape

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

   Platform|Windows CE  |MS Windows

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

[kwin] [Bug 361241] Double click to maximize does not work in some situations

[Bernd Steinhauser via KDE Bugzilla]

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

--- Comment #1 from Bernd Steinhauser  ---
Forgot to mention:
I ran kwin at commit id ed1d32288b50647469fb0e000f21b849e286ca36 to test this.
When using kwin at 95cbd7c1b3cdbe81fdee1682049bd08ab7fe99fb (parent), I cannot
reproduce it at all (or at least the above does not work when trying about 10
times).

Also present in 5.6.1.

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

[korganizer] [Bug 361242] New: korganizer fires remainder event every minute when time switch to DST

[Wulf via KDE Bugzilla]

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

Bug ID: 361242
   Summary: korganizer fires remainder event every minute when
time switch to DST
   Product: korganizer
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: reminder daemon (korgac)
  Assignee: korganizer-de...@kde.org
  Reporter: wulf.richa...@gmx.de
CC: b.buschin...@googlemail.com, cf...@kde.org,
env...@rolamasao.org, j...@holodeck1.com,
johan...@studt.de, myr...@kde.org, pro...@gmx.net,
tcl-...@fm123.fastmail.fm, tho...@tanghus.net,
tsujan2...@gmail.com, wulf.richa...@gmx.de

+++ This bug was initially created as a clone of Bug #250729 +++

Version:   4.4.5 (using KDE 4.4.5) 
OS:Linux

I've setup a pending task, with an advanced remainder: fire 1 hour after end,
repeat once each 60 minutes.
But korganizer daemon reminds me every minute.

This has been reported (with a screenshot) in Ubuntu launchpad:
https://bugs.launchpad.net/bugs/488251

Reproducible: Always

Steps to Reproduce:
Create a pending task.
Configure it for a remainder with a period larger than 1 minute (for example,
once each 60 minutes).
Wait for the remainder start time to come.

Actual Results:  
korgac remainds every minute

Expected Results:  
korgac remainds as desired (like once every 60 minutes)

korgac is unusable if it fires every minute. I must deactivate it.

--
Lst Comments:
 Wulf 2016-03-26 02:37:11 CET
the bug is back again; started today (2016-03-26) at 02:00 UTC+1 (MET) korgac
shows me reminders every minute for all birthdays for the next 12 months in
future korgnizer version 5.1.3, Frameworks 5.19.0, Qt 5.5.1

[reply] [−] Comment 16 Tsu Jan 2016-03-26 12:37:26 CET
@Wulf I think this bug has never been fixed because it occurs once a year,
being related to daylight saving time.

[reply] [−] Comment 17 Wulf 2016-03-26 14:30:51 CET
@Tsu Jan I think you are right, because reminders stopped at 3 am. But then
there is a bug in the calculation of the beginning of DST for Europe. It's the
last Sunday in march 1 am UTC, not Saturday!

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

[krita] [Bug 290960] printing: Does not scale as size as in preview

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/71f6ce6efeab7254cda018c0d
   ||9621d55ce246f23

--- Comment #5 from Boudewijn Rempt  ---
Git commit 71f6ce6efeab7254cda018c0d9621d55ce246f23 by Boudewijn Rempt.
Committed on 31/03/2016 at 17:35.
Pushed by rempt into branch 'master'.

Hide the print and print preview action

We do not properly support printing at the moment, at all. There is
no color management, no scaling, no pagination, nothing. We even
print by converting to a QImage first.

M  +2-2krita/krita.xmlgui
M  +8-8libs/ui/KisMainWindow.cpp

http://commits.kde.org/krita/71f6ce6efeab7254cda018c0d9621d55ce246f23

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

[krita] [Bug 355435] Menu > Configure Shortcuts > Print button seems to do nothing

[Boudewijn Rempt via KDE Bugzilla]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/krit
   ||a/7f656ca968afa4986dfd4ce66
   ||19ba948296d0314
 Status|CONFIRMED   |RESOLVED

--- Comment #6 from Boudewijn Rempt  ---
Git commit 7f656ca968afa4986dfd4ce6619ba948296d0314 by Boudewijn Rempt.
Committed on 31/03/2016 at 17:50.
Pushed by rempt into branch 'master'.

Apparently, it was disabled for Windows CE, which also disables it
on all of Windows.

M  +0-3libs/widgetutils/xmlgui/KisShortcutsEditor_p.cpp

http://commits.kde.org/krita/7f656ca968afa4986dfd4ce6619ba948296d0314

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

[kwin] [Bug 361241] New: Double click to maximize does not work in some situations

[Bernd Steinhauser via KDE Bugzilla]

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

Bug ID: 361241
   Summary: Double click to maximize does not work in some
situations
   Product: kwin
   Version: 5.6.1
  Platform: Exherbo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: li...@bernd-steinhauser.de

As mentioned in bug 360137, I sometimes see the issue of kwin not responding to
a double click on the window title decoration, which in my setup should
maximize the window.
I finally was able to find a way to reliably reproduce (see below) the issue
and track it down.
I was already pointed at
https://quickgit.kde.org/?p=kwin.git=commit=ed1d32288b50647469fb0e000f21b849e286ca36
and indeed that commit causes the issue to appear.
For reference, see bug 357450, which was fixed by the referenced commit.
bug 345473 seems unrelated as I'm only seeing the problem under certain
circumstance, most of the time it works.

Reproducible: Always

Steps to Reproduce:
1. Open a window, ensure it is not maximized.
2. Double click on the title, the window should maximize as expected
3. Double click to unmaximize, should work as expected
4. Click on the desktop containment / desktop background
5. Click on the window title once(!), don't move the cursor
6. Wait for at least 0.2 s
7. Double click on the window title, no response
>From here on, it doesn't seem to work reliably:
8. Wait for a second
9. Double click again, no response
etc.



• Only double click seems to be affected. Right click/wheel etc. work as
expected.
• The action that is linked to double click does not matter, shade etc. behave
the same.
• I chose "Happens every time", but I'm not sure if it is 100%, at least with
the procedure above I can reproduce it at least 9 times out of 10.
• The "Don't move the cursor" part is not strictly necessary, but it seems to
me like it increases the chance for this to happen. But I've seen it with
moving the cursor as well and I even saw this with  clicking inside a textbox
while the app is active like this one right here and then trying again, thus I
think the trigger has something to do with the app changing focus.
• If you don't double click but instead triple click, the window will maximize.

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