[k3b] [Bug 382776] New: Enable "apply" button only when some setting is changed

[Dr . Chapatin]

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

Bug ID: 382776
   Summary: Enable "apply" button only when some setting is
changed
   Product: k3b
   Version: 17.04.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: GUI/Usability
  Assignee: k...@kde.org
  Reporter: yy...@gmx.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

"Apply" button from the settings window is always enabled.
I think my summary describes the correct behavior.

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

[k3b] [Bug 382775] New: Settings window has no "cancel" button

[Dr . Chapatin]

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

Bug ID: 382775
   Summary: Settings window has no "cancel" button
   Product: k3b
   Version: 17.04.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: GUI/Usability
  Assignee: k...@kde.org
  Reporter: yy...@gmx.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

Created attachment 106887
  --> https://bugs.kde.org/attachment.cgi?id=106887=edit
"cancel" button is missing

See my screenshot. Only "defaults", "ok" and "apply" buttons are available.

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

[digikam] [Bug 165403] Build issues with 0.1.6-beta1

[bugzilla_noreply]

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

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
Product|kipiplugins |digikam
  Component|general |Portability
Summary|Build issues with   |Build issues with
   |kipi-plugins 0.1.6-beta1|0.1.6-beta1

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

[frameworks-kwallet] [Bug 382733] kwallet export does not save salt file

[Burkhard Lueck]

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

