[kcharselect] [Bug 486864] New: Add LaTeX commands as aliases

[Yann Salmon]

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

Bug ID: 486864
   Summary: Add LaTeX commands as aliases
Classification: Applications
   Product: kcharselect
   Version: 22.04.3
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

I suggest adding standard LaTeX commands as aliases, to allow searching for a
character with the name of that command, when it exists. This is a bit of the
converse of https://bugs.kde.org/show_bug.cgi?id=342579 and could be
implemented using https://www.w3.org/Math/characters/unicode.xml, which
provides a Unicode-LaTeX map.

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

[KScreen] [Bug 482888] New: kscreen-doctor always saves settings for next sessions

[Yann Salmon]

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

Bug ID: 482888
   Summary: kscreen-doctor always saves settings for next sessions
Classification: Plasma
   Product: KScreen
   Version: 5.27.10
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

SUMMARY

Not sure if bug of RFE (depends on the specified behaviour of kscreen-doctor,
but I cannot find a detailed documentation).

When using kscreen-doctor to eg. activate a secondary screen, that setting
persists after logging out then back into Plasma.

While this persistence makes sense for the GUI because most people will just
set up things once and for all, it is not desirable for people who use a
secondary screen only under certain circumstances, as it requires them to
switch back to their default setting when logging out.

Changing the "live setting" and saving some setting to be used for future
sessions should be different operations.

STEPS TO REPRODUCE
1. Log into session.
2. Issue kscreen-doctor output.$secondaryMonitor.enable
3. (do some work that uses the second monitor)
4. Log out / restart computer.
5. Log in.

OBSERVED RESULT
Plasma starts with the secondary monitor activated (and, in my case, this leads
to glitches, but that is another story).

EXPECTED RESULT
Plasma should start with the "default" setting that was set up using the GUI.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-100-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2


ADDITIONAL INFORMATION

To preserve present behaviour, it would be possible to add a --temporary flag
to kscreen-doctor to mean that the setting should be changed just for now, but
not be persistent across sessions.

A save-current operation could be added as well to persistently save the
current configuration (that might have been set up with --temporary).

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

[KScreen] [Bug 482698] kscreen-doctor disables screen instead of enabling it

[Yann Salmon]

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

--- Comment #4 from Yann Salmon  ---
I seem to be able to have a functioning setup by splitting the command into two
:

if [[ "$(xrandr --listactivemonitors | grep -c DVI-D-0)" == "0" ]]; then
  kscreen-doctor output.DVI-D-0.enable
  kscreen-doctor output.DVI-D-0.position.-1920,0
else
  kscreen-doctor output.DVI-D-0.disable
fi


But that seems contrary to the intended goal of kscreen-doctor.

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

[KScreen] [Bug 482698] kscreen-doctor disables screen instead of enabling it

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

Version|5.24.7  |5.27.10

--- Comment #3 from Yann Salmon  ---
Still happens after upgrade to 

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-97-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2

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

[KScreen] [Bug 482700] kscreen-doctor hangs when given incorrect parameters

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Version|5.24.7  |5.27.10
   Platform|Other   |Kubuntu
 Resolution|DOWNSTREAM  |---
 Status|RESOLVED|REOPENED

--- Comment #2 from Yann Salmon  ---
Still happens with

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-97-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2
Manufacturer: Dell Inc.

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

[KScreen] [Bug 482700] New: kscreen-doctor hangs when given incorrect parameters

[Yann Salmon]

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

Bug ID: 482700
   Summary: kscreen-doctor hangs when given incorrect parameters
Classification: Plasma
   Product: KScreen
   Version: 5.24.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

SUMMARY

When run with improper command line, kscreen-doctor seems to hang.


STEPS TO REPRODUCE
1. Run kscreen-doctor iopiop

OBSERVED RESULT
kscreen-doctor runs, outputing nothing.

EXPECTED RESULT
kscreen-doctor should fail in one way or the other.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-97-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2

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

[KScreen] [Bug 482698] kscreen-doctor disables screen instead of enabling it

[Yann Salmon]

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

--- Comment #2 from Yann Salmon  ---
Created attachment 166577
  --> https://bugs.kde.org/attachment.cgi?id=166577=edit
Situation after setting dual config with the GUI (works properly)

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

