[kmail2] [Bug 485661] Kmail popup windows closes when trying to copy or move message to folder
https://bugs.kde.org/show_bug.cgi?id=485661 --- Comment #5 from Roger Noble --- This bug is still there in kmail 6.1.2, frameworks 6.3.0. It's really frustrating. I have messages in folders I can't move or copy because of this. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487683] Import should import to the currently active album.
https://bugs.kde.org/show_bug.cgi?id=487683 Roger Noble changed: What|Removed |Added CC||rnbzi...@gmail.com --- Comment #2 from Roger Noble --- For me at least when importing images from a folder on my computer digikam does not remember the last album I imported to. It always appears to go back to an album I last imported to three years ago. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 485661] Kmail popup windows closes when trying to copy or move message to folder
https://bugs.kde.org/show_bug.cgi?id=485661 Roger Noble changed: What|Removed |Added CC||rnbzi...@gmail.com --- Comment #1 from Roger Noble --- Happens with me as well. Also when trying to move a message between folders: the menu disappears as soon as I try to move below the Recent Folder item. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 477553] New: Share menu should include clipboard
https://bugs.kde.org/show_bug.cgi?id=477553 Bug ID: 477553 Summary: Share menu should include clipboard Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: ro...@atchoo.org Target Milestone: --- SUMMARY When using the share menu, it should always include "copy to clipboard" as an option. STEPS TO REPRODUCE 1. Navigate to https://atchoo.org/tmp/share.html 2. Click on the Share button OBSERVED RESULT Menu appears with items: * Send SMS via KDE Connect * Twitter * Send via Email... * Generate QR Code * Send to device EXPECTED RESULT Menu includes an option to copy to clipboard. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-9-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 467306] New: Krusader Synchronize Tool Will Not Delete Files
https://bugs.kde.org/show_bug.cgi?id=467306 Bug ID: 467306 Summary: Krusader Synchronize Tool Will Not Delete Files Classification: Applications Product: krusader Version: 2.8.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: synchronize Assignee: krusader-bugs-n...@kde.org Reporter: leemull...@comcast.net CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 157250 --> https://bugs.kde.org/attachment.cgi?id=157250=edit Synchronize Dialog For Deleting Files SUMMARY *** In the past I have been able to use Krusader Synchronize Folders l to compare 2 directories. Today I am doing that and I am unable to delete any files from the left or right side. I can get a dialog that should allow me to delete files from the left side, but it is grayed out and so not usable. Am I doing something wrong? *** STEPS TO REPRODUCE 1. Set up directories to compare. 2. From the Tools Menu select Synchronize Folders 3. On the Synchronize Folders dialog, click Compare at the bottom right. 4. On the Show Options, I click on Left, right and Singles. 5. After the comparison you can click on the Synchronize button at the bottom right to get another dialog that shows you should be able to delete files from the left. OBSERVED RESULT Delete on the left is grayed out. EXPECTED RESULT Delete would be available. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462695] Automatic DisplayPort screen dimming/sleep and system sleep stops working on Wayland
https://bugs.kde.org/show_bug.cgi?id=462695 --- Comment #36 from Roger Noble --- I ran it on Fedora 37 but the plugin doesn't appear to be there either. No package appears to provide it either. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Automatic DisplayPort screen dimming/sleep and system sleep stops working on Wayland
https://bugs.kde.org/show_bug.cgi?id=462695 --- Comment #33 from Roger Noble --- $ /usr/libexec/org_kde_powerdevil --replace org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed kf.idletime: Could not find any system poller plugin QObject::connect(AbstractSystemPoller, KIdleTime): invalid nullptr parameter QObject::connect(AbstractSystemPoller, KIdleTime): invalid nullptr parameter org.kde.powerdevil: Handle button events action could not check for screen configuration org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working
https://bugs.kde.org/show_bug.cgi?id=462695 --- Comment #25 from Roger Noble --- In my case, yes. All three are DisplayPort. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working
https://bugs.kde.org/show_bug.cgi?id=462695 Roger Noble changed: What|Removed |Added CC||rnbzi...@gmail.com --- Comment #22 from Roger Noble --- Same here with Fedora 37, 5.27.0, 5.103.0, Wayland. Desktop with Radeon RX 6700 XT graphics, None of my three displays will turn off. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 458330] New: Latte dock sometimes hand at startup and do not start the UI
https://bugs.kde.org/show_bug.cgi?id=458330
Bug ID: 458330
Summary: Latte dock sometimes hand at startup and do not start
the UI
Product: lattedock
Version: 0.10.8
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: plasmoid
Assignee: mvourla...@gmail.com
Reporter: roger.vins...@gmail.com
Target Milestone: ---
This issue does not happen at every startup, but it occurs on both my laptop
(with intel CPU+GPU + wayland) and desktop (AMD CPU + Nvidia GPU + Xorg). When
it happens, latte use a whole CPU core at 100% indefinitely and the UI never
start. Killing the process and launch a new instance of latte dock is my
workaround (but it is annoying).
I am on Manjaro Linux with:
KDE Plasma 5.24.6
KDE Frameworks: 5.96.0
Qt version: 5.15.5
Kernel: 5.19.1
Latte dock: 0.10.8
I managed to capture a debug log while this problem occurs, here is what I get:
```
[1;32m[Debug : [0;32m9:37:45.878878[1;32m][0m[1;36m - [0m"badges based on
position updated to :: (\"\", \"\", \"\", \"\", \"\", \"\", \"\", \"\", \"\",
\"\", \"z\", \"x\", \"c\", \"\", \"b\", \"n\", \"m\", \",\", \"\")"
[1;32m[Debug : [0;32m9:37:45.878878[1;32m][0m[1;36m - [0m"badges for
applet shortcuts updated to :: QHash()"
[1;32m[Debug : [0;32m9:37:45.899899[1;32m][0m[1;36m - [0m" Indicator
Package Loaded ::: \"Latte\" [ \"org.kde.latte.default\" ] - [
\"/usr/share/latte/indicators/default\" ]"
[1;32m[Debug : [0;32m9:37:45.99[1;32m][0m[1;36m - [0m" Indicator Package
Loaded ::: \"Plasma\" [ \"org.kde.latte.plasma\" ] - [
\"/usr/share/latte/indicators/org.kde.latte.plasma\" ]"
[1;32m[Debug : [0;32m9:37:45.901901[1;32m][0m[1;36m - [0m" Indicator
Package Loaded ::: \"Plasma Tab Style\" [ \"org.kde.latte.plasmatabstyle\" ]
- [ \"/usr/share/latte/indicators/org.kde.latte.plasmatabstyle\" ]"
[1;32m[Debug : [0;32m9:37:45.901901[1;32m][0m[1;36m - [0m"\"Latte\""
[1;32m[Debug : [0;32m9:37:45.901901[1;32m][0m[1;36m - [0m" IMPORTER,
STORAGE TEMP DIR ::: \"/tmp/lattedock-bYngrV\""
[1;32m[Debug : [0;32m9:37:45.901901[1;32m][0m[1;36m -
[0m" Plasma Screen Ids --"
[1;32m[Debug : [0;32m9:37:45.901901[1;32m][0m[1;36m -
[0m" --- --"
[1;32m[Debug : [0;32m9:37:45.908908[1;32m][0m[1;36m - [0m" Windows
default color scheme :: \"/usr/share/color-schemes/BreezeLight.colors\""
[1;32m[Debug : [0;32m9:37:45.909909[1;32m][0m[1;36m - [0m" KWIN SERVICE
:: is available..."
[1;32m[Debug : [0;32m9:37:45.912912[1;32m][0m[1;36m - [0m"package is
valid true"
[1;32m[Debug : [0;32m9:37:45.912912[1;32m][0m[1;36m - [0m"org.kde.latte
:: Known Screen - \"10\" : \"DP-0\" : QRect(0,0 1920x1080)"
[1;32m[Debug : [0;32m9:37:45.912912[1;32m][0m[1;36m - [0m"Latte::Corona
the package
QJsonObject({\"KPlugin\":{\"Authors\":[{\"Email\":\"mvourla...@gmail.com,
audo...@openmailbox.org\",\"Name\":\"Michail Vourlakos, Smith
Ar\"}],\"Description\":\"Shell provided for the Latte
Dock\",\"Description[az]\":\"Latte Dok paneli üçün nəzərdə tutulan
üzlük\",\"Description[ca@valencia]\":\"Intèrpret d'ordres proporcionat per
l'acoblador Latte\",\"Description[ca]\":\"Intèrpret d'ordres proporcionat per
l'acoblador Latte\",\"Description[da]\":\"Skal til
Latte-dokken\",\"Description[de]\":\"Shell für
Latte-Dock\",\"Description[el]\":\"Κέλυφος που παρέχεται από την εφαρμογή
Latte\",\"Description[en_GB]\":\"Shell provided for the Latte
Dock\",\"Description[es]\":\"Shell proporcionada para Latte
Dock\",\"Description[et]\":\"Latte doki shell\",\"Description[eu]\":\"Shell-a
Latte Dockentzat\",\"Description[fi]\":\"Latte-telakalle tarjottu
käyttöliittymä\",\"Description[fr]\":\"Interpréteur de commandes fourni pour le
panneau Latte\",\"Description[gl]\":\"Intérprete de ordes fornecido para a doca
Latte.\",\"Description[id]\":\"Shell disediakan untuk Dock
Latte\",\"Description[it]\":\"Shell fornita per Latte
Dock\",\"Description[ko]\":\"Latte 독용 셸\",\"Description[lt]\":\"Latte dokui
teikiamas apvalkalas\",\"Description[nl]\":\"Shell geleverd voor de Latte
Dock\",\"Description[nn]\":\"Skal frå
Latte-dokk\",\"Description[pl]\":\"Powłoka dla doku
Latte\",\"Description[pt]\":\"Consola oferecida para a área acoplável do
Latte\",\"Description[pt_BR]\":\"Shell fornecido pelo Latte
Dock\",\"Description[ru]\":\"Оболочка для Latte
Dock\",\"Description[sl]\":\"Shell za dok Latte\",\"Description[sv]\":\"Skal
tillhandahållet för Latte dockningsfönster\",\"Description[uk]\":\"Оболонка
панелі Латте\",\"Description[x-test]\":\"xxShell provided for the Latte
Dockxx\",\"Description[zh_CN]\":\"用于 Latte 停靠栏的
Shell\",\"Description[zh_TW]\":\"由 Latte Dock 提供的
Shell\",\"Id\":\"org.kde.latte.shell\",\"License\":\"GPLv3+\",\"Name\":\"Latte
Shell\",\"Name[az]\":\"Latte Üzlüyü\",\"Name[ca@valencia]\":\"Intèrpret
d'ordres del Latte\",\"Name[ca]\":\"Intèrpret d'ordres del
[frameworks-kwindowsystem] [Bug 457064] New: Using KDE Plasma with SELinux restricted users cause weird AVC's with SELinux running as permissive and makes restricted login impossible with SELinux runn
https://bugs.kde.org/show_bug.cgi?id=457064 Bug ID: 457064 Summary: Using KDE Plasma with SELinux restricted users cause weird AVC's with SELinux running as permissive and makes restricted login impossible with SELinux running as enforcing Product: frameworks-kwindowsystem Version: 5.96.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: roger.k.truss...@gmail.com Target Milestone: --- 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 *** STEPS TO REPRODUCE 1. Install the Fedora Workstation 36 KDE Spin and apply all updates 2. Edit the "/etc/selinux/config" file and put SELinux in permissive mode because the following steps won't work in "enforcing" mode. 2. Create a new Linux user and use "sudo semanage login" to map that new Linux user onto the SELinux user "user_u" 3. Reboot and login as that restricted user OBSERVED RESULT You will see interesting AVC's such as: SELinux is preventing plasmashell from watch access on the directory / SELinux is preventing plasmashell from watch access on the file /etc/passwd. SELinux is preventing ksmserver-logou from watch access on the file /etc/passwd. SELinux is preventing kwin_wayland from write access on the file /tmp/#118 EXPECTED RESULT I kinda expected that maybe the KDE login mechanism would be modular or at least use a standard PAM and not need direct access to any sensitive system resources. I understand if temporary files need to be stored in the user directory. I was hoping to create SELinux restricted accounts on this Fedora Workstation that would not need direct access to any sensitive system resources. I'm still trying to wrap my head around how Wayland and modern window managers work. I just assumed that maybe things like sddm and the Wayland compositor would both run as daemons with root level permissions and the Wayland clients would run with the same system permissions as the "logged in user". Perhaps having the compositor and sddm both running as root would block or confuse the communication between the clients and the compositor. I just don't know. Sorry. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Workstation 36 KDE Spin: kernel: 5.18.13-200.fc36.x86_64 (available in About System) KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 453753] Akonadi crashes when opening KMail
https://bugs.kde.org/show_bug.cgi?id=453753
Vincent ROGER changed:
What|Removed |Added
CC||roger.vins...@gmail.com
--- Comment #4 from Vincent ROGER ---
I also have this problem when launching kalendar on manjaro.
My akonadi version:
akonadiserver 5.20.2 (22.04.2)
The output I get when launching kalendar:
```
QML debugging is enabled. Only use this in a safe environment.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/user/.local/share/akonadi/mysql.conf",
"--datadir=/home/user/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-20 9:21:35 0 [Note]
/usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 31918 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
org.kde.pim.akonadicore: Could not start/stop Akonadi!
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
zsh: segmentation fault (core dumped) kalendar
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/user/.local/share/akonadi/mysql.conf",
"--datadir=/home/user/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "2022-06-20 9:21:40 0 [Note]
/usr/bin/mysqld (server 10.8.3-MariaDB) starting as process 31946 ...\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
```
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 452509] Kdenlive (Appimage) crashes when I click onto a video clip in the timeline
https://bugs.kde.org/show_bug.cgi?id=452509 --- Comment #2 from Roger Wilco --- Created attachment 148113 --> https://bugs.kde.org/attachment.cgi?id=148113=edit Updated/corrected version of previous attachment Had another look at the attachment that I uploaded the first time and realized that I must've messed up a simple copy & paste regarding the second half of the attachment, where I said that I'd be sharing the output from the terminal when launching the Appimage from there. Well, this v2 of this *.txt file now contains the correct output from the terminal. The first half, containing the requested debug info, remained untouched. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452509] Kdenlive (Appimage) crashes when I click onto a video clip in the timeline
https://bugs.kde.org/show_bug.cgi?id=452509 --- Comment #1 from Roger Wilco --- I left out the screenshot mentioned in the report, as I was under the impression that it would not add relevant information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452509] Kdenlive (Appimage) crashes when I click onto a video clip in the timeline
https://bugs.kde.org/show_bug.cgi?id=452509 Roger Wilco changed: What|Removed |Added Summary|Kdenlive crashes when I |Kdenlive (Appimage) crashes |click onto a video clip in |when I click onto a video |the timeline|clip in the timeline -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452509] Kdenlive crashes when I click onto a video clip in the timeline
https://bugs.kde.org/show_bug.cgi?id=452509 Roger Wilco changed: What|Removed |Added Summary|Kdenlive crashes when I |Kdenlive crashes when I |click onto a video clip in |click onto a video clip in |the timeline that has the |the timeline |pan_zoom effect applied to | |it | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452509] Kdenlive crashes when I click onto a video clip in the timeline that has the pan_zoom effect applied to it
https://bugs.kde.org/show_bug.cgi?id=452509 Roger Wilco changed: What|Removed |Added Platform|Mint (Debian based) |Mint (Ubuntu based) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452509] New: Kdenlive crashes when I click onto a video clip in the timeline that has the pan_zoom effect applied to it
https://bugs.kde.org/show_bug.cgi?id=452509 Bug ID: 452509 Summary: Kdenlive crashes when I click onto a video clip in the timeline that has the pan_zoom effect applied to it Product: kdenlive Version: 21.12.3 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: rogerwilc...@hotmail.de Target Milestone: --- Created attachment 148101 --> https://bugs.kde.org/attachment.cgi?id=148101=edit Kdenlinve gdb debug info + CLI output when launched through CLI 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 *** I could not find 'libmlt-dbg' in the Linux Mint 20.3 Cinnamon software sources. 'apt list libmlt*' only listed these: libmlt++-dev/focal 6.20.0-2 amd64 libmlt++3/focal,now 6.20.0-2 amd64 [installiert] libmlt-data/focal,focal,now 6.20.0-2 all [Installiert,automatisch] libmlt-dev/focal 6.20.0-2 amd64 libmlt6/focal,now 6.20.0-2 amd64 [Installiert,automatisch] STEPS TO REPRODUCE 1. Launch Kdenlive Appimage 21.12.3 from either the CLI or a launcher created for that Appimage 2. Open a project, the respective one was initially created in 21.12.2. (see attached screenshot) - project has 3 audio/video tracks - the only effect used is: pan_zoom 3. click onto clips in the timeline OBSERVED RESULT Kdenlive crashes and shuts down. I did not observe that behavior with the Appimage version 21.12.2 EXPECTED RESULT Clip that I click onto to be selected. Nothing more, nothing less. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Linux Mint 20.3 Una base: Ubuntu 20.04 focal, Kernel: 5.13.0-39-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.2.7 dm: LightDM 1.30.0 KDE Plasma Version: No Plasma, using the Cinnamon DE KDE Frameworks Version: ? Qt Version: 5.12.8-0ubuntu1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 --- Comment #43 from Roger --- (In reply to Andrey from comment #42) > (In reply to Roger from comment #41) > > I'm facing this issue with only one app in autostart (telegram-desktop). It > If you telegram is Snapped, please see discussion above. I have it installed from the openSUSE Main Repository (OSS). See info below: Information for package telegram-desktop: - Repository : Main Repository (OSS) Name : telegram-desktop Version: 3.6.0-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 79,9 MiB Installed : Yes Status : up-to-date Source package : telegram-desktop-3.6.0-1.1.src Upstream URL : https://github.com/telegramdesktop/tdesktop Summary: Messaging application with a focus on speed and security Description: Telegram is a non-profit cloud-based instant messaging service. Users can send messages and exchange photos, videos, stickers, audio and files of any type. Its client-side code is open-source software but the source code for recent versions is not always immediately published, whereas its server-side code is closed-source and proprietary. The service also provides APIs to independent developers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 Roger changed: What|Removed |Added CC||roger...@gmail.com --- Comment #41 from Roger --- I'm facing this issue with only one app in autostart (telegram-desktop). It happens only on Wayland. The machine is relatively modern, so the problem is not related to a slow system. Following my config: Distro: openSUSE Tumbleweed DE: KDE Plasma 5.24.3 Display server: Wayland Qt: 5.15.2 KDE Frameworks: 5.92.0 Kernel: Linux 5.16.14-1-default -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 451679] backups configuration inconsistency after removing one plan
https://bugs.kde.org/show_bug.cgi?id=451679 Vincent ROGER changed: What|Removed |Added Version|unspecified |0.9.1 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 451679] New: backups configuration inconsistency after removing one plan
https://bugs.kde.org/show_bug.cgi?id=451679 Bug ID: 451679 Summary: backups configuration inconsistency after removing one plan Product: kup Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: simon.pers...@mykolab.com Reporter: roger.vins...@gmail.com Target Milestone: --- SUMMARY The backups plan are inconsistent if one backup plan configuration is removed. STEPS TO REPRODUCE I do not have bup on my system 1. Create one backup plan with one external drive (name the plan, using synchronized backup). 2. save backup 3. Create another backup plan with another external drive (name the plan with a different name, using synchronized backup) 4. save backup 5. remove the first plan OBSERVED RESULT The remaining plan is renamed, and all config is reset to "default" so everything is gone (on the kup config) EXPECTED RESULT The remaining plan should not be impacted. SOFTWARE/OS VERSIONS Manjaro Linux with kernel 5.16.14-1 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 142390] can't sort files in directory synchronizer
https://bugs.kde.org/show_bug.cgi?id=142390 Roger changed: What|Removed |Added Latest Commit||These are great suggestions ||and would greatly improve ||the process. CC||leemull...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Roger Noble changed: What|Removed |Added CC||rnbzi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 427530] Shutdown and restart buttons are missing from fullscreen application dashboard.
https://bugs.kde.org/show_bug.cgi?id=427530 Vincent ROGER changed: What|Removed |Added CC||roger.vins...@gmail.com --- Comment #12 from Vincent ROGER --- I am also facing the same issue on KDE neon (with kde 5.23.4). I also use latte dock and the shutdown and restart button disappear after a restart or a shutdown. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447724] Right-clicking a thumbnail produces different result in Preview and Thumbnail modes
https://bugs.kde.org/show_bug.cgi?id=447724 --- Comment #4 from Roger Foss --- I read the comments for bug 423993, and respectfully I really think you should reevaluate. Instead of saying what the thumbnail bar is for, ask what the thumbnails themselves are for and what we should be able to do with them. For example, If I multi-select 3 thumbnails in the thumbnail bar in Preview mode, and want to rotate all of them, it's logical I should be able to right-click on one of the thumbnails in my selection then choose rotate. My intention is to rotate all of the selected images. Right-clicking on the Previewed picture would be fitting if I wanted to rotate just the previewed picture. Anyway, I think you get my point. I'll just comment on the bug 423993 to add my voice, I hope there's nothing wrong in that. Roger On Sat, Jan 1, 2022 at 2:22 PM Maik Qualmann wrote: > Maik Qualmann changed bug 447724 > <https://bugs.kde.org/show_bug.cgi?id=447724> > What Removed Added > CC metzping...@gmail.com > > *Comment # 3 <https://bugs.kde.org/show_bug.cgi?id=447724#c3> on bug > 447724 <https://bugs.kde.org/show_bug.cgi?id=447724> from Maik Qualmann > * > > We already have such a wish with bug 423993 > <https://bugs.kde.org/show_bug.cgi?id=423993>. The thumbnail bar is for > selecting > the image preview. The image preview has context menu with options similar to > the one in the canvas. > > Maik > > -- > You are receiving this mail because: > >- You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423993] Allow rightclick on thumbnails in preview mode
https://bugs.kde.org/show_bug.cgi?id=423993 Roger Foss changed: What|Removed |Added Version|6.2.0 |7.4.0 CC||roger.f...@gmail.com --- Comment #6 from Roger Foss --- Just adding my voice to the sentiment that it should be possible to right-click thumbnails in Preview mode. I encourage a re-thinking. Instead of talking about what the thumbnail bar is for, let's ask what the thumbnails themselves are for - and what we should be able to do with them. If I multi-select 3 thumbnails in the thumbnail bar in Preview mode, and want to rotate all of them, it's logical I should be able to right-click on one of the thumbnails in my selection then choose rotate. My intention is to rotate all of the selected images. If I wanted to rotate just the current picture that is being previewed, then it would be fitting to right-click on the previewed picture. Anyway multiple people have commented on this, just wanted to add my voice. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447724] Right-clicking a thumbnail produces different result in Preview and Thumbnail modes
https://bugs.kde.org/show_bug.cgi?id=447724 --- Comment #2 from Roger Foss --- Hi Gilles, I'm aware, but I still think thumbnails should behave consistently. They represent images, and right clicking should provide options for what you can do with those images. Sure, you should have the same options available when you right click the canvas. But regardless, in my opinion thumbnails should behave consistently. Mind you, I did report it as a minor bug. On Fri, Dec 31, 2021, 10:02 wrote: > caulier.gil...@gmail.com changed bug 447724 > <https://bugs.kde.org/show_bug.cgi?id=447724> > What Removed Added > Version Fixed In 7.5.0 > > -- > You are receiving this mail because: > >- You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447724] New: Right-clicking a thumbnail produces different result in Preview and Thumbnail modes
https://bugs.kde.org/show_bug.cgi?id=447724 Bug ID: 447724 Summary: Right-clicking a thumbnail produces different result in Preview and Thumbnail modes Product: digikam Version: 7.4.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: roger.f...@gmail.com Target Milestone: --- SUMMARY *** The right-click menu is not available from the thumbnail bar in Preview mode. This is inconsistent with right-clicking the same thumbnail in Thumbnail mode. *** STEPS TO REPRODUCE 1. Show an album of pictures in Preview mode 2. Right-click a thumbnail in the thumbnail bar at the top of the window OBSERVED RESULT The right-click menu does not show up. EXPECTED RESULT Right-clicking a thumbnail should produce the same result in Preview as in Thumbnail mode. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.23 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444903] Digikam not updating image metadata
https://bugs.kde.org/show_bug.cgi?id=444903 --- Comment #3 from Roger Noble --- Tried it with Exiv2 0.27.4 and 0.27.5. Same issue with both. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444903] New: Digikam not updating image metadata
https://bugs.kde.org/show_bug.cgi?id=444903 Bug ID: 444903 Summary: Digikam not updating image metadata Product: digikam Version: 7.2.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Engine Assignee: digikam-bugs-n...@kde.org Reporter: rnbzi...@gmail.com Target Milestone: --- SUMMARY Attempting to update image metadata in Digikam fails, producing the error digikam.metaengine: Cannot save metadata using Exiv2 (Error # 21 : "Failed to write image" STEPS TO REPRODUCE 1. In Digikam select Item->Edit Metadata... for an image 2. Change any of the XMP data (for example) 3. Click on OK OBSERVED RESULT The metadata are not updated. The above error is produced when run from the terminal. EXPECTED RESULT The metadata should be updated. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I've also tried this with a build of digikam 7.3.0 and the result is the same. The problem did not exist on Fedora 34 with the same version of digikam. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 427319] less contacts in kaddressbook "my contacts" than in google contacts "contacts"
https://bugs.kde.org/show_bug.cgi?id=427319 Roger Noble changed: What|Removed |Added CC||rnbzi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444600] New: Discover doesn't update packages if there are both i686 and x86_64 versions present
https://bugs.kde.org/show_bug.cgi?id=444600 Bug ID: 444600 Summary: Discover doesn't update packages if there are both i686 and x86_64 versions present Product: Discover Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: lei...@leinir.dk Reporter: rnbzi...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover doesn't update packages if there are both i686 and x86_64 versions present STEPS TO REPRODUCE 1. Wait until there is an update for packages that have both i686 and x86_64 versions currently installed 2. Try to update the packages using Discover OBSERVED RESULT Neither the i686 nor x86_64 packages are updated. Discover still lists them as available updates. EXPECTED RESULT Both the i686 and x86_64 packages should be updated. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Running pkcon update successfully updates both versions. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396290] [PATCH] Possible tool - failgrind
https://bugs.kde.org/show_bug.cgi?id=396290 Roger Light changed: What|Removed |Added Attachment #118745|0 |1 is obsolete|| Attachment #118746|0 |1 is obsolete|| Attachment #118747|0 |1 is obsolete|| Attachment #118748|0 |1 is obsolete|| --- Comment #35 from Roger Light --- Created attachment 142878 --> https://bugs.kde.org/attachment.cgi?id=142878=edit Patch against 3.18.1 This is the old patches combined and refreshed for 3.18.1. It also includes the failgrind-helper utility, which makes it easy to run failgrind against an executable repeatedly until it completes with all memory allocations/syscalls in the program run succeeding, or the executable segfaults - at which point you can see which failures caused the segfault. It is imperfect, but a big improvement over manual testing. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444224] Missing io_uring syscall
https://bugs.kde.org/show_bug.cgi?id=444224 Roger Light changed: What|Removed |Added CC||ro...@atchoo.org --- Comment #1 from Roger Light --- io_uring support was added in 3.17.0: https://valgrind.org/docs/manual/dist.news.html -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 410087] Kate preview plugin doesn't render Markdown with kmarkdownwebview plugin installed
https://bugs.kde.org/show_bug.cgi?id=410087 --- Comment #14 from Roger --- Ok, jmaspons' suggestion in Comment 12, along with the instructions below, solved the problem. "To use the MarkdownPart KParts plugin in a KParts-using applications, often you will need to configure that globally in the Plasma System Settings, and there in the "File Associations" page. Select the MIME type "text/markdown" and in the "Embedding" tab in the "Service Preference Order" group make sure "Markdown View (markdownpart)" is on top of the list." -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 410087] Kate preview plugin doesn't render Markdown with kmarkdownwebview plugin installed
https://bugs.kde.org/show_bug.cgi?id=410087 Roger changed: What|Removed |Added CC||roger...@gmail.com --- Comment #13 from Roger --- I confirm exactly the same behavior and error messages as in Andrey's Comment 10 above. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442691] New: Add property button disappeared in Window menu More action
https://bugs.kde.org/show_bug.cgi?id=442691 Bug ID: 442691 Summary: Add property button disappeared in Window menu More action Product: kwin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: appmenu Assignee: kwin-bugs-n...@kde.org Reporter: rafn...@gmail.com Target Milestone: --- Created attachment 141700 --> https://bugs.kde.org/attachment.cgi?id=141700=edit Add property button is missing The button "add property" disappeared when you want to set on which screen an application should be opened (in case of 2 monitors) STEPS TO REPRODUCE 1. open an application 2. right click on application top bar and select "More actions > Configure Special Application Settings" OBSERVED RESULT In the Window Rules, there is no add property button in Plasma 5.22.5, while it should be to allow user to select screen and set on which screen should open the application EXPECTED RESULT As in previous version, Add Property button should be available to set new properties. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442143] System Monitor crashes when switching to "Applications" section
https://bugs.kde.org/show_bug.cgi?id=442143 --- Comment #1 from Roger --- After resetting "Applications" page to its default state I can access the page again now (although I've never changed anything from the defaults). However, System Monitor keeps crashing when I click on the "Show Details Sidebar" inside the Applications page. The crash can be reproduced every time. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442143] New: System Monitor crashes when switching to "Applications" section
https://bugs.kde.org/show_bug.cgi?id=442143 Bug ID: 442143 Summary: System Monitor crashes when switching to "Applications" section Product: plasma-systemmonitor Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: roger...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.13-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: openSUSE Tumbleweed -- Information about the crash: System Monitor crashes when clicking on "Applications" in the left nav menu. The crash can be reproduced every time. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7faedb6e6980 (LWP 19559))] [KCrash Handler] #6 0x in ?? () #7 0x7faeddd5cbb7 in QQuickItemLayer::~QQuickItemLayer (this=0x55ccf6842820, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickitem.cpp:8370 #8 0x7faeddd5cc29 in QQuickItemLayer::~QQuickItemLayer (this=0x55ccf6842820, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickitem.cpp:8372 #9 0x7faeddedfc93 in QAccessibleQuickItem::role (this=0x55ccf685a1f0) at ../../include/QtQuick/../../../src/quick/items/qquickitem.h:468 #10 0x7faed981fa22 in AtSpiAdaptor::pathForInterface (this=this@entry=0x55ccf472e280, interface=0x55ccf685a1f0) at atspiadaptor.cpp:1540 #11 0x7faed9822874 in AtSpiAdaptor::notifyStateChange (this=this@entry=0x55ccf472e280, interface=, state=..., value=1) at atspiadaptor.cpp:875 #12 0x7faed9823ff2 in AtSpiAdaptor::notify (this=0x55ccf472e280, event=0x7ffe9fa130d0) at atspiadaptor.cpp:900 #13 0x7faeddd6ad47 in QQuickItemPrivate::setEffectiveVisibleRecur (this=this@entry=0x55ccf66fd2e0, newEffectiveVisible=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickitem.cpp:6078 #14 0x7faeddd737a9 in QQuickItem::setParentItem (this=this@entry=0x55ccf6842820, parentItem=parentItem@entry=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickitem.cpp:2726 #15 0x7faeddd73cc6 in QQuickItem::~QQuickItem (this=0x55ccf6842820, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickitem.cpp:2327 #16 0x7faec53eb955 in QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #17 QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #18 0x7faedc8e9c57 in QQmlTableInstanceModel::destroyModelItem (this=, modelItem=0x55ccf6835f70, mode=QQmlTableInstanceModel::Immediate) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qmlmodels/qqmltableinstancemodel.cpp:245 #19 0x7faedc9105d1 in std::function::operator()(QQmlDelegateModelItem*) const (__args#0=0x55ccf6835f70, this=0x7ffe9fa13350) at /usr/include/c++/11/bits/std_function.h:560 #20 QQmlReusableDelegateModelItemsPool::drain(int, std::function) (this=0x55ccf68376b8, maxPoolTime=0, releaseItem=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qmlmodels/qqmldelegatemodel.cpp:3772 #21 0x7faedc8e9683 in QQmlTableInstanceModel::drainReusableItemsPool (this=, maxPoolTime=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/qmlmodels/qqmltableinstancemodel.cpp:290 #22 0x7faedde5bbfc in QQuickTableView::geometryChanged (this=0x55ccf67cd8f0, newGeometry=..., oldGeometry=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquicktableview.cpp:2905 #23 0x7faeddd699cb in QQuickItem::setSize (this=0x55ccf67cd8f0, size=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickitem.cpp:7037 #24 0x7faed8921c25 in QQuickControlPrivate::resizeContent() () from /lib64/libQt5QuickTemplates2.so.5 #25 0x7faed892b011 in QQuickControl::geometryChanged(QRectF const&, QRectF const&) () from /lib64/libQt5QuickTemplates2.so.5 #26 0x7faeddd699cb in QQuickItem::setSize (this=0x55ccf67b4590, size=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickitem.cpp:7037 #27 0x7faeddd54fea in QQuickAnchorsPrivate::setItemSize (v=..., this=0x55ccf67d0d10) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickanchors.cpp:435 #28 QQuickAnchorsPrivate::fillChanged (this=0x55ccf67d0d10) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.3.x86_64/src/quick/items/qquickanchors.cp
[konsole] [Bug 430036] konsole no-toolbar setting missing or forgotten
https://bugs.kde.org/show_bug.cgi?id=430036 roger truong changed: What|Removed |Added CC||dragonrmar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420702] Secondary monitor black after rotation
https://bugs.kde.org/show_bug.cgi?id=420702 Roger Light changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Roger Light --- This is no longer an issue as of at least 5.21.4. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 --- Comment #20 from Roger Wright --- (In reply to Alexander Reinholdt from comment #18) > (In reply to Roger Wright from comment #15) > > I have this too now. Any progress? My symptoms are as above. > > Which version of Smb4K are you using? With Smb4K 3.1.0 or 3.0.7 this should > not happen no more. Thanks. I'll do an upgrade and try again. Thanks for all your work :-) -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 --- Comment #16 from Roger Wright --- (In reply to Alexander Reinholdt from comment #12) > Thank you for reporting this issue. > > Have you tried the approach mentioned in the handbook under "Special > Remarks": > https://docs.kde.org/stable5/en/extragear-network/smb4k/special_remarks. > html#special_remarks_problems_browsing_samba_47 ? > > Does the scanning work when you apply the changes to the smb.conf file? Link no longer valid. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 Roger Wright changed: What|Removed |Added CC||roger_wri...@attglobal.net --- Comment #15 from Roger Wright --- I have this too now. Any progress? My symptoms are as above. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438120] Geolocation data not being saved.
https://bugs.kde.org/show_bug.cgi?id=438120 --- Comment #6 from Roger --- (In reply to Maik Qualmann from comment #4) > What do you mean by step 3 paste coordinates, text coordinates? Are the > coordinates valid? You know that you can drag and drop images from the image > list onto the map? > > Maik I had several pictures with the same coordinates. Under Item Edit Geolocation - I selected one with the proper coordinates and right clicked to copy the coordinates. Then I selected the other picture and right clicked on it and pasted the coordinates. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438120] Geolocation data not being saved.
https://bugs.kde.org/show_bug.cgi?id=438120 --- Comment #5 from Roger --- I went into the Linux version again and I did not have the Settings Metdata Geolocation data checked. But all of the other boxes in tath area except Face Tags was checked. I checked the Geolocation box and tested and it worked fine. then I went back to the Windows machine and checked all the samed settings boxes. Now it works fine. So, maybe problem solved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438120] Geolocation data not being saved.
https://bugs.kde.org/show_bug.cgi?id=438120 --- Comment #2 from Roger --- Settings Metadata Geolocation data is checked. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438120] New: Geolocation data not being saved.
https://bugs.kde.org/show_bug.cgi?id=438120 Bug ID: 438120 Summary: Geolocation data not being saved. Product: digikam Version: 7.2.0 Platform: Microsoft Windows OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Gps Assignee: digikam-bugs-n...@kde.org Reporter: leemull...@comcast.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1.Select jpg file(s) 2. Menu - Item - Edit Geolocation. 3. Paste GPS data- Apply- Apply OBSERVED RESULT In Digikam the pasted GPS data is visible. But, if I view properties of the jpg file in a file manager or Irfanview, the GPS location is not there. Copied the file to a Linux machine and viewed in Digikam and GPS data is not there. Various file managers on the Linux machine do not show the GPS either. So GPS must be stored in the Digikam that it was inserted in, but not being saved to be visible by other apps or Digikam app. I get the same result if I try from the Linux machine first also. EXPECTED RESULT Pasted and saved GPS data should be visible to any other app or file manager on any machine. SOFTWARE/OS VERSIONS Windows: 10 21H1 macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436238] New: open terminal command puts on in the home directory, not the present one
https://bugs.kde.org/show_bug.cgi?id=436238 Bug ID: 436238 Summary: open terminal command puts on in the home directory, not the present one Product: dolphin Version: 20.12.0 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: k...@herz-fischler.ca CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In previous versions of Dolphin the "open terminal" short cut (to which I assign shift + F4 open a full screen terminal in the directory was open in Dolphin. [I need a full screen because I move it to another desktop and issue commands in the terminal. Since I am usually several levels below /home I have to go to "location", copy it and paste it in the terminal STEPS TO REPRODUCE 1. go to tools --> open terminal (shift + F4) 2. Konsole opens in the home directory (/home/liliane) 3 OBSERVED RESULT One is in /home/liliane/ EXPECTED RESULT To be in the directory which is open in Dolphin SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Mageis 8 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436234] New: the multitude of "random" plasma crashes etc. may in fact be due to a firmware problem
https://bugs.kde.org/show_bug.cgi?id=436234 Bug ID: 436234 Summary: the multitude of "random" plasma crashes etc. may in fact be due to a firmware problem Product: systemsettings Version: unspecified Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: k...@herz-fischler.ca Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Over the last few years I and many others have experienced what can only be described as random (and thus unrepeatable) stalls, crashes, loss of cunctionality etx. This has occurred on different distributions. When it first happened (Mageia 6 and 7)I thought that it might be the chips on my new computer, but changing the chips did not help. I thus---not being willing to do away with KDE Plasma---learned to live with these stalls. When my computer went into a complete shutdown and I could not reinstall the distribution (Mageia 8 to be precise) I had it tested. My computer technician reported that even though the hard drive tested correctly they had received a firmware update from Kingston concerning the A400 series (the warning may have applied to other Kingston models too). I suggested that they simply replace the hard drive and so they installed a WD Blue series. The system has been working perfectly. In particular whereas peviously the system monitor did not show any CPU history, it now does. Perhaps you would like to put up a notice about this. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433163] 'configure digital clock' resizes kickoff
https://bugs.kde.org/show_bug.cgi?id=433163 --- Comment #1 from roger truong --- ive only been able to reproduce this bug in x11. wayland seems to be fine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433163] 'configure digital clock' resizes kickoff
https://bugs.kde.org/show_bug.cgi?id=433163 roger truong changed: What|Removed |Added CC||dragonrmar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433163] New: 'configure digital clock' resizes kickoff
https://bugs.kde.org/show_bug.cgi?id=433163 Bug ID: 433163 Summary: 'configure digital clock' resizes kickoff Product: plasmashell Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: dragonrmar...@gmail.com Target Milestone: 1.0 Created attachment 135843 --> https://bugs.kde.org/attachment.cgi?id=135843=edit kickoff vs clock interaction SUMMARY When the new kickoff menu is open, and 'configure digital clock' is selected through the widget, it sometimes causes the kickoff menu to resize itself so that the next becomes unreadable. This sometimes takes a few tries to reproduce, but I can get it to happen pretty consistently on a fresh user profile. So far this seems to only affect the clock and not other widgets (still not sure if this bug should be filed under kickoff or clock so feel free the change). STEPS TO REPRODUCE 1. open new kickoff and keep it open 2. right click digital clock widget 3. select 'configure digital clock' OBSERVED RESULT The applications list shrinks in width to make the text unreadable [see attachment] EXPECTED RESULT Kickoff closes as the new systems window is open and comes into focus SOFTWARE/OS VERSIONS Linux: 5.10.16 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION unsure what logs i can attach for this -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 roger truong changed: What|Removed |Added CC||dragonrmar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375446] First stashed working set disappears
https://bugs.kde.org/show_bug.cgi?id=375446 Roger changed: What|Removed |Added Version|5.6.0 |5.6.1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375446] First stashed working set disappears
https://bugs.kde.org/show_bug.cgi?id=375446 Roger changed: What|Removed |Added CC||roger...@gmail.com --- Comment #2 from Roger --- I confirm the bug, exactly as reported. I'm using Kdevelop version 5.6.1, in openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427504] Jittery scrolling behavior with a free-scrolling mouse
https://bugs.kde.org/show_bug.cgi?id=427504 --- Comment #8 from roger truong --- (In reply to Bernhard from comment #7) > I am also on Arch Linux with a different free scrolling Logitech mouse and > it very much has not gone away for me unfortunately. Are you able to attach a video and relevant logs? I can't seem to reproduce the issue on the current release (20.12.1) or the latest master. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431571] Application menu search box does not display typed text
https://bugs.kde.org/show_bug.cgi?id=431571 Alain Roger changed: What|Removed |Added CC||alain.ro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431571] New: Application menu search box does not display typed text
https://bugs.kde.org/show_bug.cgi?id=431571 Bug ID: 431571 Summary: Application menu search box does not display typed text Product: plasmashell Version: 5.19.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: alain.ro...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 134824 --> https://bugs.kde.org/attachment.cgi?id=134824=edit Application menu search box SUMMARY -Under Kubuntu 20.10, typing text in the search box of the widget "application menu" does not display (and do not search) text. STEPS TO REPRODUCE 1. switch to "Application Menu widget" (instead of Application launcher widget) 2. Click on KDE logo to open main menu 3. in search box, type some text to search and no text will be displayed OBSERVED RESULT -Typed text is not displayed in search box, so no search at all EXPECTED RESULT -Typed text is displayed and partial results are displayed in menu as potential apps searched SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.10 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -none -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430111] Plasma Wayland crashes when changing order of pinned application
https://bugs.kde.org/show_bug.cgi?id=430111 --- Comment #7 from Roger --- I confirm the issue. Reordering the icons on the "Task Manager" panel, whether they're pinned or not (running apps), makes Plasma Wayland crash. My config: plasmashell 5.20.4 Qt: 5.15.2 KDE Frameworks: 5.77.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430111] Plasma Wayland crashes when changing order of pinned application
https://bugs.kde.org/show_bug.cgi?id=430111 Roger changed: What|Removed |Added CC||roger...@gmail.com --- Comment #6 from Roger --- I confirm the issue. Reordering the icons on the "Task Manager" panel, whether they're pinned or not (running apps), makes Plasma Wayland crash. My config: plasmashell 5.20.4 Qt: 5.15.2 KDE Frameworks: 5.77.0 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 367753] notifications do not play sound
https://bugs.kde.org/show_bug.cgi?id=367753 roger peppe changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from roger peppe --- Updating the status to "Confirmed" because this still appears to be a bug. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 367753] notifications do not play sound
https://bugs.kde.org/show_bug.cgi?id=367753 --- Comment #3 from roger peppe --- I'm using another laptop now from when I first reported the bug (an X1 Carbon running Ubuntu 20.04.01) and I don't use IRC much these days, but I can still reproduce the issue. As an example, I chose the file /usr/share/sounds/gnome/default/alerts/sonar.ogg. I verified that this file can be played fine by other apps on the system, but no sound is made when clicking the "play" button in the notification settings. Please let me know if there's any other information you'd like which might help you diagnose this problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427504] Jittery scrolling behavior with a free-scrolling mouse
https://bugs.kde.org/show_bug.cgi?id=427504 roger truong changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from roger truong --- I'm not sure what changed since the last version, but the issue has gone away with 1.12.0, even when smooth scrolling is enabled. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 422691] wrong device in hover text on bluetooth icon
https://bugs.kde.org/show_bug.cgi?id=422691 Roger Noble changed: What|Removed |Added CC||rnbzi...@gmail.com Version|5.19.0 |5.20.3 --- Comment #4 from Roger Noble --- This bug or something very similar appears to be present in 5.20.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424488] Log out then login causes plasmashell to crashes
https://bugs.kde.org/show_bug.cgi?id=424488 --- Comment #4 from Roger --- I confirm that the bug persists on: openSUSE-release 2020-759.1 plasmashell 5.20.2 Qt 5.15.1 KDE Frameworks 5.75.0 Linux 5.9.1-2-default x86_64 Using loginctl commands I observed that the session keeps running even after log out. This is the cause of all the problems when logging in again. It seems related to bug: https://bugs.kde.org/show_bug.cgi?id=359651 Some of the process that persist with my session are: kio_http_cache_cleaner, kwin_x11, hp-systray ... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427504] Jittery scrolling behavior with a free-scrolling mouse
https://bugs.kde.org/show_bug.cgi?id=427504 --- Comment #3 from roger truong --- I understand I have a pretty niche use case, so having the fix in the form of disabling smooth scrolling in the next release is good enough for me. As for detecting free-scrolling mice, it might be quite difficult unfortunately. Based on the last thread, I suspect that my mouse is just sending a couple hundred to a couple thousand normal scroll events. https://bugs.kde.org/show_bug.cgi?id=420492#c15 I'd be willing to help test this with my hardware if possible. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427504] inconsistent scrolling behavior with a free-scrolling mouse
https://bugs.kde.org/show_bug.cgi?id=427504 roger truong changed: What|Removed |Added CC||dragonrmar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427504] inconsistent scrolling behavior with a free-scrolling mouse
https://bugs.kde.org/show_bug.cgi?id=427504 --- Comment #1 from roger truong --- Created attachment 132249 --> https://bugs.kde.org/attachment.cgi?id=132249=edit expected scroll behavior with 1.11.1 Here is the expected behavior for comparison. The bug is difficult to show on video but most noticeable in comparing the scrollbar behavior. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427504] New: inconsistent scrolling behavior with a free-scrolling mouse
https://bugs.kde.org/show_bug.cgi?id=427504 Bug ID: 427504 Summary: inconsistent scrolling behavior with a free-scrolling mouse Product: okular Version: 1.11.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: dragonrmar...@gmail.com Target Milestone: --- Created attachment 132248 --> https://bugs.kde.org/attachment.cgi?id=132248=edit jittery scrolling with v1.11.2 SUMMARY When using a free-scrolling mouse (Logitech G502), there is a regression in scrolling behaviors. It is jittery and jumps to the next section rather than moving smoothly. The scrolling also is slow to start and takes a few seconds to pick up speed, like it is using inertial scrolling. STEPS TO REPRODUCE 1. Update to Okular 1.11.2 2. Open a long PDF 3. scroll with a free-scroll mouse OBSERVED RESULT jittery scrolling (see the video) EXPECTED RESULT scrolling should be smooth as in previous version 1.11.1 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION Doing a git bisect narrowed down the bad commit to https://github.com/KDE/okular/commit/a5be0149ec627fbc086e5b26cbbe7be13cde49b8 This issue is currently fixed in master with commit https://github.com/KDE/okular/commit/d78e2ff9e719d2e14abd11083d3a7466f5ea2736 However, it is present as of the latest release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424488] Log out then login causes plasmashell to crashes
https://bugs.kde.org/show_bug.cgi?id=424488 Roger changed: What|Removed |Added CC||roger...@gmail.com --- Comment #1 from Roger --- Created attachment 130922 --> https://bugs.kde.org/attachment.cgi?id=130922=edit crash report plasmashell crashes on login after a logout. It not happens on the first login after a reboot, only when logout and login again. Versions: plasmashell 5.19.4 Qt 5.15.0 KDE Frameworks 5.73.0 openSUSE Tumbleweed 20200814 Linux 5.8.0-1-default x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425054] KWin crash when repeatedly triggering present windows hot corner
https://bugs.kde.org/show_bug.cgi?id=425054 Roger changed: What|Removed |Added CC||roger...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421539] Plasma crashed while deleting a desktop shortcut
https://bugs.kde.org/show_bug.cgi?id=421539 Roger changed: What|Removed |Added CC||roger.mcm...@bigfoot.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409739] [Question] Importing video files with multiple audio streams causes Kdenlive to only use the first audio stream - is multi-stream audio import worked on?
https://bugs.kde.org/show_bug.cgi?id=409739 Roger changed: What|Removed |Added CC||rogertgodzilla...@yahoo.com --- Comment #4 from Roger --- I would really like this feature. I have a bad habit of forgetting to do a sound check before recording, and having to deal with atrocious audio balance issues when editing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420702] Secondary monitor black after rotation
https://bugs.kde.org/show_bug.cgi?id=420702 --- Comment #4 from Roger Light --- Just a single Xorg instance, sorry if multihead means multiple instances. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420702] Secondary monitor black after rotation
https://bugs.kde.org/show_bug.cgi?id=420702 --- Comment #2 from Roger Light --- I have done a clean install (but still have an image of the old install, although that's irrelevant). The problem persists. I created a fresh user and the problem is not present for that user, so it must be a user configuration issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420702] Secondary monitor black after rotation
https://bugs.kde.org/show_bug.cgi?id=420702 --- Comment #1 from Roger Light --- I'm considering doing a clean reinstall, so if you'd like any debugging doing on this please let me know what I could do. I'm not afraid of gdb. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420789] New: Facetag dropdown list is too narrow
https://bugs.kde.org/show_bug.cgi?id=420789
Bug ID: 420789
Summary: Facetag dropdown list is too narrow
Product: digikam
Version: 7.0.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Faces-Workflow
Assignee: digikam-bugs-n...@kde.org
Reporter: roger.f...@gmail.com
Target Milestone: ---
Created attachment 128019
--> https://bugs.kde.org/attachment.cgi?id=128019=edit
Face nametag dropdown list too narrow
SUMMARY
The dropdown list that shows suggested names when searching for name tags for
faces is too narrow if you have several similar long names or long tag paths.
Example:
I've organized my tags in a hierarchy, something like:
People/
Collegues/
Company/
Roger Dodger
Families/
Norm Gundersson/
Roger Gunderson
Friends/
Jenny/
Roger Handsome
so when I want to tag Jenny's friend Roger Handsome and search for his name,
several Roger's show up in the dropdown list but it's not clear which one to
choose.
See attached screenshot.
STEPS TO REPRODUCE
1. Create a tag hierarchy with similar names in different branches; eg.
'Families/Gundersson Family/Roger Gundersson' and
'Families/Christensen Family/Roger Christensen'.
For good measure, also add
'Collegues/Company/Roger Dodger' and
'Friends/Jenny/Roger Handsome'.
2. Scan for unknown faces.
3. Prepare to tag unknown faces.
Go to Thumbnails view, People tab on left hand side.
Click on the 'Unknown' name tag to see unknown faces.
4. Hover the mouse over an unknown face, and start typing the name Roger.
OBSERVED RESULT
As you start typing the first few letters of 'Roger', a dropdown list of names
that begin with those letters appears. This is helpful, but the dropdown is
not wide enough to show the full tag path and tag names, making it difficult to
distinguish between the different Rogers.
See attached screenshot for a real example.
EXPECTED RESULT
I expect Digikam to show the full path and tag name, like so:
Families/Gunderson Family/Roger Gundersson
Collegues/Company/Roger Dodger
Friends/Jenny/Roger Handsome
or maybe better: [tag name] in [full tag path]
Roger Gundersson in Families/Gundersson Family
Roger Dodger in Collegues/Company
Roger Handsome in Friends/Jenny
the dropdown list should automatically adjust its width to accommodate the full
name and path. If dropdown box left-aligned the tag name and also left-aligned
the tag paths, it would visually be very easy to pick out the correct one.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Manjaro 'Lysia' with KDE 5.18.4
(available in About System)
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 --- Comment #20 from roger truong --- (In reply to Nate Graham from comment #19) > Git commit 08d368c13b0fa7368be9720b8de1b7a67188b8e9 by Nate Graham, on > behalf of Kezi Olio. I just tested the commit and that fixed my issues, thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420702] New: Secondary monitor black after rotation
https://bugs.kde.org/show_bug.cgi?id=420702 Bug ID: 420702 Summary: Secondary monitor black after rotation Product: kwin Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: ro...@atchoo.org Target Milestone: --- SUMMARY I have two monitors, a landscape 1680x1050 (main monitor) and a portrait 1920x1080, rotated 90 degrees anticlockwise (secondary monitor). Nvidia graphics card, with the proprietary drivers. When I log in, the secondary monitor is entirely black. If I move my mouse to the monitor, I can see it. If I try to drag a window to it, I can see the mouse cursor but no window. If I use Ctrl-Alt-F2 to swap to a console, then swap back to the desktop the problem is resolved and I have a notification stating that kwin restarted desktop effects due to a graphics change. STEPS TO REPRODUCE 1. Starting point - everything is displaying as expected, with one monitor landscape and the secondary monitor portrait 2. Open System Settings/Display Configuration 3. Disable the secondary monitor and click Apply 4. Enable the secondary monitor (this will have reverted to landscape mode) and click Apply 5. -> The monitor should now display the desktop as normal (although in the wrong orientation in my case) 6. Click on "90 degrees anticlockwise" orientation, then click Apply 7. -> The monitor will be black, with a visible mouse cursor The same behaviour is shown going from no rotation to 90 degrees clockwise, or from 180 degrees rotation to either of the portrait orientations, but it works fine going from no rotation to 180 degrees. OBSERVED RESULT The secondary monitor is entirely black, but with a visible mouse pointer. Attempting to move windows to the secondary monitor shows the mouse pointer but no window. EXPECTED RESULT A normal desktop showing on the monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 kwin version: 5.18.4.1-0ubuntu2 ADDITIONAL INFORMATION This is easily reproduceable, I can provide more details / debugging if needed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 --- Comment #13 from roger truong --- After looking through the rest of pageview.cpp, I think I narrowed down the problem to the auto limit_value function. https://invent.kde.org/kde/okular/-/blob/master/ui/pageview.cpp#L5369 https://invent.kde.org/kde/okular/-/blob/master/ui/pageview.cpp#L5400 (In reply to Keziolio from comment #10) > Regarding the original bug, the behaviour of the scroll events is programmed > to be literally the same as it was before, probably QScroller::scrollTo > behaves in a suboptimal way if it's flooded with events, I'll see if > something comes to mind Changing the value for nSteps to 2000 from 200 brought back the scrolling from previous versions. It seems that the regression may be in animation speed rather than scrolling if none of the code has changed. It also brought up another bug in the animations with the Contents view. When continuously scrolling, the headings don't advance as they did in 1.9.x. It jumps to whatever heading the current page is on once scrolling has stopped. I'm unsure if this qualifies for a separate bug report, as the synchronous nature of the animations lead me to believe these bugs may be related. The effect can be seen in Contents pane of the videos attached in the OP as well. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 --- Comment #6 from roger truong --- I complied from source and tested out different MaximumVelocity values, trying 1, 10, and 100. Increasing the values made scrolling appear to accelerate faster, but it was still capped at the same maximum scroll speed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] 20.04.0 significantly slows down mouse scrolling with a "hyperscroll" mouse or a touchpad driver that sends mouse wheel scroll events when configured for greater speed
https://bugs.kde.org/show_bug.cgi?id=420492 roger truong changed: What|Removed |Added CC||dragonrmar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420492] New: 20.04.0 significantly slows down mouse scrolling
https://bugs.kde.org/show_bug.cgi?id=420492 Bug ID: 420492 Summary: 20.04.0 significantly slows down mouse scrolling Product: okular Version: 20.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: dragonrmar...@gmail.com Target Milestone: --- SUMMARY 20.04.0 update breaks fast scrolling in Okular. Most noticeable with a "hyperscroll" mouse wheel. STEPS TO REPRODUCE 1. open any PDF or EPub file in 20.04.0 2a. with a hyperscroll mouse, free scroll the mouse wheel inside the document panel 2b. with a normal mouse, scroll as fast as possible inside the document window 3. downgrade to 1.9.3 and repeat step 2 OBSERVED RESULT Scrolling the same amount of clicks scrolls down less lines in 20.04.0 compared to 1.9.3. Scrolling with a hyperscroll wheel significantly limits the speed of scrolling to make free scrolling unusable. This bug is only observed when scrolling in the document panel. Scrolling in the navigation panel or in the scrollbar on the right produces the expected scroll speed. EXPECTED RESULT The scroll speed in the document panel is as fast as in the other panels and keeps the same speed as 1.9.3 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.4.1-1 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 (built against 5.14.2) ADDITIONAL INFORMATION Mouse: Logitech G502 with free scroll also tested with a generic mouse with normal scroll wheel videos of the scrolling attached: https://youtu.be/wIts9r-meME https://youtu.be/nfDjuFkjQLE -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375220] mouse wheel scrolling broken after update to 16.12
https://bugs.kde.org/show_bug.cgi?id=375220 roger truong changed: What|Removed |Added CC||dragonrmar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420080] New: Ctrl+B prefix does nothing under tmux session after last update
https://bugs.kde.org/show_bug.cgi?id=420080 Bug ID: 420080 Summary: Ctrl+B prefix does nothing under tmux session after last update Product: konsole Version: 19.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: roger.vins...@gmail.com Target Milestone: --- The Ctrl+B binding prefix of tmux does nothing under konsole (no shortcuts are binded to Ctrl+B in konsole - default behavior) STEPS TO REPRODUCE 1. launch tmux session 2. use default config 3. Ctrl+B and any tmux key (such as c or ") does nothing OBSERVED RESULT Nothing EXPECTED RESULT Standard behavior under tmux Linux/KDE Plasma: Kde neon 5.18.4 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Worked perfectly before last update. This issue is not observed under QTerminal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399532] Icons do not show correctly on desktop
https://bugs.kde.org/show_bug.cgi?id=399532 --- Comment #6 from Roger Smith --- For a number of reasons, after 10 years of use, I stopped using OpenSUSE / KDE about 12 months ago so I am unable to confirm this issue is fixed. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 --- Comment #7 from Roger Larsson --- Note: I am running pure plasma now! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 --- Comment #6 from Roger Larsson --- Created attachment 125157 --> https://bugs.kde.org/attachment.cgi?id=125157=edit strace of process So, when I got to the computer my screen was locked showing a time more than 12 h old. It was not possible to log in - no field for entry. But the kscreen lock process existed, straced it (see attachment) tried "kill -USR1 pid" no change, tried "kill -USR2 pid" time on screen updated and I was able to log in. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 --- Comment #5 from Roger Larsson --- Created attachment 124796 --> https://bugs.kde.org/attachment.cgi?id=124796=edit Another update (zypper history) After update problems reappeared in force... (unusable the day after) But after I changed from Plasma (Wayland or Full Wayland - don't remember) to pure Plasma (without Wayland) it works again. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 Roger Larsson changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 --- Comment #4 from Roger Larsson --- Created attachment 124629 --> https://bugs.kde.org/attachment.cgi?id=124629=edit zypp log Not seen the problem (nor rebooted since 2019-11-13 update), together with replacing CPU (disks are the same, still no external GPU) something (HW or SW) has fixed the issue! Old CPU: Intel Core i5-2500K RAM: 2*16GB + 2*8GB = 24GB DDR3 MB: ASUS P8H67-M New CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz RAM: 4*16G = 32GB DDR3 MB: ASUS H97M-PLUS Do not remember if the Power unit got replaced too, probably. Inherited the components from my children... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414920] Plasma freeze and crash while searching
https://bugs.kde.org/show_bug.cgi?id=414920 --- Comment #6 from roger herz-fischler --- I have just attached three snapshots, but I have other snapshots showing freezing for different operations over a few months period. That it is the newest version of plasma that is at fault is virtually (no pun intended) assured by the fact that since I reinstalled Mageia version 6.1 I have not experienced these problems. At first I thought the problem was with the chipset, but the problems persisted even though I had the chipset replaced. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414920] Plasma freeze and crash while searching
https://bugs.kde.org/show_bug.cgi?id=414920 --- Comment #5 from roger herz-fischler --- Created attachment 124408 --> https://bugs.kde.org/attachment.cgi?id=124408=edit double peak just opening open office -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414920] Plasma freeze and crash while searching
https://bugs.kde.org/show_bug.cgi?id=414920 roger herz-fischler changed: What|Removed |Added CC||k...@herz-fischler.ca --- Comment #4 from roger herz-fischler --- Created attachment 124407 --> https://bugs.kde.org/attachment.cgi?id=124407=edit simple search in kwrite note how there is little cpu usage, but that the total usage is 100% -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414920] Plasma freeze and crash while searching
https://bugs.kde.org/show_bug.cgi?id=414920 --- Comment #3 from roger herz-fischler --- Created attachment 124406 --> https://bugs.kde.org/attachment.cgi?id=124406=edit long freeze while switching desktops -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 414863] New: Option to place Yakuake window at bottom of the screen
https://bugs.kde.org/show_bug.cgi?id=414863 Bug ID: 414863 Summary: Option to place Yakuake window at bottom of the screen Product: yakuake Version: 3.0.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: roger.f...@gmail.com Target Milestone: --- SUMMARY I really would love it if Yakuake got an option that allows you to select whether the terminal window should scroll down from the top OR up from the bottom. I would love it if the window could be placed at the bottom of my screen. Like may others my age, I use progressive prescription glasses where only part of the glass lets you focus well on the head-to-screen distance. Being able to place the terminal window at the bottom is much more comfortable. There is less eye strain and tilting of the head. Currently Yakuake has an option to specify the window's horizontal placement. Just add a similar option to specify the vertical placement. I would make the animation 'rolls out' the window automatically go from the top or bottom edge, or from the left or right edge that's closest to the window. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 Roger Larsson changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|FIXED |--- --- Comment #3 from Roger Larsson --- This interface is confusing - removing NEEDSINFO -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414024] Greeter image shown, but there is no process behind it for second session
https://bugs.kde.org/show_bug.cgi?id=414024 Roger Larsson changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Roger Larsson --- Time on both accounts should be identical, I think her time was from when the process crached. I did a C-A-Backspace Backspace on her session it begun working again after that. Next time... -- You are receiving this mail because: You are watching all bug changes.
