[kmail2] [Bug 489956] New: Crashes when marking a folder as read after marking a large number of folders as read - crashing presists afterwards

2024-07-08 Thread arran
https://bugs.kde.org/show_bug.cgi?id=489956

Bug ID: 489956
   Summary: Crashes when marking a folder as read after marking a
large number of folders as read - crashing presists
afterwards
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: arr...@gmail.com
  Target Milestone: ---

Application: kmail (5.24.5 (23.08.5))
 (Compiled from sources)
Qt Version: 5.15.14
Frameworks Version: 5.116.0
Operating System: Linux 6.6.30-gentoo-x86_64 x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
Moving around a lot of mail I have encountered a large number of bugs,
especially between imap servers. In this case I had moved the failing to sync
mail locally and was marking it all as read, there are a lot of folders, I was
systematically marking them as read. There is a propagation delay, if you mark
the same folder as read before it completes, especially if there are 1,000+
messages in it, kmail will crash. 

It will get into a state where it will crash every time you mark it as read
even just after opening it. I haven't tried logging out / logging in again but
I suspect based on the other errors that will "resolve" it.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[KCrash Handler]
#4  0x7feec5b583ed in Akonadi::ItemModifyJobPrivate::fullCommand() const ()
at /usr/lib64/libKPim5AkonadiCore.so.5
#5  0x7feec5b59663 in Akonadi::ItemModifyJob::doStart() () at
/usr/lib64/libKPim5AkonadiCore.so.5
#6  0x7feec5b6063c in ??? () at /usr/lib64/libKPim5AkonadiCore.so.5
#7  0x7feec7ca7278 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#8  0x7feec8702da2 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#9  0x7feec7c7c0e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#10 0x7feec7c7f584 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#11 0x7feec7cce407 in ??? () at /usr/lib64/libQt5Core.so.5
#12 0x7feec39e2824 in ??? () at /usr/lib64/libglib-2.0.so.0
#13 0x7feec39e5977 in ??? () at /usr/lib64/libglib-2.0.so.0
#14 0x7feec39e5fa0 in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#15 0x7feec7ccdefa in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#16 0x7feec7c7aadb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#17 0x7feec7c82d91 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#18 0x56419c91d084 in ??? ()
#19 0x7feec7445390 in ??? () at /usr/lib64/libc.so.6
#20 0x7feec7445449 in __libc_start_main () at /usr/lib64/libc.so.6
#21 0x56419c91d745 in ??? ()
[Inferior 1 (process 18283) detached]

Reported using DrKonqi

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

[plasmashell] [Bug 293906] Device notifier should have an option to only unmount, not detach as well

2024-06-25 Thread arran
https://bugs.kde.org/show_bug.cgi?id=293906

arran  changed:

   What|Removed |Added

 CC||arr...@gmail.com

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

[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]

2024-06-23 Thread arran
https://bugs.kde.org/show_bug.cgi?id=339214

arran  changed:

   What|Removed |Added

 CC||arr...@gmail.com

--- Comment #42 from arran  ---
After testing it on mine, you don't have to delete it.. Close kmail. Rename
~/.local/share/local-mail/ to ~/.local/share/local-mail-old/. Open Kmail. Close
Kmail. Rename the directory back worked for me.

% kmail --version
kmail2 5.24.5 (23.08.5)

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

[kdevelop] [Bug 488397] New: kdevelop crashes when I attempt to create a new project from an Akondi resource template

2024-06-11 Thread arran
https://bugs.kde.org/show_bug.cgi?id=488397

Bug ID: 488397
   Summary: kdevelop crashes when I attempt to create a new
project from an Akondi resource template
Classification: Applications
   Product: kdevelop
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: arr...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.13.240202 (24.02.2))
 (Compiled from sources)
Qt Version: 5.15.13
Frameworks Version: 5.116.0
Operating System: Linux 6.6.30-gentoo-x86_64 x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
kdevelop crashes when I attempt to create a new project from an Akondi resource
template.

