[dolphin] [Bug 485198] New: Unknown error condition: [8216] Unknown error 8216 when trying to access smb share
https://bugs.kde.org/show_bug.cgi?id=485198 Bug ID: 485198 Summary: Unknown error condition: [8216] Unknown error 8216 when trying to access smb share Classification: Applications Product: dolphin Version: 24.02.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: vic...@pm.me CC: kfm-de...@kde.org Target Milestone: --- Created attachment 168263 --> https://bugs.kde.org/attachment.cgi?id=168263&action=edit A screenshot of the error When trying to access a SMB share from Dolphin by entering the smb-path (e.g. smb:\\IP) an error appears with the following text: Internal Error Please send a full bug report at https://bugs.kde.org Unknown error condition: [8216] Unknown error 8216 STEPS TO REPRODUCE 1. In Dolphin, navigate on the left to "Remote" - "Network" 2. Enter the smb-path at the top bar where it says "Enter server URL (e.g. smb:\\[ip address])" <- in my case i entered smb:\\10.0.0.20 3. An error appears with the text: Internal Error Please send a full bug report at https://bugs.kde.org Unknown error condition: [8216] Unknown error 8216 OBSERVED RESULT Entering a SMB path generates an error in dolphin: Internal Error Please send a full bug report at https://bugs.kde.org Unknown error condition: [8216] Unknown error 8216 EXPECTED RESULT Expected Dolphin to access the smb share without issues and able to browse the smb contents. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse tumbleweed - Kernel 6.8.2.1 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION See attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359783] Right-column-aligned desktop icons move all the way to the left when icons are added or moved
https://bugs.kde.org/show_bug.cgi?id=359783 Victor changed: What|Removed |Added CC||svictorh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 444040] New: Kickoff (Application Launcher 2.0) type to search regression with multiple screens instances
https://bugs.kde.org/show_bug.cgi?id=444040 Bug ID: 444040 Summary: Kickoff (Application Launcher 2.0) type to search regression with multiple screens instances Product: krunner Version: 5.23.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: victor.it...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Kickoff (Application Launcher 2.0) type to search regression with multiple instances of Kickoff because of multi-screen usage: No character is being input. After upgrading to KDE Neon 5.23.0, whenever opening any of the screens application launcher and start typing to search, nothing is happening, no character is appearing in the "Search..." input field at the top of the menu. STEPS TO REPRODUCE 1. Add one or more "Default Panel" which comes with Kickoff by default as the application launcher on each screen. 2. Open any of the Kickoff instance and use it. 3. Open any other of the Kickoff instances and type directly without clicking in the "Search..." input field at the top. OBSERVED RESULT Nothing happens in that other Kickoff instance; no character is appearing in that Kickoff instance "Search..." input. If you try then clicking in the "Search..." input field and type then you see the characters you are now typing but the search doesn't work. But if you open the initial Kickoff instance then you see all the characters you typed before and that didn't appear in the second Kickoff instance. EXPECTED RESULT In the previous version of KDE neon 5.22.90, whatever Kickoff instance you may have opened, typing directly filled the "Search..." input field and the search was working just fine. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.23.0 (user) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Graphics Platform: X11 Screens: 3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Victor changed: What|Removed |Added CC||svictorh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426586] New: systemsettings5 PID: 8040 Señal: Segmentation fault (11) Time: 15/9/20 23:12:40 to can be opened after the instalation. I can´t open efects kde in the windows as ma
https://bugs.kde.org/show_bug.cgi?id=426586 Bug ID: 426586 Summary: systemsettings5 PID: 8040 Señal: Segmentation fault (11) Time: 15/9/20 23:12:40 to can be opened after the instalation. I can´t open efects kde in the windows as magic lamp and others Product: systemsettings Version: 5.14.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: quet...@hotmail.com Target Milestone: --- Application: systemsettings5 (5.14.5) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 5.4.50-amd64-desktop x86_64 Distribution: Deepin 20 -- Information about the crash: - Custom settings of the application: kde settings no can be openen never. ever time to click in the aplication it´s no work and showme message abot the fail -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0b2a15ee80 (LWP 7351))] Thread 9 (Thread 0x7f0b0a5a6700 (LWP 7359)): #0 0x7f0b2c2ebb33 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0b2c2ec0e0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0b2c2ec25c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0b2e3d8753 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0b2e38615b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0b2e1d5e76 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0b2d5f2bc5 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f0b2e1dfa67 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0b2cb81fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7f0b2ded14df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f0b0bd7e700 (LWP 7358)): #0 0x7f0b2dec6816 in __GI___poll (fds=0x7f0b04004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0b2c2ec136 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0b2c2ec25c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0b2e3d8753 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0b2e38615b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0b2e1d5e76 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0b2d5f2bc5 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f0b2e1dfa67 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0b2cb81fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7f0b2ded14df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f0b20dfa700 (LWP 7357)): #0 0x7f0b2cb8800c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55eee1f730fc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0b2cb8800c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55eee1f82d40, cond=0x55eee1f730d0) at pthread_cond_wait.c:502 #2 0x7f0b2cb8800c in __pthread_cond_wait (cond=0x55eee1f730d0, mutex=0x55eee1f82d40) at pthread_cond_wait.c:655 #3 0x7f0b28770457 in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #4 0x7f0b2876a5ab in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #5 0x7f0b2876b1ac in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #6 0x7f0b2876c36c in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #7 0x7f0b28896d6a in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #8 0x7f0b2876bcc0 in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #9 0x7f0b2888c2ee in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #10 0x7f0b2885f7f6 in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #11 0x7f0b2cb81fa3 in start_thread (arg=) at pthread_create.c:486 #12 0x7f0b2ded14df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f0b20ffb700 (LWP 7356)): #0 0x7f0b2cb8800c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55eee1f730fc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0b2cb8800c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55eee1f82d40, cond=0x55eee1f730d0) at pthread_cond_wait.c:502 #2 0x7f0b2cb8800c in __pthread_cond_wait (cond=0x55eee1f730d0, mutex=0x55eee1f82d40) at pthread_cond_wait.c:655 #3 0x7f0b28770457 in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #4 0x7f0b2876a5ab in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #5 0x7f0b2876b1ac in () at /lib/x86_64-linux-gnu/librsvg-2.so.2 #6 0x7f0b2876c36c in () at /lib/x86_64-linux-
[Akonadi] [Bug 427618] New: Akonadi server does not start and kontact suite is unusable
https://bugs.kde.org/show_bug.cgi?id=427618
Bug ID: 427618
Summary: Akonadi server does not start and kontact suite is
unusable
Product: Akonadi
Version: unspecified
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: vikd...@live.fr
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. Installed akonadi and all kde kontact applications on a fresh installation
but with an imported home partition (without hidden files so a priori no config
files included that should not be important
2. Tried to start kmail and all other applications
OBSERVED RESULT
Applications crashes and return an error concerning akonadi
EXPECTED RESULT
It should start with no error, i suppose at least
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Starting akonadi with $akonadictl start --verbose
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Icon theme "ubuntu-mono-dark" not found.
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Found mysql_install_db: "/usr/bin/mysql_install_db"
org.kde.pim.akonadiserver: Found mysqlcheck: "/usr/bin/mysqlcheck"
org.kde.pim.akonadiserver: Using mysqld: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: Failed to detect mysqld version!
org.kde.pim.akonadiserver: mysqld reports version 0.0.0 (Oracle MySQL)
org.kde.pim.akonadiserver: Executing: "/usr/bin/mysql_install_db"
"--defaults-file=/etc/xdg//akonadi/mysql-global.conf --basedir=/usr
--datadir=/home/USERNAME/.local/share/akonadi/db_data/"
org.kde.pim.akonadiserver: Executing: "/usr/bin/mysqld"
"--defaults-file=/home/USERNAME/.local/share/akonadi/mysql.conf
--datadir=/home/USERNAME/.local/share/akonadi/db_data/
--socket=/run/user/1000/akonadi/mysql.socket
--pid-file=/run/user/1000/akonadi/mysql.pid"
org.kde.pim.akonadiserver: Could not start database server!
org.kde.pim.akonadiserver: executable: "/usr/bin/mysqld"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/USERNAME/.local/share/akonadi/mysql.conf",
"--datadir=/home/USERNAME/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: process error: "execvp: Permission denied"
org.kde.pim.akonadiserver: terminating connection threads
org.kde.pim.akonadiserver: terminating service threads
org.kde.pim.akonadiserver: stopping db process
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
Report of Akonadi Console :
Akonadi Server Self-Test Report===
Test 1: SUCCESS
Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server
configuration and was found on your system.
File content of '/home/USERNAME/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Host=
Name=akonadi
Options="UNIX_SOCKET=/run/user/1000/akonadi/mysql.socket"
ServerPath=/usr/bin/mysqld
StartServer=true
Test 2: SUCCESS
Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the
recommended setup for a secure system.
Test 3: SUCCESS
MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server
'/usr/bin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure
you have the necessary read and execution rights on the server executable. The
server executable is typically called 'mysqld'; its location varies depending
on the distribution.
Test 4: SUCCESS
MySQL server is executable.
Details: MySQL server found: /usr/bin/mysqld Ver 10.5.5-MariaDB for Linux on
x86_64 (Arch Linux)
Test 5: SUCCESS
No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The
log can be found in '/home/USERNAME/.local/share/akonadi/db_data/mysql.err'.
Test 6: SUCCESS
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is
readable at /etc/xdg//akonadi/mysql-global.conf.
File content of '/etc/xdg//akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp
#
[mysqld]
# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#
sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_da
[Akonadi] [Bug 427618] Akonadi server does not start and kontact suite is unusable
https://bugs.kde.org/show_bug.cgi?id=427618 --- Comment #3 from Victor --- Version 20.08.1-2 Thanks a lot the command sudo aa-complain /usr/bin/akonadiserver worked. But if I sudo aa-enforce /usr/bin/akonadiserver the problem returns. Also I apparently have to do that after the computer has been shut down. Have you got any idea to solve it permanently ? Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428105] New: Dolphin can't find all the files located in my /home
https://bugs.kde.org/show_bug.cgi?id=428105 Bug ID: 428105 Summary: Dolphin can't find all the files located in my /home Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: svictorh...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 132641 --> https://bugs.kde.org/attachment.cgi?id=132641&action=edit A simple exemple of dolphin missing some files in my /home. In this example, it just found .bash_history file, but actually there is .bash_logout and .bashrc in the directory. SUMMARY I've been using plasma for about 3 weeks and sometimes i needed to find configuration files in my /home directory. I know that configuration files are usually hidden so i have already changed my search options in the system settings to it index hidden files and my dolphin is configured to show hidden files as well. When i search for some configuration files, dolphin simply can't find a great part of them, even if the files in fact exist in /home/USER folder or in sub-directories of it. In fact it can find usually one or two files with the name i asked, but it simply don't show all the possible files. In some folders, Dolphin can't find a thing, like in .cache folder, .config, etc. I obviously tried to click in another option in the results, like "File name", "Content"... But it doesn't works. I'm using KDE Neon Unstable edition in wayland session, with BTRFS file system installed. STEPS TO REPRODUCE 1. Change your indexing settings to the system be able find hidden files. Press ctrl + H (or alt + .) in Dolphin as well. 2. Search for some hidden file (the bug happens usually searching for a file/folder located inside .config, .dbus, .kde .cache... directories) 3. After following the steps, i think you probably will not be able find a several files OBSERVED RESULT Dolphin don't have success to find many files, may you can find a small set of them, but the results section will miss a lot. EXPECTED RESULT Show every possible file with the name i put in the search box, including files located inside hidden folders. SOFTWARE/OS VERSIONS Linux/KDE Plasma Linux: Kernel 5.4.0-52-generic KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 428105] Can't find hidden files even when hidden files are set to be indexed
https://bugs.kde.org/show_bug.cgi?id=428105 --- Comment #5 from Victor --- Edit: I've just installed KDE Neon User edition and the bug happens here as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 428105] Can't find hidden files even when hidden files are set to be indexed
https://bugs.kde.org/show_bug.cgi?id=428105 Victor changed: What|Removed |Added CC||svictorh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 435655] New: latte-dock crashes on startup
https://bugs.kde.org/show_bug.cgi?id=435655 Bug ID: 435655 Summary: latte-dock crashes on startup Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: victorb...@gmail.com Target Milestone: --- Application: latte-dock (0.9.86) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.11.13-arch1-1 x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Starting it - Unusual behavior I noticed: Updated the system yesterday (latte-dock was not part of the updated packages). The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Aborted [KCrash Handler] #4 0x7f6fc61e0ef5 in raise () at /usr/lib/libc.so.6 #5 0x7f6fc61ca862 in abort () at /usr/lib/libc.so.6 #6 0x7f6fc654e86a in __gnu_cxx::__verbose_terminate_handler() () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #7 0x7f6fc655ad3a in __cxxabiv1::__terminate(void (*)()) (handler=) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #8 0x7f6fc655ada7 in std::terminate() () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #9 0x7f6fc655b04e in __cxxabiv1::__cxa_throw(void*, std::type_info*, void (*)(void*)) (obj=, tinfo=0x7f6f9f1ba2b8 , dest=0x7f6f9f1a2120 ) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95 #10 0x7f6f9f1913f5 in () at /usr/lib/libc++utilities.so.5 #11 0x7f6f9f1e4e9c in Data::SyncthingConnection::readStatus() () at /usr/lib/libsyncthingconnector.so.0.11.12 #12 0x7f6fc69829d6 in () at /usr/lib/libQt5Core.so.5 #13 0x7f6fc5b79dd5 in () at /usr/lib/libQt5Network.so.5 #14 0x7f6fc6978132 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f6fc7693762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7f6fc694b62a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7f6fc694e123 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #18 0x7f6fc69a4b64 in () at /usr/lib/libQt5Core.so.5 #19 0x7f6fc4de202c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #20 0x7f6fc4e35b59 in () at /usr/lib/libglib-2.0.so.0 #21 0x7f6fc4ddf781 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #22 0x7f6fc69a41a1 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #23 0x7f6fc6949f8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #24 0x7f6fc6952444 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #25 0x5653ca99573b in () #26 0x7f6fc61cbb25 in __libc_start_main () at /usr/lib/libc.so.6 #27 0x5653ca99603e in _start () [Inferior 1 (process 241011) detached] Possible duplicates by query: bug 434236, bug 432084, bug 431773, bug 427384, bug 425891. Reported using DrKonqi This report was filed against 'kde' because the product 'latte-dock' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 435655] latte-dock crashes on startup
https://bugs.kde.org/show_bug.cgi?id=435655 Victor changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from Victor --- It looks like this was caused by an older version of 'syncthingtray'. I was able to track down the crash point with 'ddd'. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 416118] Gwenview freezes or crashes when loading image.
https://bugs.kde.org/show_bug.cgi?id=416118 Victor changed: What|Removed |Added CC||victorb...@gmail.com --- Comment #8 from Victor --- Created attachment 130869 --> https://bugs.kde.org/attachment.cgi?id=130869&action=edit strace showing recent files issue Anything under '/home/victor/Export' is an NFS mount that is not currently available. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 416118] Gwenview freezes or crashes when loading image.
https://bugs.kde.org/show_bug.cgi?id=416118
Victor changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment #9 from Victor ---
I have had the same issue on my laptop (Desktop works ok) for quite a while.
I'm running Arch with KDE on both computers.
I had tried re-installing Gwenview, removing the config file and even disabling
KDE connect (found a post where someone had issues online). Nothing worked.
After running 'strace' it showed that it was trying to load data from
'${HOME}/.local/share/gwenview/recentfolders', which pointed to an NFS mount
that is not currently active. I deleted the folder and now Gwenview works as
expected.
I would assume this to be a bug. Not being able to open recent files should not
halt the main thread.
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 427618] Akonadi server does not start and kontact suite is unusable
https://bugs.kde.org/show_bug.cgi?id=427618 --- Comment #6 from Victor --- (In reply to Christoph Feck from comment #5) > Victor, can you confirm this issue is fixed with release 20.08.2 (KDEPIM > version 5.15.2)? Just made the update and it works just fine, thanks a lot for all the work you're making. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476891] New: The power manager does not work
https://bugs.kde.org/show_bug.cgi?id=476891 Bug ID: 476891 Summary: The power manager does not work Classification: Applications Product: systemsettings Version: 5.27.9 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: foxychill...@gmail.com CC: k...@privat.broulik.de, natalie_clar...@yahoo.de 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. 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 The power manager does not work. The service is always inactive by default. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473818] New: Discover Update Center
https://bugs.kde.org/show_bug.cgi?id=473818 Bug ID: 473818 Summary: Discover Update Center Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: wolf...@yandex.ru CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-11-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: The Discover Update Center crashes constantly The crash can be reproduced every time. -- Backtrace: Application: ЦенÑÑ Ð¿ÑогÑамм Discover (plasma-discover), signal: Segmentation fault PID: 3823 (plasma-discover) UID: 1000 (spike) GID: 1000 (spike) Signal: 11 (SEGV) Timestamp: Sun 2023-08-27 21:43:57 +04 (2min 17s ago) Command Line: /usr/bin/plasma-discover Executable: /usr/bin/plasma-discover Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-\x2fusr\x2fbin\x2fplasma\x2ddiscover-bcab5aa2730948d88d1d7bf4a3f51179.scope Unit: user@1000.service User Unit: app-\x2fusr\x2fbin\x2fplasma\x2ddiscover-bcab5aa2730948d88d1d7bf4a3f51179.scope Slice: user-1000.slice Owner UID: 1000 (spike) Boot ID: 303a12f422674969857c9aee9d302813 Machine ID: bb34af89c6784ee98d67e8c7fcd19bf8 Hostname: Spike Storage: /var/lib/systemd/coredump/core.plasma-discover.1000.303a12f422674969857c9aee9d302813.3823.169315823700.zst (present) Size on Disk: 41.6M Message: Process 3823 (plasma-discover) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64 Stack trace of thread 3823: #0 0x7efe180a9d3c n/a (libc.so.6 + 0x8ad3c) #1 0x7efe1805af32 raise (libc.so.6 + 0x3bf32) #2 0x7efe1a4f283d _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x583d) #3 0x7efe1805afd0 n/a (libc.so.6 + 0x3bfd0) #4 0x7efe180c1bbd memcpy (libc.so.6 + 0xa2bbd) #5 0x7efe1a737244 n/a (libDiscoverCommon.so + 0x3a244) #6 0x7efe1a73604f _ZN8Category14sortCategoriesER7QVectorIPS_E (libDiscoverCommon.so + 0x3904f) #7 0x7efe1a7361c1 _ZN8Category14sortCategoriesER7QVectorIPS_E (libDiscoverCommon.so + 0x391c1) #8 0x7efe1a7361c1 _ZN8Category14sortCategoriesER7QVectorIPS_E (libDiscoverCommon.so + 0x391c1) #9 0x7efe1a7390f9 _ZN16CategoriesReader18loadCategoriesFileEP24AbstractResourcesBackend (libDiscoverCommon.so + 0x3c0f9) #10 0x7efe1a7378a2 _ZN13CategoryModel18populateCategoriesEv (libDiscoverCommon.so + 0x3a8a2) #11 0x7efe184e8f4f n/a (libQt5Core.so.5 + 0x2e8f4f) #12 0x7efe184ecd6a _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2ecd6a) #13 0x7efe184dd50d _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd50d) #14 0x7efe19f62fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #15 0x7efe184b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #16 0x7efe18508c31 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x308c31) #17 0x7efe185094fc n/a (libQt5Core.so.5 + 0x3094fc) #18 0x7efe16dd47a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #19 0x7efe16dd4a38 n/a (libglib-2.0.so.0 + 0x54a38) #20 0x7efe16dd4acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #21 0x7efe18509836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #22 0x7efe184b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #23 0x7efe184b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #24 0x55dc4b73e2a7 n/a (plasma-discover + 0x182a7) #25 0x7efe180461ca n/a (libc.so.6 + 0x271ca) #26 0x7efe18046285 __libc_start_main (libc.so.6 + 0x27285) #27 0x55dc4b73e811 n/a (plasma-discover + 0x18811) Stack trace of thread 3830: #0 0x7efe1811b03f __poll (libc.so.6 + 0xfc03f) #1 0x7efe16dd49ae n/a (libglib-2.0.
[Discover] [Bug 473818] Discover Update Center
https://bugs.kde.org/show_bug.cgi?id=473818 --- Comment #2 from Victor --- 29.08.2023, 00:20, "Nate Graham" : https://bugs.kde.org/show_bug.cgi?id=473818 Nate Graham < n...@kde.org[1]> changed: What |Removed |Added CC| | n...@kde.org[1] Resolution|--- |BACKTRACE Status|REPORTED |NEEDSINFO --- Comment #1 from Nate Graham < n...@kde.org[1]> --- Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following line that we need to figure out exactly what's going wrong: #5 0x7efe1a737244 in ?? () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so Could you please install debug symbols for Discover, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for details about how to do this. Thanks again! -- You are receiving this mail because: You reported the bug. Good day. I beg your pardon, it's hard for me to figure out Linux yet, I'm new to it. As I understand it, you need these data:Application: Центр программ Discover (plasma-discover), signal: Segmentation fault [KCrash Handler]#4 0x7fca7f4c2857 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5#5 0x7fca7f3a1659 in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5#6 0x7fca1e239866 in ?? ()#7 0x in ?? ()[Inferior 1 (process 5144) detached] 1. mailto:n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 448554] New: Authentication dialog does not play sound effect set in "Notifications / Events"
https://bugs.kde.org/show_bug.cgi?id=448554 Bug ID: 448554 Summary: Authentication dialog does not play sound effect set in "Notifications / Events" Product: policykit-kde-agent-1 Version: 5.23.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: d...@kde.org Reporter: victorstanci...@gmail.com CC: jgrul...@redhat.com, jrez...@redhat.com Target Milestone: --- Created attachment 145512 --> https://bugs.kde.org/attachment.cgi?id=145512&action=edit Settings window containing the mentioned event options. SUMMARY Any "Authentication Required" popup dialog that appears when a program needs administrative privileges does not play the audio set in "System Settings → Notifications → Applications → Authentication System → Configure Events... → Play a sound". STEPS TO REPRODUCE 1. Set any audio file as the sound effect for PolicyKit (follow the path of menus listed in the first paragraph). 2. Trigger an "Authentication Required dialog. For example, starting up the KDE Partition Manager or modifying packages. OBSERVED RESULT The popup appears as usual, however the event sound effect previously cannot be heard. EXPECTED RESULT The sound effect playing upon the dialog popping up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 21.2.1 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Note that events for other programs, such as network connections, volume up/down, screenshots, etc. do follow their settings. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 423746] New: Can't open files in kdiff3
https://bugs.kde.org/show_bug.cgi?id=423746 Bug ID: 423746 Summary: Can't open files in kdiff3 Product: kdiff3 Version: 1.8.x Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: vstadniche...@gmail.com Target Milestone: --- Created attachment 129818 --> https://bugs.kde.org/attachment.cgi?id=129818&action=edit screenshot SUMMARY If I launch the app and want to open files to compare - I can't open files, the app doesn't show me .html files in directories. It shows directories as empty. If I select a file in a directory and use Open with kdiff3 - it opens one file. I can't open the other file - the app shows the directory as empty. STEPS TO REPRODUCE 1. Select an (html) file - Open with - select kdiff3 2. Press File button to select the other (html) file in the dir 3. the dir looks empty - while if I look at it in file explorer, it's full of html files. In the screenshot the 2nd file is invisible. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Version 1.8.1 (64 bit) Windows: macOS: Linux/KDE Plasma: Linux Mint Mate 20-64 (Linux (x86_64) release 5.4.0-39-generic) Qt 5.12.8 (built against 5.12.8) KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 437248] New: Non-latin characters (cyrillic, spanish) not shown on text notes
https://bugs.kde.org/show_bug.cgi?id=437248 Bug ID: 437248 Summary: Non-latin characters (cyrillic, spanish) not shown on text notes Product: okular Version: 21.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: vitr...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Make new typewriter or inline note 2. Type any text containing non-latin character (for example ñ, á, é, ы) OBSERVED RESULT Only latin charracters appear in the note. EXPECTED RESULT All characters should apper. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.3-zen1-1-zen OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION It was working before as expected. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 437755] New: (Feature Request) Changing colors configuration and Dark icons
https://bugs.kde.org/show_bug.cgi?id=437755 Bug ID: 437755 Summary: (Feature Request) Changing colors configuration and Dark icons Product: okular Version: 1.9.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: New backend wishes Assignee: okular-de...@kde.org Reporter: murilo.sc...@gmail.com Target Milestone: --- Using Okular was a game changer for me, as I have the possibility to use the interface of Okular in dark themed mode (thanks also to using Linux, one of the reasons I dumped Windows) and also the possibility of easily changing document colors. This makes a whole lot difference for someone who stays all day, 10+ hours, in front of a screen reading PDFs. At night, I don't have headaches anymore. I started doing this by inverting colors, I don't know the reason, but it was not entirely confortable, so I tried changing dark and light colors of the PDFs. I change Light colors to Dark Grey, and dark colors from the pdf as very light yellow and haven't ever tried something else. This eliminates any eyestrain. But I have one problem: I'm currently doing a PhD in a STEM related field, and sometimes it is necessary to see colors in figures. The solution available right now is to use a hotkey or a button on tool's bar that disables color changes to default (white background and black print). It would be significantly better if one could, by a button on tool's bar, to swap from changing dark and light colors to invert colors, avoiding a big contrast of dark and bright colors available right now. This could be more easily implemented by adding a hierarchy to colors, setting it up on Configurations the first color option, then a secundary color option, so that when the "change colors" button on tool's bar it changes to the secondary color option. Also, It would be more aesthetically pleasing if dark icon had better colors (they are barely visible right now) when in the OS's dark mode (panel on dark colors). Thanks in advance. Victor. 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.
[okular] [Bug 437755] (Feature Request) Changing colors configuration and Dark icons
https://bugs.kde.org/show_bug.cgi?id=437755 --- Comment #4 from Victor --- > Which icon? The Okular application icon? Anyway, that is a different issue, > the black icon is from Breeze Icons and not from Okular. I will create another bug report later! > > Can you add feedback to the below merge request? I made a review there. I couldn't understand the technical discussions, but from a viewpoint of a regular user I hope what I said helps. Thanks guys! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490658] New: Widgets on the right side of the panel have their editing options pop-up overlaped with the "panel settings" box, making it impossible to use the functionality.
https://bugs.kde.org/show_bug.cgi?id=490658 Bug ID: 490658 Summary: Widgets on the right side of the panel have their editing options pop-up overlaped with the "panel settings" box, making it impossible to use the functionality. Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Edit Mode Assignee: plasma-b...@kde.org Reporter: victorhugod...@hotmail.com Target Milestone: 1.0 Created attachment 171896 --> https://bugs.kde.org/attachment.cgi?id=171896&action=edit Picture showing the widget options getting overlapped by the "Panel settings" box. SUMMARY When editing the panel on the new Plasma 6 "Edit mode" interface, if you hover your cursor over the widgets placed on the very right side of the panel, the editing options (such as remove widget, show alternatives, ...) appear behind the "Panel settings" box, making it practically impossible for you to see and use the options for that widget. STEPS TO REPRODUCE 1. Right click the panel, "show panel settings" 2. Hover your cursor over the widgets on the right side of the panel 3. You will see that their settings box is broken as they appear behind the "Panel Settings" card OBSERVED RESULT Widgets configuration boxes overlap with the main "Panel settings" card. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Kinoite (available in About System) KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490658] Widgets on the right side of the panel have their editing options overlapped by the "panel settings" box, making the feature unusable.
https://bugs.kde.org/show_bug.cgi?id=490658 Victor changed: What|Removed |Added Summary|Widgets on the right side |Widgets on the right side |of the panel have their |of the panel have their |editing options pop-up |editing options overlapped |overlaped with the "panel |by the "panel settings" |settings" box, making it|box, making the feature |impossible to use the |unusable. |functionality. | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490658] Widgets on the right side of the panel have their editing options overlapped by the "panel settings" box, making the feature unusable.
https://bugs.kde.org/show_bug.cgi?id=490658 Victor changed: What|Removed |Added Platform|Other |Fedora RPMs Version|master |6.1.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490658] Widgets on the right side of the panel have their editing options overlapped by the "panel settings" box, making the feature unusable.
https://bugs.kde.org/show_bug.cgi?id=490658 --- Comment #1 from Victor --- I would say this belongs under the "5-minute-bugs" list, as it literally affects a very user-facing, core feature and can be reproduced with only two clicks. I first noticed this a long time ago, ever since the new plasma 6 edit mode got redesigned, but could only report it now. So I don't know whether this is a duplicate as the bug is very easy to reproduce and been around for a while now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490658] Widgets on the right side of the panel have their editing options overlapped by the "panel settings" box, making the feature unusable.
https://bugs.kde.org/show_bug.cgi?id=490658 Victor changed: What|Removed |Added CC||victorhugod...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 462671] New: Wrong display when using LateX labels roated on y axis .
https://bugs.kde.org/show_bug.cgi?id=462671 Bug ID: 462671 Summary: Wrong display when using LateX labels roated on y axis . Classification: Applications Product: LabPlot2 Version: 2.9.0 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: victor.daco...@ipcms.unistra.fr Target Milestone: --- Created attachment 154329 --> https://bugs.kde.org/attachment.cgi?id=154329&action=edit example labplot2.9 of bad latex command display SUMMARY *** Whatever the input 'texte' (title, axis labels ...) on plot and if select as 'LateX', the resulting display is bad. Something is wrong with the police. Default is very clear if you try for instance to put a rotated label on y axis with LateX command. Letters are displayed elongated... *** STEPS TO REPRODUCE 1. select 'plot', select y axis, input a text, for instance \alpha(\omega), choose LateX (texte, Latex, Markdown): nothing is displayed... 2. Change the police to 'arial' size 12, then the display is correct, but if you change the 'rotation' parameter, at 90° for instance, display of letters are very distorded and pixelerized. see attached screen shot 3. OBSERVED RESULT This is observed whatever the input 'text' when select LateX editing commands EXPECTED RESULT It should display a nicely normal or greek/math texte SOFTWARE/OS VERSIONS Windows: ADDITIONAL INFORMATION I usually used "veusz", witch is similar to laplot for display plots. (Latex commands work fine on veusz). Sincerly Victor -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 462671] Wrong display when using LateX labels roated on y axis .
https://bugs.kde.org/show_bug.cgi?id=462671 --- Comment #2 from victor --- (In reply to Alexander Semke from comment #1) > (In reply to victor from comment #0) > > Created attachment 154329 [details] > > example labplot2.9 of bad latex command display > > > > SUMMARY > > *** > > Whatever the input 'texte' (title, axis labels ...) on plot and if select as > > 'LateX', the resulting display is bad. Something is wrong with the police. > > Default is very clear if you try for instance to put a rotated label on y > > axis with LateX command. Letters are displayed elongated... > > *** > This was fixed recently for the upcoming release 2.10. If it's feasible for > you, can you please try out our nightly builds and check whether it works > for you now, too? Thank you for your answer, I tried a nightly version...and it seems to work correctly... Hope new version will coming soon. (As a scientist, LateX integration of text or symbols is very important) Congratulations for your work. sincerly, victor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418217] background setting is not retained
https://bugs.kde.org/show_bug.cgi?id=418217 Victor changed: What|Removed |Added CC||virusqui...@gmail.com --- Comment #17 from Victor --- Same problem here -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421230] New: problem with theme rounded
https://bugs.kde.org/show_bug.cgi?id=421230 Bug ID: 421230 Summary: problem with theme rounded Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: vcal...@gmail.com Target Milestone: --- Created attachment 128294 --> https://bugs.kde.org/attachment.cgi?id=128294&action=edit latte-dock with rounded theme SUMMARY problem with the rounded theme. it doesn't draw well. the url of the theme is https://www.pling.com/p/1352754 author x-varlesh-x I attach the screenshot of the problem. SOFTWARE/OS VERSIONS Linux : opensuse 15.2 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69 Qt Version: 5.12.7 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421230] problem with theme rounded
https://bugs.kde.org/show_bug.cgi?id=421230 --- Comment #2 from Victor --- you are correct psifidotos the problem is in the theme. x-varlesh-x added HiDPI support in the latest theme update. Downloading the version of the theme from February 2 solved the problem. thanks for everything -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails
https://bugs.kde.org/show_bug.cgi?id=415089 Victor changed: What|Removed |Added CC||virusqui...@gmail.com --- Comment #28 from Victor --- The same problem in KDE Neon 5.18 KDE 5.70.0 / Plasma 5.18.5 kio-gdrive 1.3.0-0xneon+18.04+bionic+build14 kaccounts-providers 4:20.04.1-0xneon+18.04+bionic+build39 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391347] New: Gmail - do not save password
https://bugs.kde.org/show_bug.cgi?id=391347 Bug ID: 391347 Summary: Gmail - do not save password Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: victorh2...@yahoo.com.br Target Milestone: --- When accessing Gmail: does not offer the option to save password account -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391347] Gmail - do not save password
https://bugs.kde.org/show_bug.cgi?id=391347 Victor changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 393685] New: Feature Request: Please add option to stop activity when empty
https://bugs.kde.org/show_bug.cgi?id=393685 Bug ID: 393685 Summary: Feature Request: Please add option to stop activity when empty Product: kactivitymanagerd Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: victorb...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Note: This is feature request, but I could not find a whishlist for 'kactivitymanagerd'. It would be great to be to able to automatically stop an activity when it's empty, or automatically start an activity when you open an application that has been assigned to that activity. I know this can be achieved via shell scripts (which is what I'm using right now), but it would be great to have this as an option for the activities settings. Note 2: You guys are doing a superb job!! -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 393685] Feature Request: Please add option to stop activity when empty
https://bugs.kde.org/show_bug.cgi?id=393685 Victor changed: What|Removed |Added Platform|Other |Archlinux Packages Version|unspecified |5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 393685] Feature Request: Please add option to stop activity when empty
https://bugs.kde.org/show_bug.cgi?id=393685 --- Comment #2 from Victor --- (In reply to David Edmundson from comment #1) > By empty you mean no application specific to that activity running? That's correct. If no windowed app is running on that specific activity, then it gets stopped. And if you open an application that is assigned to an activity that is currently not running, then the activity gets started automatically. I put this quick bash script to do just that - https://pastebin.com/1Jwn8Fqs -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 394804] New: kmix memory leak suspected
https://bugs.kde.org/show_bug.cgi?id=394804 Bug ID: 394804 Summary: kmix memory leak suspected Product: kmix Version: 4.3 Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Backend: Pulseaudio Assignee: co...@mageia.org Reporter: v.v.dy...@mail.ru CC: es...@kde.org Target Milestone: --- Sometimes ALSA sink does not work properly in PulseAudio. For example several emulators like Wine or DOSBox and some other programs using ALSA may cause errors similar to "ALSA lib pcm.c:8323:(snd_pcm_recover) underrun occurred" and stuttering sound. It was tolerable until recent update of RHEL to 7.5. Since the update every occurrence of such PulseAudio error increases memory used by kmix up to 50 GB (I killed process after that). Obviously it could be very many underrun occurences depending of buffer size so it looks like kmix should normally manage with buffer underrun occurences without memory leak. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 394804] kmix memory leak suspected
https://bugs.kde.org/show_bug.cgi?id=394804 Victor changed: What|Removed |Added Flags||corner_case+ CC||v.v.dy...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 394804] kmix memory leak suspected
https://bugs.kde.org/show_bug.cgi?id=394804 Victor changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 394804] kmix memory leak suspected
https://bugs.kde.org/show_bug.cgi?id=394804 --- Comment #2 from Victor --- Actually this bug is extremely annoying because i've found it arose while skype-calls. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385816] New: KDevelop has problems with multiple projects with same structure
https://bugs.kde.org/show_bug.cgi?id=385816 Bug ID: 385816 Summary: KDevelop has problems with multiple projects with same structure Product: kdevelop Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: file tree Assignee: kdevelop-bugs-n...@kde.org Reporter: vicfern...@gmail.com Target Milestone: --- I have the same project on two different folders, each of them in a different git branch. This way I can refactor one branch in the other branch. The issue is, KDevelop fails to understand files from different folders, but same name, are different, so, when telling KDevelop to 'Jump to', even on a method in the same file, it opens the same file, but from the other project, so I end up modifying both branches, while the idea was to have one of them untouched. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385816] KDevelop has problems with multiple projects with same structure
https://bugs.kde.org/show_bug.cgi?id=385816 --- Comment #1 from Victor --- Forgot to add that I have both projects open in the same session of KDevelop -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385816] KDevelop has problems with multiple projects with same structure
https://bugs.kde.org/show_bug.cgi?id=385816 --- Comment #3 from Victor --- It seems like the solution to me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Victor changed: What|Removed |Added CC||alenkov.vic...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410295] Underlined text highlighting not getting saved.
https://bugs.kde.org/show_bug.cgi?id=410295 Victor changed: What|Removed |Added CC||d...@r4in.tk --- Comment #2 from Victor --- I have the same problem in Kate 23.08.5. Theme Editor on pressing Apply resets .theme-file without applying changes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410295] Underlined text highlighting not getting saved.
https://bugs.kde.org/show_bug.cgi?id=410295 --- Comment #4 from Victor --- (In reply to Igor Kushnir from comment #3) > (In reply to Victor from comment #2) > > I have the same problem in Kate 23.08.5. > > Theme Editor on pressing Apply resets .theme-file without applying changes. > Cannot reproduce in Kate 24.12.3 or in KDevelop 6.3.250770 after copying a > theme as a hint on the Highlighting Text Styles tab suggests. Once changed, > the Underlined checkbox remains checked and the configured code is > underlined accordingly. Though checking the Underlined checkbox is not > always possible in the first place (need to change some other option on the > same line first for some reason). I have rechecked and for Kate 23.08.5 the problem still exist. Any changes in Settings -> Colors Themes -> Highlighting Text Styles are inapplicable. I can save video if you want. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500843] "Power Management settings could not be loaded" after recent update (6.3.1.1)
https://bugs.kde.org/show_bug.cgi?id=500843 --- Comment #7 from Victor --- (In reply to Victor from comment #6) > I did some tests and it seems that this is related to a modified EDID so > that I can force the use of pixel format RGB. > > I undid the changes and so far I haven't had the error again. Nah, just happened again :( i'll wait for JJ and then open a new bug report if needed Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500843] "Power Management settings could not be loaded" after recent update (6.3.1.1)
https://bugs.kde.org/show_bug.cgi?id=500843 --- Comment #6 from Victor --- I did some tests and it seems that this is related to a modified EDID so that I can force the use of pixel format RGB. I undid the changes and so far I haven't had the error again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500843] "Power Management settings could not be loaded" after recent update (6.3.1.1)
https://bugs.kde.org/show_bug.cgi?id=500843 --- Comment #4 from Victor --- (In reply to Nate Graham from comment #3) > Let's let JJ respond before debugging further to make sure that both of you > are hitting the same issue (Viktor's issue is an assert in DDC code). Yes, sorry, it's the first time I've sent a report and I found it a bit confusing, do you think I should do a separate report? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500843] "Power Management settings could not be loaded" after recent update (6.3.1.1)
https://bugs.kde.org/show_bug.cgi?id=500843 Victor changed: What|Removed |Added CC||victorsouzal...@gmail.com Assignee|plasma-b...@kde.org |victorsouzal...@gmail.com --- Comment #2 from Victor --- Created attachment 178975 --> https://bugs.kde.org/attachment.cgi?id=178975&action=edit powerdevil systemd status I'm having the same problem with it, but in my case it's on the Desktop, whenever my screen comes back from sleep, Powerdevil stops working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500843] "Power Management settings could not be loaded" after recent update (6.3.1.1)
https://bugs.kde.org/show_bug.cgi?id=500843 Victor changed: What|Removed |Added Assignee|victorsouzal...@gmail.com |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 500843] "Power Management settings could not be loaded" after recent update (6.3.1.1)
https://bugs.kde.org/show_bug.cgi?id=500843 --- Comment #11 from Victor --- Yea it looks like we share the same error "assertion failed" -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 504662] crash when using the "Create Data Spreadsheet" feature
https://bugs.kde.org/show_bug.cgi?id=504662 --- Comment #3 from victor --- Added remark: I haven this problem on version labplot2.11 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 504662] crash when using the "Create Data Spreadsheet" feature
https://bugs.kde.org/show_bug.cgi?id=504662 victor changed: What|Removed |Added CC||victor.dacosta@ipcms.unistr ||a.fr --- Comment #2 from victor --- Hi, I have the same problem: if I process a curve (differenciate, integrate, ), a new curve is created but when tried to to generate the corresponding data spreadsheet, the program crashes. Bests, Victor -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 466949] LaTeX font rendering looks always blurry
https://bugs.kde.org/show_bug.cgi?id=466949 victor changed: What|Removed |Added CC||victor.dacosta@ipcms.unistr ||a.fr --- Comment #3 from victor --- Hi, I still have the same problem when including any latex text on the graph. So, whatever is my choice of the latex engine (I prefer pdflatex) and the labplot version (2.10, 2.11, 2.12). Bests, Victor -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 372939] New: Rerouting can become annoying
https://bugs.kde.org/show_bug.cgi?id=372939 Bug ID: 372939 Summary: Rerouting can become annoying Product: marble Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: victor.tr...@live.com Target Milestone: --- When you deviate from the route, Marble says "deviated from the route" and reroutes you. However, this does not take into account the direction that the user is currently moving, thus if it decides that the best route from there is to go backwards, it will reroute, and then immediately say "deviated from the route" again, until either the user turns around, or the routing system finds a better route. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 372940] New: Night mode
https://bugs.kde.org/show_bug.cgi?id=372940 Bug ID: 372940 Summary: Night mode Product: marble Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: victor.tr...@live.com Target Milestone: --- A night mode would be good (at least during navigation) so that the phone does not shine into the vehicle. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 372941] New: Map Rotation
https://bugs.kde.org/show_bug.cgi?id=372941 Bug ID: 372941 Summary: Map Rotation Product: marble Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: victor.tr...@live.com Target Milestone: --- Rotation of the map would be really good, especially during navigation, because if the vehicle is moving south, the directions can be very confusing. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 372939] Rerouting can become annoying
https://bugs.kde.org/show_bug.cgi?id=372939 --- Comment #2 from Victor Tran --- Ok then, is there a way to at least add an extra instruction to "in 300m, perform a U-turn?" :) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 372992] New: Roundabouts don't have turn-by-turn voice commands
https://bugs.kde.org/show_bug.cgi?id=372992 Bug ID: 372992 Summary: Roundabouts don't have turn-by-turn voice commands Product: marble Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: victor.tr...@live.com Target Milestone: --- In Australia (left hand side driving - we go clockwise around a roundabout) roundabouts have no picture and have no voice command. When you get to the roundabout, to see where you have to go you need to look at the map and decide yourself rather than Marble telling you. That could be slightly distracting and dangerous. It should at least say something like "in 300m, at the roundabout, take the third exit" and have a corresponding picture. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 372993] New: List of instructions
https://bugs.kde.org/show_bug.cgi?id=372993 Bug ID: 372993 Summary: List of instructions Product: marble Version: 2.1 (KDE Applications 16.12) Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: victor.tr...@live.com Target Milestone: --- It would be good to have Marble show a route overview so we can see what turns we need to take next. P.S. I hope you don't mind me creating all these bug reports and feature requests... :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454517] Pager applet does not resize correctly after a screen is enabled
https://bugs.kde.org/show_bug.cgi?id=454517 Victor Ryzhykh changed: What|Removed |Added CC||victorr2...@yandex.ru --- Comment #5 from Victor Ryzhykh --- Created attachment 149458 --> https://bugs.kde.org/attachment.cgi?id=149458&action=edit Panel With this change, my view of the panel is broken, and I can no longer customize it. Every time I log in I get this view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454517] Pager applet does not resize correctly after a screen is enabled
https://bugs.kde.org/show_bug.cgi?id=454517 --- Comment #7 from Victor Ryzhykh --- Created attachment 149461 --> https://bugs.kde.org/attachment.cgi?id=149461&action=edit Rever view No, I'm talking about the other one. All the icons on the panel began to shuffle in random order. After each login to the session in different ways. And the order changes from right to left. Reverted that comment and the panel looks like normal again. This is how it looks now, as it was set up. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454517] Pager applet does not resize correctly after a screen is enabled
https://bugs.kde.org/show_bug.cgi?id=454517 --- Comment #8 from Victor Ryzhykh --- Created attachment 149464 --> https://bugs.kde.org/attachment.cgi?id=149464&action=edit layout.js file I use this default panel file in /usr/share/plasma/layout-templates/org.kde.plasma.desktop.defaultPanel/contents/layout.js -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454517] Pager applet does not resize correctly after a screen is enabled
https://bugs.kde.org/show_bug.cgi?id=454517 --- Comment #10 from Victor Ryzhykh --- (In reply to Fushan Wen from comment #9) > Created attachment 149465 [details] > test_fix1.tar.gz > > Can you test if the bug is fixed by the 3 files in the archive? Copy them to > /usr/share/plasma/plasmoids/org.kde.panel/contents/ui/ Yes, it works normally now. The panel looks exactly as intended. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455230] New: Feature Request: Hide Floating Gap when touching any window
https://bugs.kde.org/show_bug.cgi?id=455230 Bug ID: 455230 Summary: Feature Request: Hide Floating Gap when touching any window Product: lattedock Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: victorpavan...@gmail.com Target Milestone: --- SUMMARY As of now, there is only the option for it to hide the gap when a window is maximized. I often use windows "tiled" side-to-side, with latte set to "windows can go behind" option. It would be great if the floating dock could fit at the corner in this case. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464535] Charging limit is not saved
https://bugs.kde.org/show_bug.cgi?id=464535 Victor Ryzhykh changed: What|Removed |Added CC||victorr2...@yandex.ru --- Comment #13 from Victor Ryzhykh --- Created attachment 156238 --> https://bugs.kde.org/attachment.cgi?id=156238&action=edit There are no settings. This commit disables the battery limit setting. Operating System: ROSA Fresh Desktop 2021.1 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.5 Kernel Version: 6.1.11-generic-4rosa2021.1-x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 38.9 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus M16 GU603HE_GU603HE System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464535] Charging limit is not saved
https://bugs.kde.org/show_bug.cgi?id=464535
--- Comment #14 from Victor Ryzhykh ---
Created attachment 156239
--> https://bugs.kde.org/attachment.cgi?id=156239&action=edit
Removed this commit.
Removed this commit by building the package with the parameter
Patch1:
https://invent.kde.org/plasma/powerdevil/-/commit/b2e33beeed1a7ba60fb20a784c3209f97b887b8.patch
%prep
%setup -n %{oname}-%{version}
%patch1 -p1 -R
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 464535] Charging limit is not saved
https://bugs.kde.org/show_bug.cgi?id=464535 --- Comment #16 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #13) > Created attachment 156238 [details] > There are no settings. > > This commit disables the battery limit setting. > Settings are not available on this tab. but managed to enable the limit with package asusctl. Package asusctl works correctly in both cases. https://gitlab.com/asus-linux/asusctl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464535] Charging limit is not saved
https://bugs.kde.org/show_bug.cgi?id=464535 --- Comment #17 from Victor Ryzhykh --- (In reply to Fabian Vogt from comment #15) > What's the output of ls -l /sys/class/power_supply/*/*threshold*? > > I suspect the battery either has a start or stop threshold, but not both. victor@asus-rog ~ $ ls -l /sys/class/power_supply/*/*threshold -rw-r--r-- 1 root root 4096 фев 14 21:38 /sys/class/power_supply/BAT0/charge_control_end_threshold victor@asus-rog ~ $ su - Пароль: asus-rog ~ # ls -l /sys/class/power_supply/*/*threshold -rw-r--r-- 1 root root 4096 фев 14 21:38 /sys/class/power_supply/BAT0/charge_control_end_threshold asus-rog ~ # -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464535] Charging limit is not saved
https://bugs.kde.org/show_bug.cgi?id=464535 --- Comment #20 from Victor Ryzhykh --- (In reply to Fabian Vogt from comment #19) > Ok, so my suspicion was correct. Please try > https://invent.kde.org/plasma/powerdevil/-/merge_requests/135. /builddir/build/BUILD/powerdevil-5.27.0/daemon/chargethresholdhelper.cpp:67:16: error: expected identifier before '!' token -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464535] Charging limit is not saved
https://bugs.kde.org/show_bug.cgi?id=464535 --- Comment #22 from Victor Ryzhykh --- (In reply to Fabian Vogt from comment #21) > (In reply to Victor Ryzhykh from comment #20) > > (In reply to Fabian Vogt from comment #19) > > > Ok, so my suspicion was correct. Please try > > > https://invent.kde.org/plasma/powerdevil/-/merge_requests/135. > > > > /builddir/build/BUILD/powerdevil-5.27.0/daemon/chargethresholdhelper.cpp:67: > > 16: error: expected identifier before '!' token > > Fixed. So good, now it works. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464535] Charging limit is not saved
https://bugs.kde.org/show_bug.cgi?id=464535 --- Comment #23 from Victor Ryzhykh --- Created attachment 156245 --> https://bugs.kde.org/attachment.cgi?id=156245&action=edit So good, now it works. So good, now it works. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426937] kded5: Segmentation fault when I plug in controller with touchpad using xf86-input-libinput
https://bugs.kde.org/show_bug.cgi?id=426937 Victor Mataré changed: What|Removed |Added CC||vmatare+red...@cognesys.de -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 Victor Ryzhykh changed: What|Removed |Added CC||victorr2...@yandex.ru --- Comment #2 from Victor Ryzhykh --- Operating System: ROSA Fresh Desktop 2021.1 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.5 Kernel Version: 6.1.22-generic-3rosa2021.1-x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 15.6 ГиБ of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B250M-D3H Same problem. If the checkbox "After waking from sleep" is unchecked, then the download proceeds normally, if the checkbox "After waking from sleep" is checked, then after entering the password, instead of opening the session, an empty black window appears. The problem appeared after version 5.25.90. I collected updates from git for version 5.25.90 almost before the release. Ten days before the release of 5.26.0, on package built from snapshots from git, or from sources taken from https://origin.archive.neon.kde.org/unstable/pool/main/, there was no error. The system started from standby on nvidia drivers without problems. And after the release of 5.26.0, this problem appeared. To check, I rearranged versions 5.25.90 and 5.26.0 several times. On the first one there were no problems, on the second one appeared. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 --- Comment #5 from Victor Ryzhykh --- (In reply to Nate Graham from comment #4) > Sorry, I'm a bit confused. You said: > > > If the checkbox "After waking from sleep" is unchecked, then the download > > proceeds normally, > This answer is mine. I have no problem without a screen lock. After turning on the lock, this problem appears. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 --- Comment #6 from Victor Ryzhykh --- (In reply to Nate Graham from comment #4) > and also > > > Yes, the issue reproduce without Screen Locking. > > On resume I see only black screen. This was written by another user. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 --- Comment #8 from Victor Ryzhykh --- (In reply to Nate Graham from comment #7) > Viktor, your issue is different if it goes away when you disable the lock > screen. Can you submit a new bug report for it? Thanks I will try. Until I figure out how to do it right. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 --- Comment #9 from Victor Ryzhykh --- Created attachment 157904 --> https://bugs.kde.org/attachment.cgi?id=157904&action=edit log Booted up and went into standby mode. Came out and got a black screen. Rebooted and ran command « journalctl -b -01 > log.txt». Filtered the output since the transition to standby mode. The text is long. I will attach the file, and below I will add the text in the browser. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 --- Comment #10 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #9) > Created attachment 157904 [details] > The text is long. I will attach the file, and below I will add the text in > the browser. I can't put such a long text in the browser. I get an error that there are too many lines. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468228] New: Black screen after exiting screen lock on nvidia proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=468228 Bug ID: 468228 Summary: Black screen after exiting screen lock on nvidia proprietary drivers Classification: Plasma Product: kscreenlocker Version: 5.27.4 Platform: ROSA RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: victorr2...@yandex.ru Target Milestone: --- 1. It booted up and then went into standby mode. 2. Came out and got a black screen. Operating System: ROSA Fresh Desktop 2021.1 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.5 Kernel Version: 6.1.22-generic-3rosa2021.1-x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 15.6 ГиБ of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B250M-D3H Same problem. If the checkbox "After waking from sleep" is unchecked, then the download proceeds normally, if the checkbox "After waking from sleep" is checked, then after entering the password, instead of opening the session, an empty black window appears. The problem appeared after version 5.25.90. I collected updates from git for version 5.25.90 almost before the release. Ten days before the release of 5.26.0, on package built from snapshots from git, or from sources taken from https://origin.archive.neon.kde.org/unstable/pool/main/, there was no error. The system started from standby on nvidia drivers without problems. And after the release of 5.26.0, this problem appeared. To check, I rearranged versions 5.25.90 and 5.26.0 several times. On the first one there were no problems, on the second one appeared. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468228] Black screen after exiting screen lock on nvidia proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=468228 --- Comment #1 from Victor Ryzhykh --- Created attachment 157915 --> https://bugs.kde.org/attachment.cgi?id=157915&action=edit log Booted up and went into standby mode. Came out and got a black screen. Rebooted and ran command « journalctl -b -01 > log.txt». Filtered the output since the transition to standby mode. The text is long. I will attach the file, and below I will add the text in the browser. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468228] Black screen after exiting screen lock on nvidia proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=468228 --- Comment #2 from Victor Ryzhykh --- (In reply to Victor Ryzhykh from comment #1) > Created attachment 157915 [details] > log > I can't put such a long text in the browser. I get an error that there are too many lines. So I attached the log file. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 --- Comment #12 from Victor Ryzhykh --- (In reply to Nate Graham from comment #11) > In another bug report please, Victor. Ok. https://bugs.kde.org/show_bug.cgi?id=468228 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468228] Black screen after exiting screen lock on nvidia proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=468228 --- Comment #3 from Victor Ryzhykh --- I have no problem without a screen lock. After turning on the lock, this problem appears. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468228] Black screen after exiting screen lock on nvidia proprietary drivers
https://bugs.kde.org/show_bug.cgi?id=468228 --- Comment #5 from Victor Ryzhykh --- Thank you. Indeed, the problem was not in the plasma. The qt5-qtvirtualkeyboard package had a very old patch with no description. This patch is already three years old. I don't even remember why. I removed it from the package, and after rebuilding the qt5-qtvirtualkeyboard package, it became normal to exit the screen lock. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468645] New: Meta+T tileseditorr causes system unresponsiveness for a few seconds
https://bugs.kde.org/show_bug.cgi?id=468645 Bug ID: 468645 Summary: Meta+T tileseditorr causes system unresponsiveness for a few seconds Classification: Plasma Product: kwin Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: vityas_offic...@yahoo.co.jp CC: notm...@gmail.com Target Milestone: --- SUMMARY *** When using Meta+T keybind to trigger tileseditor interface system becomes completely unresponsive for a few seconds (kwind_wayland using 100% cpu). There is error in system log during this lag: file:///usr/share/kwin/effects/tileseditor/qml/main.qml:152:13: QML SpinBox: Binding loop detected for property "implicitWidth" *** SOFTWARE/OS VERSIONS Fedora Kinoite, linux 6.2.9-300.fc38.x86_64, plasma 5.27.4, frameworks 5.104, qt 5.15.8 Wayland, 200% display scale -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468645] Meta+T tileseditor causes system unresponsiveness for a few seconds
https://bugs.kde.org/show_bug.cgi?id=468645 Victor Prudniy changed: What|Removed |Added Summary|Meta+T tileseditorr causes |Meta+T tileseditor causes |system unresponsiveness for |system unresponsiveness for |a few seconds |a few seconds -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 470889] New: KPhotoAlbum crashes when closing the Annotations window if previous Viewer window is already closed
https://bugs.kde.org/show_bug.cgi?id=470889 Bug ID: 470889 Summary: KPhotoAlbum crashes when closing the Annotations window if previous Viewer window is already closed Classification: Applications Product: kphotoalbum Version: GIT master Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: victor.ip.l...@gmail.com Target Milestone: --- Created attachment 159589 --> https://bugs.kde.org/attachment.cgi?id=159589&action=edit Screen video recording showing steps to reproduce crash SUMMARY KPhotoAlbum crashes when closing the Annotations window if the previous window was the Viewer window that is already closed. Viewer --> Annotations --> Close Viewer --> Close Annotations --> Crash STEPS TO REPRODUCE 1. Open KPhotoAlbum 2. Click on Show Thumbnails 3. Double Click on any photo to View 4. Viewer window opens 5. Right Click on the photo in Viewer window and select Annotate.. 6. Annotations window opens 7. Click the Close (X) button on the Titlebar of the Viewer window (note this is the previous Viewer window and not the new Annotations window that opens) 8. Click the Close (X) button on the Titlebar of the Annotations window 9. KPhotoAlbum crashes Screen video recording is attached OBSERVED RESULT Crash EXPECTED RESULT No crash; return back to main window. SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed 20230608; Kernel Version: 6.3.6-1-default (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION 1. Crash is reproducible in most cases. Occasionally it does not crash initially at step 9 but repeating 3-8 will result in a crash at step 9. 2. Crash occurs even in the demo database and is regardless of picture or video selected. 3. drkonqi fails to start as seen from command line output. Including gdb backtrace. Command line output: victor@localhost:~> kphotoalbum Map theme file does not exist: "" No plugins loaded. Please check if the plugins were installed in the correct path, or if any errors occurred while loading plugins. Map theme file does not exist: "" Falling back to default theme: "earth/srtm/srtm.dgml" Map theme file does not exist: "" Couldn't find a valid DGML map. QImage::scaled: Image is a null image QImage::scaled: Image is a null image malloc(): unaligned fastbin chunk detected 40 -- exe=/home/victor/.local/bin/kphotoalbum 13 -- platform=xcb 11 -- display=:0 20 -- appname=kphotoalbum 32 -- apppath=/home/victor/.local/bin 9 -- signal=6 9 -- pid=7418 32 -- appversion=v5.10.0-77-g471c4c2f 24 -- programname=KPhotoAlbum 31 -- bugaddress=sub...@bugs.kde.org KCrash: Application 'kphotoalbum' crashing... KCrash: Attempting to start /usr/libexec/drkonqi Alarm clock victor@localhost:~> GDB Backtrace for current thread: #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7fffec092b03 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x7fffec041226 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7fffec029897 in __GI_abort () at abort.c:79 #4 0x7fffec02a611 in __libc_message (fmt=fmt@entry=0x7fffec1b0532 "%s\n") at ../sysdeps/posix/libc_fatal.c:150 #5 0x7fffec09d417 in malloc_printerr (str=str@entry=0x7fffec1b3780 "malloc(): unaligned fastbin chunk detected") at malloc.c:5651 #6 0x7fffec0a0a2c in _int_malloc (av=av@entry=0x7fffd430, bytes=bytes@entry=16) at malloc.c:3839 #7 0x7fffec0a19bd in __GI___libc_malloc (bytes=bytes@entry=16) at malloc.c:3305 #8 0x7fffea0132ff in read_packet (c=0x837800) at /usr/src/debug/libxcb-1.15/src/xcb_in.c:314 #9 _xcb_in_read (c=c@entry=0x837800) at /usr/src/debug/libxcb-1.15/src/xcb_in.c:1042 #10 0x7fffea013a1e in _xcb_conn_wait (c=0x837800, vector=0x0, count=0x0, cond=) at /usr/src/debug/libxcb-1.15/src/xcb_conn.c:544 #11 0x7fffea01513c in _xcb_conn_wait (count=0x0, vector=0x0, cond=0x837840, c=0x837800) at /usr/src/debug/libxcb-1.15/src/xcb_conn.c:474 #12 xcb_wait_for_event (c=0x837800) at /usr/src/debug/libxcb-1.15/src/xcb_in.c:703 #13 0x7fffe0d191a0 in QXcbEventQueue::run (this=0x8228e0) at qxcbeventqueue.cpp:228 #14 0x7fffec703b7d in operator() (__closure=) at thread/qthread_unix.cpp:350 #15 (anonymous namespace)::terminate_on_exception > (t=...) at thread/qthread_unix.cpp:287 #16 QThreadPrivate::start (arg=0x8228e0) at thread/qthread_unix.cpp:310 #17 0x7fffec090c24 in start_thread (arg=) at pthread_create.c:444 #18 0x7fffec118510 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 470889] KPhotoAlbum crashes when closing the Annotations window if previous Viewer window is already closed
https://bugs.kde.org/show_bug.cgi?id=470889 --- Comment #1 from Victor Lobo --- Created attachment 159590 --> https://bugs.kde.org/attachment.cgi?id=159590&action=edit GDB Backtrace for all threads -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 470889] KPhotoAlbum crashes when closing the Annotations window if previous Viewer window is already closed
https://bugs.kde.org/show_bug.cgi?id=470889 Victor Lobo changed: What|Removed |Added CC||victor.ip.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 470889] KPhotoAlbum crashes when closing the Annotations window if previous Viewer window is already closed
https://bugs.kde.org/show_bug.cgi?id=470889 --- Comment #4 from Victor Lobo --- Wow, such a quick response. I tested, and the fix works correctly. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460103] New: Margins for headers in System Settings tabs differs for different components.
https://bugs.kde.org/show_bug.cgi?id=460103 Bug ID: 460103 Summary: Margins for headers in System Settings tabs differs for different components. Classification: Applications Product: systemsettings Version: 5.25.90 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vityas_offic...@yahoo.co.jp Target Milestone: --- Created attachment 152635 --> https://bugs.kde.org/attachment.cgi?id=152635&action=edit demo SUMMARY Margins for headers in System Settings tabs differs for different components. This causing text jump when switching tabs. STEPS TO REPRODUCE 1. Open System Settings 2. Switch different menu items Please see attachments for visual demo. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 Victor Prudniy changed: What|Removed |Added CC||vityas_offic...@yahoo.co.jp --- Comment #15 from Victor Prudniy --- I have 2 same model displays and this bug happens only when konsole placed on first primary screen. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460564] New: Scroll on x-axis always presented in "Processes" tab despite window width.
https://bugs.kde.org/show_bug.cgi?id=460564 Bug ID: 460564 Summary: Scroll on x-axis always presented in "Processes" tab despite window width. Classification: Plasma Product: plasma-systemmonitor Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: vityas_offic...@yahoo.co.jp CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 152920 --> https://bugs.kde.org/attachment.cgi?id=152920&action=edit demo SUMMARY Scroll on x-axis always presented in "Processes" tab despite window width. Please see attachment. EXPECTED RESULT When there are enough space x-scroll removing should be higher priority than increasing columns width. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460564] Scroll on x-axis always presented in "Processes" tab despite window width.
https://bugs.kde.org/show_bug.cgi?id=460564 --- Comment #2 from Victor Prudniy --- Created attachment 152984 --> https://bugs.kde.org/attachment.cgi?id=152984&action=edit hidden part Only part of last column + area on top of scrollbar is hidden. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460564] Scroll on x-axis always presented in "Processes" tab despite window width.
https://bugs.kde.org/show_bug.cgi?id=460564 Victor Prudniy changed: What|Removed |Added Resolution|INTENTIONAL |WAITINGFORINFO --- Comment #4 from Victor Prudniy --- (In reply to Nate Graham from comment #3) > So then this is working as expected: there's a horizontal scrollbar because > the view content (including table headers) doesn't entirely fit into the > available space. :) It's like ~3500px window width on my first screenshot, surely enough space for all content =) My point is that removing scrollbar should be higher priority than increasing width of each column, because user likely wants no scroll and all columns visible instead of super-wide columns and blank space between content. -- You are receiving this mail because: You are watching all bug changes.
