[krita] [Bug 374503] "Compress .kra files more" has no effect until Krita is restarted

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

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

--- Comment #1 from Boudewijn Rempt  ---
I'm sorry, but it does work directly, I just verified it in the code & by
saving a kra file twice.

-rw-r--r-- 1 boud users 472747 Jan  4 08:56 /home/boud/bla2.kra
-rw-r--r-- 1 boud users 474973 Jan  4 08:56 /home/boud/bla.kra

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

[krita] [Bug 374524] Crash while painting

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kri
   ||ta/e6f629272b28becf6667ed00
   ||e84e15ce68381626

--- Comment #1 from Boudewijn Rempt  ---
Git commit e6f629272b28becf6667ed00e84e15ce68381626 by Boudewijn Rempt.
Committed on 04/01/2017 at 07:53.
Pushed by rempt into branch 'master'.

This is the only thing that could account for that stacktrace, but
since the crash is not reproducible, I just have to guess...

M  +5-4libs/kundo2/kundo2stack.cpp

https://commits.kde.org/krita/e6f629272b28becf6667ed00e84e15ce68381626

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

[krita] [Bug 374524] Crash while painting

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
   |ta/e6f629272b28becf6667ed00 |ta/6d69b254e7bdaf5f26d61931
   |e84e15ce68381626|0b6a380fb4fbd4d5

--- Comment #2 from Boudewijn Rempt  ---
Git commit 6d69b254e7bdaf5f26d619310b6a380fb4fbd4d5 by Boudewijn Rempt.
Committed on 04/01/2017 at 07:54.
Pushed by rempt into branch 'krita/3.1'.

This is the only thing that could account for that stacktrace, but
since the crash is not reproducible, I just have to guess...

M  +5-4libs/kundo2/kundo2stack.cpp

https://commits.kde.org/krita/6d69b254e7bdaf5f26d619310b6a380fb4fbd4d5

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

[kdevelop] [Bug 374525] KDevelop segfault when analyzing source code

[Kevin Funk]

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

--- Comment #2 from Kevin Funk  ---
Full backtrace next time please. And please upload diffs to Phabricator so we
can review them easily.

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

[karbon] [Bug 372293] Annotation not saved

[Anthony Fieroni]

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

--- Comment #3 from Anthony Fieroni  ---
Can you reproduce it with 3.0 ?

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[Boudewijn Rempt]

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

--- Comment #47 from Boudewijn Rempt  ---
> Hi Charles, I'm not a dev, just a fellow user with the same problem, also 
> running an AMD CPU looking to compare notes. I really need to find a C++ and 
> QT for dummies guide but I got the tablet to learn how to draw, not how to 
> code :P

That's how I got started working on Krita... In 2003, with a little wacom
Graphire tablet.

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

[kmail2] [Bug 372189] Dysfunctional areas with 1.5 scaling

[Bo Simonsen]

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

Bo Simonsen  changed:

   What|Removed |Added

 CC||b...@geekworld.dk

--- Comment #10 from Bo Simonsen  ---
It seems like the upstream bug is stalled due to lack of example. I know QT
programming but not qtWebEngine, anybody with the knowledge that can reproduce
an example for them?

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

[klipper] [Bug 374517] Enormous clipboard data causes crash

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin  ---
Unfortunately we no longer maintain this version of Klipper. Too many 
things have changed and this makes it difficult to investigate the bug. 
It is also quite likely that the bug has already been resolved. Please 
consider upgrading to our latest version.

@STATUS RESOLVED
@RESOLUTION UNMAINTAINED

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

[kdevelop] [Bug 374525] KDevelop segfault when analyzing source code

[Leslie Zhai]

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

--- Comment #1 from Leslie Zhai  ---
kdev-clang-tidy also segfault when analyzing source code.

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

[klipper] [Bug 374517] Enormous clipboard data causes crash

[James Ring]

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

--- Comment #2 from James Ring  ---
Ubuntu 14.04 LTS with klipper package version 4:4.11.11-0ubuntu0.2. I haven't
tried it on a later version.

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

[kdevelop] [Bug 374525] New: KDevelop segfault when analyzing source code

[Leslie Zhai]

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

Bug ID: 374525
   Summary: KDevelop segfault when analyzing source code
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (old)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: xiangzha...@gmail.com
  Target Milestone: ---

Hi KDevelop developers,


Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault.
0x7fffbbde43de in cppcheck::Parameters::Parameters (this=0x7fffa870,
project=0x192f730)
at /data/project/kde/kdevelop/analyzers/cppcheck/parameters.cpp:110
110 m_projectBuildPath   =
m_project->buildSystemManager()->buildDirectory(m_project->projectItem());


so I simply added if (m_project->buildSystemManager()) check before
m_project->buildSystemManager()->buildDirectory(...)

Regards,
Leslie Zhai

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

[plasmashell] [Bug 373920] Pager window rectangle stays in wrong workspace.

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[plasmashell] [Bug 374202] Pager does not show up and number of virtual desktops is out of sync

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

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

--- Comment #1 from Eike Hein  ---
See https://community.kde.org/Plasma/5.8_Errata#Wayland for known Wayland
missing features.

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

[plasmashell] [Bug 374310] Cannot build plasma-desktop without AppStreamQt installed

[Duncan]

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

--- Comment #4 from Duncan <1i5t5.dun...@cox.net> ---
Update:  The devs are discussing a patch that makes appstream optional in d3923
on phabricator:

https://phabricator.kde.org/D3923

Gentoo/kde did get an appstream-git ebuild in their overlay, and I hadn't tried
patching the appstream dep out yet so I thought I'd try it, but appstream
failed to build for me at head and at the 0.10.5 and 0.10.4 tags.  Something
about no *.gmo files in the po dir.  So after updating the gentoo bug (which
you can look at for the details, link's above) and now this one, I'm going to
try the d3923 patch to make appstream optional, next.

The good news is that the appstream dep /does/ appear to be reasonably lite, as
these things go.  No huge deps chain.  While having it required is certainly
irritating, assuming the broken building can be fixed, it looks like the dep is
relatively lite, so a decision to keep it required isn't as severe as it might
be.

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

[klipper] [Bug 374517] Enormous clipboard data causes crash

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin  ---
Which version are you using?

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

[plasmashell] [Bug 374162] Add an option to sort programs chronologically in task bar, when grouping

[Eike Hein]

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

--- Comment #8 from Eike Hein  ---
The actual sorting happens in the library backend:

https://github.com/KDE/plasma-workspace/tree/master/libtaskmanager

TaskGroupingProxyModel (grouping) and TasksModel (sorting).

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

[plasmashell] [Bug 374443] Kicker popup doesn't appear when other windows are on screen

[Eike Hein]

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

--- Comment #12 from Eike Hein  ---
Here's what I want you to do first: Add a new user account to your system, log
into the user account, do no changes except switch to Kicker, then see if the
problem happens with the new user, too.

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

[plasmashell] [Bug 374481] Clicking on icons with multiple windows from a different activity does nothing

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 CC||mgraess...@kde.org
 Ever confirmed|0   |1
 Status|NEEDSINFO   |REOPENED
 Resolution|WAITINGFORINFO  |---

--- Comment #3 from Eike Hein  ---
You might be on to something here. The real thing works a bit differently - the
Present Windows effect has no idea about applications, the Task Manager just
gives it a list of windows to show. But KWin probably refuses to show windows
not of the current activity. I think this is wrong. I'll CC Martin Graesslin.

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

[krita] [Bug 374524] New: Crash while painting

[Rafal]

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

Bug ID: 374524
   Summary: Crash while painting
   Product: krita
   Version: 3.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: rafal.trash...@gmail.com
  Target Milestone: ---

Created attachment 103185
  --> https://bugs.kde.org/attachment.cgi?id=103185=edit
Crash while painting

Today Krita crashed for the first time when i was just painting using Freehand
Brush Tool. I attach crash log with it.

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

[kmymoney4] [Bug 359874] Most imported transactions not automatically matched with payee matching off

[bugzilla_noreply]

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

--- Comment #2 from lwilson1...@cox.net ---
My .kmy file contains several years of my financial history.  I'm not going to
upload it to a public Bugzilla.  I'd send you an "anonymous file" version of
it, but since that would change all of the payee names, it would render it
essentially useless for diagnosing this issue.  I realize that makes it much
more difficult for you to help me, but I'm not comfortable making that much
personal data public.

If it helps to quantify the term "most," I just imported 25 transactions today,
and 2 of them matched.  Only 6 new payees were created.  I then had to manually
match 19 transactions which would have been automatically matched before this
bug was introduced.  This is about par for the course.  Each pair of
transactions I manually matched were within 30 days of each other.  I don't
have time right now to check every one, but at least two or three of the payees
involved had payee matching disabled.

How hard would it be to add a global setting to turn off payee matching?  CSV
imports worked great until that was introduced.

As of this writing, I am still running KMyMoney 4.7.2.

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

[kdevelop] [Bug 374523] New: kdevelop-pg-qt yymore_used_but_not_detected undefined

[Leslie Zhai]

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

Bug ID: 374523
   Summary: kdevelop-pg-qt yymore_used_but_not_detected undefined
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: xiangzha...@gmail.com
  Target Milestone: ---

Hi KDevelop developers,

flex-2.6.3 yymore_used_but_not_detected undefined issue
http://www.efm.leeds.ac.uk/~as/Old/gnu/info_html/flex_21.html

So I simply added --yymore option for kdev-pg/CMakeLists.txt


diff --git a/kdev-pg/CMakeLists.txt b/kdev-pg/CMakeLists.txt
index 5490835..19dc3a4 100644
--- a/kdev-pg/CMakeLists.txt
+++ b/kdev-pg/CMakeLists.txt
@@ -76,7 +76,7 @@ IF(FLEX_EXECUTABLE)
 DEPENDS "${CMAKE_CURRENT_SOURCE_DIR}/kdev-pg-lexer.ll"
  ${OPTIONAL_PARSER_HEADER_DEPENDENCY}
 COMMAND ${FLEX_EXECUTABLE}
-ARGS--nounistd -o"${CMAKE_CURRENT_BINARY_DIR}/kdev-pg-lexer.cc"
+ARGS--yymore --nounistd
-o"${CMAKE_CURRENT_BINARY_DIR}/kdev-pg-lexer.cc"
 "${CMAKE_CURRENT_SOURCE_DIR}/kdev-pg-lexer.ll"
 )



