[k3b] [Bug 372094] Please restore wodim support

[Leslie Zhai]

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

Leslie Zhai  changed:

   What|Removed |Added

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

--- Comment #13 from Leslie Zhai  ---
https://quickgit.kde.org/?p=k3b.git=commit=abe673e2f1b9b016d3a9c3aaad42d808a80a0b4a

Migrating to libburnia ... https://bugs.kde.org/show_bug.cgi?id=137436

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Thomas Schmitt]

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

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

thank you for considering cdrskin and xorriso.

I have to point to some potential problems:

- libburn underneath both programs does on CD media only pure CD-ROM (data)
  or pure CD-DA (audio). Mixed mode, CD-XA, and other CD formats are not 
  supported.
  I think the missing features are covered by cdrdao.

- libisofs underneath does not produce UDF filesystems. This implies that 
  there is no way to produce a DVD video filesystem.
  For this use case, one will have to stay with mkisofs or genisoimage.


Have a nice day :)

Thomas

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

[kdeplasma-addons] [Bug 372218] Task switcher "Compact" ignores font anti-aliasing settings

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|kwin|kdeplasma-addons
   Assignee|kwin-bugs-n...@kde.org  |plasma-b...@kde.org
  Component|core|General

--- Comment #3 from Martin Gräßlin  ---
Moving to kdeplasma-addons as the compact switcher is part of addons.

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

[kmail2] [Bug 372244] New: Move "Mark read after seconds" to accounts settings

[Massimo Burcheri]

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

Bug ID: 372244
   Summary: Move "Mark read after seconds" to accounts settings
   Product: kmail2
   Version: 4.14.10
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: massimo.burch...@gmx.de
  Target Milestone: ---

This is kmail 4.14.11.

The option

"Mark selected message as read after __ seconds"

would be better placed as an account property as I have accounts where I don't
like to mark as read as some other person is the main owner of that account and
needs to be informed about unread mails. This is possible for instance with the
K-9 mail client.

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

[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

   Severity|minor   |wishlist
 CC||thomas.pfeif...@kde.org
  Flags||Usability+

--- Comment #13 from Martin Gräßlin  ---
@Thomas: I need an evaluation from usability perspective. Is it expected that
the menu does not open on meta press if an application grabbed keyboard? Or
should we consider the modifier only shortcut as bypassing everything.

>From a technical perspective I might not be able to block the meta shortcut on
X11, which would mean rollback to not providing the feature in case the
conclusion is that grabs should prevent opening it.

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

[plasmashell] [Bug 372243] New: KDE crashed when changing between windows

[Emilio Aburto]

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

Bug ID: 372243
   Summary: KDE crashed when changing between windows
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: eaburtolemi...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

I was changing to a VirtualBox running machine window and KDE crashed. Prior to
this I was setting up the virtual desktop shortcuts and tried doing it a couple
of times. Then, when changing windows, KDE crashed

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

Thread 8 (Thread 0x7f346e6d4700 (LWP 6038)):
#0  0x7ffe257c6b02 in clock_gettime ()
#1  0x7f353bb3b6b6 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7f353c2be1a1 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f353c4453a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7f353c445955 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#5  0x7f353c446cfe in  () at /usr/lib/libQt5Core.so.5
#6  0x7f3536decc89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#7  0x7f3536ded6ab in  () at /usr/lib/libglib-2.0.so.0
#8  0x7f3536ded89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#9  0x7f353c44772b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#10 0x7f353c3f123a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#11 0x7f353c2140f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#12 0x7f353c218d78 in  () at /usr/lib/libQt5Core.so.5
#13 0x7f353b328454 in start_thread () at /usr/lib/libpthread.so.0
#14 0x7f353bb2e7df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f347c304700 (LWP 730)):
#0  0x7ffe257c6b02 in clock_gettime ()
#1  0x7f353bb3b6b6 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7f353c2be1a1 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f353c4453a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7f353c445955 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#5  0x7f353c446cfe in  () at /usr/lib/libQt5Core.so.5
#6  0x7f3536decc89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#7  0x7f3536ded6ab in  () at /usr/lib/libglib-2.0.so.0
#8  0x7f3536ded89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#9  0x7f353c44772b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#10 0x7f353c3f123a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#11 0x7f353c2140f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#12 0x7f353f5772d5 in  () at /usr/lib/libQt5Qml.so.5
#13 0x7f353c218d78 in  () at /usr/lib/libQt5Core.so.5
#14 0x7f353b328454 in start_thread () at /usr/lib/libpthread.so.0
#15 0x7f353bb2e7df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f348d96c700 (LWP 709)):
#0  0x7ffe257c6b02 in clock_gettime ()
#1  0x7f353bb3b6b6 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7f353c2be1a1 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f353c4453a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7f353c447085 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f3536ded179 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#6  0x7f3536ded724 in  () at /usr/lib/libglib-2.0.so.0
#7  0x7f3536ded89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#8  0x7f353c44772b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#9  0x7f353c3f123a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#10 0x7f353c2140f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#11 0x7f3540116856 in  () at /usr/lib/libQt5Quick.so.5
#12 0x7f353c218d78 in  () at /usr/lib/libQt5Core.so.5
#13 0x7f353b328454 in start_thread () at /usr/lib/libpthread.so.0
#14 0x7f353bb2e7df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f3520933700 (LWP 708)):
#0  0x7f353b32e10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f3541ba6ac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f3541ba6b09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f353b328454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f353bb2e7df in clone () at /usr/lib/libc.so.6

Thread 4 

[dolphin] [Bug 372242] New: dolphin crahsed

[Jake Clausen]

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

Bug ID: 372242
   Summary: dolphin crahsed
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: jakeclau...@phonecoop.coop
  Target Milestone: ---

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-45-generic i686
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
inserted  memory stick and in Dolphin  I tried to see the files on the stick.
As soon as I did this Dolphin crashed

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb1aa6800 (LWP 1681))]

Thread 3 (Thread 0xaba89b40 (LWP 1686)):
#0  0xb7737c31 in __kernel_vsyscall ()
#1  0xb755dd0f in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0xb40f2b10 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb40e410c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb40e4244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb5683964 in QEventDispatcherGlib::processEvents (this=0xab100470,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0xb56287a3 in QEventLoop::processEvents (this=0xaba891d4, flags=...) at
kernel/qeventloop.cpp:128
#7  0xb5628bfa in QEventLoop::exec (this=0xaba891d4, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb544ef1d in QThread::exec (this=0x8ee2c68) at thread/qthread.cpp:503
#9  0xb544eff8 in QThread::run (this=0x8ee2c68) at thread/qthread.cpp:570
#10 0xb545443b in QThreadPrivate::start (arg=0x8ee2c68) at
thread/qthread_unix.cpp:331
#11 0xb428c2c5 in start_thread (arg=0xaba89b40) at pthread_create.c:333
#12 0xb7567eee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 2 (Thread 0xaca90b40 (LWP 1684)):
#0  0xb7737c31 in __kernel_vsyscall ()
#1  0xb4291a9c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xb757464d in __pthread_cond_wait (cond=0x8e55868, mutex=0x8e55850) at
forward.c:149
#3  0xafd2cbba in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#4  0xafd2c185 in ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so
#5  0xb428c2c5 in start_thread (arg=0xaca90b40) at pthread_create.c:333
#6  0xb7567eee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 1 (Thread 0xb1aa6800 (LWP 1681)):
[KCrash Handler]
#7  0xb5654859 in QMimeDataPrivate::retrieveTypedData (this=0x8fc58e0,
format=..., type=QVariant::ByteArray) at kernel/qmimedata.cpp:100
#8  0xb5655ee6 in QMimeData::data (this=0x8e9b600, mimeType=...) at
kernel/qmimedata.cpp:546
#9  0xb6fb688b in KIO::isClipboardDataCut (mimeData=0x8e9b600) at
../../../src/widgets/paste.cpp:350
#10 0xb6fd88d1 in KIO::PasteJobPrivate::slotStart (this=0x91490b0) at
../../../src/widgets/pastejob.cpp:55
#11 0xb6fd8c7b in KIO::PasteJob::qt_static_metacall (_o=0x913e2e8,
_c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x922e540) at ./moc_pastejob.cpp:95
#12 0xb5658270 in QMetaCallEvent::placeMetaCall (this=0x8febfc8,
object=0x913e2e8) at kernel/qobject.cpp:486
#13 0xb565c093 in QObject::event (this=0x913e2e8, e=0x8febfc8) at
kernel/qobject.cpp:1239
#14 0xb5fb415a in QApplicationPrivate::notify_helper (this=0x8baf4e0,
receiver=0x913e2e8, e=0x8febfc8) at kernel/qapplication.cpp:3716
#15 0xb5fb981c in QApplication::notify (this=0xbfda4afc, receiver=0x913e2e8,
e=0x8febfc8) at kernel/qapplication.cpp:3499
#16 0xb562b66f in QCoreApplication::notifyInternal (this=0xbfda4afc,
receiver=0x913e2e8, event=0x8febfc8) at kernel/qcoreapplication.cpp:965
#17 0xb562dd4f in QCoreApplication::sendEvent (event=0x8febfc8,
receiver=) at kernel/qcoreapplication.h:224
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x8bae6a8) at kernel/qcoreapplication.cpp:1593
#19 0xb562e237 in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1451
#20 0xb5683553 in postEventSourceDispatch (s=0x8baef40) at
kernel/qeventdispatcher_glib.cpp:271
#21 0xb40e3ed9 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#22 0xb40e4179 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#23 0xb40e4244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#24 0xb5683943 in QEventDispatcherGlib::processEvents (this=0x8be0c30,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#25 0xb17e3a81 in QPAEventDispatcherGlib::processEvents (this=0x8be0c30,
flags=...) at eventdispatchers/qeventdispatcher_glib.cpp:115
#26 0xb56287a3 in QEventLoop::processEvents (this=0xbfda4a28, flags=...) at
kernel/qeventloop.cpp:128
#27 0xb5628bfa in QEventLoop::exec (this=0xbfda4a28, flags=...) 

