[kwin] [Bug 372809] Moving or resizing windows with Alt key does not work when Caps Lock is enabled

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Martin Gräßlin  ---
unit test confirms the situation

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

[kwin] [Bug 372821] forward declaration of 'class KWin::KeyboardInputRedirection'

[Martin Gräßlin]

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

--- Comment #1 from Martin Gräßlin  ---
ShipIt.

I'm wondering how that could compile on my system

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

[plasmashell] [Bug 372804] After the suspend the rendering of the icons and windows on the desktop is not properly working.

[bugzilla_noreply]

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

giggi1...@yahoo.com changed:

   What|Removed |Added

 CC||giggi1...@yahoo.com

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

[plasmashell] [Bug 370605] Digital clock widget does not show anything

[Florian Röhrer]

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

--- Comment #11 from Florian Röhrer  ---
5.8.3 and the clock is still damaged. Could you please fix this?

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

[kwin] [Bug 372821] New: forward declaration of 'class KWin::KeyboardInputRedirection'

[Hrvoje Senjan]

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

Bug ID: 372821
   Summary: forward declaration of 'class
KWin::KeyboardInputRedirection'
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: hrvoje.sen...@gmail.com
  Target Milestone: ---

Created attachment 102403
  --> https://bugs.kde.org/attachment.cgi?id=102403=edit
Patch

Since 'Add tabbing to debug console...' or similar commit, compilation of KWin
is failing for openSUSE Leap (gcc 4.8.something).

[  297s]
/home/abuild/rpmbuild/BUILD/kwin-5.8.90git~20161122T144901~ad06476/debug_console.cpp:
In member function 'void KWin::DebugConsole::updateKeyboardTab()':
[  297s]
/home/abuild/rpmbuild/BUILD/kwin-5.8.90git~20161122T144901~ad06476/debug_console.cpp:585:35:
error: invalid use of incomplete type 'class KWin::KeyboardInputRedirection'
[  297s]  auto xkb = input()->keyboard()->xkb();
[  297s]^
[  297s] In file included from
/home/abuild/rpmbuild/BUILD/kwin-5.8.90git~20161122T144901~ad06476/debug_console.h:25:0,
[  297s]  from
/home/abuild/rpmbuild/BUILD/kwin-5.8.90git~20161122T144901~ad06476/debug_console.cpp:20:
[  297s]
/home/abuild/rpmbuild/BUILD/kwin-5.8.90git~20161122T144901~ad06476/input.h:44:7:
error: forward declaration of 'class KWin::KeyboardInputRedirection'
[  297s]  class KeyboardInputRedirection;
[  297s]^
[  298s] CMakeFiles/kwin.dir/build.make:272: recipe for target
'CMakeFiles/kwin.dir/debug_console.cpp.o' failed
[  298s] make[2]: *** [CMakeFiles/kwin.dir/debug_console.cpp.o] Error 1
[  298s] make[2]: *** Waiting for unfinished jobs


Attached patch resolves the problem.

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

[kmail2] [Bug 343275] [1] added at the end of a hyperlink

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

   Version Fixed In||5.29
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/kcor
   ||eaddons/e51bb2172e2d414347c
   ||136e96b103c3c305eac01
 Resolution|--- |FIXED

--- Comment #5 from Laurent Montel  ---
Git commit e51bb2172e2d414347c136e96b103c3c305eac01 by Montel Laurent.
Committed on 23/11/2016 at 07:07.
Pushed by mlaurent into branch 'master'.

Fix Bug 343275 - [1] added at the end of a hyperlink

FIXED-IN: 5.29

M  +5-0autotests/ktexttohtmltest.cpp
M  +6-0src/lib/text/ktexttohtml.cpp

http://commits.kde.org/kcoreaddons/e51bb2172e2d414347c136e96b103c3c305eac01

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

[kolourpaint] [Bug 252003] KolourPaint don't respect the EXIF orientation flag

[Martin Koller]

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

--- Comment #6 from Martin Koller  ---
On Tuesday 22 November 2016 22:47:31 you wrote:
> https://bugs.kde.org/show_bug.cgi?id=252003
> 
> --- Comment #5 from Christoph Feck  ---
> ... and http://doc-snapshots.qt.io/qt5-dev/qimagereader.html#setAutoTransform
> actually transforms (i.e. rotates) the image automatically, if set to true
> (this is false because of compatibility reasons).
> 
> There is no reason to hardcode EXIF support.

yes, I'll have a look

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

[kwin] [Bug 372796] Moving a windows to the left monitor makes it disappear outside of screen coordinates.

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||everm...@pc-portal.at

--- Comment #6 from Martin Gräßlin  ---
*** Bug 372796 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 372805] Compositor thinks Panel is on the secondary screen

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|kwin|plasmashell
  Component|multihead   |Task Manager
   Target Milestone|--- |1.0
 CC||mgraess...@kde.org,
   ||plasma-b...@kde.org
   Assignee|kwin-bugs-n...@kde.org  |h...@kde.org

--- Comment #1 from Martin Gräßlin  ---
The geometry where to minimize to is set by Plasma

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

[kwin] [Bug 372820] Errors caused by bleachbit

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
Please see:
https://blog.martin-graesslin.com/blog/2012/07/do-not-use-bleachbit/

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

[kwin] [Bug 372809] Moving or resizing windows with Alt key does not work when Caps Lock is enabled

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Flags||Wayland+
  Component|wayland-generic |input

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

[kwin] [Bug 372807] Key press is repeated when new xwayland client/window shows up

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---
fixed in XWayland 1.19

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

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

[Jan Grulich]

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

--- Comment #7 from Jan Grulich  ---
Hm, I didn't realize it was pushed to master only so it will be released with
Plasma 5.9, see bug 363917.

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

[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Martin Gräßlin  ---
Could you please provide a backtrace with debug symbols.

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

[kmailcvt] [Bug 362505] Crash when importing Evolution mails

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

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

--- Comment #2 from Laurent Montel  ---
I need more debug info as asked in comment1

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

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

[Joe]

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

--- Comment #6 from Joe  ---
Meant to update/comment - looks like it isn't in 5.8 - maybe its something for
5.9?

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

[digikam] [Bug 372684] No thumbnail shows for some files

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||5.4.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Component|Thumbnails  |Versioning

--- Comment #25 from caulier.gil...@gmail.com ---
No. This is the expected behavior of the Versioning options, as explained in
Setup dialog.

Gilles Caulier

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

[kwin] [Bug 372820] New: Errors caused by bleachbit

[Emilio Arteaga]

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

Bug ID: 372820
   Summary: Errors caused by bleachbit
   Product: kwin
   Version: 5.7.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: fluidoimpondera...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.27.0
Operating System: Linux 4.5.5-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
When I use a system cleanup application these errors occur, but without causing
serious discomfort. The name of this application is: BLEACHBIT

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Bus error
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f81ef0a9940 (LWP 1568))]

Thread 4 (Thread 0x7f81c700 (LWP 1638)):
#0  0x7f8201f9cbc0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f8207befbc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7f8207befc09 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7f8201f975ba in start_thread () from /lib64/libpthread.so.0
#4  0x7f81ff1127cd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f81d7fff700 (LWP 1627)):
#0  0x7f81ff108a23 in select () from /lib64/libc.so.6
#1  0x7f81fff096df in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /lib64/libQt5Core.so.5
#2  0x7f81fff0add4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /lib64/libQt5Core.so.5
#3  0x7f81fff0b30a in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f81ffebc5ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f81ffd1b343 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f8206e448f5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7f81ffd1f99a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f8201f975ba in start_thread () from /lib64/libpthread.so.0
#9  0x7f81ff1127cd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f81e64bd700 (LWP 1617)):
#0  0x7ffeec9c8c59 in clock_gettime ()
#1  0x7f81ff120d66 in clock_gettime () from /lib64/libc.so.6
#2  0x7f81ffdbbab3 in qt_gettime() () from /lib64/libQt5Core.so.5
#3  0x7f81fff0b869 in QTimerInfoList::updateCurrentTime() () from
/lib64/libQt5Core.so.5
#4  0x7f81fff0bc65 in QTimerInfoList::timerWait(timespec&) () from
/lib64/libQt5Core.so.5
#5  0x7f81fff0b2aa in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f81ffebc5ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7f81ffd1b343 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7f8201a98559 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#9  0x7f81ffd1f99a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 0x7f8201f975ba in start_thread () from /lib64/libpthread.so.0
#11 0x7f81ff1127cd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f81ef0a9940 (LWP 1568)):
[KCrash Handler]
#6  0x7f8200f36bea in
KSharedDataCache::Private::CacheLocker::CacheLocker(KSharedDataCache::Private
const*) () from /lib64/libKF5CoreAddons.so.5
#7  0x7f8200f2fb72 in KSharedDataCache::find(QString const&, QByteArray*)
const () from /lib64/libKF5CoreAddons.so.5
#8  0x7f81febf18f1 in KIconLoaderPrivate::findCachedPixmapWithPath(QString
const&, QPixmap&, QString&) () from /lib64/libKF5IconThemes.so.5
#9  0x7f81febf264a in KIconLoader::loadIcon(QString const&,
KIconLoader::Group, int, int, QStringList const&, QString*, bool) const () from
/lib64/libKF5IconThemes.so.5
#10 0x7f8207daefe0 in KWin::StartupFeedbackEffect::start(QString const&)
[clone .part.27] () from /lib64/libkwin4_effect_builtins.so.1
#11 0x7f8207dafc14 in
KWin::StartupFeedbackEffect::gotNewStartup(KStartupInfoId const&,
KStartupInfoData const&) () from /lib64/libkwin4_effect_builtins.so.1
#12 0x7f81ffee5b92 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#13 0x7f8200c934d7 in KStartupInfo::gotNewStartup(KStartupInfoId const&,
KStartupInfoData const&) () from /lib64/libKF5WindowSystem.so.5
#14 0x7f8200c9a39d in
KStartupInfo::Private::new_startup_info_internal(KStartupInfoId const&,
KStartupInfo::Data&, bool) () from /lib64/libKF5WindowSystem.so.5
#15 0x7f8200c9a52a in KStartupInfo::Private::got_startup_info(QString
const&, bool) () from /lib64/libKF5WindowSystem.so.5
#16 0x7f8200c9ad6a in KStartupInfo::Private::got_message(QString const&) ()
from /lib64/libKF5WindowSystem.so.5
#17 

[systemsettings] [Bug 358372] KDE System Settings Crashed applying changes to Trackpad configuration

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
What you describe is a different crash, see bug 346900.

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

[kwin] [Bug 372817] Kwin crashes when System Settings are opened

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
This might be fixed with Qt 5.7.1 or Qt 5.6.2.

As a workaround, use Breeze decoration.

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

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

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||andrew.lama...@gmail.com

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

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

[kdenlive] [Bug 372819] New: Speed effect not saved in project file

[bugzilla_noreply]

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

Bug ID: 372819
   Summary: Speed effect not saved in project file
   Product: kdenlive
   Version: 16.08.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: qubo...@gmail.com
  Target Milestone: ---

1. Add video clip (mp4) to timeline
2. Apply speed effect (no need to change parameters)
3. Save project
4. Restart Kdenlive
5. Load project

Expected:
1. Speed effect still applied

Actual:
2. Speed effect is missing

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

[kdenlive] [Bug 369585] Timeline corruption due to speed effect

[bugzilla_noreply]

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

qubo...@gmail.com changed:

   What|Removed |Added

 CC||qubo...@gmail.com

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

[kile] [Bug 372818] New: Closing livepreview before main screen keeps it closed forever

[bugzilla_noreply]

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

Bug ID: 372818
   Summary: Closing livepreview before main screen keeps it closed
forever
   Product: kile
   Version: 2.9.60
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: user interface
  Assignee: michel.lud...@kdemail.net
  Reporter: terce...@gmail.com
  Target Milestone: ---

When you close the livepreview before you close the main window, the
livepreview will not show up anymore after restarting kile.

Details:
I run KDE neon. I close the livepreview with the [X] in the titlebar of the
window.

Solution:
When you close the windows that way, it sets the following value in the kilerc
file:
ShowDocumentViewer=false

upon removing that line, the livepreview reappears on the next restart of kile

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

[digikam] [Bug 372684] No thumbnail shows for some files

[Rick]

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

--- Comment #24 from Rick  ---
Now anything else I can do to help?


On Tue, Nov 22, 2016 at 7:17 PM, Rick Hallock  wrote:

> That makes them show up! :)
>
>
> On Tue, Nov 22, 2016 at 2:50 PM, Maik Qualmann 
> wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=372684
>>
>> --- Comment #22 from Maik Qualmann  ---
>> Please enable this option for testing: Settings->Image
>> Editor->Versioning->Always show original images
>>
>> Maik
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>>
>
>
>
> --
>
> Thanks
> Rick
>

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

[Discover] [Bug 372811] Discover Crash

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

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

--- Comment #1 from Aleix Pol  ---
Needs a new release upstream in libappstream.

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

[digikam] [Bug 372684] No thumbnail shows for some files

[Rick]

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

--- Comment #23 from Rick  ---
That makes them show up! :)


On Tue, Nov 22, 2016 at 2:50 PM, Maik Qualmann 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=372684
>
> --- Comment #22 from Maik Qualmann  ---
> Please enable this option for testing: Settings->Image
> Editor->Versioning->Always show original images
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[kwin] [Bug 372817] New: Kwin crashes when System Settings are opened

[bugzilla_noreply]

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

Bug ID: 372817
   Summary: Kwin crashes when System Settings are opened
   Product: kwin
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: andrew.lama...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.10-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Sometimes Kwin will crash when I open System Settings from the Application
Menu. Sometimes it'll crash when I open a specific setting. But not always...

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f23f631a840 (LWP 816))]

Thread 6 (Thread 0x7f23d3fff700 (LWP 1345)):
#0  0x7f23f5d58551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f23f3405ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f23f34073b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f23f33b423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f23f31d70f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f23edd4d2d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f23f31dbd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f23eefef454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f23f5d617df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f23be779700 (LWP 923)):
#0  0x7f23eeff510f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f23f234bac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f23f234bb09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f23eefef454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f23f5d617df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f23d35de700 (LWP 913)):
#0  0x7f23f5d58551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f23f3405ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f23f34073b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f23f33b423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f23f31d70f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f23edd4d2d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f23f31dbd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f23eefef454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f23f5d617df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f23d9d8c700 (LWP 864)):
#0  0x7f23f5d58551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f23f3405ac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f23f34073b8 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f23f33b423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f23f31d70f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f23ecf17e55 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f23f31dbd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f23eefef454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f23f5d617df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f23dbcad700 (LWP 843)):
#0  0x7f23f5d5848d in poll () at /usr/lib/libc.so.6
#1  0x7f23f4e988e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f23f4e9a679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f23dc759449 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f23f31dbd78 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f23eefef454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f23f5d617df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f23f631a840 (LWP 816)):
[KCrash Handler]
#6  0x7f23edd38810 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/usr/lib/libQt5Qml.so.5
#7  0x7f23edd39775 in
QQmlBinding::update(QFlags) () at
/usr/lib/libQt5Qml.so.5
#8  0x7f23edd43405 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f23edccc27e in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) () at /usr/lib/libQt5Qml.so.5
#10 0x7f23edccc347 in QQmlComponentPrivate::completeCreate() () at
/usr/lib/libQt5Qml.so.5
#11 0x7f23edccc1b0 in QQmlComponent::create(QQmlContext*) () at
/usr/lib/libQt5Qml.so.5
#12 0x7f23d80a3cfd in  () at
/usr/lib/qt/plugins/org.kde.kdecoration2/kwin5_aurorae.so
#13 0x7f23f597661a in  () at /usr/lib/libkwin.so.5
#14 0x7f23f583d7b2 in KWin::Client::createDecoration(QRect const&) () at

[konsole] [Bug 372766] Konsole stucks lastly opened directory when opening a new instance even explicitly set otherwise

[Ongun Kanat]

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

--- Comment #2 from Ongun Kanat  ---
Will take a look at it.

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

[plasmashell] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8

[Andrius Štikonas]

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

Andrius Štikonas  changed:

   What|Removed |Added

   Version Fixed In||5.8.4
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from Andrius Štikonas  ---
Yeah, I also don't have any problems for quite some time (I was using 5.8.3
with relevant patches backported). I guess let's close this bug.

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

[Discover] [Bug 372404] plasma-discover crashes on Kubuntu 16.10

[Matt Z .]

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

--- Comment #6 from Matt Z.  ---
a little more info (in addition to above)...

a fresh install
- nothing added
- compositor turned off

with 'nomodeset' xrand shows vga display at 1024x768 -- discover works fine
without nomodeset xrand shows LVDS1 at 1280x800 -- discover will not run

HTH

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

[yakuake] [Bug 372816] "Manage Profiles" options don't work

[bugzilla_noreply]

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

kadircance...@gmail.com changed:

   What|Removed |Added

Summary|Manage Profiles don't work  |"Manage Profiles" options
   ||don't work

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

[yakuake] [Bug 372816] New: Manage Profiles don't work

[bugzilla_noreply]

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

Bug ID: 372816
   Summary: Manage Profiles don't work
   Product: yakuake
   Version: 3.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: kadircance...@gmail.com
  Target Milestone: ---

QMetaObject::invokeMethod: No such method
Konsole::Part::showManageProfilesDialog(QWidget*)

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

[plasmashell] [Bug 372815] New: Plasma crashes because of the Launcher

[Bugskde]

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

Bug ID: 372815
   Summary: Plasma crashes because of the Launcher
   Product: plasmashell
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugskderep...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
when I enter some characters in the Launcher to search some Software, it works
well. However, If I press backspace to delete some characters I inputed just
now, it crashes.
- Custom settings of the application:
The Launcher is in default setting.

The crash can be reproduced every time.

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

Thread 16 (Thread 0x7f62deffd700 (LWP 2738)):
#0  0x7f63cc7680af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63cd64f65b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f631868542f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f6318688dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f6318686a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f63cd64e9e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f63cc763734 in start_thread () at /lib64/libpthread.so.0
#8  0x7f63ccf62d3d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f62df7fe700 (LWP 2737)):
#0  0x7f63cc7680af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63cd64f65b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f631868542f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f6318688dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f6318688e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f6318688e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f6318688e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f6318688e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f6318688e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7f6318688e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7f6318686a46 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7f63cd64e9e9 in  () at /usr/lib64/libQt5Core.so.5
#19 0x7f63cc763734 in start_thread () at /lib64/libpthread.so.0
#20 0x7f63ccf62d3d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f62d700 (LWP 2736)):
#0  0x7f63cc7680af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f63cd64f65b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f631868542f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7f6318688dea in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f6318688e32 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f631868345b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, 

[kontact] [Bug 368316] Kontact crashes often after minutes of running

[Andrei Slavoiu]

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

Andrei Slavoiu  changed:

   What|Removed |Added

 CC||ansl...@yahoo.com

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

[kontact] [Bug 368316] Kontact crashes often after minutes of running

[Andrei Slavoiu]

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

--- Comment #1 from Andrei Slavoiu  ---
Created attachment 102400
  --> https://bugs.kde.org/attachment.cgi?id=102400=edit
New crash information added by DrKonqi

kontact (4.14.10) on KDE Platform 4.14.26 using Qt 4.8.7

- What I was doing when the application crashed:

Just rebooted my computer and as soon as akregator refreshed the feeds it
crashed

-- Backtrace (Reduced):
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:35
#7  0x7f097021648f in c4_Column::CopyData (this=this@entry=0x14f3f1b8,
to_=to_@entry=15278080, from_=from_@entry=15282176, count_=190) at
/usr/src/debug/kde-apps/akregator-4.14.11_pre20160211/akregator-4.14.11_pre20160211/akregator/plugins/mk4storage/metakit/src/column.cpp:304
#8  0x7f0970216bd7 in c4_Column::Grow (this=0x14f3f1b8, off_=, diff_=diff_@entry=99) at
/usr/src/debug/kde-apps/akregator-4.14.11_pre20160211/akregator-4.14.11_pre20160211/akregator/plugins/mk4storage/metakit/src/column.cpp:555
#9  0x7f097021ddde in c4_FormatB::SetOne (this=0x14f3f1a0, index_=5654,
xbuf_=..., ignoreMemos_=ignoreMemos_@entry=false) at
/usr/src/debug/kde-apps/akregator-4.14.11_pre20160211/akregator-4.14.11_pre20160211/akregator/plugins/mk4storage/metakit/src/format.cpp:607
#10 0x7f097021e7f9 in c4_FormatS::Set (this=,
index_=, buf_=...) at
/usr/src/debug/kde-apps/akregator-4.14.11_pre20160211/akregator-4.14.11_pre20160211/akregator/plugins/mk4storage/metakit/src/format.cpp:862

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

[kate] [Bug 372814] New: Kate crashed after closing it (happend only once)

[Gregor Mi]

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

Bug ID: 372814
   Summary: Kate crashed after closing it (happend only once)
   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: codestr...@posteo.org
  Target Milestone: ---

Application: kate (16.08.3)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: Open kate, use the git context
menu (don't know if this is related to the crash), close kate. This crash
appears.

The crash does not seem to be reproducible.

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

Thread 2 (Thread 0x7f85887a7700 (LWP 15947)):
#0  0x7f859170bccd in read () at /lib64/libc.so.6
#1  0x7f858c304b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f858c2c3999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f858c2c3df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f858c2c3f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f85923169cc in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f8588c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#6  0x7f85922c62db in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f85887a6e20, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#7  0x7f859210bfca in QThread::exec() (this=this@entry=0x7f8592993d00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#8  0x7f859272ca25 in QDBusConnectionManager::run() (this=0x7f8592993d00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#9  0x7f85921107f9 in QThreadPrivate::start(void*) (arg=0x7f8592993d00
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#10 0x7f858e1370a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7f859171802d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f859703c780 (LWP 15946)):
[KCrash Handler]
#6  0x03816b50 in  ()
#7  0x7f857e8b315e in  () at /usr/lib64/libKF5Notifications.so.5
#8  0x7f857e8b31f9 in  () at /usr/lib64/libKF5Notifications.so.5
#9  0x7f85922eee35 in QObjectPrivate::deleteChildren()
(this=this@entry=0x3049500) at kernel/qobject.cpp:1970
#10 0x7f85922f83ae in QObject::~QObject() (this=,
__in_chrg=) at kernel/qobject.cpp:1041
#11 0x7f857e897029 in  () at /usr/lib64/libKF5Notifications.so.5
#12 0x7f859166ab39 in __run_exit_handlers () at /lib64/libc.so.6
#13 0x7f859166ab85 in  () at /lib64/libc.so.6
#14 0x7f8591654b2c in __libc_start_main () at /lib64/libc.so.6
#15 0x00448ef7 in _start ()

Reported using DrKonqi

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

[kolourpaint] [Bug 252003] KolourPaint don't respect the EXIF orientation flag

[Christoph Feck]

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

--- Comment #5 from Christoph Feck  ---
... and http://doc-snapshots.qt.io/qt5-dev/qimagereader.html#setAutoTransform
actually transforms (i.e. rotates) the image automatically, if set to true
(this is false because of compatibility reasons).

There is no reason to hardcode EXIF support.

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

[krita] [Bug 372800] [Windows 10] Cursor Offset - Surface Pro 1 - Latest Wacom Drivers

[Don]

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

--- Comment #2 from Don  ---
with the noted wacom pen options off both Wintab and QT resolution options in
the Krita tablet dialog produce correct cursor locations also.

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

[krita] [Bug 372800] [Windows 10] Cursor Offset - Surface Pro 1 - Latest Wacom Drivers

[Don]

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

Don  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

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

[cantor] [Bug 372676] julia backend doesn't build

[Antonio Rojas]

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

--- Comment #3 from Antonio Rojas  ---
Yes, the patch fixes the build (with and without building tests)

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

[krita] [Bug 372800] [Windows 10] Cursor Offset - Surface Pro 1 - Latest Wacom Drivers

[Don]

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

--- Comment #1 from Don  ---
turning off both "quick note on lock screen" and "show ripple effect" in the
Wacom pen options dialog in windows and also manually specifying my screen
resolution in the Krita tablet dialog clears up the offset on my end.

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

[cantor] [Bug 372676] julia backend doesn't build

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Attachment #102398|0   |1
is obsolete||

--- Comment #2 from Christoph Feck  ---
Created attachment 102399
  --> https://bugs.kde.org/attachment.cgi?id=102399=edit
Proposed patch

(updated to respect the BUILD_TESTING variable)

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

[cantor] [Bug 372676] julia backend doesn't build

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Created attachment 102398
  --> https://bugs.kde.org/attachment.cgi?id=102398=edit
Proposed patch

Could you please test attached patch? I have neither 'julia' nor 'python3'
installed.

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

[plasmashell] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8

[kafei]

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

--- Comment #4 from kafei  ---
This bug appears fixed on my end in 5.8.4, I rebooted a few times and got my
correct monitor configuration every time.

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

[dolphin] [Bug 372813] New: "Invalid protocol" message on tilde (~) prefixed non-existent directory

[Gregor Mi]

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

Bug ID: 372813
   Summary: "Invalid protocol" message on tilde (~) prefixed
non-existent directory
   Product: dolphin
   Version: 15.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: bars: location
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: codestr...@posteo.org
  Target Milestone: ---

SETUP:
In my home directory there is a tmp folder (~/tmp).

ACTION:
When I paste the existing path "~/tmp" (without the quotes) to the address bar
and hit Enter, dolphin navigates to the address. Which is fine.

When I paste a non-existing path "~/tmp/nonext" (without the quotes) to the
address bar and hit Enter, dolphin shows the "Invalid protocol" message. This
is confusing because it only happens when the path is prefixed with the tilde.

EXPECTED:
Dolphin should show the "The file or folder ... does not exist." message as it
does when the non-existing path "/home/g/tmp/nonext" (without tilde) is
entered.

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

[plasmashell] [Bug 372812] New: Changing the volume with the wheel switches open windows

[Carlos]

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

Bug ID: 372812
   Summary: Changing the volume with the wheel switches open
windows
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: carlosmp1...@gmail.com
  Target Milestone: 1.0

After the update to 5.8.4, using the mouse wheel over the sound applet in the
tray to change the volume also switches open windows (I'm using the icon-only
task manager).

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

[krusader] [Bug 372802] No way to know if two folders are synchred ("synchron folder changes")

[Rafael]

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

Rafael  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael  ---
Ok, that's valid. Thank you.

Anyway, is a pity that functionality is so "hidden". IMHO it should available
on "Menu bar" too ...  ;)

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

[plasmashell] [Bug 360862] Settings -> Wallpaper: Switch from one declarative wallpaper to another does not work directly

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

Summary|Settings -> Wallpaper:  |Settings -> Wallpaper:
   |Switch from declarative |Switch from one declarative
   |wallpaper to another does   |wallpaper to another does
   |not work directly   |not work directly

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

[plasmashell] [Bug 360862] Settings -> Wallpaper: Switch from declarative wallpaper to another does not work directly

[Gregor Mi]

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

Gregor Mi  changed:

   What|Removed |Added

Summary|Settings -> Wallpaper:  |Settings -> Wallpaper:
   |Switch from Hunyango to |Switch from declarative
   |Haenau does not work|wallpaper to another does
   |directly|not work directly

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

[Discover] [Bug 372811] New: Discover Crash

[Paul WOISARD]

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

Bug ID: 372811
   Summary: Discover Crash
   Product: Discover
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: paulwois...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.10-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
I download and install a new application in Discover and when the application
installed Discover crash.
The bug is just for new applications, there is not any problem with update.

The crash can be reproduced every time.

-- Backtrace:
Application: Découvrir (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f38c5bd17c0 (LWP 2283))]

Thread 14 (Thread 0x7f3880a27700 (LWP 2312)):
#0  0x7f38bca8676a in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f38bca88c2b in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f38bca896ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f38bca8989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f38c234c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f38c22f623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f38c21190f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f38c211dd78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f38be76e454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f38c172f7df in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f3883de4700 (LWP 2299)):
#0  0x7f38c17224ed in read () at /usr/lib/libc.so.6
#1  0x7f38bcacda10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f38bca89235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f38bca89724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f38bca89b12 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#5  0x7f3885994316 in  () at /usr/lib/libgio-2.0.so.0
#6  0x7f38bcab10d5 in  () at /usr/lib/libglib-2.0.so.0
#7  0x7f38be76e454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f38c172f7df in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f38845e5700 (LWP 2298)):
#0  0x7f38c172648d in poll () at /usr/lib/libc.so.6
#1  0x7f38bca89786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f38bca8989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f38bca898e1 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f38bcab10d5 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f38be76e454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f38c172f7df in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f3895ffb700 (LWP 2293)):
#0  0x7f38bcacedb9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f38bca8976b in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f38bca8989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f38c234c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f38c22f623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f38c21190f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f38c211dd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f38be76e454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f38c172f7df in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f38967fc700 (LWP 2292)):
#0  0x7f38c172648d in poll () at /usr/lib/libc.so.6
#1  0x7f38bca89786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f38bca8989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f38c234c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f38c22f623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f38c21190f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f38c51b3856 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7f38c211dd78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f38be76e454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f38c172f7df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f38978d0700 (LWP 2291)):
#0  0x7f38be77410f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f38a1dcc48b in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7f38a1dcc2e7 in  () at /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7f38be76e454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f38c172f7df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f38980d1700 (LWP 2290)):
#0  0x7f38be77410f in pthread_cond_wait@@GLIBC_2.3.2 () at

[kdeconnect] [Bug 370890] Media control screen is cut off on smaller devices when cover art is present

[MathB]

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

--- Comment #3 from MathB  ---
I just made a fix as a Pull Request on the github mirror :
https://github.com/albertvaka/kdeconnect-android/pull/11

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

[plasmashell] [Bug 372810] New: [Plasma crash] after uninstalling program, but launching it via K-menu (Kicker)

[bugzilla_noreply]

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

Bug ID: 372810
   Summary: [Plasma crash] after uninstalling program, but
launching it via K-menu (Kicker)
   Product: plasmashell
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: opensuse.lietuviu.ka...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

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

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

I uninstalled GUI program. Few seconds ago I opened KDE menu (kicker), I still
see that program, I click it. Dialog opens and ask, if I want to execute file.
After I accept, Plasma crash.

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

Thread 8 (Thread 0x7f0c9172b700 (LWP 18867)):
#0  0x7f0d5567249d in poll () from /lib64/libc.so.6
#1  0x7f0d51d3a314 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f0c8c0048d0, timeout=2330892, context=0x7f0c8c000990) at gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f0c8c000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3835
#3  0x7f0d51d3a42c in g_main_context_iteration (context=0x7f0c8c000990,
may_block=1) at gmain.c:3901
#4  0x7f0d55f7e32b in QEventDispatcherGlib::processEvents
(this=0x7f0c8c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f0d55f2bfdb in QEventLoop::exec (this=this@entry=0x7f0c9172ac90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f0d55d66f1a in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f0c92b538f7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#8  0x7f0d55d6b9e9 in QThreadPrivate::start (arg=0x4418a60) at
thread/qthread_unix.cpp:341
#9  0x7f0d54e7b734 in start_thread () from /lib64/libpthread.so.0
#10 0x7f0d5567ad3d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f0ca36ca700 (LWP 18850)):
#0  0x7f0d5567249d in poll () from /lib64/libc.so.6
#1  0x7f0d51d3a314 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f0c9c003120, timeout=-1, context=0x7f0c9c000990) at gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f0c9c000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3835
#3  0x7f0d51d3a42c in g_main_context_iteration (context=0x7f0c9c000990,
may_block=1) at gmain.c:3901
#4  0x7f0d55f7e32b in QEventDispatcherGlib::processEvents
(this=0x7f0c9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f0d55f2bfdb in QEventLoop::exec (this=this@entry=0x7f0ca36c9c70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f0d55d66f1a in QThread::exec (this=this@entry=0x1855780) at
thread/qthread.cpp:500
#7  0x7f0d59bf5632 in QQuickPixmapReader::run (this=0x1855780) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/util/qquickpixmapcache.cpp:817
#8  0x7f0d55d6b9e9 in QThreadPrivate::start (arg=0x1855780) at
thread/qthread_unix.cpp:341
#9  0x7f0d54e7b734 in start_thread () from /lib64/libpthread.so.0
#10 0x7f0d5567ad3d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f0cb33ee700 (LWP 18849)):
#0  0x7f0d5566e51d in read () from /lib64/libc.so.6
#1  0x7f0d51d7a670 in read (__nbytes=16, __buf=0x7f0cb33edab0,
__fd=) at /usr/include/bits/unistd.h:44
#2  g_wakeup_acknowledge (wakeup=0x7f0d38002390) at gwakeup.c:210
#3  0x7f0d51d39e49 in g_main_context_check
(context=context@entry=0x7f0cac000990, max_priority=2147483647,
fds=fds@entry=0x7f0cac003070, n_fds=n_fds@entry=1) at gmain.c:3632
#4  0x7f0d51d3a2a8 in g_main_context_iterate
(context=context@entry=0x7f0cac000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3837
#5  0x7f0d51d3a42c in g_main_context_iteration (context=0x7f0cac000990,
may_block=1) at gmain.c:3901
#6  0x7f0d55f7e32b in QEventDispatcherGlib::processEvents
(this=0x7f0cac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#7  0x7f0d55f2bfdb in QEventLoop::exec (this=this@entry=0x7f0cb33edcb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7f0d55d66f1a in QThread::exec (this=this@entry=0x1103260) at
thread/qthread.cpp:500
#9  0x7f0d590729b8 in QQmlThreadPrivate::run (this=0x1103260) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/qml/qml/ftw/qqmlthread.cpp:141
#10 0x7f0d55d6b9e9 in QThreadPrivate::start (arg=0x1103260) at
thread/qthread_unix.cpp:341
#11 0x7f0d54e7b734 

[apper] [Bug 344358] Search groups not supported by backend.

[SBB]

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

SBB  changed:

   What|Removed |Added

 CC||senorblackb...@gmail.com

--- Comment #2 from SBB  ---
DUP of 341902

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

[digikam] [Bug 372684] No thumbnail shows for some files

[Maik Qualmann]

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

--- Comment #22 from Maik Qualmann  ---
Please enable this option for testing: Settings->Image
Editor->Versioning->Always show original images

Maik

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

[kmymoney4] [Bug 368190] "Update Stock and Currency Prices" doesn't work when base currency is South Korean Won(KRW)

[bugzilla_noreply]

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

--- Comment #2 from shiz...@teksavvy.com ---
Workaround:

I use "yahoo currency" to retrieve the quotes.

Changing the default URL in "configure -> kmymoney -> online quotes -> yahoo
currency" from "http://finance.yahoo.com/d/quotes.csv?s=%1%2=X=sl1d1; to
"http://finance.yahoo.com/d/quotes.csv?s=%1CAD=X=sl1d1; fixed the Canadian
dollar issue.

I imagine for the south korean won that
"http://finance.yahoo.com/d/quotes.csv?s=%1KRW=X=sl1d1; would do the trick as
well.

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

[kwin] [Bug 372809] New: Moving or resizing windows with Alt key does not work when Caps Lock is enabled

[Kai Uwe Broulik]

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

Bug ID: 372809
   Summary: Moving or resizing windows with Alt key does not work
when Caps Lock is enabled
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@privat.broulik.de
  Target Milestone: ---

When Caps Lock is enabled, I cannot move or resize windows with Alt + Left
click or right click.

1.) Press Caps Lock so it is on
2.) Try to move a window by pressing and holding Alt while dragging the mouse

Moreover, it tends to get confused about keyboard state when I do this. I now
type in lower caps although caps lock light is on but I cannot move windows
around. Now I press Caps Lock again, light is off, I type in all caps and I can
move windows. (affects both X and wayland clients)

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

[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||mgraess...@kde.org

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

[KScreen] [Bug 372557] Plasma/XRandR detects not existing monitor

[Piotr Mierzwinski]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

Version|5.8.3   |5.8.4

--- Comment #7 from Piotr Mierzwinski  ---
Unfortunately, but this is still persist. I made very simple test.
1. I created new user like this: useradd piot1 -m -s /bin/bash
(inside his home directory were only couple scripts)
2. Restarted lightdm (to be able to see new user)
3. Logged in to Plasma
In effect I get empty desktop (no any bar) with default wallpaper. After couple
minutes I realized that it might be different "not existing" screen. I run
systemsettings (Alt+F2 worked) and checked Display and Monitors settings.
Wasn't surprise what I saw. Two screens on preview (eDP1 and DP1) and in option
"Main display" set "Laptop screen". This is explains everything.

Anyway in my opinion Plasma still detects, in some way, not existing screen in
my hardware. I have only one monitor hooked to my desktop.

When I manually fix this issue, so:
- update below section of ~/config/plasmashellrc like below
[ScreenConnectors]
0=DP1
1=eDP1
- remove section describing not existing display from config file located in
~/.local/share/kscreen
- remove ~/.cache
- restart
After login I get desktop with default wallpaper (default panel exists, but no
plasmoids). Now  when I try to add new plasmoid, so when I chose option "Add
new element of interface" (RMB of desktop - BTW. I don't have "Folder View")
then magically old wallpaper back, also plasmoids back. After next login I get
desktop what looks good. All would be fine, only one annoying issue happens. I
mean, when I add any plasmoid and try to move it to different position, it just
disappears. In this moment in plasmoids selector I have two the same plasmoid
used (number 2 in corner of its icon), but they are not visible.

Could you please check reported issue.


My software:
  Plasma 5.8.4  (kscreen 3.8.4), KF-5.28
  xf86-video-intel 1:2.99.917+730+gdad64e9-1
  kernel 4.8.10-ARCH
My hardware:
  Processor:   Skylake Intel i7-6700 and graphics HD 530 (GT2)
  Motherboard: Asus H170M-PLUS


content of ~/config/plasmashellrc please find below (as you can see not
existing eDP1 is placed on first position):

[PlasmaViews][Panel 3][Horizontal1680]
thickness=36

[ScreenConnectors]
0=eDP1
1=DP1

[Updates]
performed=/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/obsolete_kickoffrc.js

I attached also kscreen configuration created after Plasma first run on new
user.

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

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

[Philippe Waroquiers]

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

--- Comment #14 from Philippe Waroquiers  ---
(In reply to Carl Ponder from comment #13)
> Given that there's junk in the array, I know that the contents aren't being
> zero'd out, and the PGI people confirm that -Mstack_arrays are not
> initialized. How does valgrind recognize that an array is being initialized
> under the circumstances? Is it following the control-flow
> instruction-by-instruction?

For Arrays allocated on the heap, the memory is marked uninitialised
when allocated.

For Arrays on the stack (more generally for all stacks variables),
the vars are marked as uninitialised when the stack pointer is decreased
to create the frame.

So, what might happen maybe with the fortran coompiler is that
they do not decrease/increase the SP for each function call
and/or for each scope 
or whatever.

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

[krusader] [Bug 354503] Krusader adds space at the beginning of some files/dirs while ftp to AIX FTP servers, which makes it unable to enter these directories

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

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

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

cannot test. Don't know if it Krusader related

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

[kwin] [Bug 363750] KWin uses "para" instead of "p" on some QLabel's

[Frederik Schwarzer]

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

--- Comment #12 from Frederik Schwarzer  ---
SVN commit 1475453 by schwarzer:

Fix tags in translation.


 M  +5 -5  ki18n5.po  


WebSVN link: http://websvn.kde.org/?view=rev=1475453

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

[KScreen] [Bug 372557] Plasma/XRandR detects not existing monitor

[Piotr Mierzwinski]

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

--- Comment #6 from Piotr Mierzwinski  ---
Created attachment 102397
  --> https://bugs.kde.org/attachment.cgi?id=102397=edit
kscreen configuration

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

[konsole] [Bug 372808] New: Konsole crashed while editinig file with VIM

[Marcelo]

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

Bug ID: 372808
   Summary: Konsole crashed while editinig file with VIM
   Product: konsole
   Version: 16.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: open.contact...@gmail.com
  Target Milestone: ---

Application: konsole (16.08.1)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.10-100.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
I had several tabs open over 2 windows, but all were idle while I edited a text
document with VIM. When selecting a word (double click over the word for a
select/paste operation), the console immediately crashed.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe321ebf900 (LWP 2587))]

Thread 2 (Thread 0x7fe315ccc700 (LWP 2590)):
#0  0x7fe32ed8db7d in poll () at /lib64/libc.so.6
#1  0x7fe32ad7318c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7fe32ad7329c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7fe32fb82b5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7fe32fb3325a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7fe32f993bd4 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7fe334cd5675 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7fe32f99800c in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7fe32d55c61a in start_thread () at /lib64/libpthread.so.0
#9  0x7fe32ed995fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fe321ebf900 (LWP 2587)):
[KCrash Handler]
#6  0x7fe32eccba28 in raise () at /lib64/libc.so.6
#7  0x7fe32eccd62a in abort () at /lib64/libc.so.6
#8  0x7fe32ed0edea in  () at /lib64/libc.so.6
#9  0x7fe32ed15c08 in malloc_consolidate () at /lib64/libc.so.6
#10 0x7fe32ed18556 in _int_malloc () at /lib64/libc.so.6
#11 0x7fe32ed1a430 in malloc () at /lib64/libc.so.6
#12 0x7fe32f998a12 in QArrayData::allocate(unsigned long, unsigned long,
unsigned long, QFlags) () at
/lib64/libQt5Core.so.5
#13 0x7fe32fa164f3 in QString::QString(int, Qt::Initialization) () at
/lib64/libQt5Core.so.5
#14 0x7fe32fb89f56 in QUtf8::convertToUnicode(char const*, int,
QTextCodec::ConverterState*) () at /lib64/libQt5Core.so.5
#15 0x7fe32fb8a695 in QUtf8Codec::convertToUnicode(char const*, int,
QTextCodec::ConverterState*) const () at /lib64/libQt5Core.so.5
#16 0x7fe32fa8e8bd in QTextStreamPrivate::fillReadBuffer(long long) () at
/lib64/libQt5Core.so.5
#17 0x7fe32fa8f51c in QTextStreamPrivate::scan(QChar const**, int*, int,
QTextStreamPrivate::TokenDelimiter) () at /lib64/libQt5Core.so.5
#18 0x7fe32fa90685 in QTextStream::readLineInto(QString*, long long) () at
/lib64/libQt5Core.so.5
#19 0x7fe32fa908fe in QTextStream::readLine(long long) () at
/lib64/libQt5Core.so.5
#20 0x7fe3347120b6 in LinuxProcessInfo::readProcInfo(int) () at
/lib64/libkonsoleprivate.so.16
#21 0x7fe33470c9cc in Konsole::UnixProcessInfo::readProcessInfo(int, bool)
() at /lib64/libkonsoleprivate.so.16
#22 0x7fe33472cd1e in Konsole::Session::updateForegroundProcessInfo() () at
/lib64/libkonsoleprivate.so.16
#23 0x7fe33472dde5 in Konsole::Session::getProcessInfo() () at
/lib64/libkonsoleprivate.so.16
#24 0x7fe33472df9a in Konsole::Session::getDynamicTitle() () at
/lib64/libkonsoleprivate.so.16
#25 0x7fe334737fb3 in Konsole::SessionController::snapshot() () at
/lib64/libkonsoleprivate.so.16
#26 0x7fe32fb5bb1e in QMetaObject::activate(QObject*, int, int, void**) ()
at /lib64/libQt5Core.so.5
#27 0x7fe32fb67b98 in QTimer::timerEvent(QTimerEvent*) () at
/lib64/libQt5Core.so.5
#28 0x7fe32fb5c82b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#29 0x7fe33065910c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#30 0x7fe33065e646 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#31 0x7fe32fb343ea in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#32 0x7fe32fb820a3 in QTimerInfoList::activateTimers() () at
/lib64/libQt5Core.so.5
#33 0x7fe32fb82611 in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() at /lib64/libQt5Core.so.5
#34 0x7fe32ad72e5a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#35 0x7fe32ad731f0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#36 0x7fe32ad7329c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#37 0x7fe32fb82b5b in

[krusader] [Bug 371893] segfault in qt lib after a while when copying/moving files

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
   Severity|grave   |crash
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #2 from Alex Bikadorov  ---

need *a bit* more informations

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

[kwin] [Bug 372807] New: Key press is repeated when new xwayland client/window shows up

[Kai Uwe Broulik]

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

Bug ID: 372807
   Summary: Key press is repeated when new xwayland client/window
shows up
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@privat.broulik.de
  Target Milestone: ---

I haven't fully figured this out yet but when I press a keyboard shortcut such
as Ctrl+N in a Chrome window, I end up opening multiple windows if I'm not
careful to press the key only very briefly. Something similar happens in
Kolourpaint:
1.) open kolurpaint4
2.) double click a color in the palette and change a color there
3.) close kolourpaint window
-> it will wask for whether you want to save
4.) press Tab so the "Discard" button is focused (mnemonic Alt+D is
unfortunately taken by Show desktop)
5.) Now hit return
It will suddenly popup a "Save Palette As" window, as by pressing return we
accidentally confirmed the subsequent confirmation whether we want to save the
custom palette to a file.

Another simpler way I just discovered is:
1.) start kwrite with platform xcb
2.) Press and hold Ctrl+N
-> you'll spawn a ton of new windows

If you do the same in kwrite with wayand, one single new window will appear and
the shortcut won't trigger endlessly.

(Don't tell me this is yet again an Xwayland 1.18 issue :(

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

[kdenlive] [Bug 372668] Render a clip results in a black video with any of the available file formats.

[Wegwerf]

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

Wegwerf  changed:

   What|Removed |Added

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

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

[kopete] [Bug 229526] "The contact X has added you to his/her contact list" always appears on startup

[Pali Rohár]

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

Pali Rohár  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

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

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

[Carl Ponder]

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

--- Comment #13 from Carl Ponder  ---
Given that there's junk in the array, I know that the contents aren't being
zero'd out, and the PGI people confirm that -Mstack_arrays are not initialized.
How does valgrind recognize that an array is being initialized under the
circumstances? Is it following the control-flow instruction-by-instruction?

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

[kwave] [Bug 372806] new feature: collapse/expand of track views

[Thomas Eschenbacher]

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

Thomas Eschenbacher  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Priority|NOR |VLO
 Status|UNCONFIRMED |CONFIRMED

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

[kwave] [Bug 372806] New: new feature: collapse/expand of track views

[Thomas Eschenbacher]

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

Bug ID: 372806
   Summary: new feature: collapse/expand of track views
   Product: kwave
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: thomas.eschenbac...@gmx.de
  Reporter: thomas.eschenbac...@gmx.de
  Target Milestone: ---

add a small (+) icon to expand/collapse track views

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

[krusader] [Bug 371745] Editing files from SFTP stopped working in 2.5.0

[Alex Bikadorov]

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

--- Comment #1 from Alex Bikadorov  ---

Cannot confirm. I can edit text files over local sshd server connection just
fine.

Does the server has any specialities?

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

[digikam] [Bug 372684] No thumbnail shows for some files

[Rick]

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

--- Comment #21 from Rick  ---
It looks like I didn't make the link right for the ThumbnailShows

but the ThumbnailNoShows
 link
you sent back is right.

What doesn't make sense is, if you got the ThumbnailNoShows, that is the
one that the thumbnail does not show for me.

On Tue, Nov 22, 2016 at 8:26 AM,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=372684
>
> --- Comment #20 from caulier.gil...@gmail.com ---
> 2 pictures ?
>
> I only get one picture from the cloud from you. Where is the second one ?
>
> Look links given in comment #15 :
>
> ThumbnailShows.jpg
> 
>
> ThumbnailNoShows.jpg
> 
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[krusader] [Bug 372023] ISO files listing/extracting broken

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||alex.bikado...@kdemail.net
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Alex Bikadorov  ---
I'm not familiar with ISO. When opened with the iso:/ protocol the first level
are always three directories:

>/El Torito Boot
>/El Torito BootJoliet level 3
>/ISO9660

The actual content is in one of these and Ark shows this content directly.

And yes, opening any of the files shows garbage. Maybe an encoding issue.

Windows/Microsoft ISOs cannot be be opened with Krusader OR Ark. Content is one
README file:

> This disc contains a "UDF" file system and requires an operating system
> that supports the ISO-13346 "UDF" file system specification.

But I don't have an ISO with missing files. Can you give an example?

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

[kwin] [Bug 372805] New: Compositor thinks Panel is on the secondary screen

[bugzilla_noreply]

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

Bug ID: 372805
   Summary: Compositor thinks Panel is on the secondary screen
   Product: kwin
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: multihead
  Assignee: kwin-bugs-n...@kde.org
  Reporter: everm...@pc-portal.at
  Target Milestone: ---

Monitor setup:
Secondary monitor || Primary Monitor
Panel position: Left side of the primary monitor.

When using the magic lamp effect (makes the bug most apparent) and you minimize
a window on the primary monitor, the window will fly all the way to the left of
the secondary monitor where no panel is located.

If you minimize a window on the secondary monitor, the window folds its self on
the left side of the screen.

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

[krusader] [Bug 372475] Wrong window position after restart in fluxbox

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||alex.bikado...@kdemail.net

--- Comment #1 from Alex Bikadorov  ---

Could be already fixed by 2a6103ef5 in master.

Can you build from source?

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

[digikam] [Bug 354232] Lens information is always "unavailable" for Pentax K-S1 images

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #8 from Maik Qualmann  ---
Note: This requires a rereading of the metadata from the images.

Maik

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

[digikam] [Bug 354232] Lens information is always "unavailable" for Pentax K-S1 images

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/digi
   ||kam/15f323c4908e1c47201090d
   ||378e8ad4304e21e91
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Maik Qualmann  ---
Git commit 15f323c4908e1c47201090d378e8ad4304e21e91 by Maik Qualmann.
Committed on 22/11/2016 at 18:16.
Pushed by mqualmann into branch 'master'.

add Pentax lens type Makernote
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-0libs/dmetadata/dmetadata.cpp

http://commits.kde.org/digikam/15f323c4908e1c47201090d378e8ad4304e21e91

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

[plasmashell] [Bug 372804] New: After the suspend the rendering of the icons and windows on the desktop is not properly working.

[bugzilla_noreply]

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

Bug ID: 372804
   Summary: After the suspend the rendering of the icons and
windows on the desktop is not properly working.
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: se...@kde.org
  Reporter: giggi1...@yahoo.com
  Target Milestone: 1.0

Created attachment 102395
  --> https://bugs.kde.org/attachment.cgi?id=102395=edit
The example

After the suspend the rendering of the icons and windows on the desktop is not
properly working.

In some case it appear a random image instead of the proper image.

This is an example where the writing is not redrawn properly: 
http://imgur.com/LxdOMq9

I'm using the compositing, with an nvidia video-card.

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

[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU

[knossos456]

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

--- Comment #9 from knossos456  ---
Ok, understanded.
Have VLC same probleme with a recoded HD stream ?
Have you installed Ubuntu from scratch or upgraded a previous version ?
What will done the command vdpauinfo ?


On my side, for VDPAU, i had to install ubuntu 16 lts from scratch to have
VDPAU working, upgrading was not working, I had 50% CPU usage.

It is not normal your résult for 6000 ATI series card to have 20 % CPU usage...
You need to have better than me, arround 2 % usage.

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

[Discover] [Bug 326581] Muon Update does not show the new updates, after notification message

[Airton]

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

--- Comment #18 from Airton  ---
This is happening with the version 5.7.5 on Kubuntu 16.10. Always when new
updates are available, discover shows "no updates" screen instead of listing
the updates.

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

[KScreen] [Bug 340120] The maximum resolution of the secondary screen (LCD display) is not detected correctly if the laptop is in the docking station

[bugzilla_noreply]

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

azr...@googlemail.com changed:

   What|Removed |Added

 CC||azr...@googlemail.com

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

[KScreen] [Bug 352523] Switching from laptop screen to dock with external monitors does not automatically activate dock monitors

[bugzilla_noreply]

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

azr...@googlemail.com changed:

   What|Removed |Added

 CC||azr...@googlemail.com

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

[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[bugzilla_noreply]

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

azr...@googlemail.com changed:

   What|Removed |Added

 CC||azr...@googlemail.com

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

[KScreen] [Bug 371655] No configuration change reflected when disconnecting docking station with external displays

[bugzilla_noreply]

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

azr...@googlemail.com changed:

   What|Removed |Added

 CC||azr...@googlemail.com

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

[kontact] [Bug 372803] New: Kontact crashes on launch

[bugzilla_noreply]

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

Bug ID: 372803
   Summary: Kontact crashes on launch
   Product: kontact
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: simonlang1...@gmail.com
  Target Milestone: ---

Application: kontact (5.3.3 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.9-3-ck-piledriver x86_64
Distribution: "Arch Linux"

-- Information about the crash:
Kontact crashes everytime when launched.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f973e5bf840 (LWP 7914))]

Thread 31 (Thread 0x7f95fc9a6700 (LWP 7984)):
#0  0x7f973b01f48d in poll () at /usr/lib/libc.so.6
#1  0x7f9734e02786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9734e0289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f973bb5b72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f973bb0523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f973b9280f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f973b92cd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9736de7454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f973b0287df in clone () at /usr/lib/libc.so.6

Thread 30 (Thread 0x7f95fd1a7700 (LWP 7983)):
#0  0x7f9734e47de0 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f9734e028a6 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#2  0x7f973bb5b72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f973bb0523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f973b9280f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f973b92cd78 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f9736de7454 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f973b0287df in clone () at /usr/lib/libc.so.6

Thread 29 (Thread 0x7f95ff7fe700 (LWP 7963)):
#0  0x7f9734e0260c in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f9734e0289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#2  0x7f973bb5b72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f973bb0523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f973b9280f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f973b92cd78 in  () at /usr/lib/libQt5Core.so.5
#6  0x7f9736de7454 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f973b0287df in clone () at /usr/lib/libc.so.6

Thread 28 (Thread 0x7f95f700 (LWP 7961)):
#0  0x7f973b01f48d in poll () at /usr/lib/libc.so.6
#1  0x7f9734e02786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9734e0289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f973bb5b72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f973bb0523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f973b9280f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f973b92cd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9736de7454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f973b0287df in clone () at /usr/lib/libc.so.6

Thread 27 (Thread 0x7f96077fe700 (LWP 7954)):
#0  0x7f973b01f48d in poll () at /usr/lib/libc.so.6
#1  0x7f9734e02786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9734e0289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f973bb5b72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f973bb0523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f973b9280f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f973b92cd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f9736de7454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f973b0287df in clone () at /usr/lib/libc.so.6

Thread 26 (Thread 0x7f9607fff700 (LWP 7952)):
#0  0x7f9734e47db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f9734e02184 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7f9734e02724 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f9734e0289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f973bb5b72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f973bb0523a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f973b9280f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f973b92cd78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9736de7454 in start_thread () at 

[krusader] [Bug 372802] No way to know if two folders are synchred ("synchron folder changes")

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||alex.bikado...@kdemail.net

--- Comment #1 from Alex Bikadorov  ---

Settings->Configure Krusader->Panel->Buttons->"Toggle-Button for
sync-browsing"?

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

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

[Julian Seward]

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

--- Comment #12 from Julian Seward  ---
Probably your least-worst option at this point is to compile the test
program in the configuration where the errors are not reported, and hope
that it all gets compiled into a single function (which it looks like
it will).  Then disassemble it and maybe we can see if the compiler
stuck in some instructions to zero out the array on the stack before
use.  That strikes me as the most likely outcome.

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

[krusader] [Bug 372802] New: No way to know if two folders are synchred ("synchron folder changes")

[Rafael]

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

Bug ID: 372802
   Summary: No way to know if two folders are synchred ("synchron
folder changes")
   Product: krusader
   Version: 2.5.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: synchronize
  Assignee: m...@fork.pl
  Reporter: rafael.linux.u...@gmail.com
  Target Milestone: ---

When I have 2 panels side by side and I enable "synchron folder changes" there
is no any way to know if they are linked or not. There are not any visible icon
or mark to know that. 

Moreover, that kind of "synchronization" is not available on menu bar. I needed
to add to "Tool bar" to access it.

Please, this feature should be improved.

Thank you

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

[Discover] [Bug 326581] Muon Update does not show the new updates, after notification message

[Airton]

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

Airton  changed:

   What|Removed |Added

 CC||airton.ram...@gmail.com

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

[kdenlive] [Bug 372668] Render a clip results in a black video with any of the available file formats.

[bugzilla_noreply]

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

--- Comment #2 from walter.buetiko...@livenet.ch ---
Hello

Thank you for your reply to my bug-report and your advise.

I just want to give you a feed-back on theactions I took.

I did a complete new install of Kubuntu 16.04 LT. I installed Kdenlive 
from ppa.launchpad.net/kdenlive/kdenlive-stable/ubuntu.

I installed extra codeces (see attached file)

I updated frei0r and MLT. (see attached file)


After a reboot everything works fine.






On 21.11.2016 20:33, Wegwerf wrote:
> https://bugs.kde.org/show_bug.cgi?id=372668
>
> Wegwerf  changed:
>
> What|Removed |Added
> 
>   CC||wegwerf-1-...@gmx.de
>
> --- Comment #1 from Wegwerf  ---
> With this limited information it is impossible to track down your issue. Can
> you please either install Kdenlive from the Kdenlive project ppa, either
> stable, or main together with updated MLT and frei0r packages? Does the 
> problem
> persist? What codec packages did you install?
>

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

[kwin] [Bug 363750] KWin uses "para" instead of "p" on some QLabel's

[Frederik Schwarzer]

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

--- Comment #11 from Frederik Schwarzer  ---
Thank you Lasse for the hint.
Although I do not have time to look into the inner workings of ki18n to see if
that atually fixes the issue as well, I will fix that translation error
tonight.

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

[dolphin] [Bug 372801] Can't stream files from SMB in unsupported applications

[Miha Frangež]

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

Miha Frangež  changed:

   What|Removed |Added

 CC||miha.fran...@gmail.com

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

[dolphin] [Bug 372801] New: Can't stream files from SMB in unsupported applications

[Miha Frangež]

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

Bug ID: 372801
   Summary: Can't stream files from SMB in unsupported
applications
   Product: dolphin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: miha.fran...@gmail.com
  Target Milestone: ---

Opening a file from SMB sends a program the SMB uri instead of a local
representation of the file. Since most programs aren't (and shouldn't) be
capable of opening files from the network, this usually fails.

After editing vlc.desktop to remove smb (it doesn't work), I had to wait 2
minutes for Dolphin to download a video file from a local server, just to check
if I've seen it already. This is terrible UX. 

A media player plays media files. If it can do it over SMB, that's cool, but it
shouldn't be a requirement.

I really don't want to sound ungreatful to all the devs working on KDE and the
entire Linux ecosystem, but these small things are what keep the adoption low.

So, here is my proposed solution:
Mount everything. No need to decide whether to copy, mount or stream. Just
mount the share when needed, then unmount it when all handles are closed. It's
simple and it always works.
Using gvfs would also work, although I doubt any KDE dev would want to.

A few more advantages of this approach: terminal access to remote files,
next/previous buttons in programs would work, links to remote files...

I know I could easily mount the share with a single command, but that is not my
point. A normal use wouldn't do that and would immediately switch back to
Windows (I've seen it happen).

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

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

[Carl Ponder]

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

--- Comment #11 from Carl Ponder  ---
Back to comment #9, there *is* no instruction initializing the array, which is
why it has some junk entries, regardless of valgirind's lack of mention.

Talking to the PGI people, the -Mxtack_arrays flag causes the local arrays to
be allocated on the stack, so the allocation is just a matter of adjusting the
stack-pointer, rather than invoking "malloc" or equivalent.

Does valgrind work by intercepting the malloc calls and then tabulating the
uninitialized memory-cells? And if the arrays are allocated off of the stack in
gfortran or gcc, how would valgrind keep track of this?

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

[krita] [Bug 372800] New: [Windows 10] Cursor Offset - Surface Pro 1 - Latest Wacom Drivers

[Don]

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

Bug ID: 372800
   Summary: [Windows 10] Cursor Offset - Surface Pro 1 - Latest
Wacom Drivers
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: donn...@gmail.com
  Target Milestone: ---

the pen cursor is offset on the canvas only and only in the y (vertical
direction). The y offset is also always positive Y and dynamic (log scale
maybe?) and not static, ie the offset is less the higher I touch on the screen
and more the lower I touch on the screen.
Both Wacom and QT report the total screen resolution correctly.

Manually adjusting the vertical resolution to 2x the actual height the offset
begins about a 1/4 of the way down the screen and starts as a negative Y offset
and then proceeds to a positive Y offset,

Manually adjusting the vertical resolution to 1.5x the actual results in no
offset until about 1/2 way down the screen and then a seemingly log scale
offset the further I go down the screen.

DPI scaling is set to 100%(no scaling of UI elements) in display properties.

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

[kontact] [Bug 372799] New: KMail crash, probably due to HTML mail

[Johannes Kehrer]

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

Bug ID: 372799
   Summary: KMail crash, probably due to HTML mail
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: j...@gmx.de
  Target Milestone: ---

Application: kontact (5.3.3 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.8-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
The first email in my account is a HTML mail. When I open Kmail it reads the
email and tries to show it. There it crashes.

The crash can be reproduced every time.

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

Thread 33 (Thread 0x7fa88d7ff700 (LWP 14149)):
#0  0x7fa9e8e5468d in poll () at /lib64/libc.so.6
#1  0x7fa9e2b1a876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa9e2b1a98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa9e998a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa9e99341ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa9e97628b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa9e9767558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fa9e4d06454 in start_thread () at /lib64/libpthread.so.0
#8  0x7fa9e8e5d39f in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7fa88e755700 (LWP 14138)):
#0  0x7fa9e4d0c10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fa9dbea10d9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fa9dbea1719 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fa9dbea18d0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fa9dbe9e46c in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fa9e4d06454 in start_thread () at /lib64/libpthread.so.0
#6  0x7fa9e8e5d39f in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7fa89528e700 (LWP 14133)):
#0  0x7fa9e8e5468d in poll () at /lib64/libc.so.6
#1  0x7fa9e2b1a876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa9e2b1a98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa9e998a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa9e99341ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa9e97628b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa9e9767558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fa9e4d06454 in start_thread () at /lib64/libpthread.so.0
#8  0x7fa9e8e5d39f in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7fa8a8823700 (LWP 14117)):
#0  0x7fa9e8e506fd in read () at /lib64/libc.so.6
#1  0x7fa9e2b5eb00 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa9e2b1a325 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa9e2b1a814 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fa9e2b1a98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fa9e998a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fa9e99341ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fa9e97628b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fa9e9767558 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fa9e4d06454 in start_thread () at /lib64/libpthread.so.0
#10 0x7fa9e8e5d39f in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7fa8a9024700 (LWP 14115)):
#0  0x7fa9e8e54667 in poll () at /lib64/libc.so.6
#1  0x7fa9e2b1a876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fa9e2b1a98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa9e998a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fa9e99341ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fa9e97628b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fa9e9767558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fa9e4d06454 in start_thread () at /lib64/libpthread.so.0
#8  0x7fa9e8e5d39f in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7fa8abfff700 (LWP 14109)):
#0  0x7fa9e975eaa9 in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5
#1  0x7fa9e9989f21 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7fa9e2b19d79 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fa9e2b1a79b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fa9e2b1a98c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fa9e998a79b in
QEventDispatcherGlib::processEvents(QFlags) ()
at 

[kdevelop] [Bug 372795] KDevelop crashes after running unit tests when CTest is already running

[Janek Bevendorff]

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

--- Comment #1 from Janek Bevendorff  ---
Additional information: this is absolutely reproducible. I have a Qt project
(KeePassXC https://github.com/keepassxreboot/keepassxc/ ) and when I enable the
CMake option WITH_GUI_TESTS, rebuild and then click "Run All Tests" in the Unit
Tests panel, KDevelop first runs the GUI tests in tests/gui and then asks me
twice (!) if I want to terminate the running CTest instance before running the
other non-GUI tests. Confirming the second dialog reliably crashes KDevelop.

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

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Hugo Klepsch]

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

Hugo Klepsch  changed:

   What|Removed |Added

 CC|hugo.klep...@gmail.com  |

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