Regards,
Leslie Zhai

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

[kphotoalbum] [Bug 195278] forward/backward buttons should have a list of items like a browser

[bugzilla_noreply]

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

bluescreenaven...@gmail.com changed:

   What|Removed |Added

 CC||bluescreenaven...@gmail.com

--- Comment #4 from bluescreenaven...@gmail.com ---
I also would like to see this feature added

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

[calligracommon] [Bug 346921] Calligra Frameworks fails to compile against qt5.5

[bugzilla_noreply]

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

bluescreenaven...@gmail.com changed:

   What|Removed |Added

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

--- Comment #4 from bluescreenaven...@gmail.com ---
Calligra can now even compile with Qt 5.8

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

[khotkeys] [Bug 346340] khotkeys causes a crash in kded5 on Wayland

[bugzilla_noreply]

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

--- Comment #3 from bluescreenaven...@gmail.com ---
I don't think KDED5 crashed in a while, I think
https://cgit.kde.org/khotkeys.git/commit/?id=b84848594f765e171cc4d8fdc7c6094d864e8780
might have fixed it

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

[kdelibs] [Bug 245579] Dolphin Advanced ACL editor requires a refresh in order for changes to appear

[bugzilla_noreply]

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

bluescreenaven...@gmail.com changed:

   What|Removed |Added

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

--- Comment #4 from bluescreenaven...@gmail.com ---
For me, the ACL editor is greyed out now where there are no permissions

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

[konqueror] [Bug 346346] konqueror crashes on Wayland with an empty clipboard

[bugzilla_noreply]

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

bluescreenaven...@gmail.com changed:

   What|Removed |Added

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

--- Comment #2 from bluescreenaven...@gmail.com ---
I think this is resolved, I can't replicate it...

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

[kdelibs] [Bug 245579] Dolphin Advanced ACL editor requires a refresh in order for changes to appear

[bugzilla_noreply]

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

--- Comment #3 from bluescreenaven...@gmail.com ---
I think this is resolved?

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

[kate] [Bug 374522] New: Kate crashes after autocompliting D-language (lumen plugin)

[bugzilla_noreply]

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

Bug ID: 374522
   Summary: Kate crashes after autocompliting D-language (lumen
plugin)
   Product: kate
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: pinkier...@gmail.com
  Target Milestone: ---

Application: kate (16.08.2)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.36-8-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
In ~/.config/dcd/dcd.conf was:
/usr/include/dmd/druntime/import
/usr/include/dmd/phobos
~/.dub/packages/requests-0.4.0/requests/source

And after typing:
import requests;
...
MultipartForm form;
form.add⏎

Autocomplete works fine, but after choosing method and pressing "return" - kate
crushed.

The crash can be reproduced every time.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f56b5ab3880 (LWP 22582))]

Thread 3 (Thread 0x7f569b1f0700 (LWP 22585)):
#0  0x7f56b00ae51d in read () at /lib64/libc.so.6
#1  0x7f56ac5a5670 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f56ac564e49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f56ac5652a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f56ac56542c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f56b0cc332b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f56b0c70fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f56b0aabf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f56b10d81d5 in  () at /usr/lib64/libQt5DBus.so.5
#9  0x7f56b0ab09e9 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f56aca89734 in start_thread () at /lib64/libpthread.so.0
#11 0x7f56b00bad3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f56a05a0700 (LWP 22584)):
#0  0x7f56b00b249d in poll () at /lib64/libc.so.6
#1  0x7f56aceb43e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f56aceb5fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f56a316a839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f56b0ab09e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f56aca89734 in start_thread () at /lib64/libpthread.so.0
#6  0x7f56b00bad3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f56b5ab3880 (LWP 22582)):
[KCrash Handler]
#6  0x7f56b0caf5a9 in QVariant::QVariant(QString const&) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f569541e144 in  () at
/usr/lib64/qt5/plugins/ktexteditor/ktexteditor_lumen.so
#8  0x7f56b5331bcb in KateCompletionModel::Item::Item(bool,
KateCompletionModel*, HierarchicalModelHandler const&,
QPair) () at
/usr/lib64/libKF5TextEditor.so.5
#9  0x7f56b53334a4 in
KateCompletionModel::createItem(HierarchicalModelHandler const&, QModelIndex
const&, bool) () at /usr/lib64/libKF5TextEditor.so.5
#10 0x7f56b53341d8 in
KateCompletionModel::createItems(HierarchicalModelHandler const&, QModelIndex
const&, bool) () at /usr/lib64/libKF5TextEditor.so.5
#11 0x7f56b5335b63 in KateCompletionModel::createGroups() () at
/usr/lib64/libKF5TextEditor.so.5
#12 0x7f56b5336265 in
KateCompletionModel::setCompletionModels(QList
const&) () at /usr/lib64/libKF5TextEditor.so.5
#13 0x7f56b532b928 in
KateCompletionWidget::startCompletion(KTextEditor::Range const&,
QList const&,
KTextEditor::CodeCompletionModel::InvocationType) () at
/usr/lib64/libKF5TextEditor.so.5
#14 0x7f56b532baec in
KateCompletionWidget::startCompletion(KTextEditor::CodeCompletionModel::InvocationType,
QList const&) () at
/usr/lib64/libKF5TextEditor.so.5
#15 0x7f56b532bf21 in KateCompletionWidget::automaticInvocation() () at
/usr/lib64/libKF5TextEditor.so.5
#16 0x7f56b54dc375 in  () at /usr/lib64/libKF5TextEditor.so.5
#17 0x7f56b0c9cbb1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#18 0x7f56b0caa112 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x7f56b0c9df34 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#20 0x7f56b20dde3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#21 0x7f56b20e249a in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#22 0x7f56b0c72fc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#23 0x7f56b0cc2c7e in QTimerInfoList::activateTimers() () at

[kdenlive] [Bug 374314] Problem with ApplyLUT effect

[YonaRod]

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

--- Comment #2 from YonaRod  ---
Of course, I have tested with several LUTs and however in other software like
Lightworks they work perfectly.
Here I leave you a link of LUTs that I try to use:
http://deluts.businesscatalyst.com/deluts-free-lut.html

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

[plasmashell] [Bug 374162] Add an option to sort programs chronologically in task bar, when grouping

[Timvde]

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

--- Comment #7 from Timvde  ---
No worries, thanks for your effort! If there is anything I can do, feel free to
ask. I have coding experience, but sadly not too much with C++/Qt/QML.

I actually already had a look at the source on Github (that was easier than
going through
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source), and could
only find the relevant QML[0], not the actual sorting implementation...

I make no promises though, and if you think it's easier to just code it up
yourself, that's probably the better choice. Chances that I'll become a
maintainer somewhere down the road are pretty slim.

