[systemsettings] [Bug 177889] add ability to configure multiple keyboards

2024-04-28 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=177889

--- Comment #9 from Philippe Cloutier  ---
I fail to see how that relates to the issue tracked here.

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

[digikam] [Bug 388219] Geolocalization: Process to manually set an picture's capture position is undiscoverable

2023-10-15 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=388219

Philippe Cloutier  changed:

   What|Removed |Added

Summary|Setting geo-location of |Geolocalization: Process to
   |images with an inconvenient |manually set an picture's
   |workflow.   |capture position is
   ||undiscoverable

--- Comment #6 from Philippe Cloutier  ---
I'm fixing this ticket's title. A couple comments:
1. This is an ITS. Entries are issue reports, not (directly) requests.
2. The term "workflow" refers to heavy processes. Something as simple as
setting an image's location should be is not complex enough to qualify as a
"workflow": https://en.wiktionary.org/wiki/workflow

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2023-09-23 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=401088

Philippe Cloutier  changed:

   What|Removed |Added

 CC|chea...@gmail.com   |

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2023-02-10 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=401088

--- Comment #38 from Philippe Cloutier  ---
Hum, thanks Mathias. But in that case, should this ticket be re-titled to be
more general (not specific to "/")?

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2023-02-09 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=401088

--- Comment #36 from Philippe Cloutier  ---
Tim, can you clarify why this ticket was assigned to David Edmundson?

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2023-02-09 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=401088

--- Comment #35 from Philippe Cloutier  ---
(In reply to ManuelBoe from comment #34)
> The dialog described above appears when the file system is unusually slow.
> This may indicate that the hard disk is about to fail or may have other
> causes.

This bug is unfortunately not limited to OSes hosted on HDDs.

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

[kmix] [Bug 335307] Wrong Master Channel (after upgrade, keyboard shortcuts broken, volume 0% (icon completely transparent))

2022-12-23 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=335307

Philippe Cloutier  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |WAITINGFORINFO

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

[krdc] [Bug 339489] Fullscreen Toolbar location widget broken

2022-12-18 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=339489

--- Comment #12 from Philippe Cloutier  ---
Not-so-dear "Bug Janitor Service",
Please note that:
1. I am not a "Bug Submitter",
2. This was already reported and is already "ready to be confirmed".
3. As previously indicated, I no longer use KRDC and will not retest without
indication that this seems fixed.

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

[kmix] [Bug 335307] Wrong Master Channel (after upgrade, keyboard shortcuts broken, volume 0% (icon completely transparent))

2022-05-23 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=335307

--- Comment #6 from Philippe Cloutier  ---
Why was this marked "NOT A BUG"?

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

[digikam] [Bug 328855] Manual geotagging is unintuitive or misleading

2022-01-10 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=328855

--- Comment #10 from Philippe Cloutier  ---
Thank you very much Gilles, happy new year to you too

Unfortunately I have not used digiKam in years, and I gave up on KDE software
recently:
https://www.philippecloutier.com/blogpost141-The-Epik-of-Konqi-s-Krazy-Army
I have no intention to use digiKam again and have no access to a recent desktop
Linux install, so it would be costly for me to retest this.
I appreciate very much your efforts, but I unfortunately prefer to hereby
orphan this ticket.

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

[kio] [Bug 126313] testing has no effect, all functions other than delete don't work when user lacks permission to camera

2021-03-21 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=126313

--- Comment #7 from Philippe Cloutier  ---
I am unable to reproduce on Linux 5.0.0, using kcm_kamera from KDE Apps 18.12
(Ubuntu 19.04's 4:18.12.3-0ubuntu1), even with a user which is only in its own
group.

I do not know enough about udev, hal and systemd to tell how device permissions
are managed nowadays, but it may be that this is no longer reproducible under
Linux. This might still affect under non-Linux systems though.

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

[kmix] [Bug 335307] Wrong Master Channel (after upgrade, keyboard shortcuts broken, volume 0% (icon completely transparent))

2021-03-11 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=335307

--- Comment #4 from Philippe Cloutier  ---
I still own the affected machine, but it is now my third PC, it uses a much
different Linux version, and it does not even run Debian anymore. I do not
remember seeing this bug ever come back.

Considering that no one else has reported experiencing this bug in this ticket,
I guess the chances this would have been a migration bug specific to a certain
version upgrade are considerable. Unfortunately, as the exact reproduction 
conditions remain unknown, confirming persistence with testing would be
difficult.

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

[bugs.kde.org] [Bug 417941] Migrate to Discourse

2021-02-27 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=417941

Philippe Cloutier  changed:

   What|Removed |Added

 CC||chea...@gmail.com

--- Comment #6 from Philippe Cloutier  ---
I must confirm that Discourse is in no way designed to power bug trackers, and
would be quite a downgrade even from bugs.kde.org's current engine. The only
engines which I believe would be worth investigating as Bugzilla replacements
are Atlassian Jira and Redmine.


Please take care to formulate issue reports as reports of *issues*, rather than
requests. For example, this ticket should be titled something like "Uses aging
engine", not "Migrate to [some engine]". It is fine to suggest specific
solutions in your ticket, but that should not be done in its title.

Another approach is to instead report specific issues of the current engine.
Which is already started; the editing limitation you mention is already tracked
in ticket #334299, and I personally already reported a significant number of
other bugs.kde.org issues which likely come from its engine.

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

[bugs.kde.org] [Bug 240086] The guided new bug report form is not suitable for feature requests, especially the "steps to reproduce" part

2021-02-07 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=240086

--- Comment #10 from Philippe Cloutier  ---
Justin, thanks for restoring the Severity field, or at least giving it an
appropriate value.

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

[bugs.kde.org] [Bug 240086] The guided new bug report form is not suitable for feature requests, especially the "steps to reproduce" part

2021-01-09 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=240086

--- Comment #9 from Philippe Cloutier  ---
Justin, all issues are associated with a desire for a change, whether they are
bugs or not. Importance wishlist is reserved to tickets which do not report
defects.

This bug's importance is at the very least normal.

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

[bugs.kde.org] [Bug 240086] The guided new bug report form is not suitable for feature requests, especially the "steps to reproduce" part

2021-01-04 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=240086

--- Comment #7 from Philippe Cloutier  ---
Why was this bug's Importance field set to "wishlist"?

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

[krdc] [Bug 339490] Confusion (blue screen) when establishing connection (RDP, VNC to some degree)

2020-12-28 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=339490

--- Comment #17 from Philippe Cloutier  ---
(In reply to Christoph Feck from comment #16)
> The solution is NOT A BUG because it doesn't describe a single bug, but
> multiple issues.

"NOT A BUG" is not meant for reports about multiple bugs; it is intended for
tickets which do not report any bug.

> Could you please file individual tickets for each issue that is still
> appearing?

As I wrote recently, I gave up on KDE. I have not experienced this behavior in
the last years and no longer have access to any Debian install close to the one
on which I reported this. I also do not use VNC nor have access to any VNC
server, and I do not use RDP with any server to which I could connect using
KRDC. Therefore, it would be a lot less convenient for me to keep driving this,
and I lack the motivation to do this voluntarily.

It would be best for those still experiencing to try reporting more focused
issues if they feel qualified to decompose the misbehaviour into the
responsible technical problems. Or - failing that - to at least confirm that
part or all of this persists in a [more] current version, over 6 years later.

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

[krdc] [Bug 339490] Confusion (blue screen) when establishing connection (RDP, VNC to some degree)

2020-12-28 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=339490

--- Comment #15 from Philippe Cloutier  ---
Christoph, even if "there is no issue now" (meaning current versions are not
affected by the problem), the broken versions were and remain buggy. "NOT A
BUG" is not meant for issues which have been solved.

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

[krdc] [Bug 339490] Confusion (blue screen) when establishing connection (RDP, VNC to some degree)

2020-12-19 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=339490

--- Comment #13 from Philippe Cloutier  ---
Christoph, why do you think this issue is not a bug?

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

[krdc] [Bug 339490] Confusion (blue screen) when establishing connection (RDP, VNC to some degree)

2020-12-13 Thread Philippe Cloutier
https://bugs.kde.org/show_bug.cgi?id=339490

--- Comment #11 from Philippe Cloutier  ---
Thank you Justin

I unfortunately no longer use KDE, RDP or VNC, and I am afraid I am no longer
in a position to drive this further.

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