It does not reoccur with a different file path.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault

[KCrash Handler]
#4  0xfff0 in ??? ()
#5  0x7f9a9e6e81ca in ??? () at
/usr/lib64/qt5/plugins/kdevplatform/513/kdevappwizard.so
#6  0x7f9acdcb0a7e in ??? () at /usr/lib64/libQt5Core.so.5
#7  0x7f9acdcb0a7e in ??? () at /usr/lib64/libQt5Core.so.5
#8  0x7f9acdcb0b8c in ??? () at /usr/lib64/libQt5Core.so.5
#9  0x7f9ace90961b in QWidgetTextControl::qt_metacall(QMetaObject::Call,
int, void**) () at /usr/lib64/libQt5Widgets.so.5
#10 0x7f9acdcb09e2 in ??? () at /usr/lib64/libQt5Core.so.5
#11 0x7f9ace20aed4 in QTextDocumentPrivate::finishEdit() () at
/usr/lib64/libQt5Gui.so.5
#12 0x7f9ace24cfd9 in QSyntaxHighlighter::setDocument(QTextDocument*) () at
/usr/lib64/libQt5Gui.so.5
#13 0x7f9ace24d23d in QSyntaxHighlighter::~QSyntaxHighlighter() () at
/usr/lib64/libQt5Gui.so.5
#14 0x7f9ac1bee9bd in Sonnet::Highlighter::~Highlighter() () at
/usr/lib64/libKF5SonnetUi.so.5
#15 0x7f9acdca859a in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#16 0x7f9acdcae8f4 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#17 0x7f9acd2a0487 in ??? () at /usr/lib64/libKF5TextWidgets.so.5
#18 0x7f9acd299210 in KTextEdit::~KTextEdit() () at
/usr/lib64/libKF5TextWidgets.so.5
#19 0x7f9acd2992ed in KTextEdit::~KTextEdit() () at
/usr/lib64/libKF5TextWidgets.so.5
#20 0x7f9acdca859a in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#21 0x7f9ace741c36 in QWidget::~QWidget() () at
/usr/lib64/libQt5Widgets.so.5
#22 0x7f9acd98942d in DvcsImportMetadataWidget::~DvcsImportMetadataWidget()
() at /usr/lib64/libKDevPlatformVcs.so.513
#23 0x7f9acdca859a in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#24 0x7f9ace741c36 in QWidget::~QWidget() () at
/usr/lib64/libQt5Widgets.so.5
#25 0x7f9ace8c0d3d in QStackedWidget::~QStackedWidget() () at
/usr/lib64/libQt5Widgets.so.5
#26 0x7f9acdca859a in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#27 0x7f9ace741c36 in QWidget::~QWidget() () at
/usr/lib64/libQt5Widgets.so.5
#28 0x7f9a9e6e84dd in ??? () at
/usr/lib64/qt5/plugins/kdevplatform/513/kdevappwizard.so
#29 0x7f9acdca859a in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#30 0x7f9ace741c36 in QWidget::~QWidget() () at
/usr/lib64/libQt5Widgets.so.5
#31 0x7f9acadee631 in ??? () at /usr/lib64/libKF5WidgetsAddons.so.5
#32 0x7f9acdca859a in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#33 0x7f9ace741c36 in QWidget::~QWidget() () at
/usr/lib64/libQt5Widgets.so.5
#34 0x7f9acadef2bd in KPageWidget::~KPageWidget() () at
/usr/lib64/libKF5WidgetsAddons.so.5
#35 0x7f9acdca859a in QObjectPrivate::deleteChildren() () at
/usr/lib64/libQt5Core.so.5
#36 0x7f9ace741c36 in QWidget::~QWidget() () at
/usr/lib64/libQt5Widgets.so.5
#37 0x7f9a9e6e33e0 in ??? () at
/usr/lib64/qt5/plugins/kdevplatform/513/kdevappwizard.so
#38 0x7f9a9e6e070e in ??? () at
/usr/lib64/qt5/plugins/kdevplatform/513/kdevappwizard.so
#39 0x7f9acdcb0a7e in ??? () at /usr/lib64/libQt5Core.so.5
#40 0x7f9ace6fc3c6 in QAction::triggered(bool) () at
/usr/lib64/libQt5Widgets.so.5
#41 0x7f9ace6ff0d7 in QAction::activate(QAction::ActionEvent) () at
/usr/lib64/libQt5Widgets.so.5
#42 0x7f9ace6ffebb in QAction::qt_metacall(QMetaObject::Call, int, void**)
() at /usr/lib64/libQt5Widgets.so.5
#43 0x7f9aca69ccb3 in ??? () at /usr/lib64/libQt5Qml.so.5
#44 0x7f9aca57298d in ??? () at /usr/lib64/libQt5Qml.so.5
#45 0x7f9aca575deb in QV4::QObjectMethod::callInternal(QV4::Value const*,
QV4::Value const*, int) const () at /usr/lib64/libQt5Qml.so.5
#46 0x7f9aca592676 in ??? () at /usr/lib64/libQt5Qml.so.5
#47 0x7f9aca595e7f in ??? () at /usr/lib64/libQt5Qml.so.5
#48 0x7f9aca527e8a in QV4::Fu

