[Akonadi] [Bug 479342] Akonadi server crashed.

2024-01-04 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=479342

--- Comment #2 from Attila  ---
Hi, I apologise for the duplicates. It was not my intention to create
duplicates over and over again. It is a bug in DrKonqi. When I press the
"submit" button, I see the spinning wheel. There is no confirmation that the
bug report has been sent.
So I took a step back and pressed the "submit" button again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 479344] New: Akonadi server crashed.

2024-01-02 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=479344

Bug ID: 479344
   Summary: Akonadi server crashed.
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadiserver (5.24.3 (23.08.3))

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.6.6-100.fc38.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 38 (KDE Plasma)"
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
I deleted emails one after the other and suddenly the akonadi server crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault

[KCrash Handler]
#4  0x561884ebd803 in Akonadi::Server::Connection::slotSendHello() ()
#5  0x561884ebe0d7 in Akonadi::Server::Connection::init() ()
#6  0x561884eba45a in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) ()
#7  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#8  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#9  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#10 0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#11 0x7fc55c1134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#12 0x7fc55c1716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#13 0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#14 0x7fc55dd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#15 0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#16 0x7fc55daf4750 in QThread::exec() () from /lib64/libQt5Core.so.5
#17 0x7fc55daf5b5d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#18 0x7fc55d4ae947 in start_thread () from /lib64/libc.so.6
#19 0x7fc55d534860 in clone3 () from /lib64/libc.so.6

Thread 34 (Thread 0x7fc4adffb6c0 (LWP 16829) "0x561885140d70-"):
#1  0x7fc55c171629 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc55dd06af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x561884ec201c in Akonadi::Server::Connection::handleIncomingData() ()
#6  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#9  0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#10 0x7fc55c1134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#11 0x7fc55c1716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#12 0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#13 0x7fc55dd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#14 0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#15 0x7fc55daf4750 in QThread::exec() () from /lib64/libQt5Core.so.5
#16 0x7fc55daf5b5d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#17 0x7fc55d4ae947 in start_thread () from /lib64/libc.so.6
#18 0x7fc55d534860 in clone3 () from /lib64/libc.so.6

Thread 33 (Thread 0x7fc4a6c0 (LWP 16199) "0x561885196c70-"):
#1  0x7fc55c171629 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc55dd06af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x561884ec201c in Akonadi::Server::Connection::handleIncomingData() ()
#6  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#9  0x7fc55dd06fef in 

[kmail2] [Bug 479343] New: Akonadi server crashed

2024-01-02 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=479343

Bug ID: 479343
   Summary: Akonadi server crashed
Classification: Applications
   Product: kmail2
   Version: 5.24.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

Application: akonadiserver (5.24.3 (23.08.3))

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.6.6-100.fc38.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 38 (KDE Plasma)"
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
I deleted emails one after the other and suddenly the akonadi server crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault

[KCrash Handler]
#4  0x561884ebd803 in Akonadi::Server::Connection::slotSendHello() ()
#5  0x561884ebe0d7 in Akonadi::Server::Connection::init() ()
#6  0x561884eba45a in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) ()
#7  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#8  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#9  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#10 0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#11 0x7fc55c1134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#12 0x7fc55c1716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#13 0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#14 0x7fc55dd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#15 0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#16 0x7fc55daf4750 in QThread::exec() () from /lib64/libQt5Core.so.5
#17 0x7fc55daf5b5d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#18 0x7fc55d4ae947 in start_thread () from /lib64/libc.so.6
#19 0x7fc55d534860 in clone3 () from /lib64/libc.so.6

Thread 34 (Thread 0x7fc4adffb6c0 (LWP 16829) "0x561885140d70-"):
#1  0x7fc55c171629 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc55dd06af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x561884ec201c in Akonadi::Server::Connection::handleIncomingData() ()
#6  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#9  0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#10 0x7fc55c1134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#11 0x7fc55c1716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#12 0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#13 0x7fc55dd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#14 0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#15 0x7fc55daf4750 in QThread::exec() () from /lib64/libQt5Core.so.5
#16 0x7fc55daf5b5d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#17 0x7fc55d4ae947 in start_thread () from /lib64/libc.so.6
#18 0x7fc55d534860 in clone3 () from /lib64/libc.so.6

Thread 33 (Thread 0x7fc4a6c0 (LWP 16199) "0x561885196c70-"):
#1  0x7fc55c171629 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc55dd06af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x561884ec201c in Akonadi::Server::Connection::handleIncomingData() ()
#6  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#9  0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#10 

[Akonadi] [Bug 479342] New: Akonadi server crashed.

2024-01-02 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=479342

Bug ID: 479342
   Summary: Akonadi server crashed.
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadiserver (5.24.3 (23.08.3))

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.6.6-100.fc38.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 38 (KDE Plasma)"
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
I deleted emails one after the other and suddenly the akonadi server crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault

[KCrash Handler]
#4  0x561884ebd803 in Akonadi::Server::Connection::slotSendHello() ()
#5  0x561884ebe0d7 in Akonadi::Server::Connection::init() ()
#6  0x561884eba45a in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) ()
#7  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#8  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#9  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#10 0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#11 0x7fc55c1134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#12 0x7fc55c1716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#13 0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#14 0x7fc55dd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#15 0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#16 0x7fc55daf4750 in QThread::exec() () from /lib64/libQt5Core.so.5
#17 0x7fc55daf5b5d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#18 0x7fc55d4ae947 in start_thread () from /lib64/libc.so.6
#19 0x7fc55d534860 in clone3 () from /lib64/libc.so.6

Thread 34 (Thread 0x7fc4adffb6c0 (LWP 16829) "0x561885140d70-"):
#1  0x7fc55c171629 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc55dd06af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x561884ec201c in Akonadi::Server::Connection::handleIncomingData() ()
#6  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#9  0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#10 0x7fc55c1134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#11 0x7fc55c1716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#12 0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#13 0x7fc55dd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#14 0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#15 0x7fc55daf4750 in QThread::exec() () from /lib64/libQt5Core.so.5
#16 0x7fc55daf5b5d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#17 0x7fc55d4ae947 in start_thread () from /lib64/libc.so.6
#18 0x7fc55d534860 in clone3 () from /lib64/libc.so.6

Thread 33 (Thread 0x7fc4a6c0 (LWP 16199) "0x561885196c70-"):
#1  0x7fc55c171629 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc55dd06af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x561884ec201c in Akonadi::Server::Connection::handleIncomingData() ()
#6  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#9  0x7fc55dd06fef in 

[Akonadi] [Bug 479341] New: Akonadi server crashed.

2024-01-02 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=479341

Bug ID: 479341
   Summary: Akonadi server crashed.
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadiserver (5.24.3 (23.08.3))

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.6.6-100.fc38.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 38 (KDE Plasma)"
DrKonqi: 5.27.9 [KCrashBackend]

-- Information about the crash:
I deleted emails one after the other and suddenly the akonadi server crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault

[KCrash Handler]
#4  0x561884ebd803 in Akonadi::Server::Connection::slotSendHello() ()
#5  0x561884ebe0d7 in Akonadi::Server::Connection::init() ()
#6  0x561884eba45a in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) ()
#7  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#8  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#9  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#10 0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#11 0x7fc55c1134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#12 0x7fc55c1716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#13 0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#14 0x7fc55dd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#15 0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#16 0x7fc55daf4750 in QThread::exec() () from /lib64/libQt5Core.so.5
#17 0x7fc55daf5b5d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#18 0x7fc55d4ae947 in start_thread () from /lib64/libc.so.6
#19 0x7fc55d534860 in clone3 () from /lib64/libc.so.6

Thread 34 (Thread 0x7fc4adffb6c0 (LWP 16829) "0x561885140d70-"):
#1  0x7fc55c171629 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc55dd06af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x561884ec201c in Akonadi::Server::Connection::handleIncomingData() ()
#6  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#9  0x7fc55dd06fef in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#10 0x7fc55c1134fc in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#11 0x7fc55c1716b8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#12 0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#13 0x7fc55dd06ad9 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#14 0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#15 0x7fc55daf4750 in QThread::exec() () from /lib64/libQt5Core.so.5
#16 0x7fc55daf5b5d in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#17 0x7fc55d4ae947 in start_thread () from /lib64/libc.so.6
#18 0x7fc55d534860 in clone3 () from /lib64/libc.so.6

Thread 33 (Thread 0x7fc4a6c0 (LWP 16199) "0x561885196c70-"):
#1  0x7fc55c171629 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc55c110b83 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc55dd06af6 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fc55dcb2efb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x561884ec201c in Akonadi::Server::Connection::handleIncomingData() ()
#6  0x7fc55dcdf0bb in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#7  0x7fc55dcb451b in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#8  0x7fc55dcb79e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#9  0x7fc55dd06fef in 

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2023-12-10 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

Attila  changed:

   What|Removed |Added

Version|5.24.1  |5.24.3

--- Comment #34 from Attila  ---
KMail version 5.24.3 (23.08.3) has been released for Fedora 38.
No changes, the bug is still present.

I get a plenty of messages like "Unable to fetch item from backend (collection
-1): Unable to retrieve item from resource:  [LRCONFLICT] Resource
akonadi_maildir_resource_0 tries to modify item 319216 () (in collection 24)
with dirty payload, aborting STORE".

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2023-11-10 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

Attila  changed:

   What|Removed |Added

Version|5.23.1  |5.24.1

--- Comment #33 from Attila  ---
KMail version 5.24.1 (23.08.1) has been released for Fedora 38.
No changes, the bug is still present.

I get a plenty of messages like "Unable to fetch item from backend (collection
-1): Unable to retrieve item from resource:  [LRCONFLICT] Resource
akonadi_maildir_resource_0 tries to modify item 319216 () (in collection 24)
with dirty payload, aborting STORE".

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2023-07-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #32 from Attila  ---
I get a plenty of messages like "Item query returned empty result set". It
doesn't matter how many times I click on these new mails, they remain marked as
new mail. I hate to say but KMail is not suitable for daily use.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2023-06-30 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #31 from Attila  ---
KMail version 5.23.1 (23.04.1) has been released for Fedora 38.
No changes, the bug is still present.

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Graphics Platform: X11

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2023-06-30 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

Attila  changed:

   What|Removed |Added

Version|5.22.0  |5.23.1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 468382] New: KMail crashes when deleting a new e-mail.

2023-04-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=468382

Bug ID: 468382
   Summary: KMail crashes when deleting a new e-mail.
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

Application: kmail (5.22.3 (22.12.3))

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.9-200.fc37.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora release 37 (Thirty Seven)"
DrKonqi: 5.27.3 [KCrashBackend]

-- Information about the crash:
Clicking on delete new e-mail caused a crash. I am not sure if the error is
reproducible.

The reporter is unsure if this crash is reproducible.

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

[KCrash Handler]
#4  0x7f11c9231032 in KMime::Content::headerByType(char const*) const ()
from /lib64/libKF5Mime.so.5
#5  0x7f11c9231eee in KMime::Content::contentTransferEncoding(bool) () from
/lib64/libKF5Mime.so.5
#6  0x7f11c9232f7f in KMime::ContentPrivate::decodeText(KMime::Content*) ()
from /lib64/libKF5Mime.so.5
#7  0x7f11c92330bb in KMime::Content::decodedText(bool, bool) () from
/lib64/libKF5Mime.so.5
#8  0x7f11c9911bb5 in
MimeTreeParser::ObjectTreeParser::extractNodeInfos(KMime::Content*, bool) ()
from /lib64/libKF5MimeTreeParser.so.5
#9  0x7f11c9913a48 in
MimeTreeParser::ObjectTreeParser::parseObjectTree(KMime::Content*, bool) ()
from /lib64/libKF5MimeTreeParser.so.5
#10 0x7f11c9c9c3dc in
MessageViewer::ViewerPrivate::parseContent(KMime::Content*) () from
/lib64/libKF5MessageViewer.so.5
#11 0x7f11c9ca8f21 in MessageViewer::ViewerPrivate::updateReaderWin() ()
from /lib64/libKF5MessageViewer.so.5
#12 0x7f11caad0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#13 0x7f11c98f7382 in
MimeTreeParser::NodeHelper::update(MimeTreeParser::UpdateMode) () from
/lib64/libKF5MimeTreeParser.so.5
#14 0x7f11caad0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#15 0x7f11c9916cd8 in
MimeTreeParser::VerifyDetachedBodyPartMemento::slotKeyListJobDone() () from
/lib64/libKF5MimeTreeParser.so.5
#16 0x7f11caad0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#17 0x7f11c9421b29 in QGpgME::_detail::ThreadedJobMixin >, QString, GpgME::Error> >::slotFinished() () from
/lib64/libqgpgme.so.7
#18 0x7f11caac8134 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#19 0x7f11cb7aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#20 0x7f11caa9d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#21 0x7f11caaa0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#22 0x7f11caaeeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#23 0x7f11c43a7c7f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#24 0x7f11c43fe118 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#25 0x7f11c43a4f00 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#26 0x7f11caaee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#27 0x7f11caa9bf3a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#28 0x7f11caaa4002 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#29 0x5572da4dfdbf in main ()
[Inferior 1 (process 129056) detached]

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 468173] New: Sent e-mail appears in outbox

2023-04-05 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=468173

Bug ID: 468173
   Summary: Sent e-mail appears in outbox
Classification: Applications
   Product: kmail2
   Version: 5.22.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY

Some e-mails which are sent, appear in the folder outbox. A click on the e-mail
shows a message in the status bar like: Item query returned empty result set.

STEPS TO REPRODUCE
1. Launch KMail
2. Write a new e-mail
3. Send the e-mail and wait until it has been sent
4. Navigate to the folder outbox
5. Click on the e-mail which is already sent

