[kontact] [Bug 394403] Width column list resize every time to restart

2024-05-18 Thread Richard Ullger
https://bugs.kde.org/show_bug.cgi?id=394403

Richard Ullger  changed:

   What|Removed |Added

 CC|rull...@protonmail.com  |

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

[kmail2] [Bug 458245] Kmail 5.21.0 / 22.08.0 does no longer respect per contact html and remote content settings

2024-05-18 Thread Ricardo J. Barberis
https://bugs.kde.org/show_bug.cgi?id=458245

Ricardo J. Barberis  changed:

   What|Removed |Added

 Status|REOPENED|CONFIRMED

--- Comment #17 from Ricardo J. Barberis  ---
(In reply to Boltronics from comment #15)
> (In reply to Axel Braun from comment #14)
> > That works in the preview pane, but if I double click the mail t oopen it in
> > a separate window I still need to reload HTML content -> reopening
> 
> I too can confirm this. Sorry I didn't think to test that previously. It's
> not part of my usual workflow.

This keeps happening in Kmail 6.0.2 (24.02.2)

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

[kontact] [Bug 394403] Width column list resize every time to restart

2024-05-18 Thread Ricardo J. Barberis
https://bugs.kde.org/show_bug.cgi?id=394403

--- Comment #9 from Ricardo J. Barberis  ---
This still happens with Kmail 6.0.2 (24.02.2).

Sometimes columns also resize during a filtering operation, but this happened
in Plamsa 5's version of Kmail as well.

FWIW, I recently switched to Wayland, which made no diference.

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

[kontact] [Bug 487203] New: flatpak: cannot open kmail mail attachments with default apps or any other app

2024-05-18 Thread Robert Riemann
https://bugs.kde.org/show_bug.cgi?id=487203

Bug ID: 487203
   Summary: flatpak: cannot open kmail mail attachments with
default apps or any other app
Classification: Applications
   Product: kontact
   Version: 6.0.2
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-bugs@kde.org
  Reporter: rob...@riemann.cc
  Target Milestone: ---

Created attachment 169601
  --> https://bugs.kde.org/attachment.cgi?id=169601&action=edit
first dialogue happens when clicking on pdf attachment, second one when
clicking on open with

SUMMARY

I have Kontact with Kmail installed as Flatpak from fedora flatpak repository.
When I receive pdfs as attachment, I cannot open them with okular without
saving them first to disk. Same issue for any other attachment types.


STEPS TO REPRODUCE
1.  receive an email with pdf attachment (or other file)
2.  click on them for open
3. notice that okular is not an option and app chooser is basically empty

OBSERVED RESULT

Cannot open with okular

EXPECTED RESULT

flatpak aplication chooser portal opens and permits to open file with okular

ADDITIONAL INFORMATION

Related Discussion at
https://discussion.fedoraproject.org/t/evolution-flatpak-cant-open-pdf-from-attachments-when-composing-email/24230

Related flatpak bug concerning composing mails with attachment: while granting
kontact access to all system files may be good workaround, it would be better
to rely on the flatpak open file portal:
https://bugs.kde.org/show_bug.cgi?id=486838

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

[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&action=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 producti

[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.

[korganizer] [Bug 485722] there's no way to switch to the standard 24 hour display

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

t...@adminart.net changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

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

[kontact] [Bug 487170] Deleting a Todo Crahses the application

2024-05-18 Thread Ikel Atomig
https://bugs.kde.org/show_bug.cgi?id=487170

--- Comment #2 from Ikel Atomig  ---
>From Crashed Process Viewer :
https://pb.envs.net/?a0cfb8a2df5e7e1c#5njgguRW48pyZz2zX4ZRJghPBRGMPyyevCPe2r3RwabY

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

[kontact] [Bug 487170] Deleting a Todo Crahses the application

2024-05-18 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=487170

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
hi,
could you report backtrace please ?
Thanks

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

[kontact] [Bug 487170] New: Deleting a Todo Crahses the application

2024-05-18 Thread Ikel Atomig
https://bugs.kde.org/show_bug.cgi?id=487170

Bug ID: 487170
   Summary: Deleting a Todo Crahses the application
Classification: Applications
   Product: kontact
   Version: 6.0.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: todo
  Assignee: kdepim-bugs@kde.org
  Reporter: cont...@ikel.slmail.me
  Target Milestone: ---

SUMMARY

Whether the To-Do is recurring or Non-Recurring. It just crashes the app.

STEPS TO REPRODUCE
1. Try deleting a To-Do irrespective of the type.

OBSERVED RESULT

Crahses

EXPECTED RESULT

It shouldn't

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)


ADDITIONAL INFORMATION

Sent a crash report already.

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