from:"bugzy"

[ghostwriter] [Bug 485691] Ghostwriter crashes on launch

2024-05-25 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

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

[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes

2024-03-14 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

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

[korganizer] [Bug 347045] Sunday is always automatically selected once weekly recurrence drop down is clicked

2022-11-07 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

Version|5.4.3   |5.21.2
 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #7 from bugzy  ---
Still reproducable on korganizer 5.21.2

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

[kalendar] [Bug 450377] Kalendar Reminders crashes on Plasma startup

2022-02-16 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 CC||c...@carlschwan.eu
Product|kde |kalendar
  Component|general |general
   Assignee|unassigned-b...@kde.org |claudio.cam...@gmail.com
Version|unspecified |0.4.0

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

[kde] [Bug 450377] New: Kalendar Reminders crashes on Plasma startup

2022-02-16 Thread bugzy

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

Bug ID: 450377
   Summary: Kalendar Reminders crashes on Plasma startup
   Product: kde
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

Application: kalendarac ()

Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.16.8-200.fc35.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 35 (KDE Plasma)
DrKonqi: 5.23.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Logged into plasma desktop and as soon as splash screen is dismissed there is
an error about Kalendar Reminders crashing

The crash can be reproduced every time.

-- Backtrace:
Application: Kalendar Reminders (kalendarac), signal: Segmentation fault

[KCrash Handler]
#4  0x7f93549426c7 in QHashData::nextNode(QHashData::Node*) () from
/lib64/libQt5Core.so.5
#5  0x559a943ed758 in KalendarAlarmClient::checkAlarms() ()
#6  0x7f9354afa3e9 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7  0x7f935569b596 in Akonadi::EntityTreeModel::collectionPopulated(long
long) () from /lib64/libKF5AkonadiCore.so.5
#8  0x7f93556a6efc in
Akonadi::EntityTreeModelPrivate::itemFetchJobDone(long long, KJob*) () from
/lib64/libKF5AkonadiCore.so.5
#9  0x7f9354afa3e9 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7f93554a7680 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#11 0x7f93554abceb in KJob::finishJob(bool) () from
/lib64/libKF5CoreAddons.so.5
#12 0x7f9354af0f49 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7f9354ac67d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#14 0x7f9354ac9d46 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x7f9354b18117 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#16 0x7f935244d05f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#17 0x7f93524a22a8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#18 0x7f935244a853 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#19 0x7f9354b17bb8 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#20 0x7f9354ac51e2 in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#21 0x7f9354acd724 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#22 0x559a943ea58d in main ()
[Inferior 1 (process 1812) detached]

Possible duplicates by query: bug 430007, bug 421299, bug 401450, bug 391363,
bug 390491.

Reported using DrKonqi
This report was filed against 'kde' because the product 'kalendarac' could not
be located in Bugzilla. Add it to drkonqi's mappings file!

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

[kalendar] [Bug 444617] Kalendar crashes on open

2021-10-29 Thread bugzy

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

