[neon] [Bug 489115] Screen sharing didn't work since 6.1 on Wayland (Chrome, Firefox, Discord, Teams, Zoom, Slack)

2024-07-04 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=489115

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #11 from Gaël de Chalendar (aka Kleag)  ---
Same problem. Commenting to be added to the CC list as I really need a working
screen sharing for my work.

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

[Discover] [Bug 487794] Cannot perform anny updates due to on broken package

2024-05-31 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=487794

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

   Platform|Other   |Neon
 Ever confirmed|0   |1
 CC||kle...@gmail.com
   Severity|normal  |major
   Priority|NOR |HI
 Status|REPORTED|CONFIRMED

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
I have the same problem since the same moment:

```
The following packages have unmet dependencies:
 libpipewire-0.3-modules : Depends: libpipewire-0.3-0 (= 1.0.7-1~ubuntu22.04)
but 1.0.7-3~ubuntu22.04 is installed
 pipewire-alsa : Depends: libpipewire-0.3-0 (= 1.0.7-1~ubuntu22.04) but
1.0.7-3~ubuntu22.04 is installed
 pipewire-bin : Depends: libpipewire-0.3-0 (= 1.0.7-1~ubuntu22.04) but
1.0.7-3~ubuntu22.04 is installed
 pipewire-jack : Depends: libpipewire-0.3-0 (= 1.0.7-1~ubuntu22.04) but
1.0.7-3~ubuntu22.04 is installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by
held packages.
E: Unable to correct dependencies
```

Here is the output when trying `apt --fix-broken install`:
```
root@brezhoneg:/etc/apt/sources.list.d# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies...Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following package was automatically installed and is no longer required:
  libkf5iconthemes-bin
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  libpipewire-0.3-modules pipewire pipewire-alsa pipewire-bin pipewire-jack
pipewire-pulse
Suggested packages:
  libpipewire-module-x11-bell
The following packages will be upgraded:
  libpipewire-0.3-modules pipewire pipewire-alsa pipewire-bin pipewire-jack
pipewire-pulse
6 upgraded, 0 newly installed, 0 to remove and 109 not upgraded.
39 not fully installed or removed.
Need to get 0 B/1478 kB of archives.
After this operation, 2048 B of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 654288 files and directories currently installed.)
Preparing to unpack .../libpipewire-0.3-modules_1.0.7-3~ubuntu22.04_amd64.deb
...
Unpacking libpipewire-0.3-modules:amd64 (1.0.7-3~ubuntu22.04) over
(1.0.7-1~ubuntu22.04) ...
dpkg: error processing archive
/var/cache/apt/archives/libpipewire-0.3-modules_1.0.7-3~ubuntu22.04_amd64.deb
(--unpack):
 trying to overwrite '/usr/share/man/man7/libpipewire-module-access.7.gz',
which is also in package pipewire-bin 1.0.7-1~ubuntu22.04
Errors were encountered while processing:
 /var/cache/apt/archives/libpipewire-0.3-modules_1.0.7-3~ubuntu22.04_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

```

Note that I have this in a apt list file:
```
deb https://ppa.launchpadcontent.net/pipewire-debian/pipewire-upstream/ubuntu/
jammy main
```

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

[kdevelop] [Bug 486789] New: Quick open drop down draws at the wrong place

2024-05-08 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=486789

Bug ID: 486789
   Summary: Quick open drop down draws at the wrong place
Classification: Applications
   Product: kdevelop
   Version: 5.13.240202
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI: QuickOpen
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

Created attachment 169322
  --> https://bugs.kde.org/attachment.cgi?id=169322&action=edit
The drop down menu in a popup window

SUMMARY
The Quick open drop down menu is drawn in a popup window instead of a menu
under its text entry when selected while the kdevelop window does not have the
focus.

STEPS TO REPRODUCE
1. Open a project in kdevelop
2. Select another window leaving the quick open drop down entry visible
3. Click the quick open drop down entry

OBSERVED RESULT
The menu is opened in a popup window

EXPECTED RESULT
The menu should be a drop down under the entry

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-28-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-1370P
Memory: 62.4 Gio of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: HP
Product Name: HP EliteBook 840 14 inch G10 Notebook PC
System Version: SBKPF

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

[neon] [Bug 482244] libkchart5-2 repeatedly fails to install.

2024-03-04 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=482244

--- Comment #3 from Gaël de Chalendar (aka Kleag)  ---
I confirm. The update was successful 2mn ago. For me, the bug can be closed.
Thanks.

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

[neon] [Bug 482244] libkchart5-2 repeatedly fails to install.

2024-03-03 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=482244

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
   Priority|NOR |HI
 Ever confirmed|0   |1
 CC||kle...@gmail.com

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
Same problem here using nala:

Fixing Broken Packages...
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
There are broken packages that need to be fixed!
You can use --no-fix-broken if you'd like to try without fixing them.

 Installing 

  Package:  Version:   
   
 Size:  
  libkchart5-2 
2.8.0+p22.04+vrelease+git20240302.0035-0   
363 KB  


 Summary

 Install 1 Packages 

 Disk space required  1.5 MB   

Do you want to continue? [Y/n] 
╭─ Updating Packages
──╮
│(Lecture de la base de données... (Lecture de la base de données...
100%(Lecture de la base de données... 647274 fichiers et répertoires déjà
installés.) │
│Préparation du dépaquetage de
/libkchart5-2_2.8.0+p22.04+vrelease+git20240302.0035-0_amd64.deb   
│
│Dépaquetage de libkchart5-2:amd64 (2.8.0+p22.04+vrelease+git20240302.0035-0)  
   
   │
│dpkg: erreur de traitement de l'archive
/var/cache/apt/archives/libkchart5-2_2.8.0+p22.04+vrelease+git20240302.0035-0_amd64.deb
(--unpack) :  │
│tentative de remplacement de « /usr/lib/x86_64-linux-gnu/libKChart.so.2.8.0 »,
qui appartient aussi au paquet libkchart2:amd64
2.8.0-1+22.04+jammy+release+build3 │
│dpkg-deb: erreur: coller subprocess was killed by signal (Broken pipe)
   
   │
│Des erreurs ont été rencontrées pendant l'exécution : 
   
   │
│/var/cache/apt/archives/libkchart5-2_2.8.0+p22.04+vrelease+git20240302.0035-0_amd64.deb
   
  │
│╭╮│
││⠹ Running dpkg …
╸
66.7% • 0:00:01 • 2/3││
│╰╯│
╰──╯
Error: Installation has failed.
If you'd like to file a bug report please include
'/var/log/nala/dpkg-debug.log'

Error: erreur de traitement de l'archive
/var/cache/apt/archives/libkchart5-2_2.8.0+p22.04+vrelease+git20240302.0035-0_amd64.deb
(--unpack) :
 tentative de remplace

[neon] [Bug 477706] Upgrade removed kdevelop and not installable anymore

2023-11-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=477706

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

--- Comment #4 from Gaël de Chalendar (aka Kleag)  ---
(In reply to Carlos De Maine from comment #3)
> turned out to be some pins holding back qtscript* packages. should be able
> to upgrade now

I confirm. It's OK now. Thanks.
BTW, what are "pins" in this context?

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

[neon] [Bug 477706] New: Upgrade removed kdevelop and not installable anymore

2023-11-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=477706

Bug ID: 477706
   Summary: Upgrade removed kdevelop and not installable anymore
Classification: KDE Neon
   Product: neon
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: kle...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1.  Update packages on 11/28/2023

OBSERVED RESULT
kdevelop has been removed and trying to reinstall it gives:
```
❯ LC_ALL=C sudo apt install kdevelop
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libkasten4okteta2controllers0:amd64 < none ->
5:0.26.13-0xneon+22.04+jammy+release+build12 @un puN Ib >
Broken libkasten4okteta2controllers0:amd64 Depends on libqt5script5:amd64 <
5.15.10+p22.04+vrelease+git20231007.0452-0 @ii K > (>=
5.15.11+p22.04+vrelease+git20231128.0855)
  Considering libqt5script5:amd64 12 as a solution to
libkasten4okteta2controllers0:amd64 0
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libkasten4okteta2controllers0 : Depends: libqt5script5 (>=
5.15.11+p22.04+vrelease+git20231128.0855) but
5.15.10+p22.04+vrelease+git20231007.0452-0 is to be installed
E: Unable to correct problems, you have held broken packages.
```

EXPECTED RESULT
Upgrade should not break the system

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
Kernel Version: 6.2.0-37-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-1370P
Memory: 62.4 Gio of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: HP
Product Name: HP EliteBook 840 14 inch G10 Notebook PC

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

[kdevelop] [Bug 475787] New: Session state should be saved more often

2023-10-18 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=475787

Bug ID: 475787
   Summary: Session state should be saved more often
Classification: Applications
   Product: kdevelop
   Version: 5.12.230802
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Session support
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY
I reuse the text from bug #191502 which was closed in 2009, but the same
problem still occurs.

KDevelop crashes frequently, unfortunaley.

This is only really annoying because the session state is only saved on clean
shutdowns, not on crashes.
This means I lose the state of opened files and open projects, and I think of
project configurations as well.
Please save those settings more often, preferably right after they changed, so
that the session can be cleanly restored after a crash.



STEPS TO REPRODUCE
1. Use kdevelop, open a project in a session, continue to use it some time
2. Make it or the computer crash
3. Restore the session

OBSERVED RESULT
The newly opened project has not been saved in the session before the crash.

EXPECTED RESULT
The session should be saved after successfully loading the project.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.2.0-34-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-1370P
Memory: 62.4 Gio of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: HP
Product Name: HP EliteBook 840 14 inch G10 Notebook PC

ADDITIONAL INFORMATION
Could also be related to bug #194998.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2023-10-18 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #17 from Gaël de Chalendar (aka Kleag)  ---
(In reply to Gaël de Chalendar (aka Kleag) from comment #16)
> Where should I put my merge request?

Just ignore that. I will make the necessary fork.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2023-10-17 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #16 from Gaël de Chalendar (aka Kleag)  ---
Hi, I (finally!) tried to made a merge request. I tried to to push to a branch
called `work/kleag/fortisslvpn-otp-only` as it seems to be the format used in
other merge requests but I was not allowed:
```
❯ git push origin work/kleag/fortisslvpn-otp-only
ERROR: Permission to KDE/plasma-nm.git denied to kleag.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
❯ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = g...@github.com:KDE/plasma-nm.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
```

Where should I put my merge request?

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

[Akonadi] [Bug 475462] New: "Ghost emails" : absent emails appearing as unread

2023-10-11 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=475462

Bug ID: 475462
   Summary: "Ghost emails" : absent emails appearing as unread
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: 5.24.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: EWS Resource
  Assignee: kdepim-b...@kde.org
  Reporter: kle...@gmail.com
CC: c...@carlschwan.eu, kri...@op.pl
  Target Milestone: ---

Created attachment 162217
  --> https://bugs.kde.org/attachment.cgi?id=162217&action=edit
screenshot

SUMMARY
"Ghost emails" : emails appearing as unread in Inbox or Trash for example while
there is no such. email. There is no such emails visible in the Microsoft
Exchange webmail.
I found the emails from trash in akonadiconsole but trying to delete them from
there just made them to be duplicated.
I cannot see any output related to this problem in akonadi output.


STEPS TO REPRODUCE
1. I don't know. It happens randomly


OBSERVED RESULT
"Ghost emails" : emails appearing as unread in Inbox or Trash (see attached
screenshot).

EXPECTED RESULT
No falsely unread emails

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.2.0-34-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-1370P
Memory: 62.4 Gio of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: HP
Product Name: HP EliteBook 840 14 inch G10 Notebook PC

ADDITIONAL INFORMATION

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

[kmail2] [Bug 475414] New: Ghost emails in Exchange account

2023-10-10 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=475414

Bug ID: 475414
   Summary: Ghost emails in Exchange account
Classification: Applications
   Product: kmail2
   Version: 5.24.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-b...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Configure a Exchange EWS account
2. Use it, for example deleting emails, sometimes in the Microsoft webmail

OBSERVED RESULT
Ghost emails appear in the folder list: unread emails are signaled in the
folders list while no unread email appear in the emails list and no unread
email are visible in the Microsoft webmail.
Trying to fsck or vacuum akonadi does not change anything. Forcing the upadte
of the folder does not work either. 

EXPECTED RESULT
No ghost message should be present.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.2.0-34-generic (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i7-1370P
Memory: 62.4 Gio of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: HP
Product Name: HP EliteBook 840 14 inch G10 Notebook PC

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

[Tokodon] [Bug 463696] System Tray Integration

2023-07-25 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=463696

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #4 from Gaël de Chalendar (aka Kleag)  ---
As a new user, I did not understand while this instant communication program
disappeared when I closed its window. I think that a way to keep it running
with possibly notifications for new messages would be great. I prefer not to
have too many apps in the taskbar. So, I agree with others that an integration
in the system tray would be great.

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

[kmail2] [Bug 433253] Folder list shows unread messages but filter doesn't

2023-07-04 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=433253

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

   Platform|Ubuntu  |Neon
 Status|REPORTED|CONFIRMED
Version|5.15.1  |5.23.2
 Ever confirmed|0   |1

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

[kmail2] [Bug 433253] Folder list shows unread messages but filter doesn't

2023-07-04 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=433253

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #2 from Gaël de Chalendar (aka Kleag)  ---
Created attachment 160071
  --> https://bugs.kde.org/attachment.cgi?id=160071&action=edit
Another occurrence of the bug

I also encounter this bug from time to time. Don't know how I made it disappear
previous times. Some random things with akonadi I suppose. The backend is EWS
connector.

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 5.19.0-46-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 31.2 Gio of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Latitude 5590

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

[basket] [Bug 469846] New: Cursor place should remain visible when typing

2023-05-16 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469846

Bug ID: 469846
   Summary: Cursor place should remain visible when typing
Classification: Applications
   Product: basket
   Version: unspecified
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: niccolo.venera...@gmail.com
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1.  Creates notes up to filling the screen

OBSERVED RESULT
The cursor disappears at the bottom of the screens while typing

EXPECTED RESULT
The line with the cursor should remain visible by sliding the window

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 31.2 Gio of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Latitude 5590

ADDITIONAL INFORMATION

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

[okular] [Bug 469664] Temporary freezing while editing form in pdf document

2023-05-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469664

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Resolution|UPSTREAM|FIXED

--- Comment #9 from Gaël de Chalendar (aka Kleag)  ---
Great. Thanks a lot for your quick actions.

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

[okular] [Bug 469664] Temporary freezing while editing form in pdf document

2023-05-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469664

--- Comment #7 from Gaël de Chalendar (aka Kleag)  ---
I built the master of poppler. Installed it in a local folder. Added its bin
and lib to PATH and LD_LIBRARY_PATH and started okular from this shell. The bug
seems to be effectively corrected.

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

[okular] [Bug 469664] Temporary freezing while editing form in pdf document

2023-05-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469664

--- Comment #5 from Gaël de Chalendar (aka Kleag)  ---
This has already been merged. Should I compile it and test it? If yes, how can
I retrieve the correct version?

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

[ksmserver] [Bug 469670] New: Windows should remember the desktops they are on between sessions

2023-05-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469670

Bug ID: 469670
   Summary: Windows should remember the desktops they are on
between sessions
Classification: Plasma
   Product: ksmserver
   Version: 5.27.5
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kle...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
When starting a session a have to place each window on the correct desktop(s).


STEPS TO REPRODUCE
1. Create several desktops
2. Open applications and put each of them on one or several desktop (either kde
apps like kontact or non-kde ones like firefox)
3. Close and reopen the session

OBSERVED RESULT
All windows are opened on the first desktop

EXPECTED RESULT
Each window should appear on each desktop it was previously

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 31.2 Gio of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Latitude 5590

ADDITIONAL INFORMATION

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

[okular] [Bug 469664] Temporary freezing while editing form in pdf document

2023-05-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469664

--- Comment #2 from Gaël de Chalendar (aka Kleag)  ---
In the attached file, it happens only in the largest text field.

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

[okular] [Bug 469664] Temporary freezing while editing form in pdf document

2023-05-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469664

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
Created attachment 158891
  --> https://bugs.kde.org/attachment.cgi?id=158891&action=edit
A file presenting the problem

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

[okular] [Bug 469664] New: Temporary freezing while editing form in pdf document

2023-05-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469664

Bug ID: 469664
   Summary: Temporary freezing while editing form in  pdf document
Classification: Applications
   Product: okular
   Version: 23.04.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Open a pdf file containing forms
2. Click "Display forms"
3. Try to edit text fiels

OBSERVED RESULT
Each key press takes more than 4 seconds to appear. If several keys are pressed
the window switches to the "unresponsive" state.

EXPECTED RESULT
Keys pressed should appear immediately. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: up to date KDE Neon
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version:  5.105.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION

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

[neon] [Bug 469599] Kontact and Kmail broken after upgrade to KDE 5.27.5, app is still there but will not open "Failed to register new cgroup, Process does not exist" error

2023-05-11 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=469599

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

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

[neon] [Bug 463947] Wrong dependencies make it impossible to update/install packages

2023-01-10 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=463947

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #9 from Gaël de Chalendar (aka Kleag)  ---
Got the same problem. Following advice from comments 6 and 8 solved the
problem.
Thanks.

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

[kate] [Bug 460749] New: Should not remove end of current line spaces when auto saving

2022-10-20 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=460749

Bug ID: 460749
   Summary: Should not remove end of current line spaces when auto
saving
Classification: Applications
   Product: kate
   Version: 22.08.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1.  Activate auto-save
2.  Activate trimming of end of line spaces on save
3.  Input some spaces at the end of a line
4.  Wait

OBSERVED RESULT
When auto save runs, the space characters at the end of current line are
removed.

EXPECTED RESULT
As this line is currently edited, the spaces should be kept. Current behavior
encourages  to type random chars in order to avoid to lose indenting when
editing python for example.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version:  
KDE Frameworks Version: 5.98.0
Qt Version:  5.15.6 

ADDITIONAL INFORMATION
Is it related to #112084 in kile?
This is not #310712 as this one is related to manual save with Ctrl+S which
must effectively remove the trailing spaces

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

[kdevelop] [Bug 460372] New: When a variable name or value is too large, its view in the debugger is hard to use

2022-10-13 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=460372

Bug ID: 460372
   Summary: When a variable  name or value is too large, its view
in the debugger is hard to use
Classification: Applications
   Product: kdevelop
   Version: 5.9.220802
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: CPP Debugger
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kle...@gmail.com
CC: niko.s...@gmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1.  Debug a C++ programm in kdevelop
2.  Stop and inspect variables

OBSERVED RESULT
If the variable name, type or value is very large, its column in the variables
view resizes to show the whole string. The other columns are then hard to reach
and view.

EXPECTED RESULT
The columns should be limited by the available place and a thin horizontal
scrollbar should be drawn into the corresponding cell. Or a drop down arrow to
show all the content in a popup text area.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
KDE Plasma Version: 
KDE Frameworks Version: 5.98.0
Qt Version: 5.16.0

ADDITIONAL INFORMATION

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

[dolphin] [Bug 451281] New: Usability: Set dolphin default folder depending on the activity

2022-03-08 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=451281

Bug ID: 451281
   Summary: Usability: Set dolphin default folder depending on the
activity
   Product: dolphin
   Version: 21.12.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: kle...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
I'd like that Dolphin would be opened in a default folder related to the
current Plasma Activity.

STEPS TO REPRODUCE
1. Go to Activity "A"
2. Open Dolphin

OBSERVED RESULT
Dolphin is opened in its default global location (home for me)

EXPECTED RESULT
Dolphin opened in a default folder related to Plasma Activity "A" set for
example in the Activity settings page.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3

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

[okular] [Bug 450310] New: Okular should adhere to Plasma activities

2022-02-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=450310

Bug ID: 450310
   Summary: Okular should adhere to Plasma activities
   Product: okular
   Version: 21.12.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY
***
Okular does not know Plasma activities.
***

STEPS TO REPRODUCE
1. Open okular on a Plasma activity with one or more files in tabs
2. Move to another activity
3. Open okular in any way (Alt-F2 + okular, click on a file, open a file from
konsole)

OBSERVED RESULT
We are moved to the first activity and the okular window on this activity is
activated (with the new file in a tab).

EXPECTED RESULT
A new okular Window in the current activity should be opened (except if the
previous one is already set to be visible on this activity too).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  KDE neon 5.24
(available in About System)
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
This is closely related to #442891 but maybe more general

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

[okular] [Bug 442891] When tabs are enabled, opening a document from a file manager in one activity opens the document in a tab on the other activity's Okular, irrespective of whether it is open on th

2021-11-22 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=442891

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||kle...@gmail.com

--- Comment #4 from Gaël de Chalendar (aka Kleag)  ---
Well, it seems that there is no support of activities in okular at all, so it
works with the default wm behavior. Now that I seriously switched to using
activities in my work, I'd like to see this feature implemented.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2021-05-31 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #14 from Gaël de Chalendar (aka Kleag)  ---
Created attachment 138895
  --> https://bugs.kde.org/attachment.cgi?id=138895&action=edit
New patch version necessary to be able to connect

I'm still obliged to apply this patch at each plasma-nm release to be able to
connect to my vpn.

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

[kdev-python] [Bug 436395] New: python breakpoint conditions are not applied

2021-04-30 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=436395

Bug ID: 436395
   Summary: python breakpoint conditions are not applied
   Product: kdev-python
   Version: 5.6.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@svenbrauch.de
  Reporter: kle...@gmail.com
CC: m...@svenbrauch.de
  Target Milestone: ---

SUMMARY
One cannot break on a given point using a condition.

STEPS TO REPRODUCE
1. Start a python debugging session on the following program
  1: for i in range(10):
  2: print(i)
2. Put a breakpoint on line 2, edit and validate the condition with: i==5
3. Press Continue

OBSERVED RESULT
The program stops on line 2 for each value of i.

EXPECTED RESULT
The program should stop only when i is 5.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-72-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 31.2 Gio of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

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

[kwin] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything

2021-03-03 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=411729

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #23 from Gaël de Chalendar (aka Kleag)  ---
Same problem here. The workaround of setting QT_IM_MODULE= in /etc/environment
works also.


localectl
   System Locale: LANG=fr_FR.UTF-8
   VC Keymap: n/a
  X11 Layout: fr
   X11 Model: pc105
 X11 Variant: latin9

KDE Neon up to date
KDE Frameworks 5.79.0
Qt 5.15.2 (construit sur 5.15.2)
Le système de fenêtres wayland

I have two keyboard settings in KDE (fr standard and fr bépo) and both behave
the same.

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

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

2021-03-02 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=397825

--- Comment #30 from Gaël de Chalendar (aka Kleag)  ---
Contrary to what I wrote above, it does not work or at least not perfectly.
Now, the basic workflow works (switching from mail to mail, from folder to
folder and also when coming from another application.

But it fails again when coming back from the Akregator panel in kontact. And
also when waking up from sleep. In both cases, closing kontact and reopening it
allows to use kmail normally again.

KDE Frameworks 5.79.0
Qt 5.15.2 (construit sur 5.15.2)
Le système de fenêtres wayland

5.16.2 (20.12.2)

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

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

2021-01-04 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=397825

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #25 from Gaël de Chalendar (aka Kleag)  ---
It also works for me now on KDE Neon stable

KDE Frameworks 5.77.0
Qt 5.15.2 (construit sur 5.15.2)
Le système de fenêtres xcb

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

[kwin] [Bug 430440] The "Show in Activities" menu does not work as expected

2020-12-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=430440

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

Summary|The Show is Activities menu |The "Show in Activities"
   |does not work as expected   |menu does not work as
   ||expected

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

[kwin] [Bug 430440] New: The Show is Activities menu does not work as expected

2020-12-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=430440

Bug ID: 430440
   Summary: The Show is Activities menu does not work as expected
   Product: kwin
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: activities
  Assignee: kwin-bugs-n...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Create two activities A and B
2. Open an application in activity A
3. Right-click on the window title bar and select "Show in activities" -> "B"

OBSERVED RESULT
The window now is displayed on both activities A and B

EXPECTED RESULT
The window should appear only on activity B. If I wanted to display it in all
activities, I would chose "All Activities" in the menu.

The current behavior forces me to do 2 times the same selections.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-56-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 31.2 Gio of RAM
Graphics Processor: llvmpipe

ADDITIONAL INFORMATION

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

[plasma-bigscreen] [Bug 430061] New: WiFi networks do not appear in the Connections plasmoid

2020-12-05 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=430061

Bug ID: 430061
   Summary: WiFi networks do not appear in the Connections
plasmoid
   Product: plasma-bigscreen
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Homescreen
  Assignee: notm...@gmail.com
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Flash mycroft-bigscreen-rpi4-20201126-arm64-BETA2.img to a microsd card
2. Boot my Raspberry400 computer (RPi4 based)
3. Click the WiFi setup icon

OBSERVED RESULT
An empty window with Refresh and Exit buttons

EXPECTED RESULT
Should list the available wifi networks

SOFTWARE/OS VERSIONS
mycroft-bigscreen-rpi4-20201126-arm64-BETA2

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

[kmail2] [Bug 413071] [Wayland] Kmail crashes when resized or maximized

2020-10-19 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=413071

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
   Severity|normal  |crash

--- Comment #4 from Gaël de Chalendar (aka Kleag)  ---
I confirm the problem. 

Not that before crashing, the mail pane on the lower right part stays black
(see the attachment). I don't know if the problems are related. I can open
another issue if needed.

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

[kmail2] [Bug 413071] [Wayland] Kmail crashes when resized or maximized

2020-10-19 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=413071

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #3 from Gaël de Chalendar (aka Kleag)  ---
Created attachment 132549
  --> https://bugs.kde.org/attachment.cgi?id=132549&action=edit
kmail on wayland screenshot

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

[kdevelop] [Bug 384791] Option for unbuffered output

2020-09-30 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384791

--- Comment #9 from Gaël de Chalendar (aka Kleag)  ---
(In reply to Gaël de Chalendar (aka Kleag) from comment #8)
> On my side, the problem appear when running python code. I just noticed that
> output of my python script is also buffered when running in a console like
> that:
>  
> $ python tracenn.py 2>&1 | tee output.log
> 
> Could it be a problem with the python interpreter itself?

Yes, it is:
https://stackoverflow.com/questions/107705/disable-output-buffering

When adding the -u flag to the script interpreter field of the launch
configuration, the output is no more buffered. 

Should it be added by default? Or detected and the user warned?

Well, with this new information, I'm not sure anymore that my bug #427128 is
really a duplicate of the current one.

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

[kdevelop] [Bug 384791] Option for unbuffered output

2020-09-30 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384791

--- Comment #8 from Gaël de Chalendar (aka Kleag)  ---
On my side, the problem appear when running python code. I just noticed that
output of my python script is also buffered when running in a console like
that:

$ python tracenn.py 2>&1 | tee output.log

Could it be a problem with the python interpreter itself?

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

[kdev-python] [Bug 427130] Variable browser is not complete when debugging pytorch tensor

2020-09-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=427130

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
I was able to display a tensor shape by adding a monitored variable

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

[kdevelop] [Bug 384791] Option for unbuffered output

2020-09-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384791

--- Comment #7 from Gaël de Chalendar (aka Kleag)  ---
I would mark this bug as important instead of normal. It is quite a show
stopper for using kdevelop for debugging, dont't you think.

Note that I noticed just after submitting #427128 that it does not always
occur: I was able to see the output of a debugged script with no delay while
the same output was buffered when just run.

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

[kdev-python] [Bug 427128] should not buffer python script run or debug output

2020-09-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=427128

--- Comment #3 from Gaël de Chalendar (aka Kleag)  ---
Side note: how did I miss the original bug which I duplicated? I searched
before submitting!

I currently work on a research project using AI for helping software
engineering, doing requirements traceability for example. Maybe I should add
bug duplicate detection as an important task to handle!

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

[kdev-python] [Bug 427130] New: Variable browser is not complete when debugging pytorch tensor

2020-09-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=427130

Bug ID: 427130
   Summary: Variable browser is not complete when debugging
pytorch tensor
   Product: kdev-python
   Version: 5.5.2
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Debug a pytorch-based python program
2. Try to navigate a tensor variable


OBSERVED RESULT
The tensor repr is correctly displayed but the tensor members (like its shape…)
cannot be viewed

EXPECTED RESULT
Like in pycharm (that I just tried while waiting for other problems with
kdevelop to be solved), tensor details should be accessible during debugging.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: KDE Neon
KDE Frameworks 5.69.0
Qt 5.12.8 (construit sur 5.12.8)

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

[kdevelop] [Bug 375602] Debug and run should save the current file when working in python

2020-09-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=375602

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
I confirm the problem with current 5.2.2 AppImage version.

C++ programs can be automatically built with saved sources when ran or
debugged. It should be the same for python project with custom build system
(without the build step, obviously).

(I put the status as CONFIRMED. Is it allowed or reserved for the developers
confirming the bug?)

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

[kdev-python] [Bug 427128] New: should not buffer python script run or debug output

2020-09-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=427128

Bug ID: 427128
   Summary: should not buffer python script run or debug output
   Product: kdev-python
   Version: 5.5.2
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User interface
  Assignee: m...@svenbrauch.de
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Setup a launch configuration to run the following script:
import time

for i in range(1):
print(i)
time.sleep(0.001)

2. Run/debug the launch configuration

OBSERVED RESULT
Outputs appear in batches each one or 2 seconds.

EXPECTED RESULT
As in a console, ran or debugged program output (even if stdout) should not be
buffered

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Frameworks 5.69.0
Qt 5.12.8 (construit sur 5.12.8)
KDE Neon

ADDITIONAL INFORMATION

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

[kdev-python] [Bug 426866] Cannot use variable browser in debugger

2020-09-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=426866

--- Comment #6 from Gaël de Chalendar (aka Kleag)  ---
In fact, running and debugging both work with the correct setting.

After setting the full path to my virtual env python interpreter in the
"Configure project" dialog, I tried to run and debug while keeping just
"python" as the "Script interpreter" in the "Launch configurations" dialog. And
it failed like described above.

After setting the full path to my virtual env python interpreter also in the
"Script interpreter" in the "Launch configurations" dialog, it now works
(running and debugging).

My two conclusions/wishes:
- when setting a full path to the python interpreter in the launch
configuration, it should become the default one in the launch configs
- there should be detection the start of kdevelop starting from a venv and a
explicit message to the user stating that it should start from the system one

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

[kdev-python] [Bug 426866] Cannot use variable browser in debugger

2020-09-24 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=426866

--- Comment #4 from Gaël de Chalendar (aka Kleag)  ---
Well, I can accept that even if it seems natural for me to start my ide from a
fully configured environment for the project. But in this case, there should be
detection of the problem and a explicit message to the user.

Here kdevelop is an AppImage. Does it include its python interpreter and the
tools or does it depends on the system ones? In the latter case, I should be
able to install the kdevelop system utilities in the venv, thus with pip or
anything else.

Finally, I tried, as you suggested, to start kdevelop from a clean environment
with no venv and setting the venv python interpreter at the project settings
level, but then the modules loaded in the venv cannot be found at runtime
(debugger):
ModuleNotFoundError: No module named 'torch'

Is there other settings to do?

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

[kdev-python] [Bug 426866] New: Cannot use variable browser in debugger

2020-09-22 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=426866

Bug ID: 426866
   Summary: Cannot use variable browser in debugger
   Product: kdev-python
   Version: 5.5.2
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: kle...@gmail.com
  Target Milestone: ---

Created attachment 131863
  --> https://bugs.kde.org/attachment.cgi?id=131863&action=edit
Screenshot of wrong message

SUMMARY


STEPS TO REPRODUCE
1. Create a python virtualenv and activate it
2. Start kdevelop AppImage from this environment
3. Start a debugger on a project and try to browse a variable on a checkpoint

OBSERVED RESULT
The variable value displayed is: *** NameError: name
'__kdevpython_debugger_utils' is not defined.

EXPECTED RESULT
One should see the variable value.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.0

Kdevelop AppImage:
KDE Frameworks 5.69.0
Qt 5.12.8 (construit sur 5.12.8)

ADDITIONAL INFORMATION
I cannot test that in the system's kdevelop because it crashes at me (issue
opened).

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

[kdevelop] [Bug 426561] Crash on startup while parsing python code

2020-09-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=426561

--- Comment #5 from Gaël de Chalendar (aka Kleag)  ---
Python 3.8.2

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

[kdevelop] [Bug 426561] Crash on startup while parsing python code

2020-09-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=426561

--- Comment #2 from Gaël de Chalendar (aka Kleag)  ---
Even after removing duchain cache and stopping background syntax analyzer, it
continues to crash.

Correction: after several restarts and several cache removing, it stopped to
crash.


When it crashed, messages in the console were:

Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
created new snippet repo
"/home/gael/.local/share/ktexteditor_snippets/data/Bash.xml"
SnippetRepository(0x55bbb316b110)
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed
kf.kio.widgets.kdirmodel: protocol mismatch: "" vs "file"
Cyclic dependency detected between
"file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
and
"file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
qrc:/qml/Develop.qml:139:21: QML Heading: Binding loop detected for property
"font.pointSize"
qrc:/qml/area_code.qml:87:9: QML Heading: Binding loop detected for property
"font.pointSize"
qrc:/qml/area_code.qml:63:9: QML Heading: Binding loop detected for property
"font.pointSize"
qrc:/qml/storage.js:24: TypeError: Cannot call method 'openDatabaseSync' of
undefined
kdevelop.plugins.python.duchain: tuple type object is not available
kdevelop.plugins.python.duchain:  [ !!! ] did not get a typetrack container
object when expecting one! Fix code / setup.
kdevelop.plugins.python.duchain:  [ !!! ] did not get a typetrack container
object when expecting one! Fix code / setup.
kdevelop.plugins.python.duchain: tuple type object is not available
kdevelop.plugins.python.duchain:  [ !!! ] did not get a typetrack container
object when expecting one! Fix code / setup.
kdevelop.plugins.python.duchain: tuple type object is not available
kdevelop.plugins.python.duchain: tuple type object is not available
kdevelop.plugins.python.duchain: tuple type object is not available
kdevelop.plugins.python.duchain: tuple type object is not available
python code checker error:
"/home/gael/.virtualenvs/pytorch/lib/python3.8/site-packages/pep8.py:110:
FutureWarning: Possible nested set at position 1\n  EXTRANEOUS_WHITESPACE_REGEX
= re.compile(r'[[({] | []}),;:]')\n"
remaining: 0 1075
kdevplatform.language: Could not open file
"/home/gael/.virtualenvs/pytorch/lib/python3.8/site-packages/torch/_C/__init__.py"
(path
"/home/gael/.virtualenvs/pytorch/lib/python3.8/site-packages/torch/_C/__init__.py"
)
OverflowError: Python int too large to convert to C long
kdevplatform.shell: Broken text-document: 
QUrl("file:///tmp/kdevelop_HfwQsq.patch")
qrc:/qml/storage.js:24: TypeError: Cannot call method 'openDatabaseSync' of
undefined
OverflowError: Python int too large to convert to C long
OverflowError: Python int too large to convert to C long
OverflowError: Python int too large to convert to C long
OverflowError: Python int too large to convert to C long
Unsupported _expr AST type:  37
Unsupported _expr AST type:  7500915
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 22 and type 'Read', disabling...
QSocketNotifier: Invalid socket 27 and type 'Read', disabling...
QSocketNotifier: Invalid socket 24 and type 'Read', disabling...
The X11 connection broke (error 1). Did the X11 server die?
ClassDeclarationData::baseClasses There were items left on destruction: 2208
ProblemData::diagnostics There were items left on destruction: 2629
DUContextData::m_uses There were items left on destruction: 29556

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

[kdevelop] [Bug 426561] Crash on startup while parsing python code

2020-09-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=426561

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
Created attachment 131676
  --> https://bugs.kde.org/attachment.cgi?id=131676&action=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[kdevelop] [Bug 426561] New: Crash on startup while parsing python code

2020-09-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=426561

Bug ID: 426561
   Summary: Crash on startup while parsing python code
   Product: kdevelop
   Version: 5.6.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

Application: kdevelop (5.6.0)

Qt Version: 5.15.0
Frameworks Version: 5.74.0
Operating System: Linux 5.4.0-47-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.19

-- Information about the crash:
- What I was doing when the application crashed:
Starting kdevelop. Waiting without doing anything that the sources parser
finish. Several python projects loaded and one LUA project.

- Custom settings of the application:
Just changed the environment, starting with a virtualenvwrapper initialized
with the modules used in a project loaded (numpy, torch, torchvision, spacy). 
Also activated every possible config elements in kdevelop code parsing
settings.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  0x7f816fda0d07 in Python::PythonAstTransformer::visitNode(_expr*)
(this=this@entry=0x7f8105ff97e0, node=0x1) at ./parser/generated.h:164
#5  0x7f816fda123a in Python::PythonAstTransformer::visitNode(_expr*)
(this=this@entry=0x7f8105ff97e0, node=0x7f80e8fea828) at
./parser/generated.h:323
#6  0x7f816fda315b in Python::PythonAstTransformer::visitNodeList<_expr,
Python::ExpressionAst>(asdl_seq*) (node=0x7f80e8fea7e0, this=0x7f8105ff97e0) at
./parser/generated.h:38
#7  Python::PythonAstTransformer::visitNode(_slice*)
(this=this@entry=0x7f8105ff97e0, node=) at
./parser/generated.h:513
#8  0x7f816fda1673 in Python::PythonAstTransformer::visitNode(_expr*)
(this=this@entry=0x7f8105ff97e0, node=0x7f80e8fea888) at
./parser/generated.h:354


Reported using DrKonqi

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

[neon] [Bug 426303] New: SSL Connect to MS Exchange autodiscover fails since 20.04

2020-09-08 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=426303

Bug ID: 426303
   Summary: SSL Connect to MS Exchange autodiscover fails since
20.04
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: kle...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Upgrade Neon to 20.04
2. Try to use previously working akonadi-ews based account in Kontact
3. Fail
4. Try to just connect to the autodiscover server
5. Fail
6. Ask colleagues to do the same on other distributions like Ubuntu 20.04.
Success for them

OBSERVED RESULT

I try to connect to the autodiscover server with openssl:
$ openssl s_client -connect autodiscover.XXX.XX:443
CONNECTED(0003)
depth=0 C = XX, O = XXX, OU = XXX, CN = mail.XXX.XX
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 C = XX, O = XXX, OU = XXX, CN = mail.XXX.XX
verify error:num=21:unable to verify the first certificate
verify return:1
140336653460800:error:141A318A:SSL routines:tls_process_ske_dhe:dh key too
small:../ssl/statem/statem_clnt.c:2149:
---
Certificate chain
 0 s:C = XX, O = XXX, OU = XXX, CN = mail.XXX.XX
   i:C = XX O = XXX, CN = X
---
Server certificate
-BEGIN CERTIFICATE-
…
-END CERTIFICATE-
subject=C = XX, O = XXX, OU = XXX, CN = mail.XXX.XX

issuer=C = XX O = XXX, CN = X

---
No client certificate CA names sent
---
SSL handshake has read 2038 bytes and written 318 bytes
Verification error: unable to verify the first certificate
---
New, (NONE), Cipher is (NONE)
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol  : TLSv1.2
Cipher: 
Session-ID: …
Session-ID-ctx: 
Master-Key: 
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1599555816
Timeout   : 7200 (sec)
Verify return code: 21 (unable to verify the first certificate)
Extended master secret: no
---


EXPECTED RESULT
It should be connected but it returns with return code 1.
On my colleagues computer, under Ubuntu 20.04 or older, it connects and does
not return.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION

Applying this change allows me to connect and to use the Exchange server, but I
don't know what are the consequences on the security of my system or my emails.

https://askubuntu.com/questions/1233186/ubuntu-20-04-how-to-set-lower-ssl-security-level

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

[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland

2020-06-03 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=422426

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

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

[Akonadi] [Bug 422410] New: EWS resource uses 100% CPU when its target server becomes inaccessible

2020-06-03 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=422410

Bug ID: 422410
   Summary: EWS resource uses 100% CPU when its target server
becomes inaccessible
   Product: Akonadi
   Version: 5.14.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: EWS Resource
  Assignee: kdepim-b...@kde.org
  Reporter: kle...@gmail.com
CC: kri...@op.pl
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Connect my vpn (fortisslvpn) to join my work network
2. Start kontact. Retrieve my Exchange mails 
3. Disconnect the VPN

OBSERVED RESULT

After a few minutes, two processes (akonadi_ews_resource and http.so) start to
use permanently a lot of CPU. E.g.:

84.2%cpu : http.so [kdeinit5] https
local:/run/user/1000/klaunchergmjaHQ.1.slave-socket
local:/run/user/1000/akonadi_ews_resource_1jeKEmF.20.slave-socket
47.1%cpu : akonadi_ews_resource --identifier akonadi_ews_resource_1

I have to stop akonadi for my laptop temperature go down.

EXPECTED RESULT

EWS resource should stay quiet even if its server becomes unavailable?


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION

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

[kactivitymanagerd] [Bug 348012] Opening files arbitrarily switches to other Activities

2020-05-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=348012

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #3 from Gaël de Chalendar (aka Kleag)  ---
I confirm the problem. I wanted to report it but this bug report is very
comprehensive. I'm myself usually annoyed by pdf files downloaded from Firefox
opening in my Work activity even if I'm currently in the Home one.

This is quite annoying.

If the problem comes from applications, even if this bug is in
kactivitymanagerd, then the application maintainers should be aware of the bug.
Is there hash tags we could add for example?

Or maybe should we open bug reports on each application and make this one a
duplicate?

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

[Akonadi] [Bug 363928] After suspend akonadiserver use about 2 cpus

2020-05-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=363928

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #9 from Gaël de Chalendar (aka Kleag)  ---
I have the same problem since a very long time (I should have reported it
earlier). I'm on an up to date KDE Neon:

Operating System: KDE neon 5.18
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.3.0-51-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz
Memory: 31,2 Gio

My PC stays usable because I have 8 cores. But it's getting hot and it draws
the battery very quickly when not plugged in.

My .xsession-errors shows a continuous stream of
org.kde.pim.akonadi_indexer_agent: Xapian error in indexer 0x55f584d189d0 : Db
block overwritten - are there multiple writers?
org.kde.pim.akonadiserver: ItemRetrievalJob for request 0x7f2fec02ef70 finished
org.kde.pim.akonadi_indexer_agent: Xapian error in indexer 0x55f584d189d0 : Db
block overwritten - are there multiple writers?
org.kde.pim.akonadiserver: ItemRetrievalJob for request 0x7f2fec043d90 finished
org.kde.pim.akonadi_indexer_agent: Xapian error in indexer 0x55f584d189d0 : Db
block overwritten - are there multiple writers?

Around one by second.

I have one akonadi_ews_resource to an exchange server, two calendars and a
large maildir local archive.

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

[Akonadi] [Bug 418804] Indexing agent crash

2020-03-13 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=418804

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
*** Bug 418803 has been marked as a duplicate of this bug. ***

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

[Akonadi] [Bug 418803] Index

2020-03-13 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=418803

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
Submitted by error with an incomplete title.

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

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

[Akonadi] [Bug 418804] New: Indexing agent crash

2020-03-13 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=418804

Bug ID: 418804
   Summary: Indexing agent crash
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Indexer
  Assignee: kdepim-b...@kde.org
  Reporter: kle...@gmail.com
CC: chrig...@fastmail.fm, dvra...@kde.org
  Target Milestone: ---

Application: akonadi_indexing_agent (5.13.3 (19.12.3))

Qt Version: 5.14.1
Frameworks Version: 5.67.0
Operating System: Linux 5.3.0-40-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.18

-- Information about the crash:
- What I was doing when the application crashed:
I moved all my 2019 mails by drag and drop from the Microsoft Exchange server
of my work to my local maildir (?) mails , for archiving. It seemed to work but
now akonadi crashes after a few seconds or minutes. I have to leave my session
and reopen it to be able to restart it.  Otherwise, "akonadictl start" waits
some times and then says:

org.kde.pim.akonadiserver: Failed to connect to database!
org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server
through socket '/run/user/1000/akonadi/mysql.socket' (2) QMYSQL: Unable to
connect"
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/run/user/1000/akonadi/mysql.socket' (2)'
Check that mysqld is running and that the socket:
'/run/user/1000/akonadi/mysql.socket' exists!


- Custom settings of the application:
Using akonadi_ews_resource

The crash can be reproduced every time.

-- Backtrace:
Application: akonadi_indexing_agent (akonadi_indexing_agent), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa95c034380 (LWP 7757))]

Thread 4 (Thread 0x7fa93bfff700 (LWP 7836)):
#0  0x7fa9577b0bf9 in __GI___poll (fds=0x7fa9300029e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fa9524ee5c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa9524ee6dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa95832f0db in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa9582ce63a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa9580df317 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa9580e07ec in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa9542566db in start_thread (arg=0x7fa93bfff700) at
pthread_create.c:463
#8  0x7fa9577bd88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fa940dc6700 (LWP 7835)):
#0  0x7fa9577ac0b4 in __GI___libc_read (fd=6, buf=0x7fa940dc5a20,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fa9525332d0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa9524ee0b7 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa9524ee570 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa9524ee6dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa95832f0db in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa9582ce63a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa9580df317 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa9587bb555 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7fa9580e07ec in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fa9542566db in start_thread (arg=0x7fa940dc6700) at
pthread_create.c:463
#11 0x7fa9577bd88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fa946697700 (LWP 7783)):
#0  0x7fa9577b0bf9 in __GI___poll (fds=0x7fa946696b68, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fa94c4f3747 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fa94c4f536a in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fa949065cc0 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fa9580e07ec in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa9542566db in start_thread (arg=0x7fa946697700) at
pthread_create.c:463
#6  0x7fa9577bd88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fa95c034380 (LWP 7757)):
[KCrash Handler]
#6  0x7fa9576dae97 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7fa9576dc801 in __GI_abort () at abort.c:79
#8  0x7fa957d31957 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x7fa957d37ae6 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7fa957d37b21 i

[Akonadi] [Bug 418803] New: Index

2020-03-13 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=418803

Bug ID: 418803
   Summary: Index
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Indexer
  Assignee: kdepim-b...@kde.org
  Reporter: kle...@gmail.com
CC: chrig...@fastmail.fm, dvra...@kde.org
  Target Milestone: ---

Application: akonadi_indexing_agent (5.13.3 (19.12.3))

Qt Version: 5.14.1
Frameworks Version: 5.67.0
Operating System: Linux 5.3.0-40-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.18

-- Information about the crash:
- What I was doing when the application crashed:
I moved all my 2019 mails by drag and drop from the Microsoft Exchange server
of my work to my local maildir (?) mails , for archiving. It seemed to work but
now akonadi crashes after a few seconds or minutes. I have to leave my session
and reopen it to be able to restart it.  Otherwise, "akonadictl start" waits
some times and then says:

org.kde.pim.akonadiserver: Failed to connect to database!
org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server
through socket '/run/user/1000/akonadi/mysql.socket' (2) QMYSQL: Unable to
connect"
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket
'/run/user/1000/akonadi/mysql.socket' (2)'
Check that mysqld is running and that the socket:
'/run/user/1000/akonadi/mysql.socket' exists!


- Custom settings of the application:
Using akonadi_ews_resource

The crash can be reproduced every time.

-- Backtrace:
Application: akonadi_indexing_agent (akonadi_indexing_agent), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa95c034380 (LWP 7757))]

Thread 4 (Thread 0x7fa93bfff700 (LWP 7836)):
#0  0x7fa9577b0bf9 in __GI___poll (fds=0x7fa9300029e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fa9524ee5c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa9524ee6dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa95832f0db in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa9582ce63a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa9580df317 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa9580e07ec in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa9542566db in start_thread (arg=0x7fa93bfff700) at
pthread_create.c:463
#8  0x7fa9577bd88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fa940dc6700 (LWP 7835)):
#0  0x7fa9577ac0b4 in __GI___libc_read (fd=6, buf=0x7fa940dc5a20,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7fa9525332d0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa9524ee0b7 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa9524ee570 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa9524ee6dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa95832f0db in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa9582ce63a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa9580df317 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa9587bb555 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7fa9580e07ec in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fa9542566db in start_thread (arg=0x7fa940dc6700) at
pthread_create.c:463
#11 0x7fa9577bd88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fa946697700 (LWP 7783)):
#0  0x7fa9577b0bf9 in __GI___poll (fds=0x7fa946696b68, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fa94c4f3747 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fa94c4f536a in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fa949065cc0 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fa9580e07ec in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa9542566db in start_thread (arg=0x7fa946697700) at
pthread_create.c:463
#6  0x7fa9577bd88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fa95c034380 (LWP 7757)):
[KCrash Handler]
#6  0x7fa9576dae97 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#7  0x7fa9576dc801 in __GI_abort () at abort.c:79
#8  0x7fa957d31957 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x7fa957d37ae6 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7fa957d37b21 in  () at /usr/l

[KScreen] [Bug 416976] Regression: Screens should not be hidden in display configuration of systemsettings

2020-02-03 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=416976

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Resolution|INTENTIONAL |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #3 from Gaël de Chalendar (aka Kleag)  ---
I know that you can access disabled screens using the screen chooser combobox,
even if it was hard to discover.

I think that your reasoning here is a logician one, not a user perspective.
When its screen is plugged in, the user (me) wants to see it available in the
preview area. The grayed out solution I suggested if my report would work I
think, but a more explicit possibility would be to add a zone dedicated to
not-activated screens as in the mockup I have attached.

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

[KScreen] [Bug 416976] Regression: Screens should not be hidden in display configuration of systemsettings

2020-02-03 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=416976

--- Comment #2 from Gaël de Chalendar (aka Kleag)  ---
Created attachment 125640
  --> https://bugs.kde.org/attachment.cgi?id=125640&action=edit
Suggested presentation of unactivated screens

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

[systemsettings] [Bug 416977] New: Several display configurations should be saved

2020-01-31 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=416977

Bug ID: 416977
   Summary: Several display configurations should be saved
   Product: systemsettings
   Version: 5.17.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY
At work, I use two external screens connected to a dock and keep the lid of my
laptop closed. When I reconnect it, external screens configuration is always
lost and must be set again. 

STEPS TO REPRODUCE
1. Connect two screens and a laptop to a dock
2. Prepare the screen configuration you like
3. Disconnect the laptop and come back later
4. Go to Step 2 and repeat

OBSERVED RESULT
Configuration is not saved

EXPECTED RESULT
Configuration should be saved.

As screens are identified individually, I think that several configurations
could be saved and the most appropriate one automatically selected or at least
proposed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 416976] New: Regression: Screens should not be hidden in display configuration of systemsettings

2020-01-31 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=416976

Bug ID: 416976
   Summary: Regression: Screens should not be hidden in display
configuration of systemsettings
   Product: systemsettings
   Version: 5.17.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kle...@gmail.com
  Target Milestone: ---

Created attachment 125566
  --> https://bugs.kde.org/attachment.cgi?id=125566&action=edit
In the attached screenhot the SyncMaster screen is not activated and thus not
visible while it should.

SUMMARY


STEPS TO REPRODUCE
1. Plug-in a second screen
2. Open the Display configuration section of systemsettings5
3. Uncheck the "Enabled" check box for this screen

OBSERVED RESULT
The disabled screen is not visible in the area where screens position is
visible

EXPECTED RESULT
The disabled screen should be visible but grayed as previously. The current
behavior is not easy at all. If one don't now that the "Settings for" label is
a drop down, it can be missed. And anyway, having to drop it down and search
for the right external monitor in the list is not easy. Just clicking on its
grayed representation would be easier.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: up-to-date Neon 
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION
In the attached screenhot the SyncMaster screen is not activated and thus not
visible while it should.

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

[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet

2020-01-20 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=393002

--- Comment #16 from Gaël de Chalendar (aka Kleag)  ---
I used again the workaround I explained above, but this time, the akonadi
resource name changed. I used akonadiconsole to find the new name.

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

[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)

2020-01-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=373907

--- Comment #28 from Gaël de Chalendar (aka Kleag)  ---
I subscribed to the Phabricator task. Again, I will not be able to switch from
X11 without that feature.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-19 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kle...@gmail.com

--- Comment #12 from Gaël de Chalendar (aka Kleag)  ---
Created attachment 124581
  --> https://bugs.kde.org/attachment.cgi?id=124581&action=edit
Update of the patch fixing the use of OTP password

This version of the patch forces to password field to take the same value as
the OTP one. This allows me to connect to my VPN.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-18 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #11 from Gaël de Chalendar (aka Kleag)  ---
I tried the patch. It does what is announced but I then get an error:

  [1576659928.7261]
vpn-connection[0x55bc68a086d0,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"VPNCEA",0]:
VPN connection: failed to connect: 'Mot de passe VPN manquant ou non valide.'

which translates to: "VPN password missing or invalid"

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-16 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #9 from Gaël de Chalendar (aka Kleag)  ---
It was a little bit difficult due to various version issues but I was able to
connect to my VPN with the Plasma plugin. Thanks!

There is 3 little problems though. I put them below, but maybe should I open
new bug reports?

- I had to manually set internal name server IPs in the IPv4 configuration box,
while they are automatically set when using the commandline client;
- As you can see in the attachments, the password dialog shows two fields
instead of the OTP one only. And both has to be filled for the connection to
work;
- The OTP is visible in clear by default. But the OTP generated by my hardware
token is completed by a PIN code (not shown in the screenshot :-) ). This
should be hidden.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-16 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #8 from Gaël de Chalendar (aka Kleag)  ---
Created attachment 124528
  --> https://bugs.kde.org/attachment.cgi?id=124528&action=edit
Passwords problem as described in the bug report comment

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #5 from Gaël de Chalendar (aka Kleag)  ---
Hum, sorry. It is marked as connected but the connection does not work. Servers
inside the domain do not answer.

I'll try to find what happens later. I have to join a meeting right now.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #4 from Gaël de Chalendar (aka Kleag)  ---
I was finally able to connect by doing so:

- install the current master of openfortivpn
- force the install of network-manager-fortisslvpn_1.2.8-1ubuntu1_amd64.deb
- in the plasma configuration GUI, set a fake password stored in clear for all
users and ask fort a one time password
- in the connect dialog, set my one time password BOTH in the password field
AND in the OTP field.

Note the putting a fake password in the password field of the connect dialog
did not work either.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #3 from Gaël de Chalendar (aka Kleag)  ---
Well, in fact, I was wrong about the port. 443 is the default HTTPS port and
seems to be the default in new versions of [1] (current github version is
1.11.0). In the version used on KDE Neon (1.6.0), setting the port in the
configuration file was mandatory.

BTW, an empty password field was also mandatory in the configuration file even
when using one-time passwords. It is not anymore, it seems. But this is
probably not interesting for my current pb with the plasma openfortivpn nm
applet.

I tried with the latest openfortivpn version and got different errors:

NetworkManager[1060]:   [1576139547.1460]
settings-connection[0x561b296e4b60,2a77d541-0d9e-417e-9f47-d3efda16f6ff]:
write: successfully updated (keyfile: update
/etc/NetworkManager/system-connections/XXX
(2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX")), connection was modified in the
process
NetworkManager[1060]:  [1576139547.1495]
vpn-connection[0x561b29724390,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
final secrets request failed to provide sufficient secrets

The /etc/NetworkManager/system-connections/XXX content is:
[connection]
id=XXX
uuid=2a77d541-0d9e-417e-9f47-d3efda16f6ff
type=vpn
permissions=user:xxx:;

[vpn]
gateway=
otp-flags=2
password-flags=2
trusted-cert=xxx
user=XYZ
service-type=org.freedesktop.NetworkManager.fortisslvpn

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto



[1] https://github.com/adrienverge/openfortivpn

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-09 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

--- Comment #2 from Gaël de Chalendar (aka Kleag)  ---
Well, in fact, I'm not sure that the problem comes from the port, as I was not
able to get a clear error message.

What makes me think it could be the port is that in the commandline tool config
file, the port is separated and that if I am following the code correctly, the
gateway field value is directly sent to a QHostAddress which has nothing to
handle ports.

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

[plasma-nm] [Bug 414975] The openfortivpn plugin does not allow to set gateway port

2019-12-09 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

   Platform|Other   |Neon Packages
Version|unspecified |5.17.4

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

[plasma-nm] [Bug 414975] New: The openfortivpn plugin does not allow to set gateway port

2019-12-09 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=414975

Bug ID: 414975
   Summary: The openfortivpn plugin does not allow to set gateway
port
   Product: plasma-nm
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: jgrul...@redhat.com
  Reporter: kle...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Setup openfortivpn connection with  or  as gateway
2. Save config3. 
3. Try to connect

OBSERVED RESULT
In syslog:
NetworkManager[1112]:  [1575890075.2403] agent-manager:
req[0x557e287b29d0, :1.34/org.kde.plasma.networkmanagement/1000]: agent
returned secrets for request [0x557e287c4b20/"XXX"/"vpn"]
NetworkManager[1112]:  [1575890075.2407]
settings-connection[0x557e28672d20,2a77d541-0d9e-417e-9f47-d3efda16f6ff]:
(vpn:0x557e286bdf70) secrets returned from agent :1.34
NetworkManager[1112]:  [1575890075.2408]
settings-connection[0x557e28672d20,2a77d541-0d9e-417e-9f47-d3efda16f6ff]:
(vpn:0x557e286bdf70) secrets request completed
NetworkManager[1112]:  [1575890075.2420]
settings-connection[0x557e28672d20,2a77d541-0d9e-417e-9f47-d3efda16f6ff]:
(vpn:0x557e286bdf70) saving new secrets to backing storage
NetworkManager[1112]:  [1575890075.2689] ++ connection 'get-new-secrets'
(0x557e28682700/NMSimpleConnection/"vpn" <
0x557e28672d20/NMSKeyfileConnection/"vpn"):
NetworkManager[1112]:  [1575890075.2689] ++ vpn   [
0x7fa0e8014e80 < 0x557e2873e8a0 ]
NetworkManager[1112]:  [1575890075.2689] ++ vpn.secrets   =
((GHashTable*) 0x7fa0e8014d80) < ((GHashTable*) 0x7fa0e8014f00)
NetworkManager[1112]:   [1575890075.2705]
settings-connection[0x557e28672d20,2a77d541-0d9e-417e-9f47-d3efda16f6ff]:
write: successfully updated (keyfile: update
/etc/NetworkManager/system-connections/XXX
(2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX")), connection was modified in the
process
NetworkManager[1112]:  [1575890075.2715]
vpn-connection[0x557e2879c400,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
asking service if additional secrets are required
NetworkManager[1112]:  [1575890075.2793]
vpn-connection[0x557e2879c400,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
service indicated no additional secrets required
NetworkManager[1112]:  [1575890075.2800]
vpn-connection[0x557e2879c400,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
Calling old Connect function as not all agents support interactive secrets
NetworkManager[1112]:   [1575890075.2836]
vpn-connection[0x557e2879c400,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
VPN plugin: state changed: starting (3)
NetworkManager[1112]: INFO:   Connected to gateway.
NetworkManager[1112]: ERROR:  Could not authenticate to gateway (Bad HTTP
response code).
NetworkManager[1112]: INFO:   Closed connection to gateway.
NetworkManager[1112]: INFO:   Logged out.
NetworkManager[1112]:   [1575890075.7613]
vpn-connection[0x557e2879c400,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
VPN plugin: failed: connect-failed (1)
NetworkManager[1112]:   [1575890075.7614]
vpn-connection[0x557e2879c400,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
VPN plugin: state changed: stopping (5)
NetworkManager[1112]:   [1575890075.7615]
vpn-connection[0x557e2879c400,2a77d541-0d9e-417e-9f47-d3efda16f6ff,"XXX",0]:
VPN plugin: state changed: stopped (6)


EXPECTED RESULT
Succesful connection

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.17.4
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

My organization uses a FortiVPN server on a non-standard port I think (443). It
seems to me that the port information is no present in plasma-nm code.

Note that the connection to the VPN is successful with the command-line client
with the following configuration:

# config file for openfortivpn, see man openfortivpn(1)
host = 
port = 
username = 
password =
trusted-cert = 

Note also that we use a hardware token to generate one time password.

Finally, I already saw a colleague connecting successfully to the VPN using the
GNOME applet.

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

[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet

2019-09-05 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=393002

--- Comment #14 from Gaël de Chalendar (aka Kleag)  ---
Configuring today a new laptop with KDE Neon, same problem, same solution.

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

[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet

2019-07-29 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=393002

--- Comment #13 from Gaël de Chalendar (aka Kleag)  ---
Same problem today after expiration of my password. And same solution using the
dbus call.

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

[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet

2019-02-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=393002

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kl...@free.fr

--- Comment #12 from Gaël de Chalendar (aka Kleag)  ---
I had the same problem after having to change my password due to timeout
policy.

I was able to set my password with this dbus call:
qdbus org.freedesktop.Akonadi.Resource.akonadi_ews_resource_4 /Settings
org.kde.Akonadi.Ews.Wallet.setPassword "XXX"

I think that this bug is a real blocker for people in organizations that are
depending on a MS IS architecture.

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

[kmail2] [Bug 402228] New: No evident way to disable the unified inbox

2018-12-17 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=402228

Bug ID: 402228
   Summary: No evident way to disable the unified inbox
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-b...@kde.org
  Reporter: kl...@free.fr
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Activate unified inbox
2. Search through all config dialogs how to disable it
3.

OBSERVED RESULT
No UI to disable the unified inbox.

EXPECTED RESULT
There should be a way to disable it in the configuration dialog, maybe in
Appeareance/General

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Up to date KDE Neon
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.53.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION

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

[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)

2018-08-07 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=373907

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 CC||kl...@free.fr

--- Comment #15 from Gaël de Chalendar (aka Kleag)  ---
Apart from a kmail crash at startup, this is the only thing that will keep me
away from Wayland at this time.
This is probably the basic feature that makes my desktop so much more usable
than other ones.

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

[kmail2] [Bug 396780] New: Crash at startup on Wayland

2018-07-22 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=396780

Bug ID: 396780
   Summary: Crash at startup on Wayland
   Product: kmail2
   Version: 5.8.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kl...@free.fr
  Target Milestone: ---

Created attachment 114079
  --> https://bugs.kde.org/attachment.cgi?id=114079&action=edit
The GDB BT of the crash

Kmail crashes at startup in Wayland. It does not occur in X11.

Same description as #372903 but I open a new one as this one was supposed to be
 solved one year ago.

I join the BT

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

[okular] [Bug 387925] New: Automatically switch from navigate to select mode after a delay

2017-12-15 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=387925

Bug ID: 387925
   Summary: Automatically switch from navigate to select mode
after a delay
   Product: okular
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: kl...@free.fr
  Target Milestone: ---

Clicking on the toolbar buttons is boring. 

So, one should be able to click, stay still and wait 1/2 or 1 second to switch
from Navigate to Select mode.

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

[kate] [Bug 384384] Documents modified on disk dialog should stop to trigger after first occurrence

2017-09-14 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384384

--- Comment #4 from Gaël de Chalendar (aka Kleag)  ---
Hi Nate. I'm using Kate and Kwrite before in my development workflow since
1996. 

That's right that I don't use it only to "edit" files but also to dig into
traces of execution of complex (sometimes running) programs where navigating,
searching and highlighting regex occurrences is a must. I need kate features
for that and a lot of other things.

I usually run 
$ program 2>&1 | tee output.log 
and load output.log in kate along other edited files.

Kate is perfect for this usage, except for the little annoyance I report here.

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

[kdevelop] [Bug 384613] New: Make called from project root instead of selected folder

2017-09-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384613

Bug ID: 384613
   Summary: Make called from project root instead of selected
folder
   Product: kdevelop
   Version: 5.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Build tools: CMake
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kl...@free.fr
  Target Milestone: ---

Description: 

Overview: 

Make starts in the wrong folder.

Steps to Reproduce: 

1) Right-click on a project subfolder and select "Build" 

Actual Results: 

The build starts from project root, building other non-dependent
folders

Expected Results: 

Make should be called from the selected folder, not building content of
other folders with no dependencies with the selected one.
(Or, at least, the application should not crash.)

Build Date & Platform: 

Kdevelop 5

Additional Builds and Platforms:

Did not occurr with Kdevelop 4

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

[kdevelop] [Bug 384612] New: Build starts from beginning using existing build dir

2017-09-12 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384612

Bug ID: 384612
   Summary: Build starts from beginning using existing build dir
   Product: kdevelop
   Version: 5.1.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Build tools: CMake
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kl...@free.fr
  Target Milestone: ---

Description: 
I build a large cmake based project composed of a master cmake and subprojects
added with the cmake command ExternalProject_Add. for that, we use a bash
script  that calls cmake and then make and make install. When something goes
wrong, I open the problematic subproject in kdevelop and ask for the build from
there.


Actual Results: 
The build of the subproject starts at 0%.

Expected Results: 

The build of the subproject should restart from where it was using the
script (say 83%)

Build Date & Platform: 

   Up to date KDE Neon User Edition


   It was not occurring with Kdevelop4


Project in question:
https://github.com/aymara/lima

Build script:
The build of the subproject should restart from where it was using the
script (say 83%)

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

[kate] [Bug 384384] Documents modified on disk dialog should stop to trigger after first occurrence

2017-09-06 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384384

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Resolution|WONTFIX |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #2 from Gaël de Chalendar (aka Kleag)  ---
I think you don't understand what I'm asking for. I don't want a behavior like
tail -f with a continuous updating. The idea of updating a reminder just came
to me while writing.

My basic need: stop to display the "Documents modified on disk" dialog after it
has been displayed one time because it makes kate unusable as it blocks the
interface.

Option 1: display again when needed after a manual reload of the file
Option 2: Mark the file as modified on disk

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

[kate] [Bug 384384] New: Documents modified on disk dialog should stop to trigger after first occurrence

2017-09-05 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384384

Bug ID: 384384
   Summary: Documents modified on disk dialog should stop to
trigger after first occurrence
   Product: kate
   Version: 17.08.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: part
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kl...@free.fr
  Target Milestone: ---

Overview: 

I often open file modified by background processes and want to be able to
look at them and other opened files without being interrupted by recurrent
dialogs.

Steps to Reproduce: 

1) Open a file

2) Start a process writing on this file continuously

3) Try to work with kate on other files

Actual Results: 

The "Documents modified on disk" dialogs is displayed again and again

Expected Results: 

The window "Documents modified on disk" should appear the first time and if
the user choose to ignore the changes, it should not be displayed again even if
a reminder could be displayed. The reminder could be updated whenever the file
change, for example with the number of lines modified or anything else.

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

[Falkon] [Bug 384167] Failed to access host filesystem

2017-08-30 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384167

--- Comment #2 from Gaël de Chalendar (aka Kleag)  ---
OK. Noted the upstream reason. 

This would have to be solved before finalizing the goal "we at KDE neon are
moving to new packaging format Snaps" stated at
https://blog.neon.kde.org/index.php/2017/08/29/great-web-browsing-coming-back-to-kde-with-falkon-new-packaging-formats-coming-to-kde-with-snap/

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

[Falkon] [Bug 384168] Unicode capable fonts are missing, chinese character unreadable

2017-08-30 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384168

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
Well, reading the comment by Zygmunt Krynicki on
https://blog.neon.kde.org/index.php/2017/08/29/great-web-browsing-coming-back-to-kde-with-falkon-new-packaging-formats-coming-to-kde-with-snap/,
this should be solved by upstream in some time.

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

[Falkon] [Bug 384168] New: Unicode capable fonts are missing, chinese character unreadable

2017-08-30 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384168

Bug ID: 384168
   Summary: Unicode capable fonts are missing, chinese character
unreadable
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: kl...@free.fr
  Target Milestone: ---

Created attachment 107584
  --> https://bugs.kde.org/attachment.cgi?id=107584&action=edit
screenshot

In Falkon 2.1.99 Snap 19, chinese characters appear as square.

See attached screenshot.

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

[Falkon] [Bug 384167] New: Failed to access host filesystem

2017-08-30 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=384167

Bug ID: 384167
   Summary: Failed to access host filesystem
   Product: Falkon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: kl...@free.fr
  Target Milestone: ---

With Falkon 2.1.99 Snap 19, I cannot access the host filesystem. I'm stuck in
the container one.

This occurs when trying to open a file for upload, when trying to import
Firefox bookmarks, or when trying Save as… actions.

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

[clazy] [Bug 383049] Warnings are triggered when using boost tests

2017-08-02 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=383049

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
Sorry, I found the "// clazy:skip" notation in documentation just after sending
the bug report. 
It solves my problem.

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

[clazy] [Bug 383049] New: Warnings are triggered when using boost tests

2017-08-02 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=383049

Bug ID: 383049
   Summary: Warnings are triggered when using boost tests
   Product: clazy
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: kl...@free.fr
CC: smart...@kde.org
  Target Milestone: ---

Overview: Inconvenient clazy warnings on boost tests

Steps to Reproduce: 
Compile the lima project (https://github.com/aymara/lima) with clazy

Actual Results:
You get warnings when using boost unit tests, like that:

/home/gael/Projets/Lima/lima/lima_common/src/common/Data/tests/ReadWriteTools1.cpp:30:1:
warning: Using copy-ctor but class boost::unit_test::basic_cstring has a
  trivial copy-ctor but non trivial assign operator
[-Wclazy-rule-of-two-soft]
/usr/include/boost/test/unit_test_suite.hpp:114:73: note: expanded from macro
'BOOST_AUTO_TEST_CASE'
#define BOOST_AUTO_TEST_CASE( test_name )   \
^
/usr/include/boost/test/unit_test_suite.hpp:103:46: note: expanded from macro
'\
BOOST_FIXTURE_TEST_CASE'
&BOOST_AUTO_TC_INVOKER( test_name ), #test_name ),  \

Expected Results: 
While we should switch to QTest, this is not possible currently. In the
meantime, I'd like to force clazy to don't run tests in the folders containing
the boost tests, but it doesn't seem to be possible.

I don't want to suppress any given test everywhere with options like
-Wclazy-non-pod-global-static.

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

[kgraphviewer] [Bug 345108] Dutch documentation is not in 2.2.0 tar file

2017-08-02 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=345108

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |REMIND

--- Comment #2 from Gaël de Chalendar (aka Kleag)  ---
The KDE KF5 version is finished and will be released soon, so there will not be
any new work on the KDE4 version.

I don't know how to check if the problem will be solved in future release tar
files. I don't know how they are generated. I will try to ask.

Could you provide the URL of the problematic tar file ?

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

[kgraphviewer] [Bug 344555] src/part/canvaselement.cpp:201: bad use of ? : operator * 2

2017-08-02 Thread Gaël de Chalendar
https://bugs.kde.org/show_bug.cgi?id=344555

Gaël de Chalendar (aka Kleag)  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Gaël de Chalendar (aka Kleag)  ---
Corrected in commit 384cb41a39afc2c914ff1048c5809620e2cb0fff.

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

  1   2   >