[choqok] [Bug 461928] Choquk crashes when I tried to remove accounts

2023-08-30 Thread arran
https://bugs.kde.org/show_bug.cgi?id=461928

--- Comment #1 from arran  ---
I removed some twitter accounts, it crashed every time. Possibly because it was
still refreshing the data.

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

[choqok] [Bug 461928] Choquk crashes when I tried to remove accounts

2023-08-30 Thread arran
https://bugs.kde.org/show_bug.cgi?id=461928

arran  changed:

   What|Removed |Added

Summary|Choquk crashes when I tried |Choquk crashes when I tried
   |to remove Mastodon  |to remove accounts

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

[choqok] [Bug 461928] New: Choquk crashes when I tried to remove Mastodon

2022-11-16 Thread arran
https://bugs.kde.org/show_bug.cgi?id=461928

Bug ID: 461928
   Summary: Choquk crashes when I tried to remove Mastodon
Classification: Applications
   Product: choqok
   Version: 1.7.0
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: scarp...@kde.org
  Reporter: arr...@gmail.com
  Target Milestone: ---

Application: choqok (1.7.0)

Qt Version: 5.15.6
Frameworks Version: 5.98.0
Operating System: Linux 5.19.0-23-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.10
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
I tried to remove the mastodon configuration from Choquk's accounts
configuration page and when I did so the application crashed. I was able to
repeat this every time.

The crash can be reproduced every time.

-- Backtrace:
Application: Choqok (choqok), signal: Segmentation fault

