[kwin] [Bug 414242] [Wayland] KWin Can't Change To Another Window While An VLC Instance Is At Fullscreen (Probably With Any Qt 5 Fullscreen App)
https://bugs.kde.org/show_bug.cgi?id=414242 --- Comment #4 from Alberto Díaz López --- (In reply to Vlad Zahorodnii from comment #3) > Not a problem at all. So if I understand you correctly, the issue seems to > be that the application that has just received the focus remains below the > vlc window, is that correct? Exactly. But as i said, it's really strange, when i was writing this description, i tried again and it was working fine. And now i'm trying again and it's working normally. I can't explain it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414242] [Wayland] KWin Can't Change To Another Window While An VLC Instance Is At Fullscreen (Probably With Any Qt 5 Fullscreen App)
https://bugs.kde.org/show_bug.cgi?id=414242 --- Comment #2 from Alberto Díaz López --- (In reply to Vlad Zahorodnii from comment #1) > Could you please clarify what you mean by "change window?" Sure, tabulate to other opened window. I'm not sure how to express it well, sorry. When you use Task Switcher (Alt + Tab). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414242] New: [Wayland] KWin Can't Change To Another Window While An VLC Instance Is At Fullscreen (Probably With Any Qt 5 Fullscreen App)
https://bugs.kde.org/show_bug.cgi?id=414242 Bug ID: 414242 Summary: [Wayland] KWin Can't Change To Another Window While An VLC Instance Is At Fullscreen (Probably With Any Qt 5 Fullscreen App) Product: kwin Version: 5.17.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tak...@disroot.org Target Milestone: --- SUMMARY KWin under Wayland session doesn't allow to change the window while having a fullscreen VLC instance. When you try it, the focus changes in fact, but the window at screen is still VLC. STEPS TO REPRODUCE 1. Launch VLC. 2. Open a video. 3. Enter in VLC fullscreen. 4. Try to change the window to another app. OBSERVED RESULT The preview works fine and the focus change in fact, but the window remains at VLC. Updated: Sometimes it works, i don't know the details to specify here, just when i was creating this bug, i checked again to assure and it's working fine. PS: It was bothering me too that with Firefox was happening the same before Plasma 5.17, but i suppose that KWin new fixes and changes solved that, cause i don't experiment those bugs (while i was watching a YouTube video for example at fullscreen), anymore. EXPECTED RESULT KWin should allow to change the window normally, as it does in X11 session. SOFTWARE/OS VERSIONS Linux: 5.3.11 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411935] Panel and widgets are transparent on Wayland after upgrade to frameworks 5.62
https://bugs.kde.org/show_bug.cgi?id=411935 Alberto Díaz López changed: What|Removed |Added CC||tak...@disroot.org --- Comment #8 from Alberto Díaz López --- Same issue here, just after updating to KDE Frameworks 5.62. Appreciated that 'only' happens when the background color is a light one, i just checked but i detected other behavior, the issue seems to appear when the window under the panel/widget isn't a KDE one, checked with Qtransmission, blur confirmed, checked with Firefox Developer Edition, blur confirmed, checked with Dolphin, blur doesn't appear, checked with Telegram Desktop, blur confirmed, checked with VLC, blur confirmed. So it has to be something about the non-KDE Software. Operating System: Arch Linux Kernel version: 5.2.14 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410154] Contextu Menu & Drag & Drop Actions Don't Work As It Expected Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410154 --- Comment #6 from Alberto Díaz López --- (In reply to Vlad Zahorodnii from comment #5) > (In reply to Martin Flöser from comment #3) > > Do I understand correctly that you want to drag and drop while this context > > menu is open? > It seems to me like this bug report is about the user actions popup menu not > being dismissed when the user clicks outside it. Exactly, you're totally right. > (In reply to Alberto Díaz López from comment #4) > > Nope, but that doesn't work either. I should opened two different bugs, > > sorry. One issue/bug is the one related with the context menu, another one > > is with the drag & drop event/action. > Please create a bug report per each bug. Tracking several bugs in one bug > report is difficult. Yes, sorry, i won't be doing this way again. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410407] [wayland] - Latte Dock 0.9 Is faulty auto-hiding with the cursor on it after a second
https://bugs.kde.org/show_bug.cgi?id=410407 --- Comment #2 from Alberto Díaz López --- Created attachment 121843 --> https://bugs.kde.org/attachment.cgi?id=121843&action=edit Latte Dock Layout File Added my daily usage Latte Dock layout file. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409877] [Wayland] Latte-Dock Is Not Working Well
https://bugs.kde.org/show_bug.cgi?id=409877 Alberto Díaz López changed: What|Removed |Added Summary|Latte-Dock Is Not Working |[Wayland] Latte-Dock Is Not |Well Under Wayland Session |Working Well -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410408] Latte Dock 0.9 Is Not Able To Let Interact With Mouse Left-Click With Two Or More Instances Of A Program Opened At The Dock (Under Wayland)
https://bugs.kde.org/show_bug.cgi?id=410408 --- Comment #2 from Alberto Díaz López --- (In reply to Michail Vourlakos from comment #1) > isnt the previews window shown in that case? Nope, it's like you can't interact with the icon with multiple open instances. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410408] New: Latte Dock 0.9 Is Not Able To Let Interact With Mouse Left-Click With Two Or More Instances Of A Program Opened At The Dock (Under Wayland)
https://bugs.kde.org/show_bug.cgi?id=410408 Bug ID: 410408 Summary: Latte Dock 0.9 Is Not Able To Let Interact With Mouse Left-Click With Two Or More Instances Of A Program Opened At The Dock (Under Wayland) Product: lattedock Version: 0.9.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Latte Dock 0.9 Is Not Able To Let Interact With Mouse Left-Click With Two Or More Instances Of A Program Opened At The Dock (Under Wayland) STEPS TO REPRODUCE 1. Login to Wayland session. 2. Open 2 instances of a program. 3. Click at the program icon at the dock. OBSERVED RESULT It doesn't do anything. EXPECTED RESULT It should let you choose what window/instance you want to change to, close, restore, or whatever. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.4/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410407] New: Latte Dock 0.9 Is Auto-Hiding With The Cursor On It After A Second Show It Cause Place The Cursor On It Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410407 Bug ID: 410407 Summary: Latte Dock 0.9 Is Auto-Hiding With The Cursor On It After A Second Show It Cause Place The Cursor On It Under Wayland Product: lattedock Version: 0.9.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Latte Dock 0.9 Is Auto-Hiding With The Cursor On It After A Second Show It Cause Place The Cursor On It Under Wayland STEPS TO REPRODUCE 1. Login to Wayland session. 2. Move the cursor to Latte Dock location, causing it appear. 3. Keep the cursor there. OBSERVED RESULT Latte Dock auto-hides after 1 second of no moving cursor. EXPECTED RESULT Latte Dock should keep in there while you have the cursor placed on it. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.4/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409877] Latte-Dock Is Not Working Well Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409877 Alberto Díaz López changed: What|Removed |Added Version|0.8.9 |0.9.0 --- Comment #4 from Alberto Díaz López --- Tested now 0.9 version. It's still the same status. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410361] New: Caps Lock Widget Don't Show Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410361 Bug ID: 410361 Summary: Caps Lock Widget Don't Show Under Wayland Product: kwin Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Caps Lock Widget Don't Show Under Wayland STEPS TO REPRODUCE 1. Login to Wayland session. 2. Go to a panel/Latte Dock where it should appear the widget. 3. Activate the caps lock. OBSERVED RESULT It doesn't appear caps lock the widget. EXPECTED RESULT It should appear the caps lock widget, just like under Xorg. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.3/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410271] New: Mouse Input Gets Blocked After Try A Drag & Drop Event Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410271 Bug ID: 410271 Summary: Mouse Input Gets Blocked After Try A Drag & Drop Event Under Wayland Product: kwin Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Mouse Input Gets Blocked After Try A Drag & Drop Event Under Wayland STEPS TO REPRODUCE 1. Login to a Wayland session. 2. Launch a program (e.g. Firefox). 3. Try to do a drag & drop to reorder any tab. 4. After figure out you can't drop the tab, press Escape key to leave it where it was initially. 5. Try to do click, right click, mousewheel scroll, etc. OBSERVED RESULT You can't do more than move the cursor, (tested with KDE Connect Virtual Remote Mouse & with a hardware/real mouse). EXPECTED RESULT Can use the mouse input (clicks, right clicks, mousewheel scroll) normally, like you can before trying to do the drag & drop event. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.3/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410154] Contextu Menu & Drag & Drop Actions Don't Work As It Expected Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410154 --- Comment #4 from Alberto Díaz López --- (In reply to Martin Flöser from comment #3) > Do I understand correctly that you want to drag and drop while this context > menu is open? Nope, but that doesn't work either. I should opened two different bugs, sorry. One issue/bug is the one related with the context menu, another one is with the drag & drop event/action. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410154] Contextu Menu & Drag & Drop Actions Don't Work As It Expected Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410154 --- Comment #2 from Alberto Díaz López --- Created attachment 121718 --> https://bugs.kde.org/attachment.cgi?id=121718&action=edit Plasma KWin Wayland Bugged Context Menu On Title Bar It happens on both GTK (Firefox Developer Edition) & on Qt (Dolphin, Telegram Desktop, etc). So i suppose it's not related with the framework/toolkit used by the software. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410162] New: KDE Connect Clipboard Sync Doesn't Work Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410162 Bug ID: 410162 Summary: KDE Connect Clipboard Sync Doesn't Work Under Wayland Product: kdeconnect Version: 1.3.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- SUMMARY KDE Connect Clipboard Sync Doesn't Work Under Wayland STEPS TO REPRODUCE 1. Login to Wayland session. 2. Copy something to the clipboard on the PC or at the smartphone. 3. Try to paste it at other device running KDE Connect. OBSERVED RESULT Clipboard doesn't sync under Wayland. EXPECTED RESULT Clipboard should sync under Wayland as it does under Xorg. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.2/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410157] New: Firefox's Scroll Works Not Uniformly Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410157 Bug ID: 410157 Summary: Firefox's Scroll Works Not Uniformly Under Wayland Product: kwin Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Firefox's Scroll Works Not Uniformly Under Wayland STEPS TO REPRODUCE 1. Launch Firefox. 2. Load a website with enough vertical content (to be able to scroll down). 3. Scroll down/up. OBSERVED RESULT Every 2-3 events, it does like a double scroll, only once the event, but it represents as it was twice. EXPECTED RESULT The scroll event should work properly like under Xorg, not being every 2-3 times it activates, like a double event. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.2/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410156] New: KDE Connect Does The Virtual Mouse Scrolldown Inverted Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410156 Bug ID: 410156 Summary: KDE Connect Does The Virtual Mouse Scrolldown Inverted Under Wayland Product: kdeconnect Version: 1.3.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- SUMMARY KDE Connect Does The Virtual Mouse Scrolldown Inverted Under Wayland STEPS TO REPRODUCE 1. Login to Wayland session. 2. Launch KDE Connect on Android. 3. Go to Remote Input. 4. Do the two fingers to scroll event. OBSERVED RESULT Under Wayland it requires to scroll down to go up, and scroll up to go down, while under Xorg its not inverted, scroll down go down and scroll up go up. EXPECTED RESULT Work fine as it does under Xorg. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.2/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 410155] New: KRunner Doesn't Show/Keep Command History Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410155 Bug ID: 410155 Summary: KRunner Doesn't Show/Keep Command History Under Wayland Product: krunner Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: tak...@disroot.org Target Milestone: --- SUMMARY KRunner Doesn't Show/Keep Command History Under Wayland STEPS TO REPRODUCE 1. Login to Wayland session. 2. Run some commands with KRunner. 3. Type again to KRunner the same string. OBSERVED RESULT No history observed at KRunner under Wayland, it doesn't suggest you possible options based on the previous commands you executed with KRunner. EXPECTED RESULT KRunner should preserve the command history as it does under Xorg session. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.2/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410154] New: Contextu Menu & Drag & Drop Actions Don't Work As It Expected Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410154 Bug ID: 410154 Summary: Contextu Menu & Drag & Drop Actions Don't Work As It Expected Under Wayland Product: kwin Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Contextual Menu & Drag & Drop Actions Don't Work As It Expected Under Wayland STEPS TO REPRODUCE 1. Login to Wayland session. 2. Open any GUI program. 3. Right click (to open context menu) on the title bar. 4. Do a drag & drop event/action. OBSERVED RESULT It's impossible in my personal case to quit that context menu after i invoke it, either doing right click at other place of the screen, left click, pressing Esc key usually solves the problem, but it's only a temporal fix. Regarding to the drag & drop action/event, you can't do the click to finish the event, i only can finish this the same way i have to the previous bug, pressing Esc key. EXPECTED RESULT Context menu & drag & drop should work flawlessly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.2/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409877] New: Latte-Dock Is Not Working Well Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409877 Bug ID: 409877 Summary: Latte-Dock Is Not Working Well Under Wayland Session Product: lattedock Version: 0.8.9 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Latte-Dock Is Not Working Well Under Wayland Session STEPS TO REPRODUCE 1. Login Wayland session. 2. Go to Latte-Dock. 3. Context menu > Add a Widget. 4. Select a widget (e.g. Global Menu). 5. Drag & drop to Latte-Dock. OBSERVED RESULT Latte-Dock doesn't show when you place the mouse cursor at the place where it should show (auto-hide enabled). This happens with an addition of a widget to Latte-Dock, as well as drag & drop an element (e.g. an image) to Latte-Dock to go Telegram (opened as a task), etc. EXPECTED RESULT Latte-Dock should show when you are drag & dropping an element to it. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.1/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409798] New: Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409798 Bug ID: 409798 Summary: Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session Product: Spectacle Version: 19.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: tak...@disroot.org CC: k...@david-redondo.de Target Milestone: --- SUMMARY Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session STEPS TO REPRODUCE 1. Login Wayland session. 2. Perform a screenshot/launch Spectacle. 3. Copy to clipboard the screenshot. 4. Paste it to everywhere. OBSERVED RESULT The image is corrupted, not working. EXPECTED RESULT The image paste it normally & flawlessly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.0/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409797] New: KWin Window Rules Doesn't Work Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409797 Bug ID: 409797 Summary: KWin Window Rules Doesn't Work Under Wayland Session Product: kwin Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tak...@disroot.org Target Milestone: --- SUMMARY KWin Window Rules Doesn't Work Under Wayland Session STEPS TO REPRODUCE 1. Login Wayland session. 2. Go System Settings > Window Management > Window Rules. 3. Create a Window Rule, e.g. No Title Bar. 4. Go the tab Appearance & Fixes. 5. Check the checkbox No title bar and frame. 6. Select at the dropdown menu Apply Initially. 7. Select No at the radio button. OBSERVED RESULT No Window Rules applied. Tested it with disabling Title Bar & Maximized vertically & horizontally windows (Size & Position). EXPECTED RESULT Window Rules apply correctly & flawlessly as it occurs on Xorg session. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.0/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409796] New: KMail Won't Start (Not Responding) Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409796 Bug ID: 409796 Summary: KMail Won't Start (Not Responding) Under Wayland Session Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: tak...@disroot.org Target Milestone: --- SUMMARY KMail Won't Start (Not Responding) Under Wayland Session STEPS TO REPRODUCE 1. Login Wayland session. 2. Launch/start KMail. OBSERVED RESULT KMail doesn't load properly (showing Not Responding) the accounts and other GUI elements, although the daemon at the background is receiving emails, as the notifications show them normally. EXPECTED RESULT KMail started & work normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.0/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 409795] New: KRunner Crashed At Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409795 Bug ID: 409795 Summary: KRunner Crashed At Wayland Session Product: kwayland-integration Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tak...@disroot.org Target Milestone: --- SUMMARY KRunner crashed after start Wayland session. STEPS TO REPRODUCE 1. Login at Wayland session. 2. Try to type some words on it. OBSERVED RESULT It crashed a few times, but i was able to relaunch it, after a few times (2-3) it wasn't aswering to the invoke by Alt + Spacebar. After a few time (about 15-20 minutes). EXPECTED RESULT Work flawlessly without crashs, or without have to be unable to use KRunner for a while. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.0/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 408302] GDB Plugin Not Working
https://bugs.kde.org/show_bug.cgi?id=408302 --- Comment #2 from Alberto Díaz López --- (In reply to Kåre Särs from comment #1) > Hi, > > Have you started the debugging? You have to start the application in the > debugger one time before you can start setting breakpoints. > > This is because starting the application/debugging loads the application > into GDB. Before that GDB is not even started. > > Setting of breakpoints before GDB is started is a bit of a problem. One > could start GDB and load the application when one tries to set a > break-point, but somebody would have to implement it... > > Please reply if my analysis/guess of the situation is right or wrong. I suppose your guess is right, yes. I didn't started the debugging yet. In fact, i'm searching how to start GDB debugging, but i can't find it. To test if that's the only reason or if there's more. Thank you for your quick and certain response. Bests ^^. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 408302] New: GDB Plugin Not Working
https://bugs.kde.org/show_bug.cgi?id=408302 Bug ID: 408302 Summary: GDB Plugin Not Working Product: kate Version: 19.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: tak...@disroot.org Target Milestone: --- Created attachment 120572 --> https://bugs.kde.org/attachment.cgi?id=120572&action=edit Kate GDB Plugin With The Buttons Disabled SUMMARY GDB plugin is not working. Initially when i activated the plugin, it's true that i hadn't installed GDB, but it activated with no message at all. I installed it later, closed & relaunched Kate, but nothing happens likewise. STEPS TO REPRODUCE 1. Open Kate. 2. Activate GDB plugin. 3. Try to create a breakpoint somewhere at the code, impossible. 4. The plugin's buttons are disabled and they won't enable no matter what. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.1.6/5.15.5 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407253] New: Similar Color Selection Tool moves selection and returns it to original place
https://bugs.kde.org/show_bug.cgi?id=407253 Bug ID: 407253 Summary: Similar Color Selection Tool moves selection and returns it to original place Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: barbanegra+b...@posteo.mx Target Milestone: --- SUMMARY When moving a selection created with Similar Color Selection Tool it is possible to move the selection, but after moving it, it returns it to the original selection place. STEPS TO REPRODUCE 1. Select Similar Color Selection Tool 2. Do a selection by color. 3. Hover over marching ants for cursor to change into move tool icon. 4. Move selection to a different place. 5. Let go of mouse. OBSERVED RESULT After letting go the selection it returns to its original place. EXPECTED RESULT Two possible and opposite results: 1. The should move to the new place. 2. It should not be possible to move the selection to not confuse the users. SOFTWARE/OS VERSIONS Parabola (rolling release based on Arch) Using Krita 4.2.0-pre-alpha Git 199cd9f -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403412] Small Desktop Icons are too wide
https://bugs.kde.org/show_bug.cgi?id=403412 --- Comment #8 from Alberto Zacchetti --- I tried the patch, but the difference is very little. I also believe that it would be a good idea to allow users to adjust the width of the grid a little more freely. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 406618] New: Desktop icons grid is too wide
https://bugs.kde.org/show_bug.cgi?id=406618 Bug ID: 406618 Summary: Desktop icons grid is too wide Product: frameworks-plasma Version: 5.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: alberto.zacche...@tiscali.it Target Milestone: --- Created attachment 119454 --> https://bugs.kde.org/attachment.cgi?id=119454&action=edit Desktop screenshot SUMMARY After the recent update to KDE Plasma 5.12.8, the grid for aligning desktop icons (in view folder mode) has cells too large regardless of the size of the icons. The result is that the desktop fills up unnecessarily even with a few icons. STEPS TO REPRODUCE 1. Set the view folder mode in desktop setting OBSERVED RESULT Icons grid with cells too wide. EXPECTED RESULT Icons grid with cells proportional to the size of the chosen icons. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 335180] Extend expriment brush with outline mode.
https://bugs.kde.org/show_bug.cgi?id=335180 alberto changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |barbanegra+b...@posteo.mx CC||barbanegra+b...@posteo.mx -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405865] New: Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=405865 Bug ID: 405865 Summary: Dolphin crash Product: dolphin Version: 18.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: albertocanet...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.12.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I have omited to copy a folder when the same folder name alredy exist The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd6831d6e40 (LWP 31211))] Thread 4 (Thread 0x7fd65480f700 (LWP 31219)): #0 0x7fd682a4fbf9 in __GI___poll (fds=0x7fd6500049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd674f19539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd674f1964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd67cba515b in QEventDispatcherGlib::processEvents (this=0x7fd65b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fd67cb4664a in QEventLoop::exec (this=this@entry=0x7fd65480eda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fd67c96e41a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fd67c96fbc2 in QThreadPrivate::start (arg=0x556a62920fc0) at thread/qthread_unix.cpp:361 #7 0x7fd6773016db in start_thread (arg=0x7fd65480f700) at pthread_create.c:463 #8 0x7fd682a5c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd6616fb700 (LWP 31218)): #0 0x7fd6773079f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x556a62577eb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x556a62577e68, cond=0x556a62577e90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x556a62577e90, mutex=0x556a62577e68) at pthread_cond_wait.c:655 #3 0x7fd662880dcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fd662880af7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fd6773016db in start_thread (arg=0x7fd6616fb700) at pthread_create.c:463 #6 0x7fd682a5c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd66a0bc700 (LWP 31215)): #0 0x7fd674f19546 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd674f1964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd67cba515b in QEventDispatcherGlib::processEvents (this=0x7fd65c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #3 0x7fd67cb4664a in QEventLoop::exec (this=this@entry=0x7fd66a0bbd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #4 0x7fd67c96e41a in QThread::exec (this=) at thread/qthread.cpp:531 #5 0x7fd67d013015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fd67c96fbc2 in QThreadPrivate::start (arg=0x7fd67d28ad80) at thread/qthread_unix.cpp:361 #7 0x7fd6773016db in start_thread (arg=0x7fd66a0bc700) at pthread_create.c:463 #8 0x7fd682a5c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd6831d6e40 (LWP 31211)): [KCrash Handler] #6 0x7fd68114f5e4 in KIO::CopyJobPrivate::copyNextFile (this=this@entry=0x556a62c82c60) at ./src/core/copyjob.cpp:1614 #7 0x7fd68115034a in KIO::CopyJobPrivate::createNextDir (this=this@entry=0x556a62c82c60) at ./src/core/copyjob.cpp:1274 #8 0x7fd681152dce in KIO::CopyJobPrivate::slotResultConflictCreatingDirs (this=this@entry=0x556a62c82c60, job=job@entry=0x556a62cc4ab0) at ./src/core/copyjob.cpp:1224 #9 0x7fd681155b2b in KIO::CopyJob::slotResult (this=0x556a62cc33d0, job=0x556a62cc4ab0) at ./src/core/copyjob.cpp:2166 #10 0x7fd67cb77f3f in QtPrivate::QSlotObjectBase::call (a=0x7ffd50ff2f00, r=0x556a62cc33d0, this=0x556a62cc36a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #11 QMetaObject::activate (sender=sender@entry=0x556a62cc4ab0, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd50ff2f00) at kernel/qobject.cpp:3759 #12 0x7fd67cb784f7 in QMetaObject::activate (sender=sender@entry=0x556a62cc4ab0, m=m@entry=0x7fd67e7de500 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd50ff2f00) at kernel/qobject.cpp:3631 #13 0x7fd67e58708c in KJob::result (this=this@entry=0x556a62cc4ab0, _t1=, _t1@entry=0x556a62cc4ab0, _t2=
[dragonplayer] [Bug 402898] Dragon Doesn't Reproduce Any Media
https://bugs.kde.org/show_bug.cgi?id=402898 --- Comment #4 from Alberto Díaz López --- (In reply to Neousr from comment #3) > If Gstreamer is the only backend it possibly lacks some plugins ( > gstreamer1.0-plugins-good and gstreamer1.0-plugins-ugly name can vary on > your distro) to be able to play the media. On the other hand Dragon can use > the VLC Phonon backend if you install the corresponding packages > (phonon4qt5-backend-vlc and libvlc) and prioritize the backend on the > settings menu. > > If you are fine with VLC at the moment let me now so i can close this report. Yeah, it is good to know, thanks. I am pretty fine with VLC, but i realized an attempt to use as much Qt only and later KDE software as i can/could, but looks like Dragon can not replace VLC in my case, at least not for now. For sure, thanks for your help and you can close this bug. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 402898] Dragon Doesn't Reproduce Any Media
https://bugs.kde.org/show_bug.cgi?id=402898 --- Comment #2 from Alberto Díaz López --- (In reply to Neousr from comment #1) > If you already tried other media audio/video and can confirm that the video > is indeed not corrupted. > > What backend are you using you can check under System Settings >Multimedia > > Audio and Video > Engine. > > You should at least have the phonon Gstreamer backend to be able to play > media. I already tried VLC, the media player i have been using the whole time, and yes, i can play everything on it, but nothing of that on Dragon. I just checked on backend at Audio & Video as you told me, indeed, i have GStreamer as the backend. I uninstalled Dragon a few time later i reported this bug, because i felt like it was a waste. Such a shame, it feels like a great potential for me, but it is real that being a software by KDE, i miss a whole bunch of options and settings to configure it, such as VLC has. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 402898] New: Dragon Doesn't Reproduce Any Media
https://bugs.kde.org/show_bug.cgi?id=402898 Bug ID: 402898 Summary: Dragon Doesn't Reproduce Any Media Product: dragonplayer Version: 18.12 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: sit...@kde.org Reporter: tak...@disroot.org CC: myr...@kde.org Target Milestone: --- Created attachment 117298 --> https://bugs.kde.org/attachment.cgi?id=117298&action=edit Main Window Where I Tried To Open A Media File (MKV) SUMMARY I can't reproduce any media with Dragon. STEPS TO REPRODUCE 1. Launch Dragon. 2. Open a file. OBSERVED RESULT There's no reproduction start. It doesn't even appear at the main panel, at the list. The list remains empty. Only is seen the name of the file at the bottom left edge, without extension. EXPECTED RESULT The reproduction should start, or at least, appear at a list. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: 4.20.0/5.14.4 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402492] New: Baloo crashed while using wine
https://bugs.kde.org/show_bug.cgi?id=402492 Bug ID: 402492 Summary: Baloo crashed while using wine Product: frameworks-baloo Version: 5.45.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: albertopozz...@alice.it Target Milestone: --- Application: baloo_file (5.45.0) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.19.7-lp150.6-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: Installing a game (bioshock) with wine (version 3.7-lp150.1.7) -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f84bb508100 (LWP 2821))] Thread 3 (Thread 0x7f44abfff700 (LWP 22129)): [KCrash Handler] #6 0x7f84b8e770e0 in raise () from /lib64/libc.so.6 #7 0x7f84b8e786c1 in abort () from /lib64/libc.so.6 #8 0x7f84b6c3b922 in mdb_assert_fail (env=0x555869a9bf50, expr_txt=expr_txt@entry=0x7f84b6c3d3af "rc == 0", func=func@entry=0x7f84b6c3dce8 <__func__.6935> "mdb_page_dirty", line=line@entry=2071, file=0x7f84b6c3d390 "mdb.c") at mdb.c:1487 #9 0x7f84b6c30e05 in mdb_page_dirty (txn=0x555869a9d360, mp=) at mdb.c:2071 #10 0x7f84b6c31fea in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f44abffdea8, mc=) at mdb.c:2252 #11 0x7f84b6c32259 in mdb_page_touch (mc=mc@entry=0x7f44abffe3e0) at mdb.c:2370 #12 0x7f84b6c33d54 in mdb_cursor_touch (mc=mc@entry=0x7f44abffe3e0) at mdb.c:6273 #13 0x7f84b6c36eee in mdb_cursor_put (mc=0x7f44abffe3e0, key=0x7f44abffe7c0, data=0x7f44abffe7d0, flags=) at mdb.c:6407 #14 0x7f84b6c399ab in mdb_put (txn=0x555869a9d360, dbi=8, key=key@entry=0x7f44abffe7c0, data=data@entry=0x7f44abffe7d0, flags=flags@entry=0) at mdb.c:8765 #15 0x7f84ba50bc3d in Baloo::IdFilenameDB::put (this=this@entry=0x7f44abffe840, docId=, docId@entry=294039542757853187, path=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/idfilenamedb.cpp:75 #16 0x7f84ba505d1c in Baloo::DocumentUrlDB::add (this=this@entry=0x7f44abffead0, id=id@entry=294039542757853187, parentId=parentId@entry=288494538115254275, name=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/documenturldb.cpp:125 #17 0x7f84ba505fc3 in Baloo::DocumentUrlDB::put (this=this@entry=0x7f44abffead0, docId=docId@entry=294039542757853187, url=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/documenturldb.cpp:69 #18 0x7f84ba51ad24 in Baloo::WriteTransaction::addDocument (this=0x7f44a40084a0, doc=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:57 #19 0x7f84ba516479 in Baloo::Transaction::addDocument (this=this@entry=0x7f44abffeb90, doc=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:226 #20 0x5558688cf596 in Baloo::NewFileIndexer::run (this=0x555869aed830) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/newfileindexer.cpp:72 #21 0x7f84b9983372 in QThreadPoolThread::run (this=0x555869b02ff0) at thread/qthreadpool.cpp:99 #22 0x7f84b99860ce in QThreadPrivate::start (arg=0x555869b02ff0) at thread/qthread_unix.cpp:368 #23 0x7f84b7f90559 in start_thread () from /lib64/libpthread.so.0 #24 0x7f84b8f3981f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f84b0c39700 (LWP 2826)): #0 0x7f84b565bdc9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f84b5615911 in g_main_context_query () from /usr/lib64/libglib-2.0.so.0 #2 0x7f84b5616147 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f84b56162dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f84b9ba9c0b in QEventDispatcherGlib::processEvents (this=0x7f84ac000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f84b9b5209a in QEventLoop::exec (this=this@entry=0x7f84b0c38ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f84b99814da in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f84badc6985 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7f84b99860ce in QThreadPrivate::start (arg=0x7f84bb036d60) at thread/qthread_unix.cpp:368 #9 0x7f84b7f90559 in start_thread () from /lib64/libpthread.so.0 #10 0x7f84b8f3981f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f84bb508100 (LWP 2821)): #0 0x7f84b8f2f07b in poll () from /lib64/libc.so.6 #1 0x7f84b56161c9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f84b56162dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f84b9ba9c0b in QEventDispatcherGlib::processEvents (this=0x555869a8b7f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f84b9b52
[juk] [Bug 402398] New: Juk playlist mis-sorts Collection List, History, and Play Queue with playlist entries after KF5
https://bugs.kde.org/show_bug.cgi?id=402398 Bug ID: 402398 Summary: Juk playlist mis-sorts Collection List, History, and Play Queue with playlist entries after KF5 Product: juk Version: 18.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: lulosals...@gmail.com CC: mp...@kde.org Target Milestone: --- Created attachment 117036 --> https://bugs.kde.org/attachment.cgi?id=117036&action=edit Example of Juk mis-sorting special icon names in playlist SUMMARY Since the port of Juk to KF5, the playlist column has a regression with the way the "special icons" are sorted. The "special icons" are the "Collection List" icon, the "History" icon, and the "Play Queue" icon. These have special functions. The special icons used to be grouped at the top of the playlist view column, above all playlists, but now they are sorted alphabetically with the rest of the playlists. This is a problem if there are many playlists, as I have when I DJ. I used to be able to find the special icon right away, as they were right at the top, now I have to scroll and look for them, which is troublesome when I'm DJ'ing and I need to be fast, and this used to be the old functionality that brought me to Juk. See the attached screenshot to see our case where the special icons are buried in the playlist names. STEPS TO REPRODUCE 1. Make several mock playlists. Give each playlist a different name, like "B", "J", "Q". These names are designed so that you can see how all are sorting. 2. Look at the left hand side of the window, which is the Playlist area. You will see all the playlists and special icons sorting like this: B Collection List History J Play Queue Q OBSERVED RESULT You can see that the special icons are sorting in *in between* the playlist names. EXPECTED RESULT We should see the special icons *grouped together* at the top, the way it used to be before Juk was transitioned to KF5. Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.4 Qt Version: 5.11.2 KDE Frameworks Version: 5.53.0 Kernel Version: 4.15.0-43-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.6 GiB of RAM Thank you for time and your efforts, very much appreciated! -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401657] Falkon AdBlock Works Without Sense
https://bugs.kde.org/show_bug.cgi?id=401657 --- Comment #5 from Alberto Díaz López --- (In reply to David Rosca from comment #4) > This is all offtopic. > > As Alexander Browne mentioned, you can disable those rules if you really > don't want them. > > And AdBlock extension is not "outdated" in Falkon, it is custom > implementation so the version number has *nothing* in common with versions > of Firefox/Chrome/... extensions. I see. Sorry about that. I'll check it out then. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401657] Falkon AdBlock Works Without Sense
https://bugs.kde.org/show_bug.cgi?id=401657 --- Comment #3 from Alberto Díaz López --- (In reply to Felipe from comment #2) > The embedded adblock must be a REALLY old version since there isnt the > ability to right click on an ad or image to block it, plus it doesnt make > ANY sense to load ALL the lists that were added to block when we go to the > options' screen. NO Adblocker EVER does that. Also, several ads are blocked > but the spaces arent removed as they should be. Totally agree. That's one of the worst things of Falkon for me. I'm expecting a new version of the software and hoping some of the bugs/issues will be fixed, cause if i want it as my daily and default web browser, the AdBlock must work perfectly fine, or at least don't make me mad. I read before that at GSOC a mate was working on the JS add-ons compatibility, i don't know if Chromium or Firefox or what, but it would be nice, i would love to can use the Mozilla add-ons repository, but since it uses QtWebEngine, and that's Chromium, i suppose that would be Chromium extensions, but anyway, that would be better to improve the amount of add-ons that can be used on it, like uBlock Origin, the best one for me in this category. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401683] New: YouTube Player Always Restore Standard Size After Quitting Falkon
https://bugs.kde.org/show_bug.cgi?id=401683 Bug ID: 401683 Summary: YouTube Player Always Restore Standard Size After Quitting Falkon Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- SUMMARY When i use YouTube on Falkon, i just press T to change into the theatre mode, but when i close Falkon and reopen it or even just closing the tab and reopen it, the player is at its standard size, with the theater mode disabled. STEPS TO REPRODUCE 1. Open Falkon. 2. Go to any YouTube.com video and play it. 3. Change to the theatre mode pressing T or with the dedicated button for that. 4. Close the tab or Falkon. 5. Reopen the tab or Falkon. OBSERVED RESULT The YouTube player is always at the standard size, instead of saving the theater mode/size. EXPECTED RESULT YouTube player should preserve/remember the theater mode state and load it. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Linux 4.19.4 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401657] New: Falkon AdBlock Works Without Sense
https://bugs.kde.org/show_bug.cgi?id=401657 Bug ID: 401657 Summary: Falkon AdBlock Works Without Sense Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Using Falkon normally, the AdBlock extension behavior in general makes no sense, having, for example, to specify a lot of times that i don't wanna have it disabled for DuckDuckGo. STEPS TO REPRODUCE 1. Open Falkon. 2. Make a search on DuckDuckGo with AdBlock activated. 3. See the ads. 4. Go to the extension basic config with a single click on the AdBlock icon to check the checkbox of disabling is checked. OBSERVED RESULT The checkbox is checked even if i unchecked before. EXPECTED RESULT The checkbox should be unchecked. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Linux 4.19.4 (available in About System) KDE Plasma Version: Plasma 5.14.4 KDE Frameworks Version: 5.52 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 --- Comment #17 from Alberto Salvia Novella --- Since I'm not using Plasma right now I'm unsubscribing from this bug, but feel free to re-subscribe me if you needed any help from me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400704] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=400704 Alberto Salvia Novella changed: What|Removed |Added CC|es204904...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 401092] Selecting a second scan area results in garbage
https://bugs.kde.org/show_bug.cgi?id=401092 Alberto Salvia Novella changed: What|Removed |Added CC||es204904...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 401092] New: Selecting a second scan area results in garbage
https://bugs.kde.org/show_bug.cgi?id=401092 Bug ID: 401092 Summary: Selecting a second scan area results in garbage Product: Skanlite Version: 2.1.0.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: es204904...@gmail.com Target Milestone: --- https://youtu.be/kk2tYaByfO4 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 383961] Searches don't show compressed files that Baloo has indexed and can find
https://bugs.kde.org/show_bug.cgi?id=383961 --- Comment #12 from Alberto Salvia Novella --- I'm unsubscribing now, but feel free to resubscribe me if you needed my help. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 383961] Searches don't show compressed files that Baloo has indexed and can find
https://bugs.kde.org/show_bug.cgi?id=383961 Alberto Salvia Novella changed: What|Removed |Added CC|es204904...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 383961] Baloo searches don't show compressed files
https://bugs.kde.org/show_bug.cgi?id=383961 --- Comment #7 from Alberto Salvia Novella --- Strit was unable to reproduce it too. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 383961] Baloo searches don't show compressed files
https://bugs.kde.org/show_bug.cgi?id=383961 --- Comment #6 from Alberto Salvia Novella --- https://forum.manjaro.org/t/could-you-confirm-this-kde-bug/63373 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 383961] Baloo searches don't show compressed files
https://bugs.kde.org/show_bug.cgi?id=383961 --- Comment #5 from Alberto Salvia Novella --- I cannot longer check myself. Nevertheless I will ask my distro if they are experiencing the bug themselves. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #32 from José Alberto --- Thank you. =) Can we mark this as reopened so it doesn't get lost? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #21 from Alberto --- After doing a bit more research I just opened a bug for including Metal support in Krita. So if that is accepted then this issue would roll into that work. Bug 399820 - Implement Metal support as OpenGL is deprecated on OS X -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399820] New: Implement Metal support as OpenGL is deprecated on OS X
https://bugs.kde.org/show_bug.cgi?id=399820 Bug ID: 399820 Summary: Implement Metal support as OpenGL is deprecated on OS X Product: krita Version: 4.1.5 Platform: Mac OS X Disk Images OS: OS X Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: afonsec...@gmail.com Target Milestone: --- SUMMARY Apple has deprecated OpenGL support for the Mac OS X platform and the API is no longer supported. Although still functional, it may cease to be included in future releases of the operating system. This bug is to report this change and advise implementation of the Metal API for continued support of Krita on the OS X platform. Please refer to Apple's note in the OpenGL programming guide: "Important OpenGL was deprecated in macOS 10.14. To create high-performance code on GPUs, use the Metal framework instead." https://developer.apple.com/library/archive/documentation/GraphicsImaging/Conceptual/OpenGL-MacProgGuide/opengl_intro/opengl_intro.html They refer developers to use the Metal API referenced here: https://developer.apple.com/metal/ Additional information regarding Apple's deprecation warning: "Deprecations Periodically, Apple adds deprecation macros to APIs to indicate that those APIs should no longer be used in active development. When a deprecation occurs, it’s not an immediate end of life for the specified API. Instead, it is the beginning of a grace period for transitioning from that API and to newer and more modern replacements. Deprecated APIs typically remain present and usable in the system for a reasonable time past the release in which they were deprecated. However, active development on them ceases, and the APIs receive only minor changes to accommodate security patches or to fix other critical bugs. Deprecated APIs may be removed entirely from a future version of the operating system. As a developer, avoid using deprecated APIs in your code as soon as possible. At a minimum, new code you write should never use deprecated APIs. And if your existing code uses deprecated APIs, update that code as soon as possible." Reference: https://developer.apple.com/macos/whats-new/ STEPS TO REPRODUCE 1. Open Krita 2. Go to menu Krita->Preferences->Display OBSERVED RESULT Observe Canvas Graphics Acceleration option Renderer lists OpenGL and Metal is not an option. EXPECTED RESULT Metal is an available graphics acceleration renderer option SOFTWARE VERSIONS Krita Version: 4.1.5 Qt Version (compiled): 5.11.1 Version (loaded): 5.11.1 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: darwin Kernel Version: 18.0.0 Pretty Productname: macOS 10.14 Product Type: osx Product Version: 10.14 OpenGL Info **OpenGL not initialized** ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #20 from Alberto --- Thank you for the update. I have a couple of questions regarding the bug status and process as I'm still getting up to speed here. 1. Was someone able to isolate the specific OpenGL API call that is not working as it's supposed to on a Mac OS Nvidia GPU? Do we have sufficient information to resolve this bug? 2. If indeed it is a bug in Nvidia's driver on OS X, is there no code workaround possible? I have not encountered a similar bug on other paint/image editing applications on my Mac with this GPU. 3. Although Apple no longer ships new MacBook's with Nvidia GPU's, they are still supported by Apple (I just updated my own Nvidia MacBook to MacOS Mojave). Other Krita users have already reported this issue (other bugs closed out marked as duplicate of this one). What is the support cutoff in terms of hardware age for the purposes of Krita development? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #30 from José Alberto --- (In reply to Stefan Brüns from comment #29) > I asked *you* about *your* setup. It may be similar or even identical to the > one originally reported, but without detailed information it is impossible > to know. > > It is also impossible to know if your setup is completely unaltered since, > this includes any other software, e.g. kernel, udev, udisks2 at least. OK, sorry, I thought it was not useful given the old information, as it has even been pointed out which commit introduced this and what solved it partially. My setup: Archlinux linux 4.18.12..arch1-1 (also with 4.18.9.arch1-1) libsystemd 239.2-1 systemd 239.2-1 udisks2 2.8.1-1 (also 2.8.0-1) solid 5.50.0-1 kde-applications 18.08.1 If you need something else, just ask, I don't know if I'm missing something important or not. > - what you do > - what happens I plug in a pendrive (gpt partition table, luks2 encrypted ext4 partition). It appears in dolphin, I click on "3.7 GiB Encrypted Drive" to open it. It raises an error saying An error occurred while accessing '3.7 GiB Hard Drive', the system responded: The device is already mounted: Device /dev/dm-0 is already mounted at `/run/media/ja/08ef0bd7-52fe-468e-95fe-55a3b19fe074'. It's true, it's mounted there, but it should have also being opened. If I click again on "3.7 GiB Encrypted Drive", it's opened. > It is not possible to check the data you provided earlier (which may be > deprecated anyway) as the pastebin has vanished. I know, it was just to show you that I've been always willing to help. I'm not demanding for a fix (nor with any other bug, ever), nor I wanted you to extract information from a random internet video. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #28 from José Alberto --- (In reply to Stefan Brüns from comment #27) > (In reply to José Alberto from comment #26) > > This is back for LUKS containers (or maybe it was never completely gone, I > > did never tested LUKS containers, I didn't even knew what they were last > > time I posted here). > > > > I have recorded a video, just in case it helps. It will be in this link for > > a month: https://my.owndrive.com/index.php/s/fshtH0Oi70eKQhG > > > > Thanks! > > Please describe exactly > - how your setup looks like > - what you do > - what happens > > I will *not* try to extract information from some random internet video link! I didn't open a new bug because the setup has always been the same, you can find all the things you ask for in the first comment talking about luks containers. If you need more info than that, just ask more specifically and I'll give more information (see https://bugs.kde.org/show_bug.cgi?id=391706#c14 ). The video was *not* even necessary, I just added it in case it helps, it's not a random internet video, I recorded it. I cared to do it very straightforward so you can see what is happening (starts without pendrive, plug the pendrive, click on luks partition in dolphin, get the bug, repeat the bug by unmounting and mounting again). > I will *not* try to extract information from some random internet video link! Don't worry, I will not do it ever again, it seems I wasted my time on it. I did what I could, I don't have enough knowledge to try to fix it (if I had it, I would have tried it instead of recording a video, yes). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #26 from José Alberto --- This is back for LUKS containers (or maybe it was never completely gone, I did never tested LUKS containers, I didn't even knew what they were last time I posted here). I have recorded a video, just in case it helps. It will be in this link for a month: https://my.owndrive.com/index.php/s/fshtH0Oi70eKQhG Thanks! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399030] Can't print 4 pages per sheet and then odd/even for double-sided printing
https://bugs.kde.org/show_bug.cgi?id=399030 --- Comment #3 from Alberto --- Created attachment 115519 --> https://bugs.kde.org/attachment.cgi?id=115519&action=edit Print 4 pages by sheet Of course here it is. Sorry about answer later -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399031] New: Can't print 4 pages per sheet and then odd/even for double-sided printing
https://bugs.kde.org/show_bug.cgi?id=399031 Bug ID: 399031 Summary: Can't print 4 pages per sheet and then odd/even for double-sided printing Product: okular Version: 1.5.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: albertocanet...@gmail.com Target Milestone: --- SUMMARY Can't print 4 pages per sheet and then odd/even for double-sided printing for printers that not allowed to print double-sided by itself STEPS TO REPRODUCE 1. Options page set -> odd/even 2. Select printer options and pages by sheet 3. Error message: pages by sheet and pages set cant selected at the same time EXPECTED RESULT Print 1 2 3 4 in the first page print 9 10 11 12 int the second page ... and then print 5 6 7 8 in the first page by the other side changing the paper... ACTUAL RESULT Error message: pages by sheet and pages set cant selected at the same time SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 399030] New: Can't print 4 pages per sheet and then odd/even for double-sided printing
https://bugs.kde.org/show_bug.cgi?id=399030 Bug ID: 399030 Summary: Can't print 4 pages per sheet and then odd/even for double-sided printing Product: okular Version: 1.5.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: albertocanet...@gmail.com Target Milestone: --- SUMMARY Can't print 4 pages per sheet and then odd/even for double-sided printing for printers that not allowed to print double-sided by itself STEPS TO REPRODUCE 1. Options page set -> odd/even 2. Select printer options and pages by sheet 3. Error message: pages by sheet and pages set cant selected at the same time EXPECTED RESULT Print 1 2 3 4 in the first page print 9 10 11 12 int the second page ... and then print 5 6 7 8 in the first page by the other side changing the paper... ACTUAL RESULT Error message: pages by sheet and pages set cant selected at the same time SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 398874] New: skanliterc created twice due to upper/lower case 's'
https://bugs.kde.org/show_bug.cgi?id=398874 Bug ID: 398874 Summary: skanliterc created twice due to upper/lower case 's' Product: Skanlite Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: a24...@gmail.com Target Milestone: --- Hello. When I was making a backup to a samba share I noticed that there was a file which was always transfering, even when there was no change in the filesystem (running rsync twice). But noticed that filesize was changing everytime the backup was done. A close look to the ~/.config folder gives the trick: alberto@debian:~$ ls .config/*kanl* .config/skanliterc .config/Skanliterc Regards. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396034] After switching tools, quickly displaying PopUpPalette using Tablet buttons freezes tools.
https://bugs.kde.org/show_bug.cgi?id=396034 --- Comment #6 from Alberto --- Created attachment 115112 --> https://bugs.kde.org/attachment.cgi?id=115112&action=edit Canvas frozen after using pop-up palette Pen taps are indicated with red circles, larger circles indicate pressing pen button. Canvas does not respond to either inputs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396034] After switching tools, quickly displaying PopUpPalette using Tablet buttons freezes tools.
https://bugs.kde.org/show_bug.cgi?id=396034 Alberto changed: What|Removed |Added CC||afonsec...@gmail.com --- Comment #5 from Alberto --- I can confirm this bug as well with Wacom Intuos tablet using these repro steps: 1. Create new document, sketch on default layer 2. Create new layer and hide layer drawn on above 3. Sketch on new layer and bring up pop-up palette window using button on pen 4. Select a new tool and attempt to draw 5. Observe canvas UI is not responsive, unable to recover without quitting Krita Krita Version: 4.1.1 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: darwin Kernel Version: 17.7.0 Pretty Productname: macOS High Sierra (10.13) Product Type: osx Product Version: 10.13 OpenGL Info **OpenGL not initialized** I am attaching a video with repro above. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390642] Cursor gets stuck with the wrong icon after moving between canvas and gui
https://bugs.kde.org/show_bug.cgi?id=390642 --- Comment #25 from Alberto --- Created attachment 115111 --> https://bugs.kde.org/attachment.cgi?id=115111&action=edit Stuck cursor (mouse pointer and window resize) No cursor should display per default setting. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390642] Cursor gets stuck with the wrong icon after moving between canvas and gui
https://bugs.kde.org/show_bug.cgi?id=390642 Alberto changed: What|Removed |Added CC||afonsec...@gmail.com --- Comment #24 from Alberto --- Hi, I am encountering this issue as well on Mac OS X 10.13.6 with the Wacom Intuos tablet. Krita Version: 4.1.1 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: darwin Kernel Version: 17.7.0 Pretty Productname: macOS High Sierra (10.13) Product Type: osx Product Version: 10.13 OpenGL Info **OpenGL not initialized** I am attaching a movie with repro as it happens all the time now that I hooked up my tablet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #17 from Alberto --- (In reply to Dmitry Kazakov from comment #16) > Hi, Alberto! > > Can I ask you to try two things: > > 0) Enable back NVidia GPU > > 1) Go to Settings->Display->Scaling Mode and set 'Bilinear Filtering'. Does > it solve the problem? > > 2) Disable a checkbox in View->Instant Preview disabled and check if the > problem still persists? Hi Dmitry, I tried the steps you suggested but neither one resolved the issue. However, since I was there on a whim I tried unchecking the "Use texture buffer" box below Scaling Mode and that seems to work. The checkbox is enabled by default. So hopefully this helps narrow it down further, NVIDIA gpu with the default "Use texture buffer" enabled produces the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #14 from Alberto --- Thank you for clarifying, I wasn't aware you could do that. I downloaded the switching software for testing and found that the issue does not appear if I switch to Integrated only. If I leave it to Discrete or Dynamic then the issue is present. Note: I had to disconnect my external display in order to for the switcher to allow me to switch to Integrated. I normally run with an external display connected. So the issue seems to happen when the NVIDIA GPU is used. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #12 from Alberto --- If I re-enable the checkbox, the issue returns. I don't think I can choose which renderer, it has OpenGL listed but the box is disabled and can't be altered. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #10 from Alberto --- No, it's a MacBook Pro (Retina, 15-inch, Mid 2014) it's running an NVIDIA: NVIDIA GeForce GT 750M 2048 MB Intel Iris Pro 1536 MB -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #8 from Alberto --- (In reply to Boudewijn Rempt from comment #7) > Hi Alberto, > > I'm really puzzled... Can you check whether you can enable canvas > acceleration in settings/configure krita/display? Ah, yes, that is it! If I uncheck it, then the issue goes away and everything works as expected (same with the crop operation). So the bug happens in the default state, with the Canvas Graphics Acceleration enabled. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #6 from Alberto --- Created attachment 115031 --> https://bugs.kde.org/attachment.cgi?id=115031&action=edit Canvas input profile I believe this is what was asked for, I don't think I've changed anything here from the default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #4 from Alberto --- Hi Boudewijn, Thank you for following-up. This is a fresh install of Krita as I'm a new user to the software. I only have one user account on my Mac so I am including the requested kritarc file here. Where can I find the input configuration settings? Also, I encounter the same issue after performing a crop operation. Please let me know if I can provide any more information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 Alberto changed: What|Removed |Added CC||afonsec...@gmail.com --- Comment #5 from Alberto --- Created attachment 115030 --> https://bugs.kde.org/attachment.cgi?id=115030&action=edit krita settings file Requested kritarc file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #2 from Alberto --- Additional details: Source image used: PNG 5204x3472 Hardware: Single display. Krita Version: 4.1.1 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: darwin Kernel Version: 17.7.0 Pretty Productname: macOS High Sierra (10.13) Product Type: osx Product Version: 10.13 OpenGL Info **OpenGL not initialized** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 --- Comment #1 from Alberto --- Created attachment 114988 --> https://bugs.kde.org/attachment.cgi?id=114988&action=edit Video repro -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] New: Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 Bug ID: 398689 Summary: Image disappears when zooming in after scale transform Product: krita Version: 4.1.1 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: afonsec...@gmail.com Target Milestone: --- Steps to reproduce: 1. Open an image in Kitra. 2. Select Image/Scale Image to New Size... from menu 3. Enter a size smaller than the original and click OK 4. Select Zoom tool and click to zoom in a few times 5. Observer the image starts to "fade" away until it is no longer visible Please see video to illustrate above steps and behavior. I can reproduce this bug with other images consistently. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 342387] the phones type should be customizable
https://bugs.kde.org/show_bug.cgi?id=342387 alberto changed: What|Removed |Added CC||paj...@gmail.com --- Comment #2 from alberto --- This is not only wish list, its kinda needed too If kontact is supposed to be able to interact with other programs. Any other programs allow custom tags for phones. After syncing with kontact using webdav, kontact silently dropped everything it didnt understood and making some changes to the contatc, it updated the remote vcards dropping everything it didnt understood Including custom tags that radical/evolution/gmail were able to show and to transfer between them perfectly Luckily i run the backend where i save the vcards in git and i was able to detect the mess quite fast. Im not sure I want to touch kontact again looking at this policy with unknown data. Its bad enough that is not able to show it properly, but to erase it? Just add everything you dont understand to notes or something The severity of this bug should be higher than wishlist imho. In other notes, Should I open a bug about the data lost using webdav or is this bug enough? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 --- Comment #21 from José Alberto --- This bug is not happening anymore for me. Seems it was fixed somehow. :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 José Alberto changed: What|Removed |Added CC||demonocaqu...@gmail.com --- Comment #14 from José Alberto --- Thanks for all your effort, but I'm sorry to say that this is still not fixed in solid 5.45.0. I can still reproduce it with that version of solid and dolphin 18.04.0. (In reply to Stefan Brüns from comment #12) > Can anyone affected provide the output of > $> udisksctl dump https://pastebin.com/raw/khgBhsAN -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390283] Plasma sees external monitor after disconnecting
https://bugs.kde.org/show_bug.cgi?id=390283 --- Comment #2 from Alberto Curro --- Sorry, 4.13 is the kernel version, KDE version is 5.8, from the official mint repositories. (In reply to Alberto Curro from comment #1) > Same issue is happening to me, plasma does not recognize hot-connecting or > disconenecting screens for my Dell Latitude E7470, either using official > Dell Docker stations (HDMI, DVI or DP, 3 different docking models), or > miniDP on the own laptop. > > My system is Linux Mint 18 with KDE, 4.13.0. > > This was not happening with Linux Mint 17 and KDE 4.x, with my previous > latitude laptop and the same dock stations or HDMI. KDE was keeping the > configurations for the different monitors, and changing the layout > accordingly, to follow the last configuration used with the recognized > monitor. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390283] Plasma sees external monitor after disconnecting
https://bugs.kde.org/show_bug.cgi?id=390283 Alberto Curro changed: What|Removed |Added CC||bertothun...@gmail.com --- Comment #1 from Alberto Curro --- Same issue is happening to me, plasma does not recognize hot-connecting or disconenecting screens for my Dell Latitude E7470, either using official Dell Docker stations (HDMI, DVI or DP, 3 different docking models), or miniDP on the own laptop. My system is Linux Mint 18 with KDE, 4.13.0. This was not happening with Linux Mint 17 and KDE 4.x, with my previous latitude laptop and the same dock stations or HDMI. KDE was keeping the configurations for the different monitors, and changing the layout accordingly, to follow the last configuration used with the recognized monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391297] New: Tabbed to another Konsole instance while mesa and linux packages were updating
https://bugs.kde.org/show_bug.cgi?id=391297 Bug ID: 391297 Summary: Tabbed to another Konsole instance while mesa and linux packages were updating Product: kwin Version: 5.12.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: albertodz...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.2) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was updating my system (mesa and linux packages) and i tabbed to another Konsole instance to check the package mesa before it was updated). -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1ca4a0b840 (LWP 2563))] Thread 5 (Thread 0x7f1c80f55700 (LWP 2729)): #0 0x7f1c9d32b3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1ca0609f77 in () at /usr/lib/libQt5Script.so.5 #2 0x7f1ca0609fb9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f1c9d32508c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f1ca4379e7f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1c82196700 (LWP 2720)): #0 0x7f1ca436fa76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f1ca1735e73 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f1ca173760f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f1ca16dc3db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1ca14eb7ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f1c9bdf0379 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f1ca14f0b4d in () at /usr/lib/libQt5Core.so.5 #7 0x7f1c9d32508c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1ca4379e7f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f1c83fff700 (LWP 2676)): #0 0x7fff94af8be6 in clock_gettime () #1 0x7f1ca4387746 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f1ca1739c02 in () at /usr/lib/libQt5Core.so.5 #3 0x7f1ca173839a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f1ca1738976 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f1ca1737925 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f1ca16dc3db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f1ca14eb7ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f1c9ac73416 in () at /usr/lib/libQt5DBus.so.5 #9 0x7f1ca14f0b4d in () at /usr/lib/libQt5Core.so.5 #10 0x7f1c9d32508c in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f1ca4379e7f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1c8aa66700 (LWP 2675)): #0 0x7f1ca436f97b in poll () at /usr/lib/libc.so.6 #1 0x7f1ca32618e0 in () at /usr/lib/libxcb.so.1 #2 0x7f1ca3263679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f1c8bb5382a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f1ca14f0b4d in () at /usr/lib/libQt5Core.so.5 #5 0x7f1c9d32508c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1ca4379e7f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1ca4a0b840 (LWP 2563)): [KCrash Handler] #5 0x7f1ca42b8860 in raise () at /usr/lib/libc.so.6 #6 0x7f1ca42b9ec9 in abort () at /usr/lib/libc.so.6 #7 0x7f1ca14da8e8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f1c89c4faf5 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #9 0x7f1c89c4d34f in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #10 0x7f1c8bb5a503 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () at /usr/lib/libQt5XcbQpa.so.5 #11 0x7f1ca1c90fd0 in QOpenGLContext::create() () at /usr/lib/libQt5Gui.so.5 #12 0x7f1c89c50279 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #13 0x7f1c89c508d9 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #14 0x7f1c9c4d1f55 in QSGRenderLoop::instance() () at /usr/lib/libQt5Quick.so.5 #15 0x7f1c9c547adc in QQuickWindowPrivate::init(QQuickWindow*, QQuickRenderControl*) () at /usr/lib/libQt5Quick.so.5 #16 0x7f1bf0fc127e in PlasmaQuick::Dialog::Dialog(QQuickItem*) () at /usr/lib/libKF5PlasmaQuick.so.5 #17 0x7f1bf12182e1 in () at /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so #18 0x7f1c9bd711e3 in QQmlType::create(QObject**, void**, unsigned long) const () at /usr/lib/libQt5Qml.so.5 #19 0x7f1c9bde80a8 in QQmlObjectCreator::createIn
[kate] [Bug 390728] New Features And More Configurability Options For Kate
https://bugs.kde.org/show_bug.cgi?id=390728 --- Comment #2 from Alberto Díaz López --- (In reply to Nate Graham from comment #1) > Thanks for your suggestions! I know what you mean; Sublime Text is really > nice. > > However, bug reports with multiple issues/requests cannot be actionable; > each bug report must track only a single issue or feature request. See > https://community.kde.org/Get_Involved/Bug_Reporting#Step_6:_File_a_high- > quality_bug_report > > Also, please search for existing bug reports before filing a new one (see > https://community.kde.org/Get_Involved/Bug_Reporting#Step_5: > _Make_sure_it_hasn.27t_already_been_filed). Some of the requests here are > already tracked by existing tickets. For example, #3 is Bug 353654. > > for #4, you can customize the keybindings the same way you can in every KDE > app: Settings > Configure shortcuts > > for #5, such a general request cannot be actionable. Please file a separate > ticket for every feature you would like to request. Ok Nate, thanks for your quick response, i'll do it better in the future, i'm starting to use bugs.kde.org, this isn't an excuse, but i received the same advice on others bugs or whislist i opened, as i said, i'm sorry for the inconveniences. 3: I read it, and that's right, i didn't search for it, i'm sorry again, but i think this hasn't solved yet, right? 4: Oh yes, sorry i need to try and search a little on the GUI before ask, but it isn't what i said at point 1, i can't find the option "restore last closed document". 5: I see, i'll probably open a new ticket for this request. As i said, i'll do it better at the future tickets i open here, thanks and sorry for the inconveniences. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 390745] Request Of New Features For Falkon/QupZilla
https://bugs.kde.org/show_bug.cgi?id=390745 --- Comment #5 from Alberto Díaz López --- (In reply to Alberto Díaz López from comment #3) > (In reply to David Rosca from comment #1) > > 1. That depends on QtWebEngine. New Qt release usually ships with > > QtWebEngine based on newer Chromium. > > 2. Developer tools can be enabled by setting > > QTWEBENGINE_REMOTE_DEBUGGING=12345 env variable (you can use any port you > > like, 12345 in this example). QtWebEngine 5.11 will have proper developer > > tools without this hack. > > 3. Advanced options are in preferences, I don't see any reason for this. > > 4. AdBlock implementation can be improved, but if you really want uBlock you > > should write to the uBlock addon developer. > > There is a GSoC project to add support for JavaScript/QML extension which > > should make writing extensions easier. > > Thanks, i read something about that yeah, on Twitter, i'm very excited about > that. > 2: So basically at the future, the developer tools will be implemented as > native? With QtWebEngine, right? > 3: I saw them, but there are only 4 options on the Appearance, what i can > see and there are not what i mean, i mean, some really advanced options, > related to, as i said, like in Mozilla Firefox, is about:config, i suppose > you know it, but there are a lot of options, which change the behavior of > the software. > 4: Ok, i will write him to telling that. > Thanks for your surprisingly speed responses and thanks for your hard work. > Receive a huge hug. I add to the previous comment, 1: Ok, so there is no responsibility of Falkon/QupZilla, because it delegates into QtWebEngine for that. Thanks and sorry for the inconveniences. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 390745] Request Of New Features For Falkon/QupZilla
https://bugs.kde.org/show_bug.cgi?id=390745 --- Comment #4 from Alberto Díaz López --- (In reply to David Rosca from comment #2) > Also this is not a way to request new features. Each bugreport should only > have one separate bug/feature. Ok, sorry for that, thanks for the explanation, i will take in consideration at the future. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 390745] Request Of New Features For Falkon/QupZilla
https://bugs.kde.org/show_bug.cgi?id=390745 --- Comment #3 from Alberto Díaz López --- (In reply to David Rosca from comment #1) > 1. That depends on QtWebEngine. New Qt release usually ships with > QtWebEngine based on newer Chromium. > 2. Developer tools can be enabled by setting > QTWEBENGINE_REMOTE_DEBUGGING=12345 env variable (you can use any port you > like, 12345 in this example). QtWebEngine 5.11 will have proper developer > tools without this hack. > 3. Advanced options are in preferences, I don't see any reason for this. > 4. AdBlock implementation can be improved, but if you really want uBlock you > should write to the uBlock addon developer. > There is a GSoC project to add support for JavaScript/QML extension which > should make writing extensions easier. Thanks, i read something about that yeah, on Twitter, i'm very excited about that. 2: So basically at the future, the developer tools will be implemented as native? With QtWebEngine, right? 3: I saw them, but there are only 4 options on the Appearance, what i can see and there are not what i mean, i mean, some really advanced options, related to, as i said, like in Mozilla Firefox, is about:config, i suppose you know it, but there are a lot of options, which change the behavior of the software. 4: Ok, i will write him to telling that. Thanks for your surprisingly speed responses and thanks for your hard work. Receive a huge hug. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 390745] New: Request Of New Features For Falkon/QupZilla
https://bugs.kde.org/show_bug.cgi?id=390745 Bug ID: 390745 Summary: Request Of New Features For Falkon/QupZilla Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: albertodz...@gmail.com Target Milestone: --- I have been using Falkon/QupZilla since 2 days as the main web browser on my system. And i would like to request and comment new features that i think improve the UX and the quality of the software. 1: Update to latests versions of the software core, at "About QupZilla" window, i see that the Chrome/Chromium version mentioned is 61.x, being the actual on stable channel, the 64.x. I think the update of these core parts would be better for the performance of the web browser. 2: Deloper tools. I notified since the first day i tried this software (about 4 weeks ago more or less), that i can't open any developer tools or anything like that, (i tried with the habitual keyboard shortcuts, like F12, Ctrl-Shift-I but nothing opened, even searching for any of that at the options, but i didn't find anything) and i think this is an essential feature for this kind of software. 3: Advanced options. I can't see any advanced options, like on Firefox is "about:config" or the flags on Chromium/Chrome etc. I would like to have this on this software, to configure some advanced parameters, like the way that the web browser reacts to a click on the URL bar, and if the url is selected, double click on it, trim the URL or not, etc. 4: Support of the plugins. I'm not a heavy user of this kind of addons/plugins/extensions, however you prefer to call them. But i really would like to can install uBlock Origin (yeah, i know that QupZilla/Falcon has its own adblocker but uBlock Origin is for me, better, because it's FOSS too, and above all, it allows much more configurability than i have seen on the built-in adblock) or some others plugins, available on Chromium/Firefox, etc. I really have a lot of hope on this web browser and i would like to use it as an alternative that hasn't got any difference of base features when it's compared with Firefox, Chromium and that. I have to add that the Speed Dial (a feature that i never found on Firefox or Chromium and i missed very much from Opera, Maxthon, Vivaldi, etc) is really great, i didn't try it a lot, but looks great, and i remember from Opera too, the feature to could change the wallpaper on that screen, just amazing. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 390229] Falkon Freezes My System
https://bugs.kde.org/show_bug.cgi?id=390229 --- Comment #4 from Alberto Díaz López --- (In reply to David Rosca from comment #3) > I have no experience with nvidia drivers, but the situation you describe > with kwin happens with Intel when there is a gpu hang and needs to be reset. > > So I am closing this bug as the problem is in gpu drivers. Ok, as i said, with the 2.2.5-2 version, and all the updates that i applied as i commented before, i feel like these errors, have been fixed, at least i don't experience them like before, that it was open QupZilla and the system freezed. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 390731] New: Krunner segfaults after launching Firefox
https://bugs.kde.org/show_bug.cgi?id=390731 Bug ID: 390731 Summary: Krunner segfaults after launching Firefox Product: krunner Version: 5.12.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: demonocaqu...@gmail.com Target Milestone: --- Application: krunner (5.12.1) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-2-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: "Alt + F2", then typed "f" (and it autocompleted firefox), then Enter, then the segfault (but Firefox was opened). The backtrace is generated for this case. But also, if I have already opened Firefox before typing it in krunner, then it crashes without pressing Enter, only typing f. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f353d58b800 (LWP 1696))] Thread 21 (Thread 0x7f34b7fff700 (LWP 1721)): #0 0x7f3536dfa3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f353959c02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f35124bc42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f35124c1479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f35124c14d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f35124bec83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f353959ab4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f3536df408c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f3538ea2e7f in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f34d8ff9700 (LWP 1720)): #0 0x7f3536dfa3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f353959c02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f35124bc42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f35124c1479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f35124c14d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f35124bec83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f353959ab4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f3536df408c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f3538ea2e7f in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f34d97fa700 (LWP 1719)): #0 0x7f3536dfa3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f353959c02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f35124bc42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f35124c1479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f35124c14d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f35124c14d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f35124c14d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f35124c14d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f35124c14d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f35124bb924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f351
[Falkon] [Bug 390229] Falkon Freezes My System
https://bugs.kde.org/show_bug.cgi?id=390229 --- Comment #2 from Alberto Díaz López --- (In reply to David Rosca from comment #1) > Can you try to get a backtrace when it freezes? You need to run falkon in > gdb and ctrl+c when it freezes. > Although you say that the whole system except cursor freezes, so this is > most likely issue with your graphics driver. I tried to open again QupZilla after update a lot of packages on my Manjaro KDE system, the past 17th February, including QupZilla, not a new version, but an update, after all, KDE Plasma, KDE Frameworks, and now it doesn't freeze the system, but still sometimes when i do something (open a new window with something at fullscreen), KWin crashes and shows me a message that says something like this "KWin crashed and stopped the effects", with the consecuence that the panel that i have stops to work properly and freezes like when my system freezed when i did some things with QupZilla or just with open it. Looks like as you said, that it's something with the graphics driver, i've got an NVIDIA GPU and privative drivers, i fear. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390728] New: New Features And More Configurability Options For Kate
https://bugs.kde.org/show_bug.cgi?id=390728 Bug ID: 390728 Summary: New Features And More Configurability Options For Kate Product: kate Version: 17.12.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: albertodz...@gmail.com Target Milestone: --- I'm trying to migrate from Sublime Text (non FOSS) to Kate, but i have a few features that i can't find on Kate and i would like to see on Kate in the future. I proceed to enumerate and briefly explain them. 1: Reopen last closed document. On Sublime Text, the key binding for this action is like on most web browsers, Ctrl-Shift-T, on Kate this action divides the screen or the document into one more part, for each time i use it. I would like there would be an option to do this. 2: Keep the zoom manually changed by the user. When i change the zoom/text size with the mousewheel or Ctrl and -/+ it's nice, but when i close Kate and reopen it, the zoom is restablished at its default value, this is kinda frustrating for me. It would be great if you add an option at the settings for the zoom would be maintained as the user establish it, not individual for each document, global i mean, Sublime does like this. 3: Keep documents which are not saved opened when Kate closes. On Sublime, (yeah i know, Sublime reference again), i usually create a new document, write whatever i need and i don't save that document/s, when i close Sublime Text and reopen it, the document is till there, the program doesn't ask the user if he wanna save, not save or cancel when he closes the program, i don't know if the developers keep it as a temporal file or what, but i really think this is a great feature. 4: Key Bindings. I really can't i'm gonna say this but i can't find this option at Kate, i mean, the option to customize every keyboard shortcut and its action, this option is available on Sublime Text and i miss it on Kate. 5: More configuration options. This is something i never would imaginate in a KDE Software, but i feel like Sublime has got more options to configurate than Kate, and specifically, i like the way that Sublime allows the user to edit the options, not GUI, it opens the documents to edit with Sublime itself, the configuration documents, i mean. And Themes, there is an option on the Sublime menus for change the theme for another one you have installed or downloaded. Thank you so much for such a great software and keep working to improve Kate even more ^^. I would be very pleased if you can evaulate these few comments about Kate, i really think that would be great. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 390229] New: Falkon Freezes My System
https://bugs.kde.org/show_bug.cgi?id=390229 Bug ID: 390229 Summary: Falkon Freezes My System Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: now...@gmail.com Reporter: albertodz...@gmail.com Target Milestone: --- I have a lot of tabs opened at Falkon, but i got freezes a few times, when i opened a new window to open a link, when i restored a tab, when i restored a window. And now, with a lot of tabs opened, Falkon got crashed everytime i launch it. When i said it freezes the system i mean, i got Plasma with a strange color, and i only can move the cursor but not interact with the DE or system, i always do the same, launch another instance of tty with Ctrl + Alt + F2, and use Ctrl + Alt + Supr to reboot from there. I really love Falkon, but this is very frustrating. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381071] Compositing disabled on boot when any aurorae theme is chosen
https://bugs.kde.org/show_bug.cgi?id=381071 --- Comment #16 from Alberto Mattea --- (In reply to Martin Flöser from comment #15) > What's the togglecompositing you have in autostart? It's my workaround for this bug: #!/bin/sh sleep 3 xdotool key shift+alt+F12 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389744] New: KWin Crashed When I Was Tabing Between Apps
https://bugs.kde.org/show_bug.cgi?id=389744 Bug ID: 389744 Summary: KWin Crashed When I Was Tabing Between Apps Product: kwin Version: 5.11.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: albertodz...@gmail.com Target Milestone: --- Application: kwin_x11 (5.11.5) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.14.15-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was switching between apps with Alt + Tab when KWin crashed. I had opened Dolphin, Chromium, Konsole and Thunderbird. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd990eb9840 (LWP 612))] Thread 7 (Thread 0x7fd9548fb700 (LWP 736)): #0 0x7fd9897483bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd98cd12f77 in () at /usr/lib/libQt5Script.so.5 #2 0x7fd98cd12fb9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fd98974208c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fd990831e7f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fd9559fd700 (LWP 733)): #0 0x7fd9897483bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd95b404fec in () at /usr/lib/dri/r600_dri.so #2 0x7fd95b404ef8 in () at /usr/lib/dri/r600_dri.so #3 0x7fd98974208c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fd990831e7f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fd95633f700 (LWP 732)): #0 0x7fd9897483bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd95b404fec in () at /usr/lib/dri/r600_dri.so #2 0x7fd95b404ef8 in () at /usr/lib/dri/r600_dri.so #3 0x7fd98974208c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fd990831e7f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fd96edee700 (LWP 729)): #0 0x7fd990827a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7fd98de026f3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fd98de03e8f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fd98dda8d0b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd98dbb878e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fd988214a19 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fd98dbbdb2d in () at /usr/lib/libQt5Core.so.5 #7 0x7fd98974208c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fd990831e7f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd9750e6700 (LWP 646)): #0 0x7fd990827a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7fd98de026f3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fd98de03e8f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fd98dda8d0b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd98dbb878e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fd987388416 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fd98dbbdb2d in () at /usr/lib/libQt5Core.so.5 #7 0x7fd98974208c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fd990831e7f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd9775a6700 (LWP 642)): #0 0x7fd99082797b in poll () at /usr/lib/libc.so.6 #1 0x7fd98f9278e0 in () at /usr/lib/libxcb.so.1 #2 0x7fd98f929679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fd9786937aa in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fd98dbbdb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7fd98974208c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd990831e7f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd990eb9840 (LWP 612)): [KCrash Handler] #5 0x7fd95b75e774 in () at /usr/lib/dri/r600_dri.so #6 0x7fd95b5448c4 in () at /usr/lib/dri/r600_dri.so #7 0x7fd95b31ddd0 in () at /usr/lib/dri/r600_dri.so #8 0x7fd95b2e0b08 in () at /usr/lib/dri/r600_dri.so #9 0x7fd95b2e128f in () at /usr/lib/dri/r600_dri.so #10 0x7fd9888d26c7 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #11 0x7fd9888d3966 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #12 0x7fd9888d91de in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #13 0x7fd9888c9632 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #14 0x7fd9888c9afc in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #15 0x7fd988903c60 i
[kdialog] [Bug 382437] Regression in kdialog causes wrong file extension
https://bugs.kde.org/show_bug.cgi?id=382437 --- Comment #13 from Alberto Salvia Novella --- Work-around: https://forum.manjaro.org/t/chromium-to-download-files-with-the-appropriate-extension/35930 -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382437] Regression in kdialog causes wrong file extension
https://bugs.kde.org/show_bug.cgi?id=382437 --- Comment #10 from Alberto Salvia Novella --- @Aleksey Kontsevich, please: 1. Open a new report about that. 2. Paste its link here. Thanks ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387895] New: Window rules are not detected with some applications
https://bugs.kde.org/show_bug.cgi?id=387895 Bug ID: 387895 Summary: Window rules are not detected with some applications Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: kungfoo...@gmail.com Target Milestone: --- Maybe some applications change window class after the window is created? Steps to reproduce: - Open Spotify. - Add window rule with substring "potify". - Set some change to see if the rule is affecting. (in my case, minimum size of 770x70) - Restart Spotify. It no longer affects. Related: Bug 387742 (and the reason I'm skipping the S) KWin 5.9.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387742] Window class string in window-specific settings is saved in lower case
https://bugs.kde.org/show_bug.cgi?id=387742 --- Comment #3 from Alberto Torres Ruiz --- Correction, it NEVER works after restarting the application!! Maybe it was never the casing, it's just that it never works in the first place! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387742] Window class string in window-specific settings is saved in lower case
https://bugs.kde.org/show_bug.cgi?id=387742 --- Comment #2 from Alberto Torres Ruiz --- Also, when creating a rule, the class is set automatically in lower case, but it works for that session, which made the issue even more confusing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387806] New: Task bar of secondary screen is empty when there is no primary screen
https://bugs.kde.org/show_bug.cgi?id=387806 Bug ID: 387806 Summary: Task bar of secondary screen is empty when there is no primary screen Product: plasmashell Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: kungfoo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Have two screens, two taskbars, each with setting "show windows only in current screen". Disconnect the primary screen (or in my case, close the laptop lid by mistake). Reconnect it. Now the task bar of the secondary screen is empty, but the screen is still full of windows. Moving them around doesn't fix the problem. It took me a while to notice there is no active screen in display settings, and when setting an active screen it works again. -- You are receiving this mail because: You are watching all bug changes.