OBSERVED RESULT
The status bar shows the message: Item query returned empty result set.

EXPECTED RESULT
E-mails that are sent should not appear in the folder outbox.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4600

ADDITIONAL INFORMATION
This bug is perhaps not always reproducible. It happened for the first time,
but the message "Item query returned empty result set" comes up every day when
I click on new e-mails to read them.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 467607] New: Filtered E-Mails appear twice

2023-03-20 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=467607

Bug ID: 467607
   Summary: Filtered E-Mails appear twice
Classification: Applications
   Product: kmail2
   Version: 5.22.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY

New E-Mails which are filtered appear twice when they moved to the specified
folder.
If I click on the first one, KMail displays the content of the E-Mail
correctly.
If I click on the second one, KMail does not display any content, i.e. I see an
empty E-Mail.

STEPS TO REPRODUCE
1. Launch KMail
2. Add a new Subfolder
3. Set up a rule for the filter
4. Check the new E-Mails in the subfolder

OBSERVED RESULT
Some of the new E-Mails appear twice.

EXPECTED RESULT
New E-Mails which are filtered should appear once.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.1.18-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz

ADDITIONAL INFORMATION
I use POP3 to retrieve E-Mails. The filter is super slow. It takes several
minutes to filter 100 new E-Mails. The rules are very simple. It is advisable
not to use Kmail while the E-Mails are being filtered to avoid errors.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2023-01-25 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

Attila  changed:

   What|Removed |Added

Version|5.7.1   |5.22.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2023-01-13 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #30 from Attila  ---
KMail version 5.22.0 (22.12.0) has been released for Fedora 36.
No changes, the bug is still present.

Operating System: Fedora Linux 36
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Graphics Platform: X11

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2022-11-21 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #26 from Attila  ---
Created attachment 153936
  --> https://bugs.kde.org/attachment.cgi?id=153936=edit
Greyed out line for new email

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2022-11-21 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #25 from Attila  ---
I was curious and wanted to see how long KMail takes to get the job done when
the popup window appears with "Please wait for the message to be transmitted".
I gave it up after 4 hours and pressed the "Cancel" button.
I hate to say but this is super frustrating.
By the way an attachment, to show greyed out lines for new email which are
already deleted. This lines are not accessible.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2022-11-20 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #23 from Attila  ---
This bug is still not fixed.
KMail on Fedora 36 with pop3 is pretty bugy.
I guess it has something to do with the "filter" function. I have a setup with
very simple filter rules. The filter takes a very long time to apply the rules
and sort the new emails into the correct subfoleder. My experience is not to
touch KMail while the filter function processing new emails. The filter is
pretty slow and takes 5 to 10 minutes for let's say 100 emails. The filter sort
sometimes a new email twice into the subfolder. One is readable and the other
is empty. Sometimes when I click on a new email, the email is still marked as
new and sometimes I have to click 3 times on delete to delete an email and I
see many times the popup "Please wait for the message to be transmitted".
All this is really frustrating. Can someone please take a look?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kdelibs] [Bug 198172] printer margin settings are forgotten at restart

2022-08-18 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=198172

Attila  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Ever confirmed|1   |0
 Status|NEEDSINFO   |REPORTED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kdelibs] [Bug 198172] printer margin settings are forgotten at restart

2022-08-02 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=198172

--- Comment #19 from Attila  ---
Hi,

this bug has not been fixed since 2009. I know only one application which can
remember the printer margin settings. This is KWrite and perhaps Kate. KWrite
stores this information in the file "kwriterc" in the section [Kate Print
Settings][Margins].
Can someone please finally fix this bug?

Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.2
Kernel Version: 5.18.13-100.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4600

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 422095] Bad printout quality of kmail

2022-06-13 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=422095

--- Comment #6 from Attila  ---
(In reply to Kevin Kofler from comment #5)
> Printing to a real printer still sends a bitmap to the printer. As I wrote:
> 
> > For output to a physical printer, the only way to avoid the rasterization 
> > is to use the FilePrinter class from Okular though. Falkon used to do that 
> > (I had submitted that code back when the QtWebEngine did not have the print 
> > method at all, only printToPdf), but switched to using the print method for 
> > physical printers.
> 
> What QtWebEngine cannot do is print directly to a QPrinter. The Chromium
> code can only output PDFs. Then you have to get that PDF to the printer
> somehow. How QtWebEngine does it is that it renders the PDF to a pixmap
> using the PDFium library that happens to be bundled with Chromium and then
> sends that pixmap to the printer. How Okular prints PDFs (and how Falkon
> used to do it at the beginning) is that it runs the lpr CLI command to send
> the PDF to the printer. The main difficulty with that is that you have to
> translate settings such as margins or page orientation or they will just get
> ignored, and that it also only works with printers that lpr knows about
> (e.g., you cannot print to PDF with that approach).

Hi,

thank you for the explanation from the developer's point of view.
This is from the user's point of view not satisfying. The printout of e-mails
with embedded messages is even worse. The output is very blurred and almost not
readable. I think nothing is impossible in the world of IT, so there must be a
solution for this issue.
My workaround is to export e-mails to PDF, open them with Okular and print
them. This is not really cool. It is a bad user experience.

Please try to find a way to bring the print functionality back with no
rasterization.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 422095] Bad printout quality of kmail

2022-06-10 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=422095

Attila  changed:

   What|Removed |Added

 CC||bugs.kde.att...@online.de

--- Comment #4 from Attila  ---
Hi,

printing to PDF file is OK. The PDF file has real "text" and fonts are
embedded. This has been fixed.

Printing to a real printer produces blurred text. The quality is very poor and
the text is not easy to read. Can someone please take a look at this. KMail
Version 5.19.2 (21.12.2).

Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.17.11-200.fc35.x86_64 (64-bit)
Graphics Platform: X11

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2022-05-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #22 from Attila  ---
This bug is unfortunately not fixed.
I see every day the message "Unable to fetch item from backend ..." on Fedora
35.
There is some more weird behaviour.

Let's say I delete 20 new e-mails one after the other (click on the icon
"delete"), then this e-mails are still marked as new mails.
After that I click on the same 20 e-mails one after the other, then they are
marked as read.
After that I click on the same 20 e-mails one after the other, then they are
finally deleted.

So sorry to say, but this bug is pretty annoying and a bad user experience.
Can someone please inspect this bug and fix it?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-12-10 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #21 from Attila  ---
Created attachment 144419
  --> https://bugs.kde.org/attachment.cgi?id=144419=edit
Journalctl Akonadi Failed to open external payload

Here is some more:

akonadi_indexing_agent[3259]: org.kde.pim.akonadicore: Failed to open external
payload: "/home/aerdelyi/.local/share/akonadi/file_db_data/62/731662_r0" "No
such file or directory"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-12-08 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #20 from Attila  ---
Created attachment 144382
  --> https://bugs.kde.org/attachment.cgi?id=144382=edit