[KCrash Handler]
#4  0x7ffbe5b26472 in QStackedWidget::indexOf(QWidget*) const () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x7ffbe650cd55 in Choqok::UI::ChoqokTabBar::removePage(QWidget*) () at
/lib/x86_64-linux-gnu/libchoqok.so.1
#6  0x7ffbe4cf36ff in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ffbe4cec853 in QObject::destroyed(QObject*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ffbe59aa793 in QWidget::~QWidget() () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7ffbe64e5edd in Choqok::UI::TimelineWidget::~TimelineWidget() () at
/lib/x86_64-linux-gnu/libchoqok.so.1
#10 0x7ffbe4ce55fe in QObjectPrivate::deleteChildren() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7ffbe59aa4b6 in QWidget::~QWidget() () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7ffbe5b260dd in QStackedWidget::~QStackedWidget() () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7ffbe4ce55fe in QObjectPrivate::deleteChildren() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7ffbe59aa4b6 in QWidget::~QWidget() () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7ffbe650d0cb in Choqok::UI::ChoqokTabBar::~ChoqokTabBar() () at
/lib/x86_64-linux-gnu/libchoqok.so.1
#16 0x7ffbe650d23d in Choqok::UI::ChoqokTabBar::~ChoqokTabBar() () at
/lib/x86_64-linux-gnu/libchoqok.so.1
#17 0x7ffbe4ce55fe in QObjectPrivate::deleteChildren() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7ffbe59aa4b6 in QWidget::~QWidget() () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7ffbe64e0cb1 in Choqok::UI::MicroBlogWidget::~MicroBlogWidget() () at
/lib/x86_64-linux-gnu/libchoqok.so.1
#20 0x7ffbe64e0d3d in Choqok::UI::MicroBlogWidget::~MicroBlogWidget() () at
/lib/x86_64-linux-gnu/libchoqok.so.1
#21 0x7ffbe4ce78f3 in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7ffbe596bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7ffbe4cbae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7ffbe4cbdeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7ffbe4d15427 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7ffbe29224f9 in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7ffbe2977228 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7ffbe291fcb0 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7ffbe4d14aea in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7ffbe4cb97cb in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7ffbe4cc1c2a in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x5604e5671933 in  ()
#33 0x7ffbe4223510 in __libc_start_call_main
(main=main@entry=0x5604e5670dc0, argc=argc@entry=3,
argv=argv@entry=0x7ffcc9936408) at ../sysdeps/nptl/libc_start_call_main.h:58
#34 0x7ffbe42235c9 in __libc_start_main_impl (main=0x5604e5670dc0, argc=3,
argv=0x7ffcc9936408, init=, fini=,
rtld_fini=, stack_end=0x7ffcc99363f8) at ../csu/libc-start.c:381
#35 0x5604e5671a4e in _start ()
[Inferior 1 (process 4928) detached]

Reported using DrKonqi

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

[choqok] [Bug 458495] New: Settings save if I press cancel on the settings menu

2022-08-29 Thread arran
https://bugs.kde.org/show_bug.cgi?id=458495

Bug ID: 458495
   Summary: Settings save if I press cancel on the settings menu
   Product: choqok
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: scarp...@kde.org
  Reporter: arr...@gmail.com
  Target Milestone: ---

SUMMARY
Settings save even when I press 'cancel' on the settings dialog.


STEPS TO REPRODUCE
1. Change "Number of posts to show in timeline"
2. CLick cancel
3. Open settings again

OBSERVED RESULT
The value changed

EXPECTED RESULT
Value doesn't change

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-46-generic (64-bit)
Graphics Platform: X11
Processors: 16 × 12th Gen Intel® Core™ i5-12600KF
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3050/PCIe/SSE2

ADDITIONAL INFORMATION
n/a

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

[korganizer] [Bug 457995] I crashed Korganizer by double clicking on the Journal background next to but not on a journal entry

2022-08-17 Thread arran
https://bugs.kde.org/show_bug.cgi?id=457995

--- Comment #2 from arran  ---
You could be right.. It could have been a right as well. I tend to click 
around like a software tester when thinking. So I wasn't exactly paying much 
attention.

On Thursday, 18 August 2022 9:31:14 AM AEST you wrote:
> https://bugs.kde.org/show_bug.cgi?id=457995
> 
> gjditchfi...@acm.org changed:
> 
>What|Removed |Added
> 
> Version|unspecified |5.19.3
>  CC||gjditchfi...@acm.org
> 
> --- Comment #1 from gjditchfi...@acm.org ---
> Weird:  stack frame #10 makes it look like a right-click was involved.
> Please add a note here if it happens again.

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

[korganizer] [Bug 457995] New: I crashed Korganizer by double clicking on the Journal background next to but not on a journal entry

2022-08-17 Thread arran
https://bugs.kde.org/show_bug.cgi?id=457995

Bug ID: 457995
   Summary: I crashed Korganizer by double clicking on the Journal
background next to but not on a journal entry
   Product: korganizer
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: arr...@gmail.com
  Target Milestone: ---

Application: korganizer (5.19.3 (21.12.3))

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-46-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.1 LTS
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I crashed Korganizer by double clicking on the Journal background next to but
not on a journal entry

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault

[KCrash Handler]
#4  0x7fa9606d8b4c in QMetaObject::cast(QObject const*) const () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa957acce5c in QQuickShortcutContext::matcher(QObject*,
Qt::ShortcutContext) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5
#6  0x7fa960ae1480 in QShortcutMap::hasShortcutForKeySequence(QKeySequence
const&) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#7  0x7fa9613bfb9f in QWidgetTextControl::createStandardContextMenu(QPointF
const&, QWidget*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7fa96139557d in QTextEdit::createStandardContextMenu() () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7fa95ee4fca5 in KPIMTextEdit::RichTextEditor::mousePopupMenu(QPoint)
() from /lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3
#10 0x7fa95ee511b6 in
KPIMTextEdit::RichTextEditor::contextMenuEvent(QContextMenuEvent*) () from
/lib/x86_64-linux-gnu/libKF5PimTextEdit.so.5abi3
#11 0x7fa9612024ee in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7fa9612b0422 in QFrame::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7fa9606cfb8a in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7fa9611bf702 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7fa9611c6ca4 in QApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fa9606cfe2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fa96121c4a4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fa96121efd5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fa9611bf713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7fa9606cfe2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7fa960ab6307 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#22 0x7fa960a8ba2c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#23 0x7fa9587b9d6e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#24 0x7fa95ddffd1b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7fa95de546f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7fa95ddfd3c3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7fa9607290a8 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7fa9606ce74b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7fa9606d6ce4 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x560b651280e7 in ?? ()
#31 0x7fa95ffc9d90 in __libc_start_call_main
(main=main@entry=0x560b65127b60, argc=argc@entry=1,
argv=argv@entry=0x7fff0a6e11e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#32 0x7fa95ffc9e40 in __libc_start_main_impl (main=0x560b65127b60, argc=1,
argv=0x7fff0a6e11e8, init=, fini=,
rtld_fini=, stack_end=0x7fff0a6e11d8) at ../csu/libc-start.c:392
#33 0x560b65128495 in ?? ()
[Inferior 1 (process 180219) detached]

Reported using DrKonqi

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2017-02-08 Thread Arran
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #230 from Arran  ---
Hélas, probablement jamais.
Alas, probably never.
Leider, vermutlich nie.

But any Distro run with the Xfce desktop environment does it. Thats now my
choice.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2017-01-30 Thread Arran
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #227 from Arran  ---
(In reply to Nathanael Schilling from comment #224)
> (In reply to Arran from comment #223)
> > As I said before. Xfce does offer exactly this.
> 
> With kwin as the compositor?

I don't give a penny what is is called. And even less who makes it. The only
important thing for me is, that I have again the different Backgrounds on
different Desktops without any twistings, tricks and cheats. Whether this is
based on Plasma or Moon or Hell does not count for me. I am not married with
KDE, not at all. They lured me away from Mint due to exactly the different
backgrounds and now they tell me I am daft to not find Activities attractive.

Best, you try it out for yourself on any of the distros with XFC€.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2017-01-30 Thread Arran
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #223 from Arran  ---
As I said before. Xfce does offer exactly this.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2017-01-06 Thread Arran
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #217 from Arran  ---
Hi Linuxflüsterer
I totally agree with you.
I have realised, that perhaps leaving KDE is (for me) the real future, as I am
all for democracy also in OpenSource products. What we experience since more
than 10 years from KDE is a blatant dictatorship. I have found out that «xfce»
can do all that, what I wanted. Out of the Box. I'm just a bit too busy and
have the outlook that by end of the month I have a fast internet connection
(about 70+) I then will change to installing a distribution with xfce.
And then, KDE kann mir die Hosen herabrutschen und gestohlen bleiben.

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2016-11-30 Thread Arran
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #210 from Arran  ---
I don't care any longer if this negative aspect to KDE's clients, the users,
continues. I have found PClinuxOS with Trinity as desktop environment. It bases
on KDE used before the first Plasma, but steadily developed to keep up to their
users demands. I am now, after a short trial of 2 weeks, prepared to install it
as my new bread and butter distribution and I do not have to bother with KDE
any more. What a releave.

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

[dolphin] [Bug 364956] Add option to keep music/video preview, when mouse hover somewhere else

2016-09-25 Thread Arran via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364956

Arran  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Arran  ---
*** This bug has been confirmed by popular vote. ***

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


[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2016-07-05 Thread Arran via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #191 from Arran  ---
Thanks for the flowers (Danke für die Blumen), linuxflüsterer. What really
brought 
my temper to overflow, the doctor racing home and sedating me for four days,
was 
the moment I was told, that the Xfce desktop has done that feature in a couple
of 
weaks, after read the first comments here. I don't have much time until
September, 
but then, unless...» I swith to Xubuntu.


Am 05.07.2016 um 12:59 schrieb linuxfluesterer via KDE Bugzilla:
> https://bugs.kde.org/show_bug.cgi?id=341143
>
> --- Comment #190 from linuxfluesterer  ---
> (In reply to loop.rw from comment #189)
>> Ok guys, please stop useless bashing of the devs. While I also am impatient
>> to see the features back, I realize it is not a trivial matter but actually
>> a quite complex architectural change. David said they are working on it so
>> please be patient.
>>
>> As a side note however it is becoming more difficult updating different
>> systems ...
>
> Hmm, ok, the fundament of Plasma 5 may be more difficult than the one of 
> KDE...
> But only if the fundament is well, the building can should be started. I will
> not offend any dev here, but maybe Plasma could be compared with our German
> airport BER, an absolute desaster and in the end nobody is really content.
> I agree to Arran (com ment 188), who said:
>> Just on afterthought: this situation resembles the European Union. If a 
>> majority
>> of the EU-PARLIAMENT (min. 376 MEPs) make by vote a decision, this result 
>> has no
>> binding value to the 28 Commissars nor to the 28 head of States. They can 
>> decide
>> whatever they want. Democracy at its best???
> I am rather sure, Plasma devs could have prevented this trouble situation.
> As I said before, I am still using KDE version 4.14.10. Anyway, lost time for
> every Plasma users, who have a serious demand for lost features (and, much 
> more
> important, broken functions!).
>
> -Linuxfluesterer
>

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2016-07-03 Thread Arran via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #188 from Arran  ---
After a two-year try to convince the developers, I have to state this is no
longer 
a Bug.
Instead it has become battle between an group of developers who wants to
develop 
what they want and hundred of millions of users.

KDE post plasma 4.x is now definitively not on my fare and I suppose even with
a 
plasma 6 I shall never return. Xubuntu (Xfce desktop) can do it, so I am
switching 
to them, well knowing, that I loose some dear routines.  other Distros have a 
Xfce-Desktop version too. So, why get heated about something we can not
influence 
due to sort of «Chinese Stubbornness» of the producers side. If Mercedes would 
suddenly only build three-wheel-cars, they would very soon realise, the regular 
customer find valuable alternatives (Audi, Jaguar, Chryslers, etc) and get 
financially bankrupt. In this case the result will be, that less and less users 
will use KDE.

That's my last post in this depressing discussion.

Bye to all, you disregarded Users and arrogant Developers. Stay happy and use
Linux.

Just on afterthought: this situation resembles the European Union. If a
majority 
of the EU-PARLIAMENT (min. 376 MEPs) make by vote a decision, this result has
no 
binding value to the 28 Commissars nor to the 28 head of States. They can
decide 
whatever they want. Democracy at its best???





Am 03.07.2016 um 08:13 schrieb eddy.pilon via KDE Bugzilla:
> https://bugs.kde.org/show_bug.cgi?id=341143
>
> --- Comment #187 from eddy.pilon  ---
> (In reply to Danny Tamez from comment #183)
>> Created attachment 99805 [details]
>> attachment-564-0.html
>>
>> Well this totally sucks
>> On Jan 11, 2016 2:49 PM, "eddy.pilon via KDE Bugzilla" <
>> bugzilla_nore...@kde.org> wrote:
>>
>>> https://bugs.kde.org/show_bug.cgi?id=341143
>>>
>>> --- Comment #164 from eddy.pilon  ---
>>> Perhaps a work-around ?
>>> I've assigned  to each activitie the same number of virtual desktop in
>>> kactivitymanagerd-pluginrc.
>>> Now  i've  desktop number, cube effect  with different  wallpapers and
>>> widgets
>>> with the activitypager like vds.
>>> Look 's weird.
>>>
>>> --
>>> You are receiving this mail because:
>>> You are on the CC list for the bug.
>>>
>
> Sorry, my english is light and don't really understand what you want to say by
> " Well this totally sucks" !!
> I just wanted to say that since my distro switch to plasma5  i've had enough 
> to
> wait and tried my wallpapers and cube effect  to come back with config files.
> But i understand you .
> My distro just switched to plasma 5.7,  same issue and no commits about this
> bug.
>

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2016-07-02 Thread Arran via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #182 from Arran  ---
Hi aschne. The small desktop Xfce can do that. I too have given up any hope to
be able to use the once worlds best Desktop again, as I would have liked. Try
it with Manjaro Xfce, this is light Distrubution, or to continue with the
Goodies from *buntu, install Xubuntu. You can also install Xfce over your
14.04, I think. however, I did not dare to try it on my working program. If you
speak German, join us with www.kubuntusers.de

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


[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2016-01-04 Thread Arran via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #158 from Arran  ---
Maybe or maybe not. But with over 150 comments this bug report has mutated as
such.

And just to the idea of some developers to act in their own playbox, what with
the thousands of users like me who often support KDE with a financial
contribution? Would we not count as «Clients»? Despite my frustration of Plasma
5 I have continued with my contributions in 2015, but I do reserve to change my
opinion if I will be continuedly apostrophed as a «Take-what-We-give-you, be
thankful for that and keep quiet». 

(In reply to Germano Massullo from comment #156)
> This is not a place for discussions, use the development mailing list
> instead.
> Thank you

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2016-01-04 Thread Arran via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #157 from Arran  ---
Maybe or maybe not. But with over 150 comments this bug report has mutated as
such.

And just to the idea of some developers to act in their own playbox, what with
the thousands of users like me who often support KDE with a financial
contribution? Would we not count as «Clients»? Despite my frustration of Plasma
5 I have continued with my contributions in 2015, but I do reserve to change my
opinion if I will be continuedly apostrophed as a «Take-what-We-give-you, be
thankful for that and keep quiet». 

(In reply to Germano Massullo from comment #156)
> This is not a place for discussions, use the development mailing list
> instead.
> Thank you

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2016-01-03 Thread Arran via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341143

--- Comment #153 from Arran  ---
Just back from a very wet and rainy Scotland Highland (mostly indoors) week. We 
all had laptops and I convinced three friends to change to KDE (Kubuntu 4.04).
1 
Windows, 1 Fedora and one Ubuntu users.
The deciding USP's I used were the various Desktop backgrounds (all three), 
KMyMoney (1), digiKam (1). The big runner was definitively the different
backgrounds.
I told them all about the present situation of incertainity and to have to use
the 
14.04 LTS and explained in depth the use of the PPA system. 3 more were sort of 
interested, but a bit disappointed that with Plasma 5 it will no longer be 
available; I think they will not change. The last 3 did were happy with what
they 
had. Altogether we had 4 Linux, four Windows and 2 Apples (unsurprisingly for
me 
none of them wants to change).

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