[kmail2] [Bug 372142] Kmail: Forward inline messages causes crash

[Laurent Montel]

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

--- Comment #4 from Laurent Montel  ---
I confirm crash

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

[digikam] [Bug 372027] Adjust grouping behavior [patch]

[Simon]

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

--- Comment #10 from Simon  ---
There are two bug reports (that I found) which are fixed by or related to this
patch. As I don't know how the control mechanisms of bugs.kde.org work, I will
just list them here:
https://bugs.kde.org/show_bug.cgi?id=294579
https://bugs.kde.org/show_bug.cgi?id=307332

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Leslie Zhai]

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

--- Comment #19 from Leslie Zhai  ---
Git commit 6177dcec4ca59f1781bbccc49670abd3126a3cae by Leslie Zhai.
Committed on 09/11/2016 at 06:55.
Pushed by lesliezhai into branch 'cdrskin'.

Prepare for migrating to libburnia

As Thomas Schmitt suggested in KDEBUG-367639 adapting to cdrskin/xorriso
because cdrkit/wodim and dvd+rw-tools/growisofs are both dead projects,
as Kevin Kofler described, only Linux distributions packages patch them for
fixing BUG...

So it is the time to migrate to cdrskin/xorriso, please give me more code
review and help, thanks a lot!

CCMAIL: scdbac...@gmx.net

M  +31   -0libk3b/core/k3bdefaultexternalprograms.cpp
M  +20   -0libk3b/core/k3bdefaultexternalprograms.h
M  +2-0libk3b/core/k3bglobals.cpp
M  +2-1libk3b/core/k3bglobals.h

http://commits.kde.org/k3b/6177dcec4ca59f1781bbccc49670abd3126a3cae

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

[k3b] [Bug 372094] Please restore wodim support

[Kevin Kofler]

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

--- Comment #12 from Kevin Kofler  ---
Looks OK to me.

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

[k3b] [Bug 372094] Please restore wodim support

[Leslie Zhai]

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

--- Comment #11 from Leslie Zhai  ---
Git commit abe673e2f1b9b016d3a9c3aaad42d808a80a0b4a by Leslie Zhai.
Committed on 09/11/2016 at 06:30.
Pushed by lesliezhai into branch 'cdrskin'.

Restore wodim support

Although wodim from cdrkit (CD only, DVD deprecated, unmaintained) was
unmaintained, Kevin Kofler suggested restoring it. Please review it, if
it looks good to you, I will merge to master.

CCMAIL: kevin.kof...@chello.at

M  +4-1libk3b/core/k3bdefaultexternalprograms.cpp
M  +1-1libk3b/jobs/k3bdvdcopyjob.cpp
M  +1-0libk3b/jobs/k3bmetawriter.cpp
M  +8-2libk3b/projects/datacd/k3bdatajob.cpp
M  +1-1libk3b/projects/k3bcdrecordwriter.cpp
M  +1-1src/k3bsystemproblemdialog.cpp
M  +2-1src/option/k3bexternalbinpermissionmodel.cpp

http://commits.kde.org/k3b/abe673e2f1b9b016d3a9c3aaad42d808a80a0b4a

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

[plasmashell] [Bug 372241] New: Taskbar crash after several click on the clipboard ("scissors") icon

[bugzilla_noreply]

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

Bug ID: 372241
   Summary: Taskbar crash after several click on the clipboard
("scissors") icon
   Product: plasmashell
   Version: 5.6.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: devia...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.6.5)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.0.9-gentoo-gnu20160422 x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:
- What I was doing when the application crashed:
The USB devices popup list was open. I clicked several times on the clipboard
icon in the taskbar to see the clipboard contents. The clipboard popup didn't
appear. Instead, the whole taskbar disappeared.

-- Backtrace:
Application: Plasma (plasmashell), 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 0x7f52728a9780 (LWP 3533))]

Thread 8 (Thread 0x7f525fe07700 (LWP 3560)):
#0  0x7f526d20014d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5271257ac2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f527125972f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f5261b3f029 in QXcbEventReader::run (this=0x1846590) at
qxcbconnection.cpp:1325
#4  0x7f526d8bb88c in QThreadPrivate::start (arg=0x1846590) at
thread/qthread_unix.cpp:341
#5  0x7f526ca09444 in start_thread (arg=0x7f525fe07700) at
pthread_create.c:334
#6  0x7f526d20912d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f525e39f700 (LWP 3561)):
#0  g_main_context_prepare (context=context@entry=0x7f525990,
priority=priority@entry=0x7f525e39ecd0) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3437
#1  0x7f526901fe18 in g_main_context_iterate
(context=context@entry=0x7f525990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3820
#2  0x7f526901fffc in g_main_context_iteration (context=0x7f525990,
may_block=1) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3901
#3  0x7f526daa95dc in QEventDispatcherGlib::processEvents
(this=0x7f5258c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#4  0x7f526da5bc4a in QEventLoop::exec (this=this@entry=0x7f525e39ee10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f526d8b7154 in QThread::exec (this=this@entry=0x7f5272a27240
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#6  0x7f52729ba235 in QDBusConnectionManager::run (this=0x7f5272a27240
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#7  0x7f526d8bb88c in QThreadPrivate::start (arg=0x7f5272a27240 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:341
#8  0x7f526ca09444 in start_thread (arg=0x7f525e39f700) at
pthread_create.c:334
#9  0x7f526d20912d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f525cb60700 (LWP 3590)):
#0  0x7f526d8b437b in QMutex::lock (this=this@entry=0x1952e08) at
thread/qmutex.cpp:217
#1  0x7f526daa936b in QMutexLocker::QMutexLocker (m=0x1952e08,
this=) at ../../src/corelib/thread/qmutex.h:128
#2  QThreadData::canWaitLocked (this=0x1952de0) at
../../src/corelib/thread/qthread_p.h:246
#3  postEventSourcePrepare (s=0x7f52540012d0,
timeout=timeout@entry=0x7f525cb5fc54) at kernel/qeventdispatcher_glib.cpp:253
#4  0x7f526901f42d in g_main_context_prepare
(context=context@entry=0x7f5254000990, priority=priority@entry=0x7f525cb5fce0)
at /usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3442
#5  0x7f526901fe18 in g_main_context_iterate
(context=context@entry=0x7f5254000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3820
#6  0x7f526901fffc in g_main_context_iteration (context=0x7f5254000990,
may_block=1) at
/usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3901
#7  0x7f526daa95dc in QEventDispatcherGlib::processEvents
(this=0x7f52540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#8  0x7f526da5bc4a in QEventLoop::exec (this=this@entry=0x7f525cb5fe20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#9  0x7f526d8b7154 in QThread::exec (this=this@entry=0x192db80) at
thread/qthread.cpp:500
#10 0x7f52700f6a65 in QQmlThreadPrivate::run (this=0x192db80) at
qml/ftw/qqmlthread.cpp:141
#11 

[dolphin] [Bug 363794] Ddolphin ignores Maxsize in breeze index.theme icon file.

[Alexander]

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

Alexander  changed:

   What|Removed |Added

 CC||ingle...@gmail.com

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

[k3b] [Bug 372094] Please restore wodim support

[Kevin Kofler]

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

--- Comment #10 from Kevin Kofler  ---
Also, please keep in mind that cdrtools/cdrkit is not only cdrecord/wodim, but
also mkisofs/genisoimage. You will also want to detect and use xorrisofs from
libburnia, which is likely a better mkisofs replacement than genisoimage.

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

[krita] [Bug 372240] New: the cursor has a black bar directly under

[bugzilla_noreply]

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

Bug ID: 372240
   Summary: the cursor has a black bar directly under
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: marc.ali...@outlook.com
  Target Milestone: ---

as soon as i open up Krita for the first time there is a black bar directly
under the cursor and is a but larger then the cursor itself. this is quite
distracting when painting. As i attempted to screen shot this bug it
disappears. Either its a canvas issue or its a cursor issue.

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

[kde-cli-tools] [Bug 372239] New: Kcmshell5 segfaults when changing notification configurations and actions.

[Horacio Sanson]

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

Bug ID: 372239
   Summary: Kcmshell5 segfaults when changing notification
configurations and actions.
   Product: kde-cli-tools
   Version: 5.8.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aleix...@kde.org
  Reporter: hsan...@gmail.com
  Target Milestone: ---

Created attachment 102138
  --> https://bugs.kde.org/attachment.cgi?id=102138=edit
kcrash report output.

Steps to reproduce:

  - Right click in the Notifications icon in the systray.
  - Select "Configure Event Notifications and Actions..."
  - In the notifications dialog press Ok button, even without changing
anything.
  - A kcrash alert appears indicating that kcmshell5 segfaulted.
  - Happens everytime.

Notes:

  - The kcrash general tab says that I cannot report this issue (report bug
button is grayed out) because kcmshell5 does not provide a bug reporting
address.

  - When accessing the notifications settings from the kde setting application
the crash does not occur because there is no Ok button there, only Apply
button.

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

[krita] [Bug 372238] New: "Drawing Angle" Rotation Mode in Colour Smudge Scratchpad Crashes Krita

[Aniruddha Hardikar]

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

Bug ID: 372238
   Summary: "Drawing Angle" Rotation Mode in Colour Smudge
Scratchpad Crashes Krita
   Product: krita
   Version: 3.1 Beta
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: aniruddha@gmail.com
  Target Milestone: ---

While testing any Colour Smudge brush in the scratchpad, Selecting the "Drawing
Angle" rotation mode crashes Krita. This happens even if brush rotation is
turned off.

Steps to reproduce:

1. Open a document, select any colour smudge brush and open brush settings
2. turn on Drawing Angle in the rotation types
3. draw in the scratchpad.

krita-3.0.92-x86_64: Tested on Linux Mint 18 KDE 64Bit, Please note I'm using
an older GPU (Geforce 9800 GT) which may be causing this, in which case I
apologize for the inconvenience.

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

[k3b] [Bug 372094] Please restore wodim support

[Kevin Kofler]

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

--- Comment #9 from Kevin Kofler  ---
> but I want to ship still-maintaining && BUGFREE product to end-users.

I actually agree with you there. I really think we need to switch to libburnia.

You should just clearly communicate this to packagers when announcing the new
release, so we do not end up with things working poorly because wodim is
getting silently picked up due to outdated dependencies in the package.

You should also make sure that cdrskin is preferred over wodim even if wodim is
installed/symlinked as "cdrecord" (because updating K3b, even if we add a
Requires: cdrskin, is not magically going to make installed wodim packages go
away, we cannot really use Obsoletes or Conflicts to force it removed).

> Yes, I am editing libk3b/core/k3bdefaultexternalprograms.cpp for adding
> cdrskin to K3b::AbstractCdrtoolsProgram( QLatin1String( "cdrskin" ),
> QLatin1String("cdrecord") )

But that is only the easy part. You need to look at all the places where a
decision what burning program to prefer is made (or checks for "if burning
program == cdrecord, apply workaround foo"), make it prefer cdrskin for things
it is actually better at (remember that growisofs is unmaintained too, though
not as long as wodim, so cdrskin is the better choice if it works), disable
cdrecord-specific workarounds (start by looking at those workarounds already
disabled for wodim in the code you removed, but keep in mind that cdrskin is
not a fork of cdrecord as wodim is, so probably does not need ANY of the
cdrecord workarounds), etc.

I have seen a bunch of cdrecord workarounds while browsing K3b code in the
past, but unfortunately I do not remember the exact locations in the code. For
example, there is something that says that cdrecord fails at doing some things
for audio CDs in DAO mode, so cdrdao (another unmaintained tool (no news since
2009), that in addition also uses libraries from cdrtools/cdrkit, so also uses
the unmaintained wodim code) is used for those instead. (Searching for "cdrdao"
will probably find that particular one.) You really want to go through all the
burning code and check whether what it is doing still makes sense if cdrecord
is actually cdrskin.

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

[k3b] [Bug 372094] Please restore wodim support

[Leslie Zhai]

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

--- Comment #8 from Leslie Zhai  ---
(In reply to Kevin Kofler from comment #7)
> And we will default to libburnia if you add tested support for it. But I
> object to removing wodim support before a replacement is ready. We cannot
> use cdrecord in Fedora.

Yes, I am editing libk3b/core/k3bdefaultexternalprograms.cpp for adding cdrskin
to K3b::AbstractCdrtoolsProgram( QLatin1String( "cdrskin" ),
QLatin1String("cdrecord") )

I might be too anxious ;-) sorry for my expression! but I want to ship
still-maintaining && BUGFREE product to end-users.
for example, transcode was unmaintained too, please see KDEBUG-360170
http://www.leetcode.cn/2016/08/k3b.html#bug I migrated it, *NOT* be merged
again, so deprecated transcode resolutely, end-users do *NOT* need unuseful
software even it still be packaged again and again...

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

[k3b] [Bug 372094] Please restore wodim support

[Kevin Kofler]

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

--- Comment #7 from Kevin Kofler  ---
And we will default to libburnia if you add tested support for it. But I object
to removing wodim support before a replacement is ready. We cannot use cdrecord
in Fedora.

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

[k3b] [Bug 372094] Please restore wodim support

[Kevin Kofler]

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

--- Comment #6 from Kevin Kofler  ---
Removing working detection code just because you did not understand what it
really does is not helpful. Especially when your "fixes" actually make the code
misbehave on our distribution. And answering a request to restore the code with
a "NOPE!" in ALL CAPS is also not helpful.

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Leslie Zhai]

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

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

I will add libburnia backend support W.I.P, and thanks again for your great
help!  https://bugs.kde.org/show_bug.cgi?id=367639#c14

Regards,
Leslie Zhai - a KDE developer https://git.reviewboard.kde.org/users/lesliezhai/

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Leslie Zhai]

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

