from:"Rui"

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

--- Comment #1 from Rui Zhao  ---
Clarification for the "dynamic wallpaper" section:

Initially I have dynamic wallpaper (through 3rd party package) installed, and
noticed this bug is easier to be triggered when using dynamic wallpapers on the
lock-screen. After removing that package (and changed to a static wallpaper on
lock-screen), the bug seems less easy to be triggered.
(Note, however, I do not remember seeing this bug in earlier versions quite
some time ago, when I initially installed and configured the dynamic wallpaper
package.)

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

[kscreenlocker] [Bug 479601] KDE lock screen hang up in certain conditions

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

Rui Zhao  changed:

   What|Removed |Added

Version|5.27.4  |5.27.10

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

[kscreenlocker] [Bug 479601] KDE lock screen hang up in certain conditions

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

Rui Zhao  changed:

   What|Removed |Added

Summary|KDE lock screen not |KDE lock screen hang up in
   |responding in certain   |certain conditions
   |conditions  |

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

[kscreenlocker] [Bug 479601] New: KDE lock screen not responding in certain conditions

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

Bug ID: 479601
   Summary: KDE lock screen not responding in certain conditions
Classification: Plasma
   Product: kscreenlocker
   Version: 5.27.4
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: renyune...@gmail.com
  Target Milestone: ---

SUMMARY

I have configured my screen to be automatically locked after a certain timeout.
The timeout happens to be the same as "dimming the screen" (i.e. 5 min).

Usually the lockscreen works without issues. However, under certain conditions,
it will not respond to my actions: moving mouse leads to cursor movement, but
lock-screen always shows its *current/latest status*; typing on keyboard also
makes no difference.

Like indicated by the mouse cursor, the OS is responding. I can switch to tty
by, e.g., Ctrl+Alt+3.

By "current/latest status", I mean the (animation's) rendering status. For
example, if the lock-screen has finished the animation, the content will always
be that one. If the lock-screen is half-way through the animation, e.g. the
clock is dimmed, the clock will always be that dimmed one.

After tens of incidents, I noticed that this only happens when the lock-screen
has just been initiated and I immediately move my mouse trying to cancel it or
getting back from it. (I remember this worked without issues a long time ago.)

STEPS TO REPRODUCE
1. Wait until lock-screen has been (automatically) initiated
2. Move mouse immediately / within a short time-span (trying to cancel it;
within in a few seconds)

OBSERVED RESULT

Lock-screen is hung and not responding

EXPECTED RESULT

Lock-screen gets cancelled; or the lock-screen is responding normally

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11
Kernel Version: 6.6.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: LENOVO
Product Name: 82G2
System Version: Yoga 14sITL 2021

ADDITIONAL INFORMATION

Initially I have dynamic wallpaper (through 3rd party package) installed, and
noticed this is easier to be triggered when using it on the lock-screen. After
removing it, it seems less easy to be triggered.
(Note, however, this did not happen in earlier versions quite some time ago,
when I initially installed the dynamic wallpaper package.)

Because I have Howdy installed as well, I noticed that the lock-screen
sometimes (if not always) triggers Howdy to recognize faces even when this bug
happens. But I never remember that the screen will be unlocked by this way when
this bug happens.

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

[kdenlive] [Bug 476754] Serious and deterministic clip misalignment

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

--- Comment #4 from Rui Seabra  ---
I bit the bullet and repeated the test with the AppImage, with the same
results.

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

[kdenlive] [Bug 476754] Serious and deterministic clip misalignment

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

--- Comment #3 from Rui Seabra  ---
Note: the misalignment happens all over the file, I spend about two days
(between life and such) fixing the holes, render a video with no issues, then
when I open again... misalignment all over again.

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

[kdenlive] [Bug 476754] Serious and deterministic clip misalignment

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

--- Comment #2 from Rui Seabra  ---
Created attachment 162971
  --> https://bugs.kde.org/attachment.cgi?id=162971=edit
file I "saved a copy as" in the video showcasing the issue

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

[kdenlive] [Bug 476754] Serious and deterministic clip misalignment

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

--- Comment #1 from Rui Seabra  ---
Created attachment 162970
  --> https://bugs.kde.org/attachment.cgi?id=162970=edit
original file where I noticed the issue

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

[kdenlive] [Bug 476754] New: Serious and deterministic clip misalignment

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

Bug ID: 476754
   Summary: Serious and deterministic clip misalignment
Classification: Applications
   Product: kdenlive
   Version: 23.08.2
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: r...@1407.org
  Target Milestone: ---

Created attachment 162969
  --> https://bugs.kde.org/attachment.cgi?id=162969=edit
mediainfo for all clips

SUMMARY

I'm suffering from deterministic clip misalignment, it may be a bug or
something I did of very wrong, but if so I don't understand what I did wrong.

I noticed this with Fedora 38's kdenlive, but it also happens with the official
flatpak.

STEPS TO REPRODUCE
1. I describe the full process in this subtitle video:
https://youtu.be/sVwvfn6_jTI
2. I add show.kdenlive and show3.kdenlive files
3. I add mediainfo results for all clips

OBSERVED RESULT

After saving, quiting, and restarting, clips are misaligned.

EXPECTED RESULT

After saving, quiting, and restarting, clips are as aligned as they were at
save time.

SOFTWARE/OS VERSIONS
Fedora 38, native kdenlive 23.08.1 and flatpak of 23.08.2

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

[systemsettings] [Bug 341314] Plasma 5 somehow falls back to US keyboard after startup

2023-11-02 Thread Rui Zhao

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

Rui Zhao  changed:

   What|Removed |Added

 CC||renyune...@gmail.com

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

[krita] [Bug 475827] New: "Perchannel" Filter Layer curves don't change after setting up the node object

2023-10-19 Thread Rui Antunes

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

Bug ID: 475827
   Summary: "Perchannel" Filter Layer curves don't change after
setting up the node object
Classification: Applications
   Product: krita
   Version: 5.2.0
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: rui.andre.antu...@gmail.com
  Target Milestone: ---

Created attachment 162419
  --> https://bugs.kde.org/attachment.cgi?id=162419=edit
Script used to illustrate the issue.

SUMMARY
A `perchannel` `FilterLayer` node does not display the changes configured in
the `Filter` object's values it required for creation.
This is despite the `InfoObject` for the `Filter` being successfully
configured, except for the `nTransfers` property, which remains at `0`.
Also, after saving and quitting the file, the configuration of the new layer is
completely cleared.


STEPS TO REPRODUCE
1. I've provided a `test.py` file that I've used to debug my code and come to
the conclusions below. Please run that script.
2. Save the file and quit
3. Reload the file and inspect the new `node`'s configuration


OBSERVED RESULT
1. The new `FilterLayer` node, that is set to `perchannel` (`Color Adjust`)
seems to be correctly configured, except for `nTransfers`. Both `InfoObject` of
the `Filter` passed to `FilterLayer`, as well as the `Filter` that's inspected
from the new `FilterLayer` object seem to have the `curve` values specified in
the `Properties` `dict`, again, except for `nTransfers`, defaulting to `0` in
the new object. Despite this, the actual image does not visibly change. The
filter configuration should yield visible changes to the transparency of the
image.

3. After saving the file and reloading, if we inspect the Color Adjustment
layer that we've created we can see that it's configuration returns to the
default values: `{"nTransfers": 0}. The values for the curves are not present
in the `InfoObject` after reloading.
Object inspection was made with the following snippet:
```py
filter = Krita.instance().activeDocument().activeNode().filter()
print("\nInfoObject from created node:\n", filter.configuration().properties())
```

EXPECTED RESULT
1. The Color Adjustment Filter Layer should visibly change the image's
transparency, according to the values it was set to.


SOFTWARE/OS VERSIONS
Windows: 10 22H2


ADDITIONAL INFORMATION
This was first discussed in this Krita-Artists thread
(https://krita-artists.org/t/cant-set-perchannel-ntransfers-through-5-2-api/76239)
and was further assisted by user @KnowZero to come to the above conclusions.

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

[lattedock] [Bug 475811] Icon won't update normally

2023-10-18 Thread Rui Zhao

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

Rui Zhao  changed:

   What|Removed |Added

Summary|Icon not updated|Icon won't update normally

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

[lattedock] [Bug 475811] New: Icon not updated

2023-10-18 Thread Rui Zhao

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

Bug ID: 475811
Summary: Icon not updated
Classification: Plasma
Product: lattedock
Version: 0.10.8
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: renyune...@gmail.com
Target Milestone: ---

SUMMARY

The icon in Latte dock is not updated after choosing a new icon pack
system-wide (from systemsettings).
In fact, it does recognize "something", but does not change them. The behaviour
is: if moving mouse cursor through the icon, it often flashes between the new
icon and the old icon.

Deleting KDE's icon cache file (~/.cache/icon-cache.kcache) only does not work
-- restarting latte at this point makes no difference. I have to delete the
icon cache file and log-out and re-log-in to make Latte realize the new icon
pack.

This seems to be a bug for a while, as seen in this reddit post:
https://www.reddit.com/r/kde/comments/xmntc8/latte_dock_not_recognizing_system_icon_changes/

I was using ePapirus icon pack when this happened. But other icon packs also
seem to trigger this.

STEPS TO REPRODUCE
1. Change system icon

OBSERVED RESULT

Latte won't change icon pack, even after restarting latte itself.

EXPECTED RESULT

Latte picks up the new icon pack, at least after a reasonable amount of time,
or after manually restarting it.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.1.58-1-lts (64-bit)
Graphics Platform: Wayland

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

[kdeconnect] [Bug 472897] New: Feature request: Keep system (DE) unlocked but allow screen off

2023-08-01 Thread Rui Zhao

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

Bug ID: 472897
   Summary: Feature request: Keep system (DE) unlocked but allow
screen off
Classification: Applications
   Product: kdeconnect
   Version: 23.04.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: renyune...@gmail.com
  Target Milestone: ---

SUMMARY

Currently, kdeconnect does provide an option to keep system unlocked when
device is connected.
However, it also keeps the screen on all the time.

It would be ideal if it can add an option to allow screen going off, while
still keeping system unlocked. This behaviour itself is at least supported by
KDE Plasma.

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

[kwin] [Bug 468725] Menu text is sometimes blurred on Wayland with mixed-DPI screen setup

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

--- Comment #1 from Rui Zhao  ---
This was mentioned in #42 of Bug 432264. The two bugs may have some relations,
but have different results.

To me, initially (e.g. earlier this year) it was all menus, but now it's only
submenus. Indeed it seems like "redraw" fixes the blur now. No idea why
partially fixed...

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

[kwin] [Bug 432264] In multi-monitor setups with differenlty scaled displays, Context menus have items which are invisible until hovered

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

--- Comment #56 from Rui Zhao  ---
(In reply to Schlaefer from comment #42)
> There's clearly an improvement in v3 here too. Menus still start somewhat
> blurry at first (maybe a different issue) but seem to get redrawn once and
> are fine.

I'm experiencing this for a while and just opened a report today (Bug 468725).
There did not seem to be any other reports of this.
Initially it was all menus, but now it's only submenus. Indeed it seems like
"redraw" fixes the blur now. No idea why partially fixed...
The context menu bug also seems to be related to "redraw". Might have some
link, though I'm not sure.

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

[plasmashell] [Bug 468725] New: Menu text is sometimes blurred

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

Bug ID: 468725
   Summary: Menu text is sometimes blurred
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: renyune...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 158238
  --> https://bugs.kde.org/attachment.cgi?id=158238=edit
Screencast for bug

SUMMARY

The text in some menus (e.g. context menu of Dolphin, Tray icon's context menu,
appmenu) is blurred when initially open. Often after focusing, it will return
to normal.

See the screencast.

I observe this on Wayland, with my laptop's internal monitor with HiDPI
scaling. It does not appear on my external monitor (without HiDPI scaling).

STEPS TO REPRODUCE
1. Open the menu (or sub-menu)

OBSERVED RESULT

Text of the menu (or sub-menu) is blurred

EXPECTED RESULT

Not blurred

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
(available in About System)
KDE Plasma Version: 5.27.4
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.

[plasmashell] [Bug 468724] New: Context menu of tray corrupted after selection

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

Bug ID: 468724
Summary: Context menu of tray corrupted after selection
Classification: Plasma
Product: plasmashell
Version: 5.27.4
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: System Tray
Assignee: plasma-b...@kde.org
Reporter: renyune...@gmail.com
CC: mate...@gmail.com
Target Milestone: 1.0

Created attachment 158237
--> https://bugs.kde.org/attachment.cgi?id=158237=edit
Screencast of the bug

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

The context menu of any tray icon will lose all of its contents (or become
completely transparent) apart from the selected/focused one, and will gradually
have them re-appear if they are selected/focused one by one.

Please see the attached screencast.

This only happens on Wayland, with my laptop's internal monitor with HiDPI
scaling.
It does not appear on my external monitor, nor under X11 (with HiDPI scaling).

After going through the list, sometimes, when opening the same context menu
again, it may not happen.

STEPS TO REPRODUCE
1. Right-click on any tray icon
2. Context menu pops up
3. Move mouse cursor to any menu item (or use arrow keys)

OBSERVED RESULT

Menu disappears (becomes transparent), and only the focused item will remain /
reappear.
After focusing on all menu items, the menu decoration (e.g. segmentation bar)
won't recover.

EXPECTED RESULT

Menu stays.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
(available in About System)
KDE Plasma Version: 5.27.4
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.

[kdeconnect] [Bug 466889] New: [Feature Request] Receive notification only when screen is on

2023-03-05 Thread Rui Zhao

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

Bug ID: 466889
   Summary: [Feature Request] Receive notification only when
screen is on
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: renyune...@gmail.com
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY

This is a feature request for a minor but usability feature.

KDEConnect now already has the ability to send and receive notifications. But
after turning on, it receives regardless of the screen status. Therefore, if I
send notification from one Android device to another, both devices will receive
the notification.

It would be ideal to see notification only on the device that I'm currently
watching -- screen on. Therefore, adding an option to only show notifications
when screen is on would be really useful.

A use case would be before sleeping and both devices have do-not-disturb turned
on, but I'm using one of them; while during the day, that device is not usually
used so there is no point to show notifications on it.

Surely there may be a few overlapping when both are screen on; but this would
already be a lot better than having both all the time.

Hopefully this is also ported to desktop. Though to be fair, I don't currently
have a use case.

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

[dolphin] [Bug 462543] New: Enqueue copy or other file actions

2022-12-02 Thread Rui Zhao

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

Bug ID: 462543
   Summary: Enqueue copy or other file actions
Classification: Applications
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: renyune...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Currently, when copying files (or performing other relevant file actions),
multiple tasks are executed concurrently: select a range of files and paste
will result in task A, and selecting and copying other files will result in
task B, which are executed in concurrent.

In many cases, this does not make sense, or even lower the eventual time
require -- disks have their maximum speed capacity, and changing between and
seeking different files wastes more.

Of course, this is not always the case, such as between multiple pairs of
devices in parallel.

Therefore, it would be ideal if the user is allowed to enqueue the operation,
so they are performed sequentially. Currently there is the pause mechanism, but
it won't resume when the previous task is done.
It would also be great if the queue can be modified afterwards when needed,
particularly if the queue is long.

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

[kwin] [Bug 458873] New: Grouping of windows / window tabs in Plasma 5

2022-09-08 Thread Rui Zhao

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

Bug ID: 458873
   Summary: Grouping of windows / window tabs in Plasma 5
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: renyune...@gmail.com
  Target Milestone: ---

SUMMARY

In KDE 4, there used to be a quite handy feature for grouping different windows
(across applications as well). They appear as tabs on the "same window".

But this is missing in Plasma 5, AFAIK.

Earlier releases of Plasma 5 had this in the errata (e.g.
https://community.kde.org/Plasma/5.10_Errata ). But that page is no longer
published for newer versions.

Is this no longer wanting to be supported? Or is this simply not prioritized?

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

[kscreenlocker] [Bug 455639] Lock screen theme not working on 5.25

2022-06-20 Thread Rui Zhao

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

--- Comment #2 from Rui Zhao  ---
(In reply to David Edmundson from comment #1)
> There was an API break, documented on plasma-devel.
> Themes can set their metadata to v2 when supported

Thanks for the information! I was thinking of this possibility, but did not
find any posts mentioning this.
Could you please point me to where this is mentioned and/or documented (esp.
where should I look for for future updates)?

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

[kscreenlocker] [Bug 455639] New: Lock screen theme not working on 5.25

2022-06-20 Thread Rui Zhao

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

Bug ID: 455639
   Summary: Lock screen theme not working on 5.25
   Product: kscreenlocker
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: renyune...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY

After upgrading to version 5.25, themes no longer work for the lock screen.
The lock screen will always use the default theme.

STEPS TO REPRODUCE
1. Upgrade to 5.25
2. Using or switch to a theme with lock screen theme (e.g. Nova)
3. Lock the screen

OBSERVED RESULT

It is always the default lock screen (with changed highlight color, though).

EXPECTED RESULT

Use the lock screen from the theme.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux, on linux kernel 5.15.39
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

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

[lattedock] [Bug 455040] Translation string not interpreted for the 3rd line on prompt of task manager

2022-06-14 Thread Rui Zhao

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

--- Comment #2 from Rui Zhao  ---
(In reply to Michail Vourlakos from comment #1)
> double check this with git version please

It's not happening on my machine right now (without updating latte version).
Seems not to be a reliable reproduce.

I'll update if I see this again. Maybe this could be closed if no update is
given in, e.g., a month.

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

[lattedock] [Bug 455040] New: Translation string not interpreted for the 3rd line on prompt of task manager

2022-06-08 Thread Rui Zhao

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

Bug ID: 455040
   Summary: Translation string not interpreted for the 3rd line on
prompt of task manager
   Product: lattedock
   Version: 0.10.8
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: mvourla...@gmail.com
  Reporter: renyune...@gmail.com
  Target Milestone: ---

Created attachment 149558
  --> https://bugs.kde.org/attachment.cgi?id=149558=edit
Incorrect string

SUMMARY

In the Latte Task Manager (i.e. the widget that shows all application windows +
pinned applications on the dock), when hovering the mouse over an icon, the
line after window title is shown as `%1(I18N_ARGUMENT_M` (shown incomplete, due
to size of the prompt).

I'm using zh_CN.UTF-8 as my locale. Not sure if this is due to the particular
locale translation, or a general problem in the mechanism.

STEPS TO REPRODUCE
1. Hover mouse over any icon (of a running application) on the task manger
2. Look at the prompt

OBSERVED RESULT

The third line is shown as `%1(I18N_ARGUMENT_M`. See circled part in the
attachment.
Note: the first character "在" means "at". So this is clearly related to
constructing the i18n-ed string.

EXPECTED RESULT

Correctly render the value, instead of the variable name.
Based on the context, this value should be the virtual desktop (or activity?
I'm not using activities) that this window is at.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4

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

[kstars] [Bug 450097] New: Date / time

2022-02-12 Thread Rui Rigel

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

Bug ID: 450097
   Summary: Date / time
   Product: kstars
   Version: 3.5.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: rmrbra...@riseup.net
  Target Milestone: ---

SUMMARY
***
when machine sleeps with kstars running and when later machine wake up the
kstars does not update the date and time locally.
***


STEPS TO REPRODUCE
1. When machine sleeps with kstars running. 
2. When the machine wake up from sleep.

OBSERVED RESULT
Kstars does not update the local date and time.

EXPECTED RESULT
Update the local date and time.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux (x86_64) release 5.4.0-99-generic
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

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

[krunner] [Bug 444994] Calculator giving me wrong answers (PEMDAS)

2021-11-09 Thread Rui Guilherme

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

--- Comment #7 from Rui Guilherme  ---
(In reply to Nate Graham from comment #4)
> Indeed! And you can put the URL of your libqalculate bug report in the URL
> field of this one.

You can see here:
https://github.com/Qalculate/libqalculate/issues/350#issuecomment-963831275

For qalc '2/1 (2+1) = 6' and '2/1(2+1) = 0,7' are diferent expression
and diferent result. 

Check here:
https://i.imgur.com/jdZ2n9n.png

Now, Krunner without space:
https://i.imgur.com/VI7XqAP.png

With space: 
https://i.imgur.com/mYKK4jB.png

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

[krunner] [Bug 444994] Calculator giving me wrong answers (PEMDAS)

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

Rui Guilherme  changed:

   What|Removed |Added

URL||https://github.com/Qalculat
   ||e/libqalculate/issues/350

--- Comment #6 from Rui Guilherme  ---
(In reply to Nate Graham from comment #4)

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

[krunner] [Bug 444994] Calculator giving me wrong answers (PEMDAS)

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

--- Comment #5 from Rui Guilherme  ---
Issue: https://github.com/Qalculate/libqalculate/issues/350

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

[krunner] [Bug 444994] Calculator giving me wrong answers (PEMDAS)

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

--- Comment #3 from Rui Guilherme  ---
I force uninstall:
$ pacman -Rdd libqalculate 

But... https://i.imgur.com/8fFsgAP.png  

The problem then is not with krunner, in that case, I can close the issue and
open a new at https://github.com/qalculate/libqalculate?

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

[krunner] [Bug 444994] Calculator giving me wrong answers (PEMDAS)