[systemsettings] [Bug 369019] Typo in the Screen Locking module.

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #4 from Bhushan Shah  ---
Most likely it is already fixed, as I can't reproduce it with latest git master

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

[systemsettings] [Bug 369019] Typo in the Screen Locking module.

[via KDE Bugzilla]

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

--- Comment #3 from manuelcha...@gmail.com ---
I mean, Plasma 5.7.4

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

[plasmashell] [Bug 369024] New: Notification area distribution is uneven.

[via KDE Bugzilla]

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

Bug ID: 369024
   Summary: Notification area distribution is uneven.
   Product: plasmashell
   Version: 5.7.4
  Platform: Other
   URL: http://i.imgur.com/KwTSeQ5.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Look & Feel package
  Assignee: plasma-b...@kde.org
  Reporter: manuelcha...@gmail.com
CC: plasma-b...@kde.org

As you can see in the image linked, the notification/tray area icons doesn't
look evenly distributed. It doesn't look very pleasing. It should have the same
amount of space between each icon, and enough space, not to make it look all
crammed in there.

Reproducible: Always

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

[kdenlive] [Bug 369023] I want to downgrade to 16.04.3 because 16.08.1 is essentially unusable for me

[Vincent PINON via KDE Bugzilla]

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

--- Comment #2 from Vincent PINON  ---
Hello
regarding 16.8 usability, aren't you missing the timeline toolbar?
https://forum.kde.org/viewtopic.php?f=265=135852=363497#p363497
=> try restarting kdenlive after this command:
rm ~/.local/share/kxmlgui5/kdenlive/kdenliveui.rc

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

[krita] [Bug 368849] [Windows] Krita does not react to Wacom Penabled tabletPC stylus's Top Barrel Button/2nd Switch mouse event on canvas

[Tyson Tan via KDE Bugzilla]

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

--- Comment #2 from Tyson Tan  ---
Created attachment 101172
  --> https://bugs.kde.org/attachment.cgi?id=101172=edit
Krita under Windows 10 Cube i7 Stylus Top Barrel Button tablet log

Hi, wolthera 
I don't know exactly what the tablet log was saying, but it seems Krita thinks
the top barrel button belongs to a mouse and block its signal?

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

[systemsettings] [Bug 369019] Typo in the Screen Locking module.

[via KDE Bugzilla]

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

--- Comment #2 from manuelcha...@gmail.com ---
http://i.imgur.com/Vib751B.png

This is on Plasma 5..4

KDE Frameworks 5.25

Qt 5.7

I'm guessing it was fixed.

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

[plasmashell] [Bug 364529] Wayland : No title in Task manager for Systemsettings

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
Summary|Wayland : No icon nor title |Wayland : No title in Task
   |in Task manager for |manager for Systemsettings
   |Systemsettings  |
 Ever confirmed|0   |1
 CC||bhus...@gmail.com

--- Comment #3 from Bhushan Shah  ---
Systemsettings icon was fixed recently..
https://quickgit.kde.org/?p=systemsettings.git=commit=39e13de3468add20f37eb0f8814dd6996384d23f

However I can confirm that window title is not there.

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

[systemsettings] [Bug 369019] Typo in the Screen Locking module.

[Bhushan Shah via KDE Bugzilla]

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

Bhushan Shah  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||bhus...@gmail.com

--- Comment #1 from Bhushan Shah  ---
Can you post screenshot? It shows it correctly here.

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

[kdenlive] [Bug 369023] I want to downgrade to 16.04.3 because 16.08.1 is essentially unusable for me

[YEK via KDE Bugzilla]

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

--- Comment #1 from YEK  ---
Hi Jean-Baptiste,

I just found this article:

Downgrade Packages on Ubuntu
http://www.howtogeek.com/117929/how-to-downgrade-packages-on-ubuntu/

I launched the Synaptic Package Manager and uninstalled Kdenlive 4.16.08.1.
Then I rebooted my machine. Then I launched the Synaptic Package Manager and
chose Package–>Force Version. I saw that Kdenlive 4.15.12.3 was listed beneath
Kdenlive 4.16.08.1 but I received an error message when I tried to install
Kdenlive 4.15.12.3.

As I posted in my penultimate comment, which is also the initial comment in
this bug report, I want to install Kdenlive 16.04.3. However, it was not listed
in the Synaptic Package Manager.

Thanks,

Yekutiel

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

[kate] [Bug 369022] New: When a file that has a single line larger than the limits gets changed, Kwrite crashes

[Giampaolo via KDE Bugzilla]

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

Bug ID: 369022
   Summary: When a file that has a single line larger than the
limits gets changed, Kwrite crashes
   Product: kate
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: giampaolo.ferrad...@gmail.com

Application: kwrite (15.12.3)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.3-100.fc23.x86_64+debug x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
- What I was doing when the application crashed:
Activated an instance of Kwriter where a file that had a large single line was
open. 
Modification by some other application always led to the classic pop up
requesting for a choice to reload/overwrite/ignore/etc, and the choice to
reload caused a crash.
Always reproductible.

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7f427a9d6700 (LWP 11415)):
#0  0x7f429363db7d in poll () at /lib64/libc.so.6
#1  0x7f428bd41272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f428bd42ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f427dfca039 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f429425c00c in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f429119e61a in start_thread () at /lib64/libpthread.so.0
#6  0x7f42936495fd in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f427228e700 (LWP 11416)):
#0  0x7f429363db7d in poll () at /lib64/libc.so.6
#1  0x7f428ff2918c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f428ff2929c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f4294446b5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f42943f725a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f4294257bd4 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f429464c675 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f429425c00c in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f429119e61a in start_thread () at /lib64/libpthread.so.0
#9  0x7f42936495fd in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f426a336700 (LWP 11418)):
#0  0x7f429363976d in read () at /lib64/libc.so.6
#1  0x7f428ff6c3f0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f428ff28c84 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f428ff29130 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f428ff2929c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f428ff292d9 in glib_worker_main () at /lib64/libglib-2.0.so.0
#6  0x7f428ff4f8e5 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#7  0x7f429119e61a in start_thread () at /lib64/libpthread.so.0
#8  0x7f42936495fd in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f4269b35700 (LWP 11419)):
#0  0x7f429363db7d in poll () at /lib64/libc.so.6
#1  0x7f428ff2918c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f428ff29512 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3  0x7f427acbf516 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0
#4  0x7f428ff4f8e5 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5  0x7f429119e61a in start_thread () at /lib64/libpthread.so.0
#6  0x7f42936495fd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f425bfff700 (LWP 11420)):
#0  0x7f42911a3b20 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f426399fe43 in radeon_drm_cs_emit_ioctl () at
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f426399f597 in impl_thrd_routine () at
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f429119e61a in start_thread () at /lib64/libpthread.so.0
#4  0x7f42936495fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f4296c4c8c0 (LWP 11414)):
[KCrash Handler]
#6  0x7f42985b6108 in KateMessageWidget::postMessage(KTextEditor::Message*,
QList) () at /lib64/libKF5TextEditor.so.5
#7  0x7f429858aa4c in
KTextEditor::ViewPrivate::postMessage(KTextEditor::Message*,
QList) () at /lib64/libKF5TextEditor.so.5
#8  0x7f42984fea11 in
KTextEditor::DocumentPrivate::postMessage(KTextEditor::Message*) () at
/lib64/libKF5TextEditor.so.5
#9  0x7f429850c172 in KTextEditor::DocumentPrivate::openFile() () at
/lib64/libKF5TextEditor.so.5
#10 0x7f4297d5edb1 in KParts::ReadOnlyPartPrivate::openLocalFile() () at
/lib64/libKF5Parts.so.5
#11 0x7f4297d5fc44 

[frameworks-baloo] [Bug 362647] Can't search with Chinese characters

[Tao Guo via KDE Bugzilla]

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

Tao Guo  changed:

   What|Removed |Added

 CC||guotao...@gmail.com

--- Comment #1 from Tao Guo  ---
I can confirm this bug on archlinux with baloo 5.24

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

[kwin] [Bug 107302] Associate any virtual desktop with any screen

[via KDE Bugzilla]

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

mailfor.marcus.claw+3094182...@gmail.com changed:

   What|Removed |Added

 CC||mailfor.marcus.claw+3094182
   ||5...@gmail.com

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #28 from Leslie Zhai  ---
Git commit 477870ea36d07505889bfe33becc41ba57f3 by Leslie Zhai.
Committed on 19/09/2016 at 02:37.
Pushed by lesliezhai into branch 'multisession'.

growisofs described you don't have to specify -C option, it will
construct one for you.

M  +9-1libk3b/projects/k3bgrowisofswriter.cpp

http://commits.kde.org/k3b/477870ea36d07505889bfe33becc41ba57f3

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Leslie Zhai via KDE Bugzilla]

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

--- Comment #27 from Leslie Zhai  ---
Hi Thomas,

> I should mention that session 2 tests with growisofs -M instead of -Z failed

growisofs -M /dev/sr0=/dev/fd/0 -use-the-force-luke=notray
-use-the-force-luke=tty -use-the-force-luke=4gms
-use-the-force-luke=tracksize:322106 -speed=4 -use-the-force-luke=bufsize:32m

you mean the above failed to work? then what described
http://fy.chalmers.se/~appro/linux/DVD+RW/ you don't have to specify -C option,
growisofs will construct one for you?! wrongly implemented?

Regards,
Leslie Zhai

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

[konsole] [Bug 369021] New: There should be splitting options on right click menu.

[via KDE Bugzilla]

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

Bug ID: 369021
   Summary: There should be splitting options on right click menu.
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: split-view
  Assignee: konsole-de...@kde.org
  Reporter: manuelcha...@gmail.com

I like how Terminator has options to split view horizontally or vertically in
the console right click menu. There should also be the option to close the
current split/view.

Reproducible: Always

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

[systemsettings] [Bug 369020] New: Global Keys window starts too small.

[via KDE Bugzilla]

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

Bug ID: 369020
   Summary: Global Keys window starts too small.
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_keys
  Assignee: k...@michael-jansen.biz
  Reporter: manuelcha...@gmail.com

The window to change the global hotkeys starts shrinked, only one line of keys
to change is visible, I have to resize it every time to make it usable.

Reproducible: Always

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

[systemsettings] [Bug 369019] New: Typo in the Screen Locking module.

[via KDE Bugzilla]

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

Bug ID: 369019
   Summary: Typo in the Screen Locking module.
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: manuelcha...@gmail.com

Second field says Re password.  instead of Require password.

Reproducible: Always

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

[kdevelop] [Bug 368603] crash when starting an lldb debug session

[Aetf via KDE Bugzilla]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #20 from Aetf <7437...@gmail.com> ---
Pushed to master with commit 262bf5dddf2aef991c66fdc484c58daf32eaa348, so I'm
going to close this, reopen it if you have any further problems.

A debugger shouldn't take too much memory. It looks like a bug. Did you try to
manually debug using lldb 3.9? And please open another report if that only
happens in KDevelop.

Well, the working directory changing does require another patch[1] ... And I've
created a RR in their Phabricator[2], which seems to be more active than their
bug tracker.

[1] https://llvm.org/bugs/show_bug.cgi?id=30265
[2] https://reviews.llvm.org/D24711

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

[konsole] [Bug 369018] New: Ctrl + Shift + S has multiple mappings.

[via KDE Bugzilla]

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

Bug ID: 369018
   Summary: Ctrl + Shift + S has multiple mappings.
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: manuelcha...@gmail.com

Close Active split view and Save Output As have the same keyboard shortcut
(Ctrl + Shift + S) and when there's a split view open and I press it it says
it's ambiguous.

Reproducible: Always

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

[kmail2] [Bug 369017] New: Kmail crash - application unusable

[Vinu Moses via KDE Bugzilla]

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

Bug ID: 369017
   Summary: Kmail crash - application unusable
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: v...@cmcvellore.ac.in

Application: kmail (5.3.0 (QtWebEngine))
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-200.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

App sometimes crashes when opening it, sometimes it crashes after a while when
trying to view some message.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6e0b4cc940 (LWP 2462))]

Thread 32 (Thread 0x7f6d65041700 (LWP 2535)):
#0  0x7f6e20ec1bd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f6e27d3be79 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() from /lib64/libQt5WebEngineCore.so.5
#2  0x7f6e27d3c540 in base::SequencedWorkerPool::Worker::Run() () from
/lib64/libQt5WebEngineCore.so.5
#3  0x7f6e27d3c710 in base::SimpleThread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f6e27d390fd in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f6e20ebc5ca in start_thread () from /lib64/libpthread.so.0
#6  0x7f6e2fcf7f6d in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f6d66510700 (LWP 2533)):
#0  0x7f6e20ec1bd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f6e148f7bc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7f6e148f7c09 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7f6e20ebc5ca in start_thread () from /lib64/libpthread.so.0
#4  0x7f6e2fcf7f6d in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f6d6777e700 (LWP 2521)):
#0  0x7f6e2fcec3ed in poll () from /lib64/libc.so.6
#1  0x7f6e1fa3ea06 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f6e1fa3eb1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f6e30af124b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f6e30aa05ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f6e308ff343 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f6e3090399a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f6e20ebc5ca in start_thread () from /lib64/libpthread.so.0
#8  0x7f6e2fcf7f6d in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f6d7c9de700 (LWP 2518)):
#0  0x7f6e1fa82a09 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7f6e1fa3df65 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7f6e1fa3e92b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f6e1fa3eb1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f6e30af124b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f6e30aa05ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f6e308ff343 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f6e3090399a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f6e20ebc5ca in start_thread () from /lib64/libpthread.so.0
#9  0x7f6e2fcf7f6d in clone () from /lib64/libc.so.6