--- Comment #3 from bugzy  ---
(In reply to qydwhotmail from comment #1)
> Delete ~/.cache/kalendar may work.

I suppose that may have been what fixed it rather than the uninstall and
reinstall.

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

[kalendar] [Bug 444617] Kalendar crashes on open

2021-10-29 Thread bugzy

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

--- Comment #2 from bugzy  ---
Uninstalling kalendar from
https://copr.fedorainfracloud.org/coprs/zawertun/kde/package/kalendar/

And Installing kalendar from kalendar
https://copr.fedorainfracloud.org/coprs/marcdeop/kalendar/build/2912884/ fixes
the issue

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

[kalendar] [Bug 444617] New: Kalendar crashes on open

2021-10-29 Thread bugzy

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

Bug ID: 444617
   Summary: Kalendar crashes on open
   Product: kalendar
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

Application: kalendar (0.1)

Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-200.fc34.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora 34 (KDE Plasma)
DrKonqi: 5.23.2 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
- Upgraded to plasma 5.23.2 and kf 5.87.0
- Restarted system
- Attempted to open kalendar and it crashes

The crash can be reproduced every time.

-- Backtrace:
Application: Kalendar (kalendar), signal: Segmentation fault

[KCrash Handler]
#4  0x7f6f985274d4 in QQmlType::QQmlType(QQmlType const&) () from
/lib64/libQt5Qml.so.5
#5  0x7f6f983791d0 in
QQmlPropertyCacheCreator::buildMetaObjectRecursively(int,
QQmlBindingInstantiationContext const&,
QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) [clone
.cold] () from /lib64/libQt5Qml.so.5
#6  0x7f6f9857b4d1 in
QQmlPropertyCacheCreator::buildMetaObjectRecursively(int,
QQmlBindingInstantiationContext const&,
QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) () from
/lib64/libQt5Qml.so.5
#7  0x7f6f9857c370 in QQmlTypeCompiler::compile() () from
/lib64/libQt5Qml.so.5
#8  0x7f6f984edd5c in QQmlTypeData::done() () from /lib64/libQt5Qml.so.5
#9  0x7f6f984e183d in QQmlDataBlob::tryDone() () from /lib64/libQt5Qml.so.5
#10 0x7f6f9852d7c9 in QQmlTypeLoader::setData(QQmlDataBlob*,
QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5
#11 0x7f6f9852e266 in QQmlTypeLoader::setData(QQmlDataBlob*, QString
const&) () from /lib64/libQt5Qml.so.5
#12 0x7f6f9852ed08 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from
/lib64/libQt5Qml.so.5
#13 0x7f6f9852f16c in QQmlTypeLoader::load(QQmlDataBlob*,
QQmlTypeLoader::Mode) () from /lib64/libQt5Qml.so.5
#14 0x7f6f985346d2 in QQmlTypeLoader::getType(QUrl const&,
QQmlTypeLoader::Mode) () from /lib64/libQt5Qml.so.5
#15 0x7f6f984f5c24 in QQmlTypeData::resolveTypes() () from
/lib64/libQt5Qml.so.5
#16 0x7f6f984f61bd in QQmlTypeData::allDependenciesDone() () from
/lib64/libQt5Qml.so.5
#17 0x7f6f9852da32 in QQmlTypeLoader::setData(QQmlDataBlob*,
QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5
#18 0x7f6f9852e266 in QQmlTypeLoader::setData(QQmlDataBlob*, QString
const&) () from /lib64/libQt5Qml.so.5
#19 0x7f6f9852ed08 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from
/lib64/libQt5Qml.so.5
#20 0x7f6f9852f16c in QQmlTypeLoader::load(QQmlDataBlob*,
QQmlTypeLoader::Mode) () from /lib64/libQt5Qml.so.5
#21 0x7f6f985346d2 in QQmlTypeLoader::getType(QUrl const&,
QQmlTypeLoader::Mode) () from /lib64/libQt5Qml.so.5
#22 0x7f6f984f5c24 in QQmlTypeData::resolveTypes() () from
/lib64/libQt5Qml.so.5
#23 0x7f6f984f61bd in QQmlTypeData::allDependenciesDone() () from
/lib64/libQt5Qml.so.5
#24 0x7f6f9852da32 in QQmlTypeLoader::setData(QQmlDataBlob*,
QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5
#25 0x7f6f9852e266 in QQmlTypeLoader::setData(QQmlDataBlob*, QString
const&) () from /lib64/libQt5Qml.so.5
#26 0x7f6f9852ed08 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from
/lib64/libQt5Qml.so.5
#27 0x7f6f9852f16c in QQmlTypeLoader::load(QQmlDataBlob*,
QQmlTypeLoader::Mode) () from /lib64/libQt5Qml.so.5
#28 0x7f6f985346d2 in QQmlTypeLoader::getType(QUrl const&,
QQmlTypeLoader::Mode) () from /lib64/libQt5Qml.so.5
#29 0x7f6f984f5c24 in QQmlTypeData::resolveTypes() () from
/lib64/libQt5Qml.so.5
#30 0x7f6f984f61bd in QQmlTypeData::allDependenciesDone() () from
/lib64/libQt5Qml.so.5
#31 0x7f6f9852da32 in QQmlTypeLoader::setData(QQmlDataBlob*,
QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5
#32 0x7f6f9852e266 in QQmlTypeLoader::setData(QQmlDataBlob*, QString
const&) () from /lib64/libQt5Qml.so.5
#33 0x7f6f9852ed08 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from
/lib64/libQt5Qml.so.5
#34 0x7f6f984f29f1 in QQmlTypeLoaderThread::loadThread(QQmlDataBlob*) ()
from /lib64/libQt5Qml.so.5
#35 0x7f6f9858feaf in QQmlThreadPrivate::event(QEvent*) () from
/lib64/libQt5Qml.so.5
#36 0x7f6f97131443 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#37 0x7f6f9665f798 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#38 0x7f6f96662d06 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#39 0x7f6f966b10d7 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*)

[kalendar] [Bug 444445] New: Kalendar configuration settings is empty

2021-10-26 Thread bugzy

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

Bug ID: 45
   Summary: Kalendar configuration settings is empty
   Product: kalendar
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

Created attachment 142918
  --> https://bugs.kde.org/attachment.cgi?id=142918=edit
empty config window

SUMMARY
Kalendar configuration menu triggered by "Ctrl+Shift+," is empty.

STEPS TO REPRODUCE
1. Click Hamburger menu to the top left
2. Select Configure 
3. Select Configure Kalendar...

OBSERVED RESULT
A new window titled "Configure -- Kalendar" pops up with no configuration
options. See attached picture.

EXPECTED RESULT
Configuration window should contain some options, some placeholder text like
"More customization coming soon," or Configuration menu item can be removed
until there are tweakable options


SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.10-200.fc34.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics

ADDITIONAL INFORMATION
* Note: this issue could very well be a packaging issue, but I am inclined not
to think that it is, at least until I hear back from the developers.

* Kalendar Version: 0.1-2.20211024git88c9bfd obtained from: 
https://copr.fedorainfracloud.org/coprs/zawertun/kde/package/kalendar/

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

[kalendar] [Bug 444384] Selecting Weekly Recurrence/Repeat does not bring up day selection check boxes

2021-10-26 Thread bugzy

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

--- Comment #4 from bugzy  ---
I see, much thanks. I wonder if something like a pre-selected day checkbox for
a simple 7 day recurrence may work easier than two distinct categories (i.e.
"Weekly," and "Custom"). That should ease the UI changes and category confusion
at least in my case. I suppose that another alternative may be to rename
"Custom" into  "Weekly (Custom)" since that is what it actually is.

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

[kalendar] [Bug 444391] New: Kalendar crashes when marking sub-tasks in a caldav calendar as done

2021-10-25 Thread bugzy

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

Bug ID: 444391
   Summary: Kalendar crashes when marking sub-tasks in a caldav
calendar as done
   Product: kalendar
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

Application: kalendar (0.1)

Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.14.10-200.fc34.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.22.5
Distribution: Fedora 34 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:
I was clicking on the relevant circles on some of my subtasks in order to mark
them as done. The first subtask i clicked behaved as expected, but the second
crashed the app

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Kalendar (kalendar), signal: Aborted