Leslie Zhai  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||scdbac...@gmx.net,
   ||xiangzha...@gmail.com

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

[plasmashell] [Bug 372237] New: Superkey + L Causes Crash

[bugzilla_noreply]

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

Bug ID: 372237
   Summary: Superkey + L Causes Crash
   Product: plasmashell
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: xunilh...@8chan.co
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-2-default x86_64
Distribution: "openSUSE Tumbleweed"

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

Pressed the super key + "L".

- Unusual behavior I noticed:

This caused my dual monitor setup to lose their correct resolutions. By
continuing to cycle through the different resolutions by pressing the super key
+ "L" it continued changing the resolutions on both monitors, with either one
going completely black at times. Only one or the other monitor would have the
correct resolution at a time, not both. Eventually I went into the Plasma
Display and Monitor settings and noticed that the alignment was way off for
both monitors. I realigned the displays and then had to kill 2 plasmashell
processes to get my wallpaper showing again.

Superkey + L is a strange default, because I pressed it by accident and then
this happened. It also is a confusing default because Windows users are used to
this keyboard shortcut to lock the desktop. Maybe make Superkey + L actually
lock the desktop rather than this behaviour?

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

Thread 16 (Thread 0x7fac427fb700 (LWP 13063)):
#0  0x7fad4f2a368d in poll () from /lib64/libc.so.6
#1  0x7fad4a342876 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fad4a34298c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fad4fbc279b in QEventDispatcherGlib::processEvents
(this=0x7fac18001e00, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fad4fb6c1ea in QEventLoop::exec (this=this@entry=0x7fac427face0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7fad4f99a8b3 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fad52ccba75 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7fad4f99f558 in QThreadPrivate::start (arg=0x4997a80) at
thread/qthread_unix.cpp:344
#8  0x7fad4eaa5454 in start_thread () from /lib64/libpthread.so.0
#9  0x7fad4f2ac39f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7fac67fff700 (LWP 2142)):
#0  0x7fad4eaab10f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fad4f9a040b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x501b930) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x16e2d60,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fac8ea12e60 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7fac8ea17018 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7fac8ea11fdd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7fac8ea17072 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7fac8ea11fdd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7fac8ea17072 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7fac8ea11fdd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7fac8ea17072 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7fac8ea11fdd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7fac8ea17072 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7fac8ea11fdd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7fac8ea17072 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7fac8ea11fdd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7fac8ea14ea9 in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7fad4f99f558 in QThreadPrivate::start (arg=0x7fac74002d90) at
thread/qthread_unix.cpp:344
#18 0x7fad4eaa5454 in start_thread () from /lib64/libpthread.so.0
#19 0x7fad4f2ac39f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7fac7c856700 (LWP 2141)):
#0  0x7fad4eaab10f in pthread_cond_wait@@GLIBC_2.3.2 

[k3b] [Bug 372094] Please restore wodim support

[Leslie Zhai]

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

Leslie Zhai  changed:

   What|Removed |Added

 CC||xiangzha...@gmail.com

--- Comment #5 from Leslie Zhai  ---
Hi Kevin,

I am a newbie of K3b maintainer http://www.leetcode.cn/2016/08/k3b.html so
welcome to report bug to me ;-)

But Thomas Schmitt , the author of libburnia, have already reviewed my patch
https://bugs.kde.org/show_bug.cgi?id=367639#c14 *including*:

> Isn't your patch
>  "Use cdrecord for burning blueray instead of wodim."
>  http://commits.kde.org/k3b/fcb0ff1f36c319fd1e2b4bd92c2c08fdc690212c
> mislabelled ?
> Shouldn't it rather be
> "Use cdrecord for burning blueray and DVD instead of growisofs"
>?

And I am double sure I fixed it!

> DVD support in wodim is crap and BluRay support is nonexistent, but that's 
> why the code you removed, which prefers growisofs, is there!
> The only reason we need wodim at all is that growisofs does not support CDs

NOPE!
[R.E.Q]I will add libburnia backup backend W.I.P. *BUT* I will never ever use
wodim! I *hate* meaningless forked then unmaintained!

Regards,
Leslie Zhai - a KDE developer https://git.reviewboard.kde.org/users/lesliezhai/

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

[Akonadi] [Bug 372236] New: Akonadi will not start

[Stuart]

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

Bug ID: 372236
   Summary: Akonadi will not start
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: KAlarm resource
  Assignee: djar...@kde.org
  Reporter: sbe...@thevegfactor.co.uk
CC: kdepim-b...@kde.org
  Target Milestone: ---

Akonadi Server Self-Test Report
===

Test 1:  SUCCESS


Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server
configuration and was found on your system.

File content of '/home/stuart/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-stuart.3lRYnN/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS


Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the
recommended setup for a secure system.

Test 3:  SUCCESS


MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server
'/usr/sbin/mysqld-akonadi'.
Make sure you have the MySQL server installed, set the correct path and ensure
you have the necessary read and execution rights on the server executable. The
server executable is typically called 'mysqld'; its location varies depending
on the distribution.

Test 4:  SUCCESS


MySQL server is executable.
Details: MySQL server found: 161109  2:41:53 [Warning] Using unique option
prefix key_buffer instead of key_buffer_size is deprecated and will be removed
in a future release. Please use the full name instead.
/usr/sbin/mysqld  Ver 5.5.53-0ubuntu0.14.04.1 for debian-linux-gnu on i686
((Ubuntu))


Test 5:  SUCCESS


No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The
log can be found in '/home/stuart/.local/share/akonadi/db_data/mysql.err'.

Test 6:  SUCCESS


MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is
readable at /etc/akonadi/mysql-global.conf.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp 
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#
sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of
data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for
debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM
information_schema.tables WHERE table_schema not in ("mysql",
"information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show
global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other
internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables
(default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin,
8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but
more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The 

[Discover] [Bug 372131] "Failed to activate service 'org.freedesktop.PackageKit': timed out"

[Aleix Pol]

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

--- Comment #3 from Aleix Pol  ---
No worries, feel free to report if you find any other issues!

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Christoph Feck]

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

--- Comment #16 from Christoph Feck  ---
https://techbase.kde.org/Development/Tutorials/Localization/i18n_Build_Systems
does not list any technical differences, so it might be because of historical
reasons. Switching the complete infrastructure was never considered.

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

[plasma4] [Bug 372219] Panel keeps crashing in VirtualBox

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---


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

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

[plasmashell] [Bug 363371] Plasma crashes randomly when on the task panel miniatures app windows shows up.

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||staysynchron...@gmail.com

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

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

[frameworks-kio] [Bug 372207] kwrite file open dialog, filenames overwrite icons (probably all apps)

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |general
 CC||kdelibs-b...@kde.org
Version|16.08   |unspecified
   Assignee|kwrite-bugs-n...@kde.org|fa...@kde.org
Product|kate|frameworks-kio

--- Comment #1 from Christoph Feck  ---
It looks like Qt thinks these file types have no associated icon, and does not
reserve any space for them. Then, something else thinks they should get a
default icon anyway.

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

[kate] [Bug 372208] kwrite File -> New directory fails to follow current, defaults to $HOME

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

  Component|general |kwrite

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

[kwin] [Bug 372218] Task switcher "Compact" ignores font anti-aliasing settings

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
QtQuick allows native freetype text rendering (which is slower than the default
OpenGL distance field rendering), but it has to be enabled using a text
property, see http://doc.qt.io/qt-5/qml-qtquick-text.html#renderType-prop

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

[kio] [Bug 372224] Unable to 'save as' document opened in dolphin back to original network location

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #1 from Christoph Feck  ---
LibreOffice does not support KIO, so "Save As..." to a remote folder does not
work in LibreOffice.

KDE applications know about this limitation, and temporarily copy a remote file
to /tmp, then invoke LibreOffice. After exiting LibreOffice, this file is
checked for modifications, and if modified (e.g. because you made changes and
saved them), is copied back to the remote folder.

If you want LibreOffice to support remote folders in its "Save As..." dialog,
please file a feature request at the LibreOffice bug tracker.

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

[keditbookmarks] [Bug 372206] The split keditbookmarks repo doesn't contain a COPYING/LICENSE file

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||fa...@kde.org

--- Comment #1 from Christoph Feck  ---
David, do you agree to relicense
"keditbookmarks/src/kbookmarkmodel/tests/kbookmarkmodeltest.cpp" to GPL instead
of LGPL? Then only one license file needs to be added.

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

[Discover] [Bug 372131] "Failed to activate service 'org.freedesktop.PackageKit': timed out"

[Paul WOISARD]

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

Paul WOISARD  changed:

   What|Removed |Added

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

--- Comment #2 from Paul WOISARD  ---
The problem was due to an error i had do in "pacman.conf" file.

I changed "SigLevel" to "Never".
Now i am changing the value to "Optional TrustedOnly"

And Discover is work correctly.

Sorry, for the disturb.

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

[plasmashell] [Bug 372229] nvidia

[Sasha Unspecified]

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

Sasha Unspecified  changed:

   What|Removed |Added

 CC||sasha2...@gmail.com

--- Comment #1 from Sasha Unspecified  ---
I confirm this (or at least, automatic bug reporter considered my bug to be a
duplicate of this).

It appeared after software upgrade (I don't know what exactly triggered it:
either KDE packages upgrade, or nvidia package upgrade, or some other
packages). Now I just can't start plasma. It's persistent.

Workaround is to purge nvidia-304, nvidia-opencl-icd-304, nvidia-settings
packages (note: xserver-xorg-video-nouveau shouldn't be installed too, because
it displays screen full of different colors and hands the system; hovewer, such
nouveau behavior is from the very beginning; while plasma crash with nvidia is
regression).

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

[plasmashell] [Bug 372229] nvidia

[Sasha Unspecified]

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

--- Comment #2 from Sasha Unspecified  ---
Tell me if I should provide some info.

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Nikolay Brookstein]

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

--- Comment #15 from Nikolay Brookstein  ---
(In reply to Christoph Feck from comment #14)
> Our translation infrastructure is based on GNU 'gettext'; we do not use the
> Qt translation system.

Thank you for the clarification. Is gettext technically better than the Qt
translation system? What is the reason of using it?

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Christoph Feck]

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

--- Comment #14 from Christoph Feck  ---
Our translation infrastructure is based on GNU 'gettext'; we do not use the Qt
translation system.

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

[kalarm] [Bug 372223] Problem in QIconPrivate::~QIconPrivate

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
This issue could be caused by "libqtxdg". I have no idea what component is
responsible for loading this library, neither Qt nor KDE sources reference it.

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

[valgrind] [Bug 371916] execution tree xtree concept

[Josef Weidendorfer]

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

Josef Weidendorfer  changed:

   What|Removed |Added

 CC||josef.weidendor...@gmx.de

--- Comment #15 from Josef Weidendorfer  ---
Hi Philippe, nice patch!

I think it is good to move functionalty from tools to the core, if it
can make other tools better or easier to write. Attaching data to call
trees built from stack traces should fit here.
However, I did not check the large rewrite of massif.

General comments (I may be missing something here):

* is this bound to memory allocation, or is memory allocation just
  an example use case of the API? It would be nice if tools could
  attach arbitrary data to xtrees. Perhaps separate the memory allocation
  stuff into different files (e.g. xtree_memalloc.h).

* behavior of some functions in the XTree API depend on command line
  options. Wouldn't it be better for a tool using this API to be in
  full control here, ie. the tool parses command line
  options and pass them as flags?  About the changes in the malloc
  wrappers, I think it would be better if the tool can register handlers,
  and these handlers then call e.g. VG_(XTMemory_Full_alloc).

About the XTree API, why do you need these add/sub variants?
Why not just have a function to get a pointer to the value to be updated?
Any reduction operation may be useful, such as min/max.

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

[konsole] [Bug 369632] %u doesnt show current user anymore

[Kurt Hindenburg]

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

--- Comment #1 from Kurt Hindenburg  ---
I can't reproduce this - you are on the latest version and Linux so it should
work.  If you can provide an image and if anything unusual about your system. 
The code uses /proc/ and getpwuid_r to find various info.  Also try running
konsole from an xterm or another terminal to see if any errors print.

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

[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps

[Peter Wu]

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

Peter Wu  changed:

   What|Removed |Added

 CC||pe...@lekensteyn.nl
 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1

--- Comment #12 from Peter Wu  ---
The same grab issue can be observed with QEMU.

Steps to reproduce:
1. Start qemu-system-x86_64 (no options needed, this will open the GTK GUI).
2. Click in the window, this will let QEMU grab the focus and change the title
to
   "QEMU - Press Ctrl+Alt+G to release grab"
3. Press "Meta"

Actual results:
The Plasma kickoff menu opens.

Expected results:
The Plasma kickoff menu should not open.

I do not think it is useful to treat Meta specially to trigger an action given
that all other shortcuts are disabled. Principle of least surprise is violated
here.

For Ctrl-Alt-F1, Ctrl-Alt-Delete, etc., remoting software acknowledge that
these complex shortcuts are interpreted by the host and QEMU/gvncviewer for
example adds a menu option to send this keystroke. But the "Meta" key is not
such a special key.

See also bug 371560 which requests the option to disable the "Meta" shortcut
for Kickoff. (From a user's perspective, I also ran into the grab issue (this
bug) and the linked Kickoff issue. Also, in all cases where Kickoff opened, I
pressed Meta with the intent to press another key to trigger a shortcut, but
then stopped. This got so annoying that I finally started looking for bug
reports.)

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

[kile] [Bug 328712] adding build tool destroys menu layout

[Christoph Feck]

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

--- Comment #14 from Christoph Feck  ---
This is probably a duplicate of bug 314580, which again is probably a duplicate
of bug 64754.

To verify, please try Kile KF5 version with KF5 5.24 or newer.

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

[kile] [Bug 328712] adding build tool destroys menu layout

[Nico Kruber]

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

--- Comment #13 from Nico Kruber  ---
I just tried without the patch (project home:NicoK:branches:KDE:Extra) and the
problem is gone - the shortcut works, every time.

With the patch, when I go into the shortcut configuration, I do not see the
custom shortcut and the defaults are shown. If I don't change anything there,
the custom shortcut remains in the kileui.rc file when I quit. If I change
something, it is removed from kileui.rc.

My guess would be that the parser stops somewhere when the patch is applied and
does not get to the point where the shortcuts are defined. But unfortunately,
no warning is printed.

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

[plasmashell] [Bug 371560] Add a way to disable Kickoff launch with Meta key

[Peter Wu]

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

Peter Wu  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||pe...@lekensteyn.nl

--- Comment #2 from Peter Wu  ---
(In reply to Tony from comment #1)
> There is already one, remove ALT+F1 shortcut from the application launcher.

The problem is that both "Meta" and "Alt+F1" open the Kickoff menu. The
expected behavior is that only "Alt+F1" should open the Kickoff menu. How would
removing the "Alt+F1" shortcut help in this case?

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

[plasmashell] [Bug 367685] Toggle application launcher on meta key

[Peter Wu]

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

--- Comment #10 from Peter Wu  ---
For future tracking: atmarx reported bug 371821 which covers this bug and the
issue with the menu still opening even if an application grabbed it. The latter
issue is tracked by bug 371877.

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

[kscreenlocker] [Bug 372197] wrong XAUTHORITY setting leads to crashing kscreenlocker_greeter

[Stefan Brüns]

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

--- Comment #7 from Stefan Brüns  ---
The processes which are not children of ksmserver are all programs which were
restored from a previous session.

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

[kile] [Bug 328712] adding build tool destroys menu layout

[Nico Kruber]

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

--- Comment #12 from Nico Kruber  ---
Created attachment 102137
  --> https://bugs.kde.org/attachment.cgi?id=102137=edit
/home/nico/.kde4/share/config/kilerc

Attached my kilerc file as re-created by the kile from KDE:Extra after deleting
the file. Unfortunately, the same symptoms are still there:
after setting the new shortcut in the settings, Ctrl+B works (primary or
alternative shortcut, even Ctrl+M), but after quitting kile and restarting it
again, it does not anymore, although it is still mentioned in the kileui.rc
file.

Console output also shows no errors. No idea what else it could be...I'll try
to create an OBS branch without this single patch to make sure this is what is
causing my problem.

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

[frameworks-baloo] [Bug 372235] New: Baloo crash during IPL

[Vince Radice]

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

Bug ID: 372235
   Summary: Baloo crash during IPL
   Product: frameworks-baloo
   Version: 5.26.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: pinak.ah...@gmail.com
  Reporter: vhrad...@cfl.rr.com
  Target Milestone: ---

Application: baloo_file_extractor (5.26.0)

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

-- Information about the crash:
- Baloo crashed during IPL.  This seems to happen after Fedora crashes due to a
power problem.  I am running Ferora 24 64 bit

The crash can be reproduced sometimes.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), 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 0x7fd1713c0900 (LWP 1704))]