Thread 28 (Thread 0x7f6d7e9bc700 (LWP 2511)):
#0  0x7f6e2fcec3ed in poll () from /lib64/libc.so.6
#1  0x7f6e1fa3ea06 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f6e1fa3eb1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f6e30af124b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f6e30aa05ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f6e308ff343 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f6e3090399a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f6e20ebc5ca in start_thread () from /lib64/libpthread.so.0
#8  0x7f6e2fcf7f6d in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f6d7f3cf700 (LWP 2504)):
#0  0x7f6e1fa82a24 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7f6e1fa3e9fa in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f6e1fa3eb1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f6e30af124b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f6e30aa05ea in

[konversation] [Bug 369016] New: Remove pixel on top of tab bar when menubar is off

[via KDE Bugzilla]

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

Bug ID: 369016
   Summary: Remove pixel on top of tab bar when menubar is off
   Product: konversation
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: manuelcha...@gmail.com

I removed the menubar and put the tab bar on top. But there's a 1 pixel line on
top of the tab bar that disables the users from clicking on a tab as easily
since when the window is maximized you would expect the very top of the screen
to have access to the tabs, but you have to move your mouse slightly lower.

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

[skrooge] [Bug 365724] Driver not loaded Driver not loaded

[via KDE Bugzilla]

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

--- Comment #14 from mspada...@yahoo.com ---
libqsqlite.so  libskgsqlcipher.so

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

[krita] [Bug 369015] New: Canvas not registering my tablet or mouse

[Matt via KDE Bugzilla]

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

Bug ID: 369015
   Summary: Canvas not registering my tablet or mouse
   Product: krita
   Version: 3.0.1
  Platform: Mer
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: CPU Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: deadtiredd...@gmail.com

I start up the Krita platform, but when I try drawing on the canvas window
nothing happens. The dotted Krita Courser gets frozen in some random position
on the canvas window, almost as if as soon as my mouse curser entered the
window a screen shot was taken and layered of the actual canvas window; the
canvas window is still functional, I just can't see what I'm doing, unless I
(1) see what I have done in the tiny layer thumbnail or (2) click the tab that
says "Normal" then my pen strokes suddenly appear! Or if I minimize the entire
Krita program and come back to it, my work magically appears that way too. Did
I possibly configure my tablet wrong? I have a Wacom Intuos pen and touch
tablet (small) and I run on the Windows 7 operating system.

Reproducible: Always

Steps to Reproduce:
1.Start Krita.
2.Try drawing something in Krita.
3.If you can't see it minimize and come back.

Actual Results:  
Krita did not detect either my mouse or tablet.

Expected Results:  
Krita will not detect either my mouse or tablet.

I feel as though it is detecting them, but not displaying them unless further
prompted by some sort of pseudo-refresh by selecting another option, tab, or
window feature in the program.

Also I feel it's worth noting that opening additional windows of Krita crashed
krita, when I tried exiting one of them.

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

[kdenlive] [Bug 368875] "Position and Zoom" effect creates white line and dots outside clip

[Dany via KDE Bugzilla]

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

--- Comment #7 from Dany  ---
I have both effect / transition. Thanks for your work and time.

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

[kmplayer] [Bug 336341] i have installed km player. but unable to play any videos.

[kmi via KDE Bugzilla]

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

kmi  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME
 CC||kamika...@web.de

--- Comment #1 from kmi  ---
Probably wrong back-end selected.

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

[skrooge] [Bug 368828] Ubuntu KF5 PPA xenial package still uses oxygen icon theme

[via KDE Bugzilla]

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

--- Comment #2 from dberg...@gmail.com ---
Does this mean the stable 2.4.0 package will not be fixed? I will wait for the
next stable release if that is the case.

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

[kactivitymanagerd] [Bug 366688] Segfault when started under kwin_wayland

[James via KDE Bugzilla]

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

--- Comment #2 from James  ---
This crash is no longer occurring, after explicitly selecting the Breeze window
decorations, at Martin's suggestion.  But there is a crash backtrace at
 https://bugs.kde.org/show_bug.cgi?id=366689#c2

If kwin_wayland can be made to work with window decorations other than Breeze,
that would be helpful.

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

[skrooge] [Bug 368828] Ubuntu KF5 PPA xenial package still uses oxygen icon theme

[Stephane MANKOWSKI via KDE Bugzilla]

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

Stephane MANKOWSKI  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Stephane MANKOWSKI  ---
>From my ppa, "breeze" is used:
https://launchpad.net/~s-mankowski/+archive/ubuntu/beta-kf5

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

[krita] [Bug 369014] New: Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)

[via KDE Bugzilla]

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

Bug ID: 369014
   Summary: Krita freezes/locks up when saving to jpeg or png
files (esp when overwrite existing)
   Product: krita
   Version: 3.0.1
  Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: avtandil.ga...@gmail.com

When I've been working for about half an hour, (in this case saving png or jpeg
exports or saves) I notice that a file doesn't get overwritten on update.

Then next time I try to save my file, krita freezes up. All options grey out.
No control. Have to force quit Krita.

Again, issue appears to occur when saving to a format other than Kra. Total
lockup of krita. Maybe it's related to memory? I seem to be able to save one or
two files before problems start happening.

Reproducible: Sometimes

Steps to Reproduce:
1. Start working.
2. Start saving to png or jpeg. Export or save as both appear to behave this
way.
3. After about a half hour of working, you'll notice that a file didn't take
your last update.
4. The next save will lock up Krita entirely.

Actual Results:  
Krita locks up.
It seems pretty regular, but takes a while to get to that point.

Expected Results:  
Overwrite message should popup and ask permission to overwrite file (it
doesn't)

File saves to disk.
Krita returns control to user.

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

[kwin] [Bug 369013] New: New window creation crashes Kwin

[Balpo via KDE Bugzilla]

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

Bug ID: 369013
   Summary: New window creation crashes Kwin
   Product: kwin
   Version: 5.7.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: balpe...@gmail.com

Application: kwin_x11 (5.7.4)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:
Sometimes when I open new windows, KWin crashes, and sometimes it fails to
restart and windows go borderless.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa835a514c0 (LWP 10428))]