Journalctl Index is not within range

Hi,

@Raúl: Thanks again for your thoughts in comment #19.

A litte warning window came up today with the message: "Please wait for the
message to be transmitted." I can wait for hours and the window will not
disappear. I have to click on "Cancel".

Today I have discovered some new lines from journalctl:

akonadi_maildir_resource[3184]: org.kde.pim.libmaildir: Maildir::readEntry
unable to find:  "1638978596336.R472.myhostname:2,S"

and

kmail[3087]: kf.xmlgui: Index  415  is not within range (0 -  21 )

Sure "Index  415  is not within range (0 -  21 )" but how can this happen?
What a nasty bug, isn't it?

Regards

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-12-07 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #18 from Attila  ---
Created attachment 144299
  --> https://bugs.kde.org/attachment.cgi?id=144299=edit
Journalctl Akonadi timeout writing into stream

Here is another example. This time with:

"org.kde.pim.akonadiserver: NotificationSubscriber for "MailFilterItemMonitor -
94414111761152" : timeout writing into stream"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-12-06 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #17 from Attila  ---
Created attachment 144297
  --> https://bugs.kde.org/attachment.cgi?id=144297=edit
SHOW ENGINE INNODB STATUS

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-12-06 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #16 from Attila  ---
Created attachment 144296
  --> https://bugs.kde.org/attachment.cgi?id=144296=edit
Journalctl Akonadi

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-12-06 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #15 from Attila  ---
Hi Raúl,

thank you very much for your explanation. That was very helpfull.

I can see in the log a line like:
"Deadlock found when trying to get lock; try restarting transaction QMYSQL3:
Unable to execute statement"

"SHOW ENGINE INNODB STATUS" throws me lines out (see also attachments):
LATEST DETECTED DEADLOCK

2021-12-07 08:24:45 0x7fde283ff640
*** (1) TRANSACTION:
TRANSACTION 4390340, ACTIVE 0 sec starting index read
mysql tables in use 6, locked 6

Regards

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-12-01 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #13 from Attila  ---
(In reply to Raúl from comment #11)
> Could you please, confirm if this is a dupe of
> https://bugs.kde.org/show_bug.cgi?id=434706
> 
> In order to confirm, you would need to use mariadb/mysql client and check
> out the transaction status are described in there.
> 
> Regards,

Hi Raúl,

can you please response to my comment #12. I would like to confirm if I know
how.
One thing I would like to mention and please don't get me wrong. This bug has
been reported since more than 3 years. KMail doesn't work properly for
pop3-accounts. For example I have deleted a couple of new emails. They were
marked as read but not deleted and after 10 or more seconds they were really
deleted and gone from my inbox. Some messages came up with "Please wait ..."
inbetween.

Regards

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-11-02 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #12 from Attila  ---
Thank you for your quick reply.
I would like to confirm if this is a dupe of
https://bugs.kde.org/show_bug.cgi?id=434706, but to be honest I don't know how.
The description in there is not detailed enough to me. Sorry I am a user.
Could you please give me in short form the instruction?
I am very interested in a fix for this bug and would like to provide the
information you need.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 444586] New: Message "please wait" comes up when deleting emails

2021-10-29 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=444586

Bug ID: 444586
   Summary: Message "please wait" comes up when deleting emails
   Product: kmail2
   Version: 5.16.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

Created attachment 142990
  --> https://bugs.kde.org/attachment.cgi?id=142990=edit
Message "please wait"

SUMMARY
When I delete emails too fast in a row, a message "please wait ... Please wait
for the message to be transmitted" come up. As more emails I delete as more
messages come up. None of this messages will disappear until I click on
"cancel".
I use POP3. 

STEPS TO REPRODUCE
1. Launch KMail
2. Retrieve emails
3. Delete new emails fast in a row (use the trash icon for "Shift+Del")


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
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.13-200.fc34.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-10-27 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #10 from Attila  ---
As far as I can see, this bug effects only "subfolders" of the "local folder".
I have set up some filter. After new e-mails are sorted to the "subfolders",
many of them appear twice. Click on the first one shows an empty e-mail (this
is wrong) and the second shows the new e-mail correct. When I click on the
first e-mail again I get the message in the status bar: 

Unable to fetch item from backend  with dirty payload

It doesn't happen on my "inbox". So I think it is affected to the "subfolders"
and has something to do with filters.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 434132] Text on HTML-"buttons" invisible

2021-10-18 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=434132

--- Comment #6 from Attila  ---
Thank you for your quick reply. Indeed the checkbox "do not change color from
origin html" wasn't ticked. That fixes the issue.

Shouldn't the checkbox be ticked by default to avoid incorrect display on the
screen?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-10-18 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #9 from Attila  ---
The bug still exists on Fedora 34, KMail 5.16.2, Akonadi 5.16.2 (20.12.2).
Can someone please take a look at this bug?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 434132] Text on HTML-"buttons" invisible

2021-10-18 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=434132

--- Comment #4 from Attila  ---
The bug still exists on Fedora 34, KMail 5.16.2.
Can someone please take a look at this bug?
It is a bad user experience when E-Mails are not displayed correct and
therefore the user can't read them.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 434132] Text on HTML-"buttons" invisible

2021-04-29 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=434132

--- Comment #3 from Attila  ---
Can someone please take a look at this?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 434132] Text on HTML-"buttons" invisible

2021-03-15 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=434132

--- Comment #2 from Attila  ---
Additional information:

The "modern" button is a square with a color and a text inside. The text is a
link ().
This and any other color is ignored by KMail and is always overwritten by
"#2980B9". Is "#2980B9" the default color for links?
This is only affacted to HTML-Tag .
Hopefully it is not a big deal to fix it, is it?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415056] Kmail pretends to be done retrieving emails

2021-03-15 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415056

--- Comment #6 from Attila  ---
Could this be caused by "baloo_file_extractor"? When I read very large emails,
I notice that the process "baloo_file_extractor" eats up to 1.5 GB of RAM.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415056] Kmail pretends to be done retrieving emails

2021-03-15 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415056

Attila  changed:

   What|Removed |Added

Version|5.11.3  |5.15.3

--- Comment #5 from Attila  ---
I get the message "Item query returned empty result set" on Fedora 33 as well.
This happens when I have got a plenty of new emails in my inbox and I delete
them quick email by email.

KMail version 5.15.3 (20.08.3).

Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-200.fc33.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2021-03-12 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #8 from Attila  ---
I still get this message often (see comment 3).

KMail version 5.15.3 (20.08.3).

Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-200.fc33.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 434132] Text on HTML-"buttons" invisible

2021-03-08 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=434132

--- Comment #1 from Attila  ---
Created attachment 136479
  --> https://bugs.kde.org/attachment.cgi?id=136479=edit
Text on button highlighted

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 434132] New: Text on HTML-"buttons" invisible

2021-03-08 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=434132

Bug ID: 434132
   Summary: Text on HTML-"buttons" invisible
   Product: kmail2
   Version: 5.15.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