[0]
https://github.com/KDE/plasma-desktop/blob/master/applets/taskmanager/package/contents/ui/main.qml#L125

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

[plasmashell] [Bug 374521] New: Plasma breaks suddenly when closing kde apps.

[Carlos Henrique Merces Moreira]

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

Bug ID: 374521
   Summary: Plasma breaks suddenly when closing kde apps.
   Product: plasmashell
   Version: 5.8.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ch.mercesmore...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.9.0-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I finished my day work, and tried to close multiple Okular instances that were
opened, as soon as I started doing this the system screen blinked and the task
bar dissapeared, but after few seconds later everything is back to normal
again.

- Unusual behavior I noticed:

The taskbar dissapeared, sometimes this bug happens in other ocassions and I'm
unable to open other apps, so I need to reboot my system, but in this
particular case the plasma restarted automatically and I was able to use the
system normally after this bug happened.

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

Thread 16 (Thread 0x7fb7d0977700 (LWP 2361)):
#0  0x7fb8abc2810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb8acb13bab in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb7f39701c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fb7f3974988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fb7f39721f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fb8acb12cf8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fb8abc22454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fb8ac4287df in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7fb7d1178700 (LWP 2360)):
#0  0x7fb8abc2810f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb8acb13bab in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb7f39701c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fb7f3974988 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#16 0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#17 0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#18 0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#19 0x7fb7f39749e2 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#20 0x7fb7f396f263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#21 0x7fb7f39721f9 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#22 0x7fb8acb12cf8 in  () at /usr/lib/libQt5Core.so.5
#23 0x7fb8abc22454 in start_thread () at /usr/lib/libpthread.so.0
#24 

[plasmashell] [Bug 374162] Add an option to sort programs chronologically in task bar, when grouping

[Eike Hein]

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED

--- Comment #6 from Eike Hein  ---
Ah I see.

I'll consider adding a new sort mode maybe ... mmm. It might be too late for
5.9 already, though, sorry!

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

[kalarm] [Bug 374520] New: When KAlarm is running with --tray, running another instance doesn't show a new main window

[David Jarvie]

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

Bug ID: 374520
   Summary: When KAlarm is running with --tray, running another
instance doesn't show a new main window
   Product: kalarm
   Version: 2.11.9-5ak
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: djar...@kde.org
  Reporter: djar...@kde.org
  Target Milestone: ---

Normally when KAlarm is minimised into the system tray, running another
instance shows a main window. However, when KAlarm was run using 'kalarm
--tray', a main window is not displayed. If the system tray icon is
inaccessible, this means that it's impossible to display a main window without
killing KAlarm first.

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

[systemsettings] [Bug 374519] List of search plugins is language-specific

[bugzilla_noreply]

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

k...@web.de changed:

   What|Removed |Added

  Component|kcm_desktopsearch   |general

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

[systemsettings] [Bug 374519] New: List of search plugins is language-specific

[bugzilla_noreply]

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

Bug ID: 374519
   Summary: List of search plugins is language-specific
   Product: systemsettings
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_desktopsearch
  Assignee: nepomuk-b...@kde.org
  Reporter: k...@web.de
CC: nepomuk-b...@kde.org
  Target Milestone: ---

Starting ksystemsettings5 with the translation turned on at first, then again
with
LC_ALL=C ksystemsettings5
and navigating to Search > Plasma Search
shows a list of search plugins where almost every entry is disabled, except for 
Kwin, Symbols, Audio
although all entries were previously enabled in the translated
ksystemsettings5.
This happens because those are the only plugins which have the same name in the
german translation and untranslated. (Yes, the name is Symbols instead of
Symbole.)

The list of search plugins should store the original untranslated values, and
translate them when they are shown in ksystemsettings.

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

[digikam] [Bug 374428] digiKam crashes when choosing several duplicate results

[Wolfgang Scheffner]

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

--- Comment #9 from Wolfgang Scheffner  ---
Very simple, sure! For a silly user like me. Pfff ...
But now comes the interesting thing: I did it but that way digiKam didn't
crash! I tried again the "normal" way but cannot reproduce the crash anymore.
Everything works fine. Seems you fixed the bug by creating this new bundle.

Wolfgang

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

[krunner] [Bug 374518] New: Search suggestions for webshortcuts show up in all kinds of runners

[bugzilla_noreply]

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

Bug ID: 374518
   Summary: Search suggestions for webshortcuts show up in all
kinds of runners
   Product: krunner
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: k...@web.de
  Target Milestone: ---

We can run krunner searching only trough a single runner, for example we can
search for bookmarks:

qdbus-qt5 org.kde.krunner /App displaySingleRunner bookmark

When entering any text into this bookmark-SingleRunner that happens to be the
beginning of a webshortcut such as
> gg

A suggestion for the google webshortcut shows up
> gg: 1234

When pressing enter nothing happens, since there is no bookmark called "gg:
1234", and we are in the bookmark-SingleRunner, which doesn't know how to
handle webshortcuts.

Suggestions for webshortcuts should not show up in a SingleRunner that is not
the webshortcut-SingleRunner.

The only SingleRunner where the suggestions should be shown is this one:

qdbus-qt5 org.kde.krunner /App displaySingleRunner webshortcuts

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

[umbrello] [Bug 374515] Not possible to reset label text positions from association widget context menu

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/umb
   ||rello/d218d690c6cdba1c3b6a8
   ||c9af03ade79237c56ba
   Version Fixed In||2.21.1 (KDE Applications
   ||16.12.1)
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Ralf Habacker  ---
Git commit d218d690c6cdba1c3b6a8c9af03ade79237c56ba by Ralf Habacker.
Committed on 04/01/2017 at 00:00.
Pushed by habacker into branch 'Applications/16.12'.

Fix 'Not possible to reset label text positions from association widget context
menu'.

The fix adds additional menu entries having for full
associations to attribute association context menus too.
FIXED-IN:2.21.1 (KDE Applications 16.12.1)

M  +1-0umbrello/listpopupmenu.cpp

https://commits.kde.org/umbrello/d218d690c6cdba1c3b6a8c9af03ade79237c56ba

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

[umbrello] [Bug 374515] Not possible to reset label text positions from association widget context menu

[Ralf Habacker]

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

--- Comment #1 from Ralf Habacker  ---
Note: This happens with attribute associations e.g. aggregate and compositions.

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

[klipper] [Bug 374517] New: Enormous clipboard data causes crash

[James Ring]

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

Bug ID: 374517
   Summary: Enormous clipboard data causes crash
   Product: klipper
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mgraess...@kde.org
  Reporter: s...@jdns.org
  Target Milestone: ---

To reproduce:

Step 1: dd if=/dev/urandom of=/dev/stdout count=1 bs=500M | base64 | xclip
-selection clipboard

Step 2: right-click on Klipper

I think this is different to https://bugs.kde.org/show_bug.cgi?id=33747, as the
crash seems to be in computing the QFontMetrics::boundingRect for a 500Mb
string. I'd think it would be easy enough to simply truncate the displayed text
to a reasonable amount (e.g. first and last 100 bytes or something).

Application: Klipper (klipper), signal: Segmentation fault
Using host libthread_db library "/usr/grte/v4/lib64/libthread_db.so.1".
[KCrash Handler]
#5  memset () at ../sysdeps/x86_64/memset.S:80
#6  0x7fc76123a0f8 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x7fc76123a36f in QTextEngine::LayoutData::reallocate(int) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8  0x7fc76123fcd6 in QTextEngine::attributes() const () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x7fc76124dde2 in QTextLine::layout_helper(int) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x7fc761139c06 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x7fc76113a701 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x7fc76121a5c3 in QFontMetrics::boundingRect(QRect const&, int, QString
const&, int, int*) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x7fc76141c143 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x7fc76141c3a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#15 0x7fc76141d14d in QMenu::popup(QPoint const&, QAction*) () from
/usr/lib/x86_64-linux-gnu/libQtGui.so.4

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

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

[flyscan]

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