--- Comment #3 from Burkhard Lueck  ---
(In reply to Mate Soos from comment #2)
> I strongly suggest to merge the two.

This happens already , the .kwl and .salt are exported into ONE encrypted
archive file

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

[kipiplugins] [Bug 165403] Build issues with kipi-plugins 0.1.6-beta1

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

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

[kipiplugins] [Bug 149666] [PATCH] iPod Export kipi plugin cannot be disabled at compile time when libgpod is present on system

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

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

[kipiplugins] [Bug 149666] [PATCH] iPod Export cannot be disabled at compile time when libgpod is present on system

[bugzilla_noreply]

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

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

   What|Removed |Added

Summary|[PATCH] iPod Export kipi|[PATCH] iPod Export cannot
   |plugin cannot be disabled   |be disabled at compile time
   |at compile time when|when libgpod is present on
   |libgpod is present on   |system
   |system  |

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

[digikam] [Bug 353832] unmet dependencies error can not install software installed

[bugzilla_noreply]

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

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
Product|kipiplugins |digikam
  Component|general |Portability
Summary|unmet dependencies error|unmet dependencies error
   |can not install software|can not install software
   |installed KIPI plug-in  |installed
   Severity|major   |normal

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

[digikam] [Bug 233676] desktop-entry-contains-deprecated-key usr/share/applications/kde4/scangui.desktop:105 TerminalOptions

[bugzilla_noreply]

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

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
 CC||caulier.gil...@gmail.com
Product|kipiplugins |digikam
  Component|general |Import-Scanner
Summary|kipi-plugins:   |desktop-entry-contains-depr
   |desktop-entry-contains-depr |ecated-key
   |ecated-key  |usr/share/applications/kde4
   |usr/share/applications/kde4 |/scangui.desktop:105
   |/scangui.desktop:105|TerminalOptions
   |TerminalOptions |

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

[digikam] [Bug 306207] html gallery does not pass .desktop validation

[bugzilla_noreply]

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

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

   What|Removed |Added

   Assignee|kde-imag...@kde.org |digikam-de...@kde.org
Product|kipiplugins |digikam
Summary|kipi-plugins does not pass  |html gallery does not pass
   |.desktop validation |.desktop validation
  Component|general |HTMLGallery

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

[digikam] [Bug 294460] std namespace issue [patch]

[bugzilla_noreply]

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

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

   What|Removed |Added

Summary|std namespace issue in  |std namespace issue [patch]
   |kipi-plugins [patch]|
  Component|general |Portability
Product|kipiplugins |digikam
   Assignee|kde-imag...@kde.org |digikam-de...@kde.org

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

[digikam] [Bug 330111] No Thumbnails for video files - ffmpegthumbnailer works perfectly outside of digikam

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|INVALID |FIXED
   Version Fixed In||5.7.0

--- Comment #7 from caulier.gil...@gmail.com ---
Since digiKam 5.2.0, we use QtAV/FFMPeg framework to render video thumbnails.

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

[digikam] [Bug 330111] No Thumbnails for video files - ffmpegthumbnailer works perfectly outside of digikam

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|thumbnail   |Thumbnails
Product|kio |digikam
   Assignee|unassigned-b...@kde.org |digikam-de...@kde.org

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

[k3b] [Bug 382774] Just burned/erased discs are not correctly manipulated when "do not eject medium after write process" is checked

[Dr . Chapatin]

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

--- Comment #5 from Dr. Chapatin  ---
Created attachment 106886
  --> https://bugs.kde.org/attachment.cgi?id=106886=edit
dolphin shows no entry to just burned 'empty' disc

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

[k3b] [Bug 382774] Just burned/erased discs are not correctly manipulated when "do not eject medium after write process" is checked

[Dr . Chapatin]

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

--- Comment #4 from Dr. Chapatin  ---
Created attachment 106885
  --> https://bugs.kde.org/attachment.cgi?id=106885=edit
device notifier says just burned disc is empty

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

[k3b] [Bug 382774] Just burned/erased discs are not correctly manipulated when "do not eject medium after write process" is checked

[Dr . Chapatin]

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

--- Comment #3 from Dr. Chapatin  ---
Created attachment 106884
  --> https://bugs.kde.org/attachment.cgi?id=106884=edit
erased disc after eject and reinsert procedure

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

[k3b] [Bug 382774] Just burned/erased discs are not correctly manipulated when "do not eject medium after write process" is checked

[Dr . Chapatin]

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

--- Comment #2 from Dr. Chapatin  ---
Created attachment 106883
  --> https://bugs.kde.org/attachment.cgi?id=106883=edit
just erased disc has previous label in device notifier

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

[k3b] [Bug 382774] Just burned/erased discs are not correctly manipulated when "do not eject medium after write process" is checked

[Dr . Chapatin]

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

--- Comment #1 from Dr. Chapatin  ---
Created attachment 106882
  --> https://bugs.kde.org/attachment.cgi?id=106882=edit
dolphin shows error message about just erased disc

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

[k3b] [Bug 382774] New: Just burned/erased discs are not correctly manipulated when "do not eject medium after write process" is checked

[Dr . Chapatin]

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

Bug ID: 382774
   Summary: Just burned/erased discs are not correctly manipulated
when "do not eject medium after write process" is
checked
   Product: k3b
   Version: 17.04.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: yy...@gmx.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

Hi Leslie, one more bug, hehe.

Check "do not eject medium after write process" in K3b settings

Erase some rewritable disc. When the process is finished, device notifier shows
the same disc label before erase process. 
I open dolphin and click on the media label under "devices", I get a red bar
with an error message and the device notifier says "could not mount this
device" (see the screenshot).
After eject and reinsert the erased disc, the device notifier shows the correct
info about the disc ("blank cd-rw", see the screenshot).

After burn a disc, device notifier says the disc is still empty (see the
screenshot) and dolphin shows no entry to the just burned disc under "devices"
(see the screenshot). I need eject and reinsert the disc to access its content.

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

[plasmashell] [Bug 382773] New: Global Menu consistently crashes the KDE desktop

[bugzilla_noreply]

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

Bug ID: 382773
   Summary: Global Menu consistently crashes the KDE desktop
   Product: plasmashell
   Version: 5.10.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: paul.mccom...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.10.0-27-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed:
This has happened with multiple apps including but not limited to Discover and
Min (a browser). Although, I have noticed that Dolphin does not have this
problem. What happens is that I open an application, I decide to click on an
option from the Global Menu like file or edit, an outline of the dropdown menu
appears and freezes in place, then the desktop, the panels, and the widgets all
disappear and KDE Plasma crashes leaving a black background. The apps
themselves, however, are fully functioning allowing me to use them and drag
them around the black desktop with complete animations. Often KDE Plasma
restarts after 5 or so seconds, but rarely I do have to logout and re-log back
in to start up the desktop again. In other cases, I have noticed the Global
Menu to be unresponsive to any user interaction and therefore giving no
possibility for KDE Plasma to crash, but for this specific issue I'm reporting,
it is in relation to a full KDE crash. I know another bug similar to this has
been reported, however it was in reference to a specific app and cited the app
and global menu failing, whereas in this case the app continues to work
perfectly, but it is the whole of KDE Plasma that crashes.

- Unusual behaviour I noticed:
The unusual behaviour is noted above.

- Custom settings of the application:
There are no custom settings that I know of being implemented. The reason I was
attempting to access the global menu was to change the settings.

The crash can be reproduced every time.

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

Thread 13 (Thread 0x7f7ff9a44700 (LWP 13063)):
#0  0x7f81133833bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f81133858bb in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f81133862bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f811338649c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f811831394b in QEventDispatcherGlib::processEvents
(this=0x7f7ff40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f81182bc7ca in QEventLoop::exec (this=this@entry=0x7f7ff9a43cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f81180e5cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#7  0x7f7ffa101517 in KCupsConnection::run() () from
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#8  0x7f81180ea989 in QThreadPrivate::start (arg=0x57c1f10) at
thread/qthread_unix.cpp:368
#9  0x7f8116f8f6ba in start_thread (arg=0x7f7ff9a44700) at
pthread_create.c:333
#10 0x7f81179f73dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f80119eb700 (LWP 13045)):
#0  0x7f81133caa79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f8113386290 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f811338649c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f811831394b in QEventDispatcherGlib::processEvents
(this=0x7f80080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f81182bc7ca in QEventLoop::exec (this=this@entry=0x7f80119ead00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f81180e5cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f81180ea989 in QThreadPrivate::start (arg=0x27430b0) at
thread/qthread_unix.cpp:368
#7  0x7f8116f8f6ba in start_thread (arg=0x7f80119eb700) at
pthread_create.c:333
#8  0x7f81179f73dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f8020856700 (LWP 13044)):
#0  0x7f81179eb70d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f811338638c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f811338649c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f811831394b in QEventDispatcherGlib::processEvents
(this=0x7f800c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f81182bc7ca in QEventLoop::exec 

[digikam] [Bug 327470] digikam crashes when exiting, after exporting to html

[bugzilla_noreply]

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

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

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.7.0

--- Comment #4 from caulier.gil...@gmail.com ---
Problem is not reoroducible with HTML Gallery tool included in digiKam with
5.6.0 release.

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

[digikam] [Bug 327470] digikam crashes when exiting, after exporting to html

[bugzilla_noreply]

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

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

   What|Removed |Added

   Assignee|hugo.pereira.da.costa@gmail |digikam-de...@kde.org
   |.com|
Product|Oxygen  |digikam
  Component|general |HTMLGallery

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

[neon] [Bug 382772] New: LiveCD dkms package has unsatisfied dependency: patch

[bugzilla_noreply]

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

Bug ID: 382772
   Summary: LiveCD dkms package has unsatisfied dependency: patch
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: neon-b...@kde.org
  Reporter: stereople...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

My MBP 8,2 requires the bcmwl wireless driver. Like Kubuntu, Neon fails to
install this driver fails to install because it depends on dkms (included in
pool/main.

DKMS, in turn, depends on libfakeroot, fakeroot (both in pool/main as well) and
patch (as with Kubuntu, not included - filing a separate issue there).

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

[k3b] [Bug 382636] K3b opens device notifier when starts erase/format rewritable disc

[Dr . Chapatin]

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

--- Comment #5 from Dr. Chapatin  ---
(In reply to Leslie Zhai from comment #4)
> (In reply to Dr. Chapatin from comment #3)
> > Created attachment 106826 [details]
> > screenshot
> > 
> > here is my screenshot
> 
> Very clear! great bug hunter :) the notification should appear after erased,
> correct?

I think K3b should not interact with device notifier.
Device notifier is open by plasma when some device is mounted and "open a
message when a new device is connected" is chcked in its settings.

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

[k3b] [Bug 377105] Disc space/time bar is broken

[Dr . Chapatin]

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

--- Comment #17 from Dr. Chapatin  ---
maybe remove all the text above the QProgressBar and show the same info on
mouseover (tooltip) the disc space/time bar? I dont know, maybe other kde dev
or kde visual design group has a better idea.

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

[k3b] [Bug 382636] K3b opens device notifier when starts erase/format rewritable disc

[Leslie Zhai]

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

Leslie Zhai  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #4 from Leslie Zhai  ---
(In reply to Dr. Chapatin from comment #3)
> Created attachment 106826 [details]
> screenshot
> 
> here is my screenshot

Very clear! great bug hunter :) the notification should appear after erased,
correct?

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

[k3b] [Bug 382622] Do not show progress percentage in main window

[Leslie Zhai]

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

--- Comment #3 from Leslie Zhai  ---
(In reply to Dr. Chapatin from comment #2)
> this report is not a duplicate.
> I can confirm 382488 is fixed on neon dev unstable, but the percentage is
> still present in the main window.

I argue that the original developers keep 'show progress percentage' in the
main window is meaningful :) when minimized, not be the active window, it is
also visible from TaskManager panel to see the progress percentage.

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

[k3b] [Bug 382754] K3b complains about missing cdrskin at start up

[Leslie Zhai]

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

Leslie Zhai  changed:

   What|Removed |Added

 CC||lesliez...@llvm.org.cn

--- Comment #1 from Leslie Zhai  ---
> Forcing unsuspecting users to use a development alternative to cdrecord which 
> works fine for years.

Really? I argue that
https://lists.debian.org/debian-devel-announce/2006/09/msg2.html so please
remove wodim (forked cdrecord) from cdrkit (CD only, DVD deprecated,
unmaintained), website was down, release tarball is NOT available, svn repos is
so quiet! But install cdrtools A.K.A cdrecord instead.
http://www.leetcode.cn/2016/08/k3b.html#bug

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

[kleopatra] [Bug 355298] Outlook 2013 hangs after Kleopatra 2.2.0 asks for passphrase when performing signing, encryption, verification, etc.

[J . Guzman]

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

--- Comment #7 from J. Guzman  ---
I did not have the GPOs listed in the referenced TechNet article defined, but
that's a great find regarding DCOM! There may be a default state when "Not
Defined" but I didn't dig too deep into this. I won't get time until later this
week. 

DCOM GPOs: https://technet.microsoft.com/en-us/library/bb457148.aspx

I've since upgraded to Outlook 2016 and still workaround using Thunderbird or
Outlook with  GPG4Win, and GPA when needed.

Let me know if you need anything else.

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

[k3b] [Bug 377105] Disc space/time bar is broken

[Leslie Zhai]

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

--- Comment #16 from Leslie Zhai  ---
(In reply to Dr. Chapatin from comment #15)
> "thin" is my typo. I meant "this"

:)

so what about remove all the text above the QProgressBar? only keep the whole
thin long progressbar and gree bar, please give me some advice, thanks!

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

[plasmashell] [Bug 382765] Right-click menu doesn't close when left button is clicked

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

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

[kdevelop] [Bug 382771] Segfault while loading project

[Daniel Santos]

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

--- Comment #3 from Daniel Santos  ---
Created attachment 106881
  --> https://bugs.kde.org/attachment.cgi?id=106881=edit
emerge --info on all deps of kdevelop

If you need to know anything else about my environment, I've included the
emerge --info for all of kdeveop's dependencies via:

emerge --info dev-util/kdevelop $(for f in $(ldd /usr/bin/kdevelop | awk
'{print $3}'); do qfile $f; done | awk '{print $1}' | sort -u)

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

[kdevelop] [Bug 382771] Segfault while loading project

[Daniel Santos]

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

--- Comment #2 from Daniel Santos  ---
Created attachment 106880
  --> https://bugs.kde.org/attachment.cgi?id=106880=edit
.kdev4/gcc-git.kdev4

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

[kdevelop] [Bug 382771] Segfault while loading project

[Daniel Santos]

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

--- Comment #1 from Daniel Santos  ---
Created attachment 106879
  --> https://bugs.kde.org/attachment.cgi?id=106879=edit
project file

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

[kdevelop] [Bug 382771] New: Segfault while loading project

[Daniel Santos]

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

Bug ID: 382771
   Summary: Segfault while loading project
   Product: kdevelop
   Version: 5.1.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: daniel.san...@pobox.com
  Target Milestone: ---

Created attachment 106878
  --> https://bugs.kde.org/attachment.cgi?id=106878=edit
backtrace -- stack overvflow?  the address isn't < rsp but the stack trace goes
on forever

First off I'm sorry I didn't build my clang and llvm with debug symbols, I
wasn't planning on having to debug anything with them!

Just loading the gcc project after having upgraded from KDevelop 4.  I've had a
few bugs in kdev4 where you guys asked if I could try 5 and this is the reason
I hadn't upgraded yet, because the last time it crashed right off as well.

Keep in mind that all of gcc's .c files are really c++ now, but I'm not digging
into clang. :)

$ emerge --info dev-util/kdevelop dev-util/kdevplatform
!!! Repository 'rion' has sync-uri attribute, but is missing sync-type
attribute   
Portage 2.3.6 (python 3.4.6-final-0, default/linux/amd64/13.0/desktop/plasma,
gcc-5.4.0, glibc-2.24-r3, 4.1.15-gentoo-r1 x86_64)  
=   
 System Settings
=   
System uname:
Linux-4.1.15-gentoo-r1-x86_64-AMD_Phenom-tm-_9850_Quad-Core_Processor-with-gentoo-2.4.1
 
KiB Mem: 8175900 total,   1966424 free  
KiB Swap:   16795944 total,  16795944 free  
Timestamp of repository gentoo: Wed, 26 Jul 2017 13:00:01 + 
sh bash 4.4_p12 
ld GNU ld (Gentoo 2.28 p1.2) 2.28   
distcc 3.2rc1 x86_64-pc-linux-gnu [enabled] 
ccache version 3.3.4 [enabled]  
app-shells/bash:  4.4_p12::gentoo   
dev-java/java-config: 2.2.0-r3::gentoo  
dev-lang/perl:5.24.2::gentoo
dev-lang/python:  2.7.13::gentoo, 3.4.6::gentoo
dev-util/ccache:  3.3.4::gentoo
dev-util/cmake:   3.9.0::gentoo
dev-util/pkgconfig:   0.29.2::gentoo
sys-apps/baselayout:  2.4.1::gentoo
sys-apps/openrc:  0.28::gentoo
sys-apps/sandbox: 2.10-r4::gentoo
sys-devel/autoconf:   2.13::gentoo, 2.64::gentoo, 2.69-r3::gentoo
sys-devel/automake:   1.11.6-r2::gentoo, 1.12.6-r1::gentoo,
1.13.4-r1::gentoo, 1.14.1-r1::gentoo, 1.15.1::gentoo
sys-devel/binutils:   2.25.1-r1::gentoo, 2.27-r1::gentoo, 2.28-r2::gentoo
sys-devel/gcc:4.9.4::gentoo, 5.4.0-r3::gentoo, 6.3.0::gentoo
sys-devel/gcc-config: 1.8-r1::gentoo
sys-devel/libtool:2.4.6-r4::gentoo
sys-devel/make:   4.2.1-r1::gentoo
sys-kernel/linux-headers: 4.10::gentoo (virtual/os-headers)
sys-libs/glibc:   2.24-r3::gentoo
Repositories:

gentoo
location: /usr/portage
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000

loudmouth-local
location: /usr/local/portage
masters: gentoo
priority: 0

gamerlay
location: /var/lib/layman/gamerlay
masters: gentoo
priority: 50

pentoo
location: /var/lib/layman/pentoo
masters: gentoo
priority: 50

rion
location: /var/lib/layman/rion
sync-uri: https://github.com/rion-overlay/rion-overlay.git
masters: gentoo
priority: 50

sunrise
location: /var/lib/layman/sunrise
masters: gentoo
priority: 50

zugaina
location: /var/lib/layman/zugaina
masters: gentoo
priority: 50

ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -ggdb -march=amdfam10 -msahf -mpopcnt -mlzcnt -mtune=amdfam10
--param l1-cache-size=64 --param l1-cache-line-size=64 --param
l2-cache-size=512"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config
/usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild
/etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d
/etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-O2 -ggdb -march=amdfam10 -msahf -mpopcnt -mlzcnt -mtune=amdfam10
--param l1-cache-size=64 --param l1-cache-line-size=64 

[plasmashell] [Bug 382770] New: plasmashell crashed when mouse scrolling to increase volume from panel widget

[Mateus Honorato]

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

Bug ID: 382770
   Summary: plasmashell crashed when mouse scrolling to increase
volume from panel widget
   Product: plasmashell
   Version: 5.10.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mateush.honor...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.10.0-27-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed: i was with a bluetooth
headphone connected, a bluetooth mouse connected too. 

- Unusual behavior I noticed: plasmashell crashes frequently on my system.
also, sometimes, it feels very slow, even when I have noting running

- Custom settings of the application: I use a custom icon theme (papirus), and
also some custom widgets, like event calendar

The crash can be reproduced sometimes.

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

Thread 19 (Thread 0x7f96135f6700 (LWP 21013)):
#0  0x7fd71347b24f in pa_pstream_unref () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#1  0x7fd71347b7a3 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7fd71347c01a in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#3  0x7fd7141f60b7 in pa_mainloop_dispatch () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7fd7141f64bc in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7fd7141f6560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7fd7142047a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7fd71348c078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#8  0x7fd71df276ba in start_thread (arg=0x7f96135f6700) at
pthread_create.c:333
#9  0x7fd71e98f3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 18 (Thread 0x7fd63ccb3700 (LWP 21012)):
#0  0x7fd71a360a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fd71a31c4a6 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd71f2ab94b in QEventDispatcherGlib::processEvents
(this=0x7f961c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7fd71f2547ca in QEventLoop::exec (this=this@entry=0x7fd63ccb2ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#4  0x7fd71f07dcd4 in QThread::exec (this=this@entry=0x6aeb4f0) at
thread/qthread.cpp:515
#5  0x7fd72174bfa5 in QQmlThreadPrivate::run (this=0x6aeb4f0) at
qml/ftw/qqmlthread.cpp:147
#6  0x7fd71f082989 in QThreadPrivate::start (arg=0x6aeb4f0) at
thread/qthread_unix.cpp:368
#7  0x7fd71df276ba in start_thread (arg=0x7fd63ccb3700) at
pthread_create.c:333
#8  0x7fd71e98f3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7fd63e0b4700 (LWP 21008)):
#0  0x7fd71e98370d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd71a31c38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fd71a31c49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fd71f2ab94b in QEventDispatcherGlib::processEvents
(this=0x7f96180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd71f2547ca in QEventLoop::exec (this=this@entry=0x7fd63e0b3ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fd71f07dcd4 in QThread::exec (this=this@entry=0x6a57640) at
thread/qthread.cpp:515
#6  0x7fd72174bfa5 in QQmlThreadPrivate::run (this=0x6a57640) at
qml/ftw/qqmlthread.cpp:147
#7  0x7fd71f082989 in QThreadPrivate::start (arg=0x6a57640) at
thread/qthread_unix.cpp:368
#8  0x7fd71df276ba in start_thread (arg=0x7fd63e0b4700) at
pthread_create.c:333
#9  0x7fd71e98f3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7fd6457fa700 (LWP 8452)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fd71f0838eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x4d2a650) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x502d200,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fd660eef07f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  

[valgrind] [Bug 381553] VEX register allocator v3

[Ivo Raisr]

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

--- Comment #39 from Ivo Raisr  ---
Patches 010 implement the necessary changes for supporting the register
allocator v3 to all architectures supported by VEX.

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

[valgrind] [Bug 381553] VEX register allocator v3

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

 Attachment #106802|0   |1
is obsolete||

--- Comment #38 from Ivo Raisr  ---
Created attachment 106877
  --> https://bugs.kde.org/attachment.cgi?id=106877=edit
patch 010 - VEX part

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

[valgrind] [Bug 381553] VEX register allocator v3

[Ivo Raisr]

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

Ivo Raisr  changed:

   What|Removed |Added

 Attachment #106801|0   |1
is obsolete||

--- Comment #37 from Ivo Raisr  ---
Created attachment 106876
  --> https://bugs.kde.org/attachment.cgi?id=106876=edit
patch 010 - Valgrind part

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

[Akonadi] [Bug 382769] New: akonadi crash after starting kontact

[Markus Grabner]

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

Bug ID: 382769
   Summary: akonadi crash after starting kontact
   Product: Akonadi
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: grab...@icg.tugraz.at
  Target Milestone: ---

Application: akonadiserver (5.5.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.76-1-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
Ca. 30 seconds after starting kontact, the akonadi server crashes without
further user interaction. On startup, kontact displays the calendar page with
ca. 10 calendars, most of them CalDav. This behaviour is new in openSUSE Leap
42.3, kontact+akonadi worked fine in earlier versions.

The crash can be reproduced every time.

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

Thread 39 (Thread 0x7f5d89feb700 (LWP 2947)):
#0  0x7f5de79356ab in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7f5de79378fb in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f5de7938230 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f5de793842c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f5deb3151ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f5deb2c2bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f5deb0fdf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f5deb102a29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5de9621744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f5dea7f9aad in clone () at /lib64/libc.so.6

Thread 38 (Thread 0x7f5d8a7ec700 (LWP 2941)):
#0  0x7f5dea7f120d in poll () at /lib64/libc.so.6
#1  0x7f5de7938314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f5de793842c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f5deb3151ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f5deb2c2bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5deb0fdf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f5deb102a29 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f5de9621744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f5dea7f9aad in clone () at /lib64/libc.so.6

Thread 37 (Thread 0x7f5d8afed700 (LWP 2939)):
#0  0x7f5de79798b4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f5de7938436 in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f5deb3151ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f5deb2c2bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f5deb0fdf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f5deb102a29 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f5de9621744 in start_thread () at /lib64/libpthread.so.0
#7  0x7f5dea7f9aad in clone () at /lib64/libc.so.6

Thread 36 (Thread 0x7f5d8bfef700 (LWP 2781)):
#0  0x7ffc44972adc in clock_gettime ()
#1  0x7f5dea806576 in clock_gettime () at /lib64/libc.so.6
#2  0x7f5deb1ada46 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5deb313809 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f5deb313d85 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5deb31564c in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f5de793795d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f5de7938230 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f5de793842c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f5deb3151ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f5deb2c2bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f5deb0fdf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f5deb102a29 in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f5de9621744 in start_thread () at /lib64/libpthread.so.0
#14 0x7f5dea7f9aad in clone () at /lib64/libc.so.6

Thread 35 (Thread 0x7f5d8c7f0700 (LWP 2780)):
#0  0x7f5deb1ada4f in  () at /usr/lib64/libQt5Core.so.5
#1  0x7f5deb313809 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#2  0x7f5deb313d85 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f5deb31564c in  () at /usr/lib64/libQt5Core.so.5
#4  0x7f5de793795d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f5de7938230 in  () at /usr/lib64/libglib-2.0.so.0
#6  

[kdenlive] [Bug 382767] New: Pressing play only plays 1 frame

[bugzilla_noreply]

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

Bug ID: 382767
   Summary: Pressing play only plays 1 frame
   Product: kdenlive
   Version: 17.04.3
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: kekoslaye...@yahoo.com
  Target Milestone: ---

Whenever I try to play a video by using the play on the media player it only
plays a single frame. The only way for it to play the video is to scroll to a
different point in the timeline.

https://i.gyazo.com/39d8a624d8b8d13a2ffee3771a319c14.mp4

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

[plasmashell] [Bug 382768] New: Deleting files to trash crash

[oysstu]

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

Bug ID: 382768
   Summary: Deleting files to trash crash
   Product: plasmashell
   Version: 5.10.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: oys...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.10.0-27-generic x86_64
Distribution: KDE neon User Edition 5.10

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

Deleted a large amount of files (400-500) to trash, and checked the progress
indicator, at which point plasmashell crashed.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[Current thread is 1 (Thread 0x7fef864088c0 (LWP 2878))]

Thread 16 (Thread 0x7feea32fd700 (LWP 24440)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fef813558eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x33ae420) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x24fa8b8,
mutex=mutex@entry=0x24fa8b0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fef8443f10d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x24fa8a8) at scenegraph/qsgthreadedrenderloop.cpp:245
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x24fa830) at
scenegraph/qsgthreadedrenderloop.cpp:701
#5  0x7fef8443fa05 in QSGRenderThread::run (this=0x24fa830) at
scenegraph/qsgthreadedrenderloop.cpp:730
#6  0x7fef81354989 in QThreadPrivate::start (arg=0x24fa830) at
thread/qthread_unix.cpp:368
#7  0x7fef801f96ba in start_thread (arg=0x7feea32fd700) at
pthread_create.c:333
#8  0x7fef80c613dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7feea3dfe700 (LWP 21296)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fef813558eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x2dfdcf0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x2d94738,
mutex=mutex@entry=0x2d94730, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fef8443f10d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x2d94728) at scenegraph/qsgthreadedrenderloop.cpp:245
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x2d946b0) at
scenegraph/qsgthreadedrenderloop.cpp:701
#5  0x7fef8443fa05 in QSGRenderThread::run (this=0x2d946b0) at
scenegraph/qsgthreadedrenderloop.cpp:730
#6  0x7fef81354989 in QThreadPrivate::start (arg=0x2d946b0) at
thread/qthread_unix.cpp:368
#7  0x7fef801f96ba in start_thread (arg=0x7feea3dfe700) at
pthread_create.c:333
#8  0x7fef80c613dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7feeacadd700 (LWP 5987)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fef813558eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x25e9420) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x1a0be58,
mutex=mutex@entry=0x1a0be50, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fef8443f10d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x1a0be48) at scenegraph/qsgthreadedrenderloop.cpp:245
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x1a0bdd0) at
scenegraph/qsgthreadedrenderloop.cpp:701
#5  0x7fef8443fa05 in QSGRenderThread::run (this=0x1a0bdd0) at
scenegraph/qsgthreadedrenderloop.cpp:730
#6  0x7fef81354989 in QThreadPrivate::start (arg=0x1a0bdd0) at
thread/qthread_unix.cpp:368
#7  0x7fef801f96ba in start_thread (arg=0x7feeacadd700) at
pthread_create.c:333
#8  0x7fef80c613dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7feeaecf2700 (LWP 5362)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fef813558eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x29fe0b0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x29c3358,
mutex=mutex@entry=0x29c3350, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fef8443f10d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x29c3348) at 

[krita] [Bug 382766] New: the pressure of the mause and of the tablet don't work

[chiara]

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

Bug ID: 382766
   Summary: the pressure of the mause and of the tablet don't work
   Product: krita
   Version: 3.1.4
  Platform: Other
OS: Windows CE
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: chiaracognigni...@gmail.com
  Target Milestone: ---

the pressur of my mouse and of my pen don't work from the last day and i can't
draw in this contions

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

[krita] [Bug 371827] [BOSTO] Pen Pressure not working

[chiara]

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

chiara  changed:

   What|Removed |Added

 CC||chiaracognigni...@gmail.com

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

[digikam] [Bug 382703] Compile error with cmake 3.9

[Adam Stylinski]

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

--- Comment #3 from Adam Stylinski  ---
Ah, well as another data point I am in fact using CMake 3.9.

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

[digikam] [Bug 382703] Compile error with cmake 3.9

[rezso]

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

--- Comment #2 from rezso  ---
I tried it: with cmake 3.7.2 the build is successful, with cmake 3.9.0 fails.
After downgrading cmake to 3.7.2, I can compile the code without any problems.

It seems to me, that cmake 3.9 uses different dependency tracking / linking
method than older versions:
https://phabricator.kde.org/D6792

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

[plasmashell] [Bug 382765] New: Right-click menu doesn't close when left button is clicked

[Adam Markiewicz]

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

Bug ID: 382765
   Summary: Right-click menu doesn't close when left button is
clicked
   Product: plasmashell
   Version: 5.10.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: a.markiew...@live.com
  Target Milestone: 1.0

In a Wayland session, when a right-click menu is opened, a subsequent
left-click somewere else doesn't close it. This applies to all desktop
elements: wallpaper, panels, etc.

The menu can be closed with another right-click or by left-clicking an item in
the menu.

The menu also closes if the left-click happens in some other window (e.g.
dolphin) and not on a plasma desktop element.

Steps to reproduce:
1) right-click on the desktop
2) left-click on the desktop (previously opened menu doesn't close as it
should)

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

[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM

[Tristan Miller]

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

--- Comment #144 from Tristan Miller  ---
(In reply to Malte Eggers from comment #1)
> To set your locale to use ISO 8601, you have to set LC_TIME=en_DK.

For anyone doing this on a per-application basis (rather than putting it in
$HOME/.profile), there is the problem that the language setting does not get
saved with the KDE session.  I have filed a separate issue for this with the
session management product: Bug 382764.

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

[frameworks-kwallet] [Bug 382733] kwallet export does not save salt file

[Mate Soos]

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

--- Comment #2 from Mate Soos  ---
I think it's a really bad idea to have 2 files exported, a .kwl and a .salt.
Inevitably, people will forget the salt. I strongly suggest to merge the two.

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

[ksmserver] [Bug 382764] New: Save and restore environment variables per application

[Tristan Miller]

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

Bug ID: 382764
   Summary: Save and restore environment variables per application
   Product: ksmserver
   Version: 5.10.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: psychon...@nothingisreal.com
  Target Milestone: ---

I sometimes launch applications using different language environment variables,
either because I prefer to use that application in a different language from my
global defaults, or because I am trying to work around KDE/Qt's lack of support
for custom date formats (see the much-hated Bug 340982). For example, I always
launch Thunderbird with LC_TIME=en_DK so that it shows me -MM-DD dates in
my message list.

Unfortunately, ksmserver doesn't seem to remember the language environment for
these applications when I save the session.  (This problem occurs regardless
whether the application was launched from a desktop shortcut or from a shell
script that manually sets the environment variable(s).)  For example, when I
log out of KDE and log back in again, Thunderbird gets restored, but it formats
the dates according to the system default locale rather than en_DK.

It would be useful if ksmserver could somehow recognize when applications are
launched with special environment variables, and re-set these variables when
restoring the session.  I realize that this may be difficult or impossible to
do in the general case, but maybe it is possible at least for applications
launched via a standard desktop/menu shortcut.

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

[kdevelop] [Bug 381123] Kdevelop crashes on parsing php project [Php::TypeBuilder::visitStatement]

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

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

--- Comment #4 from Kevin Funk  ---
commit 252d8ff069b597d9406b954d732cdf52c679f41a
Author: Matthijs Tijink 
Date:   Wed Jul 26 14:41:22 2017 +0200

Fix bug 381123: crash while parsing PHP code

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

[kdevelop] [Bug 381123] Kdevelop crashes on parsing php project [Php::TypeBuilder::visitStatement]

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

   Version Fixed In||5.1.2

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

[ksmserver] [Bug 239971] keep the desktop shaded when shuting down

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

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

--- Comment #3 from Tristan Miller  ---
This is a duplicate of Bug 188476. Could someone with the requisite permissions
please close it as such?

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

[okular] [Bug 376990] Okular randomly crashes when launched from Emacs

[Tristan Miller]

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

Tristan Miller  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #9 from Tristan Miller  ---
No longer reproducible for me.  I'm currently running Okular 1.1.2 with Qt
5.9.1.  I'm assuming I should mark this as RESOLVED/WORKSFORME.

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

[kmail2] [Bug 382763] New: Kmail says Could not compose message: publisher certificate is missing

[Tom Kijas]

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

Bug ID: 382763
   Summary: Kmail says Could not compose message: publisher
certificate is missing
   Product: kmail2
   Version: Git (master)
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-b...@kde.org
  Reporter: t.ki...@gmail.com
  Target Milestone: ---

When I try to send signed email, Kmail says Could not compose message:
publisher certificate is missing

I use postsignum S/MIME certificate, approved authority to create qualified
certificates to use in contact with public authorities. It has been imported by
two files into Kleopatra.

Kmail Identity is set-up to use this S/MIME certificate.

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

[digikam] [Bug 382703] Compile error with cmake 3.9

[Adam Stylinski]

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

Adam Stylinski  changed:

   What|Removed |Added

 CC||kungfujesu...@gmail.com

--- Comment #1 from Adam Stylinski  ---
I'm seeing similar linking errors errors (missing vtables for
Digikam::ImageModel), though it's unclear if it's related to cmake versions.  I
only have one version of CMake to test.

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

[kaffeine] [Bug 381828] quick channel zapping eventually stops tv playback

[Mauro Carvalho Chehab]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

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

--- Comment #5 from Mauro Carvalho Chehab  ---
(In reply to Tuxo from comment #4)
> Hello Mauro, turns out it's my DVB-T usb Dongle, a "DigitalRise DVB-T USB
> 2.0 Ter Beetle " - this one still has some unfixed issues in kernel 4.9 (the
> kernel debian/stable uses). 

Kernel 4.9 had an important change, meant to improve security that badly
affected USB drivers. Yet, if the device is tuning, the required bug fixes
should already have been backported. The vp7045 driver is really simple: all it
does is to send commands to the device's internal firmware, with is responsible
internally to talk with the frontend. So, it is up to the firmware to tune.

So, what I suspect is that just increasing the timeout should be enough to make
it work with such device.

> It seems to affect the quick tuning. I'm testing
> now with a Hauppauge WinTV HVR-900H dongle and the issues are all gone.

OK, that confirms that this isn't a Kaffeine issue.

> Switching off vdpau with VDPAU_DRIVER=none is a good idea anyway, my older
> asrock mainboard can't deinterlace mpeg-2 in hardware, it has to happen in
> software. Increasing the tuning timeout to 4500ms (3x) for the Beetle device
> did not help.

Well, from its driver, it internally uses a Zarlink MT352 tuner, with is a very
old frontend. Perhaps it doesn't lock well on channels with higher throughput,
or perhaps the hardware is showing its age ;)

> 
> Please close this ticket, the problem is hardware related ...

OK, thanks for checking.

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

[kaffeine] [Bug 130335] key shortcut to switch subtitles and audio tracks.

[Tuxo]

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

Tuxo  changed:

   What|Removed |Added

 CC||tuxoho...@hotmail.de

--- Comment #2 from Tuxo  ---
Mauro, could this feature be added to 2.0.1x -git ? It's still not possible to
assign a shortcut to switch audio or subtitle tracks with a key or assign a
remote event.

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

   Version Fixed In||5.1.2

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

[kaffeine] [Bug 381827] DCMAKE_BUILD_TYPE=Release creates debug version

[Tuxo]

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

--- Comment #6 from Tuxo  ---
Maybe I'm not understanding the --desktopfile option: I thought it was possible
to use this to pass additional options or a different environment setup to a
second kaffeine starter like (kaffeine-debug.desktop) and write the debug
output to a logfile?

Anyway, the issue is fixed for me, you can close this ticket.

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

  Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde
   |v-python/6043407c4ee2e1b3ee |vplatform/396dda6a43402cade
   |fac8e1f8c96a651b92a14e  |fbcffa4473d62d34de14175
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #13 from Francis Herne  ---
Git commit 396dda6a43402cadefbcffa4473d62d34de14175 by Francis Herne.
Committed on 26/07/2017 at 19:09.
Pushed by flherne into branch '5.1'.

Normalize line endings when creating ParseJob from background file.

When the file being parsed is open in the editor, `ParseJob::readContents()`
 uses `KTextEditor::Document::text()` to read the contents.
At some point within KTextEditor, the line endings are normalized - even if
 the document uses \r or \r\n, the returned content is separated by \n only.

Otherwise, the contents are read directly from the file. Until this patch,
 the line endings aren't normalized in this case; the ParseJob contents
 differ depending on whether the file is open in the editor.

Several places in kdev-python (and, at a glance, other language plugins)
 assume that lines can be separated by, and end with, \n. Old-style Macintosh
 endings (\r) break this assumption, in the worst case causing a crash.

Using a regex in each instance would be a pain, and one code path normalizes
 line endings already, so I think the best option is to do so for background
 files also.

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

M  +4-0language/backgroundparser/parsejob.cpp
M  +15   -0util/kdevstringhandler.cpp
M  +5-0util/kdevstringhandler.h
M  +29   -1util/tests/test_stringhandler.cpp
M  +3-0util/tests/test_stringhandler.h

https://commits.kde.org/kdevplatform/396dda6a43402cadefbcffa4473d62d34de14175

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

[kaffeine] [Bug 381828] quick channel zapping eventually stops tv playback

[Tuxo]

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

--- Comment #4 from Tuxo  ---
Hello Mauro, turns out it's my DVB-T usb Dongle, a "DigitalRise DVB-T USB 2.0
Ter Beetle " - this one still has some unfixed issues in kernel 4.9 (the kernel
debian/stable uses). It seems to affect the quick tuning. I'm testing now with
a Hauppauge WinTV HVR-900H dongle and the issues are all gone.

Switching off vdpau with VDPAU_DRIVER=none is a good idea anyway, my older
asrock mainboard can't deinterlace mpeg-2 in hardware, it has to happen in
software. Increasing the tuning timeout to 4500ms (3x) for the Beetle device
did not help.

Please close this ticket, the problem is hardware related ...

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

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

[Boudewijn Rempt]

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

--- Comment #31 from Boudewijn Rempt  ---
After some more tests, this seems to happen exclusively to Apple computers with
a Radeon graphics card. Disabling OpenGL in the Krita settings/display page
works around the issue.

No Krita developers has a mac with a Radeon card, so we will need work from
owners with such hardware to find a workaround that doesn't mean opengl has to
be disabled.

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

[plasmashell] [Bug 382762] New: FEATURE REQUEST: Add ability to change icon, similar to Kickoff's settings

[Jesse]

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

Bug ID: 382762
   Summary: FEATURE REQUEST: Add ability to change icon, similar
to Kickoff's settings
   Product: plasmashell
   Version: 5.10.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Window List
  Assignee: plasma-b...@kde.org
  Reporter: jesse.dub...@gmail.com
  Target Milestone: 1.0

Created attachment 106875
  --> https://bugs.kde.org/attachment.cgi?id=106875=edit
Example of the button (or something similar) from Kickoff settings that would
be nice in Window List settings

BEHAVIOR
Currently, when placing the Windows List widget on the desktop or in a panel,
you can't change the icon.

DESIRED BEHAVIOR
It would be nice if the settings had a button similar to Kickoff's settings
(see attached screenshot) where the user could easily choose the icon for the
Window List Widget in the panel.

FEATURE REQUESTED WHILE USING
KDE Neon 5.10
KDE Plasma 5.10.4
KDE Frameworks 5.36.0
Linux kernel 4.10.0-27-generic

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

[dolphin] [Bug 382761] close dolphin

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |dolphin-bugs-n...@kde.org
 CC||elvis.angelac...@kde.org
Product|kde |dolphin
  Component|general |general
Version|unspecified |16.12.3

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

[kde] [Bug 382761] New: close dolphin

[Anaya Patos]

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

Bug ID: 382761
   Summary: close dolphin
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: anay...@hotmail.es
  Target Milestone: ---

Application: kdeinit5 (16.12.3)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.35-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
Closes 1 window when making copies of files between 2 windows(dolphin) and a
process is set to 100% in system activities

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7af22dc800 (LWP 7347))]