[KCrash Handler]
#4  0x7ff3bdb932a2 in raise () from /lib64/libc.so.6
#5  0x7ff3bdb7c8a4 in abort () from /lib64/libc.so.6
#6  0x7ff3be01245b in QMessageLogger::fatal(char const*, ...) const () from
/lib64/libQt5Core.so.5
#7  0x7ff3be01185c in qt_assert(char const*, char const*, int) () from
/lib64/libQt5Core.so.5
#8  0x7ff3bcb8550b in Akonadi::ImapSet::add(QVector const&)
[clone .cold] () from /lib64/libKF5AkonadiPrivate.so.5
#9  0x7ff3bf93a252 in Akonadi::Scope
Akonadi::ProtocolHelper::entitySetToScope(QVector const&) () from
/lib64/libKF5AkonadiCore.so.5
#10 0x7ff3bf94cc20 in Akonadi::ItemMoveJob::doStart() () from
/lib64/libKF5AkonadiCore.so.5
#11 0x7ff3bf947fdd in Akonadi::JobPrivate::startQueued() () from
/lib64/libKF5AkonadiCore.so.5
#12 0x7ff3be231f09 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7ff3becd9443 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#14 0x7ff3be207798 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#15 0x7ff3be20ad06 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#16 0x7ff3be2590d7 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#17 0x7ff3bbf924cf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#18 0x7ff3bbfe64f8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#19 0x7ff3bbf8fc03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#20 0x7ff3be258b78 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#21 0x7ff3be2061a2 in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#22 0x7ff3be20e6e4 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#23 0x5653160f2b61 in main ()
[Inferior 1 (process 361643) detached]

Possible duplicates by query: bug 424911, bug 423951, bug 423132, bug 417285,
bug 414922.

Reported using DrKonqi

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

[kalendar] [Bug 444388] New: Kalendar displays events at wrong time in certain time zones

2021-10-25 Thread bugzy

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

Bug ID: 444388
   Summary: Kalendar displays events at wrong time in certain time
zones
   Product: kalendar
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

Created attachment 142869
  --> https://bugs.kde.org/attachment.cgi?id=142869=edit
Timezone display issue

SUMMARY
Kalendar displays events at wrong time in certain time zones

STEPS TO REPRODUCE
1. Create a new Event
2. Fill out title and all other relevant options for the event
3. Using America/Matamoros timezone 

OBSERVED RESULT
Event is displayed one hour off from expected time even though the event card
representation is correct. (See attached screenshot)

EXPECTED RESULT
Event should be displayed at correct time

SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.10-200.fc34.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics

ADDITIONAL INFORMATION
* Kalendar Version: 0.1-2.20211024git88c9bfd obtained from: 
https://copr.fedorainfracloud.org/coprs/zawertun/kde/package/kalendar/

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

[kalendar] [Bug 444384] Selecting Weekly Recurrence/Repeat does not bring up day selection check boxes

2021-10-25 Thread bugzy

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

--- Comment #1 from bugzy  ---
Created attachment 142868
  --> https://bugs.kde.org/attachment.cgi?id=142868=edit
Broken repeat rule selector

Here is a screenshot of the isssue

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

[kalendar] [Bug 444384] New: Selecting Weekly Recurrence/Repeat does not bring up day selection check boxes

2021-10-25 Thread bugzy

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

Bug ID: 444384
   Summary: Selecting Weekly Recurrence/Repeat does not bring up
day selection check boxes
   Product: kalendar
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

SUMMARY
Selecting Weekly Recurrence/Repeat does not bring up day selection check boxes

STEPS TO REPRODUCE
1. Create a new Event
2. Fill out title and all other relevant options for the event
3. For the "Repeat:" rule, select "Weekly"

OBSERVED RESULT
There is no way to select what days to repeat the even on

EXPECTED RESULT
A list of check boxes should be shown to allow selection of what days the event
should repeat on.



SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.10-200.fc34.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics

ADDITIONAL INFORMATION
* Kalendar Version: 0.1-2.20211024git88c9bfd obtained from: 
https://copr.fedorainfracloud.org/coprs/zawertun/kde/package/kalendar/

* Any recurring events set up in another application (Korganizer for instance)
can be edited since the selection boxes show up as expected in those cases.

* Saving the event without repeating days still works but it causes other
issues in other applications such as not being able to select the day of the
event as part of the recurrence.

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

[kdeconnect] [Bug 441046] New: [Wayland] kdeconnect clipboard sync is broken

2021-08-16 Thread bugzy

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

Bug ID: 441046
   Summary: [Wayland] kdeconnect clipboard sync is broken
   Product: kdeconnect
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

SUMMARY
kdeconnect clipboard sync is broken in wayland session

STEPS TO REPRODUCE
1. Pair and connect mobile device to PC (Plasma wayland session).
2. Ensure that relevant options and pemissions for clipboard sync are enabled
on both mobile device and PC.
3. Attempt to copy from PC and paste on mobile device.

OBSERVED RESULT
Nothing is available on mobile device clipboard for pasting. Note that doing
the same for X11 Plasma session works as expected.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.13.8
(available in About System)
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator

2021-07-09 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 CC||tro...@free.fr

--- Comment #3 from bugzy  ---
*** Bug 397825 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle

2021-07-09 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 CC||bugzylit...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #41 from bugzy  ---


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

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

[kmail2] [Bug 427584] Missing content display in the mail pane

2021-07-09 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||bugzylit...@gmail.com
 Status|REOPENED|RESOLVED

--- Comment #4 from bugzy  ---


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

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