Thread 3 (Thread 0x7fd15156d700 (LWP 1870)):
#0  0x7fd16e3503ed in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd16cf2fa06 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7fd14c03af10, timeout=, context=0x7fd14c0009b0)
at gmain.c:4135
#2  0x7fd16cf2fa06 in g_main_context_iterate
(context=context@entry=0x7fd14c0009b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7fd16cf2fb1c in g_main_context_iteration (context=0x7fd14c0009b0,
may_block=1) at gmain.c:3901
#4  0x7fd16f15624b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7fd16f1055ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7fd16ef64343 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7fd1714dc559 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#8  0x7fd16ef6899a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7fd16d8a55ca in start_thread (arg=0x7fd15156d700) at
pthread_create.c:333
#10 0x7fd16e35bf6d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fd1599ab700 (LWP 1794)):
#0  0x7fd16e3503ed in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fd168df2f80 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7fd1599aabc0) at /usr/include/bits/poll2.h:46
#2  0x7fd168df2f80 in _xcb_conn_wait (c=c@entry=0x5568d0f6d720,
cond=cond@entry=0x5568d0f6d760, vector=vector@entry=0x0, count=count@entry=0x0)
at xcb_conn.c:459
#3  0x7fd168df4b79 in xcb_wait_for_event (c=0x5568d0f6d720) at xcb_in.c:693
#4  0x7fd15dab8da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#5  0x7fd16ef6899a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#6  0x7fd16d8a55ca in start_thread (arg=0x7fd1599ab700) at
pthread_create.c:333
#7  0x7fd16e35bf6d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fd1713c0900 (LWP 1704)):
[KCrash Handler]
#6  0x7fd153c12a18 in Exiv2::ValueType::toLong(long) const ()
at /lib64/libexiv2.so.14
#7  0x7fd1581f223b in
KFileMetaData::Exiv2Extractor::add(KFileMetaData::ExtractionResult*,
Exiv2::ExifData const&, KFileMetaData::Property::Property, char const*,
QVariant::Type) () at
/usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
#8  0x7fd1581f2a06 in
KFileMetaData::Exiv2Extractor::extract(KFileMetaData::ExtractionResult*) () at
/usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
#9  0x5568d018de0b in Baloo::App::index(Baloo::Transaction*, QString
const&, unsigned long long) ()
#10 0x5568d018e2de in Baloo::App::processNextFile() ()
#11 0x7fd16f13ad16 in QSingleShotTimer::timerEvent(QTimerEvent*) () at
/lib64/libQt5Core.so.5
#12 0x7fd16f12fb8b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#13 0x7fd16f999c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#14 0x7fd16f99f0ef in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#15 0x7fd16f1067aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#16 0x7fd16f1557ab in QTimerInfoList::activateTimers() () at
/lib64/libQt5Core.so.5
#17 0x7fd16f155d39 in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#18 0x7fd16cf2f6ba in g_main_context_dispatch (context=0x7fd154001710) at
gmain.c:3154
#19 0x7fd16cf2f6ba in g_main_context_dispatch
(context=context@entry=0x7fd154001710) at gmain.c:3769
#20 0x7fd16cf2fa70 in g_main_context_iterate
(context=context@entry=0x7fd154001710, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3840
#21 0x7fd16cf2fb1c in g_main_context_iteration (context=0x7fd154001710,
may_block=1) at 