Thread 4 (Thread 0x7f7ad30be700 (LWP 7351)):
#0  0x7f7aed4da974 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f7aed495220 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f7aed495bc3 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f7aed495d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f7af0e25e2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f7af0dd149a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f7af0c0b3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f7af0c0fff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f7aee1e466d in start_thread () at /lib64/libpthread.so.0
#9  0x7f7af08a6e4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f7ad8d3a700 (LWP 7349)):
#0  0x7f7af089b00d in poll () at /lib64/libc.so.6
#1  0x7f7aed495c94 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f7aed495d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f7af0e25e2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f7af0dd149a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f7af0c0b3bc in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f7af21fa635 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f7af0c0fff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f7aee1e466d in start_thread () at /lib64/libpthread.so.0
#9  0x7f7af08a6e4d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f7ada925700 (LWP 7348)):
#0  0x7f7af089b00d in poll () at /lib64/libc.so.6
#1  0x7f7af17e4902 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f7af17e6657 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f7add5f6be9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f7af0c0fff9 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f7aee1e466d in start_thread () at /lib64/libpthread.so.0
#6  0x7f7af08a6e4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7af22dc800 (LWP 7347)):
[KCrash Handler]
#6  0x7f7af07e4818 in raise () at /lib64/libc.so.6
#7  0x7f7af07e5f2a in abort () at /lib64/libc.so.6
#8  0x7f7af0bf7f6e in  () at /lib64/libQt5Core.so.5
#9  0x7f7af2205739 in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5
#10 0x7f7af0dff3aa in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#11 0x7f7aef68ad0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#12 0x7f7aef68fe76 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#13 0x7f7af0dd3628 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#14 0x7f7af0dd544b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#15 0x7f7af0e259f3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#16 0x7f7aed495ac7 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#17 0x7f7aed495cf8 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#18 0x7f7aed495d9c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#19 0x7f7af0e25e06 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#20 0x7f7af0dd149a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#21 0x7f7af0dd97e1 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#22 0x7f7ae70143f6 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#23 0x0040818f in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) ()
#24 0x00409437 in handle_launcher_request(int, char const*) [clone

[kexi] [Bug 379737] Add option to print specific report page(s)

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

Summary|Printing specific report|Add option to print
   |page|specific report page(s)

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

[kexi] [Bug 379737] Printing specific report page

[Jarosław Staniek]

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

Jarosław Staniek  changed:

   What|Removed |Added

   Priority|NOR |LO
   Severity|major   |wishlist
 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1

--- Comment #12 from Jarosław Staniek  ---
Assuming this is the request.

"Add option to print selected report page(s) directly from Kexi without using
the print dialog's option."

Because per Bugzilla bug (how many years? :)) the wish description cannot be
edited, I am leaving the conclusion here.

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

[plasmashell] [Bug 382760] Break apart "Expand search to bookmarks, files and emails" checkbox -- don't lump them together

[Jesse]

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

Jesse  changed:

   What|Removed |Added

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

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

[kinfocenter] [Bug 380355] Processors numbers listed are machine-sorted, not human-sorted in Device Viewer

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
You can find KDE sources on cgit.kde.org

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

[plasmashell] [Bug 382760] New: Break apart "Expand search to bookmarks, files and emails" checkbox -- don't lump them together

[Jesse]

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

Bug ID: 382760
   Summary: Break apart "Expand search to bookmarks, files and
emails" checkbox -- don't lump them together
   Product: plasmashell
   Version: 5.10.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: jesse.dub...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 106874
  --> https://bugs.kde.org/attachment.cgi?id=106874=edit
Application Launcher (Kickoff) settings as it currently is in 5.10.4

BEHAVIOR
When I press the Super key and begin typing a search string, if the "Expand
search to bookmarks, files and emails" checkbox is checked, the sear listing
will show the results from my files, emails and bookmarks. I SELDOM want to
search my bookmarks, but OFTEN search my files from the kickoff search field,
and having to sort through the clutter of my bookmarks and emails when I only
want it to list my files is very bothersome.

EXPECTED BEHAVIOR
For their to be individual checkboxes in the Kickoff settings for "Expand
search to files", "Expand search to bookmars", "Expand search to emails",
letting the user pick what they would like to filter in their search results.

FEATURE REQUEST SUGGESTED WHILE USING
KDE Neon 5.10 x64
KDE Plasma 5.10.4
KDE Frameworks 5.36.0
Linux kernel 4.10.0-27-generic

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

[kde] [Bug 382666] kdetalk certificate expired yesterday

[Alex10336]

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

--- Comment #4 from Alex10336  ---
No more certificate issue. Thanks you.

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

[digikam] [Bug 338176] Face Recognition memory allocation crash application

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 283165] crash happened while running face recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 275637] Performing multiple scans and recognises causes crash

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 275541] digikam crashed while doing face recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 330342] digiKam crash with faces recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 365669] Face Recognition improvement suggestion

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 286418] digikam crashed during face recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 329596] Digikam crashes during face recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 290891] digikam Crash while Face Recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 262212] Face recognition doesn't work

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 314744] face do not recognize

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 335624] digiKam crash when I start face recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 323271] Face Recognition doesn't work

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 292248] Recognize faces does nothing

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 268046] Switch foto with face recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 316856] I suggest to extend face recognition to text-recognition system.

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 277163] digikam valgrind issues during face recognition testing

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 275387] Digikam crashes on face recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 287099] Digikam crash when using facerecognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 336979] Digikam crash during facial recognition when closed before finished

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 300357] digikam crashes on Face Recognition scan

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 376901] [GSOC2017]Face Recognition Algorithm Improvements

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 276923] Crash during initial run of facial recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 321295] crash after face recognition run

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 282948] Face recognition crashes Digikam (again)

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 302810] Crash when closing digikam during face recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 309306] Crash during face-recognition

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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

[digikam] [Bug 344661] Face recognition makes digikam fill all the available memory

[bugzilla_noreply]

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

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

   What|Removed |Added

  Component|Faces-Management|Faces-Recognition

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