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

[bugzy]

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

bugzy  changed:

   What|Removed |Added

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

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

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

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

[bugzy]

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

bugzy  changed:

   What|Removed |Added

 CC||tro...@free.fr

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

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

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

[bugzy]

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

bugzy  changed:

   What|Removed |Added

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

--- Comment #41 from bugzy  ---


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

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

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

[bugzy]

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

bugzy  changed:

   What|Removed |Added

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

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

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

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

[bugzy]

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

bugzy  changed:

   What|Removed |Added

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

--- Comment #4 from bugzy  ---


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

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

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

[bugzy]

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

bugzy  changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

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

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

[Akonadi] [Bug 395131] Akonadi consumes all memory

[bugzy]

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

bugzy  changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

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

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

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

[bugzy]

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

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

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

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

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

In fix mode these children will be unparented.


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


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

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

Children were successfully unparented.

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

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

[bugzy]

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

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

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

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

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

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

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

[bugzy]

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

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

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

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

[bugzy]

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

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

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

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

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

[bugzy]

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

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

   What|Removed |Added

 CC||bugzylit...@gmail.com

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

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

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

[bugzy]

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

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

Thanks

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

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

[bugzy]

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

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

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

Expected Results:
korganizer opens properly

Actual results:
korganizer crashes

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

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

[bugzy]

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

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

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

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

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

[bugzy]

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

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

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

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

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

[bugzy]

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

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

Application: korganizer (5.7.3)

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

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

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

The crash can be reproduced every time.

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

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

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

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

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

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

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

[bugzy]

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

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

   What|Removed |Added

 CC||bugzylit...@gmail.com

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

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

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

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

[bugzy]

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

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

Attached video of the bug and how to reproduce it

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

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

[bugzy]

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

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

   What|Removed |Added

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

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

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

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

[Akonadi] [Bug 319289] filter rules for incoming messages on pop3 account do not seem to work

[bugzy]

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

bugzy bugzylit...@gmail.com changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

--- Comment #3 from bugzy bugzylit...@gmail.com ---
I am experiencing the same problem Kontact 4.10.5 on Fedora 19. I always have
to apply all my filters manually in order to get them to work. I also think
that this bug may be related to Bug 322871
(https://bugs.kde.org/show_bug.cgi?id=322871) which plagues KDE 4.11

-- 
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 249798] Kmail its always outputting error messages

[bugzy]

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

bugzy bugzylit...@gmail.com changed:

   What|Removed |Added

 CC||bugzylit...@gmail.com

--- Comment #3 from bugzy bugzylit...@gmail.com ---
Encountered the same problem on fedora update to kde 4.8.1
I was able to resolve the problem by going through the following steps:
1. Open Akonadi console,

2. Right click on faulty resource (in my case KMail Folders) and select
Clone Agent.

3. A new reource with the same name should appear except with (Clone) next to
the name (In my case  KMail Folders (Clone)).

4. Turn off faulty resource by right clicking the resource and selecting
Toggle Online/Offline.

5. Open Kmail or Kontact and ensure that all your email shows up in the cloned
resource (In my case I had to click on each folder in the cloned resource
before my email actually appeared in the folder). While carrying out this step,
I noticed that the faulty resource was turned on again, but I simply switched
to the Akonadiconsole window and  repeating step 4.

6. Once all your email appeares in the cloned resource, closed Kmail, switch
back to the Akonadi console window, and delete the faulty resource by selecting
it and clicking Remove.

7. If you so choose, you may rename the cloned resource by deleting the
(Cloned) in front of it.

8. After step 7 go through all your account, Identities, and filter settings to
make sure that all the settings are configured to use the new cloned resource.

Hope this helps

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