[KScreen] [Bug 482698] kscreen-doctor disables screen instead of enabling it

[Yann Salmon]

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

--- Comment #1 from Yann Salmon  ---
Created attachment 166576
  --> https://bugs.kde.org/attachment.cgi?id=166576=edit
Situation where both screens should be working but DP-0 is off

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

[KScreen] [Bug 482698] New: kscreen-doctor disables screen instead of enabling it

[Yann Salmon]

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

Bug ID: 482698
   Summary: kscreen-doctor disables screen instead of enabling it
Classification: Plasma
   Product: KScreen
   Version: 5.24.7
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

Created attachment 166575
  --> https://bugs.kde.org/attachment.cgi?id=166575=edit
Situation where DP-0 is working as single screen

SUMMARY

When invoking kscreen-doctor to enable a secondary screen, the primary screen
gets disabled.


STEPS TO REPRODUCE
1. Write a script kscreen-switch with the following content :

if [[ "$(xrandr --listactivemonitors | grep -c DVI-D-0)" == "0" ]]; then
  kscreen-doctor output.DVI-D-0.enable output.DVI-D-0.position.-1920,0
else
  kscreen-doctor output.DVI-D-0.disable
fi

2. Invoke the script.
3. Invoke the script again.

OBSERVED RESULT
On first invocation, DVI-D-0 goes live and DP-0 goes blank.

On second invocation, DVI-D-0 does blank.

EXPECTED RESULT
On first invocation, DP-0 should not go blank.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-97-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2

ADDITIONAL INFORMATION

Explicitly adding output.DP-0.enable to each line of the script makes DP-0 go
live in second invocation, but does not prevent it from going blank in the
first.

On first invocation with that addition, the console shows

Enabling output 444
kscreen.doctor: Output position QPoint(-1920,0)
kscreen.doctor: Set output position QPoint(-1920,0)
Enabling output 455
kscreen.doctor: setop exec returned KScreen::Config( 
KScreen::Output(444, "DVI-D-0", connected enabled, pos: QPoint(0,0), res:
QSize(-1, -1), modeId: "", scale: 1, clone: no, rotation:
KScreen::Output::None, followPreferredMode: false) 
KScreen::Output(455, "DP-0", connected enabled primary, pos: QPoint(1920,0),
res: QSize(3840, 2160), modeId: "456", scale: 1, clone: no, rotation:
KScreen::Output::None, followPreferredMode: false) )


Which is not consistent with the fact that DP-0 goes blank.

However, the log produced by kscreen-console bug show that something pertaining
to DP-0 is disabled.

Setting up the dual screen configuration with the GUI from Plasma works
properly.

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

[kup] [Bug 482323] New: Save new backup button does nothing when backup fails to start

[Yann Salmon]

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

Bug ID: 482323
   Summary: Save new backup button does nothing when backup fails
to start
Classification: Applications
   Product: kup
   Version: 0.9.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: simon.pers...@mykolab.com
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

SUMMARY
The Save new backup button from kup's systray icon menu does not (seem to) do
anything.


STEPS TO REPRODUCE
1. In KDE settings, set up a backup plan with Manual activation Schedule.
2. Set the destination to an external drive.
3. Open kup's systray icon.
4. Click on Save new backup

OBSERVED RESULT
Nothing

EXPECTED RESULT
Backup should start and kup's status should show that ; or backup fails to
start and the status should also inform as to why.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-97-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2

ADDITIONAL INFORMATION
Turns out the root of the problem is that the Backups folder (the default name
that KDE settings panel uses) did not exist on the destination drive.

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

[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

 CC||cont...@yannsalmon.fr

--- Comment #25 from Yann Salmon  ---
In case this is of any help (I cannot really follow the technical discussion
here) : with 21.12.3, I am experiencing this problem when pasting files, but
``cp``ing them to the exact same location works.

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

[okular] [Bug 471422] New: Okular crashes when opening specific PDF files

[Yann Salmon]

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

Bug ID: 471422
   Summary: Okular crashes when opening specific PDF files
Classification: Applications
   Product: okular
   Version: 21.12.3
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

SUMMARY

Okular crashes when I try to open some specific PDF files. It does not with
other files.


STEPS TO REPRODUCE
1. Download file from

2. Open file in Okular.

OBSERVED RESULT

Immediate crash.

EXPECTED RESULT

PDF file to be rendered, or an error message to be displayed if file is faulty.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-75-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1245 v5 @ 3.50GHz
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2

ADDITIONAL INFORMATION

The crash happens with all the files the link to which is labelled "Acte n°" on

but with no other file from that page or other pages. I suspect there is some
kind of signature (the files are acts from an high school administrative board)
that is buggy.

The bug system suggested possible duplicates, and I tried to open the related
PDF files, but none of them triggers a crash, so I suspect this is not the same
problem.

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

[okular] [Bug 463994] Okular fails to open HTTPS URLs to PDF files

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

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

--- Comment #9 from Yann Salmon  ---
I rather removed 
x-scheme-handler/http=firefox.desktop;
x-scheme-handler/https=firefox.desktop;

because there is no such desktop file on my computer, and the other file does
lunch Firefox (I get it from Mozilla directly, and it is installed under /opt).

The problem still persists after this operation.

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

[okular] [Bug 463994] Okular fails to open HTTPS URLs to PDF files

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

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

--- Comment #5 from Yann Salmon  ---
1. It opens in Firefox.

2.
```
application/pdf=okularApplication_pdf.desktop;userapp-evince-ZGIKLZ.desktop;inkscape.desktop;gimp.desktop;libreoffice-draw.desktop;libreoffice-writer.desktop;userapp-bless-FBYQTY.desktop;userapp-emacs-KNM4TY.desktop;
x-scheme-handler/http=firefox.desktop;
x-scheme-handler/https=firefox.desktop;
application/pdf=okularApplication_pdf.desktop;
x-scheme-handler/http=userapp-Firefox-FVD3O1.desktop
x-scheme-handler/https=userapp-Firefox-FVD3O1.desktop
```

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

[okular] [Bug 463994] Okular fails to open HTTPS URLs to PDF files

[Yann Salmon]

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

--- Comment #3 from Yann Salmon  ---
Also note that atril opens the links correctly, and that evince fails to all
three, but that is because for some reason it gets ``exec:
/opt/yann/firefox/firefox-bin: Permission denied`` so at least it is trying to
do the right thing.

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

[okular] [Bug 463994] Okular fails to open HTTPS URLs to PDF files

[Yann Salmon]

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

--- Comment #2 from Yann Salmon  ---
It says Firefox there, presumably because I take it directly from Mozilla (not
Ubuntu's snap) and created the desktop file myself.

Non-PDF links clicked in Okular do open in my firefox instance.

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

[okular] [Bug 463994] New: Okular fails to open HTTPS URLs to PDF files

[Yann Salmon]

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

Bug ID: 463994
   Summary: Okular fails to open HTTPS URLs to PDF files
Classification: Applications
   Product: okular
   Version: 21.12.2
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

Created attachment 155101
  --> https://bugs.kde.org/attachment.cgi?id=155101=edit
Example file

SUMMARY

STEPS TO REPRODUCE
1. Create file /tmp/essai/thing.pdf containing a link to say
https://docs.kde.org/stable5/en/okular/okular/okular.pdf
2. Open /tmp/essai/thing.pdf and click link.

OBSERVED RESULT
Okular opens another window of itself, which displays an error about not being
able to open
file:///tmp/essai/https:/docs.kde.org/stable5/en/okular/okular/okular.pdf

(notice only one slash after https:)

EXPECTED RESULT
Okular should open linked PDF file either in the browser or another Okular
window.


SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Right clicking link and copying address gives the correct URL.
URL to non-PDFs seems unaffected.
Links that do not literally end with .pdf but 302-redirect to a PDF are
affected (see 3rd link in example file).

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

[drkonqi] [Bug 459152] New: Reporting a bug after a crash is a hassle because of unclear directions to install debug packages

[Yann Salmon]

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

Bug ID: 459152
   Summary: Reporting a bug after a crash is a hassle because of
unclear directions to install debug packages
   Product: drkonqi
   Version: 5.24.6
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

SUMMARY
The Assistant that appears after a crash to report a bug requires you to have a
stacktrace with debugging information, but upgrading the system to do so is
complicated.

STEPS TO REPRODUCE
1. Have a part of Plasma crash.
2. Try to report a bug with the assistant that pops up.
3. Observe that it complains about the stacktrace not being helpful
4. Click on the link below
5. Be overwhelmed by the unclear technical steps required
6. Abandon reporting about the crash

OBSERVED RESULT
We get a list of files for which there is no debugging information and are told
to install the debug version of the corresponding packages.


EXPECTED RESULT
The assistant should show which are the corresponding packages, and offer to
install the required versions.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KUbuntu 22.04
(available in About System)
KDE Plasma Version: 5.42.6
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 455528] Task manager buttons are uselessly narrow when grouping is enabled but combining groups is disabled

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

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

[plasmashell] [Bug 455528] Task manager buttons are uselessly narrow when grouping is enabled but combining groups is disabled

[Yann Salmon]

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

--- Comment #2 from Yann Salmon  ---
Created attachment 149876
  --> https://bugs.kde.org/attachment.cgi?id=149876=edit
No grouping : wide buttons

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

[plasmashell] [Bug 455528] Task manager buttons are uselessly narrow when grouping is enabled but combining groups is disabled

[Yann Salmon]

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

--- Comment #1 from Yann Salmon  ---
Created attachment 149875
  --> https://bugs.kde.org/attachment.cgi?id=149875=edit
Grouping and combining : wide buttons

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

[plasmashell] [Bug 455528] New: Task manager buttons are uselessly narrow when grouping is enabled but combining groups is disabled

[Yann Salmon]

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

Bug ID: 455528
   Summary: Task manager buttons are uselessly narrow when
grouping is enabled but combining groups is disabled
   Product: plasmashell
   Version: 5.24.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: 1.0

Created attachment 149874
  --> https://bugs.kde.org/attachment.cgi?id=149874=edit
Grouping of buttons, but no combining : narrow buttons

SUMMARY
Task manager has an option to group buttons by program names (ie. multiple
Firefox window's button will be next to each other). It also has a distinct
option to combine such groups into a unique button. When the first option is
enabled but not the second, buttons have a reduced width, as if the task bar
were clumped.

OBSERVED RESULT
See attachments.

EXPECTED RESULT
Wide buttons in all cases, since space is not scarce.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KUbuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
I think the behaviour was correct with KUbuntu 20.04.

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

[dolphin] [Bug 451835] New: Dolphin fails to rename file in remote encrypted vault accessed through SFTP

[Yann Salmon]

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

Bug ID: 451835
   Summary: Dolphin fails to rename file in remote encrypted vault
accessed through SFTP
   Product: dolphin
   Version: 19.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cont...@yannsalmon.fr
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1.  On computer A, create an encrypted vault, mount it and put a simple file
"test" in it.
2.  From computer B, use Dolphin's SFTP to access the (mounted) vault on
computer A.
3.  Using Dolphin (right-click, rename), rename "test" into say "test2".

OBSERVED RESULT
Dolphin displays an error dialog saying "internal problem" and to report a bug
here.
File is not renamed.

EXPECTED RESULT
File should be renamed in the remote vault.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
Problems also appear when copying a file to the remote vault, creating a file
or modifying/saving an existing file with Kate : Dolphin displays an error bar
above the main view, saying it could not rename the partial file and to verify
my access rights.

Indeed, I can see a file with .partial at the end, which in each case has the
intended content.

Setting up a SSH-connexion from computer B to computer A in a terminal to the
same vault and issuing rename (mv) command there works.

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

[dolphin] [Bug 445292] New: Dolphin does not display newline character in file names

[Yann Salmon]

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

Bug ID: 445292
   Summary: Dolphin does not display newline character in file
names
   Product: dolphin
   Version: 19.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cont...@yannsalmon.fr
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
When a file name contains special characters (ie. newline), they are not
visible in the displayed name.

STEPS TO REPRODUCE
Using Python to avoid any bizarre things with how shells interpret special
characters in the input :
1. os.chdir("/tmp")
2. open("test\ntest", "w")
3. open("testtest", "w")
4. open("test\rtest", "w")
5. Show /tmp in dolphin

OBSERVED RESULT
Three files that appear as testtest ; only by using the renaming tool does the
newline appear (but the \n and \r remain indistinguishable).

EXPECTED RESULT
Some visual clue that the filename contains a newline character.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
This might be used to craft a file mimicking another file.

Inserting a tabulation gives a clue (the tabulation is displayed).
Inserting other special characters (eg. ASCII 1 or 2) gives a small black box
with the character mnemonic.

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

[gwenview] [Bug 434210] New: Gwenview needs 25 seconds to start

[Yann Salmon]

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

Bug ID: 434210
   Summary: Gwenview needs 25 seconds to start
   Product: gwenview
   Version: 19.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

SUMMARY

Gwenview takes a long time to start on some occasions, notably the first time I
start it in a session (or if it has not been started for a long time ?).


STEPS TO REPRODUCE
1. Start Gwenview, either through the command line or by double-cliking an
image file in Dolphin.


OBSERVED RESULT
The outline of the Gwenview window is briefely displayed but the inner content
is not and it is irresponsive (other programs and the DE are still usable).
After ~25 seconds, Gwenview finally functions.

EXPECTED RESULT
Gwenview should not take such a long time to start.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KUbuntu 20.04
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: KDE Frameworks 5.68.0
Qt Version: Qt 5.12.8

ADDITIONAL INFORMATION
I deactivated history and activated the low-resource thumbnail mode (use
embedded thumbnails).

The problem happens even when starting Gwenview in a working dir that contains
no files.

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

[muon] [Bug 410418] Muon preferences are not saved.

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

 CC||cont...@yannsalmon.fr

--- Comment #1 from Yann Salmon  ---
Yes, it seems that the setting dialogs does ask for sudo credentials when it
should. The "Apply" button shows a padlock icon, which I assume means that
authentication is required. But there is no password prompt, like when one
wants to configure external sources.

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

[dolphin] [Bug 429364] Dolphin does not display dollar sign ($) in some file names

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

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

--- Comment #2 from Yann Salmon  ---
This makes sense !

However I do have a file that is listed as 'base2019.sqlite'$'\n' with ls and
is displayed as base2019.sqlite by dolphin.

I do not remember how I created them, so I tried to do it again but failed.

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

[dolphin] [Bug 429364] New: Dolphin does not display dollar sign ($) in some file names

[Yann Salmon]

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

Bug ID: 429364
   Summary: Dolphin does not display dollar sign ($) in some file
names
   Product: dolphin
   Version: 19.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: cont...@yannsalmon.fr
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
I accidentally created a file with a dollar sign in it. Dolphin does not
display that sign in the name. This could cause confusion, at least.

STEPS TO REPRODUCE
1. With bash, run touch 'file.na'$'me'
2. Open Dolphin and display the containing folder

OBSERVED RESULT
File is displayed as file.name


EXPECTED RESULT
File should be displayed as file.na$me

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 20.04
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
When the name ends with $, it gets displayed (eg. touch 'filename'$). But
adding an empty string after makes it disappear (eg. touch 'filename'$'').

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

[systemsettings] [Bug 422586] KDE resets GTK font setting to non-condensed font

[Yann Salmon]

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

--- Comment #2 from Yann Salmon  ---
Created attachment 129292
  --> https://bugs.kde.org/attachment.cgi?id=129292=edit
Screenshot of dconf-editor

Thanks for the pointer. For future reader, although it seems they should not,
the steps I described above do make it possible to use a condensed font in GTK3
apps in KDE (see dconf-editor as an example).

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

[systemsettings] [Bug 422586] New: KDE resets GTK font setting to non-condensed font

[Yann Salmon]

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

Bug ID: 422586
   Summary: KDE resets GTK font setting to non-condensed font
   Product: systemsettings
   Version: 5.18.5
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: krdb
  Assignee: kdelibs-b...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Set KDE default font to Noto Sans Condensed.
2. See that this does not apply to GTK2 nor GTK3 apps.
3. Tweak various GTK config files to set Noto Sans Condensed as the default
font well.
4. Log out and back in.

OBSERVED RESULT
GTK config files are reset to "Noto Sans", nont condensed.

EXPECTED RESULT
GTK config files are either left untouched or correctly synchronised.


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

ADDITIONAL INFORMATION
For GTK2 apps, using gtk-chtheme and gtk-theme-switch2 works, but I had to go
back to KDE settings GUI after using these tools and reapply the theme to
overcome some residual glitches.

The big problem was with GTK3 apps.

Not sure which GTK3 config files actually need to be set. I did :

update ~/.config/xsettingsd/xsettingsd.conf with Gtk/FontName "Noto Sans
Condensed,  11"
update ~/.config/gtk-3.0/settings.ini with gtk-font-name=Noto Sans
Condensed,  11
in dconf, under org.gnome.desktop.interface, set font-name to 'Noto Sans
Condensed,  11'.

These files and dconf settings are reset to "Noto Sans, 11" at login.

KDE refers to the font as "Noto Sans" with the "Condensed" attribute while in
GTK one needs to have "Noto Sans Condensed" as the font name ; maybe the
setting transfer is buggy. Or maybe this has nothing to do with my wished font
being Condensed.

Anyway, I had to disable the Plasma GTKd background service to make my GTK font
setting stay.

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

[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering

[Yann Salmon]

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

Yann Salmon  changed:

   What|Removed |Added

 CC||cont...@yannsalmon.fr

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

[kwin] [Bug 398298] New: KWin crashes after resuming from hibernation

[Yann Salmon]

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

Bug ID: 398298
   Summary: KWin crashes after resuming from hibernation
   Product: kwin
   Version: 5.12.6
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: cont...@yannsalmon.fr
  Target Milestone: ---

Application: kwin_x11 (5.12.6)

Qt Version: 5.9.5
Frameworks Version: 5.47.0
Operating System: Linux 4.17.14-041714-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was logging back into my locked session after resuming from hibernation. It
happens frequently that KDE needs to restart "desktop effects" on such an
occasion or after suspend (roughly every other time), but the first time that a
crash and bug reporting procedure occurred.

- Notes:
There are also some graphical glitches after resuming from hibernation or
suspend (icons get inadequate pixels, most often) which never occur on a fresh
boot.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f6b3a6cc0 (LWP 2066))]

Thread 6 (Thread 0x7f1f33888700 (LWP 6843)):
#0  0x7f1f6ad1ccf6 in __GI_ppoll (fds=0x7f1f2c0012c8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f1f6811d5c1 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1f6811ecde in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1f680c69ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1f67ee522a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1f67eea16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1f63d726db in start_thread (arg=0x7f1f33888700) at
pthread_create.c:463
#7  0x7f1f6ad2988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f1f32fab700 (LWP 2249)):
#0  0x7f1f63d789f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f1f6731afb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f1f63d789f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f1f6731af68, cond=0x7f1f6731af90) at pthread_cond_wait.c:502
#2  0x7f1f63d789f3 in __pthread_cond_wait (cond=0x7f1f6731af90,
mutex=0x7f1f6731af68) at pthread_cond_wait.c:655
#3  0x7f1f670245f4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f1f67024639 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f1f63d726db in start_thread (arg=0x7f1f32fab700) at
pthread_create.c:463
#6  0x7f1f6ad2988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f1f48818700 (LWP 2203)):
#0  0x7f1f6ad1ccf6 in __GI_ppoll (fds=0x7f1f4d28, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f1f6811d5c1 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1f6811ecde in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1f680c69ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1f67ee522a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1f6285e6f5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f1f67eea16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f1f63d726db in start_thread (arg=0x7f1f48818700) at
pthread_create.c:463
#8  0x7f1f6ad2988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f1f4b12a700 (LWP 2139)):
#0  0x7f1f6ad1ccf6 in __GI_ppoll (fds=0x7f1f4400ed28, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f1f6811d5c1 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1f6811ecde in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f1f680c69ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1f67ee522a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1f6172ed45 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#6  0x7f1f67eea16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f1f63d726db in start_thread (arg=0x7f1f4b12a700) at
pthread_create.c:463
#8  0x7f1f6ad2988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f1f518ef700 (LWP 2085)):
#0  0x7f1f6ad1cbf9 in __GI___poll (fds=0x7f1f518eec68, nfds=1, timeout=-1)
at 

[okular] [Bug 358602] Do not open twice the same document

[Yann Salmon]

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

--- Comment #4 from Yann Salmon  ---
Ah, sorry, I thought that the technical permissions in the bug reporting tool
would match the actual actions I was allowed to do.

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