[plasmashell] [Bug 405762] xesam:artist is not read as List
https://bugs.kde.org/show_bug.cgi?id=405762 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-workspace/1be4bb880fdee ||a93381eb45846a7d487e58beb93 Resolution|--- |FIXED Version Fixed In||5.17.1 Status|CONFIRMED |RESOLVED --- Comment #5 from Kai Uwe Broulik --- Git commit 1be4bb880fdeea93381eb45846a7d487e58beb93 by Kai Uwe Broulik, on behalf of Denis Sheremet. Committed on 18/10/2019 at 07:02. Pushed by broulik into branch 'Plasma/5.17'. [Media Controller] Multiple artists support According to the spec, xesam:artist should be a string array, but majority of players uses string instead. This patch adds support for both string array and string options to allow new software development according to the spec but also maintain compatibility with existing solutions. FIXED-IN: 5.17.1 Differential Revision: https://phabricator.kde.org/D24740 M +15 -1applets/mediacontroller/contents/ui/main.qml https://commits.kde.org/plasma-workspace/1be4bb880fdeea93381eb45846a7d487e58beb93 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413130] New: New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130
Bug ID: 413130
Summary: New startplasma-* apps corrupt/truncate exported shell
functions
Product: plasmashell
Version: 5.17.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: wba...@tmo.at
CC: plasma-b...@kde.org
Target Milestone: 1.0
This has been reported downstream here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1154345
https://lists.opensuse.org/opensuse-factory/2019-10/msg00137.html
If the environment contains exported shell functions, the new startplasma
applications break them, resulting in error messages when opening a shell in
the Plasma session (as a side-effect, that also breaks kdesu).
To reproduce, make sure ~/.config/plasma-locale-settings.sh exists (some script
in ~/.config/plasma-workspace/env/ will probably do as well), and add something
like this to ~/.bashrc, ~/.profile or similar:
function sayhello {
echo 'Hello!'
}
export -f sayhello
Then logout/login to Plasma. If you open Konsole, you'll get this error now:
bash: sayhello: line 1: syntax error: unexpected end of file
bash: error importing function definition for `sayhello'
Running "env" (or plasma-sourceenv.sh) inside a Plasma session gives this
output:
...
BASH_FUNC_sayhello%%=() { echo 'Hello!'
...
Correct would be:
...
BASH_FUNC_sayhello%%=() { echo 'Hello!'
}
...
(this is what I get when running "env" in a non-Plasma session)
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de Assignee|k...@davidedmundson.co.uk|aleix...@gmail.com --- Comment #1 from Fabian Vogt --- Might be possible to fix by running plasma-sourceenv.sh with an empty environment and avoiding to read /etc/profile. I'll give it a try. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 Fabian Vogt changed: What|Removed |Added Severity|normal |critical --- Comment #2 from Fabian Vogt --- Setting impact to critical as this breaks a ton of applications and scripts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 Andreas Schneider changed: What|Removed |Added CC||a...@cryptomilk.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 413131] New: Keep cookies from whitelisted domains, even when deleting cookies on close
https://bugs.kde.org/show_bug.cgi?id=413131 Bug ID: 413131 Summary: Keep cookies from whitelisted domains, even when deleting cookies on close Product: Falkon Version: 3.1.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- It would be nice if cookies from whitelisted (1.-party) domains could be kept during deletion of cookies when "delete cookies on close" is activated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 --- Comment #3 from Fabian Vogt --- (In reply to Fabian Vogt from comment #1) > Might be possible to fix by running plasma-sourceenv.sh with an empty > environment and avoiding to read /etc/profile. I'll give it a try. Actually, that might break some scripts which rely on (WAYLAND_)DISPLAY, XDG_RUNTIME_DIR or similar. It should be sufficient to print the variables in a better format, like delimited by \0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 Christian Hartmann changed: What|Removed |Added CC||chris-hartm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413126] Filter mask is so heavy
https://bugs.kde.org/show_bug.cgi?id=413126 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- You may get improved performance by using a filter layer instead of a mask, so you don't have the masking operations performed at the same time. You can group your paint layer and put a filter mask on top of it to limit the filter scope and you can also apply a transparency mask to the group layer. That way, any transforms/moves will only be applied to the paint layer. If you actually want the transforms/moves to be applied to the mask components then I've misunderstood what you're trying to do. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413129] gtk apps not respecting border width setting
https://bugs.kde.org/show_bug.cgi?id=413129 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #2 from Kai Uwe Broulik --- Client side decorations are the client's responsibility. Rather than having *no* resize frame whatsoever, we chose to make a visible border. This will be fixed once we support the GTK shadow stuff properly but for now that's the best we can do. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 Fabian Vogt changed: What|Removed |Added URL||https://phabricator.kde.org ||/D24750 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled and hover-zoom at 0%, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 --- Comment #3 from Michail Vourlakos --- Lock button did it help? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413132] New: GTK3-Black checkbox on breeze theme
https://bugs.kde.org/show_bug.cgi?id=413132 Bug ID: 413132 Summary: GTK3-Black checkbox on breeze theme Product: Breeze Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: s1r51ck...@gmail.com Target Milestone: --- Created attachment 123311 --> https://bugs.kde.org/attachment.cgi?id=123311&action=edit Gtk 3 breeze theme - black checkbox SUMMARY After update plasma to version 5.17.0, selecting breeze as gtk3 theme, shows black checkboxes with some glitches when I move the mouse over them. I prepared a short explanatory video STEPS TO REPRODUCE 1. Open settings -> Application style -> Gnome/gtk application style SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux KDE Plasma Version: KDE 5.63.0 / Plasma 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413132] GTK3-Black checkbox on breeze theme
https://bugs.kde.org/show_bug.cgi?id=413132 s1r51ck...@gmail.com changed: What|Removed |Added CC||s1r51ck...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413132] GTK3-Black checkbox on breeze theme
https://bugs.kde.org/show_bug.cgi?id=413132 s1r51ck...@gmail.com changed: What|Removed |Added CC|s1r51ck...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400295] Some tray icons aren't highlighted upon hovering over them with mouse cursor
https://bugs.kde.org/show_bug.cgi?id=400295 --- Comment #5 from Konrad Materka --- Two left: * Battery Monitor * Notification It is not trivial to fix. All other plasmoids are using PlasmaCore.IconItem which has this effect build in (it is enough to set "active" to true). Battery Monitor and Notification are rendering their own icons, using PlasmaCore.SvgItem, PlasmaCore.Svg and other. AFAIK there is no easy way to set this mouse over effect easily. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413053] Can't remove Discover Update Notifier from System Tray
https://bugs.kde.org/show_bug.cgi?id=413053 s1r51ck...@gmail.com changed: What|Removed |Added CC||s1r51ck...@gmail.com --- Comment #2 from s1r51ck...@gmail.com --- (In reply to Nate Graham from comment #1) > Yeah, this is a side effect of it being an executable rather than a system > tray applet. Hi Nate first of all congratulations as always for the excellent work you do to create and make always better Kde. I would like to ask you how you could disable this behavior? The "/usr/lib/DiscoverNotifier" process starts with "CGroup: /user.slice/user-1000.slice/session-2.scope" -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 413039] Critical: could not load fallback mirror list from QUrl
https://bugs.kde.org/show_bug.cgi?id=413039 --- Comment #23 from Ben Cooksley --- The URL has now been changed to clearly indicate that the installer is unsupported. This also has the effect of breaking the /stable/ URLs which had previously remained working (due to special code dedicated to keeping old links alive) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413133] New: Plasma always forces its own font configuration breaking system one
https://bugs.kde.org/show_bug.cgi?id=413133 Bug ID: 413133 Summary: Plasma always forces its own font configuration breaking system one Product: systemsettings Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: kurmi...@libero.it CC: unassigned-b...@kde.org Target Milestone: --- SUMMARY Since the last upgrade on Arch Linux, Plasma Desktop is forcing it's own fontconfig on local settings. In details, it is overwriting antialiasing 'on', hintslight and subpixel rendering 'rgb'. I'm aware that this is the optimal configuration in most cases, but there's also some particular cases where this configuration is not chosen by the user to due his/her specific system characteristics. The bad behavior of this new upgrade is that even if I choose to NOT use kcm font settings, plasma keeps overwriting ~/.config/fontconfig/fonts.conf with its own options. This is also breaking my system-wide settings that I accurately wrote inside /etc/fonts/conf.d/ having the purpose to avoid to reconfig fonts for every user on my Linux installation. In fact, having Plasma to use its local configuration made fonts looks very bad on my systems, especially inside GTK browsers like Firefox and Chromium. The only way I can avoid this behavior is to symlink ~/config/fontconfig to /dev/null, which is unacceptable on a desktop environment like Plasma that claims to be highly customizable. Doing that I got a good looking fonts having all applications to rely only on system fontconfig, like it should be in my specific context where I configured fonts directly in /etc/fonts and do NOT want others to interfere with it. STEPS TO REPRODUCE 1. By default Plasma Desktop write it's own options inside ~/config/fontconfig/fonts.conf 2. Disable options under fonts kcm (plasma systemsettings5) OBSERVED RESULT ~/config/fontconfig/fonts.conf contains the default settings, which I don't want. Besides, If I empty it manually, Plasma will rewrite it when I relog into the session or enter into fonts kcm. EXPECTED RESULT Plasma should leave that file blank and does NOT have to interfere with system-wide configuration. ADDITIONAL INFORMATIONS I remember that font kcm had some options where you specified to leave the system configuration. It seems that these ones were removed? Why? Besides, why antialiasing is enabling the other settings like subpixel rendering and hinting style? Do you know that these options are independent? Maybe I want to configure hints 'full' leaving antialiasing 'off'. But this is not intended to be done inside the kcm because disabling antialiasing is graying out the others. The concept is just wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413019] Widget positioning is broken when switching to the external monitor
https://bugs.kde.org/show_bug.cgi?id=413019 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #5 from Kai Uwe Broulik --- I can confirm on my laptop where SDDM has a different resolution from the desktop. I log in, you can see KSplash shifting as the resolutions change and in the end my widgets are all stuck to the left side of the screen in a square. I suspect the fact that resolutions change during plasmashell startup has it remember the old resolution and then try to apply its heuristic of keeping screen distance same, which might also break when the aspect ratio change. I wonder if merely putting a m_containment->corona()->isStartupCompleted() check before remembering geometryBeforeResolution already mitigates this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413134] New: Night colors disabled when we open gamma in settings
https://bugs.kde.org/show_bug.cgi?id=413134 Bug ID: 413134 Summary: Night colors disabled when we open gamma in settings Product: kwin Version: 5.17.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: floreal@flo-art.fr Target Milestone: --- SUMMARY Night colors are disabled while we open gamma in settings STEPS TO REPRODUCE 1. Open system settings 2. Select "Display and Monitor" 3. Go to "Color night", check activate night color and select "Constant" for Mode 4. Apply 5. Go to Gamma item OBSERVED RESULT After step 4, color change to the desired temperature. After step 5, temperature go back to the default one without correction. The temperature never go back even we change tab or close settings. The only way to fix it is to go back to night color in settings and re-apply it. EXPECTED RESULT Temparature should be kept when we go to gamma, or at least reapplied when we leave this settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 18.04 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413134] Night colors disabled when we open gamma in settings
https://bugs.kde.org/show_bug.cgi?id=413134 Floreal changed: What|Removed |Added Target Milestone|--- |5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413134] Night colors disabled when we open gamma in settings
https://bugs.kde.org/show_bug.cgi?id=413134 Floreal changed: What|Removed |Added CC||floreal@flo-art.fr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413019] Widget positioning is broken when switching to the external monitor
https://bugs.kde.org/show_bug.cgi?id=413019 --- Comment #7 from Oleg Kapitonov --- Created attachment 123314 --> https://bugs.kde.org/attachment.cgi?id=123314&action=edit Screenshot after switchng to the external mpnitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413135] New: Battery list has a scrollbar
https://bugs.kde.org/show_bug.cgi?id=413135 Bug ID: 413135 Summary: Battery list has a scrollbar Product: plasmashell Version: 5.17.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: i...@guoyunhe.me CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 123313 --> https://bugs.kde.org/attachment.cgi?id=123313&action=edit scrollbar in battery list SUMMARY Have a Thinkpad T480 with two battery. The battery list has a scrollbar, and it is placed very close to the texts and capacity bars. STEPS TO REPRODUCE 1. Use a laptop with two battery or connect wireless mouses that has battery info. 2. Set scale factor to 1.5. 3. Check the batter list. OBSERVED RESULT The battery list has two battery rows and here is a scrollbar very close to texts. EXPECTED RESULT Not show scrollbar or leave some space between scrollbar and texts. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20191014 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.5-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 31.1 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413019] Widget positioning is broken when switching to the external monitor
https://bugs.kde.org/show_bug.cgi?id=413019 --- Comment #6 from Oleg Kapitonov --- Created attachment 123312 --> https://bugs.kde.org/attachment.cgi?id=123312&action=edit Screenshot before switching to the external monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413019] Widget positioning is broken when switching to the external monitor
https://bugs.kde.org/show_bug.cgi?id=413019 --- Comment #8 from Oleg Kapitonov --- My laptop screen resolution is 1366x768 External monitor resolution is 1280x1024 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408253] Plasma Panel Starts Flashing (Randomly?) after update from OpenSUSE 15.0 to 15.1
https://bugs.kde.org/show_bug.cgi?id=408253 --- Comment #6 from javascriptj...@hotmail.com --- Yes, disabling compositing stops the flashing, but that's not a solution for me as I need transparent windows to be able to compare one browser page to another. Apparently setting compositing to use XRender solves the problem, but both OpenGL 2.0 and 3.1 suffer from it. So can the bug be reopened or do I need to file a new one against compositing? I don't think it's OK to have the default compositing methods broken, with a commonly used feature like panel auto-hide. It worked fine in OpenSUSE 15.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408253] Plasma Panel Starts Flashing (Randomly?) after update from OpenSUSE 15.0 to 15.1
https://bugs.kde.org/show_bug.cgi?id=408253 javascriptj...@hotmail.com changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #7 from javascriptj...@hotmail.com --- Question about compositing has been answered. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 412556] is not possible to have networkmanager to ask username for wireless
https://bugs.kde.org/show_bug.cgi?id=412556 --- Comment #4 from pier andre --- (In reply to Jan Grulich from comment #2) > What type of wireless security do you use? Is that for WPA/WPA2 enterprise? this https://susepaste.org/52045119 security=WPA/WPA2 enterprise autentication=protected EAP/PEAP inner autentication=MSCHAPv2 -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 381975] "Always On Top" isn't saved, and is shown in wrong state upon relaunch
https://bugs.kde.org/show_bug.cgi?id=381975 --- Comment #11 from javascriptj...@hotmail.com --- Looks like some major changes have happened to kruler, but this bug still lives. KDE Plasma version: 5.12.8 KDE Framework version: 5.55.0 QT Version 5.9.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 412556] [RFE] Add option to always ask for a username when connecting to a wireless network
https://bugs.kde.org/show_bug.cgi?id=412556 Jan Grulich changed: What|Removed |Added Summary|is not possible to have |[RFE] Add option to always |networkmanager to ask |ask for a username when |username for wireless |connecting to a wireless ||network --- Comment #5 from Jan Grulich --- This can be in theory implemented, but because NetworkManager doesn't support anything like that, we would be implementing this feature ourself, which frankly is really specific use-case and it's unlikely going to be implemented anytime soon. -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 413136] New: Can't move kruler off screen or change it's length!
https://bugs.kde.org/show_bug.cgi?id=413136 Bug ID: 413136 Summary: Can't move kruler off screen or change it's length! Product: kruler Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: soe...@pprojekt.de Reporter: javascriptj...@hotmail.com Target Milestone: --- SUMMARY Can't move kruler off screen or change it's length. Thus, it's difficult to measure anything from a fixed point on the ruler. I can measure from something other than the point I want, but that's a hassle. STEPS TO REPRODUCE 1. Open kruler 2. Find that you can't move it off screen or change its length OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE 15.1 (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 411177] VPN password is not displayed even if store passwords is checked
https://bugs.kde.org/show_bug.cgi?id=411177 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #6 from Jan Grulich --- (In reply to prangija from comment #5) > Am I the only one who still has this issue? > I have the latest versions of KDE Plasma (5.17) and network manager > (1.20.4), but I'm still facing the same issues (password is not being > remembered and username field has the "hide" icon instead of password field). Is this for Openconnect? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408253] Plasma Panel Starts Flashing (Randomly?) after update from OpenSUSE 15.0 to 15.1
https://bugs.kde.org/show_bug.cgi?id=408253 Christoph Feck changed: What|Removed |Added Product|plasmashell |kwin Component|Panel |compositing Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Target Milestone|1.0 |--- --- Comment #8 from Christoph Feck --- Thanks for the update; reassigning. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413132] GTK3-Black checkbox on breeze theme
https://bugs.kde.org/show_bug.cgi?id=413132 Buovjaga changed: What|Removed |Added CC||todven...@suomi24.fi Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Buovjaga --- I repro on Arch Linux with Breeze theme. First noticed in Firefox. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 412556] [RFE] Add option to always ask for a username when connecting to a wireless network
https://bugs.kde.org/show_bug.cgi?id=412556 Jan Grulich changed: What|Removed |Added Severity|grave |wishlist Priority|NOR |LO -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413137] New: Global menu and fcitx make Krita's menu unusable
https://bugs.kde.org/show_bug.cgi?id=413137 Bug ID: 413137 Summary: Global menu and fcitx make Krita's menu unusable Product: krita Version: 4.2.7.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: wil...@wimiso.nl Target Milestone: --- Created attachment 123315 --> https://bugs.kde.org/attachment.cgi?id=123315&action=edit Screenshot of Krita without menu SUMMARY When fcitx (East-Asian / CJK input method) is used as the Qt IM module, and the Plasma global menu is active, Krita's global does not appear. Because the menu does not appear in the Krita window itself either, this makes Krita unusable for fcitx users, because menu commands are completely inaccessible. This was reported before by Vladimir Yerilov in an unrelated closed bug (https://bugs.kde.org/show_bug.cgi?id=408015#c34). STEPS TO REPRODUCE (Tested on a freshly installed Kubuntu 19.10 VM.) 1. Right-click on the desktop, and do `Add Panel > Application Menu Bar`. 2. Open Konsole and verify the global menu bar works. 3. Install fcitx: `sudo apt install fcitx-bin`. 4. Install Krita: `sudo apt install krita`. 5. Run `QT_IM_MODULE=fcitx krita`. OBSERVED RESULT No menu is present in the global menu, and the menu is not present in the Krita window either (see attached screenshot). Hence, the menu cannot be accessed. In any other KDE/Qt applications (e.g. Konsole, Dolphin, Kate, Gwenview, ...) the global menu works correctly. EXPECTED RESULT The global menu is present, or alternatively the menu is at least present in the Krita window itself. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 (Eoan) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Krita Version: 4.2.7.1 ADDITIONAL INFORMATION It looks like fcitx does not actually need to be running to trigger the bug. It being installed (and QT_IM_MODULE being set to `fcitx`) is enough to trigger the bug. I do not know if this is a bug in the QPA, fcitx, or Krita, but I reported it in Krita due to the fact that it occurs only in Krita (and not in other applications). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413138] New: MinimizeAll KWin script stopped restoring windows
https://bugs.kde.org/show_bug.cgi?id=413138 Bug ID: 413138 Summary: MinimizeAll KWin script stopped restoring windows Product: plasmashell Version: 5.17.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: per...@perk11.info CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Enable MinimizeAll script 2. Assign it to shortcut 3. Press the shortcut, the windows are now minimized 4. Press the shortcut again OBSERVED RESULT The windows are not restored, all the windows are still minimized. EXPECTED RESULT The windows are restored to the state they were in before minimization. This is how it used to work in 5.16, but it broke after updating to 5.17.0 SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 4.15.0-65-generic OS Type: 64-bit Processors: 8 × Intel® Xeon® CPU E3-1231 v3 @ 3.40GHz Memory: 31.4 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 411177] VPN password is not displayed even if store passwords is checked
https://bugs.kde.org/show_bug.cgi?id=411177 --- Comment #7 from prangija --- Yes, I have issues with Openconnect VPN connections. I can't be sure for others as I'm using just Openconnect currently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413139] New: Hard lockup on screen lock
https://bugs.kde.org/show_bug.cgi?id=413139 Bug ID: 413139 Summary: Hard lockup on screen lock Product: plasmashell Version: 5.17.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ciaran.gilles...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) (Compiled from sources) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 4.15.0-65-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: While I was sleeping, the lock screen crashed, showing the time of the crash and refusing input. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f32c3232800 (LWP 1586))] Thread 28 (Thread 0x7f32467fc700 (LWP 1801)): #0 0x7f32b9f9c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5635485e15f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5635485e15a0, cond=0x5635485e15c8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5635485e15c8, mutex=0x5635485e15a0) at pthread_cond_wait.c:655 #3 0x7f32bd06bb0b in QWaitConditionPrivate::wait (deadline=..., this=0x5635485e15a0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x563547a52b60, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f32bd06be19 in QWaitCondition::wait (this=0x563547a52b68, mutex=0x563547a52b60, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f32c108aec8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f32c108b2fa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f32bd064b72 in QThreadPrivate::start (arg=0x563547a52ae0) at thread/qthread_unix.cpp:360 #9 0x7f32b9f966db in start_thread (arg=0x7f32467fc700) at pthread_create.c:463 #10 0x7f32bc96188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f322726f700 (LWP 1800)): #0 0x7f32b9f9c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5635486977ac) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x563548697758, cond=0x563548697780) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x563548697780, mutex=0x563548697758) at pthread_cond_wait.c:655 #3 0x7f329d625a3b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f329d6258a7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f32b9f966db in start_thread (arg=0x7f322726f700) at pthread_create.c:463 #6 0x7f32bc96188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f3246ffd700 (LWP 1790)): #0 0x7f32b9f9c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x563547daa79c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x563547daa748, cond=0x563547daa770) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x563547daa770, mutex=0x563547daa748) at pthread_cond_wait.c:655 #3 0x7f329d625a3b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f329d6258a7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f32b9f966db in start_thread (arg=0x7f3246ffd700) at pthread_create.c:463 #6 0x7f32bc96188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f32477fe700 (LWP 1789)): #0 0x7f32b9f9c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x563547daa79c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x563547daa748, cond=0x563547daa770) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x563547daa770, mutex=0x563547daa748) at pthread_cond_wait.c:655 #3 0x7f329d625a3b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f329d6258a7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f32b9f966db in start_thread (arg=0x7f32477fe700) at pthread_create.c:463 #6 0x7f32bc96188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f3247fff700 (LWP 1788)): #0 0x7f32b9f9c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x563547daa79c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x563547daa748, cond=0x563547daa770) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x563547daa770, mutex=0x563547daa748) at pthread_cond_wait.c:655 #3 0x7f329d625a3b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f329d6258a7 in
[plasmashell] [Bug 413018] Plasma crashes in slideshow
https://bugs.kde.org/show_bug.cgi?id=413018 --- Comment #18 from Kai Uwe Broulik --- *** Bug 413139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413139] Hard lockup on screen lock
https://bugs.kde.org/show_bug.cgi?id=413139 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@privat.broulik.de Resolution|--- |DUPLICATE --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 413018 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413137] Global menu and fcitx make Krita's menu unusable
https://bugs.kde.org/show_bug.cgi?id=413137 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |DUPLICATE --- Comment #1 from Boudewijn Rempt --- I'm sorry, but it's not really useful to report a bug that has been reported before again... We just cannot do anything about this in Krita. There really is no code in Krita that does anything special with the menu. *** This bug has been marked as a duplicate of bug 408015 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 Boudewijn Rempt changed: What|Removed |Added CC||wil...@wimiso.nl --- Comment #42 from Boudewijn Rempt --- *** Bug 413137 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413140] New: Plasma startup failed
https://bugs.kde.org/show_bug.cgi?id=413140 Bug ID: 413140 Summary: Plasma startup failed Product: plasmashell Version: 5.17.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: joc...@proimi.org.ar CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) (Compiled from sources) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: -- Unit cups.socket has finished shutting down. oct 18 09:05:26 jochoapc systemd[1]: Stopping CUPS Scheduler. -- Subject: Unit cups.socket has begun shutting down -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit cups.socket has begun shutting down. oct 18 09:05:26 jochoapc systemd[1]: Listening on CUPS Scheduler. -- Subject: Unit cups.socket has finished start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit cups.socket has finished starting up. -- -- The start-up result is RESULT. oct 18 09:05:26 jochoapc systemd[1]: Started CUPS Scheduler. -- Subject: Unit cups.service has finished start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit cups.service has finished starting up. -- -- The start-up result is RESULT. oct 18 09:05:26 jochoapc systemd[1]: Started Make remote CUPS printers available locally. -- Subject: Unit cups-browsed.service has finished start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit cups-browsed.service has finished starting up. -- -- The start-up result is RESULT. oct 18 09:05:26 jochoapc colord[946]: failed to get session [pid 3096]: No data available oct 18 09:05:26 jochoapc colord[946]: failed to get session [pid 3096]: No data available oct 18 09:05:26 jochoapc colord[946]: failed to get session [pid 3096]: No data available oct 18 09:05:26 jochoapc rsyslogd[787]: [origin software="rsyslogd" swVersion="8.32.0" x-pid="787" x-info="http://www.rsyslog.com";] rsyslogd was HUPed -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9c519ae800 (LWP 1917))] Thread 6 (Thread 0x7f9c17ce5700 (LWP 2227)): #0 0x7f9c487159f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b83093dd54) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b83093dd00, cond=0x55b83093dd28) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b83093dd28, mutex=0x55b83093dd00) at pthread_cond_wait.c:655 #3 0x7f9c4b7e4b0b in QWaitConditionPrivate::wait (deadline=..., this=0x55b83093dd00) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55b8302e8050, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f9c4b7e4e19 in QWaitCondition::wait (this=0x55b8302e8058, mutex=0x55b8302e8050, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f9c4f803ec8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f9c4f8042fa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f9c4b7ddb72 in QThreadPrivate::start (arg=0x55b8302e7fd0) at thread/qthread_unix.cpp:360 #9 0x7f9c4870f6db in start_thread (arg=0x7f9c17ce5700) at pthread_create.c:463 #10 0x7f9c4b0da88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f9c264e9700 (LWP 2199)): #0 0x7f9c487159f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b8305b2e5c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b8305b2e08, cond=0x55b8305b2e30) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b8305b2e30, mutex=0x55b8305b2e08) at pthread_cond_wait.c:655 #3 0x7f9c275992cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f9c27598ff7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f9c4870f6db in start_thread (arg=0x7f9c264e9700) at pthread_create.c:463 #6 0x7f9c4b0da88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f9c33fff700 (LWP 2194)): #0 0x7f9c4504d649 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9c45006995 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9c450074fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9c450076dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9c4ba209db in QEventDispatcherGlib::processEvents (this=0x7f9c28000b20, flags=..
[plasmashell] [Bug 413140] Plasma startup failed
https://bugs.kde.org/show_bug.cgi?id=413140 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@privat.broulik.de Status|REPORTED|RESOLVED --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 413018 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413018] Plasma crashes in slideshow
https://bugs.kde.org/show_bug.cgi?id=413018 Kai Uwe Broulik changed: What|Removed |Added CC||joc...@proimi.org.ar --- Comment #19 from Kai Uwe Broulik --- *** Bug 413140 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413091] Information Panel shows almost no information inside Trash
https://bugs.kde.org/show_bug.cgi?id=413091 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Nate Graham --- (In reply to Méven Car from comment #3) > So the size should be the size of files in the trash, modified last time a > file was added to the trash. > The accessed date is kind of weird for a trash, last time you opened the > trash has not much value. Yeah for the trash itself, maybe we should just not show this piecee of information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371245] Thunderbird doesn't show email count at system tray when
https://bugs.kde.org/show_bug.cgi?id=371245 Konrad Materka changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED CC||mate...@gmail.com --- Comment #2 from Konrad Materka --- I'm closing this as all Thunderbird tray extensions are not maintained or are not working with the latest version. Please reopen if there is working extension and is malfunctioning. In that case, please also check if exnesion is using XEmbed for tray icon. The easiest way is to kill xembedsniproxy, if icon disappears then XEmbed is used. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413133] Plasma always forces its own font configuration breaking system one
https://bugs.kde.org/show_bug.cgi?id=413133 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||bhus...@gmail.com, ||n...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413141] New: Plasma crashes when booting 5.17
https://bugs.kde.org/show_bug.cgi?id=413141 Bug ID: 413141 Summary: Plasma crashes when booting 5.17 Product: plasmashell Version: 5.17.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kristopher.i...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 4.15.0-65-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Booting with nothing running yet and Plasma crashes. After booting the KDE Crash Handler appears but Plasma appears to function normally. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f799ab06800 (LWP 1238))] Thread 5 (Thread 0x7f796fa92700 (LWP 1356)): #0 0x7f79918759f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557a5a2652f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x557a5a2652a8, cond=0x557a5a2652d0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x557a5a2652d0, mutex=0x557a5a2652a8) at pthread_cond_wait.c:655 #3 0x7f7974fa02cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f7974f9fff7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f799186f6db in start_thread (arg=0x7f796fa92700) at pthread_create.c:463 #6 0x7f799423a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f797d6ac700 (LWP 1310)): #0 0x7f79942290b4 in __GI___libc_read (fd=18, buf=0x7f797d6abb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f798e1ab2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f798e1660b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f798e166570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f798e1666dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7994b809db in QEventDispatcherGlib::processEvents (this=0x7f797b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f7994b20eaa in QEventLoop::exec (this=this@entry=0x7f797d6abd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f799493c3ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f799840acb5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f799493db72 in QThreadPrivate::start (arg=0x557a5a297170) at thread/qthread_unix.cpp:360 #10 0x7f799186f6db in start_thread (arg=0x7f797d6ac700) at pthread_create.c:463 #11 0x7f799423a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f797f734700 (LWP 1250)): #0 0x7f799422dbf9 in __GI___poll (fds=0x7f7978004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f798e1665c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f798e1666dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7994b809db in QEventDispatcherGlib::processEvents (this=0x7f7978000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7994b20eaa in QEventLoop::exec (this=this@entry=0x7f797f733d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f799493c3ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f7995c340e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f799493db72 in QThreadPrivate::start (arg=0x7f7995eabd80) at thread/qthread_unix.cpp:360 #8 0x7f799186f6db in start_thread (arg=0x7f797f734700) at pthread_create.c:463 #9 0x7f799423a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f7985972700 (LWP 1241)): #0 0x7f799422dbf9 in __GI___poll (fds=0x7f7985971ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f799953a747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f799953c36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f7988343f00 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f799493db72 in QThreadPrivate::start (arg=0x557a5a049060) at thread/qthread_unix.cpp:360 #5 0x7f799186f6db in start_thread (arg=0x7f7985972700) at pthread_create.c:463 #6 0x7f799423a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f799ab06800 (LWP 1238)): [KCrash Handler] #6 0x7f7994ae9dc0 in QSortFilterProxyModelPrivate::build_source_to_proxy_mapping (proxy_to_source=..., source_to_proxy=..., this=0x557a5a6
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 Fabian Vogt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-workspace/595ab88bc2ee0 ||ed32da577ec8ae22efee90865b5 --- Comment #4 from Fabian Vogt --- Git commit 595ab88bc2ee0ed32da577ec8ae22efee90865b5 by Fabian Vogt. Committed on 18/10/2019 at 12:38. Pushed by fvogt into branch 'Plasma/5.17'. Fix reading environment variables with newline Summary: Use '\0' as separator as '\n' is likely to appear in values. Test Plan: /etc/profile.d/mc.sh exported an mc() function, which resulted in "syntax error: unexpected end of file" in the Plasma session. Now the mc function is correctly set in the environment. Reviewers: #plasma, apol, davidedmundson, adridg Reviewed By: #plasma, apol, davidedmundson, adridg Subscribers: davidedmundson, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D24750 M +1-1startkde/plasma-sourceenv.sh M +1-1startkde/startplasma.cpp https://commits.kde.org/plasma-workspace/595ab88bc2ee0ed32da577ec8ae22efee90865b5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392170] Vertical and shifted tray icons after changing entries visibility and Panel position
https://bugs.kde.org/show_bug.cgi?id=392170 Konrad Materka changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||mate...@gmail.com --- Comment #4 from Konrad Materka --- I was not able to reproduce. Can you test again with latest version? Can you test using new user? Do you have any non-standard plasmoids installed? Any configuration changes? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413142] New: Monitor settings: "Monitors" are too small to hold text
https://bugs.kde.org/show_bug.cgi?id=413142 Bug ID: 413142 Summary: Monitor settings: "Monitors" are too small to hold text Product: kwin Version: 5.17.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@philipp-wagner.com Target Milestone: --- Created attachment 123316 --> https://bugs.kde.org/attachment.cgi?id=123316&action=edit screenshot In 5.17 the monitor settings was rewritten. Unfortunately, the displayed "monitors" in the UI are too small to hold the name of the monitor. Please have a look at the attached picture, it's harder to describe than to see. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20191016 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.5-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413143] New: Equalizer/Bandpass effects missing translation
https://bugs.kde.org/show_bug.cgi?id=413143 Bug ID: 413143 Summary: Equalizer/Bandpass effects missing translation Product: kdenlive Version: 19.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: das.j...@gmail.com Target Milestone: --- Created attachment 123317 --> https://bugs.kde.org/attachment.cgi?id=123317&action=edit Settings view of Bandpass audio effect SUMMARY Several Audio effects without translation. STEPS TO REPRODUCE 1. Open Effects tab 2. Go to Audio 3. Select one of the Equaliser/Bandpass effects. OBSERVED RESULT There is I18N_EMPTY_MESSAGE everywhere... so you don't know, what each slider does. Another thing is the lower most thingy in that window (Bandpass) doesn't stop moving as if it were loading something... EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413089] Magnetic Selection Tool can't be used after another tool is used and then can crash
https://bugs.kde.org/show_bug.cgi?id=413089 Kuntal Majumder changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||hello...@disroot.org --- Comment #1 from Kuntal Majumder --- *** This bug has been marked as a duplicate of bug 413035 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413035] Magnetic selection tool doesn't remove half-finished paths when switching away from the tool
https://bugs.kde.org/show_bug.cgi?id=413035 Kuntal Majumder changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #3 from Kuntal Majumder --- *** Bug 413089 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 329076] Unable to unlock, widgets missing
https://bugs.kde.org/show_bug.cgi?id=329076 Arnaud Frézet changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||arnaudfre...@gmail.com Resolution|FIXED |--- --- Comment #15 from Arnaud Frézet --- Hi, i think the issue is not fixed or has reappeared recently. I had the same issue on KDE Neon 18.04 KDE 5.17. The symptoms are the same as mentioned early : when the PC woke up, the login screen appears but there is no input to type password, neither the time or date. I have the issue only on the work computer which is a Dell computer... I am not surprised at all (Dell computer are a nightmare on Linux...), but the bug is quite annoying Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412896] Crash while double clicking and removing a magnetic lasso point/node
https://bugs.kde.org/show_bug.cgi?id=412896 --- Comment #3 from Kuntal Majumder --- You didn't close the cage right? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362077] seperate widgets and "tray icons"
https://bugs.kde.org/show_bug.cgi?id=362077 Konrad Materka changed: What|Removed |Added CC||mate...@gmail.com --- Comment #10 from Konrad Materka --- Icons are now ordered by category and then alphabetically: https://phabricator.kde.org/D11352 Should we close this ticket? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395758] NM window (and other windows) of tray symbols don't open
https://bugs.kde.org/show_bug.cgi?id=395758 Konrad Materka changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||mate...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #3 from Konrad Materka --- Is this is issue still affecting you? Can you check the latest version of Plasma? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362077] seperate widgets and "tray icons"
https://bugs.kde.org/show_bug.cgi?id=362077 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #11 from Nate Graham --- There are still a few requests from the original request that haven't gotten done: - separate them visually somehow (maybe with a subtle vertical or horizontal separator line?) - provide an option to hide all items from the system tray or all SNIs -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413053] Can't remove Discover Update Notifier from System Tray
https://bugs.kde.org/show_bug.cgi?id=413053 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #3 from David Edmundson --- You should see a combo box under "Entries" which can be set to Hidden. Does this work? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413053] Can't remove Discover Update Notifier from System Tray
https://bugs.kde.org/show_bug.cgi?id=413053 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from Nate Graham --- I think Sebastian wants the ability to remove it entirely, not just banish it to the expanded popup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413130] New startplasma-* apps corrupt/truncate exported shell functions
https://bugs.kde.org/show_bug.cgi?id=413130 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||5.17.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397949] System Tray - New entries will not show until re-opening the settings
https://bugs.kde.org/show_bug.cgi?id=397949 Konrad Materka changed: What|Removed |Added CC||mate...@gmail.com Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Konrad Materka --- I cannot reproduce, probably fixed as part of BUG 390890 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362077] seperate widgets and "tray icons"
https://bugs.kde.org/show_bug.cgi?id=362077 --- Comment #12 from Konrad Materka --- True, but with this recent change it was decided (?) that SNI and applets are mixed. Sure, this can be changed, so we can keep this ticket open. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412896] Crash while double clicking and removing a magnetic lasso point/node
https://bugs.kde.org/show_bug.cgi?id=412896 --- Comment #4 from M --- No, I didn't. This can happen on the first or second anchor, before the loop is closable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412896] Crash while double clicking and removing a magnetic lasso point/node
https://bugs.kde.org/show_bug.cgi?id=412896 --- Comment #5 from Kuntal Majumder --- Ahh I get the problem now, another edge case that I missed, :D -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402682] If Clipboard is active in system tray, gvim crashes
https://bugs.kde.org/show_bug.cgi?id=402682 Konrad Materka changed: What|Removed |Added Status|REPORTED|RESOLVED CC||mate...@gmail.com Resolution|--- |WORKSFORME --- Comment #1 from Konrad Materka --- I checked with gvim 8.0.1453, it was not crashing. If this happens again, please send more detailed information, including exact steps how to reproduce. It is probably a good idea to report this bug to gvim team. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401016] Touchpad plasmoid popup remains open after losing focus
https://bugs.kde.org/show_bug.cgi?id=401016 Konrad Materka changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||mate...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #2 from Konrad Materka --- I testes on Plasma 5.17. Clicking on touchpad does not show anything, only switches on/off the touchpad. Can you test on latest version and provide more detailed information? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 413144] New: Global shortcuts revert to defaults upon login
https://bugs.kde.org/show_bug.cgi?id=413144 Bug ID: 413144 Summary: Global shortcuts revert to defaults upon login Product: amarok Version: 2.9.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts Assignee: amarok-bugs-d...@kde.org Reporter: ing...@gmx.de Target Milestone: kf5 SUMMARY Some of the default global shortcuts of Amarok conflict with personal shortcuts I use for the Cinnamon desktop, e.g. Win-M (Mute Volume vs. Maximize Window) or Win-L (Love@LastFM vs. Lock Screen). Setting these Amarok shortcuts to "Custom: None" makes my desktop hotkeys functional again, but after the next system start the Amarok defaults are back. STEPS TO REPRODUCE 1. In Amarok, go to Settings > Configure Shortcuts 2. Select some global shortcut, e.g. "Mute Volume" 3. Change to Custom: None 4. Save 5. Reboot (or probably logout/login) 6. In Amarok, go to Settings > Configure Shortcuts OBSERVED RESULT The old default shortcut is back EXPECTED RESULT The custom setting should be preserved SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 (x86-64) Desktop: Cinnamon 4.2.4 KDE Frameworks Version: 4.14.38 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413145] New: No Context Help button in Aurorae themes
https://bugs.kde.org/show_bug.cgi?id=413145 Bug ID: 413145 Summary: No Context Help button in Aurorae themes Product: kwin Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: mar...@greyserv.net Target Milestone: --- SUMMARY Aurorae, from what I could gather, supports the Context Help button via help.svg, but despite that it does not use it and displays nothing where the Context Help button is supposed to be. This bug apparently existed for the Shade button as well for a long time before being fixed. STEPS TO REPRODUCE 1. Add "Context Help" to the menu bar. 2. Install an Aurorae theme. 3. Enable it. OBSERVED RESULT There is no context help button. EXPECTED RESULT The context help button should exist as specified by help.svg in the theme. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413145] No Context Help button in Aurorae themes
https://bugs.kde.org/show_bug.cgi?id=413145 --- Comment #1 from Alison Watson --- I somehow managed to write "menu bar" instead of "window decorations." -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Nate Graham changed: What|Removed |Added CC||s1r51ck...@gmail.com --- Comment #29 from Nate Graham --- *** Bug 413132 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413132] GTK3-Black checkbox on breeze theme
https://bugs.kde.org/show_bug.cgi?id=413132 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 412078 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 408580] NOAA environmental visualization picture of the day not working
https://bugs.kde.org/show_bug.cgi?id=408580
Guo Yunhe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Latest Commit||https://commits.kde.org/kde
||plasma-addons/4324705766051
||3cbc942505eeba6e24c6811d0d9
--- Comment #9 from Guo Yunhe ---
Git commit 43247057660513cbc942505eeba6e24c6811d0d9 by Guo Yunhe.
Committed on 18/10/2019 at 14:11.
Pushed by guoyunhe into branch 'master'.
Fix NOAA picture of the day provider
Summary:
The webpage structure of NOAA changed so the old regular expression doesn't
work anymore. Updated it. But it can break in future again.
{F7614976}
Reviewers: #plasma, sitter
Reviewed By: sitter
Subscribers: sitter, ngraham, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D24727
M +8-40 dataengines/potd/noaaprovider.cpp
M +5-6dataengines/potd/noaaprovider.h
https://commits.kde.org/kdeplasma-addons/43247057660513cbc942505eeba6e24c6811d0d9
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 413146] New: after updating KDE Neon to 5.17 expand/compress icons not visible
https://bugs.kde.org/show_bug.cgi?id=413146 Bug ID: 413146 Summary: after updating KDE Neon to 5.17 expand/compress icons not visible Product: Breeze Version: 5.17.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: w...@culturanuova.net CC: kain...@gmail.com Target Milestone: --- Created attachment 123318 --> https://bugs.kde.org/attachment.cgi?id=123318&action=edit TB screenshot SUMMARY STEPS TO REPRODUCE 1. open Thunderbird or Autokey 2. expand/compress (triangle) icons don't appear in left folder panel 3. (only) on mouse over they appear OBSERVED RESULT I cannot see triangle icons (expand/collapse) in Thunderbird or Autokey. It seems that they are of white color (wrong) on white background (right): they become black and so visible only with mouse over (or if selected). EXPECTED RESULT Triangle icons should be always visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon KDE Plasma Version: 5.17 KDE Frameworks Version: 5.63 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 383615] "File type options" window has wrong icon under Wayland
https://bugs.kde.org/show_bug.cgi?id=383615 Méven Car changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kde ||-cli-tools/9b2c7dec61de7425 ||b62b1589d635eaa41ec77e97 --- Comment #7 from Méven Car --- Git commit 9b2c7dec61de7425b62b1589d635eaa41ec77e97 by Méven Car. Committed on 18/10/2019 at 14:19. Pushed by meven into branch 'master'. [KEditFileType] Add a desktop file Summary: Allow to display its Icon in Wayland Reviewers: broulik, ngraham Reviewed By: broulik Subscribers: kossebau, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D24758 M +1-0keditfiletype/CMakeLists.txt A +8-0keditfiletype/org.kde.keditfiletype.desktop https://commits.kde.org/kde-cli-tools/9b2c7dec61de7425b62b1589d635eaa41ec77e97 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412896] Crash while double clicking and removing a magnetic lasso point/node
https://bugs.kde.org/show_bug.cgi?id=412896 Kuntal Majumder changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/cca4b060773069 ||9188a56dba71226dda24be1ad1 --- Comment #6 from Kuntal Majumder --- Git commit cca4b0607730699188a56dba71226dda24be1ad1 by Kuntal Majumder. Committed on 18/10/2019 at 14:26. Pushed by kuntalmajumder into branch 'master'. Limits the amount of searches in magnetic lasso interactive mode M +7-3plugins/tools/selectiontools/KisToolSelectMagnetic.cc https://invent.kde.org/kde/krita/commit/cca4b0607730699188a56dba71226dda24be1ad1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen
https://bugs.kde.org/show_bug.cgi?id=402392 Konrad Materka changed: What|Removed |Added CC||mate...@gmail.com --- Comment #4 from Konrad Materka --- As Samer Masterson wrote, this issue is caused by late initialization of menu in Dropbox. When user clicks on the icon, then "AboutToShow" signal is send to Dropbox. Due to asynchronous nature of this calls, there is indeed a race condition. KDE renders the menu with old state, at the same time Dropbox is adding new items to the menu. Menu is positioned using top-left corner. When new items are added, menu simply grows t the bottom. On KDE it is a problem, because by default panel is placed on the bottom of the screen. On Ubuntu (or any other desktop with icons on the top) it is less of a problem, because menu has space to grow. Everything is fine until now, this is quite common use case. There problem is on Dropbox side, it should return true if AboutToShow event should result in the menu being updated: Spec: https://github.com/gnustep/libs-dbuskit/blob/master/Bundles/DBusMenu/com.canonical.dbusmenu.xml Dump of method call: > method call time=1571407985.253788 sender=:1.26 -> destination=:1.137 > serial=1047 path=/org/ayatana/NotificationItem/dropbox_client_12927/Menu; > > interface=com.canonical.dbusmenu; member=AboutToShow >int32 0 > > method return time=1571407985.268242 sender=:1.137 -> destination=:1.26 > serial=20 reply_serial=1047 > boolean false It returns false, so KDE does not expect LayoutUpdated and does not wait for it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412944] Wrong Piwigo version parsing (2.10.x < 2.4) [patch]
https://bugs.kde.org/show_bug.cgi?id=412944 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Wrong Piwigo version|Wrong Piwigo version |parsing (2.10.x < 2.4) |parsing (2.10.x < 2.4) ||[patch] -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409515] sometimes crashes when fetching mail
https://bugs.kde.org/show_bug.cgi?id=409515 --- Comment #5 from staka...@eclipso.eu --- Created attachment 123319 --> https://bugs.kde.org/attachment.cgi?id=123319&action=edit crash example as you might need other cases, in attachment pop-resource segfaults. Behavior is random, not very often but often enough to raise attention. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413147] New: Pictures missing from thumbnail view of album
https://bugs.kde.org/show_bug.cgi?id=413147 Bug ID: 413147 Summary: Pictures missing from thumbnail view of album Product: digikam Version: 6.0.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: jcarricksm...@gmail.com Target Milestone: --- SUMMARY When viewing an album (in thumbnail view) some pictures do not appear in Digikam although visible in Gwenview, Showfoto and my own picture program (written in C++ with Qt libraries). In an album of 165 images Digikam recognises 158. There is one file which has two versions so six images are not visible. Copying the picture file or renaming it makes no difference. Opening it with GIMP and exporting it to a new filename makes the picture visible in Digikam, but only if I delete all the EXIF data first. I have deleted the Digikam databases and Digikam has recreated them without any change. The output of 'file ' for those visible and invisible is the same, and the properties viewed using Dolphin are the same and inspecting the files with okteta reveals that the first 12 bytes are the same. I am unaware of how this situation arose, only that I was renaming files while Digikam was showing the album. However this problem only affects some files, others were renamed and are still shown by Digikam. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) <- KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION File with uploaded to Google Drive as too large for bugzilla url:- https://drive.google.com/drive/folders/1o7uLnjOrhCZF_1Vosgir_oESB-6lFtzo?usp=sharing Contents:- 1) Screenshot_20191018_151435.png # A screenshot of Digikam with a problem album open. 2) exifdata # the exif data from the picture as reported by exiv2. 3) hold_dir_ls # a list of the picture files in the directory/album. 4) nws0903004.jpg # an example of a problem picture. Many thanks for looking at this. John -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412944] Wrong Piwigo version parsing (2.10.x < 2.4) [patch]
https://bugs.kde.org/show_bug.cgi?id=412944 caulier.gil...@gmail.com changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |digikam/commit/402a88c480da |digikam/commit/b08f3555d511 |f819275470518e1a26c22c9efcd |a5a8117566dbe9d655af0019ae2 |4 |c Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from caulier.gil...@gmail.com --- Git commit b08f3555d511a5a8117566dbe9d655af0019ae2c by Gilles Caulier. Committed on 18/10/2019 at 14:37. Pushed by cgilles into branch 'master'. apply patch from Frederic Coiffier about Piwigo version check in digiKam plugin M +1-1core/dplugins/generic/webservices/piwigo/piwigoplugin.cpp M +2-2core/dplugins/generic/webservices/piwigo/piwigotalker.cpp M +2-2core/dplugins/generic/webservices/piwigo/piwigotalker.h https://invent.kde.org/kde/digikam/commit/b08f3555d511a5a8117566dbe9d655af0019ae2c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413147] Pictures missing from thumbnail view of album
https://bugs.kde.org/show_bug.cgi?id=413147 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Can you check if this problem can be reproduced with last stable digiKam 6.3.0 AppImage bundle ? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413146] after updating KDE Neon to 5.17 expand/compress icons not visible
https://bugs.kde.org/show_bug.cgi?id=413146 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO Assignee|visual-des...@kde.org |uhh...@gmail.com Component|Icons |gtk theme --- Comment #1 from Nate Graham --- Does it reproduce if you use the Breeze GTK theme, the Breeze color scheme, and the Breeze icon theme and then restart Thunderbird? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 408580] NOAA environmental visualization picture of the day not working
https://bugs.kde.org/show_bug.cgi?id=408580
Nate Graham changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde
|plasma-addons/4324705766051 |plasma-addons/b2d041fb4a276
|3cbc942505eeba6e24c6811d0d9 |d006b0062ab5088765d171b7c91
--- Comment #10 from Nate Graham ---
Git commit b2d041fb4a276d006b0062ab5088765d171b7c91 by Nate Graham, on behalf
of Guo Yunhe.
Committed on 18/10/2019 at 14:58.
Pushed by ngraham into branch 'Plasma/5.17'.
Fix NOAA picture of the day provider
Summary:
The webpage structure of NOAA changed so the old regular expression doesn't
work anymore. Updated it. But it can break in future again.
{F7614976}
Reviewers: #plasma, sitter
Reviewed By: sitter
Subscribers: sitter, ngraham, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D24727
M +8-40 dataengines/potd/noaaprovider.cpp
M +5-6dataengines/potd/noaaprovider.h
https://commits.kde.org/kdeplasma-addons/b2d041fb4a276d006b0062ab5088765d171b7c91
--
You are receiving this mail because:
You are watching all bug changes.
[kdeplasma-addons] [Bug 408580] NOAA environmental visualization picture of the day not working
https://bugs.kde.org/show_bug.cgi?id=408580 Nate Graham changed: What|Removed |Added Version Fixed In||5.17.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413148] New: Grouped clips in timeline won't resize together
https://bugs.kde.org/show_bug.cgi?id=413148 Bug ID: 413148 Summary: Grouped clips in timeline won't resize together Product: kdenlive Version: 19.08.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jesse.dub...@gmail.com Target Milestone: --- SUMMARY When I try to group a video & audio clip together in the timeline, then try to resize them by left-click + dragging either video or audio clip in timeline, both clips in timeline don't move together. I have to move them separately. STEPS TO REPRODUCE 1. Import video clip, then an audio clip into the Project Bin. 2. Put the video clip in V1 in the timeline, then the audio clip in A1. 3. Select both clips, then right-click and select "Group" 4. Try to re-size the clip in the timeline by left-clicking the edge and moving the mouse along the timeline. OBSERVED RESULT Only the clip that you left-clicked on in the timeline moves. Say, if you grab the video in V1, then that clip moves, but the audio clip that's grouped to it in track A1 doesn't move along with it. EXPECTED RESULT For the two separate clips to behave as one once they're grouped, and to move together when relocated or re-sized. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux Mint 19.2 / Cinnamon desktop 4.2.4 (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413148] Grouped clips in timeline won't resize together
https://bugs.kde.org/show_bug.cgi?id=413148 Jesse DuBord changed: What|Removed |Added CC||jesse.dub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413146] GTK tree view expand/collapse icons not visible until item is selected
https://bugs.kde.org/show_bug.cgi?id=413146 Nate Graham changed: What|Removed |Added Summary|after updating KDE Neon to |GTK tree view |5.17 expand/compress icons |expand/collapse icons not |not visible |visible until item is ||selected -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413146] GTK tree view expand/collapse icons not visible until item is selected
https://bugs.kde.org/show_bug.cgi?id=413146 Duns changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Duns --- yes: it is absolutely the same. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413146] GTK tree view expand/collapse icons not visible until item is selected
https://bugs.kde.org/show_bug.cgi?id=413146 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Nate Graham --- Thanks. Cannot reproduce with my own Thunderbird on openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413146] GTK tree view expand/collapse icons not visible until item is selected
https://bugs.kde.org/show_bug.cgi?id=413146 --- Comment #4 from Duns --- I have the same problem with Neon virtualized -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413147] Pictures missing from thumbnail view of album
https://bugs.kde.org/show_bug.cgi?id=413147 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Activate "Show always original Image" in digiKam Setup-> Editor-> Versioning. In the current pre-release version of digiKam-6.4.0 there is a repair function for images that are hidden by versioning, but no derived images exist anymore. Maik -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413024] Kontact crashes on launch
https://bugs.kde.org/show_bug.cgi?id=413024 Tom Janssen changed: What|Removed |Added Version|5.12.2 |unspecified Product|kontact |Akonadi Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 413149] New: On the boot the audio play on wrong output
https://bugs.kde.org/show_bug.cgi?id=413149 Bug ID: 413149 Summary: On the boot the audio play on wrong output Product: pulseaudio-qt Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.fe...@gmx.de Reporter: fagne...@gmail.com Target Milestone: --- Created attachment 123320 --> https://bugs.kde.org/attachment.cgi?id=123320&action=edit Demonstration SUMMARY I've two audio outputs on my PC, the HDMI and the Headset. When I turn of my PC with the output set to my headset, on the next boot the audio plays on HDMI even with the headset as default output. So if I want to use the headset, I've to set the output to HDMI and set to headset after. I'm using Kubuntu 19.10 and the kubuntu-ppa-backports, I'm on KDE Plasma 5.17, but this happens on older version too. STEPS TO REPRODUCE 1. Set default output to headset 2. Turn Off the PC 3. Boot it again OBSERVED RESULT The audio plays on wrong output, even with the output set to the headset, it plays on HDMI. So if I want to use the headset, I've to set the output to HDMI and set to headset after. EXPECTED RESULT Audio playing on correct output SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 (kubuntu-ppa-backports) (available in About System) KDE Plasma Version: 5.17 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION Maybe the output just needs to be refreshed after the logon. -- You are receiving this mail because: You are watching all bug changes.