Thread 6 (Thread 0x7fa827fff700 (LWP 25475)):
#0  0x7fa84d391253 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa84b21cd3f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) (nfds=13, fdread=fdread@entry=0x7fa81c073ab8,
fdwrite=fdwrite@entry=0x7fa81c073d48, fdexcept=fdexcept@entry=0x7fa81c073fd8,
orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75
#2  0x7fa84b21e7e4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (timeout=0x0, exceptfds=0x7fa81c073fd8, writefds=0x7fa81c073d48,
readfds=0x7fa81c073ab8, nfds=, this=0x7fa81c06a030) at
kernel/qeventdispatcher_unix.cpp:320
#3  0x7fa84b21e7e4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (this=this@entry=0x7fa81c073920, flags=..., flags@entry=...,
timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196
#4  0x7fa84b21ecfa in
QEventDispatcherUNIX::processEvents(QFlags)
(this=0x7fa81c06a030, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7fa84b1c919a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa827ffec60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fa84afeee53 in QThread::exec() (this=this@entry=0x2db2ee0) at
thread/qthread.cpp:500
#7  0x7fa845a84a55 in QQmlThreadPrivate::run() (this=0x2db2ee0) at
qml/ftw/qqmlthread.cpp:141
#8  0x7fa84aff3d78 in QThreadPrivate::start(void*) (arg=0x2db2ee0) at
thread/qthread_unix.cpp:341
#9  0x7fa846926464 in start_thread (arg=0x7fa827fff700) at
pthread_create.c:333
#10 0x7fa84d39897f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7fa818db6700 (LWP 10447)):
#0  0x7fa84692c18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa84a38d574 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa84a38d5b9 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa846926464 in start_thread (arg=0x7fa818db6700) at
pthread_create.c:333
#4  0x7fa84d39897f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7fa81affa700 (LWP 10444)):
#0  0x7fa84d391253 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa84b21cd3f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) (nfds=17, fdread=fdread@entry=0x7fa814000a78,
fdwrite=fdwrite@entry=0x7fa814000d08, fdexcept=fdexcept@entry=0x7fa814000f98,
orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75
#2  0x7fa84b21e7e4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (timeout=0x0, exceptfds=0x7fa814000f98, writefds=0x7fa814000d08,
readfds=0x7fa814000a78, nfds=, this=0x7fa8140008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  0x7fa84b21e7e4 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (this=this@entry=0x7fa8140008e0, flags=..., flags@entry=...,
timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196
#4  0x7fa84b21ecfa in
QEventDispatcherUNIX::processEvents(QFlags)
(this=0x7fa8140008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7fa84b1c919a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fa81aff9c60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7fa84afeee53 in QThread::exec() (this=this@entry=0x1a5bc00) at
thread/qthread.cpp:500
#7  0x7fa845a84a55 in QQmlThreadPrivate::run() (this=0x1a5bc00) at
qml/ftw/qqmlthread.cpp:141
#8  0x7fa84aff3d78 in QThreadPrivate::start(void*) (arg=0x1a5bc00) at
thread/qthread_unix.cpp:341
#9  0x7fa846926464 in start_thread (arg=0x7fa81affa700) at
pthread_create.c:333
#10 0x7fa84d39897f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7fa82eec1700 (LWP 10435)):
#0  0x7fa84b21e9bd in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) (this=this@entry=0x7fa8280008e0, flags=..., flags@entry=...,
timeout=timeout@entry=0x0) at 

[krita] [Bug 369012] New: crash when playing animation when document's size is larger than 30M (approx)

[via KDE Bugzilla]

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

Bug ID: 369012
   Summary: crash when playing animation when document's size is
larger than 30M (approx)
   Product: krita
   Version: 3.0.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: pedro.roch...@yahoo.com.br

I got to the limit of 30M though trial and error. That's anything larger than
2000 x 2000 pixels, 100 ppi.
On rare occasions it wont crash until the second or third time I press play.

Visual Studio debugging gave me this:
Unhandled exception at 0x5998EC7C (nvoglv64.dll) in krita.exe: Fatal
program exit requested.

Sorry if that's not very useful. I'm not very tech savvy.


Reproducible: Always

Steps to Reproduce:
1. create a New document, predefined size "texture 2048 x 2048"
2. pick animation workspace
3. press Play/Pause button
it will crash even if I don't create any frames or draw anything

Actual Results:  
"Krita stopped working" crash

Expected Results:  
Play animation normally. 
Some lag would understandable with large files, but it shouldn't just crash

Windows 10 - 64 b
Krita 3.0.1 64 b (windows installer)
Nvidia GeForce GTX 750 Ti - driver 369.09

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

[kmail2] [Bug 369011] Message view breaks after clicking on a link in an email.

[via KDE Bugzilla]

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

nikol...@kakouros.net changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

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

[kmail2] [Bug 369011] New: Message view breaks after clicking on a link in an email.

[via KDE Bugzilla]

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

Bug ID: 369011
   Summary: Message view breaks after clicking on a link in an
email.
   Product: kmail2
   Version: unspecified
  Platform: Other
   URL: http://imgur.com/a/sZQla
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: nikol...@kakouros.net

Whenever I click on a link that is included in an email, kmail's ui breaks as
shown in the pictures. The message list seems to be half duplicated into the
message area. However, the position of the elements seems to be where it is
supposed to be. If you remember the position of the "No HTML message" bar for
example, you can click on it, even if it seems that you are clicking on the
duplicated message list. This is independent of the layout. If I choose to
heave the message page below the message list, then again the message list is
duplicated in the same way into the message pane. The only way I have found to
resolve this is by restarting KMail.

Reproducible: Always

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

[frameworks-kactivities] [Bug 362748] unable to create new activities with the user interface

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

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

--- Comment #8 from Ivan Čukić  ---
I forgot to reply - the activity creation dialogue opens, but it does not go
above the main kcmshell window. There was a bug in kcmshell which was fixed
some time ago (can't remember whether the fix is in 5.7 or it will be released
with 5.8).

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

[kactivitymanagerd] [Bug 361702] Kactivitymanagerd doesn't close on shutdown and triggers 90 sec shutdown delay in systemd

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

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

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

[frameworks-kactivities] [Bug 368033] kactivitymanagerd - core dumps at will

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

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

--- Comment #1 from Ivan Čukić  ---
If that many applications are crashing, you have some setup issues.

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

[kactivitymanagerd] [Bug 366688] Segfault when started under kwin_wayland

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

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

--- Comment #1 from Ivan Čukić  ---
Seems Qml crashes KWin, and then KWin takes the rest with it.

Can you retrieve the kwin crash backtrace?

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

[kmail2] [Bug 369010] New: Kmail crash on message open or right-click

[via KDE Bugzilla]

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

Bug ID: 369010
   Summary: Kmail crash on message open or right-click
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: t...@sonic.net

Application: kmail (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.3-200.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Upgraded from FC23 to 24 (no custom packages, very vanilla). All
messages/configuration appears to be there, but just about any action on an
inbox message (click, right click) crashed kmail.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9cbc079940 (LWP 3731))]

Thread 42 (Thread 0x7f9b1f801700 (LWP 3813)):
#0  0x7f9caa69bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9cb1570e79 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() from /lib64/libQt5WebEngineCore.so.5
#2  0x7f9cb1571540 in base::SequencedWorkerPool::Worker::Run() () from
/lib64/libQt5WebEngineCore.so.5
#3  0x7f9cb1571710 in base::SimpleThread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f9cb156e0fd in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f9caa6965ca in start_thread () from /lib64/libpthread.so.0
#6  0x7f9cb9599f6d in clone () from /lib64/libc.so.6

Thread 41 (Thread 0x7f9be4ff9700 (LWP 3802)):
#0  0x7f9caa69bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9cad272203 in JSC::GCThread::waitForNextPhase() () from
/lib64/libQt5WebKit.so.5
#2  0x7f9cad272290 in JSC::GCThread::gcThreadMain() () from
/lib64/libQt5WebKit.so.5
#3  0x7f9cad578531 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQt5WebKit.so.5
#4  0x7f9caa6965ca in start_thread () from /lib64/libpthread.so.0
#5  0x7f9cb9599f6d in clone () from /lib64/libc.so.6

Thread 40 (Thread 0x7f9be57fa700 (LWP 3801)):
#0  0x7f9caa69bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9cad272203 in JSC::GCThread::waitForNextPhase() () from
/lib64/libQt5WebKit.so.5
#2  0x7f9cad272290 in JSC::GCThread::gcThreadMain() () from
/lib64/libQt5WebKit.so.5
#3  0x7f9cad578531 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQt5WebKit.so.5
#4  0x7f9caa6965ca in start_thread () from /lib64/libpthread.so.0
#5  0x7f9cb9599f6d in clone () from /lib64/libc.so.6

Thread 39 (Thread 0x7f9be5ffb700 (LWP 3800)):
#0  0x7f9caa69bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9cad272203 in JSC::GCThread::waitForNextPhase() () from
/lib64/libQt5WebKit.so.5
#2  0x7f9cad272290 in JSC::GCThread::gcThreadMain() () from
/lib64/libQt5WebKit.so.5
#3  0x7f9cad578531 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQt5WebKit.so.5
#4  0x7f9caa6965ca in start_thread () from /lib64/libpthread.so.0
#5  0x7f9cb9599f6d in clone () from /lib64/libc.so.6

Thread 38 (Thread 0x7f9be67fc700 (LWP 3799)):
#0  0x7f9caa69bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9cad272203 in JSC::GCThread::waitForNextPhase() () from
/lib64/libQt5WebKit.so.5
#2  0x7f9cad272290 in JSC::GCThread::gcThreadMain() () from
/lib64/libQt5WebKit.so.5
#3  0x7f9cad578531 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQt5WebKit.so.5
#4  0x7f9caa6965ca in start_thread () from /lib64/libpthread.so.0
#5  0x7f9cb9599f6d in clone () from /lib64/libc.so.6

Thread 37 (Thread 0x7f9be6ffd700 (LWP 3798)):
#0  0x7f9caa69bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9cad272203 in JSC::GCThread::waitForNextPhase() () from
/lib64/libQt5WebKit.so.5
#2  0x7f9cad272290 in JSC::GCThread::gcThreadMain() () from
/lib64/libQt5WebKit.so.5
#3  0x7f9cad578531 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQt5WebKit.so.5
#4  0x7f9caa6965ca in start_thread () from /lib64/libpthread.so.0
#5  0x7f9cb9599f6d in clone () from /lib64/libc.so.6

Thread 36 (Thread 0x7f9be77fe700 (LWP 3797)):
#0  0x7f9caa69bbd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f9cad272203 in JSC::GCThread::waitForNextPhase() () from
/lib64/libQt5WebKit.so.5
#2  0x7f9cad272290 in JSC::GCThread::gcThreadMain() () from
/lib64/libQt5WebKit.so.5
#3  0x7f9cad578531 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQt5WebKit.so.5
#4  0x7f9caa6965ca in start_thread () from /lib64/libpthread.so.0
#5  0x7f9cb9599f6d in clone 

[kwin] [Bug 369009] New: KWin crashes on Steam interaction without restarting

[Mathias Dietrich via KDE Bugzilla]

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

Bug ID: 369009
   Summary: KWin crashes on Steam interaction without restarting
   Product: kwin
   Version: 5.7.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: glx
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dietrichmath...@gmail.com

KWin crashes on several situations using Steam, e.g. like running Steam videos
on fullscreen or just starting Company of Heroes 2.

Reproducible: Always

Steps to Reproduce:
1. Open steam.
2. Start Company of Heroes 2
3. A warning notification of the game appears that AMD drivers are unsupported
4. Kwin crashes

Actual Results:  
Kwin crashes and all window bars disappear.

Expected Results:  
Nothing should happen

Restarting kwin_x11 and reproduce the steps produce the following terminal
output:

kwin_x11
QXcbConnection: XCB error: 3 (BadWindow), sequence: 178, resource id: 37748742,
major code: 20 (GetProperty), minor code: 0
OpenGL vendor string:   X.Org
OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN (DRM 2.45.0
/ 4.7.4-1-ARCH, LLVM 3.8.1)
OpenGL version string:  4.1 (Core Profile) Mesa 12.0.3
OpenGL shading language version string: 4.10
Driver: Unknown
GPU class:  Unknown
OpenGL version: 4.1
GLSL version:   4.10
Mesa version:   12.0.3
X server version:   1.18.4
Linux kernel version:   4.7.4
Requires strict binding:yes
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2087, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2097, resource id: 0,
major code: 14 (GetGeometry), minor code: 0 
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2098, resource id: 0,
major code: 14 (GetGeometry), minor code: 0 
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2099, resource id: 0,
major code: 14 (GetGeometry), minor code: 0 
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2100, resource id: 0,
major code: 14 (GetGeometry), minor code: 0 
QMetaProperty::read: Unable to handle unregistered datatype
'KWayland::Server::SurfaceInterface*' for property 'KWin::Toplevel::surface'
QXcbConnection: XCB error: 3 (BadWindow), sequence: 9890, resource id:
37748759, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 9938, resource id:
35652084, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 19193, resource id:
81792432, major code: 20 (GetProperty), minor code: 0   
QXcbConnection: XCB error: 3 (BadWindow), sequence: 35080, resource id:
37748743, major code: 15 (QueryTree), minor code: 0 
QXcbConnection: XCB error: 3 (BadWindow), sequence: 35155, resource id:
35652093, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 35621, resource id:
81795434, major code: 20 (GetProperty), minor code: 0   
QXcbConnection: XCB error: 3 (BadWindow), sequence: 36788, resource id:
81795581, major code: 20 (GetProperty), minor code: 0   
QXcbConnection: XCB error: 3 (BadWindow), sequence: 42552, resource id:
37748743, major code: 15 (QueryTree), minor code: 0 
QXcbConnection: XCB error: 3 (BadWindow), sequence: 42624, resource id:
35652099, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 44778, resource id:
35652101, major code: 42 (SetInputFocus), minor code: 0 
QXcbConnection: XCB error: 3 (BadWindow), sequence: 44779, resource id:
35652101, major code: 25 (SendEvent), minor code: 0 
QXcbConnection: XCB error: 3 (BadWindow), sequence: 44781, resource id:
35652101, major code: 15 (QueryTree), minor code: 0 
QXcbConnection: XCB error: 8 (BadMatch), sequence: 54049, resource id:
16777482, major code: 42 (SetInputFocus), minor code: 0 
kwin_x11: Couldn't find current GLX or EGL context. 

Application::crashHandler() called with signal 11; recent crashes: 1
KCrash: Application 'kwin_x11' crashing...

-- 
You are receiving this mail because:
You are 

[digikam] [Bug 369003] editor crash

[via KDE Bugzilla]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|general |ImageEditor

--- Comment #1 from caulier.gil...@gmail.com ---
Ir crash in memory management (memcpy) while image data are copied in digiKam
internal container.

This problem have been certainly fixed in 5.x release. Please update and try
again

Gilles Caulier

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

[frameworks-plasma] [Bug 367828] NO panel available

[Nick Cross via KDE Bugzilla]

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

Nick Cross  changed:

   What|Removed |Added

 CC||k...@goots.org

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

[kate] [Bug 369008] New: Kate crashes when doing lookoup

[Lukasz via KDE Bugzilla]

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

Bug ID: 369008
   Summary: Kate crashes when doing lookoup
   Product: kate
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: dolo...@outlook.com

Application: kate (16.08.1)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-ck4-bfq-uksm x86_64
Distribution (Platform): Archlinux Packages

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

Open a file (in my case messageviewer_AQ2428 which contains a C code), click
with right on some text, choose Project -> Lookup: text, observe crash.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7fe63daa5700 (LWP 17475)):
#0  0x7fe65cebe10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7fe6419b24d3 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so
#2  0x7fe6419b1c17 in ?? () from /usr/lib/xorg/modules/dri/radeonsi_dri.so
#3  0x7fe65ceb8454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7fe6605497df in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7fe6491e4700 (LWP 17474)):
#0  0x7fe66054048d in poll () from /usr/lib/libc.so.6
#1  0x7fe65b1d7066 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fe65b1d717c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fe66116659b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fe6611100da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fe660f330f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fe661577e75 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7fe660f37d78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fe65ceb8454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fe6605497df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fe665fb3200 (LWP 17472)):
[KCrash Handler]
#5  0x7fe6626e6570 in QStackedWidget::currentWidget() const () from
/usr/lib/libQt5Widgets.so.5
#6  0x7fe642911664 in KateProjectPluginView::slotProjectIndex
(this=0x2ad7650) at
/home/dlh/abs/kate/src/kate-16.08.1/addons/project/kateprojectpluginview.cpp:499
#7  0x7fe64292fb65 in KateProjectPluginView::qt_static_metacall
(_o=, _c=, _id=, _a=) at
/home/dlh/abs/kate/src/build/addons/project/moc_kateprojectpluginview.cpp:170
#8  0x7fe66113d4e9 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#9  0x7fe662550472 in QAction::triggered(bool) () from
/usr/lib/libQt5Widgets.so.5
#10 0x7fe662552e60 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/libQt5Widgets.so.5
#11 0x7fe6626c0eea in ?? () from /usr/lib/libQt5Widgets.so.5
#12 0x7fe6626c70ec in ?? () from /usr/lib/libQt5Widgets.so.5
#13 0x7fe6626cb0e0 in QMenu::mouseReleaseEvent(QMouseEvent*) () from
/usr/lib/libQt5Widgets.so.5
#14 0x7fe66259df18 in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#15 0x7fe6626cbb9b in QMenu::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#16 0x7fe662556e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#17 0x7fe66255f46d in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#18 0x7fe66c80 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#19 0x7fe66255db1d in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/usr/lib/libQt5Widgets.so.5
#20 0x7fe6625b85a0 in ?? () from /usr/lib/libQt5Widgets.so.5
#21 0x7fe6625ba763 in ?? () from /usr/lib/libQt5Widgets.so.5
#22 0x7fe662556e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#23 0x7fe66255e5b1 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#24 0x7fe66c80 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#25 0x7fe661dc50e3 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /usr/lib/libQt5Gui.so.5
#26 0x7fe661dc6c65 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/libQt5Gui.so.5
#27 0x7fe661da4cbb in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/libQt5Gui.so.5
#28 0x7fe65392d310 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#29 0x7fe65b1d6e67 in g_main_context_dispatch () from

[kdenlive] [Bug 358741] git master: extract frame exports proxy clip frame instead of original clip frame

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

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

--- Comment #4 from Wegwerf  ---
Fixed.

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

[kmail2] [Bug 366204] Setting Fancy headers in View is not kept in kmail 16.04

[Michal Hlavac via KDE Bugzilla]

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

Michal Hlavac  changed:

   What|Removed |Added

 CC||hla...@hlavki.eu

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

[Skanlite] [Bug 369007] New: Greyscale images saved as colour

[Tristan Miller via KDE Bugzilla]

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

Bug ID: 369007
   Summary: Greyscale images saved as colour
   Product: Skanlite
   Version: 1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: psychon...@nothingisreal.com

With my scanner, Skanlite gives me the option of scanning in greyscale or in
colour.  However, images that are scanned in greyscale are saved with RGB-space
colour (at least when PNG is selected as the output format).  This needlessly
inflates the size of the image by up to three times.

When Skanlite saves an image that has been scanned in greyscale, could you
please have it save the image in greyscale?

Reproducible: Always

Steps to Reproduce:
1. Scan an image in greyscale.
2. Save the image.


Actual Results:  
3. Even though the image is in shades of grey, it contains separate red, green,
and blue channels.

Expected Results:  
3. The image should be a genuine greyscale image, with only a single channel.

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

[plasmashell] [Bug 369006] New: [Feature Request] - Drag n' Drop files and folders in -Folder Widget for current activity's documents-

[Michail Vourlakos via KDE Bugzilla]

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

Bug ID: 369006
   Summary: [Feature Request] - Drag n' Drop files and folders in
-Folder Widget for current activity's documents-
   Product: plasmashell
   Version: 5.7.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: mvourla...@gmail.com
CC: plasma-b...@kde.org

It would be very useful if the Folder widget when it is in a state that shows
the current activity's pinned documents (either when the plasmoid is on the
Desktop or when the plasmoid is as a icon in the panel) could accept dropping
documents in it...

So the user could drag a document from dolphin for example and drop it on the
Folder Widget and that document would be pinned in the current Activity if the
Folder widget has been set by the user to behave in that way...

Reproducible: Always

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

[k3b] [Bug 369005] New: not getting all the ISO

[ralph trout via KDE Bugzilla]

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

Bug ID: 369005
   Summary: not getting all the ISO
   Product: k3b
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Burning/Hardware
  Assignee: k...@kde.org
  Reporter: rtks1...@yahoo.com
CC: mich...@jabster.pl, tr...@kde.org

burning the ISO I get all but the last 32 GB, in Linux Mint there has been
someone that has found the problem he changed the VDI disk size to 20, and he
said the all works well, I am not a programmer so I don't know all of this just
what I read.  

Reproducible: Always




Hope that this helps my e-mail address is rtks1...@yahoo.com if I can give more
infro I will.

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

[kmail2] [Bug 369004] Kmail2 crash when starting up

[Vinu Moses via KDE Bugzilla]

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

--- Comment #1 from Vinu Moses  ---
Created attachment 101171
  --> https://bugs.kde.org/attachment.cgi?id=101171=edit
Crash dump file

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

[kmail2] [Bug 369004] New: Kmail2 crash when starting up

[Vinu Moses via KDE Bugzilla]

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

Bug ID: 369004
   Summary: Kmail2 crash when starting up
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: v...@cmcvellore.ac.in

Kmail2 crashes when starting up. Sometimes, the application starts, but crashes
when I try to open a particular mail.

