[frameworks-kio] [Bug 427812] Improve handling of trailing white spaces in file names when saving
https://bugs.kde.org/show_bug.cgi?id=427812 --- Comment #2 from Claudius Ellsel --- That might be an option, although the merge request has been started to remove those pop ups if I am not mistaken. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427958] Debounce hiding the window selector upon unhovering program group icon
https://bugs.kde.org/show_bug.cgi?id=427958 --- Comment #1 from Szczepan Hołyszewski --- In order to be certain to avoid "losing" the window selector, the user must Very Consciously move the pointer vertically upwards onto the window selector, and Only Then sideways to select the desired thumbnail. This turns an elementary action into a "minigame". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427958] New: Debounce hiding the window selector upon unhovering program group icon
https://bugs.kde.org/show_bug.cgi?id=427958 Bug ID: 427958 Summary: Debounce hiding the window selector upon unhovering program group icon Product: plasmashell Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: rula...@wp.pl CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Hiding the window selection UI upon unhovering the program group icon on the Icons-Only Task Bar should be debounced to prevent the UI from being hidden as the user accidentally hovers an adjacent icon for a split second when moving the pointer towards one of the tumbnails in the window selection UI. STEPS TO REPRODUCE 1. Open two instances of a program, so that they get grouped under a single icon in the Icons-Only Task Bar 2. Hover over the group icon and wait for the window selection UI to appear 3. Try selecting one of the thumbnails. OBSERVED RESULT More often than not, as you move the pointer towards the thumbnail, you will accidentally hover an adjacent icon on the taskbar for a split second. This will cause the window selection UI to disappear. EXPECTED RESULT When the window selection UI for a taskbar group is shown, the "another taskbar icon was hovered" event should be debounced. Instead of immediately hiding the window selection UI when such an event occurs, a timer should be started that would hide the UI after e.g. 100ms, and would be cancelled if the window selection UI is hovered within that timeframe. Operating System: Arch Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.1-zen2-1-zen OS Type: 64-bit Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 960/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 427954] "First, you must pick a product on which to enter a bug" is becoming a prohibitively difficult puzzle
https://bugs.kde.org/show_bug.cgi?id=427954 Nicolás Alvarez changed: What|Removed |Added CC||nalva...@kde.org --- Comment #2 from Nicolás Alvarez --- Most applications have a "Help -> Report a Bug" that already fills the correct product. It seems most components of the Plasma desktop lack this, though... We'll have to figure out the best way to show it. You can always report Plasma bugs with the generic product=plasma-desktop component=general and let someone else classify it in the correct place, as long as the bug description is reasonably well written (sometimes people are very bad at explaining things in the bug description and we can't even figure out what application they are talking about!). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427957] New: Switch off mail pane (on demand)
https://bugs.kde.org/show_bug.cgi?id=427957 Bug ID: 427957 Summary: Switch off mail pane (on demand) Product: kmail2 Version: 5.15.2 Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: markus.elfr...@web.de Target Milestone: --- A mail message pane can be supported eventually. https://kontact.kde.org/assets/img/kontact-kmail.png There can be reasons to work without this widget occasionally. * Its service became broken. See also: Missing content display in the mail pane https://bugs.kde.org/show_bug.cgi?id=427584 * You would like to work with an user interface configuration where more messages should be listed. Thus extra widgets should be excluded from the display for this use case. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427956] New: Date format does not change when application language is changed
https://bugs.kde.org/show_bug.cgi?id=427956 Bug ID: 427956 Summary: Date format does not change when application language is changed Product: kmymoney Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: spill...@gmail.com Target Milestone: --- SUMMARY The date format does not change when application language is changed. STEPS TO REPRODUCE 1. Open the Ledger, the date format is mm/dd/ 2. Goto Help->Switch Application Language to British 3. After restarting the KmyMoney, the date format in Ledger does not change to dd/mm/ OBSERVED RESULT Ledger still display in mm/dd/ EXPECTED RESULT Ledger should display date in dd/mm/ 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.
[bugs.kde.org] [Bug 427954] "First, you must pick a product on which to enter a bug" is becoming a prohibitively difficult puzzle
https://bugs.kde.org/show_bug.cgi?id=427954 --- Comment #1 from Szczepan Hołyszewski --- Suggestion: write an utility that will allow the user to click anywhere on the screen, xkill-style, and if the window thus selected belongs to a KDE "product", the utility would disclose the correct "product" to the user. Another possibility: add the "product" information to the "About" page of the properties dialog of every "thing" that has a properties dialog accessible via a context menu. For example, right clicking on an icon of a program group in the Icon Task Bar shows a context menu with a "More actions >" submenu, which contains "Icon Task Bar settings..." item at the bottom, which shows the settings dialog, which contains an "About" page. That page should display a sentence to the effect of "When reporting bugs for this component, choose "" as the product in the first step of the procedure". -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 427955] New: Investments->Equities can also show Cost
https://bugs.kde.org/show_bug.cgi?id=427955 Bug ID: 427955 Summary: Investments->Equities can also show Cost Product: kmymoney Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: spill...@gmail.com Target Milestone: --- SUMMARY Investments->Equities Currently the screen shows 1. Equity 2. Symbol 3. Value 4. Quantity 5. Price It would be great to see "Cost of acquisition of the investment" STEPS TO REPRODUCE 1. Navigate to Investments 2. Select the tab "Equities" OBSERVED RESULT Cost is an important factor in the Investments EXPECTED RESULT Does not include Cost as part of the investment SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Additionally if ROI (Return on Investment) is also shown, that would make it great. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427940] Allow running multiple program instances for the same user
https://bugs.kde.org/show_bug.cgi?id=427940 Markus Elfring changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #2 from Markus Elfring --- (In reply to Laurent Montel from comment #1) I propose to reconsider this view. Would you like to help a bit more for working with message folders in parallel (besides the selection of favourite directories)? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 427954] "First, you must pick a product on which to enter a bug" is becoming a prohibitively difficult puzzle
https://bugs.kde.org/show_bug.cgi?id=427954 Szczepan Hołyszewski changed: What|Removed |Added Summary|"First, you must pick a |"First, you must pick a |product on which to enter a |product on which to enter a |bug" is becoming an |bug" is becoming a |increasingly difficult |prohibitively difficult |puzzle |puzzle -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 427954] New: "First, you must pick a product on which to enter a bug" is becoming an increasingly difficult puzzle
https://bugs.kde.org/show_bug.cgi?id=427954 Bug ID: 427954 Summary: "First, you must pick a product on which to enter a bug" is becoming an increasingly difficult puzzle Product: bugs.kde.org Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: rula...@wp.pl CC: she...@kde.org Target Milestone: --- SUMMARY The requirement to first "pick a product" is becoming an increasingly difficult puzzle. For example, I want to report an issue with the UI for selecting the window that appears when I hover on a group icon in Icon Task Bar. The "thing" I want to report the issue with is the Icon Task Bar, because that is the "thing" I interact with when I experience the issue. However the list of nearly 500 "things" presented on the "First, you must pick a product on which to enter a bug" page not seem to contain "Icon Task Bar", and I only know this AFTER painstakingly reading ALL 484 descriptions of all 484 "things" listed there. I don't think I will be exaggerating or needlessly harsh in my judgment if I say that this is completely unacceptable usability wise. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427940] Allow running multiple program instances for the same user
https://bugs.kde.org/show_bug.cgi?id=427940 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- Hi, We can't it's an unique apps. Regards -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 427791] Undo for remove entry
https://bugs.kde.org/show_bug.cgi?id=427791 Alexander Semke changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||alexander.se...@web.de Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 353352] Cannot setup any account in the account wizard
https://bugs.kde.org/show_bug.cgi?id=353352 kdeb...@onlinehome.de changed: What|Removed |Added Version|unspecified |5.14.2 Platform|Kubuntu Packages|openSUSE RPMs CC||kdeb...@onlinehome.de --- Comment #2 from kdeb...@onlinehome.de --- The account wizard does not work at all. As soon as I have finished setting a POP3 account up where the automatical lookup of data is not possible, only a ghost profile is created. It lacks central information from the name of the profile to the pop3 server. Once I have changed it again I have to restart kmail and akonadi until it's actually displayed in the config dialogue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427258] Wacom Tablet touch screen sometimes not recognizing clicks, but only in KDE applications
https://bugs.kde.org/show_bug.cgi?id=427258 basch...@yahoo.de changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from basch...@yahoo.de --- Forgot that I needed to change the Status after reporting back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427299] Wake up fails after suspending when monitor attached.
https://bugs.kde.org/show_bug.cgi?id=427299 vali53...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from vali53...@gmail.com --- I want to mention that in the previous comment that I've sent fixes was temporary. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427953] New: Unique instance and open in tabs ignored
https://bugs.kde.org/show_bug.cgi?id=427953 Bug ID: 427953 Summary: Unique instance and open in tabs ignored Product: okular Version: 1.11.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: okularbugrep...@mailinator.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set "Open new files in tabs" in Settings 2. Add a registry "Parameter" key in [HKEY_CLASSES_ROOT\AppXhptkdxysnj90q56w5z3sx7d7a55gse06\Shell\open] with value '--unique "%1"' OBSERVED RESULT Each new file gets opened in a new window (with a new process). Passing the --unique argument show a dialog every time saying something like 'Another unique instance is running, this won't be the unique instance...' although there are no Okular processes running on the system. EXPECTED RESULT Open all (PDF) files in tabs of a single program instance. SOFTWARE/OS VERSIONS Windows: 10 build 2004 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.
[rkward] [Bug 427670] Error at start and crash when conducting time series
https://bugs.kde.org/show_bug.cgi?id=427670 --- Comment #3 from Thomas Friedrichsmeier --- Sorry to hear that. So what is your installed version of R? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #22 from Kishore Gopalakrishnan --- (In reply to Nate Graham from comment #16) > Can confirm the issue. > > It looks like the back/forward navigation calculates the prior position in > the document based on scroll position and was not designed for animated > scrolling. So the animated scrolling effect effectively populates the > "location history" with multiple locations in the document when it should > not. > > I'll see what I can do. Worst-case scenario, we revert animated scrolling > when clicking on links until we can fix the root cause and support both. The same history bug also appears when you use the 'go to page' option with animated scrolling enabled, so in case you do this, you would also have to disable animated scrolling for the 'go to page' feature. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427896] Crash after using color picker in both Display Renders ANGLE or D3d
https://bugs.kde.org/show_bug.cgi?id=427896 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425891] Akonadi crash in KMail
https://bugs.kde.org/show_bug.cgi?id=425891 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425539] Rows display displays one row too many with an i18n error in it
https://bugs.kde.org/show_bug.cgi?id=425539 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426228] hovering over a button the tool tip dialog appears but is a blank white box
https://bugs.kde.org/show_bug.cgi?id=426228 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400540] KDE Partition Manager taking an extremely long time to start
https://bugs.kde.org/show_bug.cgi?id=400540 --- Comment #15 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 427330] Plasma freezes when playing Rocket League w/ Steam Proton. Powerdevil seems to be the Culprit.
https://bugs.kde.org/show_bug.cgi?id=427330 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426745] I opened up my sketch on Krita and my sketch is completely messed up, the lines look like staircases
https://bugs.kde.org/show_bug.cgi?id=426745 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374211] Automatic timeline scrolling during playback is jerky and in large chunks instead of smooth scrolling
https://bugs.kde.org/show_bug.cgi?id=374211 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427269] Delay in move tool's recognition of transparency lock
https://bugs.kde.org/show_bug.cgi?id=427269 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427299] Wake up fails after suspending when monitor attached.
https://bugs.kde.org/show_bug.cgi?id=427299 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368778] KDE Partiton Manager crashed when importing .ISO as partiton table
https://bugs.kde.org/show_bug.cgi?id=368778 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427283] Arrowheads in annotation tool not shown in other pdf viewers
https://bugs.kde.org/show_bug.cgi?id=427283 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427258] Wacom Tablet touch screen sometimes not recognizing clicks, but only in KDE applications
https://bugs.kde.org/show_bug.cgi?id=427258 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 388054] Crash when changing subtitle template
https://bugs.kde.org/show_bug.cgi?id=388054 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 375711] Kdenlive/Win: Track-wise Crop, Pan, Tilt effect lost when loading Kdenlive/Linux project
https://bugs.kde.org/show_bug.cgi?id=375711 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kiriki] [Bug 225581] please add undo to kiriki
https://bugs.kde.org/show_bug.cgi?id=225581 d...@chibiphotography.com changed: What|Removed |Added Status|RESOLVED|REOPENED CC||d...@chibiphotography.com Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #2 from d...@chibiphotography.com --- How is status RESOLVED when 10 years later, no feature improvement has occurred? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427735] Animation Hotkey for new keyframe needs mouseclick on docker before it will allow triggering
https://bugs.kde.org/show_bug.cgi?id=427735 --- Comment #2 from Stuart McWhinney --- I can create blank frames by alternating the right arrow and the shortcut, however if I draw on the blank frame, I can only move with the arrows rather and no longer create new frames. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423539] Password box icon to show/hide password is inverted
https://bugs.kde.org/show_bug.cgi?id=423539 --- Comment #2 from 2wxsy5823...@opayq.com --- > Eye icon is striked through when the password is hidden > and normal when the password is shown Example: KeePassXC > Eye icon is normal when the password is hidden > and striked through when the password is shown Example: ProtonMail -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427812] Improve handling of trailing white spaces in file names when saving
https://bugs.kde.org/show_bug.cgi?id=427812 --- Comment #1 from 2wxsy5823...@opayq.com --- How about a popup dialog like this? > The name has trailing space(s), are you sure? > Trailing spaces can cause issues on Windows in shared environments. > > [X] Automatically remove trailing whitespace in the future (Checkbox, checked > by default) > > Button 1: [Cancel] (Returns to rename window) > Button 2: [Continue] (Keep trailing space) > Button 3: [Trim trailing space] -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427952] New: Launched several times itself and crashed
https://bugs.kde.org/show_bug.cgi?id=427952 Bug ID: 427952 Summary: Launched several times itself and crashed Product: kdeconnect Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: il...@fastmail.fm Target Milestone: --- Application: kdeconnectd (1.4.0) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.8.14-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: I noticed an icon on panel (taskbar) flickering, it seems to be kde connect. - Custom settings of the application: I have Wayland (Full) enabled on openSUSE Tumbleweed (if related), Nokia 5.1 Plus / Android 10 -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [New LWP 2103] [New LWP 2130] [New LWP 30936] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f820e00fe7f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f820c103840 (LWP 2077))] Thread 4 (Thread 0x7f8202b8f640 (LWP 30936)): #0 0x7f820e015799 in syscall () from /lib64/libc.so.6 #1 0x7f820e39db51 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:133 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:135 #3 futexSemaphoreTryAcquire_loop (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 futexSemaphoreTryAcquire (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 QSemaphore::acquire (this=0x7f820de05540, n=) at thread/qsemaphore.cpp:326 #6 0x7f820dd55bf4 in ?? () from /usr/lib64/libQt5Network.so.5 #7 0x7f820e39b911 in QThreadPrivate::start (arg=0x7f820de05520) at thread/qthread_unix.cpp:329 #8 0x7f820d695eb1 in start_thread () from /lib64/libpthread.so.0 #9 0x7f820e01accf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f82035ef640 (LWP 2130)): #0 0x7f820e00b8dc in read () from /lib64/libc.so.6 #1 0x7f820ccaa18f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f820cc6113e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f820cc61595 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f820cc6170f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f820e5d25cb in QEventDispatcherGlib::processEvents (this=0x7f81fc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f820e579a1b in QEventLoop::exec (this=this@entry=0x7f82035eecc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f820e39a7ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f820e39b911 in QThreadPrivate::start (arg=0x560999584990) at thread/qthread_unix.cpp:329 #9 0x7f820d695eb1 in start_thread () from /lib64/libpthread.so.0 #10 0x7f820e01accf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8208edd640 (LWP 2103)): #0 0x7f820e00fe7f in poll () from /lib64/libc.so.6 #1 0x7f820cc615ee in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f820cc6170f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f820e5d25cb in QEventDispatcherGlib::processEvents (this=0x7f8204000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f820e579a1b in QEventLoop::exec (this=this@entry=0x7f8208edcc70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f820e39a7ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f820e87fa27 in QDBusConnectionManager::run (this=0x7f820e8ecd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #7 0x7f820e39b911 in QThreadPrivate::start (arg=0x7f820e8ecd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:329 #8 0x7f820d695eb1 in start_thread () from /lib64/libpthread.so.0 #9 0x7f820e01accf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f820c103840 (LWP 2077)): [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x6564656572662e6f) at /usr/include/c++/10/bits/atomic_base.h:741 #5 std::atomic::load (__m=std::memory_order_relaxed, this=0x6564656572662e6f) at /usr/include/c++/10/atomic:523 #6 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #7 QBasicAtomicPointer::loadRelaxed (this=0x6564656572662e6f) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 #8 QObjectPrivate::maybeSignalConnected (this=this@entry=0x7f8204076270, signalIndex=signalIndex@entry=5) at kernel/qobject.
[dolphin] [Bug 427929] Have no size limit for trash by default
https://bugs.kde.org/show_bug.cgi?id=427929 2wxsy5823...@opayq.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from 2wxsy5823...@opayq.com --- Although the default size limit for trash is 10%, the default action is "show a warning". In other words, under default settings, oldest or largest files will not be automatically deleted even if the trash is full. Reference: https://invent.kde.org/frameworks/kio/-/blob/master/src/ioslaves/trash/kcmtrash.cpp -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 427951] New: Display is hashed after setting the time in the startup tutorial
https://bugs.kde.org/show_bug.cgi?id=427951 Bug ID: 427951 Summary: Display is hashed after setting the time in the startup tutorial Product: krfb Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: jcschult...@hotmail.com Target Milestone: --- Created attachment 132548 --> https://bugs.kde.org/attachment.cgi?id=132548&action=edit Picture of the hash noise on the star field display SUMMARY I just got a Raspberry PI running KStars 3.5.0 beta working with TightVNC on a Windows 10 laptop. Following the Burwell tutorial "Setting the Raspberry Pi for Remote Telescope Imaging over your home nework" STEPS TO REPRODUCE 1. follow tutorial directions up to SELECT CLOCK ICON. At that point the display generated hash noise all over the star field BUT NOT the title bar now the control icons. See attached picture 2. 3. OBSERVED RESULT See the attached picture of the KStars display EXPECTED RESULT a normal star pattern display SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Working on getting the Raspberry pi as the remote device. At the moment, the Raspberry Pi is physically connected to Ethernet. I tried my Windows PC with both wireless and wired Ethernet. Same effect. The noise/has pattern does change but does not go away. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427028] Phonecalls not pausing VLC during phonecall
https://bugs.kde.org/show_bug.cgi?id=427028 --- Comment #6 from voncl...@gmail.com --- (In reply to Nicolas Fella from comment #5) > After some debugging we found that the information that the call is finished > is sent with some large delay (30s). Possiblity due to the Android system > sending it with delay, but hard to tell without talking a closer look at the > Android app Seems to be the cause after using it more often. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427753] There is a problem with the underline annotation
https://bugs.kde.org/show_bug.cgi?id=427753 --- Comment #2 from andy --- (In reply to David Hurka from comment #1) > Thanks for your report. Unfortunately I have trouble understanding it, since > there are different possible interpretations to “select comment” in Okular. > > I understand that you created an underline annotation (say, a black > underline). After that: > a) Did you deselect the underline annotation tool and double-clicked the > annotation in the document view area, so a black annotation comment window > opened? > b) Or did you select the popup comment annotation tool and clicked on the > underline annotation to add a comment to it? > > In case of a, I don’t know what you mean with the right side and the left > side, and the position relationship. Can you add a screenshot of the > problem, or even a screencast? > > In case of b, you possibly misunderstood the annotation workflow of Okular. > To add a comment to an existing annotation, you need to deselect the > annotation tool (e. g. by clicking the “Browse” tool), and then double-click > the annotation in the view area, or right-click it and select “Open popup > note”. However, the comment will not be visible unless you explicitely > double-click the annotation again. If the comment should be obviously > visible, you need to create a second annotation of type “Popup note” or > “Inline note”. Through your reminding, I seem to understand where I was wrong. Therefore, the problem should not be okular's bug, but my misoperation. By select comment, I mean underline comments. By clicking on the left and right, I mean the left and right ends of the underline. My improper operation is that when I use the underline comment to select a sentence, I do not invert the underline comment, but double-click to open a pop-up window to add comments. The error occurs when you double-click. Due to the mouse movement, I mistakenly selected a character. That is to say, in a sentence, I not only selected the whole sentence, but also selected a certain character. When I double-click to pop up the underline comment window, I may hit the underline of that character or the whole sentence. That's what caused me the illusion that clicking on the left and right sides of the underline would bring up different comments. In fact, I added two underscores without knowing it. I'm sorry that my Chinglish is not accurate enough, and thank you for your patience. -- You are receiving this mail because: You are watching all bug changes.
[pimsettingexporter] [Bug 427318] pimsettingexporter is missing in neon.kde.org 5.19
https://bugs.kde.org/show_bug.cgi?id=427318 Christoph Feck changed: What|Removed |Added Resolution|DOWNSTREAM |MOVED --- Comment #2 from Christoph Feck --- Already reported as bug 426809. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427950] New: "Application Style" settings crash when scrolling style view/list
https://bugs.kde.org/show_bug.cgi?id=427950 Bug ID: 427950 Summary: "Application Style" settings crash when scrolling style view/list Product: systemsettings Version: 5.19.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- Application: systemsettings5 (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 4.19.148-gentoo-nobuiltinmemcmp ppc64le Windowing system: X11 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: No matter how I scroll it (scroll bar, keyboard, scroll wheel), System Settings crashes when I try to scroll down in the Application Style list. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x7ffe50592100 in qtcMax (b=, a=@0x7fffc0003f78: 0) at .cmake_utils_base/cmake_c_macros/include_fix/qtcurve-utils/number.h:31 #7 QtCurve::Rect::intersect(_cairo_rectangle_int const*, _cairo_rectangle_int const*, _cairo_rectangle_int*) (src1=0x7fffc0003f78, src2=0x0, dest=0x7fffc0003f78) at /var/tmp/portage/x11-themes/qtcurve-1.9.0-r1/work/qtcurve-1.9.0/lib/cairo/utils.cpp:47 #8 0x7ffe5061e670 in QtCurve::Rect::constrain (con=, _rect=0x7fffc0003f78) at .cmake_utils_base/cmake_c_macros/include_fix/qtcurve-cairo/utils.h:102 #9 QtCurve::qtcSetProgressStripeClipping(cairo_t*, QtcRect const*, int, int, int, int, int, bool) (cr=cr@entry=0x1375136e0, area=, area@entry=0x0, x=x@entry=0, y=, y@entry=0, width=, width@entry=107, height=, height@entry=23, animShift=animShift@entry=-10, horiz=, horiz@entry=true) at /var/tmp/portage/x11-themes/qtcurve-1.9.0-r1/work/qtcurve-1.9.0/gtk2/style/drawing.cpp:1412 #10 0x7ffe50625fd4 in QtCurve::drawProgress(_cairo*, _GtkStyle*, GtkStateType, _GtkWidget*, _cairo_rectangle_int const*, int, int, int, int, bool, bool) (cr=0x1375136e0, style=0x1362b2f00 [QtCurveStyle], state=, widget=0x1363319b0 [GtkProgressBar], area=0x0, x=1, y=1, width=105, height=21, rev=false, isEntryProg=false) at /var/tmp/portage/x11-themes/qtcurve-1.9.0-r1/work/qtcurve-1.9.0/gtk2/style/drawing.cpp:1552 #11 0x7ffe50650d44 in QtCurve::drawBox(GtkStyle*, GdkWindow*, GtkStateType, GtkShadowType, GdkRectangle*, GtkWidget*, char const*, int, int, int, int, bool) (style=style@entry=0x1362b2f00 [QtCurveStyle], window=window@entry=0x1377f5cf0 [GdkPixmap], state=state@entry=GTK_STATE_SELECTED, shadow=shadow@entry=GTK_SHADOW_OUT, area=area@entry=0x0, widget=widget@entry=0x1363319b0 [GtkProgressBar], _detail=_detail@entry=0x7ffec0299190 "bar", x=x@entry=0, y=, y@entry=0, width=, height=, btnDown=) at /var/tmp/portage/x11-themes/qtcurve-1.9.0-r1/work/qtcurve-1.9.0/gtk2/style/qtcurve.cpp:1505 #12 0x7ffe50651f2c in QtCurve::gtkDrawBox(GtkStyle*, GdkWindow*, GtkStateType, GtkShadowType, GdkRectangle*, GtkWidget*, char const*, int, int, int, int) (style=0x1362b2f00 [QtCurveStyle], window=0x1377f5cf0 [GdkPixmap], state=, shadow=, area=0x0, widget=0x1363319b0 [GtkProgressBar], detail=0x7ffec0299190 "bar", x=, y=0, width=, height=) at /var/tmp/portage/x11-themes/qtcurve-1.9.0-r1/work/qtcurve-1.9.0/gtk2/style/qtcurve.cpp:1585 #13 0x7ffe90442144 in IA__gtk_paint_box (style=0x1362b2f00 [QtCurveStyle], window=0x1377f5cf0 [GdkPixmap], state_type=, shadow_type=, area=0x0, widget=0x1363319b0 [GtkProgressBar], detail=0x7ffec0299190 "bar", x=, y=0, width=107, height=23) at /var/tmp/portage/x11-libs/gtk+-2.24.32-r1/work/gtk+-2.24.32/gtk/gtkstyle.c:6207 #14 0x7ffec026fe50 in QGtk2Painter::paintBox(_GtkWidget*, char const*, QRect const&, GtkStateType, GtkShadowType, _GtkStyle*, QString const&) (this=0x7ffec02b0d78 , gtkWidget=0x1363319b0 [GtkProgressBar], part=0x7ffec0299190 "bar", paintRect=..., state=, shadow=, style=0x1362b2f00 [QtCurveStyle], pmKey=...) at /usr/include/qt5/QtCore/qrect.h:269 #15 0x7ffec028b93c in QGtkStyle::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const (this=, element=, option=, painter=, widget=) at qgtkstyle.cpp:3504 #16 0x7fffbce3b648 in QCommonStyle::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const (this=0x1360fe230, element=, opt=, p=0x7fffc0004fe8, widget=0x137819a90) at /var/tmp/portage/dev-qt/qtwidgets-5.14.2/work/qtbase-everywhere-src-5.14.2/src/widgets/styles/qcommonstyle.cpp:1515 #17 0x7ffec028ba44 in QGtkStyle::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const (this=0x1360fe230, element=, option=0x7fffc0005000, painter=0x7fffc0004fe8, widget=0x137819a90) at qgtkstyle.cpp:3510 #1
[kwin] [Bug 400987] Wayland application focus extremely inconsistent
https://bugs.kde.org/show_bug.cgi?id=400987 --- Comment #52 from Brian --- (In reply to Kyle Tirak from comment #51) > (In reply to Brian from comment #41) > > (In reply to Roman Gilg from comment #39) > > > I'm not able to reproduce it. Is there a way to reproduce it > > > consistently? I > > > tried method in comment 13, but didn't fail for me. > > > > Been doing testing and i think what might be happening is the window below > > is randomly getting input such as mouse clicks (the desktop?), leading to > > kwin mistakenly thinking you clicked something else, and therefor stopping > > you from inputing text. Meanwhile kwin renders the last thing the window was > > showing, leading to the still content seen. > > > > This surface glitching seems to happen most often with Firefox in Xwayland. > > In my experience when it happens, dialogs will open but not show, but if you > > use kwin's present window hotcorner you can see that it did infact open and > > that it's artifacted and invisble. > > > > Interestingly i just had the surface glitching happen randomly when > > downloading a file. The dialog opened, but it was artifacted and almost > > fully invisible, yet i could still click on it's titlebar. > > > > As a matter of fact, i know extremely similar behavior to this can be > > reproduced easily if you open Firefox with it's Wayland backend enabled. You > > will not only see tons of artfacting and misplaced UI elements should you > > move it or interact with it, but you will also find that some of your clicks > > are not registered and that windows below it are clipped up through it, > > giving you a mangled mess. > > This sounds similar to the issue I've seen for a long time. The easiest way > to reproduce this behavior for me is to: > > 1. Open one XWayland application (e.g. Thunderbird) and minimize it > 2. Open another XWayland application (e.g. VLC) > 3. In the second XWayland application, hammer on a menu bar option (e.g. in > VLC you could continuously click on the Help menu to activate and deactivate > the menu). You should be able to see invisible activations of the menu. > > This only happens for me when I have an XWayland window minimized. It also > seems to stop happening with "Keep Window Thumbnails" set to "Always". > > Note that if needing to turn off the "Always" setting to reproduce this, the > minimized XWayland window needs to be minimized *after* changing the setting > off of "Always". I have suspicion it's not just XWayland applications affected. But yes, the main problem is XWayland ones. -- 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 --- Comment #347 from bugreporte...@gmail.com --- On Sun, Oct 18, 2020 at 9:30 AM wrote: > https://bugs.kde.org/show_bug.cgi?id=356225 > > --- Comment #346 from m...@eisgr.com --- > (In reply to Tiago from comment #345) > > It's sad to see such a remarkable project such as KDE decaying this way. > > Oddly enough, I've had the opposite experience. > I agree. I see KDE getting better and better. I've been impressed with the progress, particularly new features and bug fixes, in 2020. I had been frustrated with this bug, but I picked a work-around (created a > script which resets my KDE environment as I want). > Could you share your script? > But this bug made me do the unthinkable: switch to >> > Gnome. And five years later I'm still using Gnome because, astoninshly, >> this >> > bug remains open... >> > The bug may remain open, but I don't think that's an indication that it will definitely affect you.I see this bug on one system from time to time, but it is rare and it goes away on its own. I think logging out and back in causes it to go away. My other KDE systems do not exhibit this bug. Maybe it won't affect you, Tiago? I don't mean to diminish the importance of this bug. I would like to see it fixed too. But it would take a lot more than this bug to cause me to leave KDE, especially with the current rate of improvements and bug fixes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427949] New: Wayland session crash/ends as soon as i hover mouse over bottom panel.
https://bugs.kde.org/show_bug.cgi?id=427949 Bug ID: 427949 Summary: Wayland session crash/ends as soon as i hover mouse over bottom panel. Product: kwin Version: git master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jodr...@live.com Target Milestone: --- SUMMARY Having updated to the latest packages and logging into a wayland session, as soon as i hovered the mouse over the bottom panel the whole session would end/crash and throw me back to sddm logging screen. I try logging in and out, rebooted same result. Running dmesg i could see this : kwin_wayland[12639]: segfault at 10 ip 562ae4ec9c9f sp 78d10560 error 4 in kwin_wayland[562ae4eac000+24000] [ 1108.742773] Code: 48 89 c3 48 8d 05 c1 98 ff ff 48 89 43 08 48 89 df c7 43 04 01 00 00 00 c7 03 01 00 00 00 e8 a8 3d fe ff 31 ff e8 41 3f fe ff <48> 8b 50 10 48 89 45 20 48 8b 42 10 48 85 c0 0f 84 5c 04 00 00 48 Checking coredumbctl shows entries for kwin_wayland. I manged to get this backtrace : #0 0x562ae4ec9c9f in KWin::PipeWireCore::init (this=0x562ae71cc2e0) at /usr/src/debug/kwin5-5.20.80git.20201016T170339~7eccfdc52-ku.137.1.x86_64/screencast/pipewirecore.cpp:102 #1 KWin::PipeWireCore::self () at /usr/src/debug/kwin5-5.20.80git.20201016T170339~7eccfdc52-ku.137.1.x86_64/screencast/pipewirecore.cpp:102 #2 KWin::PipeWireStream::init (this=0x562ae71ea600) at /usr/src/debug/kwin5-5.20.80git.20201016T170339~7eccfdc52-ku.137.1.x86_64/screencast/pipewirestream.cpp:194 Backtrace stopped: Cannot access memory at address 0x78d105e8 The only package i had at the time ralated to pipewire on my system was libpipewire-0_3-0. After installing pipewire and its dependecies i don't get the session crash anymore. STEPS TO REPRODUCE 1. Only have libpipewire-0_3-0 installed in your system. 2. Login into a wayland session. 3. Hover the mouse over the bottom panel. OBSERVED RESULT The desktop will freeze for a couple of seconds then you'll be throw back to sddm loggin screen. EXPECTED RESULT No session crash or frozen desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: opensuse Tumbleweed KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION I am using the unstable kde repositories. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> changed: What|Removed |Added CC||05e42f84-6281-4bcb-8159-d43 ||2d71ae...@anonaddy.me --- Comment #6 from Jacob <05e42f84-6281-4bcb-8159-d432d71ae...@anonaddy.me> --- Baloo indexing is not the only thing: the names of the folders within vaults can be seen at /home/user/.local/share/dolphin/view_properties/local/home/user/..., when the vault is closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427527] [Wayland] Switching tabs in Kickoff is sometimes laggy
https://bugs.kde.org/show_bug.cgi?id=427527 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427948] New: wayland session doesn't start on nvidia
https://bugs.kde.org/show_bug.cgi?id=427948 Bug ID: 427948 Summary: wayland session doesn't start on nvidia Product: kwin Version: 5.20.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: mutasik170...@gmail.com Target Milestone: --- Created attachment 132546 --> https://bugs.kde.org/attachment.cgi?id=132546&action=edit wayland session log SUMMARY STEPS TO REPRODUCE launch wayland on nvidia OBSERVED RESULT only cursor on back screen EXPECTED RESULT start system SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon 5.20 User Edition KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 Processors: Intel Pentium G4600 Memory: 7.7 GiB Graphics Processor: nvidia GTX 1050 Ti ADDITIONAL INFORMATION cat /sys/module/nvidia_drm/parameters/modeset Y echo $KWIN_DRM_USE_EGL_STREAMS 1 -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 427670] Error at start and crash when conducting time series
https://bugs.kde.org/show_bug.cgi?id=427670 --- Comment #2 from Jake --- Hi, Many thanks for your help. I have tried the latest release. However, it now crashes and it does not respond. I receive the exact same error message. However, I cannot even interact with it. Many thanks in advance. With regards, Jake On Wed, Oct 14, 2020 at 11:31 PM Thomas Friedrichsmeier < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=427670 > > Thomas Friedrichsmeier > changed: > >What|Removed |Added > > > CC| > |thomas.friedrichsmeier@ruhr >||-uni-bochum.de > > --- Comment #1 from Thomas Friedrichsmeier < > thomas.friedrichsme...@ruhr-uni-bochum.de> --- > Thanks for reporting. The real error will be the one you get immediately: > The R > engine does not start. The subsequent crash is not pretty, but likely just > a > symptom of the former: As the message says, hardly anything is expected to > work > in this case. > > So about the first problem: > - What R version do you have installed (you are aware that R needs to be > installed, separately)? > - If the answer is R 4.0.x, this is not expected to work with RKWard > 0.7.1b. > Please try using this RKWard image, instead (a preview of 0.7.2, which is > due > to be released, officially, in a few days): > > https://binary-factory.kde.org/job/RKWard_Nightly_macos/lastSuccessfulBuild/artifact/rkward-master-489-macos-64-clang.dmg > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427947] Xubuntu 20.04 multimedia control is buggy and not working as intended.
https://bugs.kde.org/show_bug.cgi?id=427947 voojj3...@gmail.com changed: What|Removed |Added Component|common |android-application -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427947] New: Xubuntu 20.04 multimedia control is buggy and not working as intended.
https://bugs.kde.org/show_bug.cgi?id=427947 Bug ID: 427947 Summary: Xubuntu 20.04 multimedia control is buggy and not working as intended. Product: kdeconnect Version: 1.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: voojj3...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. connect with kdeconnect-config (kdeconnect-app is still broken yet in 20.04) 2. play music with jack audio + pulseaudio. 3. Cant't change music audio volume, I can change the output device volume, but not the application volume. 4. Idk if this is something with jack or not, I don't think so because its using pulseaudio module jack sink and out. OBSERVED RESULT Can't change application audio volume, also after stopping song it disappear can't hit play again it says no source detected. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Never macOS: Never Linux/KDE Plasma: Xubuntu ^-^ (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.
[kdeplasma-addons] [Bug 358124] Network applet stops updating
https://bugs.kde.org/show_bug.cgi?id=358124 --- Comment #5 from Bzzz --- Can't tell, as I'm still using plasmashell --version plasmashell 5.12.9 with Kubuntu 18.04.5. Maybe someone else can check on a newer install. I will probably update early December when reaching 256 days of uptime... My current Netspeed Widget does not have an update issue, but I'd still like to see newly added interfaces in the task bar that also vanish when physically removed. Maybe the System Monitor thing does that already. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427946] New: Uninstalled Plasma widget is not immediately removed from system tray settings
https://bugs.kde.org/show_bug.cgi?id=427946 Bug ID: 427946 Summary: Uninstalled Plasma widget is not immediately removed from system tray settings Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. right-click on desktop, choose "Add widgets..." 2. click on "Get new widgets" > "Download new Plasma widgets" 3. search and install Redshift Control or Weather Widget Plasma widgets https://store.kde.org/p/998916/ https://store.kde.org/p/998917/ 4. open system tray settings, click on "Entries" section: the just installed widget is present as expected 5. uninstall the just installed widget via Widget Explorer 6. reopen system tray settings, "Entries" section: uninstalled widget unexpectedly is still present 7. restart Plasma with "plasmashell --replace" 8. reopen system tray settings, "Entries" section: uninstalled widget is no longer present EXPECTED RESULT Plasma widget should immediately be removed from system tray settings after the step 5 SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition 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.
[plasmashell] [Bug 427945] New: Plasma Crashes when plugging in 8tb external hard drive
https://bugs.kde.org/show_bug.cgi?id=427945 Bug ID: 427945 Summary: Plasma Crashes when plugging in 8tb external hard drive Product: plasmashell Version: 5.20.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dashonww...@pm.me CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.0) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.8.14-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Ever since the update to 5.20 the first time I plug in one of my 8 tb external hard drives. It causes plasmashell to crash. Crashes do not happen if removed and replugged in. I have to reboot the system and then plug in the drive in order to retrigger the crash. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 2020] [New LWP 2046] [New LWP 2146] [New LWP 2152] [New LWP 2153] [New LWP 2154] [New LWP 2155] [New LWP 2178] [New LWP 2236] [New LWP 2706] [New LWP 2926] [New LWP 2927] [New LWP 2928] [New LWP 2929] [New LWP 2930] [New LWP 2931] [New LWP 2932] [New LWP 2933] [New LWP 21099] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f4b97cefe7f in __GI___poll (fds=0x7ffe9b865870, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f4b95bef840 (LWP 2005))] Thread 20 (Thread 0x7f4b5d4fa640 (LWP 21099)): #0 0x7f4b97cefe7f in __GI___poll (fds=0x7f4b48002450, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4b787e8542 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7f4b787d9f89 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7f4b787da60f in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f4b787da6c0 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f4b787e8619 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f4b7877f5e8 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f4b97244eb1 in start_thread (arg=0x7f4b5d4fa640) at pthread_create.c:463 #8 0x7f4b97cfaccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f4b26ffd640 (LWP 2933)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55eec9c25b50) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55eec9c25b00, cond=0x55eec9c25b28) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55eec9c25b28, mutex=0x55eec9c25b00) at pthread_cond_wait.c:638 #3 0x7f4b9808192b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #4 0x7f4b793f9d73 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f4b793fa0a9 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f4b793f7fd2 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f4b793f8ac0 in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f4b9807b911 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f4b97244eb1 in start_thread (arg=0x7f4b26ffd640) at pthread_create.c:463 #10 0x7f4b97cfaccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f4b277fe640 (LWP 2932)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55eec9c25b50) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55eec9c25b00, cond=0x55eec9c25b28) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55eec9c25b28, mutex=0x55eec9c25b00) at pthread_cond_wait.c:638 #3 0x7f4b9808192b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #4 0x7f4b793f9d73 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f4b793fa0a9 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f4b793f7fd2 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f4b793fa11e in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f4b793f7fd2 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f4b793fa11e in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f4b793f7fd2 in ThreadWeaver::
[frameworks-kio] [Bug 427944] New: Positioning of the dialog used to retry/skip/cancel file copy is inconsistent
https://bugs.kde.org/show_bug.cgi?id=427944 Bug ID: 427944 Summary: Positioning of the dialog used to retry/skip/cancel file copy is inconsistent Product: frameworks-kio Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 132544 --> https://bugs.kde.org/attachment.cgi?id=132544&action=edit screen recording SUMMARY Sometimes the dialog used to retry/skip/cancel file copy is centered on the screen, sometimes it shows up in the upper left corner. Watch the attached screen recording please. EXPECTED RESULT dialog should always be centered on the screen SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition 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-kio] [Bug 427943] New: Dialog to retry/skip/cancel file copy does not fit to screen if its text is too long
https://bugs.kde.org/show_bug.cgi?id=427943 Bug ID: 427943 Summary: Dialog to retry/skip/cancel file copy does not fit to screen if its text is too long Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 132543 --> https://bugs.kde.org/attachment.cgi?id=132543&action=edit screen recording SUMMARY Watch the attached screen recording please. EXPECTED RESULT dialog should always fit to screen SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition 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.
[kontact] [Bug 425931] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=425931 --- Comment #10 from john4deidre2...@xtra.co.nz --- Created attachment 132542 --> https://bugs.kde.org/attachment.cgi?id=132542&action=edit New crash information added by DrKonqi kontact (5.15.2 (20.08.2)) using Qt 5.15.1 - What I was doing when the application crashed: i was just starting kontact from menubar. this is when it crashed -- Backtrace (Reduced): #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append (this=0x100, t=@0x7ffe4de3d330: 0x559dc09f5880) at ../../include/QtCore/../../src/corelib/tools/qlist.h:622 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426048] Changing a clip's speed causes a crash
https://bugs.kde.org/show_bug.cgi?id=426048 --- Comment #6 from h.k.gh...@gmail.com --- (In reply to Vincent PINON from comment #5) > mlt commit 9499802f on 09.05 adresses cases of low speed crashing. > can you test with 20.08.2 appimage? I see a 20.08.1 appimage (i.e. kdenlive-20.08.1-x86_64.appimage), but not a 20.08.2. I'm looking in https://files.kde.org/kdenlive/release Is there a typo in your message, is the image actually missing, or am I looking in the wrong place?... -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 427921] Text input is unusable
https://bugs.kde.org/show_bug.cgi?id=427921 --- Comment #2 from alexmatee...@yahoo.com --- Are you sure this is a duplicate of a bug fixed in Plasma 5.20 and Frameworks 5.75? I can reproduce it while using precisely that? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 427921] Text input is unusable
https://bugs.kde.org/show_bug.cgi?id=427921 alexmatee...@yahoo.com changed: What|Removed |Added Summary|Text input us unusable |Text input is unusable -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427877] Tk apps fail to start with unknown color name "BACKGROUND" after upgrading to Plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=427877 Gabriel C changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427877] Tk apps fail to start with unknown color name "BACKGROUND" after upgrading to Plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=427877 Gabriel C changed: What|Removed |Added CC||nix.or@gmail.com --- Comment #1 from Gabriel C --- Seems to be fixed by reverting https://github.com/KDE/plasma-workspace/commit/d360e3dcb608bd96d674bbae597b7938334972fd. See commit: https://github.com/KDE/plasma-workspace/commit/f0764d87fe5275a123cdf6dca1ab3d0399c97578 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #21 from David Hurka --- > Can anyone attach a PDF with hyperlinks to different sections of > the document that I can test with? What happened to your LM555? ;) > I think I remember Kezi complaining about the ViewPort setting location > history > events itself, too. Wouldn't it make more sense to make the code that > triggers > the location change request explicitly that the old location be recorded? > [...] > recordLocation(here); That sounds like the natural solution to me. Then scrolling doesn’t need to know *why* it scrolls right now. Besides that, I can’t reproduce the problem as described (as I understand it). If I enable smooth scrolling, there is no history updated when I press e. g. Arrow Down. Instead, the history is updated when I press Back and Forward, so I circle between the last two viewports only. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 427741] No way to access to user account for EDF.fr
https://bugs.kde.org/show_bug.cgi?id=427741 --- Comment #3 from louicellier...@wanadoo.fr --- It seems also that defining many diffenrent user agents leads Falkon to crash. In this case, the only solution is to reboot as restarting Falkon is impossible. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427942] Kdeconnect is slow to pause and resume media
https://bugs.kde.org/show_bug.cgi?id=427942 Nicolas Fella changed: What|Removed |Added Component|plasmamobile-application|common Assignee|nicolas.fe...@gmx.de|albertv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 427741] No way to access to user account for EDF.fr
https://bugs.kde.org/show_bug.cgi?id=427741 louicellier...@wanadoo.fr changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #2 from louicellier...@wanadoo.fr --- Changing the user agent is not a solution. Defining a user agent that works for edf.fr implies that you cannot access some other sites that were accessible with a global user agent. It seems that there is something wrong with the management of different user agents for specific sites. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 427941] The gksu package is no longer included in Ubuntu
https://bugs.kde.org/show_bug.cgi?id=427941 --- Comment #3 from Doug Baden --- Can you send me the calling configuration for Smb4k? This may be an Elementary OS configuration error. The configuration error I found was in /use/share/accessories/smb4k.desktop On Sun, Oct 18, 2020 at 5:10 PM Doug Baden wrote: > Yes. I was looking at the configuration and found this. I can talk more > later tonight (USA EDT). > > On Sun, Oct 18, 2020 at 4:58 PM Alexander Reinholdt < > bugzilla_nore...@kde.org> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=427941 >> >> --- Comment #1 from Alexander Reinholdt >> --- >> Are you using Smb4K 2.1.0 from the Ubuntu repository? >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427942] Kdeconnect is slow to pause and resume media
https://bugs.kde.org/show_bug.cgi?id=427942 voncl...@gmail.com changed: What|Removed |Added CC||voncl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427942] New: Kdeconnect is slow to pause and resume media
https://bugs.kde.org/show_bug.cgi?id=427942 Bug ID: 427942 Summary: Kdeconnect is slow to pause and resume media Product: kdeconnect Version: 1.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmamobile-application Assignee: nicolas.fe...@gmx.de Reporter: voncl...@gmail.com Target Milestone: --- SUMMARY Upon using kdeconnect I may receive a phonecall and the media will pause "sometimes" on time, other times the phonecall could have ended and then the media will pause, or the media will pause about a minute into the phonecall. Also the media will take a about 30 seconds to a minute to resume. STEPS TO REPRODUCE 1. Have VLC play 2. Make or receive phone call 3. See what result happens OBSERVED RESULT kdeconnect is slow to receive pause and resume commands. EXPECTED RESULT Pause media ontime and resume when phonecall is over SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION I have a samsung galaxy note 9 When I use the 1.4 version the pause resume function is flawless (however sms messages fail to load)...I am currently using the version: https://invent.kde.org/network/kdeconnect-kde/commit/4266834052983a788bb12a579da18fd35832d763 This version: https://download.kde.org/stable/kdeconnect/1.4/kdeconnect-kde-1.4.tar.xz Works fine EXCEPT for the sms window -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427028] Phonecalls not pausing VLC during phonecall
https://bugs.kde.org/show_bug.cgi?id=427028 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #5 from Nicolas Fella --- After some debugging we found that the information that the call is finished is sent with some large delay (30s). Possiblity due to the Android system sending it with delay, but hard to tell without talking a closer look at the Android app -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427630] KDE connect indicatior crashes when using, the phone as a pointer
https://bugs.kde.org/show_bug.cgi?id=427630 Nicolas Fella changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Nicolas Fella --- Thanks for confirming, it should be fixed in KDE Neon by now. *** This bug has been marked as a duplicate of bug 418076 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418076] KDE Connect Slideshow Remote Pointer bug
https://bugs.kde.org/show_bug.cgi?id=418076 Nicolas Fella changed: What|Removed |Added CC||yerimy...@gmail.com --- Comment #3 from Nicolas Fella --- *** Bug 427630 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 427941] The gksu package is no longer included in Ubuntu
https://bugs.kde.org/show_bug.cgi?id=427941 --- Comment #2 from Doug Baden --- Yes. I was looking at the configuration and found this. I can talk more later tonight (USA EDT). On Sun, Oct 18, 2020 at 4:58 PM Alexander Reinholdt < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=427941 > > --- Comment #1 from Alexander Reinholdt > --- > Are you using Smb4K 2.1.0 from the Ubuntu repository? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 427941] The gksu package is no longer included in Ubuntu
https://bugs.kde.org/show_bug.cgi?id=427941 --- Comment #1 from Alexander Reinholdt --- Are you using Smb4K 2.1.0 from the Ubuntu repository? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 427741] No way to access to user account for EDF.fr
https://bugs.kde.org/show_bug.cgi?id=427741 louicellier...@wanadoo.fr changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from louicellier...@wanadoo.fr --- Need a change of user agent. Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/602.3.12 (KHTML, like Gecko) Version/10.0.2 Safari/602.3.12 for global. Incompatible with facebook.com, so a diffrent user agent has to be defined : Safari/602.3.12Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 427918] Scrolling is broken when scrollbar is hidden
https://bugs.kde.org/show_bug.cgi?id=427918 Kurt Hindenburg changed: What|Removed |Added CC||gcarnei...@hotmail.com --- Comment #1 from Kurt Hindenburg --- Gustavo, can you look at this please? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 427941] New: The gksu package is no longer included in Ubuntu
https://bugs.kde.org/show_bug.cgi?id=427941 Bug ID: 427941 Summary: The gksu package is no longer included in Ubuntu Product: Smb4k Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: alexander.reinho...@kdemail.net Reporter: dougba...@gmail.com Target Milestone: --- Created attachment 132539 --> https://bugs.kde.org/attachment.cgi?id=132539&action=edit A screenshot of the error SUMMARY Smb4k relies on gksu to get the network domains and this package is no longer in the general release of Umbutu 18.04. Perhaps use pkexec? STEPS TO REPRODUCE 1. Start program 2. 3. OBSERVED RESULT Error pops up for a moment "Error retrieving the list of available domains failed:" EXPECTED RESULT Listing of the domains in the window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Elementary OS 5.1.7/Ubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427630] KDE connect indicatior crashes when using, the phone as a pointer
https://bugs.kde.org/show_bug.cgi?id=427630 --- Comment #2 from Ezike Ebuka --- Yeah that fixes it thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427725] Undefined color: "WINDOW_FOREGROUND" breaks Emacs GUI
https://bugs.kde.org/show_bug.cgi?id=427725 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|CONFIRMED Component|general |Global Theme packages CC||gjditchfi...@acm.org, ||plasma-b...@kde.org Product|kwin|plasmashell Ever confirmed|0 |1 Version|unspecified |5.20.0 Summary|Kwin maybe crashes Emacs|Undefined color: |gui |"WINDOW_FOREGROUND" breaks ||Emacs GUI Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Target Milestone|--- |1.0 --- Comment #2 from gjditchfi...@acm.org --- I worked around this problem by deleting directory /usr/share/kdisplay/app-defaults. That directory comes from package plasma-workspace. I am reassigning the bug to product "plasmashell" because I think that's a better match than kwin, but there may be a better choice. I ran into this problem on a fresh install of Neon 20.04. An upgrade in place from 18.04 did not have this problem. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 427063] Can't add Google account in system settings on last stable KDE Neon
https://bugs.kde.org/show_bug.cgi?id=427063 --- Comment #3 from Sandro --- Going further down this rabbit hole, I found there are signond segfaults in dmemsg that correlate with whenever I click on "Add new Account" in Online Accounts section of systemsettings. It points to an error in libQt5Core.so.5.15.0, and looking into that further (I didn't feel like setting up to stacktrace the error on my system directly), it seems it's an error with qt 5.15 that OpenSuse have fixed in recent months to address this. Should this be re-categorized as a Kde Neon bug to address an upstream problem? For reference: https://bugzilla.opensuse.org/show_bug.cgi?id=1172904 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 427787] Support new faccessat2 linux syscall (439)
https://bugs.kde.org/show_bug.cgi?id=427787 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Mark Wielaard --- commit fe4b349df3d5edc1c849e9890cbc6b191386a03c Author: Mark Wielaard Date: Fri Oct 16 02:55:06 2020 +0200 Support new faccessat2 linux syscall (439) faccessat2 is a new syscall in linux 5.8 and will be used by glibc 2.33. faccessat2 is simply faccessat with a new flag argument. It has a common number across all linux arches. https://bugs.kde.org/427787 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #20 from Keziolio --- The old code was updating history inside the request visible pixmap function, those two things are semantically not the same, they were put in the same place for reasons unknown to me, my new implementation just exposed this original bad design decision -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #19 from Albert Astals Cid --- (In reply to Oliver Sander from comment #17) > I think I remember Kezi complaining about the ViewPort setting location > history events itself, too. Wouldn't it make more sense to make the code > that triggers the location change request explicitly that the old location > be recorded? Something like > > // an internal link has been clicked > recordLocation(here); > scrollTo(LinkDestination) He complained because he broke everything and it's easier to complain that the old code is wrong than to accept that your new code is not as good as you think it is. Let's be honest, the old code was perfectly working, going back and forth in history would animate the viewport (i still don't understand why we needed a new animation method while we had an existing one in place) and it did this animation without destroying history, so if the new code even with him introducing a new setViewportWithHistory method is not working, shows how bad the new code is. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #18 from Nate Graham --- Yeah that's what would make sense to me. Need to see if it's possible given the existing implementation. A targeted bugfix will probably be needed for 1.11.3 if we can make it in time. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 414502] (Un)plugging the AC adapter while screen is off always results in 100% brightness
https://bugs.kde.org/show_bug.cgi?id=414502 --- Comment #1 from cantabile --- This problem is gone since I updated to Plasma 5.20, Linux 5.8.14, etc. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 427063] Can't add Google account in system settings on last stable KDE Neon
https://bugs.kde.org/show_bug.cgi?id=427063 Sandro changed: What|Removed |Added CC||liq...@liquidonline.ca --- Comment #2 from Sandro --- I believe I have this problem too. Visible behaviour is exactly the same as in video uploaded in Description. Adding more detail here to help with diagnose/fix: Steps to reproduce: 1. Open System Settings, go to Online accounts 2. Press "Add new Account" button 3. Select Google OBSERVED: * In GUI, the screen goes back to "No accounts added" (If there are none prior), and "Add new Account" button again. A "Silent" fail. * When running systemsettings5 in terminal, error output at moment of clicking "Add New Account" is as follows: "google" Looking for plugin "" Starting auth session with "oauth2" Error storing identity: "Message recipient disconnected from message bus without replying" 5 "org.freedesktop.DBus.Error.NoReply" "Message recipient disconnected from message bus without replying" 5 "org.freedesktop.DBus.Error.NoReply" "Message recipient disconnected from message bus without replying" Error: "Message recipient disconnected from message bus without replying" EXPECTED * View appears for entering Google account credentials This occurs on KDE Neon 20.04/5.20.0 In my case, I can confirm that kio-gdrive, kaccounts-integration and kaccounts-providers all installed. I'm unaware if more is required for Google integration to work. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #17 from Oliver Sander --- I think I remember Kezi complaining about the ViewPort setting location history events itself, too. Wouldn't it make more sense to make the code that triggers the location change request explicitly that the old location be recorded? Something like // an internal link has been clicked recordLocation(here); scrollTo(LinkDestination) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427940] New: Allow running multiple program instances for the same user
https://bugs.kde.org/show_bug.cgi?id=427940 Bug ID: 427940 Summary: Allow running multiple program instances for the same user Product: kmail2 Version: 5.15.2 Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: markus.elfr...@web.de Target Milestone: --- STEPS TO REPRODUCE KMail can be started multiple times (even if one program instance is running already). OBSERVED RESULT The additional program start triggers the display of the application window from the running program according to the active software user. EXPECTED RESULT Further program versions may be applied for the use of several message folders in parallel. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427939] kscreen KCM: Widget layout cannot cope with very small screens
https://bugs.kde.org/show_bug.cgi?id=427939 --- Comment #1 from Frank Steinmetzger --- Created attachment 132538 --> https://bugs.kde.org/attachment.cgi?id=132538&action=edit Kscreen KCM at 1280×720 The Apply button is just about visible. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427939] New: kscreen KCM: Widget layout cannot cope with very small screens
https://bugs.kde.org/show_bug.cgi?id=427939 Bug ID: 427939 Summary: kscreen KCM: Widget layout cannot cope with very small screens Product: systemsettings Version: 5.20.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: war...@gmx.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 132537 --> https://bugs.kde.org/attachment.cgi?id=132537&action=edit KCM at 800×600 I was checking up on my old netbook which has a 1024×600 screen and attached an external screen to it. When trying to configure the screen, I discovered that I could not operate the KCM within System Settings with the mouse, because the Apply button was off the screen and unreachable with scrollbars. Admittedly, there are not many devices out there these days which have such a low pixel count, but that doesn’t change the problematic widget layout that cannot cope well with low vertical heights. But if there is any GUI that needs this capability, it would be the screen setup. In another case, I was setting my big 2560×1440 screen to quarter resolution (1280×720) to try out the performance of a demanding 3D game on Intel graphics. There, the Apply button was just about visible and no scrollbars shown. There might be users who need very big fonts because of bad eyesight, and those big letters would also push the widgets apart. EXPECTED RESULT The Apply button should be reachable with the mouse by way of the scrollbar. My setup: Current standard Arch packages Plasma 5.20.0 KDE Frameworks 5.75.0 Qt 5.15.1 The screenshots are a few days old, from Plasma 5.19, Frameworks 5.74.0. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427028] Phonecalls not pausing VLC during phonecall
https://bugs.kde.org/show_bug.cgi?id=427028 --- Comment #4 from voncl...@gmail.com --- Happens with youtube on firefox as well.. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 351822] [Thinkpad T440] [kubuntu] (False?) notification of the removal of power when the battery has finished charging or has reached the threshold
https://bugs.kde.org/show_bug.cgi?id=351822 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |UPSTREAM --- Comment #3 from Nate Graham --- In fact, this is likely to be a upower or kernel bug, not a powerdevil issue. There is one such issue right now: https://gitlab.freedesktop.org/upower/upower/-/issues/126 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416277] Apps search order broken after recent update.
https://bugs.kde.org/show_bug.cgi?id=416277 --- Comment #5 from Alexander Lohnau --- Can you please provide the LaunchCounts entry from the ~/.config/krunnerrc file? My suspicion is that the mentioned result is ranked higher, because you have already launched it. To verify this please delete the mentioned entry in the krunnerrc file and restart KRunner (kquitapp5 krunner;krunner&) and check if it then works as expected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427876] No shortcuts for pictures, videos and audio
https://bugs.kde.org/show_bug.cgi?id=427876 --- Comment #7 from Nate Graham --- Actually it doesn't depend. Bug triaging is something that more people are capable of doing compared to software engineering; therefore a person capable of doing software engineering is generally producing more value by doing software engineering than by doing bug triage. In fact that's the entire point of bug triage: to make sure that people capable of doing software engineering have to interact with the bug tracker as little as possible, so they can spend more of their time fixing bugs and writing features. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #16 from Nate Graham --- Can confirm the issue. It looks like the back/forward navigation calculates the prior position in the document based on scroll position and was not designed for animated scrolling. So the animated scrolling effect effectively populates the "location history" with multiple locations in the document when it should not. I'll see what I can do. Worst-case scenario, we revert animated scrolling when clicking on links until we can fix the root cause and support both. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 427938] Poor quality latex rendering
https://bugs.kde.org/show_bug.cgi?id=427938 Corentin Poupry changed: What|Removed |Added CC||pouprycorenti...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 427870] lmw, lswi and related PowerPC insns aren't allowed on ppc64le
https://bugs.kde.org/show_bug.cgi?id=427870 --- Comment #1 from Mark Wielaard --- Created attachment 132536 --> https://bugs.kde.org/attachment.cgi?id=132536&action=edit Don't compile ppc64be tests on ppc64le There is a similar issue with the ldst_multiple testcase. This patch works around it by not building (or running) both tests unless on ppc64be. -- You are receiving this mail because: You are watching all bug changes.
