[yakuake] [Bug 440327] Yakuake immediately segfaults after having ticked a transparency option

[Lukáš Karas]

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

Lukáš Karas  changed:

   What|Removed |Added

 CC||lukas.ka...@centrum.cz

--- Comment #4 from Lukáš Karas  ---
Fix for the crash: https://invent.kde.org/utilities/yakuake/-/merge_requests/98

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

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

[Lukáš Karas]

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

--- Comment #24 from Lukáš Karas  ---
Here is my proposed fix in Gwenview:
https://invent.kde.org/graphics/gwenview/-/merge_requests/125

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

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

[Lukáš Karas]

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

Lukáš Karas  changed:

   What|Removed |Added

 CC||lukas.ka...@centrum.cz

--- Comment #23 from Lukáš Karas  ---
Created attachment 144593
  --> https://bugs.kde.org/attachment.cgi?id=144593=edit
sample image that is causing the crash

Here is jpg file that is causing the the crash. It is clear that libexiv is
throwing exception when it tries to parse date. This exception is not catched
in gwenview. 

$ exiv2 -P X print  test.jpg 
Xmp.tiff.SoftwareXmpText13  digiKam-7.1.0
Xmp.tiff.DateTimeXmpText19  2014-09-13T14:36:40
Xmp.tiff.ImageWidth  XmpText 4  3110
Xmp.tiff.ImageLength XmpText 4  1553
Xmp.xmp.CreatorTool  XmpText13  digiKam-3.5.0
Xmp.xmp.CreateDate   XmpText19  2014-09-13T14:36:40
Xmp.xmp.MetadataDate XmpText19  2014-09-13T14:36:40
Xmp.xmp.ModifyDate   XmpText19  2014-09-13T14:36:40
Xmp.xmp.Rating   XmpText 1  2
Xmp.exif.DateTimeOriginalXmpText19  Uncaught exception:
basic_string::at: __n (which is 19) >= this->size() (which is 19)

$ echo $?
1

So, fix is obvious. But where it should be fixed? In libexiv or gwenview? 

Ubuntu 21.10
exiv2 0.27.3
gwenview 21.08.1

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

[Akonadi] [Bug 427262] "akonadictl fsck" hung, apparmor blocks access (?)

[Lukáš Karas]

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

--- Comment #1 from Lukáš Karas  ---
Hi. 

This problem still persist on Kubuntu 21.10 with Akonadi 21.08.1. 

Access is blocked by AppArmor definitely. When I edit
/etc/apparmor.d/usr.bin.akonadiserver and replace line:

  #include 

by:

  #include 

akonadictl fsck starts working...

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

[telepathy] [Bug 387930] Plasma crashed when processing signla from telepathy

[Lukáš Karas]

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

Lukáš Karas  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Lukáš Karas  ---
As I wrote, I don't find a way how to reproduce it. But yes, it is not
happening anymore, so we may close it as fixed.

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

[Akonadi] [Bug 427262] New: "akonadictl fsck" hung, apparmor blocks access (?)

[Lukáš Karas]

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

Bug ID: 427262
   Summary: "akonadictl fsck" hung, apparmor blocks access (?)
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: lukas.ka...@centrum.cz
  Target Milestone: ---

Hi. 

I am running akonadi 20.08.1 (akonadi server build from source code) on Kubuntu
20.10. When I want to run "akonadictl fsck" this tool hung. When I run
"dbus-monitor --session" meanwhile, I see these errors:

error time=1601657704.646568 sender=org.freedesktop.DBus -> destination=:1.920
error_name=org.freedesktop.DBus.Error.NameHasNoOwner reply_serial=5
   string "Could not get owner of name 'org.freedesktop.Akonadi.Janitor': no
such name"
method call time=1601657704.647468 sender=:1.920 ->
destination=org.freedesktop.DBus serial=6 path=/org/freedesktop/DBus;
interface=org.freedesktop.DBus; member=AddMatch
   string
"type='signal',sender='org.freedesktop.Akonadi.Janitor',path='/Janitor',interface='org.freedesktop.Akonadi.Janitor',member='information'"
method call time=1601657704.648362 sender=:1.920 ->
destination=org.freedesktop.DBus serial=7 path=/org/freedesktop/DBus;
interface=org.freedesktop.DBus; member=AddMatch
   string
"type='signal',sender='org.freedesktop.DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.freedesktop.Akonadi.Janitor'"
method call time=1601657704.649335 sender=:1.920 ->
destination=org.freedesktop.DBus serial=8 path=/org/freedesktop/DBus;
interface=org.freedesktop.DBus; member=GetNameOwner
   string "org.freedesktop.Akonadi.Janitor"
error time=1601657704.649368 sender=org.freedesktop.DBus -> destination=:1.920
error_name=org.freedesktop.DBus.Error.NameHasNoOwner reply_serial=8
   string "Could not get owner of name 'org.freedesktop.Akonadi.Janitor': no
such name"
method call time=1601657704.650208 sender=:1.920 ->
destination=org.freedesktop.DBus serial=9 path=/org/freedesktop/DBus;
interface=org.freedesktop.DBus; member=AddMatch
   string
"type='signal',sender='org.freedesktop.Akonadi.Janitor',path='/Janitor',interface='org.freedesktop.Akonadi.Janitor',member='done'"
method call time=1601657704.652083 sender=:1.920 ->
destination=org.freedesktop.Akonadi.Janitor serial=10 path=/Janitor;
interface=org.freedesktop.Akonadi.Janitor; member=check
error time=1601657704.652102 sender=org.freedesktop.DBus -> destination=:1.920
error_name=org.freedesktop.DBus.Error.ServiceUnknown reply_serial=10
   string "The name org.freedesktop.Akonadi.Janitor was not provided by any
.service files"

When I run akonadi-server from different location (during debugging), fsck
process correctly. So, it is possible that Apparmor rules are involved.

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

[Akonadi] [Bug 420318] New: ItemRetrievalRequest heap-use-after-free

[Lukáš Karas]

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

Bug ID: 420318
   Summary: ItemRetrievalRequest heap-use-after-free
   Product: Akonadi
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: lukas.ka...@centrum.cz
  Target Milestone: ---

Akonadi crash sometimes on my machine. To get better idea where the bug is, I
build akonadi server with address sanitizer ( -DCMAKE_BUILD_TYPE=Debug
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_CXX_FLAGS=-fsanitize=address ). It shows me
heap-use-after-free: 

==772029==ERROR: AddressSanitizer: heap-use-after-free on address
0x604000272a90 at pc 0x55899a50df07 bp 0x7fd9cd9ef1c0 sp 0x7fd9cd9ef1b0
READ of size 8 at 0x604000272a90 thread T4 (ItemRetrievalMa)
#0 0x55899a50df06 in QListData::begin() const
/usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:116
#1 0x55899a5b1087 in QList::begin() const
/usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:325
#2 0x55899a8aec12 in QDebug QtPrivate::printSequentialContainer >(QDebug, char const*, QList const&)
/usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:219
#3 0x55899a8aaebb in QDebug operator<< (QDebug, QList
const&) /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:238
#4 0x55899a8b99e2 in Akonadi::Server::ItemRetrievalJob::start()
/home/karry/data/cecko/KDE/akonadi/src/server/storage/itemretrievaljob.cpp:47
#5 0x55899a8a69fe in
Akonadi::Server::ItemRetrievalManager::processRequest()
/home/karry/data/cecko/KDE/akonadi/src/server/storage/itemretrievalmanager.cpp:164
#6 0x55899a8b779c in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void
(Akonadi::Server::ItemRetrievalManager::*)()>::call(void
(Akonadi::Server::ItemRetrievalManager::*)(),
Akonadi::Server::ItemRetrievalManager*, void**)
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152
#7 0x55899a8b5c84 in void QtPrivate::FunctionPointer::call,
void>(void (Akonadi::Server::ItemRetrievalManager::*)(),
Akonadi::Server::ItemRetrievalManager*, void**)
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185
#8 0x55899a8b385d in QtPrivate::QSlotObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:414
#9 0x7fd9d76e0d59 in QObject::event(QEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2b2d59)
#10 0x7fd9d76b4916 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x286916)
#11 0x7fd9d76b75b7 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2895b7)
#12 0x7fd9d770cf66  (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2def66)
#13 0x7fd9d6068fbc in g_main_context_dispatch
(/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51fbc)
#14 0x7fd9d606923f  (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5223f)
#15 0x7fd9d60692e2 in g_main_context_iteration
(/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x522e2)
#16 0x7fd9d770c564 in
QEventDispatcherGlib::processEvents(QFlags)
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2de564)
#17 0x7fd9d76b34da in
QEventLoop::exec(QFlags)
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x2854da)
#18 0x7fd9d74eb784 in QThread::exec()
(/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xbd784)
#19 0x7fd9d74ec9d1  (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xbe9d1)
#20 0x7fd9d7013608 in start_thread
/build/glibc-aevPTw/glibc-2.31/nptl/pthread_create.c:477
#21 0x7fd9d7162102 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122102)