--- Comment #46 from flyscan  ---
(In reply to Charles from comment #44)
> If it makes any difference, I tried my tablet (Ugee 1910B) on my old desktop
> and it worked fine with the same driver.
> The computer I'm having a problem on has a AMD FX-8350 CPU
> The computer that works fine has an Intel(R) Core(TM) i5-3570k CPU
> Let me know if there is any other information I can provide that could be
> helpful.

Hi Charles, I'm not a dev, just a fellow user with the same problem, also 
running an AMD CPU looking to compare notes. I really need to find a C++ and 
QT for dummies guide but I got the tablet to learn how to draw, not how to 
code :P

What OS build did you have? 

Run->DxDiag might be the easiest route. 


What Ugee driver is running? 

Hovering your mouse over the driver should show this: 
http://i.imgur.com/Fk72wfZ.png

When I get home tonight and try my laptop, my i3 media PC and i5 and we'll 
compare notes. I don't have a Windows 7 computer to test on.

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

[plasmashell] [Bug 374455] scaling, using scaling leads to pointing and displaying problems

[David Edmundson]

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

--- Comment #4 from David Edmundson  ---
it's a problem with the apps not supporting the scaling.

It's not a font problem, but it's where scaling artifacts are most visible if
they go via a (non scaled) pixmap cache.

It's an application problem because this scaling is just a setting, actually
doing the scaling is the responsibility of the application.

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

[digikam] [Bug 374516] Persons metadata are not updated after a tag removed

[Marc]

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

--- Comment #1 from Marc  ---
Created attachment 103184
  --> https://bugs.kde.org/attachment.cgi?id=103184=edit
Exiftool output after removing unappropriate tag and applying metadata

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

[digikam] [Bug 374516] Persons metadata are not updated after a tag removed

[Marc]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 374516] New: Persons metadata are not updated after a tag removed

[Marc]

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

Bug ID: 374516
   Summary: Persons metadata are not updated after a tag removed
   Product: digikam
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata-Editor
  Assignee: digikam-de...@kde.org
  Reporter: erme...@gmail.com
  Target Milestone: ---

Created attachment 103183
  --> https://bugs.kde.org/attachment.cgi?id=103183=edit
Exiftool output before removing unappropriate person tag

Hello,

My wife has changed her name and so, I try to rename all her embedded tags
within digikam.
First, I have tried to rename her tag in the metadata person tag. I was
thinking it was ok.

But after reloading metadata from files, I see that on some files, pictures
have both her old and new person tag.
So I try now to remove the old tag.
Before applying update, I've collected exif metadata with exiftool (exiftool
/home/marc/pictures/img_6654.cr2). File has been attached under before.txt.
In digikam, in one picture which have both the new and old tag, I remove from
the picture her old name.
Then I click to "apply metadata in picture" from menu item. 
After applying tag, I have collected metadata with exiftool. File has been
attached under afterupdate.txt.

Under digikam, My wife is now known has her new name. But If I refresh metadata
(under menu item > reload metadata from file), she still known under the two
names.

I was thinking of a permission issue, but file have rw for every one.

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

[umbrello] [Bug 374511] Not possible to reset association widget text positions

[Ralf Habacker]

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