Created attachment 136478
  --> https://bugs.kde.org/attachment.cgi?id=136478=edit
Text on button invisible

SUMMARY
The text on "modern" buttons is invisible in almost every HTML-formatted
e-mail. I have to higlight the text by mouse to be able to read the text on
those buttons (see attachments).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-200.fc33.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2021-02-02 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #48 from Attila  ---
(In reply to Wolfgang Bauer from comment #42)
> (In reply to Attila from comment #41)
> > Firefox can display this e-mail within 2 seconds and I can scroll very
> > smooth through  the content by dragging the scrollbar.
> Have you tried in Chromium though? (which is what QtWebEngine is based upon)

I have tried Google Chrome today. It is comparable to Firefox. Chrome displays
the same e-mail in 2 seconds. There is just one difference. Chrome takes 15
seconds more to scroll down to the bottom of the e-mail. This would be
acceptable as well. Chrome eats 347.676 K. This is not bad, is it?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2021-02-01 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #41 from Attila  ---
(In reply to RJVB from comment #39)
> A pure text email of 35Mb is massive too, but eating around 4Gb of RAM for
> that isn't just massive. That's what you meant, right, not 4Mb for
> displaying just the part that fits in your window (which would seem
> reasonable)? 4Gb, that's about 120 times the size of the email.

Yes I mean 4.317.684 K (QtWebEngineProcess).

> I knew KMail would become a powerkids' tool with the design decision to use
> a full-fledged-browser-in-a-widget (QtWebEngine) for rendering everything
> including pure text emails but I wasn't expecting this. Then again, I don't
> usually get this kind of long letters by email so I have no idea how any
> other MUA would handle them.

I get this kind of long emails every day. This is the output from backup
scripts executed by Cron.

> If the account you got this email on has a web/browser interface it would be
> interesting to estimate the resources an actual browser (GChrome or
> Chromium) would use to display it, for comparison.

Unfortunately this account doesn't have a Web-Interface, but I did a test on
another account with Web-Interface.
The plain text has a size of 20 MiB.

In Comparison:
QtWebEngineProcess (KMail) is eating 1.609.232 K.
Firefox (Web-Interface) is eating 156.204 K.

Firefox can display this e-mail within 2 seconds and I can scroll very smooth
through  the content by dragging the scrollbar.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2021-01-27 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #38 from Attila  ---
Additional information:

I have observed the system activity today by opening an ASCII-email by the size
of 35 MB. The application "System Activity" shows me a CPU usage of 13%
(QtWebEngineProcess) and RAM consumption of 4.317.684 K. I think this is
massive, isn't it? Scrolling through the email is almost impossible.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 431921] Black square appears sometimes in KMail

2021-01-22 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=431921

--- Comment #2 from Attila  ---
Created attachment 135057
  --> https://bugs.kde.org/attachment.cgi?id=135057=edit
Black square 2

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 431921] Black square appears sometimes in KMail

2021-01-22 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=431921

--- Comment #1 from Attila  ---
Created attachment 135056
  --> https://bugs.kde.org/attachment.cgi?id=135056=edit
Black square 1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 431921] New: Black square appears sometimes in KMail

2021-01-22 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=431921

Bug ID: 431921
   Summary: Black square appears sometimes in KMail
   Product: kmail2
   Version: 5.15.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY
This behaviour happens randomly but often when I read emails. Unfortunately I
can not tell how to reproduce. All I can say that this happens every couple of
days.
When I point the mouse to the black square the cursor turns from "default" to
"resize" (see screenshot).

SOFTWARE/OS VERSIONS
Operating System: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.7-200.fc33.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz
Memory: 7.2 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 387061] REGRESSION: Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2021-01-14 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #37 from Attila  ---
The bug has not been fixed as far as I can see. KMail 5.15.3 is available for
Fedora 33. It doesn't work when I try to open ASCII-emails larger then 2 MB. I
got ASCII emails from 30 MB up to 55 MB. The system starts to swap by opening
such an email (8 GB RAM is installed and a CPU with 4 cores). All I can do is
to delete this email as soon as KMail responds not to overload the system. This
isn't a good user experience.
Is there anything I can do? Let me know if you still need more informtaion.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 391030] kmail does not print images in emails

2020-08-06 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=391030

Attila  changed:

   What|Removed |Added

 CC||bugs.kde.att...@online.de

--- Comment #2 from Attila  ---
I can confirm. Same on Fedora 32, KMail version 5.13.2 (19.12.2).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415056] Kmail pretends to be done retrieving emails

2020-05-28 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415056

--- Comment #4 from Attila  ---
Hi,

I have upgraded to Fedora 32. The version of KMail is 5.13.2 (19.12.2).
I can reproduce this bug.
Do you need some additional information? How can I help to fix this bug?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415052] Kmail jumps to the end of ASCII-emails.

2020-05-28 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415052

--- Comment #6 from Attila  ---
(In reply to Laurent Montel from comment #2)
> We fixed some bugs about it.
> Please update to new version 5.11.x is very old we will release 5.14.0 in 1
> month.
> Regards

Hi,

I have upgraded to Fedora 32. The version of KMail is 5.13.2 (19.12.2).
I can reproduce this bug.
Do you need some additional information? How can I help to fix this bug?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415052] Kmail jumps to the end of ASCII-emails.

2020-04-12 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415052

--- Comment #5 from Attila  ---
(In reply to Christoph Feck from comment #4)
> 19.04 is the version of the combined releases of several KDE applications.
> It refers to the year/month, so 19.04 is a year old. We will release 20.04
> in two weeks, but you could also check with KMail 5.13 (releases 19.12).

Hi,

like I said, there is no update for Fedora 31 (comment #3). I have turned to
"rdieter" because as far as I can see he is the packager for Fedora's KDE, but
he did not reply.

I will upgrade to Fedora 32 as soon as it is available. It comes with
kmail-19.12.2-1.
Regards.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 413228] Unable to change the font size for pasted words

2020-03-13 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=413228

--- Comment #4 from Attila  ---
(In reply to Laurent Montel from comment #3)
> It's a bug in qt when we import html.

Hi,

does it mean that you were able to reproduce this bug? In this case the status
should be set to "CONFIRMED".
Did you informed the Qt-developers or should I report this bug there?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415052] Kmail jumps to the end of ASCII-emails.

2020-03-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415052

--- Comment #3 from Attila  ---
(In reply to Laurent Montel from comment #2)
> We fixed some bugs about it.
> Please update to new version 5.11.x is very old we will release 5.14.0 in 1
> month.
> Regards

Hi,

thanks for the quick reply.
My Fedora 31 is up to date. KMail is still on version 5.11.3 which is provided
by the RPM-Package kmail-19.04.3-2.fc31.x86_64. I am a bit confused about the
versioning. What does the version 19.04.3-2 mean? I guess this one is old as
well.
It means that Fedora is sticking on old versions.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 413228] Unable to change the font size for pasted words

2020-03-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=413228

--- Comment #1 from Attila  ---
Can someone please respond?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415052] Kmail jumps to the end of ASCII-emails.

