[krunner] [Bug 487927] Launcher creation adds single quotes to application, preventing ~ expansion.
https://bugs.kde.org/show_bug.cgi?id=487927 --- Comment #2 from Emmett Culley --- Normally I use the launcher edit dialog. I enter a path to a script and save, and it works as expected. However, if the path include ~ I get a "Could not find program ~/bin/script_name". If it then edit the .directory file and remove the single quotes the launcher edit process added and save. Then the launcher doe work as expected that the script ~/bin/script_name does run. I only mention adding single quotes because I noticed that old launcher files on my system do not have that single quotes added and they still work. Since my upgrade to fedoraa 40, some no longers worked and in all cases I found single quotes around the script spec. I see two issues. One that some upgrade started adding single quotes to the script spec on launcher edit save. That caused no propblem, as all launchers still worked. But since upgrade to fedora 49 and KDE to 6, launchers script specs with a ~ no longer work. Unless I remove the single quotes from the launcher .directory file. Hence my suspician that what changed is bash expansion on the launcher script spec failes to translate ~ to my home directory. All I have to do to see this issue is right click on any launcher, alter the Program spec in anyway and save. the spec in the .directory file will now be wrapped in single quotes, even if it didn't before. If the spec contained a ~ then the launcher no longer works. I hope this helps. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 487927] Launcher creation adds single quotes to application, preventing ~ expansion.
https://bugs.kde.org/show_bug.cgi?id=487927 Emmett Culley changed: What|Removed |Added CC|lst_man...@webengineer.com | -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 487888] Kompare doesn't load files from kio connection in dolphin
https://bugs.kde.org/show_bug.cgi?id=487888 Emmett Culley changed: What|Removed |Added CC|lst_man...@webengineer.com | -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 487888] Kompare doesn't load files from kio connection in dolphin
https://bugs.kde.org/show_bug.cgi?id=487888 Emmett Culley changed: What|Removed |Added CC||lst_man...@webengineer.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 487927] Launcher creation adds single quotes to application, preventing ~ expansion.
https://bugs.kde.org/show_bug.cgi?id=487927 Emmett Culley changed: What|Removed |Added CC||lst_man...@webengineer.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 487927] New: Launcher creation adds single quotes to application, preventing ~ expansion.
https://bugs.kde.org/show_bug.cgi?id=487927 Bug ID: 487927 Summary: Launcher creation adds single quotes to application, preventing ~ expansion. Classification: Plasma Product: krunner Version: 6.0.5 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lst_man...@webengineer.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Not sure when this started as I have a mix of desktop objects that have the application bracketed with single quotes in the .desktop file, and some that don't. When I create a launcher now, however, single quotes are always added in the .desktop file. However, I don't believe ading single quotes to the application string is the bug. At least one of the .desktip objects that have single quotes around the application and they worked fine before the upgrade to plasma 6. If I create a launcher using the "browse" button to find and enter the application, the launcher works as expected. So I believe the issue is that with quotes around the application, shell expansion on the '~" character doesn't happen, and so the launcher cannot find the application/script it is supposed to run. Indeed, that is the error notification I see when attempting to use a "bad" launcher. STEPS TO REPRODUCE 1. Create launcher entering ~/bin/script_name to the application field. 2. Click on launcher OBSERVED RESULT Intended script does not run and a "could not find the program" error notification pops up. EXPECTED RESULT ~/bin/srcipt_name should run. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 40 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Kernel version: 6.8.10-300.fc40.x86_64 (64-bit) Currently running wayland. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 487888] New: Kompare doesn't load files from kio connection in dolphin
https://bugs.kde.org/show_bug.cgi?id=487888 Bug ID: 487888 Summary: Kompare doesn't load files from kio connection in dolphin Classification: Applications Product: kompare Version: 4.1.24022 Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: lst_man...@webengineer.com Target Milestone: --- SUMMARY When using fish:// to connect to a remote file system in dolphin, selecting two files, then using context menu to "Compare files", kompare opens but no files are loaded to compare. It works as exepected when on a local file system. Also clicking on a file and oopening with kwrite, the file is loaded in kwrite and if changed saving that loaded file changes the file on the remote host. So KIO seems to be working correctly. Note that comparing remote files worked before the upgrade to KDE 6 (Fedora 39). STEPS TO REPRODUCE 1. Open Dolphin 2. Enter fish://remote_host/etc in location bar 3. Select two files 4. Select "compare files" from context menu OBSERVED RESULT Kompare opens but both panels are empty. I assume that is because the two files selected were not loaded from the remote host. EXPECTED RESULT Kompare should open the two selected files from the remote host. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 40 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Kernel: 6.8.10-300.fc40.x86_64 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 479368] kioexec loads link as text into browser instead of requested web page.
https://bugs.kde.org/show_bug.cgi?id=479368 --- Comment #2 from Emmett Culley --- (In reply to fanzhuyifan from comment #1) > Could you check the .desktop file corresponding to chrome? This can happen > when the relevant .desktop file is missing the %u placeholder. > > https://bugs.kde.org/show_bug.cgi?id=439477#c14 Yes, that fixed it. I removed them as I was using launchers to load chrome for two different profiles. They have been removed for a long time as it worked as expected. This started happening with the latest release. Having said that, I could be wrongs, as I was recently having problems with the launcher icons. That is another bug I will report as soon as I have enough info. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 479368] New: kioexec loads link as text into browser instead of requested web page.
https://bugs.kde.org/show_bug.cgi?id=479368 Bug ID: 479368 Summary: kioexec loads link as text into browser instead of requested web page. Classification: Frameworks and Libraries Product: frameworks-kio Version: 5.111.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: lst_man...@webengineer.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY This bug was descrirbed well in https://bugs.kde.org/show_bug.cgi?id=439477 which seems to be closed. In this case, in addition to links not loading the page in chrome, I am not able to sign into zoom as the google sign in page does not load as html. I am not able to log into zoom and so am not able to participate in any zoom session. As described in the bug mentined above, clicking on any link in any desktop app only loads text and not the requested web page. STEPS TO REPRODUCE 1. Open zoom 2. click on sign-in 3. click on Google sign in OBSERVED RESULT Page text is loaded by chrome instead of the requested web page EXPECTED RESULT To see google sign-in page in browser. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 39 (up to date) (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 326569] Indicates failure after installing from web browser
https://bugs.kde.org/show_bug.cgi?id=326569 --- Comment #6 from Emmett Culley --- I have nothing to add. This was a long timae ago, and I rarily, if ever, install from my browser, and instead use dnf exclusively. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 326569] Indicates failure after installing from web browser
https://bugs.kde.org/show_bug.cgi?id=326569 --- Comment #4 from Emmett Culley --- Wow. This is old. I don't even remember what I was doing with firefox or chrome, and don't know what it meant by "apper". So I suppose this should be closed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 456713] plasma-kded.service hangs for around a minute or more on system shutdown
https://bugs.kde.org/show_bug.cgi?id=456713 Emmett Culley changed: What|Removed |Added CC||lst_man...@webengineer.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454883] In fish portocol, directories with names that end in .d cannot be descended into.
https://bugs.kde.org/show_bug.cgi?id=454883 --- Comment #3 from Emmett Culley --- This seems to be fixed after a recent update of dolphin to 22.04.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454883] In fish portocol, directories with names that end in .d cannot be descended into.
https://bugs.kde.org/show_bug.cgi?id=454883 --- Comment #2 from Emmett Culley --- I spoke too soon. It turns out that when I open the conf.d directory via the location bar I am not able to drag a file or directory into the conf.d directory. I see "Access denied to ." at the top of the listing, but I am not prompted to copy/move. The file is not copied/moved into the conf.d directory. However, if I first rename the directory to conf_d, all works as expected. Enter fish://root@server/etc/conf_d in the location bar, the drag a file into that directory, I am prompted for copy or move, and the file is copied when I select Copy. Note that I am able to rename conf.d to conf_d from dolphin. As noted before, once I have renamed the directory, I can rename it back to conf.d and I am still able to access that directory normally from that dolphin session. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454883] In fish portocol, directories with names that end in .d cannot be descended into.
https://bugs.kde.org/show_bug.cgi?id=454883 --- Comment #1 from Emmett Culley --- I just discovered that if I type the directory name (conf.d) in the location bar, dolphin will descend into it and give me access to the files in that directory. That'll do for a work around. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454883] New: In fish portocol, directories with names that end in .d cannot be descended into.
https://bugs.kde.org/show_bug.cgi?id=454883 Bug ID: 454883 Summary: In fish portocol, directories with names that end in .d cannot be descended into. Product: dolphin Version: 21.12.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: lst_man...@webengineer.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Today I attempted to adjust a webserver configuration using dolphin to connect to fish://root@server/etc. Connection worked as usual and I found I was looking at a listing of the /etc directory. All good and expected. Then I clicked on httpd which switched to listing the /etc/httpd directory. I then clicked on conf.d and got this message at the top of dolphin: "The file fish://server/etc/httpd/conf.d could not be loaded, as it was not possible to read from it. Check if you have read access to this file." And in a pop up dialog I saw this: "Could not read file fish://server/etc/httpd/conf.d." On closer inspection I saw that there was no > next to the directory conf.d, which usually means it is not a directory, but the permissions showed drwxr-xr-w. So I logged into that server via ssh and was able to enter /etc/httpd/conf.d without a problem, and from there edit or view any of the apache config files. Then I tried renaming the conf.d directory to conf_d from the dolphin fish connection. Then I was able click on conf_d to descend into that directory and edit any of the apache config files there. I tried renaming the directory to conf.d and after that was able to descend into that directory from that dolphin session. Closing dolphin, opening it again and connectin to that server via fish again, I was again not able to get into the/etc/httpd/conf.d directory. Turns out this happens no matter which server I connect, some of which are Rocky Linux, most are CentOS Stream 8, and two are CentOS 7. All do the same. That is, any directory named *.d cannot be decended into via fish on dolpin. I just upgraded to Fedora 36, and this was not a problem before the upgrade. I use dolphin multiple times a day to connect to the servers I manage, and this is the first time I saw this. STEPS TO REPRODUCE 1. Connect to remote machine via fish 2. navigate to /etc/httpd 3. click on conf.d OBSERVED RESULT Error message and pop up as described above EXPECTED RESULT Descent into conf.d directory SOFTWARE/OS VERSIONS Fedora: 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I did not see this until updated to Fedora 36 This seem to be related to bug 171473, except is is very old. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447580] Dolphin ignores umask
https://bugs.kde.org/show_bug.cgi?id=447580 Emmett Culley changed: What|Removed |Added CC||lst_man...@webengineer.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447580] New: Dolphin ignores umask
https://bugs.kde.org/show_bug.cgi?id=447580 Bug ID: 447580 Summary: Dolphin ignores umask Product: dolphin Version: 21.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: lst_man...@webengineer.com CC: kfm-de...@kde.org 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. Set user umask to 0002 in either /etc/bashrc or ~/.bashrc. 2. Open dolphin or konqueror and create a directory in any local or remote filesystem 3. Note that prems are set to drwxr-sr-x OBSERVED RESULT Dolphin ignores umask set to 002 I first discoverd it when a user complained she coud not access a file I created on an NFS4 share. I don't see this issue if I use fish:// to access any directory, local or remote. We are on fully updated fedora 34 and 35 systems, and this has been a problem for quite awhile, through many Fedora updates, possibly as far back as fedora 18 (arbitrary number). Until now I've usually just run chmod -R g+w on the share on the file server, then went about my business. I have put it off too long and so did a bit of investigation. This happens on both Konqueror and Dolphin. It never happens in Konsole. Meaning that if I open Konsole and cd to /fs1/work (the nfs share), and create a file or directory, the permissions are set to 664 and 2775 (SGID is set for all directories) as expected with a umask of 002 for all users. Note that the umask on both servers and clients are set to 002. So only Dolphin and Konqueror ignore the umask=0002 setting, and only when not accessing a file system via fish. EXPECTED RESULT drwxrwsr-x permissions when creating a directory and rwxrwxr-x when creating a file. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux/KDE Plasma (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Fedora 34 and other versions of Fedora -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392434] Dolphin does not apply UMASK
https://bugs.kde.org/show_bug.cgi?id=392434 --- Comment #5 from Emmett Culley --- I didn't see that this bug was for kubuntu. I will report if for Fedora. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392434] Dolphin does not apply UMASK
https://bugs.kde.org/show_bug.cgi?id=392434 Emmett Culley changed: What|Removed |Added CC||lst_man...@webengineer.com --- Comment #4 from Emmett Culley --- I can also reprat this issue. I first discoverd it when a user complained she coud not access a file I created on an NFS4 share. I don't see this issue if I use fish:// to access any directory, local or remote. We are on fully updated fedora 34 and 35 systems, and this has been a problem for quite awhile, through many Fedora updates, possibly as far back as fedora 18 (arbitrary number). Unti now I've usually just run chmod -R g+w on the share on the file server, then went about my business. I have put it off too long and so did a bit of investigation. This happens on both Konqueror and Dolphin. It never happens in Konsole. Meaning that if I open Konsole and cd to /fs1/work (the nfs share), and create a file or directory, the permissions are set to 664 and 2775 (SGID is set for all directories) as expected with a umask of 002 for all users. Note that the umask on both servers and clients are set to 002. So only Dolphin and Konqueror ignore the umask=0002 setting, and only when not accessing a file system via fish. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440761] Keyboard short cuts no longer work after update to fedora 34
https://bugs.kde.org/show_bug.cgi?id=440761 --- Comment #9 from Emmett Culley --- Note that I switched to wayland and found that the shortcut still did not work. I didn't change anything in the configuration, but F8 was still set to Yakuake. However, the compose key does work in wayland, whereas it doesn't in X11. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440761] Keyboard short cuts no longer work after update to fedora 34
https://bugs.kde.org/show_bug.cgi?id=440761 Emmett Culley changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440761] Keyboard short cuts no longer work after update to fedora 34
https://bugs.kde.org/show_bug.cgi?id=440761 --- Comment #7 from Emmett Culley --- Created attachment 141066 --> https://bugs.kde.org/attachment.cgi?id=141066=edit Dbus monitor output on pressing meta-F8 Copied dbus monitor output when pressing meta-F8, ewhich is newly assigned to ope system settings -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440761] Keyboard short cuts no longer work after update to fedora 34
https://bugs.kde.org/show_bug.cgi?id=440761 --- Comment #6 from Emmett Culley --- Alt-tab does bring up a graphical list of window in the current desktop, and it can be slow to show up the firts time. I assigned alt-F8 to launch Spectacle and that worked. It was not assigned before that. I assigned mets-F8 to launchsystem settings and that worked. It was not assigned before. Assigning meta-F8, or just F8, to open yakauke still doe not work. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440761] Keyboard short cuts no longer work after update to fedora 34
https://bugs.kde.org/show_bug.cgi?id=440761 --- Comment #5 from Emmett Culley --- [emmett@ws1 ~]$ dbus-monitor signal time=1629987761.259082 sender=org.freedesktop.DBus -> destination=:1.135 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.135" signal time=1629987761.259104 sender=org.freedesktop.DBus -> destination=:1.135 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.135" method call time=1629987763.955210 sender=:1.47 -> destination=org.freedesktop.DBus serial=85 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=ReleaseName string "org.freedesktop.ReserveDevice1.Audio1" signal time=1629987763.955254 sender=org.freedesktop.DBus -> destination=:1.47 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string "org.freedesktop.ReserveDevice1.Audio1" signal time=1629987763.955276 sender=org.freedesktop.DBus -> destination=(null destination) serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string "org.freedesktop.ReserveDevice1.Audio1" string ":1.47" string "" method return time=1629987763.955311 sender=org.freedesktop.DBus -> destination=:1.47 serial=4294967295 reply_serial=85 uint32 1 signal time=1629987764.680989 sender=:1.15 -> destination=(null destination) serial=1449 path=/org/freedesktop/Notifications; interface=org.freedesktop.Notifications; member=NotificationClosed uint32 156 uint32 1 ^[[19~^[[19~method call time=1629987770.736529 sender=:1.130 -> destination=org.freedesktop.DBus serial=22 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/Config',interface='org.kde.knotification',member='reparseConfiguration'" I left it on while pressing F8 which is assigned to open yakauke and attempted to use the compose key to add a degree symbol. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440761] Keyboard short cuts no longer work after update to fedora 34
https://bugs.kde.org/show_bug.cgi?id=440761 --- Comment #3 from Emmett Culley --- x11. I also installed gdm and xdm and tried them. Didn't make any difference. Alt-tab seems to work, though it isn't sticky. I dont use that key combo ans so am not familiar with how it shuld work. [emmett@ws1 ~]$ dbus-monitor signal time=1628641628.567463 sender=org.freedesktop.DBus -> destination=:1.173 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.173" signal time=1628641628.567483 sender=org.freedesktop.DBus -> destination=:1.173 serial=4294967295 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.173" ^[[19~ Last line is what was prointed when I pressed the F8 key while focused on the terminal. Nothing else happens if I hit any key when focus is on the desktop -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 440761] New: Keyboard short cuts no longer work after update to fedora 34
https://bugs.kde.org/show_bug.cgi?id=440761 Bug ID: 440761 Summary: Keyboard short cuts no longer work after update to fedora 34 Product: frameworks-plasma Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: lst_man...@webengineer.com CC: plasma-b...@kde.org Target Milestone: --- Since updating nmy system from feroda 33 keyboard short cuts do not work. For example, I set the Yakuake open short cut to F8 because F7 seems to have been taken over by chrome. Pressing F8 does nothing. However I also change Yuakw to open when moving the mouse to the top of the screen, and that doen open yakuake. Pressing ctl-atl-backspace also dose nothing, even though the key combination is configured for kill destkop. I don't use a lot of shortcuts, but those are ones I do use, especially to open yakuake. Also the compose key does not work. I believe that is related to shortcuts not working. Note that I do not use wayland, which brings up what may be the problem. If I press ctl-alt f2 nothing happens. In the past that would switch to the first system terminal session. Pressing ctl-alt-f1 takes me to an empty screen. Could it be somthing to do with switching to x11? STEPS TO REPRODUCE 1. strike any system keyboard shortcut key conbination, 2. Attrempt to enter special character via assigned compose key Observed results 1. strike any defined system shoutcut key combination and nothing happens 2. Setting yakuake shortcut to F8 does not cause yakauke to open. 3. Ctl-Alt Backspace does nothin EXPECTED RESULT striking system keyboard shortcut key conbination should cause the action expected. 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.
[kompare] [Bug 402363] File mode always set to 0600 when saving changes
https://bugs.kde.org/show_bug.cgi?id=402363 Emmett Culley changed: What|Removed |Added CC||lst_man...@webengineer.com --- Comment #7 from Emmett Culley --- Here we are in Fedore 32 and this is still a serious inconvenience. How can we find out where this issue is in KDE priorities? -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 406331] New: Slow schrool with mouse scroll wheel
https://bugs.kde.org/show_bug.cgi?id=406331 Bug ID: 406331 Summary: Slow schrool with mouse scroll wheel Product: plasma-integration Version: 5.15.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lst_man...@webengineer.com Target Milestone: --- Since Update of Fedora today, 4/4/19, mouse scroll wheel is slow. It take between 7 an 8 "clicks" of the wheel to cause any page to scroll. It doesn't seem to be application specific, as I have this problem in Chrome and well and Konsole. Alll aps I've tested so far. Including PHPstorm, a Java app. STEPS TO REPRODUCE 1. Login into plasma desktop 2. Open the Chrome web browser 3. Roll mouse wheel OBSERVED RESULT Extremely slow scrolling. Note that grabbing the scroll bar does scroll as expected. It is only the mouse wheel that has this issue. Disabling the mouse detent click does not improve the scroll speed. EXPECTED RESULT Viewport to scroll one line or more per wheel detent click SOFTWARE/OS VERSIONS Operating System: Fedora 29 KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.55.0 Kernel Version: 5.0.5-200.fc29.x86_64 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor Memory: 15.7 GiB of RAM ADDITIONAL INFORMATION WOrk perfectly prior to this morning's dnf upgrade -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 369520] FISH: directories are mistaken for files and vice-versa
https://bugs.kde.org/show_bug.cgi?id=369520 --- Comment #2 from Emmett Culley <lst_man...@webengineer.com> --- After doing some more testing I found that this issue happens only on certain servers. Connecting to any of the server on my LAN seems to work OK. Also one remote server I've been using for a number of years works as expected. One server I am having an issue is a CentOS VM in the cloud. Could this be a server ssh configuration issue, or possibly a firewall issue? I have no problem connectiny via ssh to that VM. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 369520] FISH: directories are mistaken for files and vice-versa
https://bugs.kde.org/show_bug.cgi?id=369520 Emmett Culley <lst_man...@webengineer.com> changed: What|Removed |Added CC||lst_man...@webengineer.com --- Comment #1 from Emmett Culley <lst_man...@webengineer.com> --- I have the same issue: kio-extras-17.12.1-1.fc27.x86_64 In dolphin and konqueror if I enter on fish:://example.com/etc/fail2ban I can see the fail2ban directory contents on example.com, but if I click on action.d I get a pop up that want to p=open the directory as a file. Even adding /action.d to the contents of the location bar gets me a popup. However, if I click on the expand carrot I can then see the contents of the action.d directory, and can even open a file in there by clicking on a file name. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 389081] New: kontact crash
https://bugs.kde.org/show_bug.cgi?id=389081 Bug ID: 389081 Summary: kontact crash Product: kontact Version: 5.7.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: lst_man...@webengineer.com Target Milestone: --- Application: kontact (5.7.0) Qt Version: 5.9.2 Frameworks Version: 5.41.0 Operating System: Linux 4.14.13-300.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: i was attepting to edit an entry. it crashed when i clicked on the notes tab The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc56166b900 (LWP 24694))] Thread 25 (Thread 0x7fc422a0f700 (LWP 24727)): #0 0x7fc55ac0e888 in read () from /lib64/libc.so.6 #1 0x7fc54acf70e0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7fc54acb29e8 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7fc54acb2e80 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7fc54acb2fec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7fc55ba8935b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7fc55ba370ea in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7fc55bba in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7fc55b88cb92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7fc54f85761b in start_thread () from /lib64/libpthread.so.0 #10 0x7fc55ac1f91f in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7fc42b2af700 (LWP 24725)): #0 0x7fc54acb2e61 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #1 0x7fc54acb2fec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #2 0x7fc55ba8935b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7fc55ba370ea in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fc55bba in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7fc55b88cb92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #6 0x7fc54f85761b in start_thread () from /lib64/libpthread.so.0 #7 0x7fc55ac1f91f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7fc4d1ffb700 (LWP 24724)): #0 0x7fc54f85dc4b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc5420e2604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7fc5420e2649 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7fc54f85761b in start_thread () from /lib64/libpthread.so.0 #4 0x7fc55ac1f91f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7fc4d27fc700 (LWP 24723)): #0 0x7fc54f85dc4b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc554209e85 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7fc55420a367 in base::SequencedWorkerPool::Worker::Run() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7fc55420b101 in base::SimpleThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7fc5542077cb in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7fc54f85761b in start_thread () from /lib64/libpthread.so.0 #6 0x7fc55ac1f91f in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7fc4d2ffd700 (LWP 24722)): #0 0x7fc54f85dc4b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc554209e85 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7fc55420a367 in base::SequencedWorkerPool::Worker::Run() () from /lib64/libQt5WebEngineCore.so.5 #3 0x7fc55420b101 in base::SimpleThread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7fc5542077cb in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7fc54f85761b in start_thread () from /lib64/libpthread.so.0 #6 0x7fc55ac1f91f in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7fc4d37fe700 (LWP 24719)): #0 0x7fc55ac2e47b in __libc_enable_asynccancel () from /lib64/libc.so.6 #1 0x7fc55ac0e876 in read () from /lib64/libc.so.6 #2 0x7fc52fd9f941 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #3 0x7fc53427cc9e in pa_mainloop_prepare () from /lib64/libpulse.so.0 #4 0x7fc53427d710 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #5 0x7fc53427d7d0 in pa_mainloop_run () from
[konqueror] [Bug 382976] Clicking on OTD file does not open Libreoffice
https://bugs.kde.org/show_bug.cgi?id=382976 --- Comment #2 from Emmett Culley <lst_man...@webengineer.com> --- Yes, uninstalling krusader fixed the problem. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 382976] New: Clicking on OTD file does not open Libreoffice
https://bugs.kde.org/show_bug.cgi?id=382976 Bug ID: 382976 Summary: Clicking on OTD file does not open Libreoffice Product: konqueror Version: 5.0.97 Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: lst_man...@webengineer.com Target Milestone: --- When I click on any Libreoffice file (somefile.odt) I see what looks like a directory structure instead of seeing Libreoffice open that file. It looks like it might be some kind of meta data: Configurations2 META-INF Pictures Thumbnails content.xml manifest.rdf meta.xml mimetype settings.xml styles.xml If I click on the directory up "^" button I then see this error: This site can’t be reached The webpage at error:/?error=111=%2Fhome%2Femmett%2FCCCTC%2Ftimesheets%2F#krarc:/home/emmett/CCCTC/timesheets/ might be temporarily down or it may have moved permanently to a new web address. ERR_UNKNOWN_URL_SCHEME Is it possible karc is the problem? It works correcty in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376166] New: System setting dialog crashed when clicking on all seting (back) link a top left.
https://bugs.kde.org/show_bug.cgi?id=376166 Bug ID: 376166 Summary: System setting dialog crashed when clicking on all seting (back) link a top left. Product: systemsettings Version: 5.8.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lst_man...@webengineer.com Target Milestone: --- Application: systemsettings5 (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.15-200.fc24.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: I was working on mitigating a video jitter issue and so change composting type from OpenGL to Xrender. Chaning to Xrender seemed to stop the jitter, but then when going back to OpenGL the jitter was still gone. So I turned "enable composter on startup off then hit the back link. Dialog then crashed. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f762af02900 (LWP 24778))] Thread 4 (Thread 0x7f75fcb96700 (LWP 24782)): #0 0x7f7623f1c460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7604a34c4b in util_queue_thread_func () from /usr/lib64/dri/r600_dri.so #2 0x7f7604a34aa7 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so #3 0x7f7623f166ca in start_thread () from /lib64/libpthread.so.0 #4 0x7f7626eaef7f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f7607b5e700 (LWP 24781)): #0 0x7f761fcde7f9 in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7f761fc986a6 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f761fc9907b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f761fc9926c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f7627cb373b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f7627c6473a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f7627ac15f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f76283bc739 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x7f7627ac59da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f7623f166ca in start_thread () from /lib64/libpthread.so.0 #10 0x7f7626eaef7f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f760fe2e700 (LWP 24780)): #0 0x7f7626ea301d in poll () from /lib64/libc.so.6 #1 0x7f7624562d10 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f7624564aa9 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f761456ad69 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f7627ac59da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f7623f166ca in start_thread () from /lib64/libpthread.so.0 #6 0x7f7626eaef7f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f762af02900 (LWP 24778)): [KCrash Handler] #6 0x7f762653fb95 in QV4::WeakValue::free() () from /lib64/libQt5Qml.so.5 #7 0x7f76265b0912 in QV4::QObjectWrapper::destroyObject(bool) () from /lib64/libQt5Qml.so.5 #8 0x7f7626446baf in QV4::MemoryManager::sweep(bool) () from /lib64/libQt5Qml.so.5 #9 0x7f7626447fbc in QV4::MemoryManager::~MemoryManager() () from /lib64/libQt5Qml.so.5 #10 0x7f762652f4ab in QV4::ExecutionEngine::~ExecutionEngine() () from /lib64/libQt5Qml.so.5 #11 0x7f762666ef96 in QV8Engine::~QV8Engine() () from /lib64/libQt5Qml.so.5 #12 0x7f762666f0b9 in QV8Engine::~QV8Engine() () from /lib64/libQt5Qml.so.5 #13 0x7f76264c67b6 in QJSEngine::~QJSEngine() () from /lib64/libQt5Qml.so.5 #14 0x7f76265da75d in QQmlEngine::~QQmlEngine() () from /lib64/libQt5Qml.so.5 #15 0x7f76265da819 in QQmlEngine::~QQmlEngine() () from /lib64/libQt5Qml.so.5 #16 0x7f7627c9325c in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #17 0x7f762918c09b in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #18 0x7f762bc37df9 in QQuickWidget::~QQuickWidget() () from /lib64/libQt5QuickWidgets.so.5 #19 0x7f7627c9325c in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #20 0x7f762918c09b in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #21 0x7f762918c389 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #22 0x7f7627c9325c in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #23 0x7f762918c09b in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #24 0x7f76292da379 in QStackedWidget::~QStackedWidget() () from /lib64/libQt5Widgets.so.5 #25 0x7f7627c9325c in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #26 0x7f762918c09b in