--- Comment #2 from Ralf Habacker  ---
(In reply to Ralf Habacker from comment #0)
Step 7 was incorrect:
> 7. right click in the association and press "Reset text positions"
It has to be 
7. move one of the related widgets

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

[umbrello] [Bug 374515] New: Not possible to reset label text positions from association widget context menu

[Ralf Habacker]

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

Bug ID: 374515
   Summary: Not possible to reset label text positions from
association widget context menu
   Product: umbrello
   Version: 2.21.0 (KDE Applications 16.12.0)
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de
  Target Milestone: ---

In the context menu of association widgets text tabels there is an entry to
reset text positions, but this is not possible from the association widget
context menu which is useful in cases where it is not possible to identify the
related label.

How to reproduce: 
1. Start umbrello
2. add two classes
3. add an association between both classes
4. right click in the association
What happens:
There is no entry to reset text label positions

What is expected:
There should be an entry to reset text positions

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

[umbrello] [Bug 374511] Not possible to reset association widget text positions

[Ralf Habacker]

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

Ralf Habacker  changed:

   What|Removed |Added

   Version Fixed In||2.21.1 (KDE Applications
   ||16.12.1)
  Latest Commit||https://commits.kde.org/umb
   ||rello/7396c5f2decfee0cc4098
   ||d97dd834f0a3f7a8cd0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Ralf Habacker  ---
Git commit 7396c5f2decfee0cc4098d97dd834f0a3f7a8cd0 by Ralf Habacker.
Committed on 03/01/2017 at 23:29.
Pushed by habacker into branch 'Applications/16.12'.

Fix 'Not possible to reset association widget text positions'.

UMLWidget::m_startMove was set on mouse move event but not
cleared on mouse release event.
FIXED-IN:2.21.1 (KDE Applications 16.12.1)

M  +1-0umbrello/umlwidgets/umlwidget.cpp

https://commits.kde.org/umbrello/7396c5f2decfee0cc4098d97dd834f0a3f7a8cd0

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

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

[bugzilla_noreply]

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

--- Comment #9 from k...@web.de ---
(In reply to Riku Voipio from comment #8)
> (In reply to kdeu from comment #7)
> > Are there any experiences whith using LMDB and NOSYNC?
> 
> Personally I've happily used that with patch attached since filing this bug
> - except for a handful of upgrades when I forgot the patch, only to notice
> that suddenly the disk light flashing means jittery UI again.

I mean experiences with many users, and with crashes. If you don't test for
crashes that's not a test for data corruption. You probably didn't crash your
computer on purpose.

> You are assuming that under current configuration LMDB can't get corrupted.
> File systems are nasty and even with fdatasync there are caveats.

That's not true. Without NOSYNC, LMDB is safe and does not get corrupted. See:

http://openldap-devel.openldap.narkive.com/k1bbhN5H/lmdb-crash-consistency-again#post7
> All in all a bunch of bogus reporting; claiming that all DBs are broken when
> in fact LMDB is perfectly correct

> But for
> most users, sudden crashes (especially in middle of transactions) is really
> rare events.

There are linux users who suffer from frequent power outages.
> we used to get lots of bug reports which were because of corrupted databases

> Recovering the DB is somewhat pointless - you can just
> regenerate it from scratch, if under idle iopriority the indexing really has
> no user impact.

Yes you can regenerate from scratch, but how do you detect when to have to do
that? This concern was already mentioned in comment #2:

> I'm a little conflicted about this approach since when the index does get 
> corrupted,
> it will be impossible for us to detect it. With our previous backend 
> (xapian), we
> used to get lots of bug reports which were because of corrupted databases :(

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

[kdenlive] [Bug 374449] Timeline minimum height is too large

[Alexandre Bento Freire]

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

--- Comment #2 from Alexandre Bento Freire  ---
Thanks,
I will be looking forward for the next version

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

[krusader] [Bug 374404] when copy in folder, free space info (in the upper left of panel Krusader) is not refreshed but Ctrl+R is refreshing it

[bugzilla_noreply]

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

--- Comment #4 from kde...@boson.nom.za ---
With help of the eapply_user mechanism, i'm recompiled krusader with your
patch. It's work ok now even with symlinked dirs from different hdd's. Thank
you.

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

[knetwalk] [Bug 348686] knetwalk 3.3.0 does not update network node icons

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kne
   ||twalk/6c6d71ad0822bf6b48e1c
   ||84a790ac1106e0af88b
 Resolution|--- |FIXED

--- Comment #8 from Albert Astals Cid  ---
Git commit 6c6d71ad0822bf6b48e1c84a790ac1106e0af88b by Albert Astals Cid, on
behalf of Hatto von Hatzfeld.
Committed on 03/01/2017 at 22:52.
Pushed by aacid into branch 'Applications/16.12'.

Fix network nodes not getting updated

M  +3-0src/qml/logic.js

https://commits.kde.org/knetwalk/6c6d71ad0822bf6b48e1c84a790ac1106e0af88b

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

[Akonadi] [Bug 374514] New: Crash on akonadictl stop

[Friedrich W . H . Kossebau]

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

Bug ID: 374514
   Summary: Crash on akonadictl stop
   Product: Akonadi
   Version: 5.4.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: kosse...@kde.org
  Target Milestone: ---

- What I was doing when the application crashed:
The filter agent started to do strange things, like moving any emails into
wrong folders when selecting them in the KMail UI, but not handling incoming
emails at all, with such errors in the mysql log:
[ERROR] mysqld: Deadlock found when trying to get lock; try restarting
transaction

So I called "akonadictl stop" to make it stop, to start it again hoping for
some clean-up on start, but on that akonadiserver crashed:

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

Thread 22 (Thread 0x7f11bd61e700 (LWP 26708)):
#0  0x7f11dfc1e4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f11e198b2b6 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f11c8055760) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f11c8055760) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f11c80555a0,
mutex=mutex@entry=0x7f11c80035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f11e1986ae2 in QThreadPoolThread::run (this=0x7f11c8055590) at
thread/qthreadpool.cpp:133
#5  0x7f11e198a4c8 in QThreadPrivate::start (arg=0x7f11c8055590) at
thread/qthread_unix.cpp:368
#6  0x7f11dfc18454 in start_thread () from /lib64/libpthread.so.0
#7  0x7f11e108037f in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7f113fff7700 (LWP 26707)):
#0  0x7f11dfc1e4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f11e198b2b6 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f11c80552f0) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f11c80552f0) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f11c8055130,
mutex=mutex@entry=0x7f11c80035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f11e1986ae2 in QThreadPoolThread::run (this=0x7f11c8055120) at
thread/qthreadpool.cpp:133
#5  0x7f11e198a4c8 in QThreadPrivate::start (arg=0x7f11c8055120) at
thread/qthread_unix.cpp:368
#6  0x7f11dfc18454 in start_thread () from /lib64/libpthread.so.0
#7  0x7f11e108037f in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7f1142ffd700 (LWP 26706)):
#0  0x7f11dfc1e4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f11e198b2b6 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f11c8054e20) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f11c8054e20) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f11c8044840,
mutex=mutex@entry=0x7f11c80035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f11e1986ae2 in QThreadPoolThread::run (this=0x7f11c8044830) at
thread/qthreadpool.cpp:133
#5  0x7f11e198a4c8 in QThreadPrivate::start (arg=0x7f11c8044830) at
thread/qthread_unix.cpp:368
#6  0x7f11dfc18454 in start_thread () from /lib64/libpthread.so.0
#7  0x7f11e108037f in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7f11407f8700 (LWP 26705)):
#0  0x7f11dfc1e4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f11e198b2b6 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f11c8055bd0) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f11c8055bd0) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f11c8055a10,
mutex=mutex@entry=0x7f11c80035a0, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f11e1986ae2 in QThreadPoolThread::run (this=0x7f11c8055a00) at
thread/qthreadpool.cpp:133
#5  0x7f11e198a4c8 in QThreadPrivate::start (arg=0x7f11c8055a00) at
thread/qthread_unix.cpp:368
#6  0x7f11dfc18454 in start_thread () from /lib64/libpthread.so.0
#7  0x7f11e108037f in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7f11427fc700 (LWP 26704)):
#0  0x7f11dfc1e4b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f11e198b2b6 in QWaitConditionPrivate::wait_relative (time=3,
this=0x7f11c8056040) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x7f11c8056040) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x7f11c8055e80,
mutex=mutex@entry=0x7f11c80035a0, time=3) at

[kdenlive] [Bug 374513] Crash when playing around with bass effect

[Christian Weiske]

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

--- Comment #1 from Christian Weiske  ---
Created attachment 103182
  --> https://bugs.kde.org/attachment.cgi?id=103182=edit
gdb thread apply all bt

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

[kdenlive] [Bug 374513] New: Crash when playing around with bass effect

[Christian Weiske]

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

Bug ID: 374513
   Summary: Crash when playing around with bass effect
   Product: kdenlive
   Version: 16.12.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: cwei...@cweiske.de
  Target Milestone: ---

Created attachment 103181
  --> https://bugs.kde.org/attachment.cgi?id=103181=edit
gdb bt full

I was trying to find out how the bass effect works by randomly modifying each
of the settable values to random values, and eventually kdenlive crashed.


Version info:
kdenlive Version 16.12.0
Using MLT version 6.3.0

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

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

[kdenlive] [Bug 374309] Crash when playing video and scrolling with jog wheel

[Christian Weiske]

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

Christian Weiske  changed:

   What|Removed |Added

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

--- Comment #3 from Christian Weiske  ---
Reason for this crash was the jog wheel, see bug #374362.

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

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

[neon] [Bug 374512] New: Empty plasma desktop without panel

[Lucas]

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

Bug ID: 374512
   Summary: Empty plasma desktop without panel
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Live/Install images
  Assignee: neon-b...@kde.org
  Reporter: kde...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

On the latest Neon git unstable ISO images plasma session starts with an empty
desktop without panel. I tried the ISO images from 01-Jan-2017 and 03-Jan-2017.
Checksums are ok.

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

[kdenlive] [Bug 374361] Crash when adding clip to timeline and playing

[Christian Weiske]

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

Christian Weiske  changed:

   What|Removed |Added

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

--- Comment #2 from Christian Weiske  ---
Reason for this crash was the jog wheel, see bug #374362.

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

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

[kdenlive] [Bug 374362] Jog wheel scrolls in timeline and file list

[Christian Weiske]

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

--- Comment #4 from Christian Weiske  ---
*** Bug 374309 has been marked as a duplicate of this bug. ***

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

[kdenlive] [Bug 374362] Jog wheel scrolls in timeline and file list

[Christian Weiske]

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

--- Comment #3 from Christian Weiske  ---
*** Bug 374361 has been marked as a duplicate of this bug. ***

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

[kdenlive] [Bug 374362] Jog wheel scrolls in timeline and file list

[Christian Weiske]

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

--- Comment #2 from Christian Weiske  ---
Many thanks for this tip!
Disabling the jog wheel in xinput did indeed solve the crash issues #374309 and
#374361.

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

[umbrello] [Bug 374511] New: Not possible to reset association widget text positions

[Ralf Habacker]

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

Bug ID: 374511
   Summary: Not possible to reset association widget text
positions
   Product: umbrello
   Version: 2.21.0 (KDE Applications 16.12.0)
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: ralf.habac...@freenet.de
  Target Milestone: ---

On associations there is a context menu entry named "Reset text position" to
reset positions of related association texts. This function seems to be broken.

How to reproduce:
1. Start umbrello
2. add two classes
3. add an association between both classes
4. Open association property dialog and enter text for both multiplicity e.g
'1' and  '0..1'.
5. save and close property dialog
6. move multiplicity labels to other location
7. right click in the association and press "Reset text positions"

-> nothing happens

What is expected:
The labels should be moved to the initial position

Additional informations:
After moving one multiplicity label the labels are not moved anymore when
moving a related class on the diagram. It looks that tracking labels is
completly broken after one label move.

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

[kipiplugins] [Bug 374510] Creating albums on flickr with line breaks in their descriptions fails [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kip
   ||i-plugins/d524e64e4c047d653
   ||4f4833fe36dd675d2c0c3ff

--- Comment #1 from Maik Qualmann  ---
Git commit d524e64e4c047d6534f4833fe36dd675d2c0c3ff by Maik Qualmann.
Committed on 03/01/2017 at 22:24.
Pushed by mqualmann into branch 'master'.

replace line feeds with spaces in Flickr photosets
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +15   -2flickr/flickrtalker.cpp

https://commits.kde.org/kipi-plugins/d524e64e4c047d6534f4833fe36dd675d2c0c3ff

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

[kipiplugins] [Bug 365867] Export to remote storage fails

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #8 from Luigi Toscano  ---
(In reply to caulier.gilles from comment #6)
> Welcome to the insoluble puzzle of KIO slave. This is why we have dropped
> all KIO slave support in digiKam, excepted for this plugin which is optional
> at compilation time of course.
> 
> So it's typically a packaging and installing problem. It's on your system
> (config or something like that). Contact your distro team for any help.

Instead of removing the usage of transparent file systems for users, did you
try to raise the issues on the appropriate mailing lists? I don't remember any
discussion related to this on kde-devel@, kde-core-devel@ or
kde-frameworks-devel@.

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

[kipiplugins] [Bug 373820] Port Export to Remote Storage tool to pure QT5

[Luigi Toscano]

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

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #4 from Luigi Toscano  ---
Can you please decide on a proper solution, and/or discuss this on kde-devel@?
I suspect you are cutting some choice for some categories of users, hardcoding
some values that the user expect to be set somewhere else (with an integration
plugin for example).

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

[kdev-python] [Bug 374097] Kdevelop 5 crashes when editing python file

[Jonathan Verner]

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

--- Comment #13 from Jonathan Verner  ---
I can also reproduce the crash with the 5.1 beta release... It gives me a
similar backtrace:

#0  0x7fffa8f3 in
Python::Helper::declarationForName(KDevelop::QualifiedIdentifier const&,
KDevelop::RangeInRevision const&, KDevelop::DUChainPointer) ()
   from /tmp/kdd/usr/lib/libkdevpythonduchain.so
#1  0x7fffa8f2c720 in
Python::ExpressionVisitor::visitName(Python::NameAst*) ()
   from /tmp/kdd/usr/lib/libkdevpythonduchain.so
#2  0x7fffa8f2bd58 in
Python::ExpressionVisitor::visitCall(Python::CallAst*) ()
   from /tmp/kdd/usr/lib/libkdevpythonduchain.so
#3  0x7fffcb9a3dca in
Python::AstDefaultVisitor::visitCode(Python::CodeAst*) ()
   from /tmp/kdd/usr/lib/libkdevpythonparser.so
#4  0x7fffa91977d2 in Python::visitorForString(QString,
KDevelop::DUContext*, KDevelop::CursorInRevision) () from
/tmp/kdd/usr/lib/libkdevpythoncompletion.so
#5  0x7fffa919f98e in
Python::PythonCodeCompletionContext::memberAccessItems() ()
   from /tmp/kdd/usr/lib/libkdevpythoncompletion.so
#6  0x7fffa91a0d66 in
Python::PythonCodeCompletionContext::completionItems(bool&, bool) ()
   from /tmp/kdd/usr/lib/libkdevpythoncompletion.so
#7  0x7fffedd7bd5a in
KDevelop::CodeCompletionWorker::computeCompletions(KDevelop::DUChainPointer,
KTextEditor::Cursor const&, QString, KTextEditor::Range const&, QString const&)
() from /tmp/kdd/usr/lib/libKDevPlatformLanguage.so.10
#8  0x7fffedd7b7fa in
KDevelop::CodeCompletionWorker::computeCompletions(KDevelop::DUChainPointer,
KTextEditor::Cursor const&, KTextEditor::View*) ()
   from /tmp/kdd/usr/lib/libKDevPlatformLanguage.so.10
#9  0x7fffedd8197a in QtPrivate::QSlotObject,
KTextEditor::Cursor const&, KTextEditor::View*),
QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
   from /tmp/kdd/usr/lib/libKDevPlatformLanguage.so.10
#10 0x71d92081 in QObject::event(QEvent*) () from
/tmp/kdd/usr/lib/libQt5Core.so.5
#11 0x726d3a9c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /tmp/kdd/usr/lib/libQt5Widgets.so.5
#12 0x726dae96 in QApplication::notify(QObject*, QEvent*) ()
   from /tmp/kdd/usr/lib/libQt5Widgets.so.5
#13 0x71d68248 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
   from /tmp/kdd/usr/lib/libQt5Core.so.5
#14 0x71d6a83b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
   from /tmp/kdd/usr/lib/libQt5Core.so.5
#15 0x71db56e4 in
QEventDispatcherUNIX::processEvents(QFlags)
() from /tmp/kdd/usr/lib/libQt5Core.so.5
#16 0x71d667fa in
QEventLoop::exec(QFlags) ()
   from /tmp/kdd/usr/lib/libQt5Core.so.5
#17 0x71b9ad6c in QThread::exec() () from
/tmp/kdd/usr/lib/libQt5Core.so.5
#18 0x7fffedd83708 in KDevelop::CompletionWorkerThread::run() ()
   from /tmp/kdd/usr/lib/libKDevPlatformLanguage.so.10
#19 0x71b9f6a6 in ?? () from /tmp/kdd/usr/lib/libQt5Core.so.5
#20 0x7fffe9e07184 in start_thread (arg=0x7fffa8ef1700) at
pthread_create.c:312
#21 0x7100937d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

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

[Akonadi] [Bug 373782] akonadi failed to append item

[Daniel Vrátil]

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

Daniel Vrátil  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.4.1
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/ako
   ||nadi/85c5f22b836805ecd20a7a
   ||c8eaae0a6861bdcd24

--- Comment #13 from Daniel Vrátil  ---
Git commit 85c5f22b836805ecd20a7ac8eaae0a6861bdcd24 by Daniel Vrátil.
Committed on 03/01/2017 at 22:02.
Pushed by dvratil into branch 'Applications/16.12'.

AKAPPEND: ensure we always insert with a valid date

Latest MySQL does not like null datetime for some reason, so make sure
we always have a valid date on INSERT.
FIXED-IN: 5.4.1

M  +5-4src/server/handler/akappend.cpp

https://commits.kde.org/akonadi/85c5f22b836805ecd20a7ac8eaae0a6861bdcd24

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

[kipiplugins] [Bug 373820] Port Export to Remote Storage tool to pure QT5

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
Git commit c6f8efa3c8a114deb297cf30bd3ab4382c8e4f65 by Maik Qualmann.
Committed on 03/01/2017 at 22:05.
Pushed by mqualmann into branch 'master'.

use native file dialog only if running plasma desktop

M  +3-1remotestorage/KioExportWidget.cpp

https://commits.kde.org/kipi-plugins/c6f8efa3c8a114deb297cf30bd3ab4382c8e4f65

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

[plasmashell] [Bug 367582] 19Aug16 Updates (131) Crash Desktop Icon/Scripts

[MaxiPunkt]

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

MaxiPunkt  changed:

   What|Removed |Added

 CC||maxantis...@freenet.de

--- Comment #7 from MaxiPunkt  ---
Hi there,

I've noticed similar issue on Fedora-23 & Fedora-25:

Found out that starting a bash-script via desktop-file as ordinary user is just
fine.

But same attempt in combination with UID-substitution functionality (the
bash-script shall be run as user "root") the execution of bash-script fails.

UID-substitution is defined directly inside the desktop-file (or within
KDE-properties of the icon). Like this one is asked to authenticate (password)
and the script will executed then.
This worked for me for years (in particular I run a backup-script as "root"),
now this is broken for a while already.


Content of example bash-script:
---
#!/bin/bash
echo -n "I am: "
whoami


Content of example desktop-file:

[Desktop Entry]
Comment=A simple script for test proposes
Exec=/path/to/above/script/test.sh
GenericName=Bash script
Icon=application-x-shellscript
MimeType=
Name=My-Terminal-Script
Path=
StartupNotify=false
Terminal=true
TerminalOptions=\s--noclose
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=none
#X-KDE-SubstituteUID=true
#X-KDE-Username=root


Check running the script by clicking the icon - works fine.
Uncomment the last 2 lines (enables UID-substitution) - will fail.


If my bug should not be related to the reported one please let me know.

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

[kipiplugins] [Bug 374510] Creating albums on flickr with line breaks in their descriptions fails [patch]

[bugzilla_noreply]

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

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

   What|Removed |Added

Summary|Creating albums on flickr   |Creating albums on flickr
   |with line breaks in their   |with line breaks in their
   |descriptions fails  |descriptions fails [patch]
 CC||caulier.gil...@gmail.com

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

[kgpg] [Bug 373408] kgpg segfault on boot and every later run

[Rolf Eike Beer]

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

--- Comment #3 from Rolf Eike Beer  ---
Git commit ac2ca301c6ef2d02810b762c618f1ce504382c4e by Rolf Eike Beer.
Committed on 03/01/2017 at 21:47.
Pushed by dakon into branch 'Applications/16.12'.

fix crash when GnuPG does not output curve fields for keys, take 3

secret keys, it is.
Related: bug 374509, bug 371410
FIXED-IN:16.12.1

M  +2-1kgpginterface.cpp

https://commits.kde.org/kgpg/ac2ca301c6ef2d02810b762c618f1ce504382c4e

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

[kgpg] [Bug 371410] kgpg crashes on startup and otherwise

[Rolf Eike Beer]

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

--- Comment #8 from Rolf Eike Beer  ---
Git commit ac2ca301c6ef2d02810b762c618f1ce504382c4e by Rolf Eike Beer.
Committed on 03/01/2017 at 21:47.
Pushed by dakon into branch 'Applications/16.12'.

fix crash when GnuPG does not output curve fields for keys, take 3

secret keys, it is.
Related: bug 374509, bug 373408
FIXED-IN:16.12.1

M  +2-1kgpginterface.cpp

https://commits.kde.org/kgpg/ac2ca301c6ef2d02810b762c618f1ce504382c4e

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

[kgpg] [Bug 374509] Kgpg crashes with segfault during initialization

[Rolf Eike Beer]

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

Rolf Eike Beer  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||16.12.1
  Latest Commit||https://commits.kde.org/kgp
   ||g/ac2ca301c6ef2d02810b762c6
   ||18f1ce504382c4e
 Resolution|--- |FIXED

--- Comment #1 from Rolf Eike Beer  ---
Git commit ac2ca301c6ef2d02810b762c618f1ce504382c4e by Rolf Eike Beer.
Committed on 03/01/2017 at 21:47.
Pushed by dakon into branch 'Applications/16.12'.

fix crash when GnuPG does not output curve fields for keys, take 3

secret keys, it is.
Related: bug 371410, bug 373408
FIXED-IN:16.12.1

M  +2-1kgpginterface.cpp

https://commits.kde.org/kgpg/ac2ca301c6ef2d02810b762c618f1ce504382c4e

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

[plasmashell] [Bug 371858] Occasional wrong desktop at startup

[bugzilla_noreply]

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

--- Comment #23 from it...@inwind.it ---
According to System Settings, the primary screen is the external one (HDMI1). I
don't know how to determine whether a screen is enabled in Plasma; in any case
I leave the laptop closed when booting so it stays off at startup (and all the
time)

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

[krita] [Bug 374461] Cannot right-click with a Wacom Tablet

[silva]

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

--- Comment #8 from silva  ---
Hahahaha!

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

[plasmashell] [Bug 374443] Kicker popup doesn't appear when other windows are on screen

[Wim Delvaux]

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

--- Comment #11 from Wim Delvaux  ---
Yes that would help :)