0x604000272a90 is located 0 bytes inside of 40-byte region
[0x604000272a90,0x604000272ab8)
freed by thread T12 (0x611c1ec0-) here:
#0 0x7fd9d8078025 in operator delete(void*, unsigned long)
(/usr/lib/x86_64-linux-gnu/libasan.so.5+0x111025)
#1 0x55899a8a22ee in
std::default_delete::operator()(Akonadi::Server::ItemRetrievalRequest*)
const (/usr/bin/akonadiserver+0x4692ee)
#2 0x55899a8a0ea2 in std::unique_ptr >::~unique_ptr()
/usr/include/c++/9/bits/unique_ptr.h:292
#3 0x55899a8a09b5 in void
std::_Destroy >
>(std::unique_ptr >*)
/usr/include/c++/9/bits/stl_construct.h:98
#4 0x55899a89e842 in void
std::_Destroy_aux::__destroy
>*>(std::unique_ptr >*,
std::unique_ptr >*)
/usr/include/c++/9/bits/stl_construct.h:108
#5 0x55899a89c583 in void
std::_Destroy
>*>(std::unique_ptr >*,
std::unique_ptr >*)
/usr/include/c++/9/bits/stl_construct.h:137
#6 0x55899a8991cc in void
std::_Destroy >*,
std::unique_ptr >
>(std::unique_ptr >*,
std::unique_ptr >*,
std::allocator > >&)
/usr/include/c++/9/bits/stl_construct.h:206
#7 0x55899a8966e3 in
std::vector >,
std::allocator > > >::~vector()
/usr/include/c++/9/bits/stl_vector.h:677
#8 0x55899a890ca8 in Akonadi::Server::ItemRetriever::exec()

[Heaptrack] [Bug 412098] New: Extend existing report (from embedded device) by stacktrace info on different machine?

[Lukáš Karas]

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

Bug ID: 412098
   Summary: Extend existing report (from embedded device) by
stacktrace info on different machine?
   Product: Heaptrack
   Version: 1.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: lukas.ka...@centrum.cz
  Target Milestone: ---

Hi. 

It is possible to extend existing heaptrack report by stacktrace information on
different machine?

I want to collect heap usage report on embedded device. On this device hasn't
enough space for installing debug symbols for all libraries that are used by
the process. Because of that, generated report contains many "" placeholders. In our (yocto based) SDK, we are able to prepare
sysroot with all libraries and its debug symbols. We are using it for coredump
analysis. So I believe that it should be possible even for heaptrack...

If yes, can you provide me so hint, or link to documentation?

If there is not such option (yet), can I ask you for this feature? Or at least
describe me the building blocks, I can try to implement this :-)

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

[digikam] [Bug 403649] Filesystem changes are not visible in album view [patch]

[Lukáš Karas]

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

--- Comment #13 from Lukáš Karas  ---
Thank you. Please consider to add some "isFileNested" variant anyway. Around
collection is a lot of duplicate code that can be moved to utility methods...

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

[digikam] [Bug 403649] Filesystem changes are not visible in album view

[Lukáš Karas]

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

--- Comment #9 from Lukáš Karas  ---
Created attachment 117946
  --> https://bugs.kde.org/attachment.cgi?id=117946=edit
patch that solves albumRootPath method issue with database root ending with
slash

I can offer this patch, that solves problem with albumRootPath and deduplicate
code little bit. I don't found better place where to put new method,
CollectionManager don't sounds like a good place for it :-(

More over, it don't solves original issue - re-scan is started properly, but
view is not updated. It seems that more places in the code don't work with
album root that is ending with slash...

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

[digikam] [Bug 403649] Filesystem changes are not visible in album view

[Lukáš Karas]

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

Lukáš Karas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #6 from Lukáš Karas  ---
I found it. Problem comes from the moment when I replaced my notebook and
manually updated drive UUID and path in "AlbumRoots" table. And I keep trailing
slash in the path: "/home/karry/data/fotky/". Everything seemed be fine except
collection scanning...

When you look carefully to "albumRootPath" method - in current master here:
https://cgit.kde.org/digikam.git/tree/core/libs/database/collection/collectionmanager_album.cpp#n93

there is fix for the launchpad bug #221155 that adds slash to the "rootPath"
and in my case check if "/root/album" starts with "/root//"...

I was able to fix my mistake with this knowledge and make scanning functional
again. Question is if "albumRootPath" should be more robust?  I saw similar
pattern on multiple places, I will try to send a patch...

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

[digikam] [Bug 403649] Filesystem changes are not visible in album view

[Lukáš Karas]

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

--- Comment #3 from Lukáš Karas  ---
I just upgrade to Ubuntu Cosmic (18.10) that distributes DigiKam in version
5.9.0 and problem is still here.

When I am looking to source (current master), some argument is probably empty:

if (albumRoot.isNull() || album.isEmpty())
{
// If you want to scan the album root, pass "/"
qCWarning(DIGIKAM_DATABASE_LOG) << "partialScan(QString, QString)
called with invalid values";
return;
}

How it is possible?

When I run digikam in debugger, it seems that there is no enough debug info,
local variables are not visible, just stack trace:

#0  0x7520bda0 in Digikam::CollectionScanner::partialScan(QString
const&, QString const&) () at /usr/lib/digikam/libdigikamdatabase.so.5.9.0
#1  0x7520c39e in Digikam::CollectionScanner::partialScan(QString
const&) () at /usr/lib/digikam/libdigikamdatabase.so.5.9.0
#2  0x778c70b8 in Digikam::ScanController::run() () at
/usr/lib/digikam/libdigikamgui.so.5.9.0
#3  0x75459c87 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x73f2f164 in start_thread (arg=) at
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = 
  {cancel_jmp_buf = {{jmp_buf = {140736661997312,
-7856654273440063166, 140737488344030, 140737488344031, 140737488344240,
140736661992768, 7856551462427222338, 7856645503036744002}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 
#5  0x74f2bdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


...I will try to build digikam with debug symbols...

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

[digikam] [Bug 403649] Filesystem changes are not visible in album view

[Lukáš Karas]

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

Lukáš Karas  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[digikam] [Bug 403649] New: Filesystem changes are not visible in album view

[Lukáš Karas]

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

Bug ID: 403649
   Summary: Filesystem changes are not visible in album view
   Product: digikam
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Albums-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: lukas.ka...@centrum.cz
  Target Milestone: ---

SUMMARY

When I edit image outside digikam and save result to new file (in directory
that is DigiKam album), this file is not visible in album. I have to restart
digikam.

OBSERVED RESULT

[D] 2019-01-27 10:04:40.309 2054 Digikam::AlbumWatch::rescanDirectory:267 -
Detected change, triggering rescan of "/home/karry/data/fotky/2018/12 -
prosinec/Drážďany + Míšeň/"
[D] 2019-01-27 10:04:40.548 2054
Digikam::ScanController::slotRelaxedScanning:494 - Starting scan!
[W] 2019-01-27 10:04:40.550 2058 Digikam::CollectionScanner::partialScan:631 -
partialScan(QString, QString) called with invalid values
[D] 2019-01-27 10:04:40.697 2054 Digikam::AlbumWatch::rescanDirectory:267 -
Detected change, triggering rescan of "/home/karry/data/fotky/2018/12 -
prosinec/Drážďany + Míšeň/"
[D] 2019-01-27 10:04:40.959 2054
Digikam::ScanController::slotRelaxedScanning:494 - Starting scan!
[W] 2019-01-27 10:04:40.959 2058 Digikam::CollectionScanner::partialScan:631 -
partialScan(QString, QString) called with invalid values


EXPECTED RESULT

It works fine in some previous DigiKam release. But I don't know exact version.

SOFTWARE/OS VERSIONS

Linux: Ubuntu 18.04
KDE Plasma Version: 5.12.7 
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

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

[kdeconnect] [Bug 399333] kdeconnectd crashed in clipboardplugin

[Lukáš Karas]

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

--- Comment #1 from Lukáš Karas  ---
Current version (1.3.1) fixes the crashes by disabling clipboard plugin. It is
more or less workaround, working clipboard plugin would be great! 

But I understand that provide clipboard support on Wayland may be difficult, it
should be resolved in Qt codebase...

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

[kdeconnect] [Bug 399333] New: kdeconnectd crashed in clipboardplugin

[Lukáš Karas]

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

Bug ID: 399333
   Summary: kdeconnectd crashed in clipboardplugin
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: sailfish-application
  Assignee: a...@piggz.co.uk
  Reporter: lukas.ka...@centrum.cz
  Target Milestone: ---

SUMMARY

I have KDE Connect installed on my Intex phone with Sailfish OS 2.2.1.18. KDE
connect is paired and it was connected. After some time, it crashed. I have
several coredumps with similar stacktrace, it seems to be reproducible...

STEPS TO REPRODUCE
1. pair
2. connect
3. keep it running and work...

SOFTWARE VERSIONS
KDE Connect (for SFOS): 0.1.1-1
Qt Version: 5.6.3+git6-1.5.2.jolla

ADDITIONAL INFORMATION

log seems not be useful, its tail:

20181003:104436 Debug: TCP connection done (i'm the existing device)
(/home/piggz/projects/kdeconnect-kde/core/backends/lan/lanlinkprovider.cpp:256,
void LanLinkProvider::connected())
20181003:104436 Debug: Starting server ssl (I'm the client TCP socket)
(/home/piggz/projects/kdeconnect-kde/core/backends/lan/lanlinkprovider.cpp:264,
void LanLinkProvider::connected())
20181003:104436 Debug: Socket successfully established an SSL connection
(/home/piggz/projects/kdeconnect-kde/core/backends/lan/lanlinkprovider.cpp:293,
void LanLinkProvider::encrypted())
20181003:104436 Debug: It is a known device "karry@myKubuntu"
(/home/piggz/projects/kdeconnect-kde/core/daemon.cpp:195, void
Daemon::onNewDeviceLink(const NetworkPacket&, DeviceLink*))
20181003:104436 Debug: Not loading plugin "kdeconnect_mpriscontrol" because
device doesn't support it
(/home/piggz/projects/kdeconnect-kde/core/pluginloader.cpp:129, QSet
PluginLoader::pluginsForCapabilities(const QSet&, const
QSet&))
20181003:104436 Debug: Not loading plugin "kdeconnect_lockdevice" because
device doesn't support it
(/home/piggz/projects/kdeconnect-kde/core/pluginloader.cpp:129, QSet
PluginLoader::pluginsForCapabilities(const QSet&, const
QSet&))
20181003:104436 Debug: Not loading plugin "kdeconnect_battery" because device
doesn't support it
(/home/piggz/projects/kdeconnect-kde/core/pluginloader.cpp:129, QSet
PluginLoader::pluginsForCapabilities(const QSet&, const
QSet&))
20181003:104436 Debug: Registered notifications listener for device
"karry@myKubuntu"
(/home/piggz/projects/kdeconnect-kde/plugins/sendnotifications/notificationslistener.cpp:60,
NotificationsListener::NotificationsListener(KdeConnectPlugin*))
20181003:104503 Debug: Received wakeup
(/home/piggz/projects/kdeconnect-kde/sfos/sailfishdaemon.cpp:47,
SailfishDaemon::SailfishDaemon(QObject*)::__lambda0)
20181003:104533 Debug: Received wakeup
(/home/piggz/projects/kdeconnect-kde/sfos/sailfishdaemon.cpp:47,
SailfishDaemon::SailfishDaemon(QObject*)::__lambda0)
20181003:104603 Debug: Received wakeup
(/home/piggz/projects/kdeconnect-kde/sfos/sailfishdaemon.cpp:47,
SailfishDaemon::SailfishDaemon(QObject*)::__lambda0)
20181003:104633 Debug: Received wakeup
(/home/piggz/projects/kdeconnect-kde/sfos/sailfishdaemon.cpp:47,
SailfishDaemon::SailfishDaemon(QObject*)::__lambda0)
20181003:104703 Debug: Received wakeup
(/home/piggz/projects/kdeconnect-kde/sfos/sailfishdaemon.cpp:47,
SailfishDaemon::SailfishDaemon(QObject*)::__lambda0)


(gdb) bt full
#0  QClipboard::setMimeData (this=, src=0x13f1b38,
mode=QClipboard::Clipboard) at kernel/qclipboard.cpp:466
clipboard = 
#1  0xb3d06d52 in ClipboardPlugin::receivePacket (this=, np=...)
at /home/piggz/projects/kdeconnect-kde/plugins/clipboard/clipboardplugin.cpp:47
content = {static null = {}, d = 0x11d78f8}
#2  0xb6ebf014 in Device::privateReceivedPacket (this=0x13ae490, np=...) at
/home/piggz/projects/kdeconnect-kde/core/device.cpp:403
plugin = 
__for_range = @0xbe897ea4: {> =
{}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {_M_i = -1}, }}}, alloc = 0, begin
= 0, end = 0, array = {0x0}}, d = 0x13021e0}, d = 0x13021e0}}
plugins = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {_M_i = -1}, }}}, alloc = 0, begin
= 0, end = 0, array = {0x0}}, d = 0x13021e0}, d = 0x13021e0}}
__PRETTY_FUNCTION__ = "void Device::privateReceivedPacket(const
NetworkPacket&)"
#3  0xb6c09e94 in call (a=0xbe897fb0, r=, this=0x1309298) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
No locals.
#4  QMetaObject::activate (sender=sender@entry=0x132cc90,
signalOffset=, local_signal_index=local_signal_index@entry=4,
argv=argv@entry=0xbe897fb0) at kernel/qobject.cpp:3715
obj = {d = 0x1309298}
receiverInSameThread = 
sw = {receiver = 0x13ae490, previousSender = 0x0, currentSender =
{sender = 0x132cc90, signal = 7, ref = 1}, switched = true}
callFunction = 
receiver = 
method_relative = 
c = 0x13092b0
last = 0x13092b0

[kio-extras] [Bug 394600] [KIO / sftp] copy to remote server with full disk fails silently

[Lukáš Karas]

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

--- Comment #3 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Ups. You are correct, i was using kioclient from KDE4 in console, sorry. I
mixed kioclient and scp commands in original post moreover...

Anyway, the same problem exists with kio 5:

cd /tmp/
mkdir ramdisk
sudo mount -t tmpfs - ramdisk -o size=1M
dd if=/dev/urandom of=bigfile bs=1M count=2

kioclient5 cp bigfile sftp://localhost/tmp/ramdisk