2020-03-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415052

--- Comment #1 from Attila  ---
Can someone please respond?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2020-03-02 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #5 from Attila  ---
Can someone please respond?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2020-01-12 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #21 from Attila  ---
(In reply to Christoph Feck from comment #20)
> Qt's text APIs don't use bytes, but work on UTF-16 code points. The limit is
> actually 1 million of those and each uses 16 bit (2 byte).

Thanks for this information.
You have mentioned "Qt's text API". Kwrite can show text-files larger then
50MB. Sorry I am a user. I am looking into solutions. By the way I have
upgraded from Fedora 21 to 31. Something significant has changed in between
because it wasn't a big deal for Kmail to show ASCII emails larger then 50MB.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2020-01-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #19 from Attila  ---
Something should be done because it is a bad user experience when the user
clicks on a new email. There is no warning, no nothing. It is a peace of cake
for other email clients to show large messages.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2020-01-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=387061

--- Comment #18 from Attila  ---
(In reply to Sandro Knauß from comment #5)
> As I learned now from vkrause, there is a 2MB limit inside QtWEbEngine
> (http://doc.qt.io/qt-5/qwebengineview.html#setHtml). So we will have to
> rework the part that pushed the content to not use setHtml and use instead a
> file.

Hi, if there is a limit of 2MB than I am wondering why is it not possible to
show ASCII content of 1.3 MB. I think 1.3 is less than 2, isn't it?

See my bug report: https://bugs.kde.org/show_bug.cgi?id=415051

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415342] New: Kmail shows deleted emails

2019-12-19 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415342

Bug ID: 415342
   Summary: Kmail shows deleted emails
   Product: kmail2
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY
When I delete an email and the next new email in my Inbox has a size larger
than 1.2 MiB, Kmail still shows the previous, deleted email instead of the
marked email.

OBSERVED RESULT
Kmail shows the deleted email with no warning to the user. This is really
confusing and fatal to the user.

EXPECTED RESULT
Kmail must not show deleted emails.

SOFTWARE/OS VERSIONS
Operating System: Fedora 31
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.5
Kernel Version: 5.3.16-300.fc31.x86_64
OS Type: 64-bit


ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415123] New: Kmail ignores font settings for new emails

2019-12-13 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415123

Bug ID: 415123
   Summary: Kmail ignores font settings for new emails
   Product: kmail2
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY
Kmail sets the font for new emails always to "DejaVu Sans" and ignores my own
font settings.

STEPS TO REPRODUCE
1. Launch Kmail
2. Open the "configure" dialog
3. Click on "Appearance"
4. Change the font to a font of your choice
5. Close the "configure" dialog
6. Click on "new email"

OBSERVED RESULT
The font for new emails is set to "DejaVu Sans"

EXPECTED RESULT
Kmail should use the font for new emails from the "configure" dialog.

SOFTWARE/OS VERSIONS
Operating System: Fedora 31
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.5
Kernel Version: 5.3.15-300.fc31.x86_64
OS Type: 64-bit


ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415056] Kmail pretends to be done retrieving emails

2019-12-12 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415056

--- Comment #3 from Attila  ---
(In reply to Christophe Giboudeaux from comment #2)
> which account type is it? pop3, imap...
It is pop3

> Did you create filters?
Yes I did

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415056] Kmail pretends to be done retrieving emails

2019-12-12 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415056

--- Comment #1 from Attila  ---
Hi Christophe,

sorry for being polite and asking, but why do you think that the severity for
this bug should be set to normal instead of critical? After all I lose a lot of
important data day by day. I think this is critical enough.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415056] New: Kmail pretends to be done retrieving emails

2019-12-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415056

Bug ID: 415056
   Summary: Kmail pretends to be done retrieving emails
   Product: kmail2
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY
Kmail pretends to be done retrieving emails, the progress bar is at 100% and
disappears. When I click on emails kmail can't display them.

I can see in the message bar the following:
Item query returned empty result set.

All the emails on which I have clicked are lost.
Approximately 30 seconds later Kmail shows me suddenly 2 or 3 times more new
emails which are correct sorted to my folders (I have set up a couple of
filters).

STEPS TO REPRODUCE
1. Launch Kmail
2. Retrieve emails
3. Don't wait and click on some of the emails before Kmail is going to sort
them to the right folders.

OBSERVED RESULT
Kmail must not pretend to be done when it is not done.

EXPECTED RESULT
Kmail must finish the job before the progressbar is at 100% and disappears.

SOFTWARE/OS VERSIONS
Operating System: Fedora 31
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.5
Kernel Version: 5.3.15-300.fc31.x86_64
OS Type: 64-bit


ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415052] New: Kmail jumps to the end of ASCII-emails.

2019-12-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415052

Bug ID: 415052
   Summary: Kmail jumps to the end of ASCII-emails.
   Product: kmail2
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY
When I read ASCII-email which are larger then the height of the window, Kmail
scrolls frequently to the end or to somewhere in the middle of the email.

STEPS TO REPRODUCE
1. Launch Kmail
2. Read a couple of large ASCII-emails.

OBSERVED RESULT
Kmail shows the email at the end instead at the beginning.

EXPECTED RESULT
Kmail should show the email from the beginning.

SOFTWARE/OS VERSIONS
Operating System: Fedora 31
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.5
Kernel Version: 5.3.15-300.fc31.x86_64
OS Type: 64-bit

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 415051] New: KMail can't show ASCII-emails larger than 1.2 MiB

2019-12-11 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=415051

Bug ID: 415051
   Summary: KMail can't show ASCII-emails larger than 1.2 MiB
   Product: kmail2
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY
If I click on an ASCII-email, which is larger than 1.2 MiB to read it, it will
not be shown. There is neither a warning nor an interaction with the user that
this email can't be displayed.
It was in prior versions of kmail no problem to show large ASCII-emails.

STEPS TO REPRODUCE
1. Launch kmail
2. Try to read an ASCII-email larger than 1.2 MiB
3. 

OBSERVED RESULT
Kmail doesn't give the user any warning and it dosn't show the content of the
email.


EXPECTED RESULT
Kmail should show the email like it has done in earlier versions.

SOFTWARE/OS VERSIONS

Operating System: Fedora 31
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.5
Kernel Version: 5.3.15-300.fc31.x86_64
OS Type: 64-bit


ADDITIONAL INFORMATION
My workaround is to save the email to a file and open it by Kwrite.
By the way KWrite can even open emails saved to a file larger than 25 MiB.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 414974] New: Akonadi crashed while deleting emails

2019-12-08 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=414974

Bug ID: 414974
   Summary: Akonadi crashed while deleting emails
   Product: Akonadi
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

Application: akonadiserver (5.11.3)

Qt Version: 5.12.5
Frameworks Version: 5.64.0
Operating System: Linux 5.3.13-300.fc31.x86_64 x86_64
Distribution: "Fedora release 31 (Thirty One)"

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

I have deleted a couple of emails. Kmail did not delete them and they were
still marked as "new". This happens frequently.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8b6bc32800 (LWP 1679))]

Thread 32 (Thread 0x7f8afbfff700 (LWP 2203)):
#0  0x7f8b6f70e44c in read () from /lib64/libc.so.6
#1  0x7f8b6e36e4cf in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7f8b6e3262e7 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7f8b6e326742 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7f8b6e3268d3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7f8b6fcb2cd3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f8b6fc5cceb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x55f546d4e5ce in Akonadi::Server::Connection::handleIncomingData() ()
#8  0x7f8b6fc94656 in QSingleShotTimer::timerEvent(QTimerEvent*) () from
/lib64/libQt5Core.so.5
#9  0x7f8b6fc88c15 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#10 0x7f8b6fc5dd55 in doNotify(QObject*, QEvent*) () from
/lib64/libQt5Core.so.5
#11 0x7f8b6fc5dde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#12 0x7f8b6fcb1f78 in QTimerInfoList::activateTimers() () from
/lib64/libQt5Core.so.5
#13 0x7f8b6fcb282c in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5Core.so.5
#14 0x7f8b6e3264a0 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#15 0x7f8b6e326830 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#16 0x7f8b6e3268d3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#17 0x7f8b6fcb2cb5 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#18 0x7f8b6fc5cceb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#19 0x7f8b6fab5395 in QThread::exec() () from /lib64/libQt5Core.so.5
#20 0x7f8b6fab64e6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#21 0x7f8b6ef274e2 in start_thread () from /lib64/libpthread.so.0
#22 0x7f8b6f71d693 in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f8ae57fa700 (LWP 2137)):
#0  0x7ffefc78a6cb in ?? ()
#1  0x7ffefc78a918 in clock_gettime ()
#2  0x7f8b6f6e46ab in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6
#3  0x7f8b6fcb24c5 in qt_gettime() () from /lib64/libQt5Core.so.5
#4  0x7f8b6fcb100d in QTimerInfoList::updateCurrentTime() () from
/lib64/libQt5Core.so.5
#5  0x7f8b6fcb1419 in QTimerInfoList::timerWait(timespec&) () from
/lib64/libQt5Core.so.5
#6  0x7f8b6fcb2984 in timerSourcePrepareHelper(GTimerSource*, int*) () from
/lib64/libQt5Core.so.5
#7  0x7f8b6fcb2a32 in timerSourcePrepare(_GSource*, int*) () from
/lib64/libQt5Core.so.5
#8  0x7f8b6e325d1a in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#9  0x7f8b6e3266cb in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#10 0x7f8b6e3268d3 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#11 0x7f8b6fcb2cd3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#12 0x7f8b6fc5cceb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#13 0x55f546d4e5ce in Akonadi::Server::Connection::handleIncomingData() ()
#14 0x7f8b6fc94656 in QSingleShotTimer::timerEvent(QTimerEvent*) () from
/lib64/libQt5Core.so.5
#15 0x7f8b6fc88c15 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#16 0x7f8b6fc5dd55 in doNotify(QObject*, QEvent*) () from
/lib64/libQt5Core.so.5
#17 0x7f8b6fc5dde8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#18 0x7f8b6fcb1f78 in QTimerInfoList::activateTimers() () from
/lib64/libQt5Core.so.5
#19 0x7f8b6fcb282c in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5Core.so.5
#20 0x7f8b6e3264a0 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#21 0x7f8b6e326830 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#22 0x7f8b6e3268d3 in 

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2019-12-05 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

--- Comment #4 from Attila  ---
I suggest that this bug should be classified as a serious bug, because I lose
every day a lot of emails. This bug should be fixed as soon as possible.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389829] "Unable to fetch item from backend" after deleting it using akonadi_maildir_resource_0

2019-12-04 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=389829

Attila  changed:

   What|Removed |Added

 CC||bugs.kde.att...@online.de

--- Comment #3 from Attila  ---
I get this message a couple of times every week like:

Unable to fetch item from backend (collection -1) : Unable to retrieve item
from resource: [LRCONFLICT] Resource akonadi_maildir_resource_0 tries to modify
item 5831 () (in collection 19) with dirty payload, aborting STORE.

Perhaps the info is important that I am using POP3.

The version of akonadi is: 5.11.3 on Fedora 31.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 413229] New: Unable to copy an email address on right click

2019-10-20 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=413229

Bug ID: 413229
   Summary: Unable to copy an email address on right click
   Product: kmail2
   Version: 5.11.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY
It is not possible to copy the "From" email address on right click in the inbox
of an email. When I change to the folder "Sent" and do the right click on
"From: Me" the entry "Copy Email address" appears in the context menu but it
copies the email address "To:".

STEPS TO REPRODUCE
1. Launch KMail and open your inbox.
2. Do a right click on the "From" address to see the context menu.
3. There is no "copy email address".
4. Sometimes it appears the entry "copy email address" randomly (with a little
luck).

OBSERVED RESULT
Can't copy the email address from the sender in the inbox.

EXPECTED RESULT
It must be possible to copy the email address in the inbox on right click of
"From:"

SOFTWARE/OS VERSIONS
Operating System: Fedora 30
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.5
Kernel Version: 5.3.6-200.fc30.x86_64
OS Type: 64-bit

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 413228] New: Unable to change the font size for pasted words

2019-10-20 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=413228

Bug ID: 413228
   Summary: Unable to change the font size for pasted words
   Product: kmail2
   Version: 5.11.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY
It is not possible to change the font size in a new e-mail for pasted words
from a web site.

STEPS TO REPRODUCE
1. Launch KMail and klick on "new mail".
2. Go to the site "https://kde.org/; for example and copy the word
"Announcements" on this site.
3. Paste the copied word into KMail.
4. Mark the copied word again and change the font size to any size you like.

OBSERVED RESULT
The font size won't change. It has still the origin size. Even the font size
for any text below will have the font size of the copied word.

EXPECTED RESULT
It must be possible to change the font size for any pasted words from a web
site.

SOFTWARE/OS VERSIONS
Operating System: Fedora 30
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.5
Kernel Version: 5.3.6-200.fc30.x86_64
OS Type: 64-bit

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 398987] The toolbar disappears after restart

2018-09-29 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=398987

--- Comment #4 from Attila  ---
It works with kmail-18.04.3-2.
Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 398987] The toolbar disappears after restart

2018-09-23 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=398987

--- Comment #2 from Attila  ---
(In reply to Colin J Thomson from comment #1)
> I wasn't hit by this but I think it was fixed with kmail-18.04.3-2 which is
> in updates-testing.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1630388
> 
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1145598

OK then, I will give it a try when the package is available as a regular update
and I will report.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 378281] column width in messages list view not retained

2018-09-23 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=378281

Attila  changed:

   What|Removed |Added

 CC||bugs.kde.att...@online.de

--- Comment #3 from Attila  ---
(In reply to Martin Tlustos from comment #2)
> It's still there in 5.8.3. A workaround is to click the column headings and
> choose "adjust column width" (not sure, my settings are German).
> A possible solution would be to add a setting to always automatically adjust
> column widths.

Unfortunately the workaround doesn't help permanently. By the way it is called
"Adjust columns sizes". I have to adjust the column sizes almost after every
restart of KMail.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 398987] New: The toolbar disappears after restart

2018-09-23 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=398987

Bug ID: 398987
   Summary: The toolbar disappears after restart
   Product: kmail2
   Version: 5.8.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

SUMMARY

The toolbar disappears after restart when "Show Toolbar" is set.

STEPS TO REPRODUCE
1. Open KMail
2. Click on "Settings" in the Menu bar
3. Set "Show Toolbar"
4. Close KMail
5. Open KMail again

EXPECTED RESULT
The Toolbar should be visible

ACTUAL RESULT
The Toolbar is not visible and the option "Show Toolbar" is not marked.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.4
KDE Frameworks Version: 5.48.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

2018-09-23 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=393421

Attila  changed:

   What|Removed |Added

 CC||bugs.kde.att...@online.de

--- Comment #32 from Attila  ---
Please return this option. What is the benefit of this HTML Message bar? I
don't get it. It is annoying and it's all the time in the middle of the screen.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 384243] Kmail crashes when resizing the main window

2017-08-31 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=384243

--- Comment #1 from Attila <bugs.kde.att...@online.de> ---
Created attachment 107629
  --> https://bugs.kde.org/attachment.cgi?id=107629=edit
Backtrace

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 384243] New: Kmail crashes when resizing the main window

2017-08-31 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=384243

Bug ID: 384243
   Summary: Kmail crashes when resizing the main window
   Product: kmail2
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: bugs.kde.att...@online.de
  Target Milestone: ---

-- Information about the crash:
- What I was doing when the application crashed:
I was resizing the main window.

- The crash can be reproduced always.

Steps to Reproduce:
1. Open Kmail for the first time (therefor you need a new user account).
2. The "Account Assistant" window appears for "Provide personal data".
3. Press "Cancel" to close the "Account Assistant" window.
4. Resize the main window (choose the bottom right corner).

- Actual Results: Kmail crashes.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 262853] New: Can't attach file from a samba share

2011-01-11 Thread Attila Siposs
https://bugs.kde.org/show_bug.cgi?id=262853

   Summary: Can't attach file from a samba share
   Product: kmail
   Version: 1.13.5
  Platform: Pardus PiSi Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
AssignedTo: kdepim-bugs@kde.org
ReportedBy: sipia...@gmail.com


Version:   1.13.5 (using KDE 4.4.5) 
OS:Linux

Attaching any file from a samba share to an email is not possible. Kmail says
the file does not exist.

Reproducible: Always

Steps to Reproduce:
1. start composing a new message
2. hit attach
3. browse the filechooser window to an smb share or type directly into the
addressbar
4. choose a file on the smb share and try to attach it
5. kmail says that the file does not exist

Actual Results:  
kmail does not attach the file to the email

Expected Results:  
Attach the file from the samba share

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 199375] Kontact/kmail crash during exit (QListData::shared_null, qDeleteAllQListKIO::Slave*, ProtocolInfo, Scheduler related)

2010-06-07 Thread Attila Balint
https://bugs.kde.org/show_bug.cgi?id=199375


Attila Balint abalin...@gmail.com changed:

   What|Removed |Added

 CC|abalin...@gmail.com |




-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 198172] printer margin settings are forgotten at restart

2010-03-04 Thread Attila
https://bugs.kde.org/show_bug.cgi?id=198172





--- Comment #3 from Attila bugs kde attila online de  2010-03-04 10:41:11 ---
Due to the information that my Bug 228931 is a duplicate from this i answer
here.

Hello!
Don't get me wrong but i guess that this is not a question of Qt 4.8 or other
versions. Under KDE 3x (Qt 3x) the printer dialog was excellent! I was able to
set the margins and save the settings. All i would like to do is to save my
settings (like the printer dialog under KDE 3x).
Every time i am trying to print, i have to click on Properties, then set the
margins, after that i have to click on Options , select the tab HTML
settings uncheck printer friendly mode, uncheck print header and so on.
I hate to say that, but this is so stupid! Isn't it? You can't tell in every
office all the user: Hey guys! Remember if you print, don't forget to click
here, click there . and do this on every single print. This is not
user-optimized.
Thank you for listening to me.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 215245] New: Opened Kontact, I got my mails from gmail, and closed Kontact with X. The application crashed

2009-11-19 Thread Attila Balint
https://bugs.kde.org/show_bug.cgi?id=215245

   Summary: Opened Kontact, I got my mails from gmail, and closed
Kontact with X. The application crashed
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: abalin...@gmail.com


Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic-pae i686
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x in ?? ()
#7  0xb5ac46ce in qDeleteAllKIO::SchedulerPrivate::ProtocolInfoDict () at
/usr/include/qt4/QtCore/qalgorithms.h:358
#8  ~SchedulerPrivate () at ../../kio/kio/scheduler.cpp:103
#9  destroy () at ../../kio/kio/scheduler.cpp:209
#10 0xb59f7f6b in ~KCleanUpGlobalStatic (this=0xb5bc95d4, __in_chrg=value
optimized out) at ../../kdecore/kernel/kglobal.h:62
#11 0xb62f005f in ?? () from /lib/tls/i686/cmov/libc.so.6
#12 0xb62f00cf in exit () from /lib/tls/i686/cmov/libc.so.6
#13 0xb62d7b5e in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#14 0x0804a5e1 in _start ()

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 121272] E-mail messages become blank when I open them

2008-02-10 Thread Attila GOLONCSER
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=121272 




--- Additional Comments From dunkelheit freemail hu  2008-02-11 07:11 
---
See my Comment #26 on Bug 80988, I also went to DATA LOSS with the same 
problem, after a crash.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 80988] kmail corrupts index entries of old mails (from older kmail versions?)

2008-02-10 Thread Attila GOLONCSER
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=80988 




--- Additional Comments From dunkelheit freemail hu  2008-02-11 06:59 
---
I also have this problem desribed above, but with REAL data loss. My versions 
are.

$ kmail --version
Qt: 3.3.8
KDE: 3.5.8
KMail: 1.9.7

The number and the state of the messages are correct, but all the headers in 
the list are unknown. All the corrupted mails have only these headers (but 
nothing else, my maildir folder is full with ~68 byte files):

Status: RO
X-Status: RC (or RAC, RT)
X-KMail-EncryptionState: N
X-KMail-SignatureState: N
X-KMail-MDN-Sent:

I came this problem when I filtered my messages (circa 270 in one task), and 
while the job kmail crashed. After restarting the same problem occured as in 
the main bug description, with the exception that I really lost my data from my 
folder.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs