[kmail2] [Bug 480990] KMail crashes when trying to open .mbox file

2024-05-18 Thread K0RR
https://bugs.kde.org/show_bug.cgi?id=480990

--- Comment #1 from K0RR  ---
Created attachment 169591
  --> https://bugs.kde.org/attachment.cgi?id=169591=edit
New crash information added by DrKonqi

kmail (5.24.5 (23.08.5)) using Qt 5.15.13

Akonadi Server Self-Test Report===
Test 1:  SUCCESS


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

File content of '/home/k0rr/.config/akonadi/akonadiserverrc':
[Debug]
Tracer=null

[%General]
Driver=QMYSQL

[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/run/user/1002/akonadi/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true


Test 2:  SUCCESS


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

Test 3:  SUCCESS


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

Test 4:  SUCCESS


MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld  Ver 8.0.36-2ubuntu3 for Linux on
x86_64 ((Ubuntu))


Test 5:  ERROR


MySQL server log contains errors.
Details: The MySQL server error log file '/home/k0rr/.local/share/akonadi/db_data/mysql.err'
contains errors.

File content of '/home/k0rr/.local/share/akonadi/db_data/mysql.err':
2024-05-18T10:27:49.828221Z 0 [Warning] [MY-010097] [Server] Insecure
configuration for --secure-file-priv: Current value does not restrict location
of generated files. Consider setting it to a valid, non-empty path.
2024-05-18T10:27:49.828266Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld
(mysqld 8.0.36-2ubuntu3) starting as process 40870
2024-05-18T10:27:49.829748Z 0 [Warning] [MY-013242] [Server]
--character-set-server: 'utf8' is currently an alias for the character set
UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider
using UTF8MB4 in order to be unambiguous.
2024-05-18T10:27:49.829753Z 0 [Warning] [MY-013244] [Server]
--collation-server: 'utf8mb3_general_ci' is a collation of the deprecated
character set UTF8MB3. Please consider using UTF8MB4 with an appropriate
collation instead.
2024-05-18T10:27:49.832977Z 0 [Warning] [MY-013907] [InnoDB] Deprecated
configuration parameters innodb_log_file_size and/or innodb_log_files_in_group
have been used to compute innodb_redo_log_capacity=134217728. Please use
innodb_redo_log_capacity instead.
2024-05-18T10:27:49.833941Z 1 [System] [MY-011012] [Server] Starting upgrade of
data directory.
2024-05-18T10:27:49.833951Z 1 [System] [MY-013576] [InnoDB] InnoDB
initialization has started.
2024-05-18T10:27:49.852002Z 1 [ERROR] [MY-012224] [InnoDB] Tablespace flags are
invalid in datafile: ./ibdata1, Space ID:0, Flags: 21. Please refer to
http://dev.mysql.com/doc/refman/8.0/en/innodb-troubleshooting-datadict.html for
how to resolve the issue.
2024-05-18T10:27:49.852033Z 1 [ERROR] [MY-012237] [InnoDB] Corrupted page [page
id: space=0, page number=0] of datafile './ibdata1' could not be found in the
doublewrite buffer.
2024-05-18T10:27:49.852042Z 1 [ERROR] [MY-012930] [InnoDB] Plugin
initialization aborted with error Data structure corruption.
2024-05-18T10:27:50.351961Z 1 [ERROR] [MY-011013] [Server] Failed to initialize
DD Storage Engine.
2024-05-18T10:27:50.352303Z 0 [ERROR] [MY-010020] [Server] Data Dictionary
initialization failed.
2024-05-18T10:27:50.352328Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-05-18T10:27:50.352796Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld:
Shutdown complete (mysqld 8.0.36-2ubuntu3)  (Ubuntu).


Test 6:  SUCCESS


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

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

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

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of
data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for
debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for p

[kmail2] [Bug 480990] KMail crashes when trying to open .mbox file

2024-05-18 Thread K0RR
https://bugs.kde.org/show_bug.cgi?id=480990

K0RR  changed:

   What|Removed |Added

 CC||rdkr...@gmail.com

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

[kmail2] [Bug 480990] New: KMail crashes when trying to open .mbox file

2024-02-07 Thread K0RR
https://bugs.kde.org/show_bug.cgi?id=480990

Bug ID: 480990
   Summary: KMail crashes when trying to open .mbox file
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: rdkr...@gmail.com
  Target Milestone: ---

Application: kmail (5.24.4 (23.08.4))

Qt Version: 5.15.10
Frameworks Version: 5.113.0
Operating System: Linux 6.7.1-060701-generic x86_64
Windowing System: X11
Distribution: Rhino Linux 2023.4 (mainline)
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
what do you want me to input here? I have no idea waht causes this

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted

[KCrash Handler]
#4  0x702561a9998b in pthread_kill () at /lib/x86_64-linux-gnu/libc.so.6
#5  0x702561a42856 in raise () at /lib/x86_64-linux-gnu/libc.so.6
#6  0x702561a268b7 in abort () at /lib/x86_64-linux-gnu/libc.so.6
#7  0x702561ea5fde in ??? () at /lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x702561ebae5c in ??? () at /lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x702561ea5a29 in std::terminate() () at
/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x702561ebb0e8 in __cxa_throw () at
/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x702562290216 in qBadAlloc() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x702562294bad in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x702562338bdc in QByteArray::append(char const*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x70256251122e in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x702560339305 in KIO::TransferJob::data(KIO::Job*, QByteArray const&)
() at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#16 0x70256251122e in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x70256030aad9 in KIO::SlaveInterface::data(QByteArray const&) () at
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#18 0x70256030d098 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() at /lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#19 0x70256030b42b in KIO::SlaveInterface::dispatch() () at
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#20 0x7025603106d1 in KIO::Slave::gotInput() () at
/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#21 0x70256251122e in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7025625046f3 in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x70256316bce5 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7025624d6558 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7025624d9d7d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x702562533eff in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x70255e1462e5 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x70255e1a45ff in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x70255e144403 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x702562533569 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7025624d4ecb in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7025624dd828 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x6219da5171b9 in ??? ()
#34 0x702561a280d0 in ??? () at /lib/x86_64-linux-gnu/libc.so.6
#35 0x702561a28189 in __libc_start_main () at
/lib/x86_64-linux-gnu/libc.so.6
#36 0x6219da5178a5 in ??? ()
[Inferior 1 (process 55723) detached]

Reported using DrKonqi

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

[kleopatra] [Bug 463942] New: symbol lookup error

2023-01-06 Thread K0RR
https://bugs.kde.org/show_bug.cgi?id=463942

Bug ID: 463942
   Summary: symbol lookup error
Classification: Applications
   Product: kleopatra
   Version: 3.1.24.221201
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: aheine...@gnupg.org
  Reporter: rdkr...@gmail.com
CC: kdepim-bugs@kde.org, m...@kde.org
  Target Milestone: ---

This is what I see when I try to launch Kleopatra:

kleopatra: symbol lookup error: /lib64/libKF5PimTextEdit.so.5: undefined
symbol:
_ZN11KMessageBox23warningTwoActionsCancelEP7QWidgetRK7QStringS4_RK8KGuiItemS7_S7_S4_6QFlagsINS_6OptionEE

EXPECTED RESULT
Launch, not crash

SOFTWARE/OS VERSIONS
Linux: Fedora 36
KDE Plasma Version: none - running cinnamon-de
KDE Frameworks Version: no idea
Qt Version: no idea

-- 
You are receiving this mail because:
You are on the CC list for the bug.