[khelpcenter] [Bug 372139] Debian 8.6.0 - System will not shut down , can only exit by switching off machine

[Luigi Toscano]

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

--- Comment #4 from Luigi Toscano  ---
(In reply to John from comment #3)
> Created attachment 102136 [details]
> attachment-8777-0.html
> 
> My knowledge of Linux is very limited , I have installed Debian 8.6.0 from
> a bought disc , & log in with a password as usual . It is the shut down
> function as used from the menu that does not work . At the moment I have
> taken the hard drive with Debian on it out of the machine & have gone back
> to using Linux Mint .

A reason more to ask on Debian-specific channels. I marked the bug as INVALID
only because this specific bug tracking system is not the proper place to
report it.

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

[khelpcenter] [Bug 372139] Debian 8.6.0 - System will not shut down , can only exit by switching off machine

[John]

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

--- Comment #3 from John  ---
My knowledge of Linux is very limited , I have installed Debian 8.6.0 from
a bought disc , & log in with a password as usual . It is the shut down
function as used from the menu that does not work . At the moment I have
taken the hard drive with Debian on it out of the machine & have gone back
to using Linux Mint .

On Sun, Nov 6, 2016 at 11:17 PM, Luigi Toscano 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=372139
>
> Luigi Toscano  changed:
>
>What|Removed |Added
> 
> 
>  Status|UNCONFIRMED |RESOLVED
>  CC||luigi.tosc...@tiscali.it
>  Resolution|--- |INVALID
>
> --- Comment #2 from Luigi Toscano  ---
> I understand the pain, but this is not the proper channel for this issue.
> This
> bug was opened against khelpcenter, an browser for help guides, which is
> for
> sure not the right component. But this is not even about software by the
> KDE
> community, or at least not directly. If the desktop environment used is KDE
> Plasma, this may be relevant here, but I would first check on the proper
> support channel for Debian, providing more details.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[digikam] [Bug 372232] Strange window switching between main digikam window and importing window

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/dc2d60332be61eb192c3c86
   ||1bffa3d0f793da942
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Maik Qualmann  ---
Git commit dc2d60332be61eb192c3c861bffa3d0f793da942 by Maik Qualmann.
Committed on 08/11/2016 at 21:57.
Pushed by mqualmann into branch 'master'.

fix import window behaviour
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +4-4app/main/digikamapp.cpp
M  +4-4utilities/importui/main/importui.cpp
M  +2-4utilities/importui/main/importui.h

http://commits.kde.org/digikam/dc2d60332be61eb192c3c861bffa3d0f793da942

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

[kmymoney4] [Bug 372234] CSV Import account selector malfunction on KF5

[allan]

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

--- Comment #1 from allan  ---
KMyMoney Version 4.100.0-e36687e

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

[kmymoney4] [Bug 372234] New: CSV Import account selector malfunction on KF5

[allan]

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

Bug ID: 372234
   Summary: CSV Import account selector malfunction on KF5
   Product: kmymoney4
   Version: git (master)
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: csvimporter
  Assignee: kmymoney-de...@kde.org
  Reporter: agande...@gmail.com
  Target Milestone: ---

When I am importing a CSV file and get to the account selector dialog,
multiple accounts show, as expected, but not all of them.  So, I have to
scroll to display the required name.  Unfortunately, any click in the
window, other than on one of the names, causes the scroll list drop-down
to disappear.

It is necessary to enter a few matching characters into the edit box to
get the required account to show in the drop-down.

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

[kscreenlocker] [Bug 372197] wrong XAUTHORITY setting leads to crashing kscreenlocker_greeter

[Martin Gräßlin]

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

--- Comment #6 from Martin Gräßlin  ---
In the end all processes should be children of ksmserver. It's weird if you
have processes which are not.

But anyway: distro topic

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

[KScreen] [Bug 372228] libkscreen-qt5: qt_message_fatal(): kscreen_backend_launcher

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Version|unspecified |5.8.2
Product|kde |KScreen
   Assignee|unassigned-b...@kde.org |se...@kde.org
  Component|general |libkscreen

--- Comment #1 from Christoph Feck  ---
Somehow your system has both Wayland and X11 activated. Applications detect the
X11 mode, but fail to open the display. This seems to be a common theme of your
recent bug reports.

Are you using a released version of a distribution so that developers can try
to reproduce the issues?

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

[digikam] [Bug 372027] Adjust grouping behavior [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/digi
   ||kam/5f6aa8656cf333e8949b106
   ||60407e8c8a0c0cc4f
   Version Fixed In||5.4.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #9 from Maik Qualmann  ---
Git commit 5f6aa8656cf333e8949b10660407e8c8a0c0cc4f by Maik Qualmann.
Committed on 08/11/2016 at 21:11.
Pushed by mqualmann into branch 'master'.

apply patch #102005 from Simon Frei to adjust grouping behavior
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-1app/items/digikamimageview.cpp
M  +29   -18   app/items/imagecategorizedview.cpp
M  +6-3app/items/imagecategorizedview.h
M  +0-27   app/items/imageviewutilities.cpp
M  +12   -3app/views/digikamview.cpp
M  +96   -49   app/views/tableview/tableview.cpp
M  +10   -4app/views/tableview/tableview.h
M  +0-24   app/views/tableview/tableview_model.cpp
M  +0-2app/views/tableview/tableview_model.h
M  +13   -0libs/database/item/imageinfolist.cpp
M  +2-1libs/database/item/imageinfolist.h
M  +1-0libs/models/imagefiltermodel.h
M  +0-1libs/tags/tagslineeditoverlay.cpp

http://commits.kde.org/digikam/5f6aa8656cf333e8949b10660407e8c8a0c0cc4f

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

[systemsettings] [Bug 372137] Failed after click on sensor panel option in input devices tab under wayland

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DUPLICATE
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Christoph Feck  ---


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

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

[Touchpad-KCM] [Bug 363109] systemsettings crash when selecting touchpad when run in a wayland session

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

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

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

[digikam] [Bug 372027] Adjust grouping behavior [patch]

[bugzilla_noreply]

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

--- Comment #8 from caulier.gil...@gmail.com ---
No problem Maik, lets go...

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

[digikam] [Bug 372027] Adjust grouping behavior [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

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

I would commit the patch. I sometimes see an incorrect counter of items to
delete in the context menu in the Tables view. We can fix that later.

Maik

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

[kdenlive] [Bug 366798] Timeline cursor and all timeline features not working but clip monitor still functional

[Samuel]

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

Samuel  changed:

   What|Removed |Added

 CC||sbc_hates_s...@yahoo.com.au

--- Comment #3 from Samuel  ---
I have Kdenlive Version 16.08.2 using KDE Frameworks 5.27.0 and Qt 5.7.0. 

My timeline cursor cannot be moved by the cursor.  I can get it to change
position by clicking between the "Clip Monitor" and "Project Monitor".  This
does not always work though.

I find this a very frustrating and time consuming process for video editing.

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

[frameworks-knewstuff] [Bug 369646] The 'free' menu in Dolphin's status bar incorrectly lists KDE Partition Manager as not installed

[João Vidal da Silva]

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

--- Comment #5 from João Vidal da Silva  ---
(In reply to Gregor Mi from comment #2)

> /opt/kf5/share/applications/org.kde.PartitionManager.desktop
> (...)
> Maybe the cause is that partitionmanager is now the KF5 version which is
> located in the /opt/kf5/... directory?
> (...)
> The "Name" in the desktop file has changed (see
> https://lxr.kde.org/source/frameworks/knewstuff/data/kmoretools-desktopfiles/
> org.kde.PartitionManager.desktop ("Name=KDE Partition Manager") vs. the
> installed one ("Name=KDE Partition Manager/KF5")) but this should not be the
> cause.

I'm running Manjaro, an Arch based distro, and just as with Andrius Štikonas
both desktop files (org.kde.PartitionManager.desktop from partitionmanager and
from knewstuff) are locate at /usr/share/... and both have Name=KDE Partition
Manager.

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

[kate] [Bug 348765] Perl syntax highlighting is wrong when using scalar references (backslash quote)

[EGD]

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

EGD  changed:

   What|Removed |Added

 CC||egd.f...@gmail.com

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

[krita] [Bug 372233] New: tablet stylus and cursor position not correct

[bugzilla_noreply]

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

Bug ID: 372233
   Summary: tablet stylus and cursor position not correct
   Product: krita
   Version: 3.0.1.1
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: cvgl...@googlemail.com
  Target Milestone: ---

The left half of the canvas ist not accessible with the pen. The right half ist
good to use but when entering the left half, the cursor jumps to the far right.
when using the mouse you can use the whole canvas.

The krita-GUI itself and the Windows GUI is not affected only the painting
area.

Windows 10 x64
ThinkPad X201 Tablet
Krita 64bit 3.0.1.1

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

[kmail2] [Bug 368378] Regression in kMail 5.3.x: Drag and drop of attachments from a received mail into the composer does not work any more

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.4.0
  Latest Commit||http://commits.kde.org/mess
   ||agelib/42a5c00667e6440fcf38
   ||79a1dfdc9f31088f78d2

--- Comment #7 from Laurent Montel  ---
Git commit 42a5c00667e6440fcf3879a1dfdc9f31088f78d2 by Montel Laurent.
Committed on 08/11/2016 at 20:12.
Pushed by mlaurent into branch 'master'.

Fix Bug 366652 - Drag and drop attachments in Kmail has stopped working

Fix Bug 368378 - Regression in kMail 5.3.x: Drag and drop of attachments from a
received mail into the composer does not work any more

FIXED-IN: 5.4.0
Related: bug 366652

M  +2-44   messageviewer/src/viewer/viewer_p.cpp
M  +0-3messageviewer/src/viewer/viewer_p.h
M  +45   -32   messageviewer/src/viewer/webengine/mailwebengineview.cpp
M  +3-4messageviewer/src/viewer/webengine/mailwebengineview.h
M  +1-24   webengineviewer/src/webengineview.cpp
M  +1-5webengineviewer/src/webengineview.h

http://commits.kde.org/messagelib/42a5c00667e6440fcf3879a1dfdc9f31088f78d2

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

[kmail2] [Bug 366652] Drag and drop attachments in Kmail has stopped working

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/mess
   ||agelib/42a5c00667e6440fcf38
   ||79a1dfdc9f31088f78d2
 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.4.0
 Resolution|--- |FIXED

--- Comment #3 from Laurent Montel  ---
Git commit 42a5c00667e6440fcf3879a1dfdc9f31088f78d2 by Montel Laurent.
Committed on 08/11/2016 at 20:12.
Pushed by mlaurent into branch 'master'.

Fix Bug 366652 - Drag and drop attachments in Kmail has stopped working

Fix Bug 368378 - Regression in kMail 5.3.x: Drag and drop of attachments from a
received mail into the composer does not work any more

FIXED-IN: 5.4.0
Related: bug 368378

M  +2-44   messageviewer/src/viewer/viewer_p.cpp
M  +0-3messageviewer/src/viewer/viewer_p.h
M  +45   -32   messageviewer/src/viewer/webengine/mailwebengineview.cpp
M  +3-4messageviewer/src/viewer/webengine/mailwebengineview.h
M  +1-24   webengineviewer/src/webengineview.cpp
M  +1-5webengineviewer/src/webengineview.h

http://commits.kde.org/messagelib/42a5c00667e6440fcf3879a1dfdc9f31088f78d2

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

[digikam] [Bug 372232] New: Strange window switching between main digikam window and importing window

[bugzilla_noreply]

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

Bug ID: 372232
   Summary: Strange window switching between main digikam window
and importing window
   Product: digikam
   Version: 5.2.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: piotergmo...@hotmail.com
  Target Milestone: ---

When I open import window there is not obvious way to switch to main digikam
window. On the taskbar I can see only one window - when I click on it the
import window appears. When trying from keyboard the second (main) window
appears on the list, but I cannot switch to him even when I choose them. The
import windows appears always. There is only one way to get back (besides
closing the import window of course): in import window minimize it, than main
window appears, but getting back to import is weird. I have to minimize the
digikam window, and choose it again, then whoopla the import window appears. Is
it by design or bug?
digikam4 worked fine in this aspect.

Only the import window (as far as I know) behaves so ugly.
P.

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

[konsole] [Bug 158235] Add support for xterm CSI 3 J sequence

[Kurt Hindenburg]

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

--- Comment #3 from Kurt Hindenburg  ---
print '^[[3J'  where the ^[ are one character - hit Ctrl+v and then ESC to
generate it.


It seems to work as xterm which both print a ' which is strange.

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Nikolay Brookstein]

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

--- Comment #13 from Nikolay Brookstein  ---
No problem, without bug reports bugs will never be fixed ^_^

As far as I have understood, KDE/Plasma/KF are all Qt based,
so why you are using 'i18n("Blabla")' instead of 'tr("Blabla")'

Btw, you are the main maintainer of Ark right now?
If yes, some offtopic question from my side, is it possible to make a progress
indication in Ark, or the current architecture is not sutable for the such kind
of functionality?

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Elvis Angelaccio]

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

--- Comment #12 from Elvis Angelaccio  ---
(In reply to Nikolay Brookstein from comment #10)
> I have just created a bug report at the unarchiver bug tracker:
> https://bitbucket.org/WAHa_06x36/theunarchiver/issues/919/unarchiver-crash-
> while-
> trying-to-open-or

Thanks for reporting it upstream!

> 
> Elvis, "Archive too big" is probably some how confusing.
> Possibly "Archive can not be extracted due to insufficient free memory"?

Yeah, this is just a temporary patch so that I won't forget it :p

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Nikolay Brookstein]

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

Nikolay Brookstein  changed:

   What|Removed |Added

URL||https://bitbucket.org/WAHa_
   ||06x36/theunarchiver/issues/
   ||919/unarchiver-crash-while-
   ||trying-to-open-or

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Nikolay Brookstein]

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

--- Comment #11 from Nikolay Brookstein  ---
oops, the same URl without line break:
https://bitbucket.org/WAHa_06x36/theunarchiver/issues/919/unarchiver-crash-while-trying-to-open-or

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Nikolay Brookstein]

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

--- Comment #10 from Nikolay Brookstein  ---
I have just created a bug report at the unarchiver bug tracker:
https://bitbucket.org/WAHa_06x36/theunarchiver/issues/919/unarchiver-crash-while-
trying-to-open-or

Elvis, "Archive too big" is probably some how confusing.
Possibly "Archive can not be extracted due to insufficient free memory"?

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

[krusader] [Bug 372231] right click service menu's not working

[bugzilla_noreply]

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

dutchk...@txoriaskea.org changed:

   What|Removed |Added

 CC||dutchk...@txoriaskea.org

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

[krusader] [Bug 372231] New: right click service menu's not working

[bugzilla_noreply]

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

Bug ID: 372231
   Summary: right click service menu's not working
   Product: krusader
   Version: 2.5.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: dutchk...@txoriaskea.org
  Target Milestone: ---

In the previous version of Krusader items from
/usr/share/kde4/services/ServiceMenus would show up in the appropriate right
click menu's in Krusader, like an extra category "Actions", etc. In plasma 5
the new location for this is /usr/share/kservices5/ServiceMenus but Krusader
doesn't show any of those since the port to plasma 5 was completed with the
2.5.0 version. The items do show up in Dolphin. This removes a lot of
functionality from Krusader.

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Elvis Angelaccio]

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

--- Comment #9 from Elvis Angelaccio  ---
Created attachment 102135
  --> https://bugs.kde.org/attachment.cgi?id=102135=edit
Catch bad_alloc patch

With this patch Ark doesn't crash, at least.

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

[kde] [Bug 372228] libkscreen-qt5: qt_message_fatal(): kscreen_backend_launcher

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 371247] Ability to find out the location of a or the current wallpaper

[Gregor Mi]

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

--- Comment #3 from Gregor Mi  ---
- A "Show in folder" action would be very helpful.

- Currently, when hovering the mouse over custom-added wallpapers a "Delete"
button appears in the upper right corner.This could be the place where the
"Show in folder" action could be added. (Currently there is no context menu)

- Currently, the tooltip shows the title of the image. Even if it contained
also the path it would be more complicated to use it to find the image on disk.

- The standard context menu for image files would be helpful to directly copy
the image to clipboard or to invoke the "Properties" dialog which also contains
the (copyable) location of the containing folder.

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Elvis Angelaccio]

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

--- Comment #8 from Elvis Angelaccio  ---
(In reply to Nikolay Brookstein from comment #7)
> What is the difference between unrar and unar approaches?
> It is really strange, to get over 3 GB memory allocation fo a ~240MB file.
> It looks like coner case or a totally inefficient implementation from unar
> side.
> Probably Ark just need a better backend error detection, and a bug is in
> unar. Or I am wrong here?
> (That are just my thoughts, I am not an expert in rar/unar/unrar)
> 
> P.S. I will look in a source file tomorrow.

Yes, ideally a bug should also be filed against unar.

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

[digikam] [Bug 372230] New: Context menu not complete on right click on searches

[TG]

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

Bug ID: 372230
   Summary: Context menu not complete on right click on searches
   Product: digikam
   Version: 5.3.0
  Platform: MacPorts Packages
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Searches
  Assignee: digikam-de...@kde.org
  Reporter: thierry.gare...@orange.fr
  Target Milestone: ---

Created attachment 102134
  --> https://bugs.kde.org/attachment.cgi?id=102134=edit
right click on current search

When Right clicking on Searches in the left search tabs, the context menu only
shows "new" or "modify" no possibilities to delete the search.
there are also several "current search"

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

[digikam] [Bug 372158] Allow changing metadata of multiple images at once

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Version|5.2.0   |5.3.0

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

[digikam] [Bug 366624] Digikam defaults to fullscreen with no menu and status bar

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
   Version Fixed In|5.3.0   |5.4.0

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

[plasmashell] [Bug 372229] New: nvidia

[krirz79]

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

Bug ID: 372229
   Summary: nvidia
   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: krir...@gmail.com
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-45-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
Install complete.
Black screen

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7f67cfb4b700 (LWP 1564)):
#0  0x7f687ff1169d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f687c10473c in ?? () from /usr/lib/libGL.so.1
#2  0x7f6878adfbf7 in ?? () from /usr/lib/tls/libnvidia-tls.so.304.132
#3  0x7f687ccee740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f687ccaae84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f687ccab340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f687ccab4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f68808427eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f68807e9b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f6880606834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f6883834ed6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7f688060b7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f687c105754 in ?? () from /usr/lib/libGL.so.1
#13 0x7f687f6f870a in start_thread (arg=0x7f67cfb4b700) at
pthread_create.c:333
#14 0x7f687ff2182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f68569cf700 (LWP 1563)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6885253bd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f6885253c19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f687c105754 in ?? () from /usr/lib/libGL.so.1
#4  0x7f687f6f870a in start_thread (arg=0x7f68569cf700) at
pthread_create.c:333
#5  0x7f687ff2182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f6857fff700 (LWP 1562)):
#0  0x7ffdbdbdbcaf in clock_gettime ()
#1  0x7f687ff2fc86 in __GI___clock_gettime (clock_id=1, tp=0x7f6857ffe950)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f68806bbb86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f6880840279 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f68808407e5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6880841bce in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f687ccaa92d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f687ccab2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f687ccab4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f68808427eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f68807e9b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f6880606834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f6882eae3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f688060b7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f687c105754 in ?? () from /usr/lib/libGL.so.1
#15 0x7f687f6f870a in start_thread (arg=0x7f6857fff700) at
pthread_create.c:333
#16 0x7f687ff2182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f685e1dd700 (LWP 1561)):
#0  0x7ffdbdbdbcaf in clock_gettime ()
#1  0x7f687ff2fc86 in __GI___clock_gettime (clock_id=1, tp=0x7f685e1dc950)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f68806bbb86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f6880840279 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f68808407e5 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6880841bce in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f687ccaa92d in g_main_context_prepare () from

[frameworks-kded] [Bug 372227] kf5-kded: QObject::disconnect(): kded5

[RJ]

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

RJ  changed:

   What|Removed |Added

   See Also||https://bugzilla.redhat.com
   ||/show_bug.cgi?id=1393064

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

[kde] [Bug 372228] libkscreen-qt5: qt_message_fatal(): kscreen_backend_launcher

[RJ]

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

RJ  changed:

   What|Removed |Added

 CC||ogldel...@mail.ru

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

[digikam] [Bug 366624] Digikam defaults to fullscreen with no menu and status bar

[bugzilla_noreply]

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

--- Comment #13 from mr.mahon...@gmail.com ---
Seems it's working fine now in 5.3.0

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

[kde] [Bug 372228] libkscreen-qt5: qt_message_fatal(): kscreen_backend_launcher

[RJ]

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

RJ  changed:

   What|Removed |Added

   See Also||https://bugzilla.redhat.com
   ||/show_bug.cgi?id=1393062

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

[digikam] [Bug 366624] Digikam defaults to fullscreen with no menu and status bar

[bugzilla_noreply]

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

mr.mahon...@gmail.com changed:

   What|Removed |Added

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

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

[kde] [Bug 372228] New: libkscreen-qt5: qt_message_fatal(): kscreen_backend_launcher

[RJ]

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

Bug ID: 372228
   Summary: libkscreen-qt5: qt_message_fatal():
kscreen_backend_launcher
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: ogldel...@mail.ru
  Target Milestone: ---

warning: core file may not match specified executable file.
[New LWP 7403]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/kf5/kscreen_backend_launcher'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
58  }

Thread 1 (Thread 0x7f360f618d40 (LWP 7403)):
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
set = {__val = {0, 139870153232265, 166, 140720936176880, 104, 8,
139869897520864, 1, 0, 139870150836220, 8, 139870150829125, 47,
140720936176848, 140720936176944, 4543238025}}
pid = 
tid = 
#1  0x7f360dd9c52a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x55afe2dac4a0, sa_sigaction
= 0x55afe2dac4a0}, sa_mask = {__val = {17028194897886074112, 140720936177536,
140720936177168, 3, 94213913533104, 139870153292768, 139870150733945,
139870045181080, 17028194897886074112, 140720936177536, 140720936177168, 3,
140720936177536, 94213913533104, 139870150734280, 94213913533104}}, sa_flags =
1453217024, sa_restorer = 0x55afe2daad80}
sigs = {__val = {32, 0 }}
#2  0x7f360ea64af1 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1680
No locals.
#3  QMessageLogger::fatal (this=this@entry=0x7ffc2569cf80,
msg=msg@entry=0x7f35ff8ea9e8 "QXcbConnection: Could not connect to display %s")
at global/qlogging.cpp:793
message = 
ap = 
#4  0x7f35ff85bb5e in QXcbConnection::QXcbConnection (this=0x55afe2daad80,
nativeInterface=0x55afe2d95ab0, canGrabServer=,
defaultVisualId=, displayName=) at
qxcbconnection.cpp:592
dpy = 
extensions = {0x70, 0x7f360e125ae0 , 0x18, 0x55afe2d95e58,
0x7ffc2569d6b8, 0x7f360e125ae0 , 0x370, 0x0}
glIntegrationNames = { =
{ = {}, {p = {static shared_null
= {ref = {atomic = {_q_value = { = {static
_S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin = 0, end =
0, array = {0x0}}, d = 0x38}, d = 0x38}}, }
glIntegrationName = {static null = {}, d =
0x7ffc2569cfa0}
#5  0x7f35ff85ed1e in QXcbIntegration::QXcbIntegration (this=, parameters=..., argc=@0x7ffc2569d54c: 1, argv=0x7ffc2569d6b8) at
qxcbintegration.cpp:186
displayName = 
noGrabArg = 
doGrabArg = 
canNotGrabEnv = false
canNotGrabEnv = false
canNotGrabEnv = false
#6  0x7f360f7716ed in QXcbIntegrationPlugin::create (this=,
system=..., parameters=..., argc=@0x7ffc2569d54c: 1, argv=0x7ffc2569d6b8) at
qxcbmain.cpp:56
No locals.
#7  0x7f360ef438fd in QPlatformIntegrationFactory::create (platform=...,
paramList=..., argc=@0x7ffc2569d54c: 1, argv=,
argv@entry=0x7ffc2569d6b8, platformPluginPath=...) at
kernel/qplatformintegrationfactory.cpp:71
No locals.
#8  0x7f360ef510c1 in init_platform (argv=,
argc=@0x7ffc2569d54c: 1, platformThemeName=..., platformPluginPath=...,
pluginArgument=...) at kernel/qguiapplication.cpp:1094
arguments = { = { = {}, {p = {static shared_null = , d = 0x55afe2d79f50},
d = 0x55afe2d79f50}}, }
name = {static null = {}, d = 0x55afe2d90aa0}
themeNames = { = { = {}, {p = {static shared_null = , d = 0x55afe2d92600},
d = 0x55afe2d92600}}, }
#9  QGuiApplicationPrivate::createPlatformIntegration (this=0x55afe2d910e0) at
kernel/qguiapplication.cpp:1263
platformPluginPath = {static null = {}, d =
0x7f360ecd2b60 }
platformName = {d = 0x55afe2d927c0}
platformNameEnv = {d = 0x7f360ecd2b60 }
platformThemeName = {static null = {}, d =
0x7f360ecd2b60 }
icon = {static null = {}, d = 0x7f360ecd2b60
}
j = 
#10 0x7f360ef51f3d in QGuiApplicationPrivate::createEventDispatcher
(this=) at kernel/qguiapplication.cpp:1280
No locals.
#11 0x7f360ec1f4f9 in QCoreApplicationPrivate::init
(this=this@entry=0x55afe2d910e0) at kernel/qcoreapplication.cpp:787
No locals.
#12 0x7f360ef5319e in QGuiApplicationPrivate::init (this=0x55afe2d910e0) at
kernel/qguiapplication.cpp:1303
loadTestability = 
pluginList = { = {},
{p = {static shared_null = , d = 0x12}, d = 0x12}}
session_id = {static null = {}, d = 0x68}
s = {static null = {}, d = 0xa}
j = 
envPlugins = {d = 0x0}
#13 0x7f360ef53fa4 in 

[digikam] [Bug 366624] Digikam defaults to fullscreen with no menu and status bar

[bugzilla_noreply]

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

mr.mahon...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||5.3.0
Version|5.1.0   |5.3.0

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

[frameworks-kded] [Bug 372227] New: kf5-kded: QObject::disconnect(): kded5

[RJ]

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

Bug ID: 372227
   Summary: kf5-kded: QObject::disconnect(): kded5
   Product: frameworks-kded
   Version: 5.27.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: ogldel...@mail.ru
CC: kdelibs-b...@kde.org
  Target Milestone: ---

[New LWP 7174]
[New LWP 7289]
[New LWP 7358]
[New LWP 7150]
[New LWP 7273]
[New LWP 7357]
[New LWP 7269]
[New LWP 7272]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/kded5'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7ff16363b87d in QObject::disconnect (sender=0x7ff11c040890,
signal=signal@entry=0x0, receiver=receiver@entry=0x7ff13c0122b0,
method=method@entry=0x0) at kernel/qobject.cpp:2956
2956const QMetaObject *smeta = sender->metaObject();
[Current thread is 1 (Thread 0x7ff14204b700 (LWP 7174))]

Thread 1 (Thread 0x7ff14204b700 (LWP 7174)):
#0  0x7ff16363b87d in QObject::disconnect (sender=0x7ff11c040890,
signal=signal@entry=0x0, receiver=receiver@entry=0x7ff13c0122b0,
method=method@entry=0x0) at kernel/qobject.cpp:2956
signal_arg = 0x0
signal_name = {d = 0x7ff1636cab60 }
signal_found = false
method_name = {d = 0x7ff1636cab60 }
method_arg = 0x0
membcode = 
method_found = false
res = false
smeta = 0x7ff147cac8a0

signalName = {d = 0x7ff1636cab60 }
signalTypes = {a = 10, s = 0, ptr = 0x7ff14204aac0, {array =
"+\312w\257\000\000\000\000\230\345'\332!V\000\000\200a\005<\361\177\000\000t/~b\361\177\000\000\260\223\004<\361\177\000\000
\000\000<\361\177\000\000 \000\000<\361\177\000\000
\004\000\000\000\000\000\000C\000\000\000\000\000\000\000\a\000\000\000\000\000\000\000\320\005\006<\361\177\000\000\017\017~b\361\177\000\000\340\001\000\000\000\000\000\000\b\b\000\000\000\000\000\000\240\253\004B\361\177\000\000\237\253\004B\361\177\000\000
\000\000\000\000\000\000\000\030\000\000\000\000\000\000\000\300\253\004B\361\177\000\000\277\253\004B\361\177\000",
q_for_alignment_1 = 2943863339, q_for_alignment_2 = 1.4544617418514035e-314}}
methodName = {d = 0x7ff1636cab60 }
methodTypes = {a = 10, s = 0, ptr = 0x7ff14204ab70, {array =
"\004\000\000\000\000\000\000\000AT\373\275\016\200\377\377\000\000\000\000\000\000\000\000\002\000\000\000\060",
'\000' , "[\000\000\000n", '\000' ,
"w\000\000\000|\000\000\000\260\"\001<\361\177\000\000
\000\000<\361\177\000\000\b\b\000\000\000\000\000\000+#t\257\000\000\000\000\260\"\001<\361\177\000\000
\000\000<\361\177\000\000\030\000\000\000\000\000\000\000`U\001<\361\177\000\000\260\223\004<\361\177\000\000P\330\005<\361\177\000",
q_for_alignment_1 = 4, q_for_alignment_2 = 1.9762625833649862e-323}}
#1  0x7ff1652bffd0 in QObject::disconnect (member=0x0,
receiver=0x7ff13c0122b0, this=) at
../../src/corelib/kernel/qobject.h:359
No locals.
#2  QDBusConnectionPrivate::closeConnection (this=this@entry=0x7ff13c0122b0) at
qdbusintegrator.cpp:1133
locker = { = {}, self =
0x7ff13c0122b0, action = CloseConnectionAction}
oldMode = 
allObjects = {q_hash = {{d = 0x7ff13c0493b0, e = 0x7ff13c0493b0}}}
sit = 
oit = {i = {i = 0x7ff13c011060}}
#3  0x7ff1652ac8c2 in QDBusConnectionManager::run (this=0x7ff165322060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:206
d = 0x7ff13c0122b0
it = {i = 0x7ff13c012c00}
locker = {val = 140674761629809}
#4  0x7ff163471a1a in QThreadPrivate::start (arg=0x7ff165322060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:344
__clframe = {__cancel_routine = 0x7ff163470b40
, __cancel_arg = 0x7ff165322060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>, __do_it = 1,
__cancel_type = }
thr = 0x7ff165322060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>
data = 
#5  0x7ff1625466ca in start_thread (arg=0x7ff14204b700) at
pthread_create.c:333
__res = 
pd = 0x7ff14204b700
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140674171451136,
8559708019580081564, 0, 140723477064655, 140674171451840, 140674171451136,
-8563395547042277988, -8563324488656611940}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 
pagesize_m1 = 
sp = 
freesize = 
__PRETTY_FUNCTION__ = "start_thread"
#6  0x7ff162864f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105
No locals.

Thread 2 (Thread 0x7ff10f8da700 (LWP 7289)):
#0  0x7ff16285900d in poll () at 

[frameworks-kded] [Bug 372227] kf5-kded: QObject::disconnect(): kded5

[RJ]

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

RJ  changed:

   What|Removed |Added

   Severity|normal  |crash
 CC||ogldel...@mail.ru

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Nikolay Brookstein]

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

--- Comment #7 from Nikolay Brookstein  ---
What is the difference between unrar and unar approaches?
It is really strange, to get over 3 GB memory allocation fo a ~240MB file.
It looks like coner case or a totally inefficient implementation from unar
side.
Probably Ark just need a better backend error detection, and a bug is in unar.
Or I am wrong here?
(That are just my thoughts, I am not an expert in rar/unar/unrar)

P.S. I will look in a source file tomorrow.

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

[kate] [Bug 372226] Some sessions stay in full screen on cinnamon

[MikMak]

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

--- Comment #1 from MikMak  ---
It is impossible de quit full screen mode, the button "exit full screen"
doesn't work, neiher the menu item, neither the shortcut

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

[KScreen] [Bug 372225] black screen when booting with external monitors

[Theresa]

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

Theresa  changed:

   What|Removed |Added

 CC||rockprinz...@gmail.com

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

[kate] [Bug 372226] Some sessions stay in full screen on cinnamon

[MikMak]

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

MikMak  changed:

   What|Removed |Added

Summary|Some session stay in full   |Some sessions stay in full
   |screen on cinnamon  |screen on cinnamon

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