Kmail Version 5.3.0 (QtWebEngine)
KDE Frameworks 5.26.0
Qt 5.6.1 (built against 5.6.1)
The xcb windowing system

Reproducible: Always

Steps to Reproduce:
1. Open kmail
2. Application crashes
3.

Actual Results:  
Application crashes

Expected Results:  
Application should work

A crash dump is provided at http://pastebin.com/5pZ8p7gf

When opening the application in a konsole, I get the following error:
[vinu@vinu ~]$ kmail this does not work on a KActionCollection containing
actions! KMail got signal 11 (Exiting) Dead letters dumped. nouveau: kernel
rejected pushbuf: Bad file descriptor nouveau: ch13: krec 0 pushes 1 bufs 6
relocs 0 nouveau: ch13: buf  0002 0004 0004 
nouveau: ch13: buf 0001 0007 0002 0002  nouveau: ch13:
buf 0002 0008 0002 0002  nouveau: ch13: buf 0003
000a 0002 0002  nouveau: ch13: buf 0004 0006
0004  0004 nouveau: ch13: buf 0005 0017 0002
 0002 nouveau: ch13: psh  039dc0 039e50 nouveau:
0x200203fd nouveau: 0x0001 nouveau: 0x0001 nouveau: 0x20090200 nouveau:
0x nouveau: 0x01a5 nouveau: 0x0001 nouveau: 0x0001 nouveau:
0x00e6 nouveau: 0x nouveau: 0x0001 nouveau: 0x nouveau:
0x nouveau: 0x2001054e nouveau: 0x nouveau: 0x20010487 nouveau:
0x0fac6881 nouveau: 0x8574 nouveau: 0x200308e0 nouveau: 0x0800 nouveau:
0x nouveau: 0x00542000 nouveau: 0xa00308e3 nouveau: 0x0180 nouveau:
0x3f00 nouveau: 0x3f00 nouveau: 0x800101d5 nouveau: 0x2001054f nouveau:
0x nouveau: 0x20040360 nouveau: 0x nouveau: 0x nouveau:
0x nouveau: 0x nouveau: 0x20010674 nouveau: 0x003c kmail:
pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed. QSocketNotifier:
Invalid socket 14 and type 'Read', disabling... QSocketNotifier: Invalid socket
24 and type 'Read', disabling... Unable to start Dr. Konqi [vinu@vinu ~]$

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

[kdenlive] [Bug 357722] 886b778-git-master - wrong handling of x264 crf in new render widget / options greyed out

[Pander Musubi via KDE Bugzilla]

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

Pander Musubi  changed:

   What|Removed |Added

 CC||pan...@users.sourceforge.ne
   ||t

--- Comment #2 from Pander Musubi  ---
Version Kdenlive 4:16.08.1~ubuntu16.04.1 from Kdenlive PPA still has 2 pass
disabled. When can be expected that this is solved?

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

[digikam] [Bug 369003] New: editor crash

[via KDE Bugzilla]

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

Bug ID: 369003
   Summary: editor crash
   Product: digikam
   Version: 4.12.0
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: blu...@gmail.com

Application: digikam (4.12.0)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-36-generic i686
Distribution: Linux Mint 18 Sarah

-- Information about the crash:
- What I was doing when the application crashed: clicked 
"ok" in digikam image editor after choosing B effect

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xacbfa9c0 (LWP 19436))]

Thread 5 (Thread 0x9c6fab40 (LWP 20910)):
[KCrash Handler]
#7  __memcpy_ssse3 () at ../sysdeps/i386/i686/multiarch/memcpy-ssse3.S:144
#8  0xb6d4fa68 in Digikam::DImg::putImageData(unsigned char*, bool) () from
/usr/lib/digikam/libdigikamcore.so.4.12.0
#9  0xb6e04c5a in Digikam::MixerFilter::filterImage() () from
/usr/lib/digikam/libdigikamcore.so.4.12.0
#10 0xb6da15b9 in Digikam::DImgThreadedFilter::startFilterDirectly() () from
/usr/lib/digikam/libdigikamcore.so.4.12.0
#11 0xb6dfb0dc in Digikam::BWSepiaFilter::applyChannelMixer(Digikam::DImg&) ()
from /usr/lib/digikam/libdigikamcore.so.4.12.0
#12 0xb6dfb43d in
Digikam::BWSepiaFilter::blackAndWhiteConversion(Digikam::DImg&, int) () from
/usr/lib/digikam/libdigikamcore.so.4.12.0
#13 0xb6dfba64 in Digikam::BWSepiaFilter::filterImage() () from
/usr/lib/digikam/libdigikamcore.so.4.12.0
#14 0xb6da15b9 in Digikam::DImgThreadedFilter::startFilterDirectly() () from
/usr/lib/digikam/libdigikamcore.so.4.12.0
#15 0xb6da042d in Digikam::DImgThreadedFilter::run() () from
/usr/lib/digikam/libdigikamcore.so.4.12.0
#16 0xb6f82723 in Digikam::DynamicThread::DynamicThreadPriv::run() () from
/usr/lib/digikam/libdigikamcore.so.4.12.0
#17 0xb456c3c9 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#18 0xb4579d3e in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#19 0xb392e2b5 in start_thread (arg=0x9c6fab40) at pthread_create.c:333
#20 0xb422816e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 4 (Thread 0xaa7ffb40 (LWP 19439)):
#0  0xb30855cf in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb3086014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb3086244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb46ca11c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/i386-linux-gnu/libQtCore.so.4
#4  0xb4695c5d in
QEventLoop::processEvents(QFlags) () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#5  0xb4695fee in QEventLoop::exec(QFlags) ()
from /usr/lib/i386-linux-gnu/libQtCore.so.4
#6  0xb45770eb in QThread::exec() () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#7  0xb46754a6 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#8  0xb4579d3e in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#9  0xb392e2b5 in start_thread (arg=0xaa7ffb40) at pthread_create.c:333
#10 0xb422816e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 3 (Thread 0xab135b40 (LWP 19438)):
#0  0xb7708c31 in __kernel_vsyscall ()
#1  0xb3933a8c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xb42348cd in __pthread_cond_wait (cond=0x97eec90, mutex=0x97eec78) at
forward.c:149
#3  0xb457a312 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#4  0x082256be in ?? ()
#5  0xb4579d3e in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#6  0xb392e2b5 in start_thread (arg=0xab135b40) at pthread_create.c:333
#7  0xb422816e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 2 (Thread 0xac9f7b40 (LWP 19437)):
#0  0xb7708c31 in __kernel_vsyscall ()
#1  0xb421df8f in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0xafb417cb in ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0
#3  0xb392e2b5 in start_thread (arg=0xac9f7b40) at pthread_create.c:333
#4  0xb422816e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 1 (Thread 0xacbfa9c0 (LWP 19436)):
#0  0xb7708c31 in __kernel_vsyscall ()
#1  0xb3933a8c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xb42348cd in __pthread_cond_wait (cond=0x9a20970, mutex=0x9a20958) at
forward.c:149
#3  0xb457a312 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#4  0xb456b72e in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#5  0xb456cbfc in QThreadPool::~QThreadPool() () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
#6  0xb456cc4a in QThreadPool::~QThreadPool() () from

[konsole] [Bug 361790] konsole uses 100%cpu

[via KDE Bugzilla]

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

gwar...@gmail.com changed:

   What|Removed |Added

 CC||gwar...@gmail.com

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

[kde] [Bug 369002] New: KCMInit crashes every time on F24 during autologin

[shamim . islam]

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

Bug ID: 369002
   Summary: KCMInit crashes every time on F24 during autologin
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: shamim.is...@gmail.com

Application: kdeinit5 ()

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.3-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- What I was doing when the application crashed:
I was waiting for the login to take place. Before Plasma appears

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f4f30eab700 (LWP 1954)):
#0  0x7ffe5bbe1b84 in clock_gettime ()
#1  0x7f4f50e664e6 in clock_gettime () at /lib64/libc.so.6
#2  0x7f4f51affab3 in qt_gettime() () at /lib64/libQt5Core.so.5
#3  0x7f4f51c4f869 in QTimerInfoList::updateCurrentTime() () at
/lib64/libQt5Core.so.5
#4  0x7f4f51c4fc65 in QTimerInfoList::timerWait(timespec&) () at
/lib64/libQt5Core.so.5
#5  0x7f4f51c50dac in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib64/libQt5Core.so.5
#6  0x7f4f51c50e75 in timerSourcePrepare(_GSource*, int*) () at
/lib64/libQt5Core.so.5
#7  0x7f4f4f511f59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#8  0x7f4f4f51292b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#9  0x7f4f4f512b1c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#10 0x7f4f51c5124b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#11 0x7f4f51c005ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#12 0x7f4f51a5f343 in QThread::exec() () at /lib64/libQt5Core.so.5
#13 0x7f4f53996559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#14 0x7f4f51a6399a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#15 0x7f4f5069b5ca in start_thread () at /lib64/libpthread.so.0
#16 0x7f4f50e57f6d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f4f3dad8700 (LWP 1952)):
#0  0x7f4f50e4c3ed in poll () at /lib64/libc.so.6
#1  0x7f4f52c17f80 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f4f52c19b79 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f4f4105cda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f4f51a6399a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f4f5069b5ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f4f50e57f6d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f4f538d58c0 (LWP 1950)):
[KCrash Handler]
#6  0x7f4f538301fa in _dl_lookup_symbol_x () at /lib64/ld-linux-x86-64.so.2
#7  0x7f4f53831f29 in _dl_relocate_object () at /lib64/ld-linux-x86-64.so.2
#8  0x7f4f5383ac51 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#9  0x7f4f53835c34 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#10 0x7f4f53839fe9 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#11 0x7f4f50240f09 in dlopen_doit () at /lib64/libdl.so.2
#12 0x7f4f53835c34 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#13 0x7f4f50241591 in _dlerror_run () at /lib64/libdl.so.2
#14 0x7f4f50240fa2 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#15 0x7f4f51bfe996 in QLibraryPrivate::load_sys() () at
/lib64/libQt5Core.so.5
#16 0x7f4f51bf8fd5 in QLibraryPrivate::load() () at /lib64/libQt5Core.so.5
#17 0x7f4f51bf9188 in QLibrary::resolve(char const*) () at
/lib64/libQt5Core.so.5
#18 0x7f4f51bfaf14 in QLibrary::resolve(QString const&, char const*) () at
/lib64/libQt5Core.so.5
#19 0x7f4f415e04ea in KCMInit::runModule(QString const&,
QExplicitlySharedDataPointer) () at
/lib64/libkdeinit5_kcminit_startup.so
#20 0x7f4f415e0f94 in KCMInit::runModules(int) () at
/lib64/libkdeinit5_kcminit_startup.so
#21 0x7f4f415e177e in KCMInit::KCMInit(QCommandLineParser const&) () at
/lib64/libkdeinit5_kcminit_startup.so
#22 0x7f4f415e27ba in kdemain () at /lib64/libkdeinit5_kcminit_startup.so
#23 0x55be59244f37 in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) ()
#24 0x55be59241932 in main ()

Possible duplicates by query: bug 269995, bug 264350, bug 261129, bug 255221.

Reported using DrKonqi

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

[valgrind] [Bug 369000] AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #2 from Mark Wielaard  ---
Created attachment 101170
  --> https://bugs.kde.org/attachment.cgi?id=101170=edit
Testcases for fma4 instructions.

This is an extension of the testcases for the fma4 instructions I wrote for bug
#339596.

There are tests for the 128bit and 256 bit instructions, but the 256 bit
variants are disabled for now since they aren't yet implemented.

I looked at the testcase (none/tests/arm64/fp_and_simd.c) Julian pointed out
and took the various zero/inf/nan/subnormal cases from there. But I don't
filter them out of the tests. Instead I explicitly add them and print them out
as +/-ZERO, +/-INF, NAN and SUBNORMAL. To do this correctly I had to split the
tests into ones that work on floats (ending in S) and those that work on
doubles (ending in D).

There is a little bit of duplication because you have to indicate whether the
instruction works on floats or doubles both when generating and when calling
the testcase (someone with stronger preprocessor foo might be able to "fix"
that).

Although the testcase tries to generate positive and negative NAN values the
test does not check for that (I don't believe NANs can be positive/negative).
If we would test for that the testcase would fail since we sometimes generate a
different representation for NAN that is positive/negative according to
signbit().

The testcase does produce and test for positive/negative SUBNORMALs, I am not
100% sure that makes sense. It doesn't impact the result though.

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

[kdenlive] [Bug 368984] Removing "dissolve" crashes Kdenlive

[YEK via KDE Bugzilla]

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

--- Comment #2 from YEK  ---
Jean-Baptiste,

Merci beaucoup for your extremely prompt and very helpful reply. In a nutshell,
yes, by installing Kdenlive version 16.08.1 the bug in this issue no longer
appears :)

Specifically, I uninstalled Kdenlive Version 16.04.3 using the Synaptic Package
Manager. Then I installed Kdenlive 16.08.1 using PPA:
https://kdenlive.org/download/. Then I too failed to reproduce this bug using
Kdenlive version 16.08.1

The very first time I opened a file in  Kdenlive 16.08.1 it crashed a second or
two after I began playing a file. I though, "Uh, oh. Here we go again." But
then I reopened the same file and then a few others and had no problems during
roughly one minute of very quick testing.

One of the glitches I alluded to above no longer occurs. (It had to do with
moving a clip that had, had a speed effect applied to it). I will let you know
if the other very occasional glitch I alluded to above occurs.

Also, Kdenlive 16.08.1 addressed many of the user interface design suggestions
I had alluded to above. But not all of them. I still have a handful of user
interface design suggestions. They might seem trivial to you guys, but I find
them irksome. 

Also, I suppose that Kdenlive would attract many new users if it had a "novice
mode" which contained far fewer options. (You might think of this as merely
graying out many of the current options although I would suggest they would be
actually be removed). Getting up to speed on Kdenlive was a hassle for me. It
could have been *much* easier.