[kontact] [Bug 438345] Contents load as Blank Page in Wayland - Kmail and Akregator

2021-07-09 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 CC||markus.elfr...@web.de

--- Comment #2 from bugzy  ---
*** Bug 427584 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"

2021-07-09 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

--- Comment #17 from bugzy  ---
This is now over two years since this issue has been reported, extensively
commented on (https://bugs.kde.org/show_bug.cgi?id=393421 and
https://www.reddit.com/r/kde/comments/do27td/a_cure_for_kmail_html_message_status_bar/),
and had an alternative design proposed (See https://phabricator.kde.org/M155).
It would be nice if this issue got some fresh attention either to revert
https://phabricator.kde.org/R94:1c55919a64491bd5598cf9d8616e77b037edbf87 or
move in the direction of the proposal listed above.

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

[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History

2019-12-16 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

--- Comment #36 from bugzy  ---
Problem: KDE Connect-SMS App never syncs SMS messages
STEPS TO REPRODUCE
1. Click on KDE Connect in the system tray
2. Click the 3-dot menu
3. Select 'SMS Messages'

OBSERVED RESULT
The loading icon stays spinning forever, and no messages are synced.

EXPECTED RESULT
All messages on the targeted phone are synced.

SOFTWARE/OS VERSIONS
Phone: Moto G7 Power
Android Version: 9
SMS app: Stock "Messages" App
KDE Connect Version: 1.4.0 (Desktop); 1.13.5 (Android)
Linux: 5.3.13-200.fc30
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.12.5

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

[zanshin] [Bug 411339] zanshin fails to run on neon

2019-09-30 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

   Platform|Neon Packages   |Fedora RPMs
 CC||bugzylit...@gmail.com

--- Comment #4 from bugzy  ---
This is true for all distros not just Neon. On Fedora 30, I get:
zanshin: symbol lookup error: zanshin: undefined symbol: _ZTIN8KCalCore4TodoE

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

[Akonadi] [Bug 395131] Akonadi consumes all memory

2018-10-26 Thread bugzy

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

bugzy  changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

--- Comment #5 from bugzy  ---
I also ran into the same problem. I believe that the problem in this case may
be that your akonadi mysql database is older than what the latest mariadb or
mysql server versions you have installed on the system will allow. Regrettably,
it is not evident how to log into the maridb instance that akonadi is using to
that the database can be upgraded. In any case, the workaround is as you have
described. delete the entire akonadi mysql database.

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

[plasmashell] [Bug 400252] New: Plasma crashes on login

2018-10-24 Thread bugzy

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

Bug ID: 400252
   Summary: Plasma crashes on login
   Product: plasmashell
   Version: 5.12.6
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugzylit...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.6)

Qt Version: 5.9.6
Frameworks Version: 5.48.0
Operating System: Linux 4.18.13-100.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

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

I logged into a new session and plasma session never loaded the taskbar. Then
it crashed. All attempts to restart plasmashell behave the same way. That is:
1. Desktop loads with icons
2. Taskbar never loads
3. Everything goes black (Plasmashell segfaults)

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f0c6e263700 (LWP 30260)):
#0  0x7f0d3edde8b8 in read () at /lib64/libc.so.6
#1  0x7f0d372ec160 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f0d372a79c8 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f0d372a7e60 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f0d372a7fcc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f0d3fc39d3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f0d3fbe7a3a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f0d3fa38a1a in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f0c70bca5a7 in KCupsConnection::run() () at /lib64/libkcupslib.so
#9  0x7f0d3fa3cf32 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7f0d3e13f50b in start_thread () at /lib64/libpthread.so.0
#11 0x7f0d3eded38f in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f0c85765700 (LWP 30253)):
#0  0x7f0d3ede2ddb in poll () at /lib64/libc.so.6
#1  0x7f0d372a7eb9 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f0d372a7fcc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f0d3fc39d3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f0d3fbe7a3a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f0d3fa38a1a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f0d44a59576 in QQuickPixmapReader::run() () at
/lib64/libQt5Quick.so.5
#7  0x7f0d3fa3cf32 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f0d3e13f50b in start_thread () at /lib64/libpthread.so.0
#9  0x7f0d3eded38f in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f0d19358700 (LWP 30252)):
#0  0x7f0d3e14582d in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f0d46d8c604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f0d46d8c649 in  () at /lib64/libQt5Script.so.5
#3  0x7f0d3e13f50b in start_thread () at /lib64/libpthread.so.0
#4  0x7f0d3eded38f in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f0d1b3b8700 (LWP 30251)):
#0  0x7f0d3ede2ddb in poll () at /lib64/libc.so.6
#1  0x7f0d372a7eb9 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f0d372a7fcc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f0d3fc39d3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f0d3fbe7a3a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f0d3fa38a1a in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f0d43eba565 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f0d3fa3cf32 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f0d3e13f50b in start_thread () at /lib64/libpthread.so.0
#9  0x7f0d3eded38f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f0d219cb700 (LWP 30250)):
#0  0x7f0d372ed499 in g_mutex_lock () at /lib64/libglib-2.0.so.0
#1  0x7f0d372a78f6 in g_main_context_check () at /lib64/libglib-2.0.so.0
#2  0x7f0d372a7e60 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f0d372a7fcc in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f0d3fc39d3b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f0d3fbe7a3a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f0d3fa38a1a in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f0d43eba565 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7f0d3fa3cf32 in QThreadPrivate::start(void*)

[plasmashell] [Bug 394377] Plasma Crashes when switching activities

2018-05-18 Thread bugzy

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

--- Comment #3 from bugzy <bugzylit...@gmail.com> ---
Yes, I have the web plasmoid running on one of my desktops.

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

[plasmashell] [Bug 394377] New: Plasma Crashes when switching activities

2018-05-17 Thread bugzy

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

Bug ID: 394377
   Summary: Plasma Crashes when switching activities
   Product: plasmashell
   Version: 5.12.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugzylit...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.5)

Qt Version: 5.9.4
Frameworks Version: 5.46.0
Operating System: Linux 4.16.7-200.fc27.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Switched activities using assigned mouse shortcut (horizontal scroll)

The crash can be reproduced sometimes.

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

Thread 24 (Thread 0x7fe451bf7700 (LWP 15346)):
#0  0x7fe5bdc4e738 in read () from /lib64/libc.so.6
#1  0x7fe5b2db7941 in pa_read () from
/usr/lib64/pulseaudio/libpulsecommon-11.1.so
#2  0x7fe5b36e4c9e in pa_mainloop_prepare () from /lib64/libpulse.so.0
#3  0x7fe5b36e5710 in pa_mainloop_iterate () from /lib64/libpulse.so.0
#4  0x7fe5b36e57d0 in pa_mainloop_run () from /lib64/libpulse.so.0
#5  0x7fe5b36f3639 in thread () from /lib64/libpulse.so.0
#6  0x7fe5b2de6ac8 in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-11.1.so
#7  0x7fe5bcf9f50b in start_thread () from /lib64/libpthread.so.0
#8  0x7fe5bdc5d16f in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7fe452ffb700 (LWP 5676)):
#0  0x7fe5b5ec83d9 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7fe5b5e82f98 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#2  0x7fe5beab1c4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7fe5bea5f96a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7fe5be8b08ca in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7fe5be8b4de2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#6  0x7fe5bcf9f50b in start_thread () from /lib64/libpthread.so.0
#7  0x7fe5bdc5d16f in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7fe4537fc700 (LWP 5675)):
#0  0x7fe5b5ec83f4 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7fe5b5e823ec in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7fe5b5e82dcb in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7fe5b5e82fac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7fe5beab1c4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7fe5bea5f96a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7fe5be8b08ca in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7fe5be8b4de2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fe5bcf9f50b in start_thread () from /lib64/libpthread.so.0
#9  0x7fe5bdc5d16f in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7fe453ffd700 (LWP 5662)):
#0  0x7fe5bdc4e738 in read () from /lib64/libc.so.6
#1  0x7fe5b5ec70a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7fe5b5e829a8 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7fe5b5e82e40 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7fe5b5e82fac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7fe5beab1c4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7fe5bea5f96a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7fe5be8b08ca in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7fe5be8b4de2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7fe5bcf9f50b in start_thread () from /lib64/libpthread.so.0
#10 0x7fe5bdc5d16f in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7fe4989fe700 (LWP 5661)):
#0  0x7fe5bcfa582d in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe5be53de0c in
std::condition_variable::wait(std::unique_lock&) () from
/lib64/libstdc++.so.6
#2  0x7fe4a1034187 in WTF::ParkingLot::parkConditionally(void const*,
std::function, std::function,
std::chrono::time_point > >) () from
/lib64/libQt5WebKit.so.5
#3  0x7fe4a175c04d in WebCore::IconDatabase::syncThreadMainLoop() () from
/lib64/libQt5WebKit.so.5
#4  0x7fe4a175dda8 in WebCore::IconDatabase::iconDatabaseSyncThread() ()
from /lib64/libQt5WebKit.so.5
#5  0x7fe4a1036938 in WTF::threadEntryPoint(void*) () from

[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar

2018-05-17 Thread bugzy

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

--- Comment #9 from bugzy <bugzylit...@gmail.com> ---
I was able to find and fix the actual cause of the problem by running the
"calendarjanitor" tool. The tool found an orphaned TODO entry in the affected
calendar. It turns out that whenever I added a new entry into the affected
calendar, the orphaned TODO would cause korganizer to crash when parsing that
calendar. So my new entries (attached above) were not the problem, I was simply
adding new entries to a faulty calendar:

==Output of calendarjanitor (default scan mode):==

Checking for orphans...
[!!]
The following incidences are children of nonexistent parents:

* Found buggy incidence:
id=159344; summary="Set in plant dividers for garden in plot behind
house"
DTSTART=invalid; 
DTDUE=invalid; 

In fix mode these children will be unparented.


Running the too in fix mode solved the problem and everything has been running
smooth since then.


==Output of calendarjanitor --fix (fix mode):== 
Checking for orphans...
[!!]
The following incidences are children of nonexistent parents:

* Found buggy incidence:
id=159344; summary="Set in plant dividers for garden in plot behind
house"
DTSTART=invalid; 
DTDUE=invalid; 

Children were successfully unparented.

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

[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar

2018-04-28 Thread bugzy

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

--- Comment #8 from bugzy <bugzylit...@gmail.com> ---
None of the other views work. The only solution to get things functional again
is to disable the calendar with the problem.

Additional Information:
- All my calendars are webdav calendars synced using nextcloud to my various
devices.

- I should mention that the faulty todo entry was created using Zanshin. I did
not think that was relevant until I added some new todo items yesterday and
began experiencing the same problem.

I use Zanshin at work and Kontact with Korganizer on laptop and home PC.

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

[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar

2018-04-28 Thread bugzy

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

--- Comment #6 from bugzy <bugzylit...@gmail.com> ---
I have libical 2.0, specifically libical-2.0.0-13.fc27.x86_64

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

[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar

2018-04-24 Thread bugzy

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

--- Comment #13 from bugzy <bugzylit...@gmail.com> ---
Is there any way to re-open this issue. Whereas it is understandable that some
kmail devs may want the html bar displayed by default in emails, there seems to
be no real justification, or at least a satisfactory one, for removing the
ability to change that default behavior. 

Note: I speak as one who uses and likes the html bar feature. I just don't
think that it was reasonable to remove the ability to customize kmail,
especially when there was no development cost that we know of(i.e. option that
was already in place).

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

[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar

2018-04-23 Thread bugzy

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

bugzy <bugzylit...@gmail.com> changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

--- Comment #6 from bugzy <bugzylit...@gmail.com> ---
I actually like the bar and its functionality. Not that my preference addresses
the issue, but I am wondering if the toggle switch to turn off the bar at
"Settings > Configure Kmail > Appearance > General > Show HTML Side Bar" has
been removed. If not, simply turn it off.

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

[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar

2018-04-12 Thread bugzy

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

--- Comment #4 from bugzy <bugzylit...@gmail.com> ---
Deleting the bad entry fixes the issue but just wanted to document this
behavior here.

Thanks

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

[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar

2018-04-12 Thread bugzy

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

--- Comment #3 from bugzy <bugzylit...@gmail.com> ---
The last point to note is that I am able to reproduce the crash whenever I
re-import the attached todo entry. 

Steps to reproduce:
1. Download Attached Todo calendar entry
2. Import the entry and "merge" to existing calendar.
3. Close korganizer (or kontact).
4. Open korganizer.

Expected Results:
korganizer opens properly

Actual results:
korganizer crashes

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

[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar

2018-04-12 Thread bugzy

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

--- Comment #2 from bugzy <bugzylit...@gmail.com> ---
Created attachment 111995
  --> https://bugs.kde.org/attachment.cgi?id=111995=edit
terminal output on delete of bad entry

After deleting the entry directly from akonadiconsole, the line in the attached
file appeared in the terminal. Not sure if it will be helpful in diagnosing the
issue.

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

[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar

2018-04-12 Thread bugzy

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

--- Comment #1 from bugzy <bugzylit...@gmail.com> ---
Created attachment 111994
  --> https://bugs.kde.org/attachment.cgi?id=111994=edit
Todo Calendar fentry that crashes korganizer

After finding a way to disable my calendar collections and re-enable each
calendar one by one, I was able to narrow down the cause of the crash to the
attached vtodo entry. I copied the contents of the entry using akonadiconsole
and pasted it in the attached file.

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

[korganizer] [Bug 393059] New: KOrganizer crashes when using caldav calendar

2018-04-12 Thread bugzy

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

Bug ID: 393059
   Summary: KOrganizer crashes when using caldav calendar
   Product: korganizer
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

Application: korganizer (5.7.3)

Qt Version: 5.9.4
Frameworks Version: 5.44.0
Operating System: Linux 4.15.13-300.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

-- Information about the crash:
- What I was doing when the application crashed:
I opened KOrganizer and it crashed.

I am unsure if this issue is related to a calendar entry of some sort; I have
been trying to disable soem of my calendars in to see if I can narrow it down
but I have had no success thus far. I will update this if I find the culprit.

The crash can be reproduced every time.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff0ca722940 (LWP 24550))]

Thread 5 (Thread 0x7ff09a5ed700 (LWP 24555)):
#0  0x7ff0c1071738 in read () from /lib64/libc.so.6
#1  0x7ff0b65c40a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7ff0b657f9a8 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7ff0b657fe40 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7ff0b657ffac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7ff0c1ecbc4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7ff0c1e7996a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7ff0c1cca8ca in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7ff0c1ccede2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7ff0bb6f750b in start_thread () from /lib64/libpthread.so.0
#10 0x7ff0c108016f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7ff09adee700 (LWP 24553)):
#0  0x7ff0c1071738 in read () from /lib64/libc.so.6
#1  0x7ff0b65c40a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7ff0b657f9a8 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7ff0b657fe40 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7ff0b657ffac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7ff0c1ecbc4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7ff0c1e7996a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7ff0c1cca8ca in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7ff0c1ccede2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7ff0bb6f750b in start_thread () from /lib64/libpthread.so.0
#10 0x7ff0c108016f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7ff09bfff700 (LWP 24552)):
#0  0x7ff0c1071738 in read () from /lib64/libc.so.6
#1  0x7ff0b65c40a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7ff0b657f9a8 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7ff0b657fe40 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7ff0b657ffac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7ff0c1ecbc4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7ff0c1e7996a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7ff0c1cca8ca in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7ff0c36d2449 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#9  0x7ff0c1ccede2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 0x7ff0bb6f750b in start_thread () from /lib64/libpthread.so.0
#11 0x7ff0c108016f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ff0a34d8700 (LWP 24551)):
#0  0x7ff0c1075c6b in poll () from /lib64/libc.so.6
#1  0x7ff0b9cc6fe7 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7ff0b9cc8dda in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7ff0a563abf9 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7ff0c1ccede2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7ff0bb6f750b in start_thread () from /lib64/libpthread.so.0
#6  0x7ff0c108016f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ff0ca722940 (LWP 24550)):
[KCrash Handler]
#6  0x7ff0c92bad50 in greaterThan(QSharedPointer const&,
QSharedPointer const&) () from /lib64/libKF5EventViews.so.5
#7  0x7ff0c92c329a in void
std::__unguarded_linear_insert::iterator,
__gnu_cxx::__ops::_Val_comp_iter const&,
QSharedPointer const&)> >(QList::iterator,

[kdeconnect] [Bug 393030] New: Notification sync plugin no longer works from android app versions to 1.7+ to 1.8.2

2018-04-12 Thread bugzy

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

Bug ID: 393030
   Summary: Notification sync plugin no longer works from android
app versions to 1.7+ to 1.8.2
   Product: kdeconnect
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: bugzylit...@gmail.com
  Target Milestone: ---

After upgrading from kde-connect-android version 1.6.6 to version 1.7.1 and
beyond, the notification sync plugin no longer works. Rolling back to version
1.6.6 on the phone brings notifications back. I tried various apk releases for
the phone, and versions 1.2.1 and 1.3.0 on the desktop. The result remains the
same. Bellow is additional information on the 

Phone:
Samsung Galaxy S8
Android 8.0
kdeconnect versions 1.7.1, 1.8.0, 1.8.1, 1.8.2 

Desktop:
Linux Specs
Fedora 27 - kernel 4.15.15
plasma 5.12.4
kde frameworks 5.44.0
qt 5.9.4
kdeconnect: 1.2.1, 1.3.0

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

[kmail2] [Bug 381519] remove duplicates options do not work

2017-08-21 Thread bugzy

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

bugzy <bugzylit...@gmail.com> changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

--- Comment #1 from bugzy <bugzylit...@gmail.com> ---
Same issue here but on

Fedora 26
Qt: 5.7.1
KDE Frameworks: 5.36.0
KDE Plasma: 5.10.4
kmail2 5.5.1
Kernel:  4.12.5-300

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

[korganizer] [Bug 347045] Sunday is always automatically selected once weekly recurrence drop down is clicked

2017-06-24 Thread bugzy

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

--- Comment #5 from bugzy <bugzylit...@gmail.com> ---
Created attachment 106275
  --> https://bugs.kde.org/attachment.cgi?id=106275=edit
Video Showing the bug and how to reproduce it

Attached video of the bug and how to reproduce it

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

[korganizer] [Bug 347045] Sunday is always automatically selected once weekly recurrence drop down is clicked

2017-06-23 Thread bugzy

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

bugzy <bugzylit...@gmail.com> changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---
Version|unspecified |5.4.3

--- Comment #4 from bugzy <bugzylit...@gmail.com> ---
The bug still exists in korganizer (5.4.3) and kdepim 16.12.3. Whereas I have
not tested the 17.04.x versions of the same, I strongly doubt that the problem
is fixed. Nevertheless, I will update this bug as soon as fedora kde
applications packages are updated to match kde release.

When I have a chance I will also try to upload a video of this issue.

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

[kdeconnect] [Bug 345686] Allow managing calls

2017-02-20 Thread bugzy

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

bugzy <bugzylit...@gmail.com> changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

--- Comment #5 from bugzy <bugzylit...@gmail.com> ---
If a bluetooth backend were enabled, I suppose the computer could use an audio
sink and audio source profile, like a bluetooth head set profile. Then an
answered call can be handled over bluetooth the using your computer's
headphones and mic.

Not sure if this is possible, just throwing it out there. (Note: I can already
play music from my phone in plasma over bluetooth, so some part of it is
possible)

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

[www.kde.org] [Bug 370164] New: SSL certificate for planetkde.org has expired

2016-10-05 Thread bugzy via KDE Bugzilla

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

Bug ID: 370164
   Summary: SSL certificate for planetkde.org has expired
   Product: www.kde.org
   Version: unspecified
  Platform: Other
   URL: https://planetkde.org
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kde-...@kde.org
  Reporter: bugzylit...@gmail.com

The SSL certificate for the website planetkde.org expired as of October 4 2016.
Hence, all visitors to the site receive cert error messages and need to allow
exceptions in order to be able to view the web page

Reproducible: Always

Steps to Reproduce:
1. open web browser of choice
2. visit planetkde.org
3.

Actual Results:  
The following error message is displayed on firefox:
Your connection is not secure

The owner of planetkde.org has configured their website improperly. To protect
your information from being stolen, Firefox has not connected to this website.

Expected Results:  
View planetkde.org

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

[dolphin] [Bug 368367] New: Dolphin Crashes on right-click for list-menu options

2016-09-06 Thread bugzy via KDE Bugzilla

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

Bug ID: 368367
   Summary: Dolphin Crashes on right-click for list-menu options
   Product: dolphin
   Version: 15.12.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: bugzylit...@gmail.com

Application: dolphin (15.12.3)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.2-101.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

Opened dolphin
Attempted to right-click on an icon (which should bring up list menu options)

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f155730b700 (LWP 28966)):
#0  0x7f157026ab7d in poll () from /lib64/libc.so.6
#1  0x7f156c406272 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7f156c407ee7 in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7f155a08f039 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7f1570e8900c in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7f156ddd361a in start_thread () from /lib64/libpthread.so.0
#6  0x7f15702765fd in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f1555ccb700 (LWP 28967)):
#0  0x7f156b88a779 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7f156b845951 in g_main_context_query () from /lib64/libglib-2.0.so.0
#2  0x7f156b846107 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f156b84629c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f1571073b5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f157102425a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f1570e84bd4 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f1571279675 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#8  0x7f1570e8900c in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7f156ddd361a in start_thread () from /lib64/libpthread.so.0
#10 0x7f15702765fd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f154c98b700 (LWP 28968)):
#0  0x7f156ddd8b20 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f154f99ce43 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/radeonsi_dri.so
#2  0x7f154f99c597 in impl_thrd_routine () from
/usr/lib64/dri/radeonsi_dri.so
#3  0x7f156ddd361a in start_thread () from /lib64/libpthread.so.0
#4  0x7f15702765fd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f1547c83700 (LWP 28969)):
#0  0x7f157026676d in read () from /lib64/libc.so.6
#1  0x7f156b8893f0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7f156b845c84 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7f156b846130 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7f156b84629c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7f1571073b5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f157102425a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7f1570e84bd4 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7f1570e8900c in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7f156ddd361a in start_thread () from /lib64/libpthread.so.0
#10 0x7f15702765fd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f157564a940 (LWP 28965)):
[KCrash Handler]
#6  0x7f154485c204 in _GLOBAL__sub_I_qprinterinfo.cpp () from
/lib64/libQtGui.so.4
#7  0x7f1577a6b73a in call_init.part () from /lib64/ld-linux-x86-64.so.2
#8  0x7f1577a6b84b in _dl_init () from /lib64/ld-linux-x86-64.so.2
#9  0x7f1577a703a2 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2
#10 0x7f1577a6b5e4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#11 0x7f1577a6f6a3 in _dl_open () from /lib64/ld-linux-x86-64.so.2
#12 0x7f15687d4fc9 in dlopen_doit () from /lib64/libdl.so.2
#13 0x7f1577a6b5e4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#14 0x7f15687d5631 in _dlerror_run () from /lib64/libdl.so.2
#15 0x7f15687d5061 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2
#16 0x7f1571022610 in QLibraryPrivate::load_sys() () from
/lib64/libQt5Core.so.5
#17 0x7f157101cd95 in QLibraryPrivate::load() () from
/lib64/libQt5Core.so.5
#18 0x7f157101cfcb in QLibraryPrivate::loadPlugin() () from
/lib64/libQt5Core.so.5
#19 0x7f1572c946fa in KPluginLoader::load() () from

[plasmashell] [Bug 361251] New: Plasma Crashes when main/only monitor auto turns off/suspends

2016-03-31 Thread bugzy via KDE Bugzilla

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

Bug ID: 361251
   Summary: Plasma Crashes when main/only monitor auto turns
off/suspends
   Product: plasmashell
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugzylit...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
After some inactivity, my monitor on my desktop initiates the powersave feature
and turns off the screen to conserve power. Whenever I return and login, plasma
has crashed along with ksm server and a bunch of other services.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f4c27f15940 (LWP 16973))]

Thread 7 (Thread 0x7f4c074b5700 (LWP 16985)):
#0  0x7f4c1f8ecfdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4c25da7272 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7f4c074b4b80) at /usr/include/bits/poll2.h:46
#2  0x7f4c25da7272 in _xcb_conn_wait (c=c@entry=0x562fe55c8080,
cond=cond@entry=0x562fe55c80c0, vector=vector@entry=0x0, count=count@entry=0x0)
at xcb_conn.c:459
#3  0x7f4c25da8ee7 in xcb_wait_for_event (c=0x562fe55c8080) at xcb_in.c:693
#4  0x7f4c09ddfda9 in QXcbEventReader::run() (this=0x562fe55d2250) at
qxcbconnection.cpp:1255
#5  0x7f4c204f53de in QThreadPrivate::start(void*) (arg=0x562fe55d2250) at
thread/qthread_unix.cpp:331
#6  0x7f4c1ec3060a in start_thread (arg=0x7f4c074b5700) at
pthread_create.c:334
#7  0x7f4c1f8f8a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f4c04a64700 (LWP 16995)):
#0  0x7f4c1f8ecfdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4c1ae1016c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f4bf8003070, timeout=, context=0x7f4bf8000990) at
gmain.c:4135
#2  0x7f4c1ae1016c in g_main_context_iterate
(context=context@entry=0x7f4bf8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f4c1ae1027c in g_main_context_iteration (context=0x7f4bf8000990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f4c2072cecb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4bf80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f4c206d3eca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4c04a63c60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f4c204f0434 in QThread::exec() (this=this@entry=0x562fe56a05f0) at
thread/qthread.cpp:503
#7  0x7f4c2483e9b5 in QQmlThreadPrivate::run() (this=0x562fe56a05f0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7f4c204f53de in QThreadPrivate::start(void*) (arg=0x562fe56a05f0) at
thread/qthread_unix.cpp:331
#9  0x7f4c1ec3060a in start_thread (arg=0x7f4c04a64700) at
pthread_create.c:334
#10 0x7f4c1f8f8a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f4bfcc38700 (LWP 17001)):
#0  0x7f4c1f8ecfdd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4c1ae1016c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f4bf0002e70, timeout=, context=0x7f4bf990) at
gmain.c:4135
#2  0x7f4c1ae1016c in g_main_context_iterate
(context=context@entry=0x7f4bf990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3835
#3  0x7f4c1ae1027c in g_main_context_iteration (context=0x7f4bf990,
may_block=may_block@entry=1) at gmain.c:3901
#4  0x7f4c2072cecb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f4bf8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f4c206d3eca in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f4bfcc37c60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#6  0x7f4c204f0434 in QThread::exec() (this=this@entry=0x562fe58ff560) at
thread/qthread.cpp:503
#7  0x7f4c2483e9b5 in QQmlThreadPrivate::run() (this=0x562fe58ff560) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7f4c204f53de in QThreadPrivate::start(void*) (arg=0x562fe58ff560) at
thread/qthread_unix.cpp:331
#9  0x7f4c1ec3060a in start_thread (arg=0x7f4bfcc38700) at
pthread_create.c:334
#10 0x7f4c1f8f8a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f4bf5428700 (LWP 17030)):
#0  0x7f4c1f8ecfdd in poll () at

44 matches

Mail list logo