[konsole] [Bug 373440] konsole --new-tab opens window instead

[don Christophe]

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

don Christophe  changed:

   What|Removed |Added

 CC||christo...@donchristophe.be

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

[kalarm] [Bug 373886] regression: cannot adjust alarm date for new alarms with cursor keys anymore

[bugzilla_noreply]

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

--- Comment #2 from a4...@t-online.de ---
(In reply to David Jarvie from comment #1)
> The widget used to edit the date looks as if it should still respond to
> up-arrow and page-up, but for some reason it doesn't work in the alarm edit
> dialog.

Using kalarm without this feature is quite cumbersome.
Will you try to fix it?

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

[Akonadi] [Bug 373111] Crash During Start Up After Login

[bugzilla_noreply]

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

--- Comment #8 from bj.kdede...@bkaj.org ---
The issue also seems resolved for me with the latest round of Tumbleweed
updates.

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

[partitionmanager] [Bug 373944] theming still broken with partiton manager 3 under Neon

[PK]

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

--- Comment #27 from PK  ---
thank you for your suggestion. I keep testing on my two computers (one intel
based and one amd based) and I keep getting unexpected (and different) results.
I hope I get so far that I can make a bug out of it.

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

[krita] [Bug 374024] New: Brush strokes lags terribly

[bugzilla_noreply]

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

Bug ID: 374024
   Summary: Brush strokes lags terribly
   Product: krita
   Version: 3.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: danielkir...@gmail.com
  Target Milestone: ---

Every time I pain a big stroke it lags terribly like 1-2 secs, even if I lower
the size of the brush it still lags for few moments. I am in a small canvas:
300 dpi, 8bits, 1000x1000.

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

[Discover] [Bug 374025] New: search does not function

[rbugman28]

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

Bug ID: 374025
   Summary: search does not function
   Product: Discover
   Version: 5.6.2
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: rbugma...@yahoo.com
  Target Milestone: ---

Search function does not work, Search for a known package = zero results
apt-get works just fine.

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

[kwin] [Bug 374023] New: KDE session crashes on startup, 4.8.14, nvidia driver with 7600gs card

[Gregg]

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

Bug ID: 374023
   Summary: KDE session crashes on startup, 4.8.14, nvidia driver
with 7600gs card
   Product: kwin
   Version: 5.8.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mnpmo...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.29.0
Operating System: Linux 4.8.14-1-default i686
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: booted to level 3, init 5,
chose a KDE plasma failsafe session, logged in. Screen went dark and then
backlit (not so dark) I think. Previous attempts at Plasma 5 sessions noted
crash putting up welcome screen and then crash starting plasma session. Could
not find core dump.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb0a262c0 (LWP 9528))]

Thread 3 (Thread 0xac2ebb40 (LWP 9541)):
#0  0xb7717e69 in __kernel_vsyscall ()
#1  0xb75fd154 in ppoll () from /lib/libc.so.6
#2  0xb614a835 in ppoll (__ss=, __timeout=,
__nfds=, __fds=) at /usr/include/bits/poll2.h:77
#3  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0xadc021d0) at
kernel/qcore_unix.cpp:91
#4  qt_safe_poll (fds=0xadc021d0, nfds=1, timeout_ts=0x0) at
kernel/qcore_unix.cpp:112
#5  0xb614c1c1 in QEventDispatcherUNIX::processEvents (this=,
flags=...) at kernel/qeventdispatcher_unix.cpp:495
#6  0xb60f40dd in QEventLoop::exec (this=, flags=...) at
kernel/qeventloop.cpp:210
#7  0xb5f2bb55 in QThread::exec (this=0x9237880) at thread/qthread.cpp:507
#8  0xb4d58e4f in QQmlThreadPrivate::run (this=0x9237880) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/ftw/qqmlthread.cpp:147
#9  0xb5f3100a in QThreadPrivate::start (arg=) at
thread/qthread_unix.cpp:344
#10 0xb46212b1 in ?? () from /usr/lib/libGL.so.1
#11 0x5c8b0824 in ?? ()
#12 0xbab80424 in ?? ()
#13 0x6500 in ?? ()
#14 0x001015ff in ?? ()
#15 0xd389 in ?? ()
#16 0xfff0013d in ?? ()
#17 0xed830fff in ?? ()
#18 0xc3fffea7 in ?? ()
#19 0x90669066 in ?? ()
#20 0x90669066 in ?? ()
#21 0x90669066 in ?? ()
#22 0xe8535657 in ?? ()
#23 0x000f5add in ?? ()
#24 0x8558c781 in ?? ()
#25 0xec810018 in ?? ()
#26 0x0094 in ?? ()
#27 0xa4249c8b in ?? ()
#28 0x8d00 in ?? ()
#29 0x56082474 in ?? ()
#30 0xe853006a in ?? ()
#31 0xf998 in ?? ()
#32 0x8510c483 in ?? ()
#33 0x8d6978c0 in ?? ()
#34 0x01b8ff4b in ?? ()
#35 0x8900 in ?? ()
#36 0x8be0d3ca in ?? ()
#37 0x00a4248c in ?? ()
#38 0xeac1 in ?? ()
#39 0x75c98505 in ?? ()
#40 0x81d0f737 in ?? ()
#41 0x0088248c in ?? ()
#42 0x in ?? ()

Thread 2 (Thread 0xb0a22b40 (LWP 9531)):
#0  0xb7717e69 in __kernel_vsyscall ()
#1  0xb75fd154 in ppoll () from /lib/libc.so.6
#2  0xb614a835 in ppoll (__ss=, __timeout=,
__nfds=, __fds=) at /usr/include/bits/poll2.h:77
#3  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0xae809040) at
kernel/qcore_unix.cpp:91
#4  qt_safe_poll (fds=0xae809040, nfds=1, timeout_ts=0x0) at
kernel/qcore_unix.cpp:112
#5  0xb614c1c1 in QEventDispatcherUNIX::processEvents (this=,
flags=...) at kernel/qeventdispatcher_unix.cpp:495
#6  0xb60f40dd in QEventLoop::exec (this=, flags=...) at
kernel/qeventloop.cpp:210
#7  0xb5f2bb55 in QThread::exec (this=0xb49ad6c0) at thread/qthread.cpp:507
#8  0xb491b7ec in ?? () from /usr/lib/libQt5DBus.so.5
#9  0xb5f3100a in QThreadPrivate::start (arg=) at
thread/qthread_unix.cpp:344
#10 0xb46212b1 in ?? () from /usr/lib/libGL.so.1
#11 0x5c8b0824 in ?? ()
#12 0xbab80424 in ?? ()
#13 0x6500 in ?? ()
#14 0x001015ff in ?? ()
#15 0xd389 in ?? ()
#16 0xfff0013d in ?? ()
#17 0xed830fff in ?? ()
#18 0xc3fffea7 in ?? ()
#19 0x90669066 in ?? ()
#20 0x90669066 in ?? ()
#21 0x90669066 in ?? ()
#22 0xe8535657 in ?? ()
#23 0x000f5add in ?? ()
#24 0x8558c781 in ?? ()
#25 0xec810018 in ?? ()
#26 0x0094 in ?? ()
#27 0xa4249c8b in ?? ()
#28 0x8d00 in ?? ()
#29 0x56082474 in ?? ()
#30 0xe853006a in ?? ()
#31 0xf998 in ?? ()
#32 0x8510c483 in ?? ()
#33 0x8d6978c0 in ?? ()
#34 0x01b8ff4b in ?? ()
#35 0x8900 in ?? ()
#36 0x8be0d3ca in ?? ()
#37 0x00a4248c in ?? ()
#38 0xeac1 in ?? ()
#39 0x75c98505 in ?? ()
#40 0x81d0f737 in ?? ()
#41 0x0088248c in ?? ()
#42 0x in ?? ()

Thread 1 (Thread 0xb0a262c0 (LWP 9528)):
[KCrash Handler]
#7  0xb7717e69 in __kernel_vsyscall ()
#8  0xb754a2a0 in raise () from /lib/libc.so.6
#9  0xb754b791 in abort () from /lib/libc.so.6
#10 0xb5f16653 in qt_message_fatal (context=..., message=)
at global/qlogging.cpp:1680
#11 QMessageLogger::fatal (this=0xbfc779e8, msg=0xb4dec9c0 "This program
requires an X86 processor that supports SSE2 extension, at least a 

[marble] [Bug 371010] Position Marker is gone/invisible

[Tom Hardy]

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

--- Comment #1 from Tom Hardy  ---
I just noticed the position marker is visible at zoom levels 5 and below.  It
is also visible at zoom level 6 if positioned well below the crosshairs; that
is, below about the 3/8th of the screen height.

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

[konsole] [Bug 374022] xos4 Terminus font - Cyrillic letters - wrong alignment and unexpected font substitution

[Igor Zhuravlov]

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

--- Comment #5 from Igor Zhuravlov  ---
My distro is openSUSE Leap 42.2 x86_64.
The same bug is in Konsole version 15.12.3 (openSUSE Leap 42.1 x86_64).

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

[konsole] [Bug 374022] xos4 Terminus font - Cyrillic letters - wrong alignment and unexpected font substitution

[Igor Zhuravlov]

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

Igor Zhuravlov  changed:

   What|Removed |Added

 Attachment #102938|0   |1
is obsolete||

--- Comment #4 from Igor Zhuravlov  ---
Created attachment 102939
  --> https://bugs.kde.org/attachment.cgi?id=102939=edit
xos4 Terminus font in xterm looks ok

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

[konsole] [Bug 374022] xos4 Terminus font - Cyrillic letters - wrong alignment and unexpected font substitution

[Igor Zhuravlov]

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

Igor Zhuravlov  changed:

   What|Removed |Added

 Attachment #102936|0   |1
is obsolete||

--- Comment #3 from Igor Zhuravlov  ---
Created attachment 102938
  --> https://bugs.kde.org/attachment.cgi?id=102938=edit
xos4 Terminus font in xterm looks ok

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

[konsole] [Bug 374022] xos4 Terminus font - Cyrillic letters - wrong alignment and unexpected font substitution

[Igor Zhuravlov]

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

--- Comment #2 from Igor Zhuravlov  ---
Created attachment 102937
  --> https://bugs.kde.org/attachment.cgi?id=102937=edit
xos4 Terminus font in konsole looks wrong

Cyrillic letters are replaced by another font. As a result, wrong width and
alignment. Notice in last line cursor "eats" some letters at the end:
- must be: "Для продолжения нажмите любую клавишу..."
- but is shown: "Для продолжения нажмите любую клав"

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

[konsole] [Bug 374022] xos4 Terminus font - Cyrillic letters - wrong alignment and unexpected font substitution

[Igor Zhuravlov]

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

--- Comment #1 from Igor Zhuravlov  ---
Created attachment 102936
  --> https://bugs.kde.org/attachment.cgi?id=102936=edit
xos4 Terminus font in xterm looks ok

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

[dolphin] [Bug 374019] Searching for one type of content under "search for" and then switching to another type of content only shows initial content types

[Paul M]

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

--- Comment #4 from Paul M  ---
> Could not reproduce on Arch with dolphin 16.12, frameworks 5.29, plasma
> 5.8.4. Does the same behaviour occur for you on a new user?

Just created a new user to test and, yes, exactly the same odd behaviour occurs
for a new user. 

(Dolphin 16.08.2, OpenSUSE Leap 42.2, Plasma 5.8.3, Frameworks 5.26.0, Baloo5
5.26.0-2.1, baloo5-widgets 16.08.2-1.1)

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

[konsole] [Bug 374022] New: xos4 Terminus font - Cyrillic letters - wrong alignment and unexpected font substitution

[Igor Zhuravlov]

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

Bug ID: 374022
   Summary: xos4 Terminus font - Cyrillic letters - wrong
alignment and unexpected font substitution
   Product: konsole
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: zhuravlov...@ya.ru
  Target Milestone: ---

Created attachment 102935
  --> https://bugs.kde.org/attachment.cgi?id=102935=edit
xos4 Terminus font in "kcmshell5 fontinst" looks ok

When selecting "xos4 Terminus" font, Cyrillic letters are rendered by another
font family, so its width and alignment is wrong. The problem is seen with all
font style and size combinations excepting one: Regular, 9pt.

While it is displayed correctly in "kcmshell5 fontinst" and in xterm, e.g.
> xterm -xrm 'XTerm*font: 
> -xos4-terminus-medium-r-normal-*-14-*-*-*-*-*-iso10646-*'

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

[ksysguard] [Bug 373935] Bar graph does not allow you to change sensor label

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #1 from kishor...@gmail.com ---
(In reply to Paul M from comment #0)
> If you add a sensor as a bar graph and
> right-click->properties->Sensors->Edit... the change in label is not saved.

I don't have an option to edit the label on Arch with ksysguard 5.8.4. Does
opensuse make modifications to the program while packaging it?

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

[dolphin] [Bug 374019] Searching for one type of content under "search for" and then switching to another type of content only shows initial content types

[bugzilla_noreply]

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

kishor...@gmail.com changed:

   What|Removed |Added

 CC||kishor...@gmail.com

--- Comment #3 from kishor...@gmail.com ---
(In reply to Paul M from comment #0)
> To Reproduce:
> 1. Select, for example, "Images" in the "Search For" section in the left
> panel.
> 2. Enter your search term and images of that type are successfully displayed.
> 3. Under the "Search For" section on the left change to, for example,
> "Videos" and the search for that term now is not updated with videos as
> expected, rather shows ALL videos. (unexpected behaviour 1)
> 4. Enter a new search term in the search box and now instead of videos (as
> now selected) it still provides results for image searches with new term!!!
> (unexpected behaviour 2)
> 
> System: OpenSUSE Leap 42.2, KDE 5.8.3, KDE Frameworks 5.26.0

Could not reproduce on Arch with dolphin 16.12, frameworks 5.29, plasma 5.8.4.
Does the same behaviour occur for you on a new user?

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

[dolphin] [Bug 374019] Searching for one type of content under "search for" and then switching to another type of content only shows initial content types

[Paul M]

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

--- Comment #2 from Paul M  ---
(In reply to Paul M from comment #1)
> What I have called "Unexpected behaviour 1" also seems to be discussed in
> bug 261148

Not the same at all -- please ignore this comment.

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

[dolphin] [Bug 374019] Searching for one type of content under "search for" and then switching to another type of content only shows initial content types

[Paul M]

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

--- Comment #1 from Paul M  ---
What I have called "Unexpected behaviour 1" also seems to be discussed in
#261148

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

[dolphin] [Bug 374019] Searching for one type of content under "search for" and then switching to another type of content only shows initial content types

[Paul M]

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

Paul M  changed:

   What|Removed |Added

Product|BalooWidgets|dolphin
  Component|general |search
Version|unspecified |16.08.2

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

[BalooWidgets] [Bug 374019] Searching for one type of content under "search for" and then switching to another type of content only shows initial content types

[Paul M]

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

Paul M  changed:

   What|Removed |Added

Product|dolphin |BalooWidgets
  Component|search  |general
Version|16.08.2 |unspecified

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

[dolphin] [Bug 374019] Searching for one type of content under "search for" and then switching to another type of content only shows initial content types

[Paul M]

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

Paul M  changed:

   What|Removed |Added

  Component|general |search

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

[ksysguard] [Bug 373935] Bar graph does not allow you to change sensor label

[Paul M]

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

Paul M  changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

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

[krita] [Bug 374021] New: Krita 3.1 Crop tool - Tool Options - Ratio Up/Down buttons changes value by 1.0 per step. Too large

[Tyson Tan]

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

Bug ID: 374021
   Summary: Krita 3.1 Crop tool - Tool Options - Ratio Up/Down
buttons changes value by 1.0 per step. Too large
   Product: krita
   Version: 3.1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: tyson...@mail.com
  Target Milestone: ---

In Krita 3.1, Crop tool - Tool Options - Ratio Up/Down buttons changes value by
1.0 per step. This is just too large. Those buttons are there to do small
tweaks. But now one click you go from square to noodle, making them useless in
most situations. They should change the value by 0.01 per step, like it was
before.

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

[krita] [Bug 374020] New: Save/Export dialogue doesn't pre-select last-used file type in Krita 3.1.0 during the same session

[Tyson Tan]

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

Bug ID: 374020
   Summary: Save/Export dialogue doesn't pre-select last-used file
type in Krita 3.1.0 during the same session
   Product: krita
   Version: 3.1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: tyson...@mail.com
  Target Milestone: ---

In Krita 3.1.0, Save/Export dialogue always pre-select Krita Document file
type. I don't remember this was the supposed behavior.

We don't need Krita to remember last-used file type after closing it. But in
the same session, it's very useful for Krita to remember it so exporting large
amount of pictures as one certain file type gets easier.

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

[dolphin] [Bug 374019] New: Searching for one type of content under "search for" and then switching to another type of content only shows initial content types

[Paul M]

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

Bug ID: 374019
   Summary: Searching for one type of content under "search for"
and then switching to another type of content only
shows initial content types
   Product: dolphin
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: k...@paulmcauley.com
  Target Milestone: ---

To Reproduce:
1. Select, for example, "Images" in the "Search For" section in the left panel.
2. Enter your search term and images of that type are successfully displayed.
3. Under the "Search For" section on the left change to, for example, "Videos"
and the search for that term now is not updated with videos as expected, rather
shows ALL videos. (unexpected behaviour 1)
4. Enter a new search term in the search box and now instead of videos (as now
selected) it still provides results for image searches with new term!!!
(unexpected behaviour 2)

System: OpenSUSE Leap 42.2, KDE 5.8.3, KDE Frameworks 5.26.0

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

[krita] [Bug 374018] original layers invisible

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|FIXED   |INVALID

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

[krita] [Bug 374018] original layers invisible

[T . Reyes]

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

--- Comment #2 from T. Reyes <22tre...@gmail.com> ---
resolved, the advanced color selector was not locked into the sidebar, and
covered the top of the layers docket. silly me.

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

[krita] [Bug 374018] original layers invisible

[T . Reyes]

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

T. Reyes <22tre...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #1 from T. Reyes <22tre...@gmail.com> ---
resolved, the advanced color selector was not locked into the sidebar, and
covered the top of the layers docket. silly me.

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

[krita] [Bug 374018] New: original layers invisible

[T . Reyes]

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

Bug ID: 374018
   Summary: original layers invisible
   Product: krita
   Version: unspecified
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Layer Stack
  Assignee: krita-bugs-n...@kde.org
  Reporter: 22tre...@gmail.com
  Target Milestone: ---

When krita loads, the layer docker is blank. The lower icons are present and
responsive, but you cannot see the layers. You can make new layers, but you
still cant see new layers created. New layers function properly, except you
cannot switch to the other layers. Found a workaround: pressing the copy
function repeatedly, copies of the layers become visible in panel. Existing,
original layers remain invisible when copies appear.

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

[kdeconnect] [Bug 374017] New: Stream audio to Android device

[evea]

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

Bug ID: 374017
   Summary: Stream audio to Android device
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: everm...@pc-portal.at
  Target Milestone: ---

It would be great if you could enable audio output to you Android Device.
Looks like it should be quite simple with PulseAudio:
http://superuser.com/questions/605445/how-to-stream-my-gnu-linux-audio-output-to-android-devices-over-wi-fi

Which would give you free wireless headphones.

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

[plasmashell] [Bug 373865] plasmashell crashes on usb disconnect

[Adam Reed]

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

--- Comment #10 from Adam Reed  ---
Another app crashes when KVM switches to a different computer:

Application: drkonqi (drkonqi), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f96c69b3780 (LWP 11414))]

Thread 3 (Thread 0x7f96a0761700 (LWP 11426)):
#0  0x7f96c0b7a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f96a71b7a73 in  () at /usr/lib64/dri/r600_dri.so
#2  0x7f96a71b71f7 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7f96c0b760a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f96c24ce02d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f96b7371700 (LWP 11416)):
#0  0x7f96c24c5bfd in poll () at /lib64/libc.so.6
#1  0x7f96bdfeb422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f96bdfed00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f96b96c63c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f96c2bc032f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f96c0b760a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f96c24ce02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f96c69b3780 (LWP 11414)):
[KCrash Handler]
#6  0x7f96c241e0c7 in raise () at /lib64/libc.so.6
#7  0x7f96c241f478 in abort () at /lib64/libc.so.6
#8  0x7f96c245b784 in  () at /lib64/libc.so.6
#9  0x7f96c2461026 in malloc_printerr () at /lib64/libc.so.6
#10 0x7f96c2461d53 in _int_free () at /lib64/libc.so.6
#11 0x7f96b94803f1 in XIQueryDevice () at /usr/lib64/libXi.so.6
#12 0x7f96b96e7d74 in QXcbConnection::touchDeviceForId(int) () at
/usr/lib64/libQt5XcbQpa.so.5
#13 0x7f96b96e94ed in QXcbConnection::xi2SetupDevices() () at
/usr/lib64/libQt5XcbQpa.so.5
#14 0x7f96b96e9ba0 in QXcbConnection::xi2HandleHierachyEvent(void*) () at
/usr/lib64/libQt5XcbQpa.so.5
#15 0x7f96b96eb93b in QXcbConnection::xi2HandleEvent(xcb_ge_event_t*) () at
/usr/lib64/libQt5XcbQpa.so.5
#16 0x7f96b96c434d in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() at /usr/lib64/libQt5XcbQpa.so.5
#17 0x7f96b96c601b in QXcbConnection::processXcbEvents() () at
/usr/lib64/libQt5XcbQpa.so.5
#18 0x7f96c2dccac6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#19 0x7f96c3a7fe7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#20 0x7f96c3a84cc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#21 0x7f96c2d9be95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#22 0x7f96c2d9e057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#23 0x7f96c2df38f3 in  () at /usr/lib64/libQt5Core.so.5
#24 0x7f96c01fbc84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#25 0x7f96c01fbed8 in  () at /usr/lib64/libglib-2.0.so.0
#26 0x7f96c01fbf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#27 0x7f96c2df2d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#28 0x7f96c2d99d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#29 0x7f96c2da18f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#30 0x004394be in main ()

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

[Spectacle] [Bug 374009] Spectacle keeps hanging my system

[Rajinder Yadav]

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

--- Comment #4 from Rajinder Yadav  ---
typos: checkout should be checkbox

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

[Spectacle] [Bug 374009] Spectacle keeps hanging my system

[Rajinder Yadav]

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

--- Comment #3 from Rajinder Yadav  ---
I believe the problem show up when

1. I have "On Click" checkout selected
2. Area is "Rectangular Region"

When I click on the "Take New Screenshot" button, and then click once, at t his
point the screens dimmed, around this period the hang will occur.

The mouse is continue to move, screen remain dimmed. I an unable to click to
start area selection. My keyboard stop functioning and I am unable to escape
out of capture mode.

I am not sure if it matters that "On Click" checkout is selected, just that
last time I was using the tool it was selected.

My suggestion:

* When area is "Rect. Region" selection, doesn't make sense to have option "On
click" available.

* When Window under cursor is selected it make sense to click on a window, this
should be implicit and not require a "On Click" option.

* Active Window doesn't make sense, the active window will be "Spectable" right
and you will be forced to "click on another window", the same as my previous
point.

This GUI could be simplified too many conflicting and confusing "needless"
options.

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

[neon] [Bug 373934] Konsole can not load any nerd-fonts/Overpass

[Josh Benham]

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

--- Comment #7 from Josh Benham  ---
Created attachment 102934
  --> https://bugs.kde.org/attachment.cgi?id=102934=edit
sudo fc-cache -fv ~/.local/share/fonts

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

[neon] [Bug 373934] Konsole can not load any nerd-fonts/Overpass

[Josh Benham]

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

--- Comment #6 from Josh Benham  ---
Harald Sitter

I have just installed a completely blank Neon User Edition. These are the
commands I am running.

```
sudo apt update
sudo apt upgrade
sudo apt install git (Makes sense)

git clone https://github.com/ryanoasis/nerd-fonts.git ~/.nerd_fonts
cd ~/.nerd_fonts
sudo ./install.sh
```

Nothing shows after doing this.

Attaching an image of some feedback.

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

[Breeze] [Bug 373668] Lock Screen should warn when the keyboard status is not default (layout/capslock)

[Anton]

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

Anton  changed:

   What|Removed |Added

Summary|Tiny keyboard layout|Lock Screen should warn
   |indicator is the Lock   |when the keyboard status is
   |Screen  |not default
   ||(layout/capslock)

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

[Breeze] [Bug 373668] Tiny keyboard layout indicator is the Lock Screen

[Anton]

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

Anton  changed:

   What|Removed |Added

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

--- Comment #9 from Anton  ---
Honestly, I don't even need this indicator all the time. I need some kind of
warning when capslock is "on" or layout of keyboard is not default.

So I see two options: 
 - move it next to the password input box and display non-default keyboard
status
 - (hate to say it) In windows, they display a balloon box under input box, but
it looks strange, not inline with the main design.

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

[kile] [Bug 374016] New: Abbreviations not working

[Amaro]

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

Bug ID: 374016
   Summary: Abbreviations not working
   Product: kile
   Version: 2.9.60
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: user interface
  Assignee: michel.lud...@kdemail.net
  Reporter: am...@fisica.ist.utl.pt
  Target Milestone: ---

With the master branch for kile 
Version 2.9.60
Using:
KDE Frameworks 5.27.0
Qt 5.7.1 (built against 5.7.0)

the completion of abbreviations, either auto- or via ctrl+alt+space key-combo
isn't working, the abbreviation letters are erased instead. 
The abbreviations are properly listed in the Abbreviation sidebar, so they are
being read. For example, the abbreviation q1=\,q_{1}
but if I type q1+ctrl+alt+space, then q1 disappears and no code is inserted.

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

[kalarm] [Bug 373848] Indicator not showing in Ubuntu Unity 16.10 (4:16.04.3-0ubuntu2)

[Sienile]

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

Sienile  changed:

   What|Removed |Added

   Severity|major   |normal

--- Comment #2 from Sienile  ---
I was using Unity when I encountered the lack of an icon.

I have since added a recurring alarm and the icon is now present. It just seems
odd that the icon is missing entirely with no alarm set and not simply switched
to a disabled alarm icon.

I install Kalarm whenever I set up a clean install and usually don't set an
alarm right away because I would not have yet moved over my custom alarm
sounds. While most users may immediately set an alarm at first run, I imagine
several users that prefer Kalarm to the various other available alarms may
experience the same issue and try to resolve it before setting an alarm (as I
did for nearly a day).

I downgraded the importance to 'normal', but it would be nice to have this
altered whenever a new update comes out.

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

[clazy] [Bug 373947] Signals false positive

[Sergio Martins]

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

--- Comment #3 from Sergio Martins  ---
Git commit 789c9eb0cd108ddcc839815901462e12cd60c825 by Sergio Martins.
Committed on 21/12/2016 at 23:25.
Pushed by smartins into branch 'master'.

incorrect-emit: Don't warn about emit in CTOR if inside a lambda

The emit can be inside a lambda, which is fine, since it probably
will be emitted later and not when CTOR is being run.

M  +3-0checks/level1/incorrect-emit.cpp
M  +1-0tests/incorrect-emit/main.cpp

https://commits.kde.org/clazy/789c9eb0cd108ddcc839815901462e12cd60c825

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

[okteta] [Bug 182577] Okteta unable to load large files

[Hans-Peter Jansen]

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

Hans-Peter Jansen  changed:

   What|Removed |Added

 CC||h...@urpla.net

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

[kdenlive] [Bug 374015] New: Make multiple executables accessible in kdenlive AppImage

[Lutz Vieweg]

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

Bug ID: 374015
   Summary: Make multiple executables accessible in kdenlive
AppImage
   Product: kdenlive
   Version: Appimage | Snap
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Installation
  Assignee: vpi...@kde.org
  Reporter: k...@5t9.de
  Target Milestone: ---

The kdenlive AppImage contains multiple executables (besides the main kdenlive
executable) that would be useful to be accessible to run on their own - most
prominently "melt", but probably also "ffmpeg".

According to the AppImage documentation, this should be trivially possible by
including more "*.desktop"-files than just the "kdenlive.desktop" file, so e.g.
one additional for "melt" and one for "ffmpeg".

Rationale: kdenlive has always had the ability to create scripts for rendering
videos independently of a running kdenlive instance/GUI. I for one need to use
such scripts because the videos I render are long and complex enough to require
~10 GB RAM and many hours of rendering, and it's very inconvenient to keep the
kdenlive GUI open at the same time. However, running "melt" on its own is
currently not possible with the AppImage.

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

[trojita] [Bug 374000] Trojita fails to load, re-location error

[Jan Kundrát]

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

Jan Kundrát  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

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

[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated

[hotschi]

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

--- Comment #5 from hotschi  ---
Comment on attachment 102929
  --> https://bugs.kde.org/attachment.cgi?id=102929
QT-Creator - Fonts are broken

font rendering fails in the QT-Creator

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

[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated

[bugzilla_noreply]

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

--- Comment #4 from hots...@gmx.at ---
Created attachment 102933
  --> https://bugs.kde.org/attachment.cgi?id=102933=edit
How the pdf should look like

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

[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated

[bugzilla_noreply]

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

--- Comment #3 from hots...@gmx.at ---
Created attachment 102932
  --> https://bugs.kde.org/attachment.cgi?id=102932=edit
pdf rendering fails

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

[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated

[bugzilla_noreply]

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

--- Comment #2 from hots...@gmx.at ---
Created attachment 102931
  --> https://bugs.kde.org/attachment.cgi?id=102931=edit
How KMail fails

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

[plasmashell] [Bug 373427] Plasma locks up in nouveau DRI2GetBuffersWithFormat creating new windows.

[Anthony Messina]

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

Anthony Messina  changed:

   What|Removed |Added

 CC||amess...@messinet.com

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

[plasmashell] [Bug 374014] Plasmashell renders fonts in QT5-Apps pixelated

[bugzilla_noreply]

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

--- Comment #1 from hots...@gmx.at ---
Created attachment 102930
  --> https://bugs.kde.org/attachment.cgi?id=102930=edit
Fontview - Fonts on the right side are broken

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

[plasmashell] [Bug 374014] New: Plasmashell renders fonts in QT5-Apps pixelated

[bugzilla_noreply]

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

Bug ID: 374014
   Summary: Plasmashell renders fonts in QT5-Apps pixelated
   Product: plasmashell
   Version: 5.8.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: hots...@gmx.at
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 102929
  --> https://bugs.kde.org/attachment.cgi?id=102929=edit
QT-Creator - Fonts are broken

If the scaling-factor in Systemsettings->Hardware->Display & Monitor->scale
display differs from 1 (e.g. 1.4), the font-rendering in QT fails and you get
pixelated fonts for QT-Apps.

If you use 1.5 it is not as worse as using 1.4 or 1.3 but it is still not
perfect.

Using a failing scaling-factor results in KMail displaying the emails in a
"broken way", so you are unable to click on links or reply to emails.

I am using an 3k-Monitor (2880*1680 Pixels). 

If you set the DPI in Systemsettings->Font->force dpi to a higher number (e.g.
144) and the scaling factor to 1 it works perfectly.

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

[kdevelop] [Bug 374013] New: Crash in highlighting

[Francis Herne]

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

Bug ID: 374013
   Summary: Crash in highlighting
   Product: kdevelop
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Language Support: PHP
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@flherne.uk
  Target Milestone: ---

Using recent git 0070511, and similar kdevplatform/kdevelop.

On opening a group of files (over sftp, in case that matters), KDevelop crashed
with this trace:

(gdb) bt full
#0  0x7f1c861cd538 in KDevelop::AbstractType::d_func() const (this=0x0) at
/home/flh/projects/kdevplatform/language/duchain/types/abstracttype.h:286
#1  0x7f1c861cceb0 in KDevelop::AbstractType::modifiers() const (this=0x0)
at /home/flh/projects/kdevplatform/language/duchain/types/abstracttype.cpp:52
#2  0x7f1c56e59c59 in
HighlightingInstance::typeForDeclaration(KDevelop::Declaration*,
KDevelop::DUContext*) const (this=0x7f1c3c6c0110, decl=0x7f1c3c660a60,
context=0x7f1c3c0f5d30)
at /home/flh/projects/kdev-php/phphighlighting.cpp:45
#3  0x7f1c86251520 in
KDevelop::CodeHighlightingInstance::highlightUse(KDevelop::DUContext*, int,
QColor const&) (this=0x7f1c3c6c0110, context=0x7f1c3c0f5d30, index=2,
color=...)
at
/home/flh/projects/kdevplatform/language/highlighting/codehighlighting.cpp:474
type = KDevelop::HighlightingEnumContainer::ErrorVariableType
decl = 0x7f1c3c660a60
#4  0x7f1c862508ed in
KDevelop::CodeHighlightingInstance::highlightDUChain(KDevelop::DUContext*,
QHash, QVector)
(this=0x7f1c3c6c0110, context=0x7f1c3c0f5d30, colorsForDeclarations=...,
declarationsForColors=...) at
/home/flh/projects/kdevplatform/language/highlighting/codehighlighting.cpp:301
decl = 0x7f1c3c660a60
color =
  {cspec = QColor::Rgb, ct = {argb = {alpha = 65535, red = 12938,
green = 32146, blue = 12578, pad = 0}, ahsv = {alpha = 65535, hue = 12938,
saturation = 32146, value = 12578, pad = 0}, acmyk = {alpha = 65535, cyan =
12938, magenta = 32146, yellow = 12578, black = 0}, ahsl = {alpha = 65535, hue
= 12938, saturation = 32146, lightness = 12578, pad = 0}, array = {65535,
12938, 32146, 12578, 0}}}
a = 2
lock = {m_lock = 0x7f1c869921e0 , m_locked =
true, m_timeout = 0}
top = 0x7f1c3c02de60
takeFreeColors =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{ = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7f1c88f48c60
}, d = 0x7f1c88f48c60 }}
children = {d = 0x7f1c88f46e80 }
#5  0x7f1c86250aa9 in
KDevelop::CodeHighlightingInstance::highlightDUChain(KDevelop::DUContext*,
QHash, QVector)
(this=0x7f1c3c6c0110, context=0x7f1c3c02de60, colorsForDeclarations=...,
declarationsForColors=...) at
/home/flh/projects/kdevplatform/language/highlighting/codehighlighting.cpp:314
child = 0x7f1c3c0f5d30
_container_ = {c = {d = 0x7f1c3c0f9bd0}, i = {i = 0x7f1c3c0f9fd0}, e =
{i = 0x7f1c3c0fa0e8}, control = 1}
lock = {m_lock = 0x7f1c869921e0 , m_locked =
false, m_timeout = 0}
top = 0x7f1c3c02de60
takeFreeColors =
{> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{ = {static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d = 0x7f1c88f48c60
}, d = 0x7f1c88f48c60 }}
children = {d = 0x7f1c3c0f9bd0}
#6  0x7f1c8624fe34 in
KDevelop::CodeHighlightingInstance::highlightDUChain(KDevelop::TopDUContext*)
(this=0x7f1c3c6c0110, context=0x7f1c3c02de60)
at
/home/flh/projects/kdevplatform/language/highlighting/codehighlighting.cpp:212
#7  0x7f1c8624fb05 in
KDevelop::CodeHighlighting::highlightDUChain(KDevelop::ReferencedTopDUContext)
(this=0x274f170, context=...)
at
/home/flh/projects/kdevplatform/language/highlighting/codehighlighting.cpp:193
url = {m_index = 337154}
urlLock = {m_url = {m_index = 337154}}
lock = {m_lock = 0x7f1c869921e0 , m_locked =
false, m_timeout = 0}
revision = 0
__PRETTY_FUNCTION__ = "virtual void
KDevelop::CodeHighlighting::highlightDUChain(KDevelop::ReferencedTopDUContext)"
instance = 0x7f1c3c6c0110
highlighting = 0x677dcf8
#8  0x7f1c860a08c7 in KDevelop::ParseJob::highlightDUChain()
(this=0x59293a0) at

[kdenlive] [Bug 373890] Many icons missing from Kdenlive-16.12-x86_64.AppImage GUI

[Lutz Vieweg]

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

--- Comment #2 from Lutz Vieweg  ---
"Force Breeze Icons" in the "Settings" menu was already enabled by default.

BTW: Changing the status of this checkbox isn't possible: kdenlive says it
needs to restart to change this option, and after doing so, the checkbox is
always active.

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

[digikam] [Bug 374004] Different Images recognised as identical images

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
yes, exactly. Exif.Photo.ImageUniqueID is used to register image to database. 

Code relevant :

metadata parser :
https://cgit.kde.org/digikam.git/tree/libs/dmetadata/dmetadata.cpp#n981

used to register image in DB while scanning :
https://cgit.kde.org/digikam.git/tree/libs/database/item/imagescanner.cpp#n984

Gilles Caulier

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

[digikam] [Bug 374010] Segfault on accessing DNG file

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||54.0

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

[digikam] [Bug 374010] Segfault on accessing DNG file

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In|54.0|5.4.0

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

[digikam] [Bug 374010] Segfault on accessing DNG file

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|--- |FIXED
 CC||caulier.gil...@gmail.com
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from caulier.gil...@gmail.com ---
Yes, this crash is not reproducible here with 5.4.0 pre release AppImage. This
bundle use now Libraw 0.18 beta2.

So this problem will be fixed with next 5.4.0...

Gilles Caulier

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Cruz Enrique]

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

Cruz Enrique  changed:

   What|Removed |Added

 CC||cruzki...@gmail.com

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

[kalarm] [Bug 373848] Indicator not showing in Ubuntu Unity 16.10 (4:16.04.3-0ubuntu2)

[David Jarvie]

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

--- Comment #1 from David Jarvie  ---
I'm not sure how indicator icons work in Ubuntu, but on some systems certain
icons can be hidden by default unless they are manually shown. For example, in
the KDE Plasma desktop, clicking an up-arrow icon beside the other icons brings
up a list of hidden indicator icons (which can then be clicked in the same way
as the non-hidden icons). There is a settings dialog which can be used to
control this, so that any icon can be always displayed, always hidden or use
automatically controlled visibility.

KAlarm by default hides its icon when no alarms are active, so I would expect
the behaviour you are seeing. The only question is how you get access to hidden
icons in Ubuntu.

What desktop are you using - Unity, Gnome 3 or what?

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

[digikam] [Bug 374012] Binary "Exif.Photo.UserComment" converted to "METADATA-START" caption at import

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
Please check if problem exists yet with 5.4.0 pre-release as Linux universal
bundle. This one use Exiv2 0.26-svn which is not yet released but which
introduce more than 200 bugfixes since Exiv2 0.25.

The bundle can be downloaded here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

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

[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started

[bugzilla_noreply]

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

--- Comment #42 from caulier.gil...@gmail.com ---
Just for info, last KF5 5.29.0 is now used to build digiKam bundles. In this
KF5 release, Solid changelog report : "winutils_p.h: Restore compatibility with
WinXP SDK".

This can be the solution of the problem.

So please check if new Windows installer work fine now, as Maik said.
Thanks in advance for your feedback.

Gilles Caulier

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

[digikam] [Bug 374012] New: Binary "Exif.Photo.UserComment" converted to "METADATA-START" caption at import

[Blomi]

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

Bug ID: 374012
   Summary: Binary "Exif.Photo.UserComment" converted to
"METADATA-START" caption at import
   Product: digikam
   Version: 5.3.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: im...@web.de
  Target Milestone: ---

Created attachment 102928
  --> https://bugs.kde.org/attachment.cgi?id=102928=edit
Image before and after the import

When importing images with binary UserComment the image caption is set to
"METADATA-START".

I import an image via Import/Add Images which has a binary value in
Exif.Photo.UserComment.
I select one image which hasn't a description yet and press "Download
selected".
Afterwards in digikam this image has the caption "METADATA-START".
exiv2 output before:
Exif.Photo.UserComment   Undefined 4104  (Binary value
suppressed)

and afterwards:
Exif.Photo.UserComment   Undefined  22  METADATA-START

I would expect digikam to either interpret the binary value or completely
ignore it, but not to fill the captions with "METADATA-START".

exiv2 0.25 001900 (64 bit build)

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

[plasmashell] [Bug 374011] New: Plasma crash during task switch

[Zsombor]

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

Bug ID: 374011
   Summary: Plasma crash during task switch
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: zo...@mailbox.hu
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-51-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

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

I've clicked on a dolphin window, and quickly tried to alt-tab to a different
console, when the crash happened

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
[KCrash Handler]
#6  0x7f8e958df5e0 in
QAbstractAnimationJob::setState(QAbstractAnimationJob::State) () at
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f8e96263291 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f8e931f5c01 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f8e93ccb05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7f8e93cd0516 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7f8e931c638b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f8e931c8786 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f8e9321c3c3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f8e8f60a1a7 in g_main_context_dispatch (context=0x7f8e7c0016f0) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3154
#15 0x7f8e8f60a1a7 in g_main_context_dispatch
(context=context@entry=0x7f8e7c0016f0) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3769
#16 0x7f8e8f60a400 in g_main_context_iterate
(context=context@entry=0x7f8e7c0016f0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3840
#17 0x7f8e8f60a4ac in g_main_context_iteration (context=0x7f8e7c0016f0,
may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
#18 0x7f8e9321c7cf in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f8e931c3b4a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f8e931cbbec in QCoreApplication::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00432d4a in main ()

Reported using DrKonqi

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

[kalarm] [Bug 373886] regression: cannot adjust alarm date for new alarms with cursor keys anymore

[David Jarvie]

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

David Jarvie  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from David Jarvie  ---
The widget used to edit the date looks as if it should still respond to
up-arrow and page-up, but for some reason it doesn't work in the alarm edit
dialog.

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

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

[Rolf Eike Beer]

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

Rolf Eike Beer  changed:

   What|Removed |Added

 CC||k.zimmerm...@online.de

--- Comment #2 from Rolf Eike Beer  ---
*** Bug 373994 has been marked as a duplicate of this bug. ***

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

[kgpg] [Bug 373994] crash kgpg

[Rolf Eike Beer]

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

Rolf Eike Beer  changed:

   What|Removed |Added

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

--- Comment #1 from Rolf Eike Beer  ---


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

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

[digikam] [Bug 374010] New: Segfault on accessing DNG file

[Malte Cornils]

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

Bug ID: 374010
   Summary: Segfault on accessing DNG file
   Product: digikam
   Version: 5.3.0
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Import
  Assignee: digikam-de...@kde.org
  Reporter: ma...@cornils.net
  Target Milestone: ---

While accessing an older collection on a removable drive, digikam (Linux x64
appimage 5.3.0 on Ubuntu 16.04 LTS) eventually segfaults (on the same image,
which is 64 MB big, and can be found for the next few weeks on
http://srv.cornils.net/DSC09641-hdr.dng):

digikam.dimg:
"/media/mcornils/82aad9c3-7dc9-4db0-9616-177ee44af6c7/fotos/2012-09-01 Nepal:
Tatopani, Dhulikhel, Bakthapur, Kathmandu, Patan,
Langtang/hdrenblend/DSC09641-hdr.dng"  : RAW file identified
digikam.rawengine: LibRaw: failed to run open_file:  Unsupported file format or
not RAW file
digikam.dimg:
"/media/mcornils/82aad9c3-7dc9-4db0-9616-177ee44af6c7/fotos/2012-09-01 Nepal:
Tatopani, Dhulikhel, Bakthapur, Kathmandu, Patan,
Langtang/hdrenblend/DSC09641-hdr.dng"  : QIMAGE file identified
TIFFReadDirectory: Warning, foo: unknown field with tag 18246 (0x4746)
encountered.
TIFFReadDirectory: Warning, foo: unknown field with tag 18249 (0x4749)
encountered.
TIFFReadDirectory: Warning, foo: unknown field with tag 33421 (0x828d)
encountered.
TIFFReadDirectory: Warning, foo: unknown field with tag 33422 (0x828e)
encountered.
TIFFReadDirectory: Warning, foo: unknown field with tag 50341 (0xc4a5)
encountered.
/tmp/.mount_ChURHY/AppRun: Zeile 35:  5535 Speicherzugriffsfehler 
(Speicherabzug geschrieben) digikam.wrapper $@

Using Gilles Caulier's appimage for 5.4.0 (beta, I think) does not show this
issue, so this is mainly for reference and is probably in the same class of
issues as https://bugs.kde.org/show_bug.cgi?id=373500

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

[plasmashell] [Bug 373880] desktop background messed up after connecting external display (docking)

[Erik Quaeghebeur]

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

--- Comment #4 from Erik Quaeghebeur  ---
(In reply to Marco Martin from comment #1)
> can you post screenshots?

I'll do this once I get back to my work setup and the problem occurs.

(In reply to Marco Martin from comment #3)
> possible fix https://phabricator.kde.org/D3777

The fact that you encounter an issue in the same context and that you have
identified the underlying cause is hopeful. Great!

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

[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11

[Jack]

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

Jack  changed:

   What|Removed |Added

 CC|ostroffjh@users.sourceforge |
   |.net|

--- Comment #7 from Jack  ---
I agree the distribution is probably the right place for the initial report,
but it should also go upstream.  Remember, the correct action is not the
symlink (which is only a temporary fix) but modifying the application to not
use the ..._pthreads library any more, since the underlying library is now
thread-safe.  

In the case of rhythmbox (I don't run it myself, so I can't easily check) if it
isn't directly calling libgpgme, then they are correct that it would be gmime
or libtotem-plparser which needs to be corrected.

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

[Spectacle] [Bug 374009] Spectacle keeps hanging my system

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|ase...@kde.org  |m...@baloneygeek.com
  Component|general |General
Product|ksnapshot   |Spectacle

--- Comment #2 from Christoph Feck  ---
Please report one ticket per issue. Could you clarify exactly at which point
the system hangs?

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

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

[Evgeni]

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

--- Comment #80 from Evgeni  ---
Created attachment 102927
  --> https://bugs.kde.org/attachment.cgi?id=102927=edit
New crash information added by DrKonqi

kwin_x11 (5.8.3) using Qt 5.6.1

- What I was doing when the application crashed:
>From Chromium trying to install package from opensuse page and when i press
'1-click install' and new window opens for instalation software , crash message
appears but all continue to work after.

-- Backtrace (Reduced):
#6  QV4::Value::as (this=0x7f73cd2fa320) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/qml/jsruntime/qv4value_p.h:348
#7  QQmlBinding::write (this=this@entry=0x2da01e0, core=..., result=...,
isUndefined=, flags=...) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/qml/qml/qqmlbinding.cpp:257
#8  0x7f7494f6e24a in QQmlBinding::update (this=0x2da01e0, flags=...) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/qml/qml/qqmlbinding.cpp:191
#9  0x7f7494f772f6 in QQmlObjectCreator::finalize (this=0x2ed2570,
interrupt=...) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/qml/qml/qqmlobjectcreator.cpp:1193
#10 0x7f7494f0593b in QQmlComponentPrivate::complete (enginePriv=0x2896620,
state=state@entry=0x2ad3910) at
/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/qml/qml/qqmlcomponent.cpp:919

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

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

[Evgeni]

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

Evgeni  changed:

   What|Removed |Added

 CC||evgeni...@gmail.com

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

[ksnapshot] [Bug 374009] Spectacle keeps hanging my system

[Rajinder Yadav]

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

--- Comment #1 from Rajinder Yadav  ---
typo correction: 

3. Make "On Click" checkbox selected by default...

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

[ksnapshot] [Bug 374009] New: Spectacle keeps hanging my system

[Rajinder Yadav]

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

Bug ID: 374009
   Summary: Spectacle keeps hanging my system
   Product: ksnapshot
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: ase...@kde.org
  Reporter: rajind...@hotmail.com
  Target Milestone: ---

I am using the latest KDE from Kubuntu PPA backports, Plasama 5.8.4

Each time I use Spectacle most often than not my system will hang.

First of all, the experience is really crappy, really odd UX design.

1. Stop darkening the entire screen, the frame is good enough, doing too much
increases probability of more bugs! Probably why my system hangs.

2. When I select "Rectangle region", I am forced to click twice? why.

I should be able to click once, drag the mouse to create the rectangle region
of the area I want copied.

Right now, when I try to draw a rectangle region there is a lag to get going,
once click to start, 2nd click some times doesn't get registered. This is
really annoying,

3. Make "On Click" checkout selected by default. It's doesn't make sense when I
select to copy an active window I need to make another click for the checkbox
before I start. Most people will do it this way, forcing them to make an
additional mouse click is just bad UX design.

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

[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11

[Michael Tunnell]

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

--- Comment #6 from Michael Tunnell  ---
Here is the response from Rhythmbox developers on the issue, essentially saying
it is a distro level issue.

> rhythmbox ( -> ) libtotem-plparser ( -> )  libgmime ( -> ) libgpgme
>
> So, there is no direct relation between rhythmbox and libgpgme. Also, this 
> issue should be reported to the distribution maintainer, at best. The 
> symlinks are already there in my case ( Debian ).

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

[trojita] [Bug 374000] Trojita fails to load, re-location error

[DaveCooper]

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

--- Comment #2 from DaveCooper  ---
Thank you, Rex.  I'll do that now.  Dave

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

[krita] [Bug 374008] New: Any selection tool will not allow a selected item to be transformed, and instead select a portion off of the canvas.

[Elara Methone]

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

Bug ID: 374008
   Summary: Any selection tool will not allow a selected item to
be transformed, and instead select a portion off of
the canvas.
   Product: krita
   Version: 3.1.1
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: emethone54...@gmail.com
  Target Milestone: ---

When using any selection tool (mainly free select and circle select), the item
will be selected, but when clicking on the transformation tool, the entire
image will be selected, as well as a major extended rectangle or square
extending off of the main canvas, making moving and transforming very
difficult.  Copy/paste is also difficult to pull off with this problem.

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

[trojita] [Bug 374000] Trojita fails to load, re-location error

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

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

--- Comment #1 from Rex Dieter  ---
Appears to be a downstream fedora issue with packaging, I'd recommend you file
a bug @ bugzilla.redhat.com  against gpgme or kf5-gpgmepp component

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

[plasmashell] [Bug 355588] Switching between alternative widgets makes them lose settings

[Tony]

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

--- Comment #4 from Tony  ---
This bug somehow "got bigger", i used to have it only for alternate task
managers, as i reported here bug 368528. Now i get it for switching launchers.

Even worse, kicker does not remember my favorites after logging out.

Neon unstable.
Frameworks 5.30.0
QT 5.7.0
Plasma 5.8.90

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

[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7

[Tushar]

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

--- Comment #11 from Tushar  ---
Is the above information useful?

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

[konqueror] [Bug 374007] New: Konqueror 16.12 fails to load flash content

[avlas]

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

Bug ID: 374007
   Summary: Konqueror 16.12 fails to load flash content
   Product: konqueror
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: jsar...@gmail.com
  Target Milestone: ---

I guess this is because konqueror now uses webEngine.

One can test whether flash content works or not at:
http://www.adobe.com/software/flash/about/

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

[kontact] [Bug 374006] New: Kontact crashes when pressing "New" without any app (mail, calendar) open

[Kurt Seebauer]

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

Bug ID: 374006
   Summary: Kontact crashes when pressing "New" without any app
(mail, calendar) open
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kurt_seeba...@yahoo.de
  Target Milestone: ---

Application: kontact (5.4.0)

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

-- Information about the crash:
- What I was doing when the application crashed:
I started Kontact and immediately pressed the "New" dropdown button on the top
left. It does not crash if i select Mail in the list of applications and press
"New" then.

The crash can be reproduced every time.

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

Thread 27 (Thread 0x7f72718eb700 (LWP 6072)):
#0  0x7f73a69bb10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f739db880d9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f739db88719 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f739db888d0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f739db8546c in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f73aab1737f in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f7278c0d700 (LWP 6041)):
#0  0x7f73aab0e66d in poll () at /lib64/libc.so.6
#1  0x7f73a47c7876 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f73a47c798c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f73ab64479b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f73ab5ee1ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f73ab41c8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f73ab421558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f73aab1737f in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f73327fc700 (LWP 6036)):
#0  0x7f73a69bb10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f73979f7834 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f73979f7879 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0
#4  0x7f73aab1737f in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f7332ffd700 (LWP 6029)):
#0  0x7f73a69bb10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f739d656d00 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f739d63fb30 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f739d63febb in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f739d63bb4a in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f739e8d18de in  () at /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7f739e8d3c94 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7f739e8d3ce5 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7f739e8d3db9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#9  0x7f739db70efa in  () at /usr/lib64/libQt5WebEngineCore.so.5
#10 0x7f739db5b995 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#11 0x7f739db88e8a in  () at /usr/lib64/libQt5WebEngineCore.so.5
#12 0x7f739db8546c in  () at /usr/lib64/libQt5WebEngineCore.so.5
#13 0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0
#14 0x7f73aab1737f in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f73337fe700 (LWP 6028)):
#0  0x7f73a69bb10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f739db880d9 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f739db88719 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f739db888d0 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f739db8546c in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f73a69b5454 in start_thread () at /lib64/libpthread.so.0
#6  0x7f73aab1737f in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f7333fff700 (LWP 6027)):
#0  0x7f73aab0a6dd in read () at /lib64/libc.so.6
#1  0x7f7386b6d641 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7f73871fcfce in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7f73871fda40 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f73871fdb00 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f738720bb29 in  () at /usr/lib64/libpulse.so.0
#6  0x7f7386b9c1e8 in  () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so
#7  0x7f73a69b5454 in 

[kdelibs] [Bug 261539] Application crashed on exit [QRasterWindowSurface::~QRasterWindowSurface]

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|REOPENED|RESOLVED

--- Comment #74 from Christoph Feck  ---
Use Krusader 2.5.0, which is not based on Qt 4.

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

[kdevelop] [Bug 374003] clicking any button for "another instance of CTest still running" made KDevelop crash

[Rolf Eike Beer]

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

--- Comment #2 from Rolf Eike Beer  ---
For this to happen you must run all tests of the project at once, and one of
them needs to crash. Running the test that crashes alone does not trigger the
bug.

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

[Breeze] [Bug 374005] Kate, Krusader and Lokalize have too similar icons

[Andrej M .]

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

--- Comment #1 from Andrej M.  ---
Created attachment 102926
  --> https://bugs.kde.org/attachment.cgi?id=102926=edit
Oxygen icons of Krusader, Kate and Lokalize

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

[Breeze] [Bug 374005] New: Kate, Krusader and Lokalize have too similar icons

[Andrej M .]

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

Bug ID: 374005
   Summary: Kate, Krusader and Lokalize have too similar icons
   Product: Breeze
   Version: 5.8.2
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: andr...@ubuntu.si
CC: kain...@gmail.com
  Target Milestone: ---

Created attachment 102925
  --> https://bugs.kde.org/attachment.cgi?id=102925=edit
Breeze icons of Krusader, Kate and Lokalize

Breeze icons for Kate, Krusader and Lokalize have too much white areas. This
makes them really hard to tell apart if you have a lot of them open and for me
it's a huge regression from Oxygen icon set where the icons were clearly
different. Please see attached screenshots. I would suggest using more colors
in icons of Krusader and Lokalize.

Best Regards,
Andrej Mernik

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

[kdelibs] [Bug 261539] Application crashed on exit [QRasterWindowSurface::~QRasterWindowSurface]

[Landis]

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

--- Comment #73 from Landis  ---
Created attachment 102924
  --> https://bugs.kde.org/attachment.cgi?id=102924=edit
New crash information added by DrKonqi

krusader (2.4.0-beta3 "Single Step") on KDE Platform 4.14.9 using Qt 4.8.6

- What I was doing when the application crashed:

using krusader as normal. works fine while open
Quit
Crash! 
Every Time.

-- Backtrace (Reduced):
#6  0x7fb56df48d29 in QRasterWindowSurface::~QRasterWindowSurface
(this=0x29db4c0, __in_chrg=) at
painting/qwindowsurface_raster.cpp:117
#7  0x7fb56df48da9 in QRasterWindowSurface::~QRasterWindowSurface
(this=0x29db4c0, __in_chrg=) at
painting/qwindowsurface_raster.cpp:121
#8  0x7fb56df6107c in QWidgetBackingStore::~QWidgetBackingStore
(this=0x2db8dc0, __in_chrg=) at painting/qbackingstore.cpp:909
#9  0x7fb56dd9d709 in QWidgetBackingStoreTracker::destroy (this=0x2db8d10)
at kernel/qwidget.cpp:225
#10 0x7fb56dd9d8a9 in QWidgetPrivate::deleteExtra
(this=this@entry=0x297f450) at kernel/qwidget.cpp:1833

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

[kdevelop] [Bug 374003] clicking any button for "another instance of CTest still running" made KDevelop crash

[Rolf Eike Beer]

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

--- Comment #1 from Rolf Eike Beer  ---
I tried it again. Also clicking "No" crashed KDevelop. And of course it is
"Yes", not "kill".

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

[kdevelop] [Bug 374003] clicking any button for "another instance of CTest still running" made KDevelop crash

[Rolf Eike Beer]

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

Rolf Eike Beer  changed:

   What|Removed |Added

Summary|clicking "kill" for |clicking any button for
   |"another instance of CTest  |"another instance of CTest
   |still running" made |still running" made
   |KDevelop crash  |KDevelop crash

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

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

[Christoph Feck]

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

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

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

[kwin] [Bug 374002] kwin_x11 crash every time I login

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
Please use Breeze decoration as a workaround.

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

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

[digikam] [Bug 374004] New: Different Images recognised as identical images

[Blomi]

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

Bug ID: 374004
   Summary: Different Images recognised as identical images
   Product: digikam
   Version: 5.3.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: im...@web.de
  Target Milestone: ---

Created attachment 102923
  --> https://bugs.kde.org/attachment.cgi?id=102923=edit
Zip with the 3 images of the camera.

Different images are treated as identical images by digikam.

I've copied 3 images from my smartphone camera with a file browser into an
album.
I start digikam and browser to this album and wait until these pictures are
detected.
In the side-pane in Versions/Versions with the display option "Show available
versions and the applied filters in a combined list." for each picture only the
current image is shown below "Image History". Everything fine so far.
Now I select each picture (individual or together doesn't matter) a give these
one star.
When I now select one picture the other two images are shown in the section
"Identical Images" in the right side-pane. But the content of the pictures is
different.
I wouldn't expect that different images are shown as identical.

Besides that the pictures are shown as identical (I wouldn't bother too much),
within my album some as wrongly identical detected images are NOT shown in the
album view anymore (although they can be seen in the file browser).
Unfortunately I can't reproduce how this happened but this is very annoying.

The pictures are taken by a Samsung Galaxy S4.
The Exif-Information contains for each picture the same
Exif.Photo.ImageUniqueID of S13F0LAHA01.
In the database all 3 pictures have the same uuid S13F0LAHA01 in the table
ImageHistory.

Is the same ImageUniqueID given by the camera the root cause?
Do I have to manipulate the ImageUniqueID by my self before using digikam or
can digikam take care of this maybe not ideal behaviour of the smartphone?

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

[kdevelop] [Bug 374003] New: clicking "kill" for "another instance of CTest still running" made KDevelop crash

[Rolf Eike Beer]

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

Bug ID: 374003
   Summary: clicking "kill" for "another instance of CTest still
running" made KDevelop crash
   Product: kdevelop
   Version: 5.0.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: k...@opensource.sf-tec.de
  Target Milestone: ---

Application: kdevelop (5.0.3)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.9.0-1.g8c92422-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
I ran all 3 of my unittests, one of them segfaulted. Trying to run them again
later showed the warning "another instance of CTest is still running". Clicking
"kill it" killed KDevelop instead of just the test.

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

Thread 13 (Thread 0x7fe3ea7fc700 (LWP 15522)):
#0  0x7fe470b7c458 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe4776467b8 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe477642c00 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fe477645bcf in  () at /usr/lib64/libQt5Core.so.5
#4  0x7fe470b77734 in start_thread () at /lib64/libpthread.so.0
#5  0x7fe476f58d3d in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7fe3fc9eb700 (LWP 13127)):
#0  0x7fe476f5049d in poll () at /lib64/libc.so.6
#1  0x7fe46ea05314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fe46ea0542c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fe47784c84b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fe4777fb9cb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fe47764130a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fe477645bcf in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fe470b77734 in start_thread () at /lib64/libpthread.so.0
#8  0x7fe476f58d3d in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7fe3fd1ec700 (LWP 13051)):
#0  0x7fe470b7c0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe47764686b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe46bf073ff in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe46bf0adca in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe46bf0542b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe46bf08a26 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe477645bcf in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fe470b77734 in start_thread () at /lib64/libpthread.so.0
#8  0x7fe476f58d3d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fe3fd9ed700 (LWP 13050)):
#0  0x7fe470b7c0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe47764686b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe46bf073ff in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe46bf0adca in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe46bf0542b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe46bf0ae12 in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fe46bf0542b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fe46bf08a26 in ThreadWeaver::Thread::run() () at
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fe477645bcf in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fe470b77734 in start_thread () at /lib64/libpthread.so.0
#10 0x7fe476f58d3d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fe3fe1ee700 (LWP 13049)):
#0  0x7fe470b7c0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe47764686b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7fe46bf073ff in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
#3  0x7fe46bf0adca in  () at /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fe46bf0542b in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fe46bf08a26 in ThreadWeaver::Thread::run() () at

[kwin] [Bug 374002] New: kwin_x11 crash every time I login

[Staffan Palmroos]

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

Bug ID: 374002
   Summary: kwin_x11 crash every time I login
   Product: kwin
   Version: 5.8.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: spalmr...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.3)
 (Compiled from sources)
Qt Version: 5.6.2
Frameworks Version: 5.26.0
Operating System: Linux 4.8.15-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

Logging in to KDE crashes kwin_x11 every time. I think this is related to bug
#361236 but DrKonqi doesn't seem to allow me to add to that report. I just
wanted to upload my backtrace in case it's helpful.

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".
84  T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f3de80e1800 (LWP 3882))]

Thread 5 (Thread 0x7f3dd0b7b700 (LWP 3923)):
#0  0x7f3de79d7243 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3de58bb246 in qt_safe_select (nfds=8,
fdread=fdread@entry=0x7f3dc4000a78, fdwrite=fdwrite@entry=0x7f3dc4000d08,
fdexcept=fdexcept@entry=0x7f3dc4000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:65
#2  0x7f3de58bc9f2 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f3dc4000f98, writefds=0x7f3dc4000d08, readfds=0x7f3dc4000a78,
nfds=, this=0x7f3dc40008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f3dc40008e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f3de58bcfa4 in QEventDispatcherUNIX::processEvents
(this=0x7f3dc40008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f3de586f53a in QEventLoop::exec (this=this@entry=0x7f3dd0b7ad70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:206
#6  0x7f3de56bd9bd in QThread::exec (this=this@entry=0x7f3de8268580
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#7  0x7f3de81fa276 in QDBusConnectionManager::run (this=0x7f3de8268580
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#8  0x7f3de56c2323 in QThreadPrivate::start (arg=0x7f3de8268580 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:365
#9  0x7f3de7c974e0 in start_thread (arg=0x7f3dd0b7b700) at
pthread_create.c:334
#10 0x7f3de79de82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f3dc9ea5700 (LWP 3947)):
#0  0x7f3de79d7243 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f3de58bb246 in qt_safe_select (nfds=13,
fdread=fdread@entry=0x7f3db8000a78, fdwrite=fdwrite@entry=0x7f3db8000d08,
fdexcept=fdexcept@entry=0x7f3db8000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:65
#2  0x7f3de58bc9f2 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f3db8000f98, writefds=0x7f3db8000d08, readfds=0x7f3db8000a78,
nfds=, this=0x7f3db80008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f3db80008e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f3de58bcfa4 in QEventDispatcherUNIX::processEvents
(this=0x7f3db80008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f3de586f53a in QEventLoop::exec (this=this@entry=0x7f3dc9ea4d80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:206
#6  0x7f3de56bd9bd in QThread::exec (this=this@entry=0x1e34090) at
thread/qthread.cpp:500
#7  0x7f3de0878ca6 in QQmlThreadPrivate::run (this=0x1e34090) at
qml/ftw/qqmlthread.cpp:141
#8  0x7f3de56c2323 in QThreadPrivate::start (arg=0x1e34090) at
thread/qthread_unix.cpp:365
#9  0x7f3de7c974e0 in start_thread (arg=0x7f3dc9ea5700) at
pthread_create.c:334
#10 0x7f3de79de82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f3dc8dec700 (LWP 3995)):
#0  pthread_cond_wait () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3de4a77f65 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f3de4b61e40 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f3de4a77fa9 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f3de7c974e0 in start_thread (arg=0x7f3dc8dec700) at
pthread_create.c:334
#4  0x7f3de79de82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

[kaffeine] [Bug 373707] Wrong aspect ratio for dvb streams

[bugzilla_noreply]

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

johannes...@hotmail.com changed:

   What|Removed |Added

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

--- Comment #4 from johannes...@hotmail.com ---
Fixed by an update of vlc / vlc-core / vlc-devel and vlc-extras to
3.0.0-14.20161221

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

[KAccounts] [Bug 374001] New: kaccounts-integration crashes when configuring some online accounts

[bugzilla_noreply]

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

Bug ID: 374001
   Summary: kaccounts-integration crashes when configuring some
online accounts
   Product: KAccounts
   Version: git-latest
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: KCM
  Assignee: kde-telepathy-b...@kde.org
  Reporter: kwanza.p...@virginmedia.com
  Target Milestone: ---

The latest version kaccounts-integration (16.12.0) cannot create some types of
online accounts (e.g. google, facebook, ...). The generic error is "cannot find
generic-oauth plugin" despite the fact that the plugin is installed. To access
it, I ran "kcmshell5 kcm_kaccounts" under gdb. After the app starts, I choose
"Create" which brings up the menu list. Then choose any of the offending
protocols (e.g. google or facebook). An error dialog appears complaining about
the oauth plugin. Then the segmentation fault results with the following
backtrace:

*** Error in `/opt/kde/bin/kcmshell5': double free or corruption (!prev):
0x55a6b210 ***
=== Backtrace: =
Thread 1 "kcmshell5" received signal SIGABRT, Aborted.
0x778628af in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x778628af in raise () from /lib64/libc.so.6
#1  0x77863caa in abort () from /lib64/libc.so.6
#2  0x778a0460 in __libc_message () from /lib64/libc.so.6
#3  0x778a6816 in malloc_printerr () from /lib64/libc.so.6
#4  0x778a700e in _int_free () from /lib64/libc.so.6
#5  0x7fffd8b78042 in QTypedArrayData::deallocate
(data=)
at /opt/kde/include/qt5/QtCore/qarraydata.h:228
#6  QString::~QString (this=, __in_chrg=)
at /opt/kde/include/qt5/QtCore/qstring.h:1078
#7  QPair::~QPair (this=, __in_chrg=)
at /opt/kde/include/qt5/QtCore/qpair.h:49
#8  QHashNode, Tp::WeakPtr >::~QHashNode
(this=0x559b4e70, 
__in_chrg=) at /opt/kde/include/qt5/QtCore/qhash.h:147
#9  QHash, Tp::WeakPtr >::deleteNode2
(node=0x559b4e70)
at /opt/kde/include/qt5/QtCore/qhash.h:533
#10 0x75754d09 in QHashData::free_helper(void (*)(QHashData::Node*)) ()
   from /opt/kde/lib64/libQt5Core.so.5
#11 0x7fffd8b7600c in QHash,
Tp::WeakPtr >::freeData (
this=0x55877650, x=) at
/opt/kde/include/qt5/QtCore/qhash.h:573
#12 QHash, Tp::WeakPtr >::~QHash
(this=0x55877650, 
__in_chrg=) at /opt/kde/include/qt5/QtCore/qhash.h:252
#13 Tp::DBusProxyFactory::Cache::~Cache (this=0x55877640,
__in_chrg=)
at /usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/dbus-proxy-factory.cpp:223
#14 Tp::DBusProxyFactory::Cache::~Cache (this=0x55877640,
__in_chrg=)
at /usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/dbus-proxy-factory.cpp:225
#15 0x7fffd8b76159 in Tp::DBusProxyFactory::Private::~Private
(this=0x55877620, 
__in_chrg=) at
/usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/dbus-proxy-factory.cpp:50
#16 Tp::DBusProxyFactory::~DBusProxyFactory (this=0x55877540,
__in_chrg=)
at /usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/dbus-proxy-factory.cpp:85
#17 0x7fffd8b24019 in Tp::ConnectionFactory::~ConnectionFactory
(this=0x55877540, 
__in_chrg=) at
/usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/connection-factory.cpp:84
#18 0x7fffd8a48db1 in Tp::SharedPtr::~SharedPtr (this=0x55b46bd8, 
__in_chrg=) at
/usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/shared-ptr.h:139
#19 Tp::AccountManager::Private::~Private (this=0x55b46bb0,
__in_chrg=)
at /usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/account-manager.cpp:137
#20 0x7fffd8a48e3d in Tp::AccountManager::~AccountManager
(this=0x558354c0, __in_chrg=)
at /usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/account-manager.cpp:447
---Type  to continue, or q  to quit---
#21 0x7fffd8a48e99 in Tp::AccountManager::~AccountManager
(this=0x558354c0, __in_chrg=)
at /usr/src/debug/telepathy-qt-0.9.7/TelepathyQt/account-manager.cpp:448
#22 0x7fffd91e6dbc in ?? () from
/opt/kde/lib64/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so
#23 0x7fffd91e6e99 in ?? () from
/opt/kde/lib64/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so
#24 0x7fffe091a61e in qDeleteAll::const_iterator>
(end=..., begin=...)
at /opt/kde/include/qt5/QtCore/qalgorithms.h:323
#25 qDeleteAll > (c=...) at
/opt/kde/include/qt5/QtCore/qalgorithms.h:331
#26 UiPluginsManagerPrivate::~UiPluginsManagerPrivate (
this=0x7fffe0b2e980 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>, 
__in_chrg=) at
/usr/src/debug/kaccounts-integration-16.12.0/src/uipluginsmanager.cpp:57
#27 0x7fffe091a6a9 in (anonymous
namespace)::Q_QGS_s_instance::Holder::~Holder (this=, 
__in_chrg=) at

[kmymoney4] [Bug 373291] kMyMoney error loading shared library libgpgme-pthread.so.11

[Michael Tunnell]

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

--- Comment #5 from Michael Tunnell  ---
> No, please leave this open until kmymoney gets updated to not need the 
> pthreads library.  

I agree with this point . . . until it is fixed by the application the bug
report is still valid. I will also submit this bug report to the other
applications I experienced the issue with.

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

[frameworks-kio] [Bug 373658] KDEInit could not launch 'konsole'

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

 CC||kdelibs-b...@kde.org
   Assignee|h...@kde.org|fa...@kde.org
Version|5.8.4   |5.29.0
Product|plasmashell |frameworks-kio
  Component|Folder  |general
   Target Milestone|1.0 |---

--- Comment #13 from Antonio Rojas  ---
Or rather remove it altogether? AFAIK konsole overrides the window title
anyway, so this looks useless to me.

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

[trojita] [Bug 374000] New: Trojita fails to load, re-location error

[DaveCooper]

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

Bug ID: 374000
   Summary: Trojita fails to load,  re-location error
   Product: trojita
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Desktop GUI
  Assignee: trojita-b...@kde.org
  Reporter: d...@accuramatic.co.uk
  Target Milestone: ---

Trojita was working fine on Fedora 24.  After a dalliance with Gallium (big
mistake!) I went beck to Fedora 24.  Now I can't get Trojita to work - it won't
start.

journalctl gives following message "Dec 20 19:57:28 humble
trojita.desktop[2199]: trojita: relocation error:
/lib64/libKF5Gpgmepp-pthread.so.5: symbol gpgme_set_offline, version G"

  Any suggestions graefully received.  I'm not too proud to edit code!
Dave Cooper

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

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

[Andreas Hartmann]

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

--- Comment #78 from Andreas Hartmann  ---
(In reply to Bernhard Übelacker from comment #66)
> After the latest updates in Debian Testing I am not able to
> reproduce the crash anymore by switching from Breeze to Plastik decorations.
> 
> The updates contained mostly Qt from 5.6.1 to 5.7.1~20161021.
> And some packages libkf5* and kwin* got just rebuilt at the same version.

Leap 42.2: I switched to the QT5.7 / Frameworks5 repository and I couldn't see
the problem any more, too. But therefore, I got a lot of other problems /
crashes (e.g. with systemsettings5 and the desktop itself being suddenly
completely black). Therefore I decided to switch back to original packages
again and to use Breeze which works fine.

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