See:

Design for the Novice, Configure for the Pro
https://bothsidesofthetable.com/design-for-the-novice-configure-for-the-pro-b259c6b4662a#.ht8klwvqo

and

The Paradox of Choice
https://en.wikipedia.org/wiki/The_Paradox_of_Choice

If you want me to elucidate any or all of the above ideas please let me know.

Thanks,

Yekutiel

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

[valgrind] [Bug 369000] AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

[Mark Wielaard via KDE Bugzilla]

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

--- Comment #1 from Mark Wielaard  ---
Created attachment 101169
  --> https://bugs.kde.org/attachment.cgi?id=101169=edit
Implement AMD FMA4 instructions.

This is just the FMA4 part of the patch proposed in bug #339596. The original
patch is by p4pl...@gmail.com with some minor formatting cleanups and an
explicit clearing of the the upper 128 bits of the YMM registers these
instruction operate on. It only handles the 128bit variants (that is the
explicit 0==getVexL(pfx) check in the patch).

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

[kwin] [Bug 368685] wishlist - systemsettings --> desktop behavior --> screen edges does not allow custom actions.

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #2 from Thomas Lübking  ---
xdotool, and the forum says "slide conky off screen"
in that case, you just want to bind a kwin script that does this (and skip
shell and xdotool)

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

[valgrind] [Bug 339596] AMD64 xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

Summary|AMD64 fma4 and xop  |AMD64 xop instructions
   |instructions unsupported.   |unsupported. vex amd64->IR:
   |vex amd64->IR: unhandled|unhandled instruction
   |instruction bytes: 0x8F |bytes: 0x8F 0xE8 0x78 0xCD
   |0xE8 0x78 0xCD 0xC1 0x4 |0xC1 0x4 0xC5 0xF9
   |0xC5 0xF9   |

--- Comment #22 from Mark Wielaard  ---
I split this bug into a xop (this) one and fma4 (bug #369000) one.
I had some time to look at the fma4 instructions, but not yet at the xop one.
So I split the patch in two.

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

[kontact] [Bug 369001] New: Kontact crashes upon opening

[Anthony Messina via KDE Bugzilla]

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

Bug ID: 369001
   Summary: Kontact crashes upon opening
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: amess...@messinet.com

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-200.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

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

Trying to open Kontact.  Earlier, I also got the following in dmesg:

[Sun Sep 18 11:11:31 2016] nouveau :01:00.0: kontact[3006]: Unknown handle
0x0068
[Sun Sep 18 11:11:31 2016] nouveau :01:00.0: kontact[3006]: validate_init
[Sun Sep 18 11:11:31 2016] nouveau :01:00.0: kontact[3006]: validate: -2
[Sun Sep 18 11:11:31 2016] nouveau :01:00.0: kontact[3006]: Unknown handle
0x0088
[Sun Sep 18 11:11:31 2016] nouveau :01:00.0: kontact[3006]: validate_init
[Sun Sep 18 11:11:31 2016] nouveau :01:00.0: kontact[3006]: validate: -2
[Sun Sep 18 11:46:59 2016] nouveau :01:00.0: kontact[3455]: Unknown handle
0x0037
[Sun Sep 18 11:46:59 2016] nouveau :01:00.0: kontact[3455]: validate_init
[Sun Sep 18 11:46:59 2016] nouveau :01:00.0: kontact[3455]: validate: -2
[Sun Sep 18 11:46:59 2016] nouveau :01:00.0: kontact[3455]: Unknown handle
0x0041
[Sun Sep 18 11:46:59 2016] nouveau :01:00.0: kontact[3455]: validate_init
[Sun Sep 18 11:46:59 2016] nouveau :01:00.0: kontact[3455]: validate: -2

The crash can be reproduced sometimes.

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

Thread 35 (Thread 0x7f333f7fe700 (LWP 2732)):
#0  0x7f348dd15a5e in g_source_iter_next () from /lib64/libglib-2.0.so.0
#1  0x7f348dd18354 in g_main_context_check () from /lib64/libglib-2.0.so.0
#2  0x7f348dd189a4 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f348dd18b1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f349803024b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f3497fdf5ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f3497e3e343 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f3497e4299a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f348f9c95ca in start_thread () from /lib64/libpthread.so.0
#9  0x7f3497236f6d in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7f333700 (LWP 2727)):
#0  0x7f349722b3ed in poll () from /lib64/libc.so.6
#1  0x7f348dd18a06 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f348dd18b1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f349803024b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f3497fdf5ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f3497e3e343 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f3497e4299a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f348f9c95ca in start_thread () from /lib64/libpthread.so.0
#8  0x7f3497236f6d in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f334d78e700 (LWP 2694)):
#0  0x7f348f9cebd0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3493b2ae79 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() from /lib64/libQt5WebEngineCore.so.5
#2  0x7f3493b2b540 in base::SequencedWorkerPool::Worker::Run() () from
/lib64/libQt5WebEngineCore.so.5
#3  0x7f3493b2b710 in base::SimpleThread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f3493b280fd in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f348f9c95ca in start_thread () from /lib64/libpthread.so.0
#6  0x7f3497236f6d in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f334f1e7700 (LWP 2658)):
#0  0x7f348dd17f60 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#1  0x7f348dd1892b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f348dd18b1c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f349803024b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f3497fdf5ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f3497e3e343 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f3497e4299a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f348f9c95ca in start_thread () from 

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Tristan Miller via KDE Bugzilla]

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

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

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

[valgrind] [Bug 339596] AMD64 fma4 and xop instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

[Mark Wielaard via KDE Bugzilla]

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

Mark Wielaard  changed:

   What|Removed |Added

 Blocks||369000

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

[valgrind] [Bug 369000] New: AMD64 fma4 instructions unsupported. vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9

[Mark Wielaard via KDE Bugzilla]

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

Bug ID: 369000
   Summary: AMD64 fma4 instructions unsupported. vex amd64->IR:
unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1
0x4 0xC5 0xF9
   Product: valgrind
   Version: 3.9.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: m...@redhat.com
CC: andreas.boer...@w84u.org, bellamy.b...@gmail.com,
dra...@shaw.ca, m...@redhat.com, p4pl...@gmail.com,
smj...@gmail.com, t...@compton.nu
Depends on: 339596

Lets split the fma4 and xop instructions into separate bugs & patches.
(I have already looked at the fma4 ones, but haven't had time for the xop
instructions.)

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

When running valgrind upon program startup I immediately run into an illegal
instruction.  My first action was to try using the latest source from SVN, this
however, did not help.  Below are a few extra details on the instruction in
question, my system, and anything else I can think of.

vex amd64->IR: unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5
0xF9
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==16432== valgrind: Unrecognised instruction at address 0x5adb623.
==16432==at 0x5ADB623: findChar(QChar const*, int, QChar, int,
Qt::CaseSensitivity) (in /usr/lib64/libQt5Core.so.5.4.0)
==16432==by 0x5AEC0C9: QString::split(QChar, QString::SplitBehavior,
Qt::CaseSensitivity) const (in /usr/lib64/libQt5Core.so.5.4.0)
==16432==by 0x5BC8E61:
QStandardPaths::standardLocations(QStandardPaths::StandardLocation) (in
/usr/lib64/libQt5Core.so.5.4.0)
==16432==by 0x5B7D9B7:
QStandardPaths::locate(QStandardPaths::StandardLocation, QString const&,
QFlags) (in /usr/lib64/libQt5Core.so.5.4.0)
==16432==by 0x5BB6028: QLoggingRegistry::init() (in
/usr/lib64/libQt5Core.so.5.4.0)
==16432==by 0x5C2BC8A: QCoreApplication::init() (in
/usr/lib64/libQt5Core.so.5.4.0)
==16432==by 0x5C2BEF5:
QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) (in
/usr/lib64/libQt5Core.so.5.4.0)
==16432==by 0x5560718:
QGuiApplication::QGuiApplication(QGuiApplicationPrivate&) (in
/usr/lib64/libQt5Gui.so.5.4.0)
==16432==by 0x4F8F23C: QApplication::QApplication(int&, char**, int) (in
/usr/lib64/libQt5Widgets.so.5.4.0)
==16432==by 0x40D62D: main (main.cpp:37)

I've run it through GDB and grabbed a disassembly output (More can be provided
if requested):
   0x05adb619 <+329>:mov%r8,%rax
   0x05adb61c <+332>:vmovups (%rax),%xmm0
   0x05adb620 <+336>:mov%rcx,%r8
=> 0x05adb623 <+339>:vpcomw $0x4,%xmm1,%xmm0,%xmm0
   0x05adb629 <+345>:vpmovmskb %xmm0,%esi
   0x05adb62d <+349>:test   %si,%si
   0x05adb630 <+352>:je 0x5adb610
<_ZL8findCharPK5QChariS_iN2Qt15CaseSensitivityE+320>
   0x05adb632 <+354>:bsf%esi,%esi
   0x05adb635 <+357>:sub%rdi,%rax

My system CPU is an AMD FX-8150, and Qt (where the instruction seems to
originate) is compiled with GCC 4.8.  I am running a Gentoo based system and
have used -march=native, -O2, and -fomit-frame-pointer as my only three default
CFLAGS.   

If it helps I can setup a VM with SSH access temporarily to aid in
testing/debugging of the problem.  However, for sanity sake I will only do this
Valgrind developers.

My final observersations seem to be that the XOP and FM4 instructions
introduced in the bulldozer generation AMD processors seem to cause the most
trouble.  But that may be beyond the scope of this bug report.

Reproducible: Always

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

[plasmashell] [Bug 368999] New: Folders ending with a space in their name are not retrieved from Folder View

[Mario Tosques via KDE Bugzilla]

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

Bug ID: 368999
   Summary: Folders ending with a space in their name are not
retrieved from Folder View
   Product: plasmashell
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: mario.tosq...@gmail.com
CC: plasma-b...@kde.org

Folders ending with a space in their name are not retrieved from Folder View

Reproducible: Always

Steps to Reproduce:
1. Create a folder on your Folder View or Desktop.
2. Rename it including a space as the ending character, e.g. "Test ".
3. Try to open it, e.g. click on it.

Actual Results:  
Dolphin (or any file manager) doesn't open the folder, because it is looking
for the folder *without* the ending space in its name.

Expected Results:  
Dolphin opens the folder.

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

[plasmashell] [Bug 361097] impossible rename file with long filename in desktop (with folder view)

[Mario Tosques via KDE Bugzilla]

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

Mario Tosques  changed:

   What|Removed |Added

 CC||mario.tosq...@gmail.com

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

[kdenlive] [Bug 358741] git master: extract frame exports proxy clip frame instead of original clip frame

[Wegwerf via KDE Bugzilla]

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

Wegwerf  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Wegwerf  ---
Seems that the bug is in line 989 of manager.cpp: the "resource" property seems
to always point to the proxy resource. Is it the property
"kdenlive:originalurl" that you intended to use instead?

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

[kdenlive] [Bug 358741] git master: extract frame exports proxy clip frame instead of original clip frame

[Wegwerf via KDE Bugzilla]

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

--- Comment #2 from Wegwerf  ---
This is still present with recent git master. I've tested using an .mp4 clip
and exported once with proxy enabled and once without proxy. The resulting
images are clearly different, with the proxy'd one being rather blurred.

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

[konsole] [Bug 368998] New: Konsole keeps running in background after closing window with nvidia drivers

[via KDE Bugzilla]

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

Bug ID: 368998
   Summary: Konsole keeps running in background after closing
window with nvidia drivers
   Product: konsole
   Version: 15.12.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: sheep...@gmail.com
CC: 11tet...@gmail.com, a...@batkin.net,
andr...@blochberger.net, arminn...@gmail.com,
b...@suse.com, chep...@gmail.com,
chgonzal...@gmail.com, deabruf...@gmail.com,
desint...@gmail.com, deve...@fuchsnet.ch,
elvis.angelac...@kde.org, fabrizio.rugg...@gmail.com,
freddie_cho...@op.pl, futurepi...@gmx.us,
gilb...@gmail.com, gons...@gmail.com,
hans.ullr...@loop.de, headlongfli...@rushpost.com,
illumil...@gmail.com, j...@wiele.org,
jwrings...@gmail.com, kai...@kailed.net,
kdeb...@fratti.ch, lnx...@westlot.net,
maboro...@mail.ru, males.tomlin...@gmail.com,
mich...@michaelmarley.com, m...@mgoodwin.net,
mrbo...@live.de, ober...@gmail.com, ok...@suse.de,
p...@opensuse.org, phegoru...@throwam.com,
psyri...@protonmail.com, sheep...@gmail.com,
simonandr...@gmail.com, slug...@live.co.uk,
sverre@gmail.com, tomsk_interf...@vtomske.ru,
ufosc...@gmail.com, vikran...@gmail.com,
xwaang1...@gmail.com, zmo...@hotmail.com

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

Konsole keeps running in the background after closing the window by clicking
the X in the window frame. After closing the window, the process starts to
consume a constant 25% of the CPU.

If I close Konsole by typing 'exit' in the terminal, it closes normally and
does not keep running in the background.

Reproducible: Always

Steps to Reproduce:
1. Open Konsole and do something: 
# mkdit ~/temp
# ls
2. Close Konsole by clicking the X in the window frame
3. Open ksysguard and observe that Konsole is still running, now with a 25% CPU
loading.
4. Kill the Konsole process
5. Repeat step 1
6. Close Konsole by typing 'exit' in the terminal
7. Konsole is not running in the background.

Actual Results:  
Konsole keeps running in the background after closing the window by clicking
the X in the window frame. After closing the window, the process starts to
consume a constant 25% of the CPU.

Expected Results:  
Konsole should not be running in the background after closing the window.

Plasma 5 desktop 
Frameworks 5.6.0

Further note:  if CL "exit" or "tab" X is used to close konsole, the problem
does NOT occur. - sheepmud

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

[kdenlive] [Bug 364318] git master: regression: effect is totally "ineffective" (with regression project)

[Wegwerf via KDE Bugzilla]

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

--- Comment #3 from Wegwerf  ---
I've did some more tests: when I delete both the timeline clip and its effect,
next drop the bin clip into the timeline again, and then add the blur effect,
the difference of the project XML document boils down to this ... remember that
I did drop the offending clip into the exact place in the timeline!

regression project:

  83=0;93=0,641;220=0,641;232=0

recreated:

  0=0;10=0,7;144=0,7;149=0

So, could this mean that the keyframes of the effect never get correctly
regenerated?

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

[plasmashell] [Bug 352651] Widgets get pushed off the panel despite flexible spacer [regression]

[via KDE Bugzilla]

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

--- Comment #7 from andydecle...@gmail.com ---
Thank you, I'm excited for this!

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

[plasmashell] [Bug 368997] New: 'More panel settings' button gets hidden behind a panel on the bottom of the screen

[via KDE Bugzilla]

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

Bug ID: 368997
   Summary: 'More panel settings' button gets hidden behind a
panel on the bottom of the screen
   Product: plasmashell
   Version: 5.6.2
  Platform: Other
   URL: https://imgur.com/a/JTMBC
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: tamius@gmail.com

If you have a vertical panel on the side of the monitor and another horizontal
(always-visible) panel on the bottom of the monitor, the "More panel options"
button is hidden under the horizontal panel.

Reproducible: Always

Steps to Reproduce:
0. Have one vertical panel on the side and one horizontal panel on the bottom
of the display
1. Right-click on the vertical panel
2. Click 'panel settings'

Actual Results:  
'More panel options' (bottom-most button) is hidden below the horizontal panel

Expected Results:  
Buttons should not be allowed to go behind an existing panel.

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

[krita] [Bug 349458] JJ:Add workspaces as submenu in the window menu

[Lee Zhen Yong via KDE Bugzilla]

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

Lee Zhen Yong  changed:

   What|Removed |Added

 CC||bruceoutdo...@gmail.com

--- Comment #2 from Lee Zhen Yong  ---
WIP: https://phabricator.kde.org/D2809

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

[plasmashell] [Bug 368078] Plasma-Task Manager and Wine issues

[David Brooke via KDE Bugzilla]

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

--- Comment #12 from David Brooke  ---
https://dl.dropboxusercontent.com/u/17574275/TMWP-Patch-C3770-P2.mp4

The video shows Sierra Chart being used on C3770-P2. Everything seems to be
working:
1. The panel can hide/unhide
2. The group popup
3. Grouping function
Once more Sierra Chart windows are added, the panel and group popup start to
malfunction. The panel and group popup seem to freeze, being non-accessible.
The malfunction can be corrected by:
1. Switching to another virtual desktop
2. Moving the mouse over the panel area then back to the desktop

The following post I will layout wine and Sierra Chart installation and setup
for testing.

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

[plasmashell] [Bug 352651] Widgets get pushed off the panel despite flexible spacer [regression]

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/8e1339887a01e0
   ||78b04fb18ff575c16998447665
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #6 from David Edmundson  ---
Git commit 8e1339887a01e078b04fb18ff575c16998447665 by David Edmundson.
Committed on 18/09/2016 at 14:52.
Pushed by davidedmundson into branch 'Plasma/5.8'.

Fix panel spacer

Summary:
An expanding spacer had it's minimum size set to the config.length
Allowing the panel to go from config size to infinite.

The problem is the panel length effectively defaults to the size the
spacer starts at (it gets set when we drag it into the right place)
meaning it starts off huge and can never shrink. This then leads to
applets being pushed off the panel.

We want it to be in expanding mode from 0 to config.length
and non expanding to ideally be a fixed width - though still probably
compress if it would otherwise mean the applets would overflow.

Setting the preferred size does all that implicitly; and also sets the
appropriate hint so you can have a spacer in a flexible width panel
correctly.

Reviewers: #plasma, mart

Reviewed By: mart

Subscribers: mart, plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D2785

M  +2-5applets/panelspacer/contents/ui/main.qml

http://commits.kde.org/plasma-workspace/8e1339887a01e078b04fb18ff575c16998447665

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

[dolphin] [Bug 368995] New: Crashes when right clicking on a symlink

[gait via KDE Bugzilla]

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

Bug ID: 368995
   Summary: Crashes when right clicking on a symlink
   Product: dolphin
   Version: 15.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: gasmit+...@xs4all.nl

Application: dolphin (15.12.3)

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

-- Information about the crash:
- What I was doing when the application crashed:
I clicked right on a symbolic link.
This is reproducible (it happens all the time)

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f5e0ede1700 (LWP 28905)):
#0  0x7f5e31692bfd in poll () at /lib64/libc.so.6
#1  0x7f5e266cae64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5e266caf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5e2b9d4d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5e2b97bd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5e2b79d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f5e2b7a232f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f5e272500a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f5e3169b02d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f5e1ada1700 (LWP 28904)):
#0  0x7f5e31692bfd in poll () at /lib64/libc.so.6
#1  0x7f5e2469d422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f5e2469f00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f5e1d0f63c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f5e2b7a232f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f5e272500a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f5e3169b02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f5e31dd87c0 (LWP 28903)):
[KCrash Handler]
#6  0x7f5e0704694c in  () at /usr/lib64/libQtGui.so.4
#7  0x7f5e31c3f8ea in call_init.part () at /lib64/ld-linux-x86-64.so.2
#8  0x7f5e31c3f9d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2
#9  0x7f5e31c43b08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#10 0x7f5e31c3f7a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#11 0x7f5e31c432fb in _dl_open () at /lib64/ld-linux-x86-64.so.2
#12 0x7f5e24f0002b in dlopen_doit () at /lib64/libdl.so.2
#13 0x7f5e31c3f7a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#14 0x7f5e24f005dd in _dlerror_run () at /lib64/libdl.so.2
#15 0x7f5e24f000c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2
#16 0x7f5e2b979bd0 in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f5e2b972305 in  () at /usr/lib64/libQt5Core.so.5
#18 0x7f5e2b9727ab in  () at /usr/lib64/libQt5Core.so.5
#19 0x7f5e2d72d9ea in KPluginLoader::load() () at
/usr/lib64/libKF5CoreAddons.so.5
#20 0x7f5e2d72db0a in KPluginLoader::instance() () at
/usr/lib64/libKF5CoreAddons.so.5
#21 0x7f5e2d72db47 in KPluginLoader::factory() () at
/usr/lib64/libKF5CoreAddons.so.5
#22 0x7f5e319b52d9 in  () at /usr/lib64/libkdeinit5_dolphin.so
#23 0x7f5e319b58a2 in  () at /usr/lib64/libkdeinit5_dolphin.so
#24 0x7f5e319b6eed in  () at /usr/lib64/libkdeinit5_dolphin.so
#25 0x7f5e319ace46 in  () at /usr/lib64/libkdeinit5_dolphin.so
#26 0x7f5e2b9ad73f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#27 0x7f5e31374f64 in DolphinView::requestContextMenu(QPoint const&,
KFileItem const&, QUrl const&, QList const&) () at
/usr/lib64/libdolphinprivate.so.5
#28 0x7f5e313530ff in DolphinView::slotItemContextMenuRequested(int,
QPointF const&) () at /usr/lib64/libdolphinprivate.so.5
#29 0x7f5e2b9ad73f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#30 0x7f5e31373db6 in KItemListController::itemContextMenuRequested(int,
QPointF const&) () at /usr/lib64/libdolphinprivate.so.5
#31 0x7f5e313167e4 in
KItemListController::mousePressEvent(QGraphicsSceneMouseEvent*, QTransform
const&) () at /usr/lib64/libdolphinprivate.so.5
#32 0x7f5e313158fb in KItemListController::processEvent(QEvent*, QTransform
const&) () at /usr/lib64/libdolphinprivate.so.5
#33 0x7f5e313273c2 in KItemListView::event(QEvent*) () at
/usr/lib64/libdolphinprivate.so.5
#34 0x7f5e2caf4e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#35 0x7f5e2caf9cc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#36 0x7f5e2b97de95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at 

[plasmashell] [Bug 368078] Plasma-Task Manager and Wine issues

[David Brooke via KDE Bugzilla]

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

--- Comment #11 from David Brooke  ---
I have tested the patch on three computers (see below) and the grouping
function works with notepad and Sierra Chart programs.
1. I opened 40 windows of notepad without issue.
2. Sierra Chart has a limit to the number of windows that can be opened before
a "freezing" issue occurs which I will explain further in the next post. The
limited number of windows is less than the current ability of Plasma 5.6 of
which an upper limit has not been tested.

Partition2 or C3770-P2
Gentoo AMD64 Stable
Plasma 5.7.95
Frameworks 5.26
KDE Apps 16.08.1
QT5 - version 5.6.1
xf86-video-intel 2.99.917-r2

Partition2 or C4790K-P2
Gentoo AMD64 Stable
Plasma 5.7.95
Frameworks 5.26
KDE Apps 16.08.1
QT5 - version 5.6.1
xf86-video-intel 2.99.917-r2

Partition1 or C4790-P1
Gentoo AMD64 Stable
Plasma 5.7.5
Frameworks 5.26
KDE Apps 16.08.1
QT5 - version 5.6.1
nvidia-drivers 361.28

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Thomas Schmitt via KDE Bugzilla]

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

--- Comment #26 from Thomas Schmitt  ---
I should mention that session 2 tests with growisofs -M instead of -Z failed.

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

[kde] [Bug 368994] New: Baloo crashed while a file has been transfered

[Axel Wintermann via KDE Bugzilla]

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

Bug ID: 368994
   Summary: Baloo crashed while a file has been transfered
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bortech...@gmail.com

Application: baloo_file (5.21.0)

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

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

I've transfered a file, and baloo crashed. I have this crash several times
after  each system reboot

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6b07a78780 (LWP 2695))]

Thread 2 (Thread 0x7f69bc95e700 (LWP 3050)):
#0  0x7f6b01fb4d14 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f6b01f724a0 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f6b01f72d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f6b01f72f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f6b0619cd8b in QEventDispatcherGlib::processEvents
(this=0x7f69b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f6b06143d53 in QEventLoop::exec (this=this@entry=0x7f69bc95dd20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x0041531b in Baloo::FileContentIndexer::run (this=0x7687b0) at
/usr/src/debug/baloo-5.21.0/src/file/filecontentindexer.cpp:73
#7  0x7f6b05f67382 in QThreadPoolThread::run (this=0x867290) at
thread/qthreadpool.cpp:93
#8  0x7f6b05f6a32f in QThreadPrivate::start (arg=0x867290) at
thread/qthread_unix.cpp:331
#9  0x7f6b0458f0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f6b0556c02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f6b07a78780 (LWP 2695)):
[KCrash Handler]
#6  0x7f6b0326e25c in mdb_get () from /usr/lib64/liblmdb-0.9.14.so
#7  0x7f6b0683f4cd in Baloo::IdTreeDB::get (this=this@entry=0x7ffd0604c030,
docId=docId@entry=0) at /usr/src/debug/baloo-5.21.0/src/engine/idtreedb.cpp:82
#8  0x7f6b0683cdc0 in Baloo::DocumentUrlDB::getId
(this=this@entry=0x7ffd0604c0a0, docId=0, fileName=...) at
/usr/src/debug/baloo-5.21.0/src/engine/documenturldb.cpp:186
#9  0x7f6b0684e949 in Baloo::Transaction::documentId
(this=this@entry=0x7ffd0604c120, path=...) at
/usr/src/debug/baloo-5.21.0/src/engine/transaction.cpp:121
#10 0x0041d453 in Baloo::MetadataMover::removeMetadata
(this=this@entry=0x795600, tr=tr@entry=0x7ffd0604c120, url=...) at
/usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:74
#11 0x0041de02 in Baloo::MetadataMover::moveFileMetadata
(this=0x795600, from=..., to=...) at
/usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:53
#12 0x7f6b0617573f in QtPrivate::QSlotObjectBase::call (a=0x7ffd0604c290,
r=0x7ffd0604c9f0, this=0x751fa0) at ../../src/corelib/kernel/qobject_impl.h:124
#13 QMetaObject::activate (sender=sender@entry=0x7afa60,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7ffd0604c290) at kernel/qobject.cpp:3698
#14 0x7f6b061762e7 in QMetaObject::activate (sender=sender@entry=0x7afa60,
m=m@entry=0x638bc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffd0604c290)
at kernel/qobject.cpp:3578
#15 0x0041e75a in KInotify::moved (this=this@entry=0x7afa60, _t1=...,
_t2=...) at /usr/src/debug/baloo-5.21.0/build/src/file/moc_kinotify.cpp:330
#16 0x004228f9 in KInotify::slotEvent (this=,
socket=) at
/usr/src/debug/baloo-5.21.0/src/file/kinotify.cpp:421
#17 0x7f6b0617573f in QtPrivate::QSlotObjectBase::call (a=0x7ffd0604c550,
r=0x7afa60, this=0x798aa0) at ../../src/corelib/kernel/qobject_impl.h:124
#18 QMetaObject::activate (sender=sender@entry=0x773210,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffd0604c550) at kernel/qobject.cpp:3698
#19 0x7f6b061762e7 in QMetaObject::activate (sender=sender@entry=0x773210,
m=m@entry=0x7f6b06594780 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd0604c550)
at kernel/qobject.cpp:3578
#20 0x7f6b061f78ee in QSocketNotifier::activated (this=this@entry=0x773210,
_t1=13) at .moc/moc_qsocketnotifier.cpp:134
#21 0x7f6b06182a89 in QSocketNotifier::event (this=0x773210,
e=0x7ffd0604c6c0) at kernel/qsocketnotifier.cpp:260
#22 0x7f6b0614618d in QCoreApplication::notify (this=,
receiver=, event=) at
kernel/qcoreapplication.cpp:1038
#23 0x7f6b06145e95 in QCoreApplication::notifyInternal
(this=0x7ffd0604c960, receiver=0x773210, event=event@entry=0x7ffd0604c6c0) at
kernel/qcoreapplication.cpp:965
#24 0x7f6b0619dca5 in 

[cantor] [Bug 368986] Shouldn't the Julia back-end be an optional back-end ?

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

   Assignee|fil...@kde.org  |ivan.lakhta...@gmail.com
 CC||ivan.lakhta...@gmail.com
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Filipe Saraiva  ---
Hi Raymond, this problem was detected some weeks ago. Currently Ivan, the julia
backend developer, is working to fix it. Follow the work to fix it in [1].

[1] https://phabricator.kde.org/D2575

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

[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)

[Thomas Schmitt via KDE Bugzilla]

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

--- Comment #25 from Thomas Schmitt  ---
Hi,

i tested growisofs and separately running mkisofs/genisoimage/xorrisofs
on DVD+RW to show how i imagine this could be done in K3B:

---

# Create some input files
  echo file1 >file1
  echo file2_a_bit_larger >file2

# First session 

  genisoimage -R file1 | \
  growisofs -Z /dev/sr0=/dev/fd/0 

# This run reports:  176 extents written (0 MB)
# So i choose a deliberately high Next Writable Address:  1024

# mount(8) and ls(1) show one file in the ISO
#   -rw-r--r-- 1 thomas thomas 6 Sep 18 14:59 file1

# Second session (after unmounting /dev/sr0, of course)

  genisoimage -M /dev/sr0 -C 0,1024 -R file2 | \
  growisofs -use-the-force-luke=seek=1024 -C 0,1024 -Z /dev/sr0=/dev/fd/0 

# mount(8) and ls(1) show both files in the ISO
#   -rw-r--r-- 1 thomas thomas  6 Sep 18 14:59 file1
#   -rw-r--r-- 1 thomas thomas 19 Sep 18 14:59 file2

---

Both are needed: -use-the-force-luke=seek=1024 and -C 0,1024
Else mount(8) and ls(1) will show only file1 after the second session.
(I.e. without -C, growisofs does not update the superblock at offset 0.)

In the second run growisofs reports:
  About to execute 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=64'
  builtin_dd: 176*2KB out @ average 0.1x1352KBps
genisoimage reports:
  1200 extents written (2 MB)
We learn that genisoimage added 1024 and 176 in its message.
Suitable Next Writable Address would be any properly aligned value
not smaller than 1200.

So it would work with growisofs if K3B would compute its own Next Writable
Address and force it on genisoimage and growisofs.
For the sake of BD-RE performance and compatibility to my software i
sincerely advise to round up to full multiples of 32 blocks.
growisofs rounds to 16, which is not necessary aligned to a BD data
unit of 32 (aka "Cluster"). DVD has 16 blocks per "ECC Block".


Being selfish i show the cdrskin way:
---

# Pseudo-blank the medium, so that cdrskin will not append its
# first session to the existing ISO filesystem.
# The same command blanks CD-RW and unformatted DVD-RW.
# It tolerates blank media and fails on non-blank non-blankable media.

  cdrskin --grow_overwriteable_iso dev=/dev/sr0 -v blank=as_needed

# First session. 
# Option --grow_overwriteable_iso lets cdrskin tolerate -multi on DVD+RW.
# (One cannot close a DVD+RW. So -multi is normally rejected.)

  genisoimage -R file1 | \
  cdrskin --grow_overwriteable_iso -multi dev=/dev/sr0 -v -eject -

# Inquire values for genisoimage -C.
# Option --grow_overwriteable_iso lets cdrskin inspect the ISO.
# Nevertheless this works too on sequential media:
#   CD-R[W], DVD-R[W], DVD+R, non-pseudo-overwritable BD-R.

  C_VALUES=$(cdrskin dev=/dev/sr0 --grow_overwriteable_iso -msinfo)

# Second session. Option --grow_overwriteable_iso lets cdrskin direct
# the burn run to the same address as predicted by the previous run
# and handed to genisoimage.

  genisoimage -M /dev/sr0 -C "$C_VALUES" -R file2 | \
  cdrskin --grow_overwriteable_iso -multi dev=/dev/sr0 -v -eject -

---

The advantage of this is that K3B does not have to inspect the ISO
and can operate any kind of media by the same cdrskin runs.


Have a nice day :)

Thomas

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

[kwin] [Bug 368993] New: Kwin crash every time

[Damian via KDE Bugzilla]

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

Bug ID: 368993
   Summary: Kwin crash  every time
   Product: kwin
   Version: 5.7.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dbolt...@gmail.com

Application: kwin_x11 (5.7.4)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: Start session, ktorrent and
firefox. every time after few minutes crash notification appears

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7f60e7fff700 (LWP 2289)):
#0  0x7f61a2522281 in clock_gettime () from /lib64/libc.so.6
#1  0x7f619fa0fd96 in qt_clock_gettime (ts=0x7f60e7ffeb10, clock=) at tools/qelapsedtimer_unix.cpp:105
#2  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#4  0x7f619fb8f639 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f60e00010f8) at kernel/qtimerinfo_unix.cpp:84
#5  0x7f619fb8fbe5 in QTimerInfoList::timerWait
(this=this@entry=0x7f60e00010f8, tm=...) at kernel/qtimerinfo_unix.cpp:381
#6  0x7f619fb8f212 in QEventDispatcherUNIX::processEvents
(this=0x7f60e007a6a0, flags=...) at kernel/qeventdispatcher_unix.cpp:594
#7  0x7f619fb396fa in QEventLoop::exec (this=this@entry=0x7f60e7ffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7f619f95f3c3 in QThread::exec (this=this@entry=0x2e5eb90) at
thread/qthread.cpp:500
#9  0x7f6199ba60a5 in QQmlThreadPrivate::run (this=0x2e5eb90) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/qml/qml/ftw/qqmlthread.cpp:141
#10 0x7f619f9642e8 in QThreadPrivate::start (arg=0x2e5eb90) at
thread/qthread_unix.cpp:341
#11 0x7f619b074454 in start_thread () from /lib64/libpthread.so.0
#12 0x7f61a25153ff in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f616700 (LWP 1633)):
#0  0x7f619b07a10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f619eaee7f4 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f619eaee839 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f619b074454 in start_thread () from /lib64/libpthread.so.0
#4  0x7f61a25153ff in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f617bfff700 (LWP 1613)):
#0  0x7f619f95c419 in
std::__atomic_base::compare_exchange_strong (__m2=,
__m1=std::memory_order_release, __p2=0x0, __p1=@0x7f617bffeaa8: 0x1,
this=0x20d1928) at /usr/include/c++/6/bits/atomic_base.h:752
#1  std::atomic::compare_exchange_strong
(__m=std::memory_order_release, __p2=0x0, __p1=@0x7f617bffeaa8: 0x1,
this=0x20d1928) at /usr/include/c++/6/atomic:475
#2  QAtomicOps::testAndSetRelease
(currentValue=, newValue=0x0, expectedValue=0x1,
_q_value=...) at ../../src/corelib/arch/qatomic_cxx11.h:167
#3  QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=, this=0x20d1928) at
../../src/corelib/thread/qbasicatomic.h:278
#4  QBasicMutex::fastTryUnlock (current=, this=0x20d1928) at
thread/qmutex.h:85
#5  QMutex::unlock (this=this@entry=0x20d1928) at thread/qmutex.cpp:271
#6  0x7f619fb3d73b in QMutexLocker::unlock (this=) at
../../src/corelib/thread/qmutex.h:138
#7  QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../src/corelib/thread/qmutex.h:132
#8  QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x20d1900) at
kernel/qcoreapplication.cpp:1536
#9  0x7f619fb8f152 in QEventDispatcherUNIX::processEvents
(this=0x7f6178c0, flags=...) at kernel/qeventdispatcher_unix.cpp:579
#10 0x7f619fb396fa in QEventLoop::exec (this=this@entry=0x7f617bffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#11 0x7f619f95f3c3 in QThread::exec (this=this@entry=0x206d540) at
thread/qthread.cpp:500
#12 0x7f6199ba60a5 in QQmlThreadPrivate::run (this=0x206d540) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/qml/qml/ftw/qqmlthread.cpp:141
#13 0x7f619f9642e8 in QThreadPrivate::start (arg=0x206d540) at
thread/qthread_unix.cpp:341
#14 0x7f619b074454 in start_thread () from /lib64/libpthread.so.0
#15 0x7f61a25153ff in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f6182f1a700 (LWP 1601)):
#0  0x7f619fb8f149 in QEventDispatcherUNIX::processEvents
(this=0x7f617c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:579
#1  0x7f619fb396fa in QEventLoop::exec (this=this@entry=0x7f6182f19c50,
flags=..., 

[plasmashell] [Bug 364529] Wayland : No icon nor title in Task manager for Systemsettings

[via KDE Bugzilla]

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

--- Comment #2 from tro...@free.fr ---
Yeah I think non-Qt applications don't have icon.

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

[kdevelop] [Bug 368855] changing files via git (rebase, checkout) causes 100% CPU usage on 2 cores

[Rolf Eike Beer via KDE Bugzilla]

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

Rolf Eike Beer  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #2 from Rolf Eike Beer  ---
Thread 14 (Thread 0x7fe1a8c3f700 (LWP 10656)):
#0  0x7fe203b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe1fe47f86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fe1fe47f899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fe209ddc02d in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7fe1aa5ab700 (LWP 10635)):
#0  0x7fe209dd3bfd in poll () at /lib64/libc.so.6
#1  0x7fe202e94e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe202e94f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe20a700d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fe20a6a7d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fe20a4c961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fe20a4ce32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fe209ddc02d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fe18bfff700 (LWP 10528)):
#0  0x7fe209dd3bfd in poll () at /lib64/libc.so.6
#1  0x7fe202e94e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe202e94f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe20a700d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fe20a6a7d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fe20a4c961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fe20a4ce32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fe209ddc02d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fe1aadac700 (LWP 10515)):
#0  0x7fe203b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe20a4cf34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe1ff2b465f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe1ff2b843a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe1ff2b26cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe1ff2b6005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe20a4ce32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fe209ddc02d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fe1ab5ad700 (LWP 10514)):
#0  0x7fe203b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe20a4cf34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe1ff2b465f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe1ff2b843a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe1ff2b26cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe1ff2b8481 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe1ff2b26cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fe1ff2b6005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fe20a4ce32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fe209ddc02d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fe1abdae700 (LWP 10513)):
#0  0x7fe203b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe20a4cf34b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe1ff2b465f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe1ff2b843a in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe1ff2b26cb in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe1ff2b6005 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe20a4ce32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7fe209ddc02d in clone 

[kdenlive] [Bug 368799] Tooltips show in yellow background and white color, it's impossible to read to them.

[Alexandre Bento Freire via KDE Bugzilla]

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

--- Comment #4 from Alexandre Bento Freire  ---
Thanks. I installed gnome-color-chooser, and found a background color that is
readable with white and black foreground, since as you mention changing the
foreground as no effect.
This all the other programs have black foreground, and kdenlive uses white
foreground, but is a solution, and it works.

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

[digikam] [Bug 368444] Not supporting XCF anymore

[via KDE Bugzilla]

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

--- Comment #5 from caulier.gil...@gmail.com ---
Git commit bbcb98526b5878491a96e440ae534a1637e4ef8e by Gilles Caulier.
Committed on 18/09/2016 at 12:47.
Pushed by cgilles into branch 'master'.

add extra Qimage Loaders for Windows and MacOS

M  +1-0project/macports/02-build-extralibs.sh
M  +1-0project/mxe/02-build-extralibs.sh

http://commits.kde.org/scratch/mwiesweg/digikam-sc/bbcb98526b5878491a96e440ae534a1637e4ef8e

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

[krita] [Bug 368992] New: Crash when accidentally drawing over the ruler (GDB backtrace)

[wolthera via KDE Bugzilla]

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

Bug ID: 368992
   Summary: Crash when accidentally drawing over the ruler (GDB
backtrace)
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: griffinval...@gmail.com

I was drawing, accidentally drawed over the ruler-canvas decoration. My guess
is that Krita tried to produce a guide but then got deeply confused.

Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
KUndo2Command::timedMergeWith (this=0x16e7a480, other=0xe5) at
/home/krita/kde/src/krita/libs/kundo2/kundo2stack.cpp:349
349if(other->timedId() == this->timedId() && other->timedId()!=-1 )
(gdb) thread apply all backtrace

Thread 463 (Thread 0x7fff817c8700 (LWP 13253)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x75531738 in QWaitCondition::wait(QMutex*, unsigned long) () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7552d467 in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75530c89 in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeec836fa in start_thread (arg=0x7fff817c8700) at
pthread_create.c:333
#5  0x74c2cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 462 (Thread 0x7fff7f365700 (LWP 13252)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x75531738 in QWaitCondition::wait(QMutex*, unsigned long) () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7552d467 in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x75530c89 in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeec836fa in start_thread (arg=0x7fff7f365700) at
pthread_create.c:333
#5  0x74c2cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fff997cd700 (LWP 10018)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x755317eb in QWaitCondition::wait(QMutex*, unsigned long) () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x76707aa2 in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Widgets.so.5
#3  0x75530c89 in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#4  0x7fffeec836fa in start_thread (arg=0x7fff997cd700) at
pthread_create.c:333
#5  0x74c2cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fff9a115700 (LWP 10017)):
#0  0x74bf18dd in nanosleep () at ../sysdeps/unix/syscall-template.S:84
#1  0x755d8f7d in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x75530138 in QThread::msleep(unsigned long) () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5

#3  0x72e395ca in KisTileDataSwapper::run (this=0x732f2780
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>)
at
/home/krita/kde/src/krita/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:97
#4  0x75530c89 in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#5  0x7fffeec836fa in start_thread (arg=0x7fff9a115700) at
pthread_create.c:333
#6  0x74c2cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fff9a916700 (LWP 10016)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x755317eb in QWaitCondition::wait(QMutex*, unsigned long) () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#2  0x7552ae8b in QSemaphore::acquire(int) () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#3  0x72e1f79e in KisTileDataPooler::waitForWork (this=0x732f2740
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>)
at /home/krita/kde/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:165
#4  0x72e1ff5a in KisTileDataPooler::run (this=0x732f2740
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>)
at /home/krita/kde/src/krita/libs/image/tiles3/kis_tile_data_pooler.cc:187
#5  0x75530c89 in ?? () from
/home/krita/Qt/5.6/gcc_64/lib/libQt5Core.so.5
#6  0x7fffeec836fa in start_thread (arg=0x7fff9a916700) at
pthread_create.c:333
#7  0x74c2cb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fffd882a700 (LWP 10008)):
#0  0x74c20e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffee35839c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
---Type  to continue, or q  to quit---
#2  0x7fffee3584ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  

[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner

[Pablo via KDE Bugzilla]

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

Pablo  changed:

   What|Removed |Added

 CC||pablow.1...@gmail.com

--- Comment #20 from Pablo  ---
*** Bug 368665 has been marked as a duplicate of this bug. ***

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

[krunner] [Bug 368665] krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or typing something)

[Pablo via KDE Bugzilla]

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

Pablo  changed:

   What|Removed |Added

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

--- Comment #3 from Pablo  ---
Sorry for wasting your time. I've found the Bug Report
"https://bugs.kde.org/show_bug.cgi?id=364342; which didn't come up in my first
google search. If I disable the Contacts Plugin, krunner won't crash anymore.
I'll be waiting the 16.04.2 update.

Thanks for your hard work!

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

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

[plasmashell] [Bug 367822] After update to kernel 4.7 no panel after plasma login

[MikeC via KDE Bugzilla]

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

--- Comment #8 from MikeC  ---
I have finally been able to resolve this problem.  It turned out that way back
in the history of my machine when I originally set it up, I had used a DVI
monitor, and then a few days later plugged in an HDMI monitor and had the two
monitors connected for  a short period whilst I configured the displays, and
HDMI monitor after that has been the only monitor on the machine for the
following three years until now.  However removing the original DVI monitor
that was originally plugged in as a second monitor gave a phantom screen, that
was presented to KDE4 and then later to plasma as a unified screen output, and
the original panel that was assigned to the old DVI monitor had been displayed
within plasma just fine on the primary HDMI monitor until the kernel was
upgraded to the 4.7 series. At that point the phantom monitor attached to the
eDP1 screen was where the panel was being displayed and therefore no longer
visible on the primary HDMI display.
So in order to resolve this issue I logged on with kernel 4.6.4-1 running with
the erroneously assigned panel still displayed on the primary real monitor.
Then unlocking the plasma widgets, and removing the panel using the panel
controls, I then created a new default panel, configured it, and locked the
widgets again. Logging out and back in displayed the newly created panel
correctly on the primary monitor.

Then adjusting the xorg config to include the following lines allowed logging
out and back in with no phantom screen detected:

Section "Monitor"
Identifier "HDMI2"
Option "Enable"  "true"
EndSection

Section "Monitor"
Identifier "eDP1"
Option "ignore"  "true"
EndSection

Then upgrading the kernel to 4.7.4-1 and rebooting, allows the login from the
sddm screen to proceed normally and completes without any problem including
having the panel displayed on the only screen detected by kwin.
The xrandr output before and after these changes shows that prior to the steps
detailed above there was a phantom eDP1 screen, but afterwards there is only a
single HDMI2 screen - and now all is well.

I also found that Martin Graeslin has commented on the multi-screen issue in
the past at 
https://blog.martin-graesslin.com/blog/2015/10/some-thoughts-on-the-quality-of-plasma-5/
and there is another post also mentioning this issue at:
https://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/

So although the problem is resolved in my case, it looks like there are still
possible remnants of problems for systems where more than one monitor has been
connected and during multi-screen operation some screen configs have been
changed which can become an issue when the additional monitors are later
removed.

Please therefore close this bug even though it is marked as a duplicate.

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

[plasmashell] [Bug 368991] New: Shell crash while typing into application menu

[Ludvig Böklin via KDE Bugzilla]

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

Bug ID: 368991
   Summary: Shell crash while typing into application menu
   Product: plasmashell
   Version: 5.7.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ludvig.bok...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.5)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.1.31-30-pv x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

I searched for an application in application menu, which resulted in a brief
pause and a following crash. It restarted thereafter seemingly without issue.


- Unusual behavior I noticed:

Possibly related: I tried searching in krunner first, and it crashed (did not
restart, but on manual start it ran fine and without any error output in
terminal).

Possibly helpful info: Search is disabled in system settings because baloo took
up too many resources (X froze and stuttered often, as well as taking up R/W
resources making navigating the file system unresponsive at times) and never
stopped doing so even after letting it run for hours.

The crash does not seem to be reproducible.

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

Thread 32 (Thread 0x7f462e7fc700 (LWP 26236)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f475e33050b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x601c260) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x37dafb0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f468fbea3fb in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x37bd830, th=) at
/usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:594
#4  0x7f468fbeb3ff in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x37bd830,
th=th@entry=0x7f4624002d90, threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at
/usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:554
#5  0x7f468fbeedca in ThreadWeaver::WorkingHardState::applyForWork
(this=0x5ea96a0, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/workinghardstate.cpp:66
#6  0x7f468fbe942b in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:568
#7  0x7f468fbeee12 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x5ea96a0, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/workinghardstate.cpp:73
#8  0x7f468fbe942b in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:568
#9  0x7f468fbeee12 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x5ea96a0, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/workinghardstate.cpp:73
#10 0x7f468fbe942b in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:568
#11 0x7f468fbeee12 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x5ea96a0, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/workinghardstate.cpp:73
#12 0x7f468fbe942b in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:568
#13 0x7f468fbeee12 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x5ea96a0, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/workinghardstate.cpp:73
#14 0x7f468fbe942b in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:568
#15 0x7f468fbeee12 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x5ea96a0, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/workinghardstate.cpp:73
#16 0x7f468fbe942b in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f4624002d90, wasBusy=) at
/usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:568
#17 0x7f468fbeca26 in ThreadWeaver::Thread::run (this=0x7f4624002d90) at
/usr/src/debug/threadweaver-5.26.0/src/thread.cpp:103
#18 0x7f475e32f899 in QThreadPrivate::start (arg=0x7f4624002d90) at
thread/qthread_unix.cpp:344
#19 0x7f475d4390a4 in start_thread (arg=0x7f462e7fc700) at
pthread_create.c:309
#20 0x7f475dc3802d in clone () at

[frameworks-plasma] [Bug 367828] NO panel available

[MikeC via KDE Bugzilla]

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

--- Comment #21 from MikeC  ---
I have finally been able to resolve this problem.  It turned out that way back
in the history of my machine when I originally set it up, I had used a DVI
monitor, and then a few days later plugged in an HDMI monitor and had the two
monitors connected for  a short period whilst I configured the displays, and
HDMI monitor after that has been the only monitor on the machine for the
following three years until now.  However removing the original DVI monitor
that was originally plugged in as a second monitor gave a phantom screen, that
was presented to KDE4 and then later to plasma as a unified screen output, and
the original panel that was assigned to the old DVI monitor had been displayed
within plasma just fine on the primary HDMI monitor until the kernel was
upgraded to the 4.7 series. At that point the phantom monitor attached to the
eDP1 screen was where the panel was being displayed and therefore no longer
visible on the primary HDMI display.
So in order to resolve this issue I logged on with kernel 4.6.4-1 running with
the erroneously assigned panel still displayed on the primary real monitor.
Then unlocking the plasma widgets, and removing the panel using the panel
controls, I then created a new default panel, configured it, and locked the
widgets again. Logging out and back in displayed the newly created panel
correctly on the primary monitor.

Then adjusting the xorg config to include the following lines allowed logging
out and back in with no phantom screen detected:

Section "Monitor"
Identifier "HDMI2"
Option "Enable"  "true"
EndSection

Section "Monitor"
Identifier "eDP1"
Option "ignore"  "true"
EndSection

Then upgrading the kernel to 4.7.4-1 and rebooting, allows the login from the
sddm screen to proceed normally and completes without any problem including
having the panel displayed on the only screen detected by kwin.
The xrandr output before and after these changes shows that prior to the steps
detailed above there was a phantom eDP1 screen, but afterwards there is only a
single HDMI2 screen - and now all is well.

I also found that Martin Graeslin has commented on the multi-screen issue in
the past at 
https://blog.martin-graesslin.com/blog/2015/10/some-thoughts-on-the-quality-of-plasma-5/
and there is another post also mentioning this issue at:
https://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/

So although the problem is resolved in my case, it looks like there are still
possible remnants of problems for systems where more than one monitor has been
connected and during multi-screen operation some screen configs have been
changed which can become an issue when the additional monitors are later
removed.

Whether any progress can be made by the original poster of this bug report
using a similar approach to that which fixed my issue will need to be answered
by Leslie Zhai.

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

[krusader] [Bug 297079] "open with"->"other" context menu parameter behaviour (%U)

[Alex Bikadorov via KDE Bugzilla]

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

--- Comment #14 from Alex Bikadorov  ---
I mean "open with -> other", this works for me. But this could be caused by
different versions, Okular 16.08.1, KF5 5.25.0 here.

Anyway, once fixed for Kate it will also be solved for Okular.

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

[krunner] [Bug 368665] krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or typing something)

[Pablo via KDE Bugzilla]

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

--- Comment #2 from Pablo  ---
Created attachment 101168
  --> https://bugs.kde.org/attachment.cgi?id=101168=edit
The output from konsole

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

[krunner] [Bug 368665] krunner crash: radeon: failed to allocate buffer (by just presing alt+f2 or typing something)

[Pablo via KDE Bugzilla]

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

--- Comment #1 from Pablo  ---
Created attachment 101167
  --> https://bugs.kde.org/attachment.cgi?id=101167=edit
krunner crash

A short video of krunner crashing when trying to do a simple sum. This crash
situation happens always.

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

[plasma-nm] [Bug 368990] New: Applet shows "disconnected" icon although I am connected

[Igor Poboiko via KDE Bugzilla]

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

Bug ID: 368990
   Summary: Applet shows "disconnected" icon although I am
connected
   Product: plasma-nm
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: igor.pobo...@gmail.com
CC: lu...@kde.org

The plasma-nm applet still shows a "WiFi Disconnected" icon in the system tray
(the one with yellow "?" sign), although I am connected to wifi.
However, It shows a correct icon and "Connected to ..." message in the tooltip,
and in the applet itself.

Reproducible: Always




This is clearly a regression, it appeared after an upgrade to Plasma 5.7.95.

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

[plasmashell] [Bug 362657] Device Notifier stealing keyboard focus when notification is displayed.

[Valdas via KDE Bugzilla]

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

Valdas  changed:

   What|Removed |Added

 CC||zmo...@hotmail.com

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

[plasmashell] [Bug 364529] Wayland : No icon nor title in Task manager for Systemsettings

[Igor Poboiko via KDE Bugzilla]

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

Igor Poboiko  changed:

   What|Removed |Added

 CC||igor.pobo...@gmail.com

--- Comment #1 from Igor Poboiko  ---
I can confirm this; I am also using Wayland and most recent Plasma (5.7.95). 
This is only application with such weird behavior.

However, dozen of other applications don't show icon too (but they do show
title). Several examples are: Chromium, Skype, Inkscape, Gimp, Firefox, LyX
(Qt4), Okular. 
Several examples of applications that work correctly are: Dolphin, Gwenview,
Konsole.

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

[krunner] [Bug 366726] KRunner always shows up under top panel

[Igor Poboiko via KDE Bugzilla]

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

--- Comment #3 from Igor Poboiko  ---
Created attachment 101166
  --> https://bugs.kde.org/attachment.cgi?id=101166=edit
Plasma 5.7.95 update

Ping!

With Plasma 5.8 Beta 1 it's even worse: the KRunner window apparently became
smaller and now it completely hides under the panel. It is even impossible to
say whether it has shown up or not (apart from typing and hoping that it got
the focus).

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

[kwin] [Bug 368989] New: Alt+F4 shortcut works only with XWayland windows

[Igor Poboiko via KDE Bugzilla]

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

Bug ID: 368989
   Summary: Alt+F4 shortcut works only with XWayland windows
   Product: kwin
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: igor.pobo...@gmail.com

The summary speaks for itself. Dolphin/Okular/Systemsettings (which, I assume,
work natively with Wayland now) ignore Alt+F4 shortcut; while LyX (Qt4 version)
and Chromium does work.

Funny thing, GTK applications (I checked GIMP and Inkscape) ignore it too. Does
it mean that they run natively now?

Reproducible: Always

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

[bugs.kde.org] [Bug 368988] New: "My Requests" menu always shows empty list

[Igor Poboiko via KDE Bugzilla]

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

Bug ID: 368988
   Summary: "My Requests" menu always shows empty list
   Product: bugs.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sysad...@kde.org
  Reporter: igor.pobo...@gmail.com
CC: she...@kde.org

The bug is in the title: the "My Requests" link on the top panel doesn't
actually show my requests, and prints "No requests" instead.

(I'm pretty sure I have plenty of bugs reported; e.g. Bug 366726).

Reproducible: Always

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

[frameworks-kactivities] [Bug 347613] recent documents appear though disabled in options

[Ivan Čukić via KDE Bugzilla]

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

Ivan Čukić  changed:

   What|Removed |Added

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

--- Comment #2 from Ivan Čukić  ---
Which version of Plasma is this?

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