...
kf5.kio.core.copyjob: emit processedSize 1044480
kf5.kio.core.copyjob: d->state= 6
kf5.kio.core.copyjob: 0 files remaining
kf5.kio.core.copyjob: 
kf5.kio.core.copyjob: copyNextFile finished
kf5.kio.core.copyjob: KDirNotify'ing FilesAdded
QUrl("sftp://localhost/tmp/ramdisk;

echo $?
0

ls -alh ramdisk/* bigfile 
-rw-rw-r-- 1 karry karry 2.0M May 24 07:19 bigfile
-rw-rw-r-- 1 karry karry 1.0M May 24 07:23 ramdisk/bigfile.part

kioclient5 --version
kioclient 5.12.4

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

[dolphin] [Bug 394600] New: [KIO / sftp] copy to remote server with full disk fails silently

[Lukáš Karas]

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

Bug ID: 394600
   Summary: [KIO / sftp] copy to remote server with full disk
fails silently
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: lukas.ka...@centrum.cz
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Created attachment 112824
  --> https://bugs.kde.org/attachment.cgi?id=112824=edit
reporting kio bugs are disabled?!

First, sorry that I am reporting KIO bug to Dolphin, but there is no
possibility to create bug report for KIO directly. Why?!

And now the bug: when I copy files to remote machine using sftp protocol (sftp
kio) and remove machine has full disk, there is no error reported to user, but
files are not copied...

>From shell, it is visible that copy was not successful: 

```
scp file root@remote:/home/user/

...
kio_sftp(23014) sftpProtocol::sftpPut: Error during 'put'. Aborting.
...
kio_sftp(23014)/kio (kioslave) KIO::SlaveBase::dispatchLoop: slave was killed,
returning
```

When I am using scp command, I get usable error message:

```
scp file root@remote:/home/user
   
   
  
scp: /home/user//file: No space left on device
```

I am using KDE from Kubuntu 18.04 packages:
```
$ kioclient --version
Qt: 4.8.7
KDE Development Platform: 4.14.38
KIO Client: 2.0
```

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

[krunner] [Bug 393564] New: Krunner crashed after typing few characters

[Lukáš Karas]

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

Bug ID: 393564
   Summary: Krunner crashed after typing few characters
   Product: krunner
   Version: 5.10.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: lukas.ka...@centrum.cz
  Target Milestone: ---

Application: krunner (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.16.1 x86_64
Distribution: Ubuntu 17.10

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

I just aktivate krunner by keyboard shortcut, type start of the command and
krunner crashed. It happen time by time

The crash can be reproduced sometimes.

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

Thread 14 (Thread 0x7f36727fc700 (LWP 11691)):
#0  0x7f36c436d072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5617c7539a74) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f36c436d072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5617c7539a20, cond=0x5617c7539a48) at pthread_cond_wait.c:502
#2  0x7f36c436d072 in __pthread_cond_wait (cond=0x5617c7539a48,
mutex=0x5617c7539a20) at pthread_cond_wait.c:655
#3  0x7f36c6a396cb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f369f376995 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f369f37aa18 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f369f375b5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f369f37aa72 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f369f375b5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f369f3788db in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f36c6a3829d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f36c43667fc in start_thread (arg=0x7f36727fc700) at
pthread_create.c:465
#12 0x7f36c633ab5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7f3672ffd700 (LWP 11690)):
#0  0x7f36c436d072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5617c7539a74) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f36c436d072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5617c7539a20, cond=0x5617c7539a48) at pthread_cond_wait.c:502
#2  0x7f36c436d072 in __pthread_cond_wait (cond=0x5617c7539a48,
mutex=0x5617c7539a20) at pthread_cond_wait.c:655
#3  0x7f36c6a396cb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f369f376995 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f369f37aa18 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f369f375b5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f369f37aa72 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f369f375b5d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f369f3788db in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f36c6a3829d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f36c43667fc in start_thread (arg=0x7f3672ffd700) at
pthread_create.c:465
#12 0x7f36c633ab5f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f36737fe700 (LWP 11689)):
#0  0x7f36c436d072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x5617c7539a74) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f36c436d072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x5617c7539a20, cond=0x5617c7539a48) at pthread_cond_wait.c:502
#2  0x7f36c436d072 in __pthread_cond_wait (cond=0x5617c7539a48,
mutex=0x5617c7539a20) at pthread_cond_wait.c:655
#3  0x7f36c6a396cb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f369f376995 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f369f37aa18 in  () at

[plasmashell] [Bug 387930] New: Plasma crashed when processing signla from telepathy

[Lukáš Karas]

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

Bug ID: 387930
   Summary: Plasma crashed when processing signla from telepathy
   Product: plasmashell
   Version: 5.10.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lukas.ka...@centrum.cz
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.14.5 x86_64
Distribution: Ubuntu 17.10

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

I just do my daily work and Plasma crashed. From stacktrace is visible that it
is related with processing signal from telepathy in kpeople library...

The crash does not seem to be reproducible.

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

Thread 8 (Thread 0x7f2dd9f9b700 (LWP 3037)):
#0  0x7f2e9aff95c8 in g_mutex_lock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f2e9afb3cf6 in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2e9afb41f0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2e9afb427c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2ea0cc149b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f2ea0c66e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f2ea0a863ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f2ddc5b4717 in KCupsConnection::run() () at
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#8  0x7f2ea0a8b29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f2e9fc217fc in start_thread (arg=0x7f2dd9f9b700) at
pthread_create.c:465
#10 0x7f2ea038db0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f2dec95a700 (LWP 2850)):
#0  0x7f2ea037cffd in __GI___libc_read (fd=16, buf=0x7f2dec959a20,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f2e9aff8280 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2e9afb3c4b in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2e9afb4110 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2e9afb427c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f2ea0cc149b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f2ea0c66e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f2ea0a863ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f2ea477c846 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x7f2ea0a8b29d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f2e9fc217fc in start_thread (arg=0x7f2dec95a700) at
pthread_create.c:465
#11 0x7f2ea038db0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f2e7bfff700 (LWP 2755)):
#0  0x7f2e9fc28072 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f2ea671ffb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f2e9fc28072 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f2ea671ff68, cond=0x7f2ea671ff90) at pthread_cond_wait.c:502
#2  0x7f2e9fc28072 in __pthread_cond_wait (cond=0x7f2ea671ff90,
mutex=0x7f2ea671ff68) at pthread_cond_wait.c:655
#3  0x7f2ea642bbd4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f2ea642bc19 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f2e9fc217fc in start_thread (arg=0x7f2e7bfff700) at
pthread_create.c:465
#6  0x7f2ea038db0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f2e8617b700 (LWP 2590)):
#0  0x7f2ea037cffd in __GI___libc_read (fd=11, buf=0x7f2e8617aa70,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f2e9aff8280 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2e9afb3c4b in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2e9afb4110 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f2e9afb427c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f2ea0cc149b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f2ea0c66e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f2ea0a863ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f2ea3be6f45 in  () at 

[plasmashell] [Bug 387614] New: Plasmashell crashed after resume from sleep

[Lukáš Karas]

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

Bug ID: 387614
   Summary: Plasmashell crashed after resume from sleep
   Product: plasmashell
   Version: 5.10.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lukas.ka...@centrum.cz
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.14.3 x86_64
Distribution: Ubuntu 17.10

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

Hi, I just wakeup my notebook from sleep (after one hour, on different network)
and Plasma crashed after unlock the screen. 
I guess that it is related with kde telepathy reconnection (it is in the
stacktrace)...

The crash does not seem to be reproducible.

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

Thread 9 (Thread 0x7ff0908c5700 (LWP 13479)):
#0  0x7ff17c77c901 in __GI___poll (fds=0x7ff080001b20, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff170ea9451 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7ff170e9ae10 in pa_mainloop_poll () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7ff170e9b4a0 in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7ff170e9b530 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7ff170ea9399 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7ff1700efed8 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
#7  0x7ff17c01c7fc in start_thread (arg=0x7ff0908c5700) at
pthread_create.c:465
#8  0x7ff17c788b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7ff0a6eb3700 (LWP 11633)):
#0  0x7ff17c77c901 in __GI___poll (fds=0x7ff09c003f60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff1773af169 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff1773af27c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff17d0bc49b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff17d061e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff17ce813ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff17ffe1f45 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7ff17ce8629d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ff17c01c7fc in start_thread (arg=0x7ff0a6eb3700) at
pthread_create.c:465
#9  0x7ff17c788b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7ff0b2421700 (LWP 6575)):
#0  0x7ff17d0babe7 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7ff17d0bc82c in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7ff1773ae6a8 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff1773af09b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff1773af27c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff17d0bc49b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff17d061e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff17ce813ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ff0b4a3a717 in KCupsConnection::run() () at
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#9  0x7ff17ce8629d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7ff17c01c7fc in start_thread (arg=0x7ff0b2421700) at
pthread_create.c:465
#11 0x7ff17c788b0f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7ff0c8ec2700 (LWP 5552)):
#0  0x7ff1773f45d4 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff1773aeb69 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff1773af110 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff1773af27c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff17d0bc49b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff17d061e3a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff17ce813ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff180b77846 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7ff17ce8629d in  () at 

[krunner] [Bug 384353] New: Krunner crash sometimes

[Lukáš Karas]

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

Bug ID: 384353
   Summary: Krunner crash sometimes
   Product: krunner
   Version: 5.9.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: lukas.ka...@centrum.cz
  Target Milestone: ---

Application: krunner (5.9.5)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.12.10 x86_64
Distribution: Ubuntu 17.04

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

I just activate krunner by keyboard shortcut (ctrl+F12), wrote "virtualbox" and
press Enter. KRunner crashed then...

The crash can be reproduced sometimes.

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

Thread 12 (Thread 0x7ff86effd700 (LWP 9917)):
[KCrash Handler]
#6  0x7ff8b595fc67 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff8b59663a5 in operator<(QString const&, QString const&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ff8a2139184 in  () at /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
#9  0x7ff8a2128c38 in  () at /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
#10 0x7ff8a2129ad3 in  () at /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
#11 0x7ff8b5ad8789 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7ff8a21643ac in  () at /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
#13 0x7ff8a2167785 in  () at /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
#14 0x7ff8b738c570 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#15 0x7ff8b5ad9639 in QObject::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7ff8b6a1735c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7ff8b6a1eb21 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7ff8b5aacc00 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7ff8b5aaf39d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7ff8b5b00c93 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7ff8b0c87377 in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7ff8b0c875e0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7ff8b0c8768c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7ff8b5b0109f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7ff8b5aaabea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7ff887548796 in  () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_baloosearchrunner.so
#27 0x7ff88ed15538 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5
#28 0x7ff88eaf4bf8 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#29 0x7ff88eaf3630 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#30 0x7ff88eaf31d0 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#31 0x7ff8b58ddc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7ff8b2fbb6da in start_thread (arg=0x7ff86effd700) at
pthread_create.c:456
#33 0x7ff8b51ead7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 11 (Thread 0x7ff86f7fe700 (LWP 9916)):
#0  0x7ff8b2fc1510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff8b58deaeb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7ff88eaf1240 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7ff88eaf5478 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7ff88eaf03bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7ff88eaf54d2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7ff88eaf03bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5

[kontact] [Bug 343923] Konract crash on startup when existing instance running

[Lukáš Karas]

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

Lukáš Karas <lukas.ka...@centrum.cz> changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from Lukáš Karas <lukas.ka...@centrum.cz> ---
I am not able to reproduce any more. Closing it.

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

[kontact] [Bug 354276] Kontact crashed when switched from KMail to Akregator

[Lukáš Karas]

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

Lukáš Karas <lukas.ka...@centrum.cz> changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Lukáš Karas <lukas.ka...@centrum.cz> ---
I am not able to reproduce any more. Closing it.

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

[kontact] [Bug 354699] Akregator crash when view web page and move cursor over link (KHTMLPart::overURL, KFileItem::mimeComment...)

[Lukáš Karas]

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

Lukáš Karas <lukas.ka...@centrum.cz> changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Hi. I can't reproduce this bug any more (version 5.2.3). Closing it.

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

[kontact] [Bug 358908] Kontact crashed when restarting akonadi

[Lukáš Karas]

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

Lukáš Karas <lukas.ka...@centrum.cz> changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from Lukáš Karas <lukas.ka...@centrum.cz> ---
I don't see this bug in recent months. I am closing it...

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

[kwin] [Bug 379547] New: KWin creshed when I touch of left top screen corner with mouse (desktop grid action)

[Lukáš Karas]

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

Bug ID: 379547
   Summary: KWin creshed when I touch of left top screen corner
with mouse (desktop grid action)
   Product: kwin
   Version: 5.9.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukas.ka...@centrum.cz
  Target Milestone: ---

Application: kwin_x11 (5.9.4)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.11.0 x86_64
Distribution: Ubuntu 17.04

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

I was using my desktop as usual, when I wanted to show desktop grid, kwin
crashed. 

This crash is not reproducible just after kwin_x11 restart, but when I trigger
another action, 
like window presentation, followed with desktop grid, it crash... It seems to
me that previous 
action keep some dirty context that affect desktop grid. But it is hard to say
what it is without 
debugging...

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7fa443fff700 (LWP 28380)):
#0  0x7fa4a0f94251 in __GI_ppoll (fds=0x7fa3a8000ac8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fa49e85b251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa49e85cb4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa49e80988a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa49e636fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa499401df5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fa49e63bc98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa49a6946da in start_thread (arg=0x7fa443fff700) at
pthread_create.c:456
#8  0x7fa4a0fa017f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7fa442cf1700 (LWP 28377)):
#0  0x7fa4a0f94251 in __GI_ppoll (fds=0x7fa3ac000da8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fa49e85b251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa49e85cb4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa49e80988a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa49e636fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa499401df5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fa49e63bc98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa49a6946da in start_thread (arg=0x7fa442cf1700) at
pthread_create.c:456
#8  0x7fa4a0fa017f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7fa44d0d3700 (LWP 28376)):
#0  0x7fa4a0f94251 in __GI_ppoll (fds=0x7fa44406f338, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fa49e85b251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa49e85cb4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa49e80988a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa49e636fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa499401df5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7fa49e63bc98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa49a6946da in start_thread (arg=0x7fa44d0d3700) at
pthread_create.c:456
#8  0x7fa4a0fa017f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7fa448be2700 (LWP 28370)):
#0  0x7fa4a0f94251 in __GI_ppoll (fds=0x7fa3b40a39b8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7fa49e85b251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa49e85cb4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fa49e80988a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa49e636fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa49e63bc98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa49a6946da in start_thread (arg=0x7fa448be2700) at
pthread_create.c:456
#7  0x7fa4a0fa017f 

[kwin] [Bug 356141] virtual desktop ?

[Lukáš Karas]

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

Lukáš Karas <lukas.ka...@centrum.cz> changed:

   What|Removed |Added

 CC||lukas.ka...@centrum.cz

--- Comment #2 from Lukáš Karas <lukas.ka...@centrum.cz> ---
I got similar stacktrace when I restarted kded5 process and it turn off my
external monitor (keep just notebook display).

I have Kubuntu 16.10
kwin 5.7.5
Qt 5.6.1 
Intel graphics card

Backtrace k pádu, na který jsem narazil/a:

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

Thread 8 (Thread 0x7fa1d8bff700 (LWP 14354)):
#0  0x7fa28c3d2ea3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa28a254caf in qt_safe_select (nfds=21,
fdread=fdread@entry=0x7fa1c8000a58, fdwrite=fdwrite@entry=0x7fa1c8000ce8,
fdexcept=fdexcept@entry=0x7fa1c8000f78, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7fa28a256754 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7fa1c8000f78, writefds=0x7fa1c8000ce8, readfds=0x7fa1c8000a58,
nfds=, this=0x7fa1c80b00b0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fa1c80008c0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7fa28a256c6a in QEventDispatcherUNIX::processEvents
(this=0x7fa1c80b00b0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7fa28a2010fa in QEventLoop::exec (this=this@entry=0x7fa1d8bfec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fa28a026d43 in QThread::exec (this=this@entry=0x559902cdb170) at
thread/qthread.cpp:500
#7  0x7fa284ad7c65 in QQmlThreadPrivate::run (this=0x559902cdb170) at
qml/ftw/qqmlthread.cpp:141
#8  0x7fa28a02bc68 in QThreadPrivate::start (arg=0x559902cdb170) at
thread/qthread_unix.cpp:341
#9  0x7fa28597970a in start_thread (arg=0x7fa1d8bff700) at
pthread_create.c:333
#10 0x7fa28c3dd0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7fa25bfff700 (LWP 9779)):
#0  0x7fa28c3d2ea3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa28a254caf in qt_safe_select (nfds=17,
fdread=fdread@entry=0x7fa1d4000a78, fdwrite=fdwrite@entry=0x7fa1d4000d08,
fdexcept=fdexcept@entry=0x7fa1d4000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7fa28a256754 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7fa1d4000f98, writefds=0x7fa1d4000d08, readfds=0x7fa1d4000a78,
nfds=, this=0x7fa1d40008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fa1d40008e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7fa28a256c6a in QEventDispatcherUNIX::processEvents
(this=0x7fa1d40008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7fa28a2010fa in QEventLoop::exec (this=this@entry=0x7fa25bffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fa28a026d43 in QThread::exec (this=this@entry=0x55990577fb10) at
thread/qthread.cpp:500
#7  0x7fa284ad7c65 in QQmlThreadPrivate::run (this=0x55990577fb10) at
qml/ftw/qqmlthread.cpp:141
#8  0x7fa28a02bc68 in QThreadPrivate::start (arg=0x55990577fb10) at
thread/qthread_unix.cpp:341
#9  0x7fa28597970a in start_thread (arg=0x7fa25bfff700) at
pthread_create.c:333
#10 0x7fa28c3dd0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7fa264e28700 (LWP 9778)):
#0  0x7fa28c3d2ea3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa28a254caf in qt_safe_select (nfds=16,
fdread=fdread@entry=0x7fa1cc01eff8, fdwrite=fdwrite@entry=0x7fa1cc01f288,
fdexcept=fdexcept@entry=0x7fa1cc01f518, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7fa28a256754 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7fa1cc01f518, writefds=0x7fa1cc01f288, readfds=0x7fa1cc01eff8,
nfds=, this=0x7fa1cc0008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fa1cc01ee60,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7fa28a256c6a in QEventDispatcherUNIX::processEvents
(this=0x7fa1cc0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7fa28a2010fa in QEventLoop::exec (this=this@entry=0x7fa264e27c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fa28a026d43 in QThread::exec (this=this@entry=0x559903864120) at
thread/qthread.cpp:500
#7  0x7fa284ad7c65 in QQmlThreadPrivate::run (this=0x559903864120) at
qml/ftw/qqmlthread.cpp:141
#8  0x7fa28a02bc68 in QThreadPrivate::sta

[Akonadi] [Bug 361575] New: Background operation cause crash of akonadi_imap (Akonadi::Protocol::HelloResponse::HelloResponse)

[Lukáš Karas via KDE Bugzilla]

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

Bug ID: 361575
   Summary: Background operation cause crash of akonadi_imap
(Akonadi::Protocol::HelloResponse::HelloResponse)
   Product: Akonadi
   Version: GIT (master)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: libakonadi
  Assignee: kdepim-b...@kde.org
  Reporter: lukas.ka...@centrum.cz

akonadi_imap_resource crashed after computer resume from suspend. 

Reproducible: Couldn't Reproduce

Steps to Reproduce:
I have no idea

Actual Results:  
Application: akonadi_imap_resource (akonadi_imap_resource), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f188227a940 (LWP 9986))]

Thread 7 (Thread 0x7f1880164700 (LWP 10012)):
#0  0x7f18918795ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f188d9c2c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f188d9c48d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f1881e8f4a9 in QXcbEventReader::run (this=0x157e6e0) at
qxcbconnection.cpp:1253
#4  0x7f18921857fe in QThreadPrivate::start (arg=0x157e6e0) at
thread/qthread_unix.cpp:331
#5  0x7f188e5df6fa in start_thread (arg=0x7f1880164700) at
pthread_create.c:333
#6  0x7f18918852dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f187e9c5700 (LWP 10093)):
#0  0x7f18918750ed in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f188d2df6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f188d29be14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f188d29c2d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f188d29c43c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f18923bca7b in QEventDispatcherGlib::processEvents
(this=0x7f1878c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f1892363d8a in QEventLoop::exec (this=this@entry=0x7f187e9c4c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f1892180854 in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7f18921857fe in QThreadPrivate::start (arg=0x15e1210) at
thread/qthread_unix.cpp:331
#9  0x7f188e5df6fa in start_thread (arg=0x7f187e9c5700) at
pthread_create.c:333
#10 0x7f18918852dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f187e1c4700 (LWP 10106)):
#0  0x7f18918750ed in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f188d2df6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f188d29be14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f188d29c2d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f188d29c43c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f18923bca7b in QEventDispatcherGlib::processEvents
(this=0x7f18740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f1892363d8a in QEventLoop::exec (this=this@entry=0x7f187e1c3c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f1892180854 in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7f18921857fe in QThreadPrivate::start (arg=0x15fb9d0) at
thread/qthread_unix.cpp:331
#9  0x7f188e5df6fa in start_thread (arg=0x7f187e1c4700) at
pthread_create.c:333
#10 0x7f18918852dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f187cfb3700 (LWP 10212)):
#0  0x7f18918750ed in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f188d2df6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f188d29be14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f188d29c2d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f188d29c43c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f18923bca7b in QEventDispatcherGlib::processEvents
(this=0x7f18680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f1892363d8a in QEventLoop::exec (this=this@entry=0x7f187cfb2c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f1892180854 in QThread::exec (this=) at
thread/qthread.cpp:503
#8  0x7f18921857fe in QThreadPrivate::start (arg=0x1684740) at
thread/qthread_unix.cpp:331
#9  0x7f188e5df6fa in start_thread (arg=0x7f187cfb3700) at
pthread_create.c:333
#10 0x7f18918852dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f186d598700 (LWP 10871)):
#0  0x7f18918795ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f188d29c32c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f188d29c43c in g_main_context_iteration () from

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #12 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Thank Maik, good job.

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

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #9 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Linker problem exists on latest Ubuntu Xenial (unreleased yet). You can
reproduce it when you install Docker on your machine, download attached
Dockerfile to directory "dk-build-ubuntu-test" and try to compile digikam in
container based on this image...

# build docker image:
docker build --tag dk-build-ubuntu-test:latest dk-build-ubuntu-test

# try to compile digikam in container:
docker run --rm=true -it dk-build-ubuntu-test /usr/bin/make

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

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #8 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Created attachment 98233
  --> https://bugs.kde.org/attachment.cgi?id=98233=edit
make log with docker image

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

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #7 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Created attachment 98232
  --> https://bugs.kde.org/attachment.cgi?id=98232=edit
Docker image based on ubuntu:xenial that help to reproduce compile problem

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

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #5 from Lukáš Karas <lukas.ka...@centrum.cz> ---
No. When I compile it by these instructions, it fails too. On linking
renamecustomizertest...

Are you able to reproduce? I can try to prepare Docker image if you will have
problems to reproduce this bug...

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

[kwin] [Bug 359529] KWin (X11) crashed after login (two monitor configuration)

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #2 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Sorry, it seems that it was random bug. I connect external monitor twice per
day and it don't shows up again since then.

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

[Akonadi] [Bug 361319] New: akonadi_googlecalendar_resource crashed when it runs on background

[Lukáš Karas via KDE Bugzilla]

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

Bug ID: 361319
   Summary: akonadi_googlecalendar_resource crashed when it runs
on background
   Product: Akonadi
   Version: GIT (master)
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@kde.org
  Reporter: lukas.ka...@centrum.cz
CC: kdepim-b...@kde.org

I re-compile Akonadi from source some hours before this crash. My current head
is: bf2fddd8ecb9a8e3ec8d50d8371b651e1c1e3406

I found many bugs related with this assert in "createItemSyncInstanceIfMissing"
but it seems that none is related with this code path. Sorry if this report is
duplicate.

Application: akonadi_googlecalendar_resource (akonadi_googlecalendar_resource),
signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f70c61d8940 (LWP 3099))]

Thread 5 (Thread 0x7f70c40c8700 (LWP 3127)):
#0  0x7f70dcfaf5ad in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f70d4d0ec62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f70d4d108d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f70c5def4a9 in QXcbEventReader::run (this=0x920010) at
qxcbconnection.cpp:1253
#4  0x7f70dd8bb7fe in QThreadPrivate::start (arg=0x920010) at
thread/qthread_unix.cpp:331
#5  0x7f70d46e36fa in start_thread (arg=0x7f70c40c8700) at
pthread_create.c:333
#6  0x7f70dcfbb2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f70c2b35700 (LWP 3160)):
#0  socketNotifierSourceCheck (source=0x7f70b4002e00) at
kernel/qeventdispatcher_glib.cpp:74
#1  0x7f70d41c1d61 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f70d41c22d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f70d41c243c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f70ddaf2a6b in QEventDispatcherGlib::processEvents
(this=0x7f70b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f70dda99d7a in QEventLoop::exec (this=this@entry=0x7f70c2b34c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f70dd8b6854 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f70dd8bb7fe in QThreadPrivate::start (arg=0x9a2790) at
thread/qthread_unix.cpp:331
#8  0x7f70d46e36fa in start_thread (arg=0x7f70c2b35700) at
pthread_create.c:333
#9  0x7f70dcfbb2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f70c2334700 (LWP 3170)):
#0  0x7f70d4206a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f70d41c224e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f70d41c243c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f70ddaf2a6b in QEventDispatcherGlib::processEvents
(this=0x7f70b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f70dda99d7a in QEventLoop::exec (this=this@entry=0x7f70c2333c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f70dd8b6854 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f70dd8bb7fe in QThreadPrivate::start (arg=0x99cbc0) at
thread/qthread_unix.cpp:331
#7  0x7f70d46e36fa in start_thread (arg=0x7f70c2334700) at
pthread_create.c:333
#8  0x7f70dcfbb2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f70c1b33700 (LWP 3237)):
#0  0x7f70d41c1c7f in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f70d41c22d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f70d41c243c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f70ddaf2a6b in QEventDispatcherGlib::processEvents
(this=0x7f70ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f70dda99d7a in QEventLoop::exec (this=this@entry=0x7f70c1b32c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f70dd8b6854 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f70dd8bb7fe in QThreadPrivate::start (arg=0x9a87d0) at
thread/qthread_unix.cpp:331
#7  0x7f70d46e36fa in start_thread (arg=0x7f70c1b33700) at
pthread_create.c:333
#8  0x7f70dcfbb2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f70c61d8940 (LWP 3099)):
[KCrash Handler]
#6  0x7f70dcee9518 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f70dceeb0ea in __GI_abort () at abort.c:89
#8  0x7f70dd8a8fb1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=this@entry=0x7ffee00e0bd0,
msg=msg@entry=0x7f70ddb66028 "ASSERT failure in %s: \"%s\", file %s, line %d")
at 

[Akonadi] [Bug 353957] Akonadi IMAP resource crashed when checked maildir

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #16 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Yes, it seems to be fixed already. You can close it. If it shows up again,
someone can reopen it...

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

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #3 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Created attachment 98187
  --> https://bugs.kde.org/attachment.cgi?id=98187=edit
CMakeLists.txt patch that fixes build

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

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #1 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Created attachment 98185
  --> https://bugs.kde.org/attachment.cgi?id=98185=edit
cmake log

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

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #2 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Created attachment 98186
  --> https://bugs.kde.org/attachment.cgi?id=98186=edit
make log

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

[digikam] [Bug 361275] New: Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

Bug ID: 361275
   Summary: Compile time error: undefined reference while linking
renamecustomizertest
   Product: digikam
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Advanced Rename
  Assignee: digikam-de...@kde.org
  Reporter: lukas.ka...@centrum.cz

When I try to compile digikam from git, it fails on linking
renamecustomizertest:

[ 88%] Linking CXX executable renamecustomizertest
../../utilities/importui/libimportui.a(renamecustomizer.cpp.o): In function
`Digikam::RenameCustomizer::RenameCustomizer(QWidget*, QString const&)':
/media/karry/data/src/digikam/utilities/importui/widgets/renamecustomizer.cpp:143:
undefined reference to
`Digikam::AdvancedRenameWidget::AdvancedRenameWidget(QWidget*)'

...and many more. See attached logs for more details

My current head is:
d3a20a0cd682dddcc6f9ff8f5990028232d845b5

Attached patch solves this problem. But I don't know if my fix is correct...

Reproducible: Always

Steps to Reproduce:
1. cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/usr .. 
2. make

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

[telepathy] [Bug 359571] Plasma (and ktp-contact-list) crashed when I block new contact invitation on jabber (telepathy-gabble)

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #5 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Ok, I created review request: https://git.reviewboard.kde.org/r/127532/

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

[telepathy] [Bug 359571] Plasma (and ktp-contact-list) crashed when I block new contact invitation on jabber (telepathy-gabble)

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #3 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Another similar case in method PersonsModelPrivate::onContactAdded:

stacktrace:

Thread 1 (Thread 0x7fb0af99d8c0 (LWP 3044)):
[KCrash Handler]
#6  0x7fb0a9cf3518 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7fb0a9cf50ea in __GI_abort () at abort.c:89
#8  0x7fb0aa49cfb1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=this@entry=0x7ffe47e02600,
msg=msg@entry=0x7fb0aa75a028 "ASSERT failure in %s: \"%s\", file %s, line %d")
at global/qlogging.cpp:781
#10 0x7fb0aa498181 in qt_assert_x (where=, what=, file=, line=) at global/qglobal.cpp:2974
#11 0x7faff143d617 in QList::operator[]
(this=0x5cd3c28, i=-1) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:518
#12 0x7faff143a7da in KPeople::PersonsModelPrivate::onContactAdded
(this=0x5cd3c00, contactUri=..., contact=...) at
/media/karry/data/src/kpeople/src/personsmodel.cpp:305
#13 0x7faff14406da in QtPrivate::FunctorCall<QtPrivate::IndexesList<0, 1>,
QtPrivate::List const&>, void, void
(KPeople::PersonsModelPrivate::*)(QString const&,
QExplicitlySharedDataPointer const&)>::call (f=(void
(KPeople::PersonsModelPrivate::*)(KPeople::PersonsModelPrivate * const, const
QString &, const QExplicitlySharedDataPointer &))
0x7faff143a6fa <KPeople::PersonsModelPrivate::onContactAdded(QString const&,
QExplicitlySharedDataPointer const&)>, o=0x5cd3c00,
arg=0x7ffe47e02910) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:501
#14 0x7faff144021d in QtPrivate::FunctionPointer
const&)>::call<QtPrivate::List const&>, void> (f=(void
(KPeople::PersonsModelPrivate::*)(KPeople::PersonsModelPrivate * const, const
QString &, const QExplicitlySharedDataPointer &))
0x7faff143a6fa <KPeople::PersonsModelPrivate::onContactAdded(QString const&,
QExplicitlySharedDataPointer const&)>, o=0x5cd3c00,
arg=0x7ffe47e02910) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:520
#15 0x7faff143fcff in QtPrivate::QSlotObject const&),
QtPrivate::List const&>, void>::impl
(which=1, this_=0x5ed76f0, r=0x5cd3c00, a=0x7ffe47e02910, ret=0x0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:143
#16 0x7fb0aa6bee1f in QtPrivate::QSlotObjectBase::call (a=0x7ffe47e02910,
r=0x5cd3c00, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#17 QMetaObject::activate (sender=0x71206c0, signalOffset=,
local_signal_index=, argv=) at
kernel/qobject.cpp:3698
#18 0x7faff0f9eed0 in KPeople::AllContactsMonitor::contactAdded
(this=0x71206c0, _t1=..., _t2=...) at
/media/karry/data/src/kpeople/myBuild/src/backends/moc_allcontactsmonitor.cpp:177
#19 0x7fafcc3ddf0b in KTpAllContacts::onAllKnownContactsChanged
(this=0x71206c0, contactsAdded=..., contactsRemoved=...) at
/media/karry/data/src/ktp-common-internals/kpeople/datasourceplugin/im-persons-data-source.cpp:302
#20 0x7fafcc3de872 in KTpAllContacts::qt_static_metacall (_o=0x71206c0,
_c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7ffe47e02bc0) at
/media/karry/data/src/ktp-common-internals/myBuild/kpeople/datasourceplugin/im-persons-data-source.moc:105
#21 0x7fb0aa6bef9a in QMetaObject::activate (sender=0x69e6c80,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3713
#22 0x7fafda571a08 in KTp::GlobalContactManager::allKnownContactsChanged
(this=0x69e6c80, _t1=..., _t2=...) at
/media/karry/data/src/ktp-common-internals/myBuild/KTp/moc_global-contact-manager.cpp:178
#23 0x7fafda554226 in
KTp::GlobalContactManager::onContactManagerStateChanged (this=0x69e6c80,
contactManager=..., state=Tp::ContactListStateSuccess) at
/media/karry/data/src/ktp-common-internals/KTp/global-contact-manager.cpp:138
#24 0x7fafda554046 in KTp::GlobalContactManager::onConnectionReady
(this=0x69e6c80, op=0x818ecb0) at
/media/karry/data/src/ktp-common-internals/KTp/global-contact-manager.cpp:119
#25 0x7fafda5717b6 in KTp::GlobalContactManager::qt_static_metacall
(_o=0x69e6c80, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7ffe47e02e30) at
/media/karry/data/src/ktp-common-internals/myBuild/KTp/moc_global-contact-manager.cpp:116
#26 0x7fb0aa6bef9a in QMetaObject::activate (sender=0x818ecb0,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3713
#27 0x7fafda12dd0f in Tp::PendingOperation::finished(Tp::PendingOperation*)
() from /usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
#28 0x7fafda12f430 in ?? () from
/usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
#29 0x7fb0aa6bfe71 in QObject::event (this=0x818ecb0, e=) at
kernel/qobject.cpp:1239
#30 0x7fb0aaf8305c in QApplicationPrivate::notify_helper
(this=this@entry=0x249d5a0, receiver=receiver@entry=0x818ecb0,
e=e@entry=0x71e8c50) at kernel/qapplication.cpp:3716
#31 0x

[telepathy] [Bug 359571] Plasma (and ktp-contact-list) crashed when I block new contact invitation on jabber (telepathy-gabble)

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #2 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Created attachment 98130
  --> https://bugs.kde.org/attachment.cgi?id=98130=edit
patch that avoids access to list with negative index

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

[telepathy] [Bug 359571] Plasma (and ktp-contact-list) crashed when I block new contact invitation on jabber (telepathy-gabble)

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #1 from Lukáš Karas <lukas.ka...@centrum.cz> ---
I recompiled kpeople today and this bug still exists... 
kpeople head: a72809761419457b803e13ab91c1a1950b5f9ac8

I created simple patch that avoids `metacontacts[personRow]` access when
`personRow` is < 0. 

diff --git a/src/personsmodel.cpp b/src/personsmodel.cpp
index 0c9fa13..13bdb50 100644
--- a/src/personsmodel.cpp
+++ b/src/personsmodel.cpp
@@ -343,6 +343,11 @@ void PersonsModelPrivate::onContactRemoved(const QString
)

 int personRow = personIndex[personUri].row();

+if(personRow < 0){
+qDebug() << "personRow: " << personRow << ", contactUri: " <<
contactUri << ", personUri: " << personUri;
+removePerson(personUri);
+return;
+}
 MetaContact  = metacontacts[personRow];
 int contactPosition = mc.contactUris().indexOf(contactUri);
 q->beginRemoveRows(q->index(personRow, 0), contactPosition,
contactPosition);

Console output when I remove spam contact:

personRow:  -1 , contactUri: 
"ktp://gabble/jabber/ktp_2djabber_2dim_12?doofyn...@swissjabber.org" ,
personUri: 
"ktp://gabble/jabber/ktp_2djabber_2dim_12?doofyn...@swissjabber.org"

It fixes these crashes but I don't know if this is correct place where it
should be fixed...

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

[plasmashell] [Bug 359571] New: Plasma (and ktp-contact-list) crashed when I block new contact invitation on jabber (telepathy-gabble)

[Lukáš Karas via KDE Bugzilla]

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

Bug ID: 359571
   Summary: Plasma (and ktp-contact-list) crashed when I block new
contact invitation on jabber (telepathy-gabble)
   Product: plasmashell
   Version: 5.5.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: lukas.ka...@centrum.cz
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.4)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.1 x86_64
Distribution: Ubuntu Xenial Xerus (development branch)

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

When I loged in to my jabber account (telepathy-gabble), plasma notify my that
someone wants to add me to his contact list. It was spam, so I decided block
it. Then, plasmashell and ktp-contact-list crashed. It happens often and I have
to block same accounts after each login.

I compiled KDE from source code just days before. 
kpeople head : dbf8ba2fdebf3829a816abc847fc064edc106f13
ktp-common-internals head: 2a955003f509900332fb950d67e06309bb8bea26
plasma-workspace head: a62aae16e9e758a5fcf75f8a7704a03608de4dfc

The crash can be reproduced sometimes.

-- 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 0x7f6f37cbc900 (LWP 12504))]

Thread 10 (Thread 0x7f6f22b23700 (LWP 12506)):
#0  0x7f6f320f89ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f6f363d3c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f6f363d58d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6f24c6d539 in QXcbEventReader::run (this=0x14d7a40) at
qxcbconnection.cpp:1230
#4  0x7f6f327ee7fe in QThreadPrivate::start (arg=0x14d7a40) at
thread/qthread_unix.cpp:331
#5  0x7f6f318da66a in start_thread (arg=0x7f6f22b23700) at
pthread_create.c:333
#6  0x7f6f3210401d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f6f1bdf9700 (LWP 12507)):
#0  0x7f6f320f45ad in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f6f2edbe700 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6f2ed7ae24 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f2ed7b2e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6f2ed7b44c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f6f32a25a5b in QEventDispatcherGlib::processEvents
(this=0x7f6f140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f6f329ccd6a in QEventLoop::exec (this=this@entry=0x7f6f1bdf8ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f6f327e9854 in QThread::exec (this=this@entry=0x15cd980) at
thread/qthread.cpp:503
#8  0x7f6f351eec85 in QQmlThreadPrivate::run (this=0x15cd980) at
qml/ftw/qqmlthread.cpp:141
#9  0x7f6f327ee7fe in QThreadPrivate::start (arg=0x15cd980) at
thread/qthread_unix.cpp:331
#10 0x7f6f318da66a in start_thread (arg=0x7f6f1bdf9700) at
pthread_create.c:333
#11 0x7f6f3210401d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f6f10a35700 (LWP 12508)):
#0  0x7f6f320f45ad in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f6f2edbe700 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6f2ed7ae24 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f2ed7b2e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6f2ed7b44c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f6f32a25a5b in QEventDispatcherGlib::processEvents
(this=0x7f6f0c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x7f6f329ccd6a in QEventLoop::exec (this=this@entry=0x7f6f10a34ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f6f327e9854 in QThread::exec (this=this@entry=0x18d32d0) at
thread/qthread.cpp:503
#8  0x7f6f351eec85 in QQmlThreadPrivate::run (this=0x18d32d0) at
qml/ftw/qqmlthread.cpp:141
#9  0x7f6f327ee7fe in QThreadPrivate::start (arg=0x18d32d0) at
thread/qthread_unix.cpp:331
#10 0x7f6f318da66a in start_thread (arg=0x7f6f10a35700) at
pthread_create.c:333
#11 0x7f6f3210401d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f6f0a73c700 (LWP 12509)):
#0  0x7f6f320f89ed in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f6f2ed7b33c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6f2ed7b44c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6f32a25a5b in 

[kwin] [Bug 359529] New: KWin (X11) crashed after login (two monitor configuration)

[Lukáš Karas via KDE Bugzilla]

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

Bug ID: 359529
   Summary: KWin (X11) crashed after login (two monitor
configuration)
   Product: kwin
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: lukas.ka...@centrum.cz

Application: kwin_x11 (5.5.90)
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.4.1 x86_64
Distribution: Ubuntu Xenial Xerus (development branch)

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

Hi, I just login to KDE session and kwin crashed. I had to switch to terminal,
setup DISPLAY variable and start kwin_x11 again.

I compiled kwin from master just before restart, my HEAD is:
f0ec89f38b1dd86d8b79f1057706b222bce80bba

QT version 5.5.1, packages are from Ubuntu Xenial (development)

$ kwin_x11 --version
kwin 5.5.90

$ glxinfo | grep version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
Max core profile version: 3.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.2
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 11.1.2
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.1.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

$ xrandr 
Screen 0: minimum 8 x 8, current 4160 x 1440, maximum 32767 x 32767
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 310mm x
174mm
   1600x900  60.04*+  40.02  
   1440x900  59.89  
   1368x768  60.00  
   1360x768  59.8059.96  
   1152x864  60.00  
   1280x720  60.00  
   1024x768  60.00  
   1024x576  60.00  
   960x540   60.00  
   800x600   60.3256.25  
   864x486   60.00  
   800x450   60.00  
   640x480   59.94  
   720x405   60.00  
   640x360   60.00  
DP1 connected primary 2560x1440+1600+0 (normal left inverted right x axis y
axis) 597mm x 336mm
   2560x1440 59.95*+  29.94  
   1920x1200 59.88  
   1920x1080 60.0059.94  
   1600x1200 60.00  
   1280x1024 60.02  
   1280x960  60.00  
   1280x720  60.0059.94  
   1024x768  60.00  
   800x600   60.32  
   720x480   60.0059.94  
   640x480   60.0059.9459.93  
   720x400   70.08  
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f080c6b656d in
KWin::XRandRScreens::update (this=0xed9690)
at /media/karry/data/src/kwin/screens_xrandr.cpp:76
#7  0x7f080c6b5016 in KWin::XRandRScreens::init (this=0xed9690) at
/media/karry/data/src/kwin/screens_xrandr.cpp:119
#8  0x7f080c6b385d in KWin::Screens::create (parent=0x7ffeeef525d0) at
/media/karry/data/src/kwin/screens.cpp:53
#9  0x7f080c69fba5 in KWin::Application::createScreens
(this=0x7ffeeef525d0) at /media/karry/data/src/kwin/main.cpp:391
#10 0x7f080c61fff6 in KWin::Workspace::init (this=0xe09c90) at
/media/karry/data/src/kwin/workspace.cpp:217
#11 0x7f080c61fb42 in KWin::Workspace::Workspace (this=0xe09c90,
sessionKey=...) at /media/karry/data/src/kwin/workspace.cpp:210
#12 0x7f080c69fb2b in KWin::Application::createWorkspace
(this=0x7ffeeef525d0) at /media/karry/data/src/kwin/main.cpp:374
#13 0x7f080cf23bc2 in KWin::ApplicationX11::::operator()(void)
const (__closure=0x7ffeeef51c20) at /media/karry/data/src/kwin/main_x11.cpp:182
#14 0x7f080cf24e4e in QtPrivate::FunctorCall,
QtPrivate::List<>, void, KWin::ApplicationX11::performStartup()::
>::call(KWin::ApplicationX11::, void **) (f=..., arg=0x7ffeeef51d80)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:495
#15 0x7f080cf24dcf in
QtPrivate::Functor,
0>::call, void>(KWin::ApplicationX11:: &, void *,
void **) (f=..., arg=0x7ffeeef51d80) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:552
#16 0x7f080cf24d68 in
QtPrivate::QFunctorSlotObject,
0, 

[Akonadi] [Bug 354536] Akonadi fails to migrate database from version 30 (foreign key constraint fails)

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #7 from Lukáš Karas <lukas.ka...@centrum.cz> ---
Good to know that. What about automatic fsck operation before every schema
upgrade? We can avoid similar situations in the future. But we should trust
fsck code and keep it updated then...

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