I have an NVIDIA card with NVIDIA drivers if that helps.

Can I perhaps download a 'debug' version of kicker which I could run ?

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

[marble] [Bug 316969] crashed always when importing a bookmark file

[Dennis Nienhüser]

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

--- Comment #9 from Dennis Nienhüser  ---
GCI task https://codein.withgoogle.com/tasks/5107915830591488/ should take care
of this issue.

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

[digikam] [Bug 374248] importing photo, bad file selector

[bugzilla_noreply]

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

--- Comment #13 from caulier.gil...@gmail.com ---
Maik,

Dbus can be a solution. Not perfect so far, but look here :

https://cgit.kde.org/digikam.git/tree/libs/notificationmanager/dnotificationwrapper.cpp#n87

Take a care : Dbus is optional in digiKam.

Gilles

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

[plasmashell] [Bug 371858] Occasional wrong desktop at startup

[bugzilla_noreply]

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

--- Comment #22 from it...@inwind.it ---
Created attachment 103179
  --> https://bugs.kde.org/attachment.cgi?id=103179=edit
applersrc of ordinary user 5.8.5

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

[plasmashell] [Bug 371858] Occasional wrong desktop at startup

[bugzilla_noreply]

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

--- Comment #21 from it...@inwind.it ---
Created attachment 103178
  --> https://bugs.kde.org/attachment.cgi?id=103178=edit
plasmashellrc of ordinary user 5.8.5

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[bugzilla_noreply]

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

an.in...@free.fr changed:

   What|Removed |Added

 CC||an.in...@free.fr

--- Comment #214 from an.in...@free.fr ---
There is a work-around that does not require any installation, just
configuration.
Tested on Debian Stretch with KDE 5.8 (which will be used for a while, so the
w/a may be useful). 

At the end, you will have a pager with N "screen", Ctrl-FN will switch to
"screen" N, and the mouse wheel will also move between "screens". Except that
technically each "screen" will be an activity of 1 virtual desktop (VD).

Let's start:

1) switch the pager from a VD to an activity pager:
  - unlock the taskbar
  - right click on the pager
  - select the "Alternatives..." menu entry
  - click "Activity Pager" and then the "Switch" button
  => now the pager tracks activities
  While there, right click on the pager again, select "Activity Pager
Settings..." and configure to taste.

2) Move to a single VD, so each activity = 1 VD = 1 screen
  - System Settings => Desktop Behavior => Virtual Desktops, reduce to 1.

3) Create as many activities as you need "screens" (same number as the qty of
   VDs you used to use);
  - System Settings => Desktop Behavior => Activities, create and name as
needed.
  Now you see the activities in your pager, and from the pager point of view
  it's as before except activities replaced VDs.   

4) Enable the mouse wheel to switch between activities
  - Right click on the desktop background => Configure Desktop
  - Select the "Mouse Actions" tab
  - Item "Vertical-Scroll", select "Switch Activity"
  IMPORTANT: this setting is per activity. So you need to repeat this for all
  the created activities.

5) Enable Ctrl-Fn to switch directly to screen (= activity) n

  The first thing I tried (and it didn't work for me) is in System Settings =>
Shortcuts => Global Shortcuts. In the "Components" list, select the "Plasma"
entry. Here you can see the created activities, but there are two problems:
- instead of their nice, user chosen name, it's a UUID based name
- assigning a keyboard shortcut "Ctrl-Fn" is possible, but does not work
for me
  => Could someone confirm this on latest KDE? So I know if I need to file a
 bug on KDE or on Debian. Thanks.

  The alternate method, which works, uses "Custom Shortcuts" under the shortcut
system settings too and is a bit more complicated. For each screen/activity:
   - click on "Edit" and select New => Global Shortcut => D-Bus Command
   - Name the new keyboard shortcut, for example "Go to screen N"
   - In "Trigger", set the shortcut. For example Ctrl-F1 for the 1st screen
   - In the Action tab:
 * For "Remote application", use "org.kde.ActivityManager"
 * For "Remote object": "/ActivityManager/Activities"
 * For "Function": "org.kde.ActivityManager.Activities.SetCurrentActivity"
 * For "Arguments": the UUID of the activity (see below).
 (no quote in any field)

 And to get an activity UUID:
 * click on "Launch D-Bus Browser"
 * in the "search" field, enter "activity"
 * select "org.kde.ActivityManager"
 * in the methods tab, select ActivityManager => Activities
   then: org.kde.ActivityManager.Activities
 * click on the "Method: ListActivitiesWithInformation" entry
 Now in the bottom field, you have the method output listing all the
created activities with their nice user name and their UUID. Select the UUID
(only, not the "Argument: (i) part nor the quotes) and use it the shortcut
"Arguments" field as is. 
 * Apply.

 Now Ctrl-Fn will switch to the activity/screen n. There is a slide
animation that doesn't seem to be configurable. If anyone knows how to disable
it, I'd appreciate the info (but I can live with it).

Done! And of course, because each "screen" is now an activity, you can
configure different backgrounds and widgets. As I don't use other fancy VD
tools (cube, etc.) for my limited use it's functionally equivalent to the VD
features I used to use under KDE4. For others, you may loose some features. If
anyone knows how to improve on this, feel free to share.

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

[marble] [Bug 373750] KDE Marble (Installed from openSUSE standard) breaks down when trying to import bookmarks from a previous installed Marble

[Dennis Nienhüser]

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

Dennis Nienhüser  changed:

   What|Removed |Added

 CC||nienhue...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Dennis Nienhüser  ---


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

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

[marble] [Bug 316969] crashed always when importing a bookmark file

[Dennis Nienhüser]

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

Dennis Nienhüser  changed:

   What|Removed |Added

 CC||flywh...@illogical.dk

--- Comment #8 from Dennis Nienhüser  ---
*** Bug 373750 has been marked as a duplicate of this bug. ***

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

[marble] [Bug 352208] Can't import bookmarks in kml format, nothing happends or crashes

[Dennis Nienhüser]

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

--- Comment #3 from Dennis Nienhüser  ---
I still think it's a duplicate of bug 316969. The reason is likely that the
imported placemarks are deleted when the bookmark file goes out of scope. This
can lead to a crash, but it does not have to.

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

[marble] [Bug 331312] Marble crashes when Importing Bookmarks

[Dennis Nienhüser]

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

Dennis Nienhüser  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Dennis Nienhüser  ---


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

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

[marble] [Bug 316969] crashed always when importing a bookmark file

[Dennis Nienhüser]

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

Dennis Nienhüser  changed:

   What|Removed |Added

 CC||begle...@gmail.com

--- Comment #7 from Dennis Nienhüser  ---
*** Bug 331312 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 373782] akonadi failed to append item

[John Salatas]

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

--- Comment #12 from John Salatas  ---
# mysqld-akonadi --version
/usr/sbin/mysqld  Ver 5.7.16-0ubuntu0.16.04.1 for Linux on x86_64 ((Ubuntu))
# dpkg -l mysql-server-core
dpkg-query: no packages found matching mysql-server-core
# dpkg -l | grep mysql-server-core
ii  mysql-server-core-5.7  
5.7.16-0ubuntu0.16.04.1 amd64MySQL database
server binaries
# 



However the issue is resolved after applying Bernhard Scheirle's suggestion in
Comment 3:

https://bugs.kde.org/show_bug.cgi?id=373782#c3

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

[kipiplugins] [Bug 374510] New: Creating albums on flickr with line breaks in their descriptions fails

[Richard Ash]

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

Bug ID: 374510
   Summary: Creating albums on flickr with line breaks in their
descriptions fails
   Product: kipiplugins
   Version: 5.4.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Flickr
  Assignee: kde-imag...@kde.org
  Reporter: rich...@audacityteam.org
  Target Milestone: ---

Created attachment 103177
  --> https://bugs.kde.org/attachment.cgi?id=103177=edit
Patch to remove new lines from album descriptions as well.

This is the same bug as #374442, but with photosets instead of photos. Patch
supplied to apply the same work-around as for #374442 for the moment.

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

[plasmashell] [Bug 373958] panel/taskmanager: constant "notifications" keep panel visible

[arne anka]

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

--- Comment #3 from arne anka  ---
(In reply to Kai Uwe Broulik from comment #1)
> you have a non-maximized panel, I suppose?

no, both panels are at maximum width

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

[Akonadi] [Bug 373782] akonadi failed to append item

[Luis Silva]

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

--- Comment #11 from Luis Silva  ---
Using KDE Neon Edition

> mysqld-akonadi --version
/usr/sbin/mysqld  Ver 5.7.16-0ubuntu0.16.04.1 for Linux on x86_64 ((Ubuntu))

> dpkg -s mysql-server-core-5.7 | grep -i version
Version: 5.7.16-0ubuntu0.16.04.1

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

[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance

[Riku Voipio]

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

--- Comment #8 from Riku Voipio  ---
(In reply to kdeu from comment #7)
> Are there any experiences whith using LMDB and NOSYNC?

Personally I've happily used that with patch attached since filing this bug -
except for a handful of upgrades when I forgot the patch, only to notice that
suddenly the disk light flashing means jittery UI again.

Baloo makes finding files from local HD almost as easy as finding public files
with google. It's really sad if people disable baloo because it's causing the
desktop freeze and stutter.

> Are there tools/ways to recover a corrupted database or lost transactions
> with LMDB? They might not even exist yet, if people don't use NOSYNC.

You are assuming that under current configuration LMDB can't get corrupted.
File systems are nasty and even with fdatasync there are caveats. But for most
users, sudden crashes (especially in middle of transactions) is really rare
events. 

Lost transactions are not a problem, entries would be just regenerated in next
index scanning. Recovering the DB is somewhat pointless - you can just
regenerate it from scratch, if under idle iopriority the indexing really has no
user impact.

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

[kdenlive] [Bug 374502] Problem with transparent output rendering

[Fred Périé]

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

--- Comment #2 from Fred Périé  ---
Thanks Jean-Baptiste, it is doing what I expected.

Maybe a word of explanation on 
https://kdenlive.org/project/timeline-track-compositing would be welcome.

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

[bugs.kde.org] [Bug 374500] New versions of Android are missing in the OS list

[Ben Cooksley]

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

Ben Cooksley  changed:

   What|Removed |Added

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

--- Comment #1 from Ben Cooksley  ---
Added as requested.

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

[kgpg] [Bug 374509] New: Kgpg crashes with segfault during initialization

[Andreas]

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

Bug ID: 374509
   Summary: Kgpg crashes with segfault during initialization
   Product: kgpg
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@opensource.sf-tec.de
  Reporter: hoheneg...@web.de
  Target Milestone: ---

Application: kgpg (16.12.0)

Qt Version: 5.7.0
Frameworks Version: 5.29.0
Operating System: Linux 4.4.0-57-generic x86_64
Distribution: KDE neon User Edition 5.8

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

- Custom settings of the application:
I have an existing directory .gnugpg with my configuration.
If I remove it the crash does not occur.

May be related to fixed bugs 373408 or 371410, but I have kgpg 16.12.0 from kde
neon.

The crash can be reproduced every time.

-- Backtrace:
Application: KGpg (kgpg), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5f333f6980 (LWP 7202))]

Thread 3 (Thread 0x7f5f21032700 (LWP 7213)):
#0  0x7f5f5111fb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5f4b48e39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5f4b48e4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5f51c6023b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5f51c0acea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f51a2ffb4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5f51a34b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5f4d97e6ba in start_thread (arg=0x7f5f21032700) at
pthread_create.c:333
#8  0x7f5f5112b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f5f293ca700 (LWP 7208)):
#0  0x7f5f5111fb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5f4b48e39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5f4b48e4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5f51c6023b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5f51c0acea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5f51a2ffb4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5f5686e7a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f5f51a34b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5f4d97e6ba in start_thread (arg=0x7f5f293ca700) at
pthread_create.c:333
#9  0x7f5f5112b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f5f333f6980 (LWP 7202)):
[KCrash Handler]
#6  std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at
/usr/include/c++/5/bits/atomic_base.h:396
#7  QAtomicOps::load (_q_value=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:103
#8  QBasicAtomicInteger::load (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:99
#9  QtPrivate::RefCount::ref (this=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:55
#10 QString::QString (other=..., this=0x1e5ddd0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:899
#11 KgpgCore::KgpgKeyPrivate::KgpgKeyPrivate (this=0x1e5dd70, id=...,
size=, trust=..., algo=..., subtype=..., keytype=...,
creationDate=..., curve=...) at /workspace/build/core/kgpgkey.cpp:178
#12 0x004372c9 in KgpgCore::KgpgKey::KgpgKey (this=0x7ffd223b1640,
id=..., size=1024, trust=..., algo=..., subtype=..., keytype=...,
creationDate=..., curve=...) at /workspace/build/core/kgpgkey.cpp:205
#13 0x004af366 in readSecretKeysProcess (p=...) at
/workspace/build/kgpginterface.cpp:347
#14 KgpgInterface::readSecretKeys (ids=...) at
/workspace/build/kgpginterface.cpp:415
#15 0x00440029 in KGpgRootNode::addKeys (this=0x1c0f130, ids=...) at
/workspace/build/core/KGpgRootNode.cpp:71
#16 0x00453b5c in KGpgItemModel::refreshAllKeys (this=0x1c10c40) at
/workspace/build/model/kgpgitemmodel.cpp:474
#17 0x00487620 in KeysManager::refreshkey (this=0x1bea100) at
/workspace/build/keysmanager.cpp:2648
#18 0x004e6f53 in KeysManager::qt_static_metacall (_o=0x1bea100,
_c=, _id=, _a=) at
/workspace/build/obj-x86_64-linux-gnu/moc_keysmanager.cpp:431
#19 0x7f5f51c38a19 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f5f5279c58b in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f5f528994cb in QMainWindow::event(QEvent*) () from

[kipiplugins] [Bug 374442] Exporting images with line breaks in their captions to flickr fails

[Richard Ash]

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

--- Comment #4 from Richard Ash  ---
I wondered if this was responsible for other people's issues. I've been using
the line-feed substitution as a work-around. Can confirm that the fix in Git
works for me.

What is annoying is that in 4.4.0 this worked fine, but I can't see any
relevant difference in the code, except that 4.4.0 used kurl instead of QUrl
and wasn't (I don't think) working in UTF-8.

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

[digikam] [Bug 374248] importing photo, bad file selector

[Maik Qualmann]

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

--- Comment #12 from Maik Qualmann  ---
Gilles,

Thanks, Happy New Year to you. You're right there is no way with Qt-5.7.0 to
recognize the desktop. I find another way.

Maik

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

[dolphin] [Bug 362439] dolphin crashed every time i copy ore move a file with acl's that is mounted over nfs3

[boospy]

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

--- Comment #7 from boospy  ---
Sorry for the delay. Some things are changed to the first post. Upgraded System
with the kubuntu-ppa. Versions are:

KDE Frameworks 5.28.0
Qt 5.6.1 (kompiliert gegen 5.6.1)
Dolphinversion: 4:16.04.3-0ubuntu1~ubuntu16.04~ppa62

The application does not crash anymore, but the errormessage is still existing,
and this is blocking an normal officeuser.
But the right ones are applied correctly when copying files. 

Thank you

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

[kipiplugins] [Bug 316719] New tool to export to jAlbum [patch]

[Andrew Goodbody]

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

Andrew Goodbody  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

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

[dolphin] [Bug 362439] dolphin crashed every time i copy ore move a file with acl's that is mounted over nfs3

[boospy]

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

--- Comment #6 from boospy  ---
Created attachment 103176
  --> https://bugs.kde.org/attachment.cgi?id=103176=edit
Log with Valgrind vers.2

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

[krusader] [Bug 374404] when copy in folder, free space info (in the upper left of panel Krusader) is not refreshed but Ctrl+R is refreshing it

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Alex Bikadorov  ---

Got it now. I simply had to copy a bigger file (2GB) to trigger the bug, my ssd
was too fast.

See https://phabricator.kde.org/D3938

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