[kmail2] [Bug 374768] Impossible to paste multiple email addresses

2017-01-09 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374768

--- Comment #2 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
>From the test I created, yes it does.

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

[kmail2] [Bug 374768] New: Impossible to paste multiple email addresses

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374768

Bug ID: 374768
   Summary: Impossible to paste multiple email addresses
   Product: kmail2
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

I reopen here the bug #177398 :
"When pasting into the to or bcc adress fields the lines in the copied text are
separated with spaces instead of commas as it was in previous versions of
kmail.

This means i cannot copy a column of email addresses from a spreadsheet and add
them all as recipients in a mail in kmail.
Because Kmail will understand the text as one long email address."


The problem is still present in v5.2.3.

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

[kmail2] [Bug 177398] paste multiple emaill addresses

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=177398

--- Comment #11 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
I opened the related bug #374768

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

[korganizer] [Bug 297769] Categories should be hierarchically organized

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=297769

--- Comment #3 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
To be continued on #374779

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

[korganizer] [Bug 374779] New: Categories should be hierarchically organized

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374779

Bug ID: 374779
   Summary: Categories should be hierarchically organized
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Reopening bug #297769 :
"Hierarchically higher categories could show their color in stripes

It would be nice to be able to organize categories hierarchically like in
Kmymoney.

For instance, you could assign "Work:Project Fury:Coding" to an event or a
task.
That way categorization would be much more precise.

Choosing which category color to display would be a bit more complicated, but
you could imagine having color stripes for each 'Work' and 'Project Fury'
categories on the left hand side of the event/task (see the attached mock-up,
where Work is in dark blue, Project Fury in green, and Coding in light blue)."

Still valid for v5.2.3.

Please see the attached file in the previous bug report.

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

[korganizer] [Bug 304726] A task that is overdue can't be dragged to a future hour on the same day it was due

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=304726

--- Comment #4 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
This bug is not present anymore in v5.2.3.

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

[kmail2] [Bug 250345] Ignore diacritic in quick search

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=250345

--- Comment #24 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Using v5.2.3, this bug is still present.

Having a message subject containing "Élévation", when you type 'elev' in the
filter bar, this message is not shown.

I couldn't found how to make the quickfilter on top of the folder list appears
again though.

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

[korganizer] [Bug 304839] Incidence editor doesn't let me save certain changes

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=304839

--- Comment #16 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
My bad, it still appears.

I'm not sure exactly how I managed to get to the point where such bug appears
though.

I was playing with a task end date/time (while having the start time
unchecked), and now when I edit the task end time (hour or minute), the 'apply'
button stays disabled.

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

[korganizer] [Bug 304839] Incidence editor doesn't let me save certain changes

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=304839

--- Comment #17 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
To be continued on #374777

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

[kmail2] [Bug 177398] paste multiple emaill addresses

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=177398

Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #10 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
This bug is still present in v5.2.3.

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

[korganizer] [Bug 374769] New: There is no more keyboard shortcut for editing the task/event category combobox or achievement slider element

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374769

Bug ID: 374769
   Summary: There is no more keyboard shortcut for editing the
task/event category combobox or achievement slider
element
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: incidence editors
  Assignee: korganizer-de...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

I reopen the bug #305207 that has been closed for lack of activity :

"Since a few korganizer version, to be exact since the last major ui change in
the incidence editor, you can't use any keyboard shortcut to select the
category combobox or the achievement slider (eg. on the French configuration
alt+i for accessing the title filed, alt+l for the place (cf. screencapture)).

Reproducible: Always

Steps to Reproduce:
1. Add a new task
2. using only your keyboard, try to directly access the category combobox
Actual Results:  
you can't.

Expected Results:  
Being able to use something like alt+c to put the focus on the category
combobox"

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

[korganizer] [Bug 305207] There is no more keyboard shortcut for editing the task/event category combobox or achievement slider element

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=305207

--- Comment #4 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Reopened as #374769

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

[korganizer] [Bug 374772] New: Events and tasks width or height aren't correctly set when there are some time conflicts

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374772

Bug ID: 374772
   Summary: Events and tasks width or height aren't correctly set
when there are some time conflicts
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: agendaview (weekview)
  Assignee: korganizer-de...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Created attachment 103292
  --> https://bugs.kde.org/attachment.cgi?id=103292=edit
Wrong layout in the bottom part of the agenda view

I reopen here the bug #305211 :

"Events and tasks width or height aren't correctly set when there are some time
conflicts. It's hard to explain with words, so please take a look at the
attached screen captures.

On the first one, the orange task should take half the width of the day, on the
second one, it's an hard one, but 'Test 3' and 'Test 1' shouldn't look like
that imho.

Reproducible: Always"

You can take a look at the initial screenshots in that bug report.
I update those with the latest v5.2.3 though.

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

[korganizer] [Bug 374774] New: When setting the completion level of a task to 100%, the expiration date isn't updated

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

Bug ID: 374774
   Summary: When setting the completion level of a task to 100%,
the expiration date isn't updated
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: incidence editors
  Assignee: korganizer-de...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

I reopen here the bug #297148 :
"Before 4.8, when setting the completion level to 100% in a task, the
expiration date was automatically set with the current date and time.
Using this 'expiration date' is the only way to visually set the task in the
agenda view. This way you can have a clear view of which tasks you accomplished
for a given period of time.

Please add back this feature !

Reproducible: Always

Steps to Reproduce:
see above"

The problem is still present in v5.2.3.

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

[korganizer] [Bug 297148] When setting the completion level of a task to 100%, the expiration date isn't updated

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=297148

--- Comment #3 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
To be continued on #374774

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

[korganizer] [Bug 304839] Incidence editor doesn't let me save certain changes

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=304839

--- Comment #15 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
I tried all the previous ways that made that bug appears, and indeed on v5.2.3,
it does not appear anymore.

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

[korganizer] [Bug 305211] Events and tasks width or height aren't correctly set when there are some time conflicts

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=305211

--- Comment #5 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
To be continued on #374772

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

[korganizer] [Bug 374777] New: Incidence editor doesn't let me save certain changes

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374777

Bug ID: 374777
   Summary: Incidence editor doesn't let me save certain changes
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: incidence editors
  Assignee: korganizer-de...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Reopened #374774:
"When making changes to an event or todo, KOrganizer doesn't recognize most
changes - and thus doesn't let you save them. The "Apply" button remains
disabled, and if you click "Okay", then your changes won't be saved. The
following changes will not be recognized: 
 - changes to time and date
 - changes to recurrance settings of the event
 - changes to reminders

Recognized changes: 
 - category
 - check boxes "all day" and "blocks me for other events" (sry retranslated
from German)

This means if you want your changes to take effect, you have to make changes to
the category or one of the check boxes. 

An example: Say you have a task set as a reminder to return books to the
library. You regularly repurpose this reminder depending on your due dates. Say
this reminder was last set to go off on July 12th. Now you want to set it to
August 15th. If you just change the date and press ok, your changes won't be
saved. Your reminder will still be set to July 12th. 

Reproducible: Always

Steps to Reproduce:
1. Edit an existing task or event
2. Edit either one of time, date, reminders or recurrance settings
3. See if the "Apply" button is active or not, and check if your changes are
saved when you press "Okay". 
Actual Results:  
Most changes aren't recognized and will not be saved, if you do not work around
with additional changes that will be recognized by the program. 

Expected Results:  
All changes to an incidence should be recognized and saved. 

I haven't checked what happens to changes in attendants, comments or
attachments (nor anything related to the journal editor), but it seems that
anybody working on this bug will easily figure these things out anyway. 

I'm marking this as major because it seriously decapacitates me almost any time
I change a task or event, and because it has a high risk of leading to data
loss, and thus renders the program unreliable for anyone who is not aware of
this bug. Of course the classification will be up to the maintainer. 

This happened with an ICAL calender (the default
.kde4/share/apps/korganizer/std.ics location) and the default internal mysql
akonadi backend. I had first noticed this bug in 4.8."

The bug is still present in v5.2.3.

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

[korganizer] [Bug 374780] New: Huge memory usage just for the calendar with korgac and ical resource

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374780

Bug ID: 374780
   Summary: Huge memory usage just for the calendar with korgac
and ical resource
   Product: korganizer
   Version: 5.2.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Reopened bug #329205 :
"At all time, I have 1 GiB of memory used by korganizer, korgac and
akonadi_ical_resource processes, and only 72 MiB of it is shared.

The main memory hog seems to come from a duplication between the korganizer and
korgac processes, respectively with 487 and 469 MiB used.

Here is my memory consumption using 4.11.2 :
Process | Memory | Shared memory | Virtual Memory
korganizer | 487.7 M | 31.0 M | 1.2 G
akonadi_ical_resource_1 | 5.0 M | 12.7 M | 308.4 M
akonadi_ical_resource_2 | 126.7 M | 13.5 M | 448.6 M
==> korgac | 469.0 M | 15.1 M | 1.0 G <==

The total memory usage for a single calendar is in my humble opinion far too
high (more than 1,088 GiB) for a 6.7 MiB ics file.
This is specially true for netbook users.

More history about this bug can be found in bug 314900.

Reproducible: Always"

The problem is still present in v5.2.3, to a lesser extent, but korganizer/pim
still uses way too much memory for not shown tasks/events, etc.

Updated grep commands :
`» grep BEGIN:VTODO calendrier.ics | wc -l
8553
» grep BEGIN:VJOURNAL calendrier.ics | wc -l
10
» grep BEGIN:VEVENT calendrier.ics | wc -l
5114
» grep BEGIN:JOURNAL calendrier.ics | wc -l 
0
» grep BEGIN:TODO calendrier.ics | wc -l
0
» grep BEGIN:EVENT calendrier.ics | wc -l   
0`

Memory usage :
korganizer : 209 Mio
korgac : 102 Mio
akonadi_ical_resource : 142 Mio
Total : 453 Mio of memory used...for a 6.6 Mio ics file.

Just to put that into perspective, that *68* time the size of the file on
disk!!


If you ask yourself why the numbers of events/tasks did not go up since 2013,
it's because the critical breaking bugs reported here are still present and
still prevents the normal use of Korganizer.

I do think Korganizer can revive from its ashes and get back the pre-2013
version functionalities, hence my recent testing here..

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

[Akonadi] [Bug 329205] Huge memory usage just for the calendar with korgac and ical resource

2017-01-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=329205

--- Comment #7 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
To be continued on #374780

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

[kmail2] [Bug 374768] Impossible to paste multiple email addresses

2017-01-15 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374768

--- Comment #4 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Ok so I tested once again, and if you copy then paste an email list from
LibreOffice into a text editor, you do get newlines between each emails, like
so :
```
f...@example.com
b...@example.com
"Foobar" <foo...@example.com>
```

I think those newlines should do the trick, right?

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

[dolphin] [Bug 306257] Add a feature so that we can save and restore a dolphin session

2017-03-12 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=306257

Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> changed:

   What|Removed |Added

   Platform|Ubuntu Packages |Debian testing
Version|2.1 |16.08.3

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

[akregator] [Bug 383404] New: The content pane does not respect the Breeze dark theme

2017-08-11 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=383404

Bug ID: 383404
   Summary: The content pane does not respect the Breeze dark
theme
   Product: akregator
   Version: 5.2.3
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Created attachment 107211
  --> https://bugs.kde.org/attachment.cgi?id=107211=edit
The bright white content pane

When using the dark theme from Breeze, all the akregator application colors
change correctly, apart from the content pane.

This is hard on the eyes.

Would it be possible to change the background-color and color attribute so that
it match the theme and the other panes?

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

[korganizer] [Bug 81781] An option to display all the months of the year in KOrganizer

2017-09-14 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=81781

Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #10 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
That would be great, but don't get your hopes up given the creation date ;)

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

[korganizer] [Bug 374777] Incidence editor doesn't let me save certain changes

2017-08-29 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374777

--- Comment #3 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
I just checked with version 5.2.3 again, from Debian stable 9.1, and this time
I was able to modify the time, date, recurrence and reminders and have my
changes saved when clicking 'Apply'.

I'm not sure what changed since last time I checked. Oh well..

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

[korganizer] [Bug 306944] Using the mousewheel to increment/decrement the dates

2017-09-26 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=306944

--- Comment #2 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Noice! :)

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

2017-09-01 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=283682

--- Comment #195 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Kmail version 5.2.3 (in Debian Stable) is definitely showing this bug (see the
attached screenshot).

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

2017-09-01 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=283682

--- Comment #196 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Created attachment 107642
  --> https://bugs.kde.org/attachment.cgi?id=107642=edit
Duplicated mails in Kmail 5.2.3

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

[amarok] [Bug 195368] Spreadsheet-like collection browser (at least for local collections)

2017-10-31 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=195368

Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #7 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Stop with this emotional rollercoaster!
Almost 10 years in waiting, please do not give us false hope ;)

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

[akregator] [Bug 383404] The content pane does not respect the Breeze dark theme

2018-03-22 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=383404

--- Comment #2 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Well, thanks for the hint.

I modified all the files there (that was needed otherwise some parts of
Akregator did not update), and there is no white flickers when changing pane!

The files :
https://gist.github.com/AlexandreBonneau/c41066e36191db7c135af7db3ccab9fa

To the maintainer; any news about fixing that in the near future?
(this does look like an easy one, but perhaps I'm mistaken)

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

[kwin] [Bug 296069] Walk Through Desktop layout rendering desktop previews

2018-10-19 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=296069

Alexandre Bonneau  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #4 from Alexandre Bonneau  ---
This is still unresolved in 5.13.5-1; there are still no previews shown when
switching desktop using the 'slide' effect.

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

[kwin] [Bug 296071] Drop BoxSwitch effect

2018-10-19 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=296071
Bug 296071 depends on bug 296069, which changed state.

Bug 296069 Summary: Walk Through Desktop layout rendering desktop previews
https://bugs.kde.org/show_bug.cgi?id=296069

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

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

[korganizer] [Bug 400043] New: Korganizer categories are broken; never stay selected, and duplicate themselves

2018-10-19 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=400043

Bug ID: 400043
   Summary: Korganizer categories are broken; never stay selected,
and duplicate themselves
   Product: korganizer
   Version: 5.9.1
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

To sum up, I have an old 2012 ics calendar created by Korganizer between 2005
up until the end of 2012, then all hell broke loose and Korganizer categories
got broken.

I was since then unable to use korganizer as before (ie. with correctly working
categories and categories' colors), but I now need to be able to use Korganizer
again.

The categories problem still exists 6 years after ; basically you cannot create
and use a category; it unselect itself when editing the event/task again, and
the category keeps duplicating itself when opening the category list.


STEPS TO REPRODUCE
I tested 3 things;
- with my old calendar and current settings,
- with my old calendar and a brand new user,
- with a new calendar and a new user.
In each case, the bug was there.


> With my old calendar and current settings
Note: my old calendar has 233087 lines and is 6.9MB big.
`grep VEVENT calendar.ics|wc -l` lists 11470 events.
`grep VTODO calendar.ics|wc -l` lists 17668 tasks.

1. Open Korganizer
2. Double-click an existing event with a 'Work' category to edit it (You know
this is a work event since it's color is correctly shown, and the tooltip does
show the correct Work category)
3. Select the 'click to add tags' button to open the categories window
4. See that the 'Work' category (or any other categories) are _unselected_
5. Additionally see that the 'Work' category is currently duplicated 5 times
6. Cry


> with my old calendar and a brand new user
1. Create a new user
2. Login with that new user
3. Open the brand new Korganizer
4. Create a new agenda and point it to the existing 6.9MB ics calendar file
5. Wait 1 hour and 45 minutes for akonadi/korganizer to finish 'importing' it
(Akonadi/Korganizer can only import 4.63 events/tasks per seconds, on my 12
core cpus, with 32GB of ram, really?! :/)
6. Go into the settings; there are NO categories shown in the color settings
(it looks like those are not imported during the...import)
6. Double-click an existing event you KNOW has the 'Work' category to edit it
7. Select the 'click to add tags' button to open the categories window
8. See that the 'Work' category just appeared in that list, but still is
_unselected_
9. Check the categories on another event (ie. 'Fun'), and see that the
categories list is now showing two unselected 'Work' and 'Fun' categories.
10. If you edit any Work event and check the categories list, then you can see
that the 'Work' category is duplicated 5+ times, but still all are unselected
10. Cry again


> with a new calendar and a new user
1. Create a new user
2. Login with that new user
3. Open the brand new Korganizer
4. Create a few new categories : 'Work', 'Fun', 'Soirée', 'Administrative work'
5. Create an event without categories
6. Create an event with the 'Work' category selected
7. Go into the settings to add a specific color to the 'Work' category (ie.
blue)
8. Check that in the agenda view, the 2nd event is correctly colored in blue
9. Double-click on that event (with the 'Work' category) to edit it
10. Click the button next to the falsely advertised placeholder 'click to add
tags' field, to open the categories window
11. See that the 'Work' category (or any other categories) are _unselected_
12. See that the 'Work' category is currently duplicated 2 times
13. Close those windows and re-edit the event then show the tag window; the
'Work' category has been duplicated again
14. Try to cry since you have no tears left


OBSERVED RESULT
Well, in all cases, the categories at utterly broken, even on a new Kde user
with a new agenda. (Is there any QA done for Korganizer?)


EXPECTED RESULT
Categories should :
1. Be listed directly instead of the 'Click here to add tags' placeholder
(separated by a comma), currently they are not and I imagine this is related to
this bug
2. Be correctly selected in the categories list, and stay selected between
edits
3. Accepts accentuated characters in their names without getting duplicated
4. Not be duplicated in the categories list


SOFTWARE VERSIONS
(info given by kinfocenter)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.49.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
I'm sad, does this help?
Let's hope this won't take 6 years again ;P
Do you need the original ics file? I tried anonymizing it using
https://github.com/collective/plone.app.eventindex/blob/master/anonical.py, but
that removes too much information (including the categories). Do you have a
script of your own to remove 

[kwin] [Bug 296069] Walk Through Desktop layout rendering desktop previews

2018-10-20 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=296069

--- Comment #6 from Alexandre Bonneau  ---
Well, you marked bug https://bugs.kde.org/show_bug.cgi?id=297139 as a
duplicated of this one, therefore I have difficulties seeing how this is not
related.

Does Kwin display miniatures of windows as desktop indicators when switching
desktops? Did I miss something?

If not, either reopen this bug, and remove the faulty duplicate resolution from
my initial report.

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

[dolphin] [Bug 171366] add bookmarks on dolphin

2019-05-14 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=171366

--- Comment #42 from Alexandre Bonneau  ---
Indeed, this is great!
Patience is a virtue ;D

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

[dolphin] [Bug 306257] Add a feature so that we can save and restore a dolphin session

2019-05-21 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=306257

--- Comment #13 from Alexandre Bonneau  ---
Dolphin already works like that, saving sessions automatically. This feature is
for saving and restoring manually, specifically.

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

2019-04-23 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=283682

--- Comment #210 from Alexandre Bonneau  ---
On my end, I'm currently using Kmail 5.9.3 (Debian buster), and am seeing no
duplicates using imap only.
Some very rare times I can see a few duplicates, but they disappear by
themselves pretty quicly.

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

[kmail2] [Bug 374768] Impossible to paste multiple email addresses

2019-12-02 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374768

--- Comment #5 from Alexandre Bonneau  ---
I tried again with Kmail XX and the following text:
```
f...@example.com
b...@example.com
"Foobar foo" 
```

When pasted, the newlines are ignored and all the text is used as is in a
single 'To:' field.
If you then select all the text in that field and paste it in a text editor, I
then see the newlines again!
The newlines could be used to 'explode' the email recipients.

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

[kmail2] [Bug 374768] Impossible to paste multiple email addresses

2019-12-02 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374768

--- Comment #6 from Alexandre Bonneau  ---
Kmail was v5.9.3 above.

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

[korganizer] [Bug 316352] Selecting categories like in Kmymoney

2019-12-02 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=316352

--- Comment #2 from Alexandre Bonneau  ---
This would also fix the bug in the category list bug when you type 'ab'
quickly, the first word starting with 'ab' is not selected.
You have to type 'a', wait a few ms, then 'b' to get the same behavior you have
in any list in kde.

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

[korganizer] [Bug 297766] Category colors should be shown in a list, not one by one

2019-12-02 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=297766

--- Comment #1 from Alexandre Bonneau  ---
Since the categories aren't editable from this screen, the list could be
static.
However there are not easy way to find where to edit those categories, so
perhaps there should be a shortcut to the tag editor window from there?

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

[korganizer] [Bug 297145] Add a visual indicator for the task priority

2019-12-02 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=297145

--- Comment #1 from Alexandre Bonneau  ---
Currently when you are using a remote calendar (which is I think the usual use
case), you get a globe icon on the far left of any event/tasks), which takes
place for not additional value if you only use one calendar.

Displaying that icon should be configurable, and the space gained there could
be used to display info with real value, like the task priority for instance.

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

[kmail2] [Bug 414782] New: Change the priority order of the text color

2019-12-02 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=414782

Bug ID: 414782
   Summary: Change the priority order of the text color
   Product: kmail2
   Version: 5.9.3
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

The great thing with Kmail is that you can manage a work flow with the
'Important', 'read/unread' and 'todo' tags.

However, the priority currently in which tags should color the message text are
in my opinion wrong.

Currently, when you set a message as important, the text color is red.
When you set a message as unread, the text color is blue.
And when you set a message as todo, the text color is green (on my
configuration at least).

Unfortunately, when you set the todo tag on an unread message, well, you can
only see the text as blue, not green.
If you have an important message that imply that an action is necessary,
setting the todo tag will not help since the color will stay red, not green.
If you receive a message, starts to read it but mid-way find out that it's an
important message that you will have to postpone reading for later, set in
unread again and set the important tag, no luck, the message color will stay
blue.

So currently the tag precedence are unread > important > todo.

I think it would be more useful to have the following precedence : todo >
important > unread.

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

[korganizer] [Bug 297144] Allow "Not busy" event to be overlapped by "Busy" event

2019-12-02 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=297144

--- Comment #1 from Alexandre Bonneau  ---
Also, the 'not busy' events could have their opacity set to 85% (ideally that
percentage should be configurable).

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

[korganizer] [Bug 297150] Add the ability to cancel _any_ changes (with ctrl+z)

2019-12-02 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=297150

--- Comment #1 from Alexandre Bonneau  ---
No proper undo history degrades the experience of using Korganizer.
Since sometimes if works, sometimes it doesn't, it makes the user fear using
the application and moving around the events and tasks.

Deletion, even on remote calendar, should be cancelable too (to a certain
point, of course).

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

[kmail2] [Bug 414782] Change the priority order of the text color

2019-12-16 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=414782

--- Comment #2 from Alexandre Bonneau  ---
It's true that ideally, you should be able to quickly know how messages are
marked.
However, just using bold/italic is not enough in my opinion to distinguish
marks between them, specially if you quickly browse your emails using the mouse
wheel to see if there are any outstanding TODOs.
Color in that case is more visible.

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

[korganizer] [Bug 415005] New: Korganizer do not synchronize tasks nor events with a remote nextcloud server

2019-12-09 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=415005

Bug ID: 415005
   Summary: Korganizer do not synchronize tasks nor events with a
remote nextcloud server
   Product: korganizer
   Version: 5.9.2
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Created attachment 124414
  --> https://bugs.kde.org/attachment.cgi?id=124414=edit
The log when starting Korganizer

SUMMARY
The Korganizer is 5.9.3, not 5.9.2 as specified in the bug report, since that
version was not present in the enumeration.

Since mid-august, korganizer/akonadi stopped synchronizing (both ways) my
remote caldav calendar (nextcloud).

STEPS TO REPRODUCE 1
1. Launch Korganizer
2. Create a task or event
3. That task/event is never synchronized to the remote server

STEPS TO REPRODUCE 2
1. Launch Korganizer
1. Create a task or event with the web calendar on the remote nextcloud server
2. Check that the task/event is correctly saved with another remote client (ex:
Etar on Android)
3. Launch Korganizer and wait a few days
3. That remote tasks and events are never synchronized from the remote server
anymore

EXPECTED RESULT
Synchronization should work both ways.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux version: Debian Buster (10.2), kernel 5.2.17
KDE Plasma Version: 5.14.5 
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
Check the attachment to see the log when starting Korganizer.
This bug is major since the tasks and events are only stored in one computer.
If a crash should occur, and if akonadi just decide to clear the cached
events/tasks (I speak from experience ; you can search for the same kind of bug
from 2013), the data will be LOST.
In my opinion, this is even borderline critical, since this on the edge of data
loss.

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

[kmail2] [Bug 417471] New: Add a new column with a new tag "check back later"

2020-02-11 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=417471

Bug ID: 417471
   Summary: Add a new column with a new tag "check back later"
   Product: kmail2
   Version: 5.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

In kmail there are two great features ; you can configure the columns shown to
display an icon for important messages, as well as an icon for the TODO tag.

Also, when you click those icons, you simply toggle the important/not important
state, or the TODO/DONE one.
When the important state is used, the mail text color is shown in red.
When the TODO tag is used, the mail text color is shown in green.

This is great, and allow an efficient workflow.


But that workflow could be improved with a small addition :
When you receive some mails, you often have a choice to make :
- The mail is basic information -> Read it directly and be done with it
- The mail contains information you need to act on -> Read it and set the TODO
tag (so you get a nice color you can identify easily while browsing your
previous mails to search for unfinished todos)
- The mail contains information that you worked on, then replied to with a
question of your own. -> Now, since some people are unreliable and may miss
your email, you WILL need to check later if you got an answer. To do that you
need to mark that initial email as "Check back later" (which could color the
text in pink for instance).
This way you know you _already have done the work_, but only need to ping again
the person you answered to.

This "Check back later" tag (name to be defined) is different than the "TODO"
one since a todo means some amount of work have to be done (and that take
time), while "Check back later" only needs you to resend a quick message like
"Hey, I haven't heard about you on this subject. Could you please get back to
me whenever you're available? xoxoxo".

This would go a long way to improve a mail management workflow, and be sure to
not miss anything (this is loosely based on the Get Things Done methodology).


Bonus :
Even better, when adding a 'check back later' tag to an email, it could
automatically create a task (like you can already do) and just asks for the
date and hour, the default calendar being configured somewhere else.
Right now once you created a task from kmail, you have no indication if a
particular email has tasks attached to it, or even if those tasks are done.

So the main purpose of this wish is to have a way to color an email with a one
click toggle like the TODO one.

Regards

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

[kmail2] [Bug 388155] Kmail shows duplicate emails - detect automatically on refresh?

2020-05-05 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=388155

Alexandre Bonneau  changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #1 from Alexandre Bonneau  ---
This sounds like an XY problem.
Instead of "automatically detecting and deleting" duplicates mails (I can
easily imagine how this could go wrong and delete lots of non-duplicated
mails), akonadi should strive to _not_ duplicate the mails in the first place!

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

[kmail2] [Bug 388155] Kmail shows duplicate emails - detect automatically on refresh?

2020-05-05 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=388155

--- Comment #2 from Alexandre Bonneau  ---
I'm adding a comment here instead of creating a new issue, since under Debian
Bullseye with akonadi and kmail version `4:19.08.3-1`, I'm getting mail
duplicates only in a very specific situation ;
If I open kmail on two different computers at the same time (ie. on my laptop
and my workstation).

If only one akonadi server is running on both computers, then everything is
fine.
However if I run akonadi server on both computers, everything goes haywire and
kmail starts spewing lots (LOTS!..in the hundreds) of duplicates mails.

I hope this helps figuring out any race condition that might happen.

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

2020-05-10 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=283682

--- Comment #226 from Alexandre Bonneau  ---
(In reply to Alexandre Bonneau from comment #210)
> On my end, I'm currently using Kmail 5.9.3 (Debian buster), and am seeing no
> duplicates using imap only.
> Some very rare times I can see a few duplicates, but they disappear by
> themselves pretty quicly.

For info (I posted that info in another related issue already), I found out
that I only get duplicates when I have 2 computers running akonadi-server.

For instance it happens when I'm on my main rig, then casually open my laptop.
Then mails are duplicated a lot...until I close one of the akonadi server
(usually the one from the laptop).

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

[korganizer] [Bug 415005] Korganizer do not synchronize tasks nor events with a remote nextcloud server

2020-08-25 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=415005

--- Comment #2 from Alexandre Bonneau  ---
For information after trying all the hacks and tricks I learnt using akonadi, I
couldn't find how to fix or work around that critical bug.

I had to remove the calendar resource, and recreate it from Nextcloud.
So far it works again.

All that points out the bug to, as always, akonadi and how it (badly) stores
data and/or manages errors it introduces.

This bug is still critical, a word from devs would be great!

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

[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers

2021-05-03 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=386985

Alexandre Bonneau  changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #52 from Alexandre Bonneau  ---
Well, the bug was 3,5 years ago, and is about not being able to sync events for
remote servers.
Considering having a centralized server for calendar events is the main way to
go for a few years now (with phones, etc.), this means Korganizer is useless.
This is not a 'grave' bug, this is a critical one, and must be dealt as one
(ie. not within a 3 years span).

Anyway, this bug just started happening under Debian Testing with kdepim
`4:20.08.3+5.111`, connecting to an up-to-date Nextcloud server (version 20).
You can create events in Korganizer and they will be synchronized onto
Nexcloud, but Korganizer won't update events/tasks from Nextcloud.

Again, this is a critical bug since it makes Korganizer useless.
If you have some spare time, please focus on this bug instead on any other.

Thank you for your time

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

[dolphin] [Bug 306255] Add an option to display tabs on multiple lines or display all the tabs in one line (with a variable width)

2021-03-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=306255

--- Comment #2 from Alexandre Bonneau  ---
This is still valid after 5 years.
Having the ability to display tabs on multiple lines would be handy.

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

[gwenview] [Bug 176698] no shortcuts for next/previous folder

2021-03-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=176698

--- Comment #6 from Alexandre Bonneau  ---
This is still valid after 12 years.

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

[Akonadi] [Bug 55835] Learn filter rules "automatically"

2021-03-08 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=55835

Alexandre Bonneau  changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #16 from Alexandre Bonneau  ---
Still valid after 18 years.

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

[korganizer] [Bug 374774] When setting the completion level of a task to 100%, the expiration date isn't updated

2021-09-20 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

Alexandre Bonneau  changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #6 from Alexandre Bonneau  ---
Created attachment 141714
  --> https://bugs.kde.org/attachment.cgi?id=141714=edit
Screenshot of categories

About the journal since it's a list, it's not visual enough for my use case, as
I use category colors a lot to differentiate the work I do (see the attached
screenshot of a 'light week') .


About the bug report, sorry, in my initial comment in 2017 I mentioned a poorly
translated 'expiration date', which should have been 'due date'.

Before Korganizer 4.8, when you set a task to 100% completion, then the due
date was automatically set to the current date and time.
This was very useful since you just had to change the completion to 100%, and
the tasks was then correctly displayed in the agenda view at the right time and
day.

Since 4.8 this behavior has changed ; now when you finish a task by setting its
completion to 100%, the due date is _not_ updated, therefore the task placement
(via the due date) in the agenda view is not updated.
In order to get the same behavior pre-4.8, you have to :
- Set the task completion to 100%
- Then set the due date manually (setting the exact time each time is a bit of
a pain)


I understand that there are 2 different date/time here:
- The completion date (set when the task is saved at 100% (by the way, does
that date gets updated if the tasks is set back to a value <100%, then again at
100% (in case of entry error)?)
- The due date (when the tasks is supposed to be done)

However while both completion and due dates are important information (to me at
least), only the due dates gets the attention of Korganizer:
- The tasks are displayed on their due date in the agenda view, and in the
task/event detail on the left
- The completion date is displayed, _but not the time_ in the task/event detail
on the left



One solution to this could be to allow the user to choose where the tasks
should be displayed ; either on their due dates, or on their completion date.
That way there wouldn't be a need to update the due date with the completion
date like before 4.8, in order for the tasks to be displayed at their
completion date.
All in all, it would be more logical.


In my opinion, both use case could be useful (and in my dreams I wish there
could be a way to view both the due and completion date in a way that shows you
how in advance or late you managed your tasks, but that's for another bug
report ;))

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

[korganizer] [Bug 374774] When setting the completion level of a task to 100%, the due date isn't updated

2021-09-20 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

Alexandre Bonneau  changed:

   What|Removed |Added

Summary|When setting the completion |When setting the completion
   |level of a task to 100%,|level of a task to 100%,
   |the expiration date isn't   |the due date isn't updated
   |updated |

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

[korganizer] [Bug 374774] When setting the completion level of a task to 100%, the expiration date isn't updated

2021-09-20 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

--- Comment #5 from Alexandre Bonneau  ---
Created attachment 141713
  --> https://bugs.kde.org/attachment.cgi?id=141713=edit
No icons showing when task is completed, with Breeze icon theme v5.78

Using Debian Bullseye with breeze-icon-theme version 4:5.78.0-2, I cannot see
the completed task icon shown in
https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/53

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

[korganizer] [Bug 374774] When setting the completion level of a task to 100%, the expiration date isn't updated

2021-09-17 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

--- Comment #2 from Alexandre Bonneau  ---
Would you know in which version this has been fixed?

I'm currently using `5.15.3` and it still exhibit the same problem (ie. not
setting the date/time to the current date and time when setting the tasks to
100% completion, like it did before).

About the completed to-do icon, when a task is completed I do see the
'not-found' icon instead on my Debian installation for years now.
I have no use for the journal.

My use case is that using a mix of the Get Things Done methodology and other
ones, I plan my day/week by putting my tasks at certain time in the following
day. When I complete a task, I want it to stay where(when really!) I completed
it, so that I can keep a clear view at one glance of what I did and when.
It's very useful for reporting to clients for instance, as well as organizing
your time.

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

[korganizer] [Bug 442937] New: The "Do you really want to cancel?" dialog is shown even when nothing have been changed in the event/tasks editor

2021-09-25 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=442937

Bug ID: 442937
   Summary: The "Do you really want to cancel?" dialog is shown
even when nothing have been changed in the event/tasks
editor
   Product: korganizer
   Version: 5.15.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: incidence editors
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Created attachment 141901
  --> https://bugs.kde.org/attachment.cgi?id=141901=edit
The annoying dialog

SUMMARY
A few versions back, Korganizer introduced the "Do you really want to cancel?"
dialog.
This dialog is supposed to be shown ONLY when you had unsaved/unapplied
modification to the opened event or task, however it's ALWAYS displayed even
when you just opened a task/event to take a quick look at it, without changing
anything.
This is _really_ annoying.


STEPS TO REPRODUCE
1. In the agenda view, double click on any existing event or tasks
2. The event or task window is shown
3. Do not change anything, then click cancel or hit 'Escape'

OBSERVED RESULT
A modal dialog showing the string "Do you really want to cancel?" is shown.

EXPECTED RESULT
No dialog should be shown, and the event/task window should be closed
immediately.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Bullseye / Kernel 5.10.0-8-amd64 / 4:5.20.5-6
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Korganizer version : 4:20.08.3-1

Do note that this is the same bug as in 2009 which has been resolved as fixed :
https://bugs.kde.org/show_bug.cgi?id=195734
https://bugs.kde.org/show_bug.cgi?id=181981
https://bugs.kde.org/show_bug.cgi?id=184570

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

[korganizer] [Bug 441846] Tags duplicated with copy an event

2021-09-30 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=441846

Alexandre Bonneau  changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #4 from Alexandre Bonneau  ---
I use Korganizer...a LOT. This is my main work tool to manage my time.
As such, I use Korganizer not once or twice a day, but constantly during my
day.

In my experience, copy/pasting events (which I do pretty often) does not lead
to tag duplication. (I could not tell for tasks, since I almost never
copy-paste those)
However, if I try to use the tag manager, then tags are created left and right.
Same if you use the tag color configuration window.
I think copy/pasting is not the problem, the tag manager and tag color
configuration window are.

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

[korganizer] [Bug 374774] When setting the completion level of a task to 100%, the due date isn't updated

2021-09-21 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

--- Comment #12 from Alexandre Bonneau  ---
I have a both type of screens, and in both my setup:
- on my laptop (usual 1920x1080),
- nor my 27" 4k screen,
the task icon is correctly shown, while the task-complete is not.
Global scaling is untouched at 100%.

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

[korganizer] [Bug 374774] When setting the completion level of a task to 100%, the due date isn't updated

2021-09-20 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

--- Comment #9 from Alexandre Bonneau  ---
# dLg breeze-icon-theme task-complete
/usr/share/icons/breeze/status/16/task-complete.svg
/usr/share/icons/breeze/status/22/task-complete.svg
/usr/share/icons/breeze-dark/status/16/task-complete.svg
/usr/share/icons/breeze-dark/status/22/task-complete.svg

# dlg breeze-icon-theme
ii  breeze-icon-theme  4:5.78.0-2   all  Default Plasma icon theme
ii  breeze-icon-theme-rcc  4:5.78.0-2   all  RCC resources for the breeze icon
theme

The task-complete.svg icon is only available in size 16 and 22, not 24. Perhaps
that's the cause of it not showing?

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

[korganizer] [Bug 374774] When setting the completion level of a task to 100%, the due date isn't updated

2021-09-20 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

--- Comment #10 from Alexandre Bonneau  ---
> Would it be helpful to put a "Completed Date" column in the To-do List view?  
> That view already has a category color swatch.

Perhaps, but since I have a LOT of tasks, and need to visualize them when they
will be dealt with, I do not use the task list, but the agenda view where it's
easier at a glance to see when you have have to do, and when you have some
'free time'.

I really think being able to choose how to display the tasks (either at the due
date, or completion date), could be the answer to the change of behavior after
v4.8.

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

[korganizer] [Bug 443335] New: Being able to create an event with a mouse selection through other events

2021-10-05 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=443335

Bug ID: 443335
   Summary: Being able to create an event with a mouse selection
through other events
   Product: korganizer
   Version: 5.18.1
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: agendaview (weekview)
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Today you can create an event by selecting a zone in the agenda view.
However it does not work well if you already have events/tasks already in place
when you want to create the event/task, since clicking on them then dragging
will just move them.

It would be great to be able to create an event/task at a specific place in the
agenda view using the mouse selection (so the starting time would be already
set), even if there was events/tasks there.

One way could be to use a modifier key when selecting the agenda view zone (for
instance `Shift`) ; that would instruct Korganizer to let the user select a
zone and pass through the other events at that specific timeframe.

Bonus effect; when selecting a zone that way, make all the tasks/events in the
agenda view 40% opacity, then back to 100% opacity when losing the
focus/unpress the mouse.

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

[korganizer] [Bug 294649] Creating a new incidence with a mouse selection through other incidences

2021-10-06 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=294649

--- Comment #5 from Alexandre Bonneau  ---
Perhaps this could be related, but the Marcus Bains line prevents clicking the
events/tasks behind it.
It should be made transparent to clicks too.

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

[korganizer] [Bug 442937] The "Do you really want to cancel?" dialog is shown even when nothing have been changed in the event/tasks editor

2021-09-25 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=442937

--- Comment #3 from Alexandre Bonneau  ---
Ok so I tried a few things:
- create a new event with no tags ; opening that event and cancelling work as
expected and does not show a warning. I then added a tag to that event, saved
it. Then opened it again and hit Esc ; no modial dialog
- I created a new event with a tag; opening that event and cancelling work as
expected and does not show a warning

- However when I open my existing events, the dialog is shown
(then the category color is removed (while the tag still exist (and is even in
double/triple in the tag list now. Well, I removed the duplicated tags, and
their color disappeared from the agenda view (while still being shown in the
tag color configuration window. I had to restart Korganizer for that color to
be shown again)

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

[korganizer] [Bug 442937] The "Do you really want to cancel?" dialog is shown even when nothing have been changed in the event/tasks editor

2021-09-25 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=442937

Alexandre Bonneau  changed:

   What|Removed |Added

   Platform|Debian stable   |Debian testing
Version|5.15.3  |5.18.1

--- Comment #2 from Alexandre Bonneau  ---
I upgraded from Debian Bullseye to Bookworm (the current testing), and with
Korganizer Version 5.18.1 (21.08.1), I unfortunately still see that behavior.

(Also, upgrading to 5.18.1 made it forgot the category colors when I double
click on an event, then hit Esc, and click "Yes I want to cancel")

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

[korganizer] [Bug 442937] The "Do you really want to cancel?" dialog is shown even when nothing have been changed in the event/tasks editor

2021-09-25 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=442937

--- Comment #4 from Alexandre Bonneau  ---
Ok this is not the relevant issue for this ticket, but the Tags management is a
huge mess.
I thought I was, one by one, defining the lost colors everytime I opened the
incidence editor of a previous element, but in fact Korganizer/akonadi was
creating new tags with the exact same name.
So when I open another old event with the same tag, it removes the color...then
I go change the color in the settings...then the tag is duplicated again :|

1. Duplicated names shouldn't be allowed for tags
2. When finding an ical CATEGORY, Korganizer/Akonadi should search if a color
has been set and use that, instead of not finding the already configured
tag/color, and forcing the user to create a duplicate.

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

[korganizer] [Bug 374774] When setting the completion level of a task to 100%, the due date isn't updated

2021-09-24 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374774

--- Comment #15 from Alexandre Bonneau  ---
I re-installed breeze-icon-theme using `apt install --reinstall
breeze-icon-theme`, ran `update-icon-caches /usr/share/icons/*`, they closed
and restarted kde and korganizer, and the icon is still missing from the agenda
view.

By the way, thanks for committing the change to display the time and hour for
the completion time Glen.

Though I still think being able to choose at which time tasks should be
displayed (either on completion date or due date) is the best way to solve this
current issue.

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

[korganizer] [Bug 374772] Events and tasks width or height aren't correctly set when there are some time conflicts

2021-09-26 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374772

--- Comment #1 from Alexandre Bonneau  ---
Also, specially with events, sometimes 2 events "fights" for being displayed on
top of the other, leading to a very quick blinking of one of the event, and a
100% CPU load.

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

[korganizer] [Bug 297150] Add the ability to cancel _any_ changes (with ctrl+z)

2021-07-23 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=297150

Alexandre Bonneau  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Alexandre Bonneau  ---
Well I just tested different actions and could undo all those I could think of.
Thanks !

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

[dolphin] [Bug 306255] Add an option to display tabs on multiple lines or display all the tabs in one line (with a variable width)

2021-07-27 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=306255

--- Comment #5 from Alexandre Bonneau  ---
Using the split view 100% of the time, having vertical tabs would be a massive
waste of space for my use case.

However I could understand why somebody would want that feature.
Maybe it should be created in a separated issue since it serves a different
purpose?

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

[korganizer] [Bug 474168] New: Display the Sequence number in the task/event detail pane

2023-09-04 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=474168

Bug ID: 474168
   Summary: Display the Sequence number in the task/event detail
pane
Classification: Applications
   Product: korganizer
   Version: 5.22.3
  Platform: Other
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: otherviews
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

In the .ics files, each VTODO, VEVENT and VJOURNAL have a SEQUENCE information,
which translate to the number of editions this particular element has seen.
It would be useful to show that number at the bottom of the Task/Event detail
pane after the 'Creation date', in italic, like `Revision: 12`.

Example in the .ics file:
```
SEQUENCE:12
```

Example of display in Korganizer detail pane:
```
[icon] Create a feature requests for Korganizer

Agenda: Calendar in Nextcloud
Starting date: Friday 28th april 2023 18:30:00 -10
Due date: Monday 4th of September 2023 14:30:00 -10
Duration: 128 days 20 hours
Description: This a task description...
...that can span multiple lines



..and paragraphs.
Tags: Computing, Misc
Pourcentage done : 0 %

Creation date: Monday 27th March 2023 08:30:04 -10
Revision: 12
```

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

[korganizer] [Bug 474169] New: Add an option for better managing unfinished tasks which have a passed due date

2023-09-04 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=474169

Bug ID: 474169
   Summary: Add an option for better managing unfinished tasks
which have a passed due date
Classification: Applications
   Product: korganizer
   Version: 5.22.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: agendaview (weekview)
  Assignee: kdepim-b...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Currently, the incomplete tasks that have a passed due date are moved at the
top of the weekview as soon as you 'force' an update of that weekview (i.e.
going to next week and back).

The positioning of the tasks are their due date is _critically important_ if
you want to be able to organize your days. Therefore, moving the unfinished
task to the current day is not good.

Now, since it's still not possible to select multiple tasks and move them in
one go, it means that if you fail to complete a bunch of tasks during the
previous days, all those unfinished tasks will be stacked at the top of the
current day, and if there are many:
- it can be very difficult and sometimes impossible to select one in particular
to be able to move it to another day in the future
- it's impossible to get an overview of which tasks were failed when in the
previous days, since they have been moved to the current day, whatever was
their due date

To circumvent this annoying behavior, it would be great to have an option:
- To keep this existing behavior (since it's has been like this for 17+ years)
- To keep the unfinished tasks at their due date/time place in the agenda view,
but color them in a specific way (without removing their tag color) and/or add
a very visible 'Due date passed'-icon. Perhaps here make the tasks background
hashed with a variation of the tag color?, or change the task opacity to 60%?
Which ever is best design-wise and that insure legibility.

The goal of this being to be able to get a clear view of what was missed, and
what needs to be rescheduled, and with an added benefit of being able to select
those tasks more easily.
Also in the future when we'll be able to select and move multiple tasks in one
go, it'll greatly help.

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

[kalzium] [Bug 457191] Kalzium crashes after clicking the Molecular Editor button

2023-09-11 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=457191

Alexandre Bonneau  changed:

   What|Removed |Added

 CC||en...@outlook.com

--- Comment #6 from Alexandre Bonneau  ---
*** Bug 473096 has been marked as a duplicate of this bug. ***

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

[kalzium] [Bug 473096] Molecues editor Crash every time when I clicked it.

2023-09-11 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=473096

Alexandre Bonneau  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #2 from Alexandre Bonneau  ---


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

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

[kmymoney] [Bug 462366] The currency conversion rate for EUR/XPF is wrong

2022-11-28 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=462366

Alexandre Bonneau  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |NOT A BUG

--- Comment #2 from Alexandre Bonneau  ---
Ok, my bad, it seems I have entered the 1000/8,38 ratio in both EUR -> XPF and
XPF -> EUR ratio.
This is fixed now.
Thanks for the hint.

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

[kmymoney] [Bug 462366] New: The currency conversion rate for EUR/XPF is wrong

2022-11-28 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=462366

Bug ID: 462366
   Summary: The currency conversion rate for EUR/XPF is wrong
Classification: Applications
   Product: kmymoney
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

SUMMARY
The currency conversion rate for EUR/XPF is wrong, leading to hugely wrong
dashboards and reports


STEPS TO REPRODUCE
1. You have an account with the total amount 680.056 XPF
2. In the value calculated in Euro is calculated to 81.152.267,14 € (this is
wrong)

The fixed ratio between EUR and XPF is equal to 1000/8,38 ~= 119,3317422.

OBSERVED RESULT & EXPECTED RESULT
When you have 680.056 XPF, you should do 680.056 / 119,33 ~= 5.698,86928€.
Currently Kmymoney does the inverse using 680.056 * 119,33  = 81.152.267,14 €.

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

[korganizer] [Bug 374779] Categories should be hierarchically organized

2022-11-15 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=374779

Alexandre Bonneau  changed:

   What|Removed |Added

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

--- Comment #3 from Alexandre Bonneau  ---
Yes, this is still a valid feature request.

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

[korganizer] [Bug 400043] Korganizer categories are broken; never stay selected, and duplicate themselves

2022-11-28 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=400043

Alexandre Bonneau  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #2 from Alexandre Bonneau  ---
Also in Korganizer 5.21.3.
The categories are still a pain to use; they still get duplicated, they still
are un-sorted, they still 'sometimes' decide to forget the color they were
assigned to, and they still aren't coherent between Korganizer and say, Kmail.

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

[akregator] [Bug 330472] ownCloud News App support

2023-11-14 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=330472

--- Comment #12 from Alexandre Bonneau  ---
It's always weird when a bug is closed as duplicate of a more recent one,
specially when there was more comments on the former, just saying.

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

[calligraplan] [Bug 481699] New: Plan crashes when trying to open a 2013 plan file in 2024

2024-02-22 Thread Alexandre Bonneau
https://bugs.kde.org/show_bug.cgi?id=481699

Bug ID: 481699
   Summary: Plan crashes when trying to open a 2013 plan file in
2024
Classification: Applications
   Product: calligraplan
   Version: 3.3.0
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dag.ander...@kdemail.net
  Reporter: alexandre.bonn...@linuxfr.eu
  Target Milestone: ---

Application: calligraplan (3.3.0)

Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.6.15-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 5.27.10 [CoredumpBackend]

-- Information about the crash:
Install a brand new calligraplan 1:3.3.0-2 on Debian Trixie (testing).
Try to open a plan created with calligraplan in 2013.

The app crashes.

I can post the plan file privately if needed.

The crash can be reproduced every time.

-- Backtrace:
Application: Plan (calligraplan), signal: Aborted

   PID: 1535014 (calligraplan)
   UID: 1000 (acid)
   GID: 1000 (acid)
Signal: 6 (ABRT)
 Timestamp: Thu 2024-02-22 11:16:56 -10 (19s ago)
  Command Line: /usr/bin/calligraplan
Executable: /usr/bin/calligraplan
 Control Group:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fcalligraplan-fd39862436104c94a70d52b7fa363493.scope
  Unit: user@1000.service
 User Unit:
app-\x2fusr\x2fbin\x2fcalligraplan-fd39862436104c94a70d52b7fa363493.scope
 Slice: user-1000.slice
 Owner UID: 1000 (acid)
   Boot ID: b404ca645c734eb78f2a5abe64506c34
Machine ID: 80bf05fa6a4f4e26a066dd73d081fa2b
  Hostname: AciD
   Storage:
/var/lib/systemd/coredump/core.calligraplan.1000.b404ca645c734eb78f2a5abe64506c34.1535014.170863661600.zst
(present)
  Size on Disk: 4.9M
   Message: Process 1535014 (calligraplan) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-255.3-2.amd64
Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64
Module libudev.so.1 from deb systemd-255.3-2.amd64
Stack trace of thread 1535014:
#0  0x7fb5d55c416c n/a (libc.so.6 + 0x8a16c)
#1  0x7fb5d5576472 raise (libc.so.6 + 0x3c472)
#2  0x7fb5d2c0d84d _ZN6KCrash19defaultCrashHandlerEi
(libKF5Crash.so.5 + 0x584d)
#3  0x7fb5d5576510 n/a (libc.so.6 + 0x3c510)
#4  0x7fb5d55c416c n/a (libc.so.6 + 0x8a16c)
#5  0x7fb5d5576472 raise (libc.so.6 + 0x3c472)
#6  0x7fb5d55604b2 abort (libc.so.6 + 0x264b2)
#7  0x7fb5d55603d5 n/a (libc.so.6 + 0x263d5)
#8  0x7fb5d556f3a2 __assert_fail (libc.so.6 + 0x353a2)
#9  0x7fb5b40624dc _ZN6KGantt12DateTimeGrid11setDayWidthEd
(libKGantt.so.2 + 0x5a4dc)
#10 0x7fb5b4386959
_ZN6KPlato13GanttViewBase11loadContextERK12KoXmlElement (libplanui.so.18 +
0x186959)
#11 0x7fb5b439250a n/a (libplanui.so.18 + 0x19250a)
#12 0x7fb5c59be9e3 _ZN6KPlato4View11createViewsEv
(libplanprivate.so.18 + 0xa69e3)
#13 0x7fb5c59beb35 _ZN6KPlato4View13initiateViewsEv
(libplanprivate.so.18 + 0xa6b35)
#14 0x7fb5d48f9940 _ZN7QObject5eventEP6QEvent
(libQt5Core.so.5 + 0x2f9940)
#15 0x7fb5d4d62f32
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 +
0x162f32)
#16 0x7fb5d54d3897
_ZN13KoApplication6notifyEP7QObjectP6QEvent (libplanmain.so.18 + 0x3b897)
#17 0x7fb5d48cc748
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 +
0x2cc748)
#18 0x7fb5d48cfe51
_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData
(libQt5Core.so.5 + 0x2cfe51)
#19 0x7fb5d4928697 n/a (libQt5Core.so.5 + 0x328697)
#20 0x7fb5d29111f4 n/a (libglib-2.0.so.0 + 0x571f4)
#21 0x7fb5d2914317 n/a (libglib-2.0.so.0 + 0x5a317)
#22 0x7fb5d2914930 g_main_context_iteration
(libglib-2.0.so.0 + 0x5a930)
#23 0x7fb5d4927d4a
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5 + 0x327d4a)
#24 0x7fb5d48cb0fb
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 +
0x2cb0fb)
#25 0x7fb5d48d38a4 _ZN16QCoreApplication4execEv
(libQt5Core.so.5 + 0x2d38a4)
#26 0x7fb5d571f19e kdemain (libkdeinit5_calligraplan.so +
0x319e)
#27 0x7fb5d55616ca n/a (libc.so.6 + 0x276ca)
#28 0x7fb5d5561785 __libc_start_main (libc.so.6 + 0x27785)

[dolphin] [Bug 306257] Add a feature so that we can save and restore a dolphin session

2016-06-05 Thread Alexandre Bonneau via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=306257

--- Comment #8 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
So, this bug is almost 4 years old, has 60 votes, 8 comments, a brainstorm
topic, one other bug marked as duplicated of it, and still has a status of
unconfirmed.
Why is that? :)

Is there any technical reasons why this seemingly basic feature could be hard
to implement?

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


[kiten] [Bug 360757] Extremely verbose log spam from GUI component to xsession-errors

2016-06-22 Thread Alexandre Bonneau via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360757

Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

--- Comment #1 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
I'm currently on Kubuntu 16.05 using the kubuntu-ppa backports
(http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial).
I do not have kiten installed, but I still have a 60 _millions_ line log with :
59484176 [character:baseIsStart] true Position( 0x0 "null" : 0 ) Position( 0x0
"null" : 0 )
59484177 
59484178 Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] Position( 0x0 "null"
: 0 ) Position( 0x0 "null" : 0 )
59484179 
59484180 Selection[ Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) 1 ] 0
...repeated over and over (the number at the start of the line in the line
number shown in vim).

Unfortunately, I have no way of knowing which app is causing that, since this
log is pretty useless.

The workaround so far :
`echo '' > .xsession-errors` every few days.
Also, that would explain why the plasmashell process is _always_ at 100% of one
cpu core.

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


[akregator] [Bug 330472] ownCloud News App support

2016-02-24 Thread Alexandre Bonneau via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=330472

Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> changed:

   What|Removed |Added

 CC||alexandre.bonneau@linuxfr.e
   ||u

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


[korganizer] [Bug 148136] Striped multi-colour entries (events, tasks) in Korganizer when the entry belongs to more then one cathegory

