[konsole] [Bug 377252] New: Modifying font style will save in profile but will not be remembered
https://bugs.kde.org/show_bug.cgi?id=377252 Bug ID: 377252 Summary: Modifying font style will save in profile but will not be remembered Product: konsole Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: hsanta...@gmail.com Target Milestone: --- Created attachment 104383 --> https://bugs.kde.org/attachment.cgi?id=104383&action=edit konsole profile with bold font style selected When you edit konsole's profile to change font style (eg. from regular to bold), konsole will save that accordingly in the profile file, but will not apply that font style after closing konsole and opening it again (despite applying the font style to the current and new tabs before closing konsole). Reproducible: Always Steps to Reproduce: 1. Start Konsole with the any profile 2. Select "Edit current profile..." from the menu 3. Select "Appearance" tab. 4. Press "Select Font..." button 5. Change "Font Style" from Regular to Bold Actual Results: Konsole will apply the the font style to the current konsole session and will save that to the profile file, but the next time konsole will be opened it will ignore the font style (bold) and will render the font style as regular. Expected Results: Konsole should correctly read font style from saved profile instead of ignoring it. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 365030] terminal doesn't get focus after opening yakuake
https://bugs.kde.org/show_bug.cgi?id=365030 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- I couldn't reproduce that. Can you confirm if it's still reproducible? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 297445] Alt-Tab behavior - not really recently used
https://bugs.kde.org/show_bug.cgi?id=297445 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com Status|RESOLVED|REOPENED Resolution|INVALID |--- Ever confirmed|0 |1 --- Comment #7 from Henrique Sant'Anna --- Plasma 5.13.2 and this bug is still annoying people and there is still being requested for a solution where, at least, users could chose the behavior: - If the minimized window will actually be sent to bottom of the stack (current plasma behavior); or - If the last minimized window will be at the top of the stack (Microsoft Windows behavior, Gnome, xfce). That way users can select "the last used window" even if it was just minimized. Another approach would be to offer another shortkey to change to the last used window. Microsoft Windows also have this feature, where you can use gesture on touchpad or touchscreen (slide from right border to inside) to do that. Android N also offers that feature by double tapping the multitask phone button. KDE Plasma System Settings already haves a robust Task Switcher configuration, but it really misses that option where a minimized window is kept in top of the stack, just like a regular window. Current discussion: https://forum.kde.org/viewtopic.php?t=143414 Older topics: https://forum.kde.org/viewtopic.php?t=99625 https://forum.kde.org/viewtopic.php?t=101211 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395744] MPRIS dataengine fails to add spotifyd as a MediaPlayer
https://bugs.kde.org/show_bug.cgi?id=395744 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393618] bookmark sync is missing
https://bugs.kde.org/show_bug.cgi?id=393618 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- Not only bookmarks, but sync of passwords too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354179] File associations cannot be changed if already defined in $XDG_CONFIG_HOME/mimeapps.list
https://bugs.kde.org/show_bug.cgi?id=354179 Henrique Sant'Anna changed: What|Removed |Added CC||tet...@gmail.com --- Comment #12 from Henrique Sant'Anna --- Still happens in 5.8.3. The workaround seems to be working, after creating the link (as in comment9) I could edit mimetype settings and it will correctly be saved. Sometimes you have to recreate the symbolic link, because package updates can replace it. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 385045] Falkon doesn't know about printers in KDE
https://bugs.kde.org/show_bug.cgi?id=385045 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #2 from Henrique Sant'Anna --- (In reply to Tom Kijas from comment #0) > Falkon doesn't know about printers in KDE (probably because of being snap). > The only option is to print into PDF. Printing is working great here, Falkon on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 386409] Add option to middle click in empty area of tab bar to reopen closed tab
https://bugs.kde.org/show_bug.cgi?id=386409 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- There is any other browser that have the mentioned behavior (middle click reopens tab) ? Currently Ctrl + Shift + Tab reopens the last closed tab. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 386409] Add option to middle click in empty area of tab bar to reopen closed tab
https://bugs.kde.org/show_bug.cgi?id=386409 --- Comment #2 from Henrique Sant'Anna --- (In reply to Henrique Sant'Anna from comment #1) > There is any other browser that have the mentioned behavior (middle click > reopens tab) ? > > Currently Ctrl + Shift + Tab reopens the last closed tab. Sorry, I mean Ctrl + Shift + T -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415505] Kdenlive to cannot import files or open projects when jack is running.
https://bugs.kde.org/show_bug.cgi?id=415505 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- Tested here with 20.08.1 linux distro package and with kdenlive-20.11.70-8a08988-x86_64.appimage. jack2 version 1.9.14. Tested with SDL: Pulseaudio (on my system pulseaudio redirects to jack). Works good. and with RtAudio: * 20.08.1 linux distro package: Will work good with direct output to Jack (autodetects and autoconnects to jack's system output) and sound plays correctly. The distinct behavior is that when I select any frame on timeline, it produces continuous noise representing the audio frame. With SDL+pulseaudio it will produce only some ms of noise to do that representation. * kdenlive-20.11.70-8a08988-x86_64.appimage: RtAudio will detect and outputs to ALSA ( and on my system it will be than be redirected do pulseaudio, which sends to jack). I could not select the RtAudio output (it's grayed out). I could not reproduce the described behavior. Also, i didn't understood what you meant when said: > Then, in pavucontrol, I assigned kdenlive to the "Jack sink (PulseAudio JACK > sink)" audio device instead of the direct device, and kdenlive un-hung. Because if kdenlive outputs directly to jack, than Pulseaudio wont see kdenlive. But if kdenlive outputs to Pulseaudio, than I think the only way to the sound to go to jack is through PulseAudio JACK sink. What do you mean when you say "direct device" ? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423337] Waveform display for longer audio track goes out of sync with played or rendered content
https://bugs.kde.org/show_bug.cgi?id=423337 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423337] Waveform display for longer audio track goes out of sync with played or rendered content
https://bugs.kde.org/show_bug.cgi?id=423337 --- Comment #2 from Henrique Sant'Anna --- I can confirm that audio waveform thumbnails on timeline will get out of sync with real sound by several frames, representing around 500 ms of delay from the real sound to the corresponding displayed waveform, and will increase over the timeline progress. Tested with 20.08.1 linux distro package (arch): Confirmed. Tested with kdenlive-20.11.70-8a08988-x86_64.appimage: Confirmed. Tried to clean project cache to regenerate audio thumbnails, closing kdenlive and than reopening the project, but it will be regenerated out of sync again. Tested with and without ffmpeg audio thumbnails, but with the same results. kdenlive-20.11.70-8a08988-x86_64.appimage seems to regenerate audio thumbnails much faster than 20.08.1 linux distro package. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422139] Audio is not syncing with video, audio wave changes when cremoving sections
https://bugs.kde.org/show_bug.cgi?id=422139 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #2 from Henrique Sant'Anna --- Seems related to bug #423337. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410798] Audio and Video are out of sync
https://bugs.kde.org/show_bug.cgi?id=410798 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #4 from Henrique Sant'Anna --- Seems related or duplicate of bug #423337. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414011] Double-click doesn't open the preview in fullscreen AND Video and Audio timeline are shrunk
https://bugs.kde.org/show_bug.cgi?id=414011 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- Tested with kdenlive-20.11.70-8a08988-x86_64.appimage. About monitor double click: I can double click over video monitor and it goes full screen. There is a particular situations where I double click and it wont goes full screen: that is when I select in timeline a clip or a track that haves an effect like zoom or transform, that puts a layer over de monitor that is used to receive mouse commands. About timeline track thickness: At current version it can be resized. I suggest you to test the described behavior with kdenlive daily build appimage and report if the behavior persists, otherwise close this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411766] Audio wave doesn't match actual audio.
https://bugs.kde.org/show_bug.cgi?id=411766 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- Seems related to bug #423337. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426861] Indicate if a clip is used in Timeline or not
https://bugs.kde.org/show_bug.cgi?id=426861 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426861] Indicate if a clip is used in Timeline or not
https://bugs.kde.org/show_bug.cgi?id=426861 --- Comment #1 from Henrique Sant'Anna --- You can right click over the clip in Project Bin, there is a menu item called "Clip in Timeline". It's sub-menu is a list of occurrences of that clip in timeline. If the clip is not used anywhere in timeline the menu will be disabled (grayed out). Tested here with kdenlive-20.11.70-8a08988-x86_64.appimage Please test this procedure on last kdenlive version. If you find that this behavior satisfy your needs, please close this bug. Otherwise please explain in details the desired behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368775] [Wishlist] Remove automatically silent part of video.
https://bugs.kde.org/show_bug.cgi?id=368775 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424972] No se puede abrir ningún archivo para trabajar
https://bugs.kde.org/show_bug.cgi?id=424972 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- Seems related with bug #417021. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 428308] New: Can't limit ksysguard to a single instance.
https://bugs.kde.org/show_bug.cgi?id=428308 Bug ID: 428308 Summary: Can't limit ksysguard to a single instance. Product: ksysguard Version: 5.20.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: hsanta...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Can't limit ksysguard to a single instance. STEPS TO REPRODUCE 1. Set a shortcut to open ksysguard, like Ctrl + Shift + Esc (like MS Windows's Task Manager). 2. Press the shortcut and open ksysguard. 3. Change focus to another window. 4. Press the shortcut again and you will get a new instance of ksysguard, instead of getting the first instance back. OBSERVED RESULT You will have multiple instances of ksysguard running at the same time. EXPECTED RESULT The shortcut could turn back to front the current running ksysguard instance, instead of starting a new instance. Maybe having an command line option like dolphin haves (--new-window), can be nice. Or the inverse, --single-window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION - Mouse click over System Load Viewer applet will also open new instance of ksysguard. - As dirty workaround this command line can do the trick to have a single instance (editing the window title 'System Monitor' to match your language): bash -c "([ \"$(xdotool getwindowfocus getwindowname)\" == 'System Monitor' ] && pkill ksysguard) || (pgrep '^ksysguard$' && wmctrl -x -R ksysguard) || (ksysguard && pkill ksysguard)" -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 428312] New: ksysguard tree view with incorrect arrow keys navigation
https://bugs.kde.org/show_bug.cgi?id=428312 Bug ID: 428312 Summary: ksysguard tree view with incorrect arrow keys navigation Product: ksysguard Version: 5.20.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: hsanta...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY ksysguard, process table tab, tree view mode have incorrect arrow keys navigation STEPS TO REPRODUCE 1. Open ksysguard; 2. Activate the "All Processes, Tree" list mode; 3. Focus to the processes list; 4. Navigate between listed processes using the arrow keys (up and down) 5. Use the right arrow key to open any branch / tree 6. Go down to the processes from within the branch using the down arrow key 7. Go up with the up arrow key to try to get out of the branch and the focus will leave the list of processes and will automatically switch to the quick search OBSERVED RESULT The list of processes loses focus when we try to navigate upwards with the up arrow key on the keyboard, from within a branch / sub-tree. EXPECTED RESULT When we press the up arrow key on the keyboard, the selection must switch to the immediately previous process (above) in the list, at the same level of the tree, when there is another process above at the same level / branch. But, when there is no other previous process at the same level, the selection in the list must move to the parent process, which is at the level immediately prior to the current level. When pressing the left arrow key on the keyboard, the current branch should be hidden regardless of which process is selected within that branch. Thus, passing the selection to the parent process of the previously selected process. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION I'm on X11. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 428316] New: ksysguard presents a difficult and inconsistent navigation sequence between the elements of the window (tab key)
https://bugs.kde.org/show_bug.cgi?id=428316 Bug ID: 428316 Summary: ksysguard presents a difficult and inconsistent navigation sequence between the elements of the window (tab key) Product: ksysguard Version: 5.20.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: hsanta...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Flags: Usability+ SUMMARY In the ksysguard window, element focus starts in the list of tabs. Shifting focus to the list of processes is difficult to do without using the mouse, using the keyboard instead. We have to press TAB key 5 times before we can get to precesses list. Pressing left and right arrow keys will navigate between ksysguard's tabs. Pressing the down arrow key on the keyboard does not shift the focus down from list of tabs, either for the quick search or for the list of processes. But if you are already focused at quick search, than you can press down arrow key to change the focus to processes list. STEPS TO REPRODUCE 1. Start ksysguard, the element focused is the first tab from the list of tabs. 2. Pressing down arrow key will not change focus to list of processes 3. Press TAB key fo 5 times to change the focus to list of processes OBSERVED RESULT With TAB key, is hard to go from initial focused element to the processes list element. With down arrow key the behavior is inconsistent, because it works only when the focus is already at the quick search. EXPECTED RESULT ksysguard starting already focused over processes list, so we can use arrow keys to navigate over the processes on the list. >From there, with the current behavior we already can use Ctrl+TAB and Ctrl+Shift+TAB to change between ksysguard's tabs if needed. And also already can use Ctrl+F to go to quick search (or just start typing). An alternative solution would be to make the down arrow key to change focus from list of tabs to quick search. The current behavior already allow to press the down arrow key to go from quick search to processes list. So that way could go down to quick search and down again to processes list. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION I'm on X11. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 428312] ksysguard tree view with incorrect arrow keys navigation
https://bugs.kde.org/show_bug.cgi?id=428312 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=428316 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 428318] New: ksysguard text alignment in the labels and content of the columns are not uniform.
https://bugs.kde.org/show_bug.cgi?id=428318 Bug ID: 428318 Summary: ksysguard text alignment in the labels and content of the columns are not uniform. Product: ksysguard Version: 5.20.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: hsanta...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Flags: Usability+ SUMMARY The text alignment in the labels of the columns, in the tab Processes Table, are not uniform. STEPS TO REPRODUCE 1. Open ksysguard 2. Observe the text alignment from labels of the columns and text alignment inside columns. OBSERVED RESULT some labels have left-aligned text: - Name - Window title - Download * - Upload * - GPU usage - GPU memory a label is centered: - User - CPU % other labels have right-aligned text: - Priority - Total Memory - Shared memory * The visual effect of this is even worse in the cases of Download and Upload columns because, although the labels of these columns are aligned to the left, the content of these columns is numeric and is aligned to the right. Therefore, the labels for the Download and Upload columns are out of alignment with their respective contents. This creates an unpleasant feeling when we focus on the values displayed in these columns. It happens that, if the Download and Upload columns are arranged in this sequence, the value within the Download column is closer to the alignment of the label of the next column, Upload, than the label of its own column, Download. The same can be said about the value inside the Upload column in relation to the label of the next column, if the label of the next column is also aligned to the left (in my case it is, (GPU usage)). EXPECTED RESULT A uniform pattern of text alignment for column labels and their contents. I would suggest the following pattern: - Texts: left aligned - % rates: centralized - numbers: right aligned But I'm not sure about what is the correct solution to this. Maybe UI people can say something about this. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature (missing output in nvidia-smi dmon)
https://bugs.kde.org/show_bug.cgi?id=427603 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 428316] ksysguard presents a difficult and inconsistent navigation sequence between the elements of the window (tab key)
https://bugs.kde.org/show_bug.cgi?id=428316 --- Comment #3 from Henrique Sant'Anna --- Ok, so I created a new test user and logged in with that user and then ran ksysguard (sorry for not doing that before). With clean settings I couldn't reproduce the reported behavior. So I changed some ksysguard settings to try to get it similar as my main user settings and maybe discover which setting was causing that. In short, I found that if I add a new tab to ksysguard and than add a new Process Controller to that tab, the behavior described at the bug report is reproduced. STEPS TO REPRODUCE 1. Open ksysguard; 2. Add new tab (File > New Tab); 3. Add the component Process Controller to the new tab (dragging it from right to left); 4. Go back to the main tab (Process Table); 5. Close ksysguard and reopen it. OBSERVED RESULT The behavior that I first described at the bug report: the element with (input) focus is the first tab from the tab list. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, kernel 5.4.72-1-lts KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 I also compiled ksysguard and all dependencies from sources to reproduce the bug and can confirm that this is reproducible from sources. ADDITIONAL INFORMATION Removing the second instance of the Process Controller from ksysguard will stop it from presenting the undesired behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426942] 20.08.1: OpenTimelineIO - Project Conversion Failed
https://bugs.kde.org/show_bug.cgi?id=426942
Henrique Sant'Anna changed:
What|Removed |Added
CC||hsanta...@gmail.com
--- Comment #3 from Henrique Sant'Anna ---
I can export, but I can't import.
To test the exporting I did:
STEPS TO REPRODUCE
1. Create empty project
2. Add a clip to the bin
3. Add the clip to timeline
4. Menu File > OpenTimelineIO Export
But if I try to import the exported file, I get the error alert:
"Project conversion failed:
%1(I18N_ARGUMENT_MISSING)"
So I tried to import the exported file directly to a OpenTimelineIO python
script:
#
import opentimelineio as otio
timeline = otio.adapters.read_from_file("kdenlive_exported.xml", "fcp_xml")
# I'm not sure if fcp_xml is the correct adapter
#
But the python script import will get this error:
Exception has occurred: AttributeError
'NoneType' object has no attribute 'text'
File
"/home/henrique/.local/lib/python3.8/site-packages/opentimelineio/adapters/fcp_xml.py",
line 943, in item_and_timing_for_element
start_value = int(item_element.find("./start").text)
So I debugged opentimelineio/adapters/fcp_xml.py and it seems that
kdenlive_exported.xml is not valid, at least for fcp_xml adapter.
--
You are receiving this mail because:
You are watching all bug changes.
[Touchpad-KCM] [Bug 395348] [Libinput backend] enable/disable touchpad setting is gray out and unavailable since plasma 5.13
https://bugs.kde.org/show_bug.cgi?id=395348 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 401440] Neon installer slideshow uses white text on light background
https://bugs.kde.org/show_bug.cgi?id=401440 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397952] kdenlive Automask crashed by clicking analyse button
https://bugs.kde.org/show_bug.cgi?id=397952 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- Created attachment 120109 --> https://bugs.kde.org/attachment.cgi?id=120109&action=edit backtrace to kdenlive crashing by clicking Automask analyse button kdenlive 19.04.1-1, Arch Linux. movit 1.6.2-1 installed and GPU processing activated. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397952] kdenlive Automask crashed by clicking analyse button
https://bugs.kde.org/show_bug.cgi?id=397952 --- Comment #2 from Henrique Sant'Anna --- Tested multiple times and kdenlive consistently crashes by clicking Automask analyse button. Steps to reproduce: 1. Create a new project. 2. Add any new clip and put it to the timeline. 3. Add Automask effect to the clip. 4. Click on the Analyze button from Automask effect Properties. 5. Kdenlive has crashed Always reproducible. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407696] New: Kdenlive will Crash after pressing Analyze button from Motion Track effect applied to track
https://bugs.kde.org/show_bug.cgi?id=407696 Bug ID: 407696 Summary: Kdenlive will Crash after pressing Analyze button from Motion Track effect applied to track Product: kdenlive Version: 19.04.1 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: hsanta...@gmail.com Target Milestone: --- SUMMARY Clicking on the Analyze button from Motion Track effect will crash Kdenlive if the effect is applied to the video track, not the clip. STEPS TO REPRODUCE 1. Create new project 2. Add a new clip to Project bin 3. Add the clip to a video track on timeline 4. Add the Motion track effect to the same timeline track (to the entire track, not the clip) 5. Select region for Motion track on Project monitor 6. Press Analyze button from Motion track properties 7. Kdenlive will crash OBSERVED RESULT Kdenlive will crash after pressing Analyze button from Motion track effect EXPECTED RESULT Analyze button would do the Analyze job SOFTWARE/OS VERSIONS Linux: Linux Arch 5.1.2-zen1-1-zen #1 ZEN SMP PREEMPT Wed May 15 00:13:04 UTC 2019 x86_64 GNU/Linux KDE Plasma: Yes (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.51.0 Qt Version: Qt 5.11.2 (compilado com 5.11.2) MLT version 6.17.0 ADDITIONAL INFORMATION Tested the 19.04.1 from arch linux repository and also from kdenlive-19.04.1b-x86_64.appimage with the same always reproducible behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407696] Kdenlive will Crash after pressing Analyze button from Motion Track effect applied to track
https://bugs.kde.org/show_bug.cgi?id=407696 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 401068] Repositioning and scaling image unintuitive to find
https://bugs.kde.org/show_bug.cgi?id=401068 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 401068] Repositioning and scaling image unintuitive to find
https://bugs.kde.org/show_bug.cgi?id=401068 --- Comment #3 from Henrique Sant'Anna --- Just to add that today I went through this situation where I wanted to resize the image and to position it inside the frame. The first place where I looked was the image inside the project monitor, where I looked for a way to select the image, to activate borders where I could resize it, and drag and drop it inside the monitor. Since doing that was not possible, I tried to go with Clip Properties tab, and on the sub-tab Properties I could find something that could be adjusted, but it was only the Proportion rate, not the size (or relative size) itself, or positioning. I really had the feel that those properties should be there at that tab. Then I understood that an effect should be needed, but I had no idea of each one to test first. Tried "Corners", but it wasn't exactly what I was looking for. Then sow "Transformation", which I applied to the figure on the timeline and that worked pretty well, with all properties I was expecting to find at the beginning, from Clip Properties tab. My suggestion is that Kdenlive should by default to auto add the right effect to any figure added to the timeline, that would let users easily control the size, rotating and positioning of the figure. To this my experience, the "Transform" effect did the job pretty well. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 400929] kwallet-pam errors when logging into Plasma from lightdm
https://bugs.kde.org/show_bug.cgi?id=400929 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 --- Comment #20 from Henrique Sant'Anna --- Created attachment 127437 --> https://bugs.kde.org/attachment.cgi?id=127437&action=edit journalctl -b | grep kwallet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414979] New: Drag and drop launcher from desktop/panel to latte dock
https://bugs.kde.org/show_bug.cgi?id=414979 Bug ID: 414979 Summary: Drag and drop launcher from desktop/panel to latte dock Product: lattedock Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: usability Severity: wishlist Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: hsanta...@gmail.com Target Milestone: --- Flags: Usability+ SUMMARY I had a plasma panel that doesn't correctly auto-hides, so I decided to convert it to a new latte dock panel/area. So I was in need to move every launcher and widget from the plasma panel to the latte panel. I tried to drag-and-drop the launchers and widgets from one to another but it was no possible (even during plasma panel edit mode). Then I moved every launcher and widget to plasma desktop, outside the plasma panel, removed the old plasma panel, and then tried to drag-and-drop the launchers and widgets from plasma desktop to the new created Latte dock panel. The result is that I couldn't do that, even while on latte edit mode fixed. When I drop a launcher over latte panel it will be placed behind the latte panel, not inside. STEPS TO REPRODUCE 1. Create a new latte dock area. 2. Drag a launcher from plasma desktop and move it and drop over the latte area. OBSERVED RESULT The dropped launcher will be placed behind latte area, no inside latte. EXPECTED RESULT Drag-and-drop would work to move launchers from desktop or plasma panel into latte. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430210] Font previews do not show up on Wayland
https://bugs.kde.org/show_bug.cgi?id=430210 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473851] New: Dolphin crashes when right click or context menu key pressed over a file from Insync synced folder
https://bugs.kde.org/show_bug.cgi?id=473851
Bug ID: 473851
Summary: Dolphin crashes when right click or context menu key
pressed over a file from Insync synced folder
Classification: Applications
Product: dolphin
Version: 23.04.3
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: hsanta...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (23.04.3)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.1.47-1-lts x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Dolphin crashes when right click or press keybord context menu key over a file
inside Insync synced folder
The crash can be reproduced every time.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f0d6acdb614 in QVariant::toString() const () at
/usr/lib/libQt5Core.so.5
#7 0x7f0d1c403275 in
FileItemActionInsyncPlugin::getContextMenuActions(QString const&) () at
/usr/lib/qt/plugins/fileitemactioninsyncplugin.so
#8 0x7f0d1c402fb9 in
FileItemActionInsyncPlugin::actions(KFileItemListProperties const&, QWidget*)
() at /usr/lib/qt/plugins/fileitemactioninsyncplugin.so
#9 0x7f0d6ca8406b in () at /usr/lib/libKF5KIOWidgets.so.5
#10 0x558efa104041 in ()
#11 0x558efa104939 in ()
#12 0x558efa0e98ca in ()
#13 0x7f0d6acd1637 in () at /usr/lib/libQt5Core.so.5
#14 0x7f0d6cdbe289 in DolphinView::requestContextMenu(QPoint const&,
KFileItem const&, KFileItemList const&, QUrl const&) () at
/usr/lib/libdolphinprivate.so.5
#15 0x7f0d6ce2ea10 in DolphinView::slotItemContextMenuRequested(int,
QPointF const&) () at /usr/lib/libdolphinprivate.so.5
#16 0x7f0d6acd1637 in () at /usr/lib/libQt5Core.so.5
#17 0x7f0d6cdbbb8b in KItemListController::itemContextMenuRequested(int,
QPointF const&) () at /usr/lib/libdolphinprivate.so.5
#18 0x7f0d6cdf97b6 in KItemListController::keyPressEvent(QKeyEvent*) () at
/usr/lib/libdolphinprivate.so.5
#19 0x7f0d6cdfd08e in KItemListView::event(QEvent*) () at
/usr/lib/libdolphinprivate.so.5
#20 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#22 0x7f0d6b9aee6d in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#23 0x7f0d6ba5d703 in QFrame::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#24 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#25 0x7f0d6b97d958 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#26 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#27 0x7f0d6b9cec5b in () at /usr/lib/libQt5Widgets.so.5
#28 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#29 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#30 0x7f0d6b145570 in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() at /usr/lib/libQt5Gui.so.5
#31 0x7f0d6b12a6c5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#32 0x7f0d6815e955 in () at /usr/lib/libQt5WaylandClient.so.5
#33 0x7f0d6890fa31 in g_main_dispatch (context=0x7f0d6ee0) at
../glib/glib/gmain.c:3460
#34 g_main_context_dispatch (context=0x7f0d6ee0) at
../glib/glib/gmain.c:4200
#35 0x7f0d6896ccc9 in g_main_context_iterate.isra.0
(context=context@entry=0x7f0d6ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#36 0x7f0d6890d0e2 in g_main_context_iteration (context=0x7f0d6ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#37 0x7f0d6aceb51c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#38 0x7f0d6ac9b404 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#39 0x7f0d6ac9c8a3 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#40 0x558efa0deda8 in ()
#41 0x7f0d6a227cd0 in __libc_start_call_main
(main=main@entry=0x558efa0dc520, argc=argc@entry=1,
argv=argv@entry=0x7ffe0a9e3648) at ../sysdeps/nptl/libc_start_call_main.h:58
#42 0x7f0d6a227d8a in __libc_start_main_impl (main=0x558efa0dc520, argc=1,
argv=0x7ffe0a9e3648, init=, fini=,
rtld_fini=, stack_end=0x7ffe0a9e3638) at ../csu/libc-start.c:360
#43 0x558efa0df565 in ()
[Inferior 1 (process 79986) detached]
The reporter in
[dolphin] [Bug 473858] New: Dolphin crashes when right click or context menu key pressed over a file from Insync synced folder
https://bugs.kde.org/show_bug.cgi?id=473858
Bug ID: 473858
Summary: Dolphin crashes when right click or context menu key
pressed over a file from Insync synced folder
Classification: Applications
Product: dolphin
Version: 23.04.3
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: hsanta...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (23.04.3)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.1.47-1-lts x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Dolphin crashes when right click or press keybord context menu key over a file
inside Insync synced folder
The crash can be reproduced every time.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f0d6acdb614 in QVariant::toString() const () at
/usr/lib/libQt5Core.so.5
#7 0x7f0d1c403275 in
FileItemActionInsyncPlugin::getContextMenuActions(QString const&) () at
/usr/lib/qt/plugins/fileitemactioninsyncplugin.so
#8 0x7f0d1c402fb9 in
FileItemActionInsyncPlugin::actions(KFileItemListProperties const&, QWidget*)
() at /usr/lib/qt/plugins/fileitemactioninsyncplugin.so
#9 0x7f0d6ca8406b in () at /usr/lib/libKF5KIOWidgets.so.5
#10 0x558efa104041 in ()
#11 0x558efa104939 in ()
#12 0x558efa0e98ca in ()
#13 0x7f0d6acd1637 in () at /usr/lib/libQt5Core.so.5
#14 0x7f0d6cdbe289 in DolphinView::requestContextMenu(QPoint const&,
KFileItem const&, KFileItemList const&, QUrl const&) () at
/usr/lib/libdolphinprivate.so.5
#15 0x7f0d6ce2ea10 in DolphinView::slotItemContextMenuRequested(int,
QPointF const&) () at /usr/lib/libdolphinprivate.so.5
#16 0x7f0d6acd1637 in () at /usr/lib/libQt5Core.so.5
#17 0x7f0d6cdbbb8b in KItemListController::itemContextMenuRequested(int,
QPointF const&) () at /usr/lib/libdolphinprivate.so.5
#18 0x7f0d6cdf97b6 in KItemListController::keyPressEvent(QKeyEvent*) () at
/usr/lib/libdolphinprivate.so.5
#19 0x7f0d6cdfd08e in KItemListView::event(QEvent*) () at
/usr/lib/libdolphinprivate.so.5
#20 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#22 0x7f0d6b9aee6d in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#23 0x7f0d6ba5d703 in QFrame::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#24 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#25 0x7f0d6b97d958 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#26 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#27 0x7f0d6b9cec5b in () at /usr/lib/libQt5Widgets.so.5
#28 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#29 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#30 0x7f0d6b145570 in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() at /usr/lib/libQt5Gui.so.5
#31 0x7f0d6b12a6c5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#32 0x7f0d6815e955 in () at /usr/lib/libQt5WaylandClient.so.5
#33 0x7f0d6890fa31 in g_main_dispatch (context=0x7f0d6ee0) at
../glib/glib/gmain.c:3460
#34 g_main_context_dispatch (context=0x7f0d6ee0) at
../glib/glib/gmain.c:4200
#35 0x7f0d6896ccc9 in g_main_context_iterate.isra.0
(context=context@entry=0x7f0d6ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#36 0x7f0d6890d0e2 in g_main_context_iteration (context=0x7f0d6ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#37 0x7f0d6aceb51c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#38 0x7f0d6ac9b404 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#39 0x7f0d6ac9c8a3 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#40 0x558efa0deda8 in ()
#41 0x7f0d6a227cd0 in __libc_start_call_main
(main=main@entry=0x558efa0dc520, argc=argc@entry=1,
argv=argv@entry=0x7ffe0a9e3648) at ../sysdeps/nptl/libc_start_call_main.h:58
#42 0x7f0d6a227d8a in __libc_start_main_impl (main=0x558efa0dc520, argc=1,
argv=0x7ffe0a9e3648, init=, fini=,
rtld_fini=, stack_end=0x7ffe0a9e3638) at ../csu/libc-start.c:360
#43 0x558efa0df565 in ()
[Inferior 1 (process 79986) detached]
The reporter in
[plasmashell] [Bug 455252] Applications do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 --- Comment #7 from Henrique Sant'Anna --- I'm affected by this bug too. I have 6 apps set to autostart, but only one is currrently starting (Yakuake). X11 plasma session. from `journalctl -b` I can see this: ` jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/copyq.desktop:181: Invalid value for boolean: False jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/copyq.desktop:181: Failed to parse file: Invalid argument jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Failed to parse /home/henrique/.config/autostart/copyq.desktop, ignoring it jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/insync.desktop:15: Unknown key name 'TerminalOptions' in section 'Desktop Entry', ignoring. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/org.kde.latte-dock.desktop:43: Unknown key name 'InitialPreference' in section 'Desktop Entry', ignoring. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Configuration file /home/henrique/.config/autostart/org.kde.yakuake.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/org.kde.yakuake.desktop:163: Unknown key name 'TerminalOptions' in section 'Desktop Entry', ignoring. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Configuration file /home/henrique/.config/autostart/telegramdesktop.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/telegramdesktop.desktop:18: Unknown key name 'TerminalOptions' in section 'Desktop Entry', ignoring. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Configuration file /home/henrique/.config/autostart/goldendict.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/goldendict.desktop:16: Unknown key name 'TerminalOptions' in section 'Desktop Entry', ignoring. ` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 --- Comment #8 from Henrique Sant'Anna --- Created attachment 150104 --> https://bugs.kde.org/attachment.cgi?id=150104&action=edit the desktop generates log error and the app will not be autostarted jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/copyq.desktop:181: Invalid value for boolean: False jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/copyq.desktop:181: Failed to parse file: Invalid argument jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Failed to parse /home/henrique/.config/autostart/copyq.desktop, ignoring it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications with malformed .desktop files do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 --- Comment #14 from Henrique Sant'Anna --- I suggest that for every ".desktop" file that cannot be auto-started, a notification be generated for the user, so that the user knows that that specific application could not be started automatically. Furthermore, it is important that in the configuration screen for automatic startup it is clear to the user which of the listed applications will never be started and, if possible, for what reason. Waiting for users to realize for themselves that a certain application did not start when it should and that after that they have to investigate in the logs why the application was not started, does not seem to me to be an desirable behavior. Therefore, I consider that this is a bug, whatever the solution that is developed to fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications with malformed .desktop files do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 --- Comment #15 from Henrique Sant'Anna --- The "TerminalOptions=" parameter, which makes ".desktop" files invalid, is added by Plasma. To reproduce: In the startup and shutdown settings click on Properties for any listed application, then enter the Application tab of the properties window, edit the command line and then press the OK button. As a result, the ".desktop" file now has the invalid parameter "TerminalOptions=" which prevents the application from auto-starting. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455889] Parse autostarted .desktop files and display any errors in the UI
https://bugs.kde.org/show_bug.cgi?id=455889 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439664] Dolphin crashes with Insync 3.4.2.40293
https://bugs.kde.org/show_bug.cgi?id=439664 --- Comment #21 from Henrique Sant'Anna --- Dolphin can (or should) handle the plugin error and prevent the entire application from shutting down. The application is closing because its code does not anticipate that plugins can perform actions that result in a fatal error. There are multiple errors that Dolphin itself can cause, but these errors are handled in such a way that they do not result in failure. In short, the application needs to handle not only errors arising from its own native actions, but also generally handle errors that may arise from plugin actions. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432658] New: System Settings, Task Switcher: "Defaults" button incorrect behavior for shortcuts options
https://bugs.kde.org/show_bug.cgi?id=432658
Bug ID: 432658
Summary: System Settings, Task Switcher: "Defaults" button
incorrect behavior for shortcuts options
Product: systemsettings
Version: 5.20.5
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_kwintabbox
Assignee: kwin-bugs-n...@kde.org
Reporter: hsanta...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
In Task Switcher System Settings, the "Defaults" button is disabled despite
changing shortcuts options (if no other option have been changed, e.g. "Filter
windows by" options).
If some other options are changed then the "Defaults" button gets enabled and
pressing it will reset all settings, including shortcuts, but the new default
shortcut will not be updated onscreen.
Closing Task Switcher settings and coming back to it will than update shortcuts
onscreen.
The "Reset" and "Apply" buttons are also affected by (or correlate with) the
"Defaults" button malfunctioning.
STEPS TO REPRODUCE
1. Open System Settings, Window Management, Task Switcher
2. Press the "Defaults" button, if enabled. Than the button gets disabled.
3. Change shortcuts to new ones
("Defaults", "Reset" and "Apply" buttons stays disabled)
4. Change any other option (e.g. "Filter windows by" options)
(Then "Defaults", "Reset" and "Apply" buttons gets enabled)
5. Press the "Defaults" button.
(Any modified option will be reset to default, but shortcuts will not be
updated onscreen)
6. Close System Settings
7. Reopen System Settings, Window Management, Task Switcher
(Shortcuts are now updated onscreen)
OBSERVED RESULT
- "Defaults", "Reset" and "Apply" buttons stays disabled despite shortcut
options changes.
- "Defaults" button will change shortcuts to defaults without updating it
onscreen.
EXPECTED RESULT
- "Defaults", "Reset" and "Apply" buttons should be enabled after any shortcut
options changing.
- "Defaults" button should change shortcuts to defaults updating it also
onscreen.
SOFTWARE/OS VERSIONS
- Linux: 5.4.94-1-lts
- KDE Plasma Version:5.20.5
- KDE Frameworks Version: 5.78.0
- Qt Version: 5.15.2
ADDITIONAL INFORMATION
- The same behavior occurs over "Main" and "Alternative" tabs.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 419176] Keyboard shortcut meta+tab only allows one tab per meta, while alt+tab allows repeated presses of tab
https://bugs.kde.org/show_bug.cgi?id=419176 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419176] Keyboard shortcut meta+tab only allows one tab per meta, while alt+tab allows repeated presses of tab
https://bugs.kde.org/show_bug.cgi?id=419176 Henrique Sant'Anna changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Henrique Sant'Anna --- I can confirm that once set the shortcut Meta + Tab for Task Switcher (Main or Alternative) it will change between windows only once, no matter the effect selected for the switcher. And I can confirm that restarting computer (comment3) will fix the issue and, from that, Meta + Tab will than work to change between windows multiple times, as expected. SOFTWARE/OS VERSIONS - Linux: 5.4.94-1-lts - KDE Plasma Version: 5.20.5 (X11 session) - KDE Frameworks Version: 5.78.0 - Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432449] Memleak in plasmashell 5.20.5
https://bugs.kde.org/show_bug.cgi?id=432449 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #3 from Henrique Sant'Anna --- I realized memory leak once while using slideshow as wallpaper on the desktop (X11). Setting plain color as wallpaper fixed that. Anyway, this increasing memory usage can be caused by any widget set in desktop or in panels. So, disabling some widgets and waiting the same time could help to discover which one is causing the memory leak. There is also some users reporting that using some plasma theme (style) could get plasma to memory leak. So maybe it's a case of testing plasma with its default themes, breeze and dark breeze. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451531] Dual screen, different resolutions, clone mode -> missing panel
https://bugs.kde.org/show_bug.cgi?id=451531 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #17 from Henrique Sant'Anna --- I'm using kwin 5.24.4 and can reproduce this problem ALWAYS, every time I unplug HDMI cable without deactivating the external monitor first. But now the screen completely freezes, even the mouse pointer, and after that it will not unfreeze anymore. I'm on Arch and I don't know how to collect useful information about this freeze, since I don't have debug symbols installed, maybe I have to compile it myself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355588] Switching between alternative widgets makes them lose settings
https://bugs.kde.org/show_bug.cgi?id=355588 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425537] For applications with 2 variants of desktop files remembers the wrong one as pinned
https://bugs.kde.org/show_bug.cgi?id=425537 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435923] New: Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started
https://bugs.kde.org/show_bug.cgi?id=435923 Bug ID: 435923 Summary: Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: hsanta...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started, instead of the task being associated to already pinned icon. STEPS TO REPRODUCE 1. Pin Firefox Nightly icon to task manager (drag and drop Firefox Nightly icon from menu launcher to task manager); 2. Start Firefox Nightly by clicking over its task manager pinned icon; 3. Firefox Nightly will start and a new separated task icon will show up at task manager; OBSERVED RESULT - Starting Firefox Nightly from pinned icon will generate a new task icon in task manager while Firefox Nightly is running. This new icon is orange and not blue (it is associated to Firefox Stable, and not Firefox Nightly). - Trying to pin Firefox Nightly to task manager (right click over current running instance of Firefox Nightly) will pin Firefox Stable instead of Firefox Nightly. EXPECTED RESULT - Pinned Firefox Nightly icon, when started, should not create a new task icon at task manager. Firefox Nightly task should be associated to the already pinned icon. - Pinning Firefox Nightly from right click over currently running Firefox Nightly task should pin Firefox Nightly icon and not Firefox Stable icon. SOFTWARE/OS VERSIONS Linux: Arch (Linux 5.11.14-arch1-1) KDE Plasma Version: 5.21.4 KDE Frameworks 5.81.0 Qt 5.15.2 (built against 5.15.2) The wayland windowing system ADDITIONAL INFORMATION This behavior seems to have been introduced very recently, somewhat in Plasma 5.21.x, but may be triged by some Firefox update, I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435923] Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started
https://bugs.kde.org/show_bug.cgi?id=435923 --- Comment #1 from Henrique Sant'Anna --- May be related to Bug #425537 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435923] Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started
https://bugs.kde.org/show_bug.cgi?id=435923 --- Comment #2 from Henrique Sant'Anna --- Created attachment 137706 --> https://bugs.kde.org/attachment.cgi?id=137706&action=edit ~/.local/share/applications/firefox.desktop Firefox (stable) .desktop file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435923] Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started
https://bugs.kde.org/show_bug.cgi?id=435923 --- Comment #3 from Henrique Sant'Anna --- Created attachment 137707 --> https://bugs.kde.org/attachment.cgi?id=137707&action=edit /usr/share/applications/firefox-nightly.desktop Firefox Nightly .desktop file -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436595] Badly rendered rounded corners.
https://bugs.kde.org/show_bug.cgi?id=436595 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435860] Window decorations broken under non 100% scaling in wayland
https://bugs.kde.org/show_bug.cgi?id=435860 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428066] Panel show/hide animation does not work in "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=428066 Henrique Sant'Anna changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||hsanta...@gmail.com Ever confirmed|0 |1 --- Comment #2 from Henrique Sant'Anna --- I think that the difference between "auto-hide" and "windows can cover" is the animation that auto-hide shows (and the fact that auto-hide also hides from desktop). This is not a bug, but can be a feature request. Like: To enable the same animation to "windows can cover" panels as in "auto-hide" panels. Personally I would like it configurable, I don't want animations. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 --- Comment #44 from Henrique Sant'Anna --- There is a shortcut key to change focus between panels (just like Alt+Tab for windows), it is Meta+Alt+P. Pressing the shortcut (as many times as panels you need) will make the panel reaper. It is a good workaround to recover a hidden panels without having to minimize all windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426840] Panels should automatically enter "Auto-Hide" or "Windows can Cover" mode when full screen content causes them to be covered up
https://bugs.kde.org/show_bug.cgi?id=426840 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%.
https://bugs.kde.org/show_bug.cgi?id=462762 Henrique Sant'Anna changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- I don't think that Yakuake should be in front of any panel if Yakuake is not on full-screen mode (Ctrl + Shift + F11, by default). For me, the expected behavior (when not full-screen) is: The top panel should reaper when Yakuake is shown (currently doesn't happen, leaving a gap), Yakuake window geometry should start right below that panel (already happen). Then, the panel should hide again (if set to auto-hide or "windows can cover) when Yakuake got hidden. This is the behavior when using a Latte dock panel, but is not when using a native plasma panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Henrique Sant'Anna changed: What|Removed |Added Blocks||462762 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=462762 [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%.
https://bugs.kde.org/show_bug.cgi?id=462762 Henrique Sant'Anna changed: What|Removed |Added Depends on||349785 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=349785 [Bug 349785] Intelligent auto-hide mode that hides the panel only when windows are maximized or move over it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426840] Panels should automatically enter "Auto-Hide" or "Windows can Cover" mode when full screen content causes them to be covered up
https://bugs.kde.org/show_bug.cgi?id=426840 Henrique Sant'Anna changed: What|Removed |Added Blocks||462762 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=462762 [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%.
https://bugs.kde.org/show_bug.cgi?id=462762 Henrique Sant'Anna changed: What|Removed |Added Depends on||426840 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=426840 [Bug 426840] Panels should automatically enter "Auto-Hide" or "Windows can Cover" mode when full screen content causes them to be covered up -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 263607] Yakuake as default terminal doesn't open on desired path after SHIFT+F4
https://bugs.kde.org/show_bug.cgi?id=263607 Henrique Sant'Anna changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #10 from Henrique Sant'Anna --- The bug is still reproducible for yakuake 22.08.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437251] increase disable touchpad while typing time
https://bugs.kde.org/show_bug.cgi?id=437251 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437251] increase disable touchpad while typing time
https://bugs.kde.org/show_bug.cgi?id=437251 --- Comment #5 from Henrique Sant'Anna --- I have enabled the touchpad option to "Disable while typing" and it doesn't work at all on Wayland. As a test I opened Kate and started typing a sequence of keybord keys while doing some touching over touchpad. The result is that every touch over touchpad will trigger mouse clicks, which will change position from text input cursor and sometimes will select already typed text, which will lead to overwriting the selected text if I continue the typing on keyboard. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436246] New: Mouse selection clipboard (PRIMARY) works on Wayland, but klipper wont capture it
https://bugs.kde.org/show_bug.cgi?id=436246 Bug ID: 436246 Summary: Mouse selection clipboard (PRIMARY) works on Wayland, but klipper wont capture it Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: hsanta...@gmail.com Target Milestone: 1.0 Flags: Wayland+ SUMMARY GTK 3.24.29 received a path that made PRIMARY work between QT/KDE apps on Wayland. So we can mouse select text from (e.g.) Firefox and than paste it by middle clicking to (e.g.) Konsole. But right now this text is not captured by klipper (5.21.4). Klipper will not capture PRIMARY (mouse selection), no matter if from GTK apps or KDE / QT apps. STEPS TO REPRODUCE 1. Start KDE Plasma (Wayland session) and start Klipper 2. Open any app (like a GTK app or a KDE/QT app); 3. Select text with mouse cursor; 4. Open another app; 5. Use middle click to paste the text previously selected, from the first app to the second one; 6. Check Klipper, the selected (and pasted) text was not captured by Klipper. OBSERVED RESULT Klipper will not capture text from mouse selection on Wayland, even when mouse selection clipboard is working good (we can select to copy and middle click to paste). EXPECTED RESULT Klipper should capture from mouse selection on Wayland. SOFTWARE/OS VERSIONS Platform: Linux (Arch Linux) QT: 5.15.2+kde+r180-1 Desktop: KDE Plasma 5.21.4 (Wayland) ADDITIONAL INFORMATION Tested with: QT_QPA_PLATFORM=wayland klipper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434504] Klipper wayland sync highlight does not work in wayland
https://bugs.kde.org/show_bug.cgi?id=434504 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- May be related to bug #436246 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436249] New: "open klipper at mouse position" shows a menu inside a regular window on Wayland
https://bugs.kde.org/show_bug.cgi?id=436249 Bug ID: 436249 Summary: "open klipper at mouse position" shows a menu inside a regular window on Wayland Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: hsanta...@gmail.com Target Milestone: 1.0 Flags: Wayland+ Created attachment 137949 --> https://bugs.kde.org/attachment.cgi?id=137949&action=edit Klipper menu inside a regular window SUMMARY On Wayland, pressing shortcut to "open klipper at mouse position" will open a menu inside a window (with title-bar and borders) if Klipper was started by/inside notification area on Latte (dock / panel). STEPS TO REPRODUCE 1. Start KDE Plasma Wayland session; 2. Start Latte dock with an layout containing notification area widget inside a latte dock / latte panel; (be sure that isn't any other notification area widget on another plasma panel or another instance of klipper running besides the one started inside latte dock) 3. Press shortcut to "open Klipper at mouse position" OBSERVED RESULT A Window will be opened (with tittle-bar and borders) containing a menu listing clipboard contents. EXPECTED RESULT A menu should be opened (without title-bar or borders) listing clipboard contents on this menu. SOFTWARE/OS VERSIONS Platform: Linux (Arch Linux) QT: 5.15.2+kde+r180-1 Desktop: KDE Plasma 5.21.4 (Wayland) ADDITIONAL INFORMATION If not using Latte dock, but regular plasma panel, pressing shortcut to "open klipper at mouse position" will open a menu at mouse position, without title-bar or borders. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436249] "open klipper at mouse position" shows a menu inside a regular window on Wayland
https://bugs.kde.org/show_bug.cgi?id=436249 --- Comment #1 from Henrique Sant'Anna --- May be related to Bug #430662 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425537] For applications with 2 variants of desktop files remembers the wrong one as pinned
https://bugs.kde.org/show_bug.cgi?id=425537 --- Comment #2 from Henrique Sant'Anna --- As reported at Bug 435923, I had installed Firefox Nightly and Firefox stable, than trying to pin Firefox Nightly from (and to) Icons-only Task Manager will pin Firefox stable instead. Also, pinning from launcher (drag and drop) will produce the correct pinned icon (Firefox Nightly), but once the task is started the task manager will create another icon associated to the started Firefox Nightly but with wrong icon (got from Firefox stable). Trying to workaround this and get more details to this bug report, I removed any Firefox .desktop files from ~/.local/share/applications/, keeping only those in /usr/share/applications/. This didn't help and the problem persisted. So I uninstalled Firefox stable, to remove /usr/share/applications/firefox.desktop and to leave only /usr/share/applications/firefox-nightly.desktop. Than, after starting Firefox Nightly from Icons-Only Task Manager, the started task got a new icon from icon task manager, not related to Firefox Nightly, not even Firefox Stable (which was uninstalled), the new task icon was the orange icon from Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 --- Comment #26 from Henrique Sant'Anna --- Seems related to Bug 436246. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437083] Kwin_wayland crashes and kills all running apps randomly
https://bugs.kde.org/show_bug.cgi?id=437083 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429087] Entire session crashes closing all running apps if kwin_wayland crashes
https://bugs.kde.org/show_bug.cgi?id=429087 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437115] New: kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true
https://bugs.kde.org/show_bug.cgi?id=437115 Bug ID: 437115 Summary: kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true Product: kwin Version: 5.21.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: hsanta...@gmail.com Target Milestone: --- SUMMARY I updated firefox-nightly on Arch Linux to 90.0a1 (2021-05-13) and I'm getting compositor crash on KDE Plasma Wayland (kwin_wayland) every time firefox-nightly is started. Tested with firefox-nightly --safe-mode and that way kwin_wayland compositor will not crash. So I figured out that it was related to Firefox's gfx.webrender.compositor.force-enabled=true about:config setting. Opening firefox-nightly on XWayland (works) and setting gfx.webrender.compositor.force-enabled=false solved the compositor crashing, so I can start the current nightly version as an Wayland client again. STEPS TO REPRODUCE 0. Start KDE Plasma (Wayland) 1. Install and open firefox-nightly 90.0a1 (2021-05-13) 2. go to about:config and set: - gfx.webrender.compositor = true - gfx.webrender.compositor.force-enabled = true 3. Quit Firefox Nighly (Ctrl+Q) 4. Start Firefox Nightly with `MOZ_ENABLE_WAYLAND=1 firefox-nightly` 5. kwin_wayland will crash and all open apps will die. OBSERVED RESULT kwin_wayland compositor will crash when firefox-nightly is started. My previous firefox-nightly version (90.0a1 (2021-05-07)) was working good even with gfx.webrender.compositor.force-enabled=true. EXPECTED RESULT kwin_wayland should not crash when firefox-nightly starts and all open apps should not die together. SOFTWARE/OS VERSIONS Linux: 5.12.3-arch1 (Arch Linux) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2+kde+r192-1 ADDITIONAL INFORMATION Please, I would appreciate any info on how to debug this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434631] wp_viewporter support
https://bugs.kde.org/show_bug.cgi?id=434631 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=437115 CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437115] kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true
https://bugs.kde.org/show_bug.cgi?id=437115 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=434631 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437115] kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true
https://bugs.kde.org/show_bug.cgi?id=437115 --- Comment #2 from Henrique Sant'Anna --- Here is the bug report on Firefox's side: https://bugzilla.mozilla.org/show_bug.cgi?id=1711266 There we figured out that the crash is probably related to kwin_wayland wp_viewporter (un)support protocol, already requested by Bug 434631. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- This happens on Wayland or X11? What is your window manager / compositor? Is this kwin? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428383] [Wayland] Yakuake is not minimizing/hiding when clicking on empty area of desktop
https://bugs.kde.org/show_bug.cgi?id=428383 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 --- Comment #2 from Henrique Sant'Anna --- May be a duplicate of Bug 428383. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428383] [Wayland] Yakuake is not minimizing/hiding when clicking on empty area of desktop
https://bugs.kde.org/show_bug.cgi?id=428383 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=435544 -- You are receiving this mail because: You are watching all bug changes.