2016-08-22 Thread Alexandre Bonneau via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=148136

--- Comment #3 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Indeed, this is still a valid request, even 9 years after it was first posted
:)

The mixing of colors is in my opinion not a good idea, since you'll just happen
to get a rainbow colored weekview that way, with color not really corresponding
to the categories.

Perhaps you could reorganize quickly the current categories (which are still
broken by the way since 2013) with drag and drop. The very first category would
be the primary one, ie. its color fill the entire event.
BUT, you'd have colored dots for each other categories show somewhere in that
event.

What do you think about that?

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


[kmail2] [Bug 279516] Add a checkbox for selecting emails without reading its content.

2016-08-22 Thread Alexandre Bonneau via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=279516

--- Comment #4 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
Also, since it's still about selection emails without showing its
content/affecting its state, when you select a mail, then shift + click
another, the second mail content is shown and is marked as read, which is not
logical if you consider that the user is currently moving around mails (and do
not want to read them while doing so).

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


[korganizer] [Bug 76540] Select and operate on multiple events or to-dos

2016-08-22 Thread Alexandre Bonneau via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=76540

--- Comment #12 from Alexandre Bonneau <alexandre.bonn...@linuxfr.eu> ---
So it's been 12 and a half years.
Let's break a record and fix that for the next release! ;)

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