[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off
https://bugs.kde.org/show_bug.cgi?id=359542 --- Comment #19 from Martin Gräßlin --- Given the xrandr output it seems like two external screens are connected, but not configured (?). They don't have a position and the X-Server screen size only matches the internal size. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366278] Application menu items hidden behind auto-hide taskbar
https://bugs.kde.org/show_bug.cgi?id=366278 --- Comment #5 from Martin Gräßlin --- (In reply to Eike Hein from comment #2) > Some sort of strut problem, Martin? IIRC auto-hiding panels don't set struts. This rather looks like an incorrect transient problem to me. The sub-menu should be a transient to the main menu, which should be a transient to the panel. If that's all setup correctly the windows should all be in the same layer and above the panel. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #13 from Martin Gräßlin --- Can you change the Qt debug message pattern to get the application included? I would like to know whether the message with the invalid command stream is from KWin. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it
https://bugs.kde.org/show_bug.cgi?id=364915 Martin Gräßlin changed: What|Removed |Added CC||goetzchr...@gmail.com --- Comment #3 from Martin Gräßlin --- *** Bug 366317 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 366317] When resuming from suspend, the desktop is shown before kscreenlocker_greet starts
https://bugs.kde.org/show_bug.cgi?id=366317 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 364915 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366063] Window switcher does not start with specific key combination
https://bugs.kde.org/show_bug.cgi?id=366063 --- Comment #1 from Martin Gräßlin --- This sounds like KWin is not able to recognize that the new control key is a modifier. Can you try to use the gui configuration of the keyboard layout whether there is a pre-defined option describing what you want and whether that works? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365292] Present Windows should not zoom out "always on top" windows
https://bugs.kde.org/show_bug.cgi?id=365292 --- Comment #4 from Martin Gräßlin --- > The biggest problem with the feature is, that currently full screen windows > (at least vlc) are completely hidden This sounds like a bug. That should be fixed and not worked around with a feature. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 Martin Gräßlin changed: What|Removed |Added CC||rnd...@nm.ru --- Comment #36 from Martin Gräßlin --- *** Bug 366115 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366115] Windows without titlebar belong to all activities
https://bugs.kde.org/show_bug.cgi?id=366115 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 274931 *** -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 366117] korgac doesn't start korganizer on click as service name changed
https://bugs.kde.org/show_bug.cgi?id=366117 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.3.0 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/675f284ddcdd78fde85b8e03 ||cf3e3164049ee9b9 --- Comment #2 from Laurent Montel --- Git commit 675f284ddcdd78fde85b8e03cf3e3164049ee9b9 by Montel Laurent. Committed on 01/08/2016 at 07:26. Pushed by mlaurent into branch 'Applications/16.08'. Fix Bug 366117 - korgac doesn't start korganizer on click as service name changed Adapt patch from tkope...@redhat.com and add test application. Thanks FIXED-IN: 5.3.0 M +1-1kalarm/src/functions.cpp M +1-1 kmail/agents/followupreminderagent/jobs/followupremindershowmessagejob.cpp M +5-0kmail/src/tests/CMakeLists.txt A +52 -0kmail/src/tests/ktoolinvocationtest.cpp [License: GPL (v2+)] M +1-1korganizer/korgac/alarmdialog.cpp M +1-1korganizer/korgac/alarmdockwindow.cpp http://commits.kde.org/kdepim/675f284ddcdd78fde85b8e03cf3e3164049ee9b9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366318] No transparency, blur or shadows in plasmashell at startup
https://bugs.kde.org/show_bug.cgi?id=366318 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 362531 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 Martin Gräßlin changed: What|Removed |Added CC||pablow.1...@gmail.com --- Comment #31 from Martin Gräßlin --- *** Bug 366318 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 313754] Very slow repainting on remote connections
https://bugs.kde.org/show_bug.cgi?id=313754 Rémi Benoit changed: What|Removed |Added CC||r3m1.ben...@gmail.com Summary|Very slow repainting on |Very slow repainting on |remove connections |remote connections -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 Martin Gräßlin changed: What|Removed |Added CC||dennis.schridde@uni-heidelb ||erg.de --- Comment #25 from Martin Gräßlin --- *** Bug 366240 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 363430] Plasma crashes on right click on the menu
https://bugs.kde.org/show_bug.cgi?id=363430 --- Comment #5 from Phil Evans --- Apologies, for some reason I didn't see this request, and I've been away: I'll check this out tonight and get back to you ASAP. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366240] KWin crashed when opening Plasma digital clock settings
https://bugs.kde.org/show_bug.cgi?id=366240 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- Please switch to Breeze window decoration as a workaround. *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366185] Impossible d'effectuer un changement de bureau virtuel
https://bugs.kde.org/show_bug.cgi?id=366185 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is missing debug symbols. If you are able to reproduce please install debug symbols for kwin and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366198] crash occurs shortly after login
https://bugs.kde.org/show_bug.cgi?id=366198 Martin Gräßlin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- As a workaround use the breeze window decoration. *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 Martin Gräßlin changed: What|Removed |Added CC||petrb...@gmail.com --- Comment #26 from Martin Gräßlin --- *** Bug 366198 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 366321] New: KRDC in Plasma5 still calls KWallet4
https://bugs.kde.org/show_bug.cgi?id=366321 Bug ID: 366321 Summary: KRDC in Plasma5 still calls KWallet4 Product: krdc Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: k...@macferrin.com Kubuntu (Ubuntu 16.04.1 LTS) w/Plasma 5 KRDC Version 4.14.16 Behavior: When using the "Remember passwords (KWallet)" option, KRDC still calls the legacy kwallet4 using: ~/.kde/share/apps/kwallet/kdewallet.kwl ~/.kde/share/config/kwalletrc Under Plasma5, KRDC should instead call for: ~/.local/share/kwalletd/kdewallet.kwl ~/.config/kwalletrc As it stands now, the legacy kwallet4 can be used, but users cannot configure or change the password on the older kwallet4 wallets using the new kwalletmanager5, nor can the cause the legacy wallet to stay open persistently for any period of time since kwalletmanager4 cannot be installed concurrently. Reproducible: Always Steps to Reproduce: 1. enable "Remember passwords (KWallet)" in KRDC settings 2. 3. Actual Results: see Details above Expected Results: see Details above -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 366181] Template inserted by user isn't saved
https://bugs.kde.org/show_bug.cgi?id=366181 Ralf Habacker changed: What|Removed |Added Version|2.15.3 (KDE Applications|2.11.2 |14.12.3)| --- Comment #2 from Ralf Habacker --- Bug is also present in older versions like 2.11.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #32 from Martin Gräßlin --- We might be on the wrong trail with the effects: according to OpenSUSE it's also hit on openQA which uses XRender compositing! Thus it might be that we don't detect Compositing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366316] Adding tag results in duplicate tag error
https://bugs.kde.org/show_bug.cgi?id=366316 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- What the content of the error dialog ? When you run digiKam in a console, what's printed as debug trace while error dialog appear ? Problem is in album view or tags manager, or both ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366305] Undo is disfunctional for complex operations
https://bugs.kde.org/show_bug.cgi?id=366305 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |5.0.0 CC||caulier.gil...@gmail.com --- Comment #6 from caulier.gil...@gmail.com --- I agree that Undo manager need to show some message box with relevant information about missing free space to complete undo registration in temporary directory. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 Markus Heß changed: What|Removed |Added CC||hess...@googlemail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366125] screen is locked when changing activities after closing lid while docked
https://bugs.kde.org/show_bug.cgi?id=366125 Erik Quaeghebeur changed: What|Removed |Added Version|unspecified |5.6.5 Component|general |general Product|kscreenlocker |Powerdevil --- Comment #3 from Erik Quaeghebeur --- (In reply to Martin Gräßlin from comment #2) > > The screen should not be locked when closing the lid, > > This is a configuration option in powerdevil Well, this is when attached to mains, and I don't have “Even when external monitor is attached” enabled. > > but it should certainly not be locked when switching activities. > > No idea what's going on there. KScreenlocker doesn't integrate with > activities AFAIK. While looking at the power saving config, I noticed there is a tab for activities configuration. So I assume it may be there, I'll reassign to powerdevil (if I can't, please do it for me). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 Yaroslav Sidlovsky changed: What|Removed |Added CC||zawer...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366278] Application menu items hidden behind auto-hide taskbar
https://bugs.kde.org/show_bug.cgi?id=366278 --- Comment #6 from Eike Hein --- ^ Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811 Boudewijn Rempt changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/1cf18b8e7c20800c5ad36ffd9 ||84f51b0220f9fb8 Resolution|WONTFIX |FIXED --- Comment #14 from Boudewijn Rempt --- Git commit 1cf18b8e7c20800c5ad36ffd984f51b0220f9fb8 by Boudewijn Rempt. Committed on 01/08/2016 at 08:41. Pushed by rempt into branch 'video-export-rebased'. Make it possible to use any style, for the sufficiently determined Set KRITA_NO_STYLE_OVERRIDE to something and the currently style will not be overridden. Since there are some reports that breeze works now, enable that, too. We can always disable it when it turns out to be a bad idea. M +14 -9libs/ui/KisApplication.cpp http://commits.kde.org/krita/1cf18b8e7c20800c5ad36ffd984f51b0220f9fb8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811 Boudewijn Rempt changed: What|Removed |Added Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit |a/1cf18b8e7c20800c5ad36ffd9 |a/c5aa1b180bc24c548e37203a8 |84f51b0220f9fb8 |a6007beba5ea47a --- Comment #15 from Boudewijn Rempt --- Git commit c5aa1b180bc24c548e37203a8a6007beba5ea47a by Boudewijn Rempt. Committed on 01/08/2016 at 08:45. Pushed by rempt into branch 'master'. Make it possible to use any style, for the sufficiently determined Set KRITA_NO_STYLE_OVERRIDE to something and the currently style will not be overridden. Since there are some reports that breeze works now, enable that, too. We can always disable it when it turns out to be a bad idea. M +14 -9libs/ui/KisApplication.cpp http://commits.kde.org/krita/c5aa1b180bc24c548e37203a8a6007beba5ea47a -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 363719] Sidebar can not be resized even when the details are too long
https://bugs.kde.org/show_bug.cgi?id=363719 --- Comment #9 from Elvis Angelaccio --- (In reply to Brendon Higgins from comment #8) > (I hesitate to respond, as this seems like a digression from the bug here, > but since you asked...) Indeed, feel free to open a dedicated bug report and we can continue there. > > (In reply to Elvis Angelaccio from comment #7) > > This should not happen... You do have have shared-mime-info installed, > > right? > > Yes, the shared-mime-info package is installed. > > > What about the Open dialog(CTRL+O) ? In the "Filter:" picker, do you see the > > raw mimetypes or the friendly names > > In Ark's open dialog, I also see mimetypes. Same with Dragon, but > interestingly not KMail or KMyMoney. I start to wonder if it's just KF5 > programs, not those still on KF4. FWIW, two machines I use exhibit this > mimetype issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 347964] Shortcuts mixup and falling through mouse clicks with non-standard keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=347964 Arne Babenhauserheide changed: What|Removed |Added CC||arne_...@web.de --- Comment #26 from Arne Babenhauserheide --- Might be related: With plasma kde-plasma/kwin 5.6.5-r1 CTRL-X does not reach the application when setting a lithauian keyboard (lv), but the copied text appears in klipper. This makes it pretty hard to use Emacs. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366125] screen is locked when changing activities after closing lid while docked
https://bugs.kde.org/show_bug.cgi?id=366125
Kai Uwe Broulik changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0 |1
CC||k...@privat.broulik.de
--- Comment #4 from Kai Uwe Broulik ---
I think I found the reason. When activities change PowerDevil reloads its
profile (as you might have per-activity settings) and in the profile loader it
has the following code:
// If the lid is closed, retrigger the lid close signal
if (m_backend->isLidClosed()) {
Q_EMIT
m_backend->buttonPressed(PowerDevil::BackendInterface::LidClose);
}
and then it locks the screen, it also doesn't even check whether the lid is
already closed, so it does that everytime you change activities.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 347964] Shortcuts mixup and falling through mouse clicks with non-standard keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=347964 --- Comment #27 from Arne Babenhauserheide --- (In reply to Arne Babenhauserheide from comment #26) > Might be related: With plasma kde-plasma/kwin 5.6.5-r1 CTRL-X does not reach > the application when setting a lithauian keyboard (lv), but the copied text > appears in klipper. This makes it pretty hard to use Emacs. I now found that I can trigger CTRL-x in emacs with CTRL-SHIFT-x. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366125] screen is locked when changing activities after closing lid while docked
https://bugs.kde.org/show_bug.cgi?id=366125 --- Comment #5 from Kai Uwe Broulik --- This doesn't change the fact that the handle button events plugin eventually discards the event when an external monitor is present, at least that's what it should do, so we have two bugs here: 1. Closing the lid triggering a screen lock although an external monitor is present which might have been caused by [1] 2. The lid closed signal being emitted unconditionally on profile load if the lid is currently closed [1] https://quickgit.kde.org/?p=powerdevil.git&a=blobdiff&h=1c3a06d9bb1bf1abade1cc02024e4bbccbf12781&hp=7e1d16e4123d1ac280ad71807f265b0859e347b9&hb=d3162725cfffb79da7bb8f276a31a915e3349dab&f=daemon%2Factions%2Fbundled%2Fhandlebuttonevents.cpp -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366125] screen is locked when changing activities after closing lid while docked
https://bugs.kde.org/show_bug.cgi?id=366125 --- Comment #6 from Erik Quaeghebeur --- (In reply to Kai Uwe Broulik from comment #5) > > https://quickgit.kde.org/?p=powerdevil. > git&a=blobdiff&h=1c3a06d9bb1bf1abade1cc02024e4bbccbf12781&hp=7e1d16e4123d1ac2 > 80ad71807f265b0859e347b9&hb=d3162725cfffb79da7bb8f276a31a915e3349dab&f=daemon > %2Factions%2Fbundled%2Fhandlebuttonevents.cpp Maybe it would be helpful for me to check what KScreen thinks output->type() is for me. Is there a way I could find this out? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366125] screen is locked when changing activities after closing lid while docked
https://bugs.kde.org/show_bug.cgi?id=366125 --- Comment #7 from Kai Uwe Broulik --- Can you run kscreen-console and attach its output here? It should have eg. "Type: "Panel (Laptop)"" and some other information we could use to figure out why (if it does) it detects it as Unknown. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366243] Something's really wrong with the update scheduler/kisstroke/etc.
https://bugs.kde.org/show_bug.cgi?id=366243 Boudewijn Rempt changed: What|Removed |Added Summary|Something's really wrong|Something's really wrong |with the update |with the update |sceduler/kisstroke/etc. |scheduler/kisstroke/etc. CC||b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 334080] kdeconnect,some sent photo are uncomplete
https://bugs.kde.org/show_bug.cgi?id=334080 Ben Cooksley changed: What|Removed |Added CC|topot...@hotmail.com| --- Comment #37 from Ben Cooksley --- Unsubscribing CC user per abuse report. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358116] messageviewer leaks temporary files with mail parts in it
https://bugs.kde.org/show_bug.cgi?id=358116 David Faure changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||fa...@kde.org --- Comment #8 from David Faure --- This was fixed (for the case of cleanly quitting kmail) in c803a7a (v16.07.80). Please test. We can't do much in case of crashes -- except fixing those crashes in the first place, of course :-) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 366322] New: Krunner search does not works
https://bugs.kde.org/show_bug.cgi?id=366322 Bug ID: 366322 Summary: Krunner search does not works Product: krunner Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: qmor.q...@gmail.com krunner and kde start menu search does not work at all. I'm trying to type some symbols like "konsol" and has no results. It is impossible to use start menu or krunner to run any application. File search is also not working. Reproducible: Always Steps to Reproduce: 1. Click on start menu and start to type some app name to start 2. No any results shows 3. Press alt+f2 start type some app name to start - has no any results Actual Results: No expected behavior - searched app does no start Expected Results: Typed application should start -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366125] screen is locked when changing activities after closing lid while docked
https://bugs.kde.org/show_bug.cgi?id=366125 --- Comment #8 from Erik Quaeghebeur --- Created attachment 100405 --> https://bugs.kde.org/attachment.cgi?id=100405&action=edit kscreen-console output DP1 is laptop-DP and DP2 is dock-DP -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364151] Overview Docker - bad quality of preview
https://bugs.kde.org/show_bug.cgi?id=364151 Boudewijn Rempt changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Boudewijn Rempt --- This is fixed in master now, thanks to Eugening's work! See https://phabricator.kde.org/diffusion/KRITA/browse/thumbnail_improvements/ -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366125] screen is locked when changing activities after closing lid while docked
https://bugs.kde.org/show_bug.cgi?id=366125 --- Comment #9 from Kai Uwe Broulik --- Thanks a lot. Can you try if this [1] fixes it for you? The heuristic was recently changed to detect outputs that start with DP (DP2 in your case) as DisplayPort which should fix this problem. This commit should have landed in Plasma 5.7.0. [1] https://quickgit.kde.org/?p=libkscreen.git&a=commit&h=54ec74901a0fea1601f76278d6e04af4fbd4b74d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366278] Application menu items hidden behind auto-hide taskbar
https://bugs.kde.org/show_bug.cgi?id=366278 Eike Hein changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350243] No Help no Handbooks at Kdenlive Menu: "Help"
https://bugs.kde.org/show_bug.cgi?id=350243 --- Comment #3 from kdenlivefriend --- Tryed so hard to reach my Bugreport... Well: As I remember this statement concerns ex Ubuntu versions. -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 366263] Cursor changes to contrast-large theme when hovering over firefox, nightly and thunderbird (probably gtk)
https://bugs.kde.org/show_bug.cgi?id=366263 Aleix Pol changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Aleix Pol --- Can you maybe upload your gtk settings? cat ~/.gtkrc-2.0 echo ".." cat ~/.config/gtk-3.0/settings.ini -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365999] Pairing with Android file system "Invalid object path:" in "dolphin"
https://bugs.kde.org/show_bug.cgi?id=365999 Carlos changed: What|Removed |Added CC||cbapti...@opensuse.us -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 366320] Heavy CPU usage when pulseaudio fails to start
https://bugs.kde.org/show_bug.cgi?id=366320 David Rosca changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 157272] disable system notification for all applications should be possible (as in kde 3.5.x) (disable sounds for all apps)
https://bugs.kde.org/show_bug.cgi?id=157272 Pascal d'Hermilly changed: What|Removed |Added CC||pas...@dhermilly.dk --- Comment #29 from Pascal d'Hermilly --- Which version will the fix appear in? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 366181] Template inserted by user isn't saved
https://bugs.kde.org/show_bug.cgi?id=366181 --- Comment #3 from Ralf Habacker --- This problem does not occur on using a pointer as data type e.g. test1234*. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 366181] Template inserted by user isn't saved
https://bugs.kde.org/show_bug.cgi?id=366181
--- Comment #4 from Ralf Habacker ---
Classifier widget and tree view requires to have an UMLTemplate class instance
for showing the template datatype. The recent code has two bugs, which
prevents adding of non pointer and non common data types as template datatype.
In bool UMLDatatypeWidget::applyTemplate(), which got the data type related
part of UMLTemplateDialog::apply() there is the following code:
QString typeName = m_datatypeWidget->currentText();
UMLDoc *pDoc = UMLApp::app()->document();
UMLClassifierList namesList(pDoc->concepts());
* get all objects from logical root with type Class, Interface, Datatype,
Enum, Entity, Package, Folder
foreach (UMLClassifier* obj, namesList) {
if (typeName == obj->name()) {
* here a related classifier has been found and is set as template type.
m_pTemplate->setType(obj);
* because it does not return with TRUE the last occurence of the related type
is used
}
}
* only if no global objects has been found (which is never the case) the
template type name is used.
if (namesList.isEmpty()) { // not found.
// FIXME: This implementation is not good yet.
m_pTemplate->setTypeName(typeName);
}
The second bug is located in UMLClassifierListItem::setTypeName(), which in the
recent state adds such an instance only for common data and pointer types [1],
not for classes.
void UMLClassifierListItem::setTypeName(const QString &type)
{
if (type.isEmpty() || type == QLatin1String("void")) {
m_pSecondary = NULL;
m_SecondaryId.clear();
return;
}
UMLDoc *pDoc = UMLApp::app()->document();
m_pSecondary = pDoc->findUMLObject(type);
if (m_pSecondary == NULL) {
// Make data type for easily identified cases
[1] if (Model_Utils::isCommonDataType(type) ||
type.contains(QLatin1Char('*'))) {
m_pSecondary =
Object_Factory::createUMLObject(UMLObject::ot_Datatype, type);
uDebug() << "created datatype for " << type;
} else {
m_SecondaryId = type;
}
}
UMLObject::emitModified();
}
In all other cases it sets m_secondaryID with the template datatype as text,
which is not displayed in the tree view and classifier widget and not fetched
on initial setup of UMLDataTypeWidget.
/**
* Overrides method from UMLClassifierListItem.
* Returns the type name of the UMLTemplate.
* If the template parameter is a class, there is no separate
* type object. In this case, getTypeName() returns "class".
*
* @return The type name of the UMLClassifierListItem.
*/
QString UMLTemplate::getTypeName() const
{
if (m_pSecondary == NULL)
return QLatin1String("class");
return m_pSecondary->name();
}
--
You are receiving this mail because:
You are watching all bug changes.
[rkward] [Bug 366323] New: rkward/plugin/rkformula.cpp:386: possible bad erase ?
https://bugs.kde.org/show_bug.cgi?id=366323 Bug ID: 366323 Summary: rkward/plugin/rkformula.cpp:386: possible bad erase ? Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: dcb...@hotmail.com rkward-0.6.5/rkward/plugin/rkformula.cpp:386] -> [/home/dcb/rpmbuild/BUILD/rkward-0.6.5/rkward/plugin/rkformula.cpp:400]: (error) Iterator 'in' used after element has been erased. Source code is interaction_map.erase (in); -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 366163] korganizer don't sync with owncloud 9.x
https://bugs.kde.org/show_bug.cgi?id=366163 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdep ||im-runtime/636801e900d0945d ||8fc45accd106da6351d53780 Resolution|--- |FIXED Version Fixed In||5.3.0 --- Comment #1 from Laurent Montel --- Git commit 636801e900d0945d8fc45accd106da6351d53780 by Montel Laurent. Committed on 01/08/2016 at 11:37. Pushed by mlaurent into branch 'Applications/16.08'. Fix Bug 366163 - korganizer don't sync with owncloud 9.x FIXED-IN: 5.3.0 M +1-1resources/dav/resource/setupwizard.cpp A +8-0resources/dav/services/owncloud-pre9.desktop M +2-2resources/dav/services/owncloud.desktop http://commits.kde.org/kdepim-runtime/636801e900d0945d8fc45accd106da6351d53780 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 366324] New: [REGRESSION] Show CPUs separately no longer works
https://bugs.kde.org/show_bug.cgi?id=366324 Bug ID: 366324 Summary: [REGRESSION] Show CPUs separately no longer works Product: kdeplasma-addons Version: 5.7.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: systemloadviewer Assignee: plasma-b...@kde.org Reporter: kdeb...@plast.id.au Previously, I could select show CPUs separately. This no longer works; the plasmoid is blank and shows no information. Reproducible: Always Steps to Reproduce: 1. Change system load view's settings. 2. Show CPU monitor; CPUs separately. (Monitor type: Compact Bar.) 3. Click OK and observe plasmoid. Actual Results: Plasmoid is blank. Expected Results: Shown several bars, one for each CPU. I've only noticed this recently, in the last week or so. I tried reverting to the last few versions of `kdeplasma-addons` as below, but they all had this problem. 5.6.3-2 5.6.4-1 5.6.5-1 5.6.95-1 5.7.0-1 5.7.1-1 This reflects the last three months of my update history for this package, so I'm fairly sure that this regression occurred within this time period. Presumably it's a bug in a different package, instead. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 365350] password visible on screen / in URL when testing connection to Xchange calendar
https://bugs.kde.org/show_bug.cgi?id=365350 Laurent Montel changed: What|Removed |Added Version Fixed In||5.3.0 Latest Commit||http://commits.kde.org/kdep ||im-runtime/15296cb80be303c2 ||fdad39ed2e055521eba30c43 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Laurent Montel --- Git commit 15296cb80be303c2fdad39ed2e055521eba30c43 by Montel Laurent. Committed on 01/08/2016 at 11:58. Pushed by mlaurent into branch 'Applications/16.08'. Fix Bug 365350 - password visible on screen / in URL when testing connection to Xchange calendar Force to use a valid url FIXED-IN: 5.3.0 M +3-0resources/openxchange/oxa/connectiontestjob.cpp http://commits.kde.org/kdepim-runtime/15296cb80be303c2fdad39ed2e055521eba30c43 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364699] Kubuntu: Kwin crash random times and windows menu and buttons disappear
https://bugs.kde.org/show_bug.cgi?id=364699 --- Comment #9 from Wellington Torrejais da Silva --- (In reply to Thomas Lübking from comment #6) > The "developer information" tab in the crash dialog. > > As a shortcut, run > qdbus org.kde.KWin /KWin supportInformation | grep -i plugin > > if it says something about "aurorae", run "kcmshell5 kwindecorations" and > select the breeze deco. Hello, The "kcmshell5 kwindecorations " command not exist because "kwindecorations" not installed. And now the taskbar always disfigure at start/boot up/logon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365868] Hang in plasmashell when searching for specific "mä" in widgets using widget explorer
https://bugs.kde.org/show_bug.cgi?id=365868 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/plas ||ma-desktop/14d48bac5f95e4e2 ||76b227023fed97d9cdeb6157 --- Comment #13 from David Edmundson --- Git commit 14d48bac5f95e4e276b227023fed97d9cdeb6157 by David Edmundson. Committed on 01/08/2016 at 12:50. Pushed by davidedmundson into branch 'Plasma/5.7'. Workaround searching lockup Summary: QQC::ScrollView has an annoying bug where you can get it in a situation where if you have exactly if delegates are based on the viewport width you can get in a loop where you need the scrollbar, that shrinks the view so it resizes the delegates at which point you don't need the scrollbar, so it resizes the delegates so and so on. Keeping scrollbars always on is a good workaround. If anything it's nice to not have things jumping around slightly when searching Test Plan: Plasma explorer still works. Approach works as I've used it in the wallpaper selection dialog for exactly the same reason. Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D2239 M +2-0desktoppackage/contents/explorer/WidgetExplorer.qml http://commits.kde.org/plasma-desktop/14d48bac5f95e4e276b227023fed97d9cdeb6157 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365295] The three icons in buttons "Search", "Filter" and "Close" are very small
https://bugs.kde.org/show_bug.cgi?id=365295 --- Comment #8 from David Edmundson --- Git commit 79f842066d0544d879434b50aecee2cff7156336 by David Edmundson. Committed on 01/08/2016 at 12:50. Pushed by davidedmundson into branch 'Plasma/5.7'. Remove dead code Summary: Setting the layout height to be the height of one of the layout items is both pointless, it will be calculated from all child items implicitHeight anyway, and wrong as the heading/textField could be bigger. Test Plan: Opened it, looked the same Reviewers: #plasma Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D2241 M +0-2desktoppackage/contents/activitymanager/Heading.qml http://commits.kde.org/plasma-desktop/79f842066d0544d879434b50aecee2cff7156336 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363846] Krita crashes if a second window with a view into the first window is closed
https://bugs.kde.org/show_bug.cgi?id=363846 speedyblueskyf...@gmail.com changed: What|Removed |Added CC||speedyblueskyf...@gmail.com --- Comment #5 from speedyblueskyf...@gmail.com --- Im not sure if t his is the same bug, in krita version 3.0 I have a 100% reproducible crash: crash when closing any "new window", but only if i have selected a template before opening and then closing the "new window". in other words, if i open krita with nothing in it, and then select "new window" and close it, it will not crash. but if i have selected a template and then do it, it will always crash. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363846] Krita crashes if a second window with a view into the first window is closed
https://bugs.kde.org/show_bug.cgi?id=363846 --- Comment #6 from speedyblueskyf...@gmail.com --- (In reply to speedyblueskyfish from comment #5) > Im not sure if t his is the same bug, in krita version 3.0 I have a 100% > reproducible crash: > crash when closing any "new window", but only if i have selected a template > before opening and then closing the "new window". > in other words, if i open krita with nothing in it, and then select "new > window" and close it, it will not crash. but if i have selected a template > and then do it, it will always crash. correction: not every time. this time it crashed when i selected "use template" when making a new window. maybe. or maybe it was just a delay before it crashed. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 366277] klipper systray applet autostarts on non-plasma DE's
https://bugs.kde.org/show_bug.cgi?id=366277 --- Comment #3 from Jonathan Riddell --- https://phabricator.kde.org/D2323 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #59 from Samantha McVey --- Created attachment 100407 --> https://bugs.kde.org/attachment.cgi?id=100407&action=edit strace of plasmashell Here is an strace. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 366325] New: Crash after update Aug 1, 2016
https://bugs.kde.org/show_bug.cgi?id=366325 Bug ID: 366325 Summary: Crash after update Aug 1, 2016 Product: ksmserver Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: crgla...@gmail.com Application: ksmserver () Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: System updated and on a re-boot Plasma crashed for the OpenSuSE LEAP 42.1 distribution. Dumbing down kernel to see if it works. This has been the typical workaround until someone relaizes the mistake in packaging. The crash can be reproduced every time. -- Backtrace: Application: ksmserver (ksmserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa2c9d0e800 (LWP 3912))] Thread 2 (Thread 0x7fa28d1a9700 (LWP 4765)): #0 0x7fa2c9648ccd in read () at /lib64/libc.so.6 #1 0x7fa2b9a33073 in () at /usr/lib64/tls/libnvidia-tls.so.367.35 #2 0x7fa2bdbb3b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa2bdb72999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa2bdb72df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fa2bdb72f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fa2c4212d8b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa264001600, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #7 0x7fa2c41b9d53 in QEventLoop::exec(QFlags) (this=this@entry=0x7fa28d1a8db0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7fa2c3fdb61a in QThread::exec() (this=this@entry=0xbbf260) at thread/qthread.cpp:503 #9 0x7fa2c7805e18 in QQmlThreadPrivate::run() (this=0xbbf260) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #10 0x7fa2c3fe032f in QThreadPrivate::start(void*) (arg=0xbbf260) at thread/qthread_unix.cpp:331 #11 0x7fa2bf4c50a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fa2c965502d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fa2c9d0e800 (LWP 3912)): [KCrash Handler] #6 0x7fa2c95a50c7 in raise () at /lib64/libc.so.6 #7 0x7fa2c95a6478 in abort () at /lib64/libc.so.6 #8 0x7fa2c3fce7ce in QMessageLogger::fatal(char const*, ...) const (context=..., message=) at global/qlogging.cpp:1578 #9 0x7fa2c3fce7ce in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffc86287700, msg=msg@entry=0x7fa2c7e500aa "%s") at global/qlogging.cpp:781 #10 0x7fa2c7ccbe71 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) (this=this@entry=0xbc8480, window=0xaadb60, isEs=isEs@entry=false) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:244 #11 0x7fa2c7cccdf5 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) (this=this@entry=0xbc8480, window=0xaadb60) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:333 #12 0x7fa2c7ccdb5e in QSGGuiThreadRenderLoop::exposureChanged(QQuickWindow*) (this=0xbc8480, window=0xaadb60) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:422 #13 0x7fa2c4715b69 in QWindow::event(QEvent*) (this=this@entry=0xaadb60, ev=ev@entry=0x7ffc86287ba0) at kernel/qwindow.cpp:2028 #14 0x7fa2c7d060d1 in QQuickWindow::event(QEvent*) (this=0xaadb60, e=0x7ffc86287ba0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/items/qquickwindow.cpp:1413 #15 0x7fa2c4e9fe7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x9cb8c0, receiver=receiver@entry=0xaadb60, e=e@entry=0x7ffc86287ba0) at kernel/qapplication.cpp:3716 #16 0x7fa2c4ea4cc8 in QApplication::notify(QObject*, QEvent*) (this=0x9cb8a0, receiver=0xaadb60, e=0x7ffc86287ba0) at kernel/qapplication.cpp:3499 #17 0x7fa2c41bbe95 in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x9cb8a0, receiver=receiver@entry=0xaadb60, event=event@entry=0x7ffc86287ba0) at kernel/qcoreapplication.cpp:965 #18 0x7fa2c470e5d4 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) (event=0x7ffc86287ba0, receiver=0xaadb60) at ../../src/corelib/kernel/qcoreapplication.h:227 #19 0x7fa2c470e5d4 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) (e=0xc164b0) at kernel/qguiapplication.cpp:2650 #20 0x7fa2c470f1ed in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) (e=e@entry=0xc164b0) at kernel/qguiapplication.cpp:1645 #21 0x7fa2c46f4268 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) (flags=...) at kernel/qwindowsysteminterface.cpp:625 #22 0x7fa2b3e6d
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #14 from Jan-Marek Glogowski ---
So this time I can confirm, that "Alt + Shift + F12" stops the compositing and
the flickering.
Guess I hit the wrong key combo last time, or I had a different problem, but
xsession-errors and dmesg show almost the same messages:
Today:
[18199.442243] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch
(888, 0x40, 1) invalid
[18199.442334] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
Previous:
[26610.825302] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch
(792, 0x40, 1) invalid
[26610.825349] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
What's the preferred way to set a different QT_MESSAGE_PATTERN? Edit startkde?
Guess the example from the Qt docs is ok for you: QT_MESSAGE_PATTERN="[%{type}]
%{appname} (%{file}:%{line}) - %{message}"
This proves my theory about the "late at day" is wrong, as I neither installed
new software, nor intensively used the system. Actually this time it happened
almost instantly after the first start of LO, when opening a dialog.
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney4] [Bug 366326] New: OFX direct download fails when OFX UID is expected by bank
https://bugs.kde.org/show_bug.cgi?id=366326 Bug ID: 366326 Summary: OFX direct download fails when OFX UID is expected by bank Product: kmymoney4 Version: 4.8.0 Platform: MS Windows URL: https://mail.kde.org/pipermail/kmymoney/2015-December/ 002337.html OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: wolfe...@gmail.com Chase Bank (surely among others) requires a UID when using their OFX Direct Download service. I don't think that KMyMoney sends a UID under any circumstances, as shown in the linked URL. A quick fix was implemented, though I don't have the devel-list email handy. Basically someone had patched the account properties so you could specify a UID of the proper length that would be sent to that account. Reproducible: Always Steps to Reproduce: 1. Try to use OFX direct download at a bank that expects a UID response field 2. Download fails. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #33 from Martin Gräßlin --- A shot in the blue patch: https://git.reviewboard.kde.org/r/128566/ - if anyone could try and report back whether it helps, that would be very appreciated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365292] Present Windows should not zoom out "always on top" windows
https://bugs.kde.org/show_bug.cgi?id=365292 --- Comment #5 from Alexander Schier --- Not sure, if this is a real bug, because the expected behaviour on clicking firefox in the panel is: - hide everything - expose all firefox windows This happens, but on both monitors and the second one even when there is no firefox window. Still possible matching the current spec of the feature. But when working with two monitors and a fullscreen window on the second one, my wanted behaviour is more like this: - hide everything on the *current* monitor - expose all firefox windows on the current monitor This is a small change in the specification of the feature. Which is another candidate for a setting, like the panel settings "Show windows from all monitors" / "Show windows from all workspaces". Maybe kwin should respect the plasmoid's setting for this, maybe it should have own options. Personally i would like to have everything in the panel, but the more logical setting would probably to follow the panel behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #58 from Samantha McVey --- Created attachment 100406 --> https://bugs.kde.org/attachment.cgi?id=100406&action=edit Perf report while plasmashell running at 100% Here is perf which I ran against plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365959] Addressbook is not usable via Owncloud-Ressource
https://bugs.kde.org/show_bug.cgi?id=365959 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel --- Which is owncloud version ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #15 from Martin Gräßlin --- > What's the preferred way to set a different QT_MESSAGE_PATTERN? Edit startkde? startkde is an option, though maybe overkill. Another possibility is to edit any environment file, e.g. /etc/environment or the local users overwrite. The example for the pattern looks good. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 p...@alicious.com changed: What|Removed |Added CC||p...@alicious.com --- Comment #2 from p...@alicious.com --- Wow, is that for real - KDE the DE known as the most configurable no longer supports resizing major UI elements for usability?? That can't be the projects official decision surely, that this is notabug? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366125] screen is locked when changing activities after closing lid while docked
https://bugs.kde.org/show_bug.cgi?id=366125 --- Comment #10 from Kai Uwe Broulik --- Can you try this patch https://phabricator.kde.org/D2325 please? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355504] xembedsniproxy: java tray icon doesn't work
https://bugs.kde.org/show_bug.cgi?id=355504 --- Comment #16 from EMR_Kde --- So I tried to start a java based app (DavMail for Exchange) and it's not embedding correctly in my system tray anymore. I tried to install the SNI Proxy package, to no avail: installed plasma5-workspace-5.5.5.2-12.1.x86_64 obsoletes xembed-sni-proxy Why was this dropped from 5.4? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Jan Pavlicek changed: What|Removed |Added CC|jan.pavli...@centrum.cz | -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 362541] Crashes whenever i try to zoom into an image
https://bugs.kde.org/show_bug.cgi?id=362541 bugs.kde@derflupp.e4ward.com changed: What|Removed |Added CC||bugs.kde.org@derflupp.e4war ||d.com --- Comment #3 from bugs.kde@derflupp.e4ward.com --- Created attachment 100409 --> https://bugs.kde.org/attachment.cgi?id=100409&action=edit second image that causes a crash I can confirm the bug with the attached image “second image that causes a crash”. I can reliably reproduce the bug by opening the image (the image is initially resized to fit the available space) and then clicking the 100%-zoom button. Strangely, the crash does not occour if I zoom in _slowly_ step-by-step using the zoom-in button or Ctrl+Scroll-Wheel. If I zoom in fast (e.g. by clicking the zoom-in button rapidly), the crash occurs again. Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2635eff8c0 (LWP 10151))] Thread 4 (Thread 0x7f260ea31700 (LWP 10154)): #0 0x7f262a85a458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f2630f5db66 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f2630f59274 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f2630f5cd78 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f262a854484 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f263086f6dd in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f2617fff700 (LWP 10153)): #0 0x7f26308666cd in poll () from /usr/lib/libc.so.6 #1 0x7f26291f2fd6 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f26291f30ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f263118b59b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f26311350da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f2630f580f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f2630512e75 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f2630f5cd78 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f262a854484 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f263086f6dd in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f261e38e700 (LWP 10152)): #0 0x7f26308666cd in poll () from /usr/lib/libc.so.6 #1 0x7f26286468e0 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f2628648679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f261fca5469 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f2630f5cd78 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f262a854484 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f263086f6dd in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f2635eff8c0 (LWP 10151)): [KCrash Handler] #5 0x7f262f6f57a0 in ?? () from /usr/lib/liblcms2.so.2 #6 0x7f262f6fc41b in ?? () from /usr/lib/liblcms2.so.2 #7 0x7f26356b83d2 in Gwenview::RasterImageView::updateFromScaler(int, int, QImage const&) () from /usr/lib/libgwenviewlib.so.5 #8 0x7f263116285e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #9 0x7f2635735b71 in Gwenview::ImageScaler::scaledRect(int, int, QImage const&) () from /usr/lib/libgwenviewlib.so.5 #10 0x7f26356e0357 in Gwenview::ImageScaler::scaleRect(QRect const&) () from /usr/lib/libgwenviewlib.so.5 #11 0x7f26356e09b7 in Gwenview::ImageScaler::doScale() () from /usr/lib/libgwenviewlib.so.5 #12 0x7f26356b6a67 in Gwenview::RasterImageView::updateImageRect(QRect const&) () from /usr/lib/libgwenviewlib.so.5 #13 0x7f2635737809 in ?? () from /usr/lib/libgwenviewlib.so.5 #14 0x7f26311624e9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #15 0x7f2635734b45 in Gwenview::Document::imageRectUpdated(QRect const&) () from /usr/lib/libgwenviewlib.so.5 #16 0x7f26311624e9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #17 0x7f2635734822 in ?? () from /usr/lib/libgwenviewlib.so.5 #18 0x7f26356a096b in ?? () from /usr/lib/libgwenviewlib.so.5 #19 0x7f2635695db5 in Gwenview::Document::switchToImpl(Gwenview::AbstractDocumentImpl*) () from /usr/lib/libgwenviewlib.so.5 #20 0x7f26356a1ab8 in ?? () from /usr/lib/libgwenviewlib.so.5 #21 0x7f26311624e9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #22 0x7f2630f53711 in QFutureWatcherBase::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #23 0x7f2632825e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #24 0x7f263282d5b1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #25 0x7f2631136c80 in QCoreApplication::notifyInt
[plasmashell] [Bug 355504] xembedsniproxy: java tray icon doesn't work
https://bugs.kde.org/show_bug.cgi?id=355504 --- Comment #17 from Rex Dieter --- You'll have to ask your distro for packaging details, but I can *guess* one reason may be plasma5-workspace-5.5.5.2-12.1.x86_64 includes xembedsniproxy itself (ie, it's no longer packaged separately). -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 366307] activity manager daemon crash
https://bugs.kde.org/show_bug.cgi?id=366307 Christoph Feck changed: What|Removed |Added CC||chan...@gmail.com Product|kde |plasma4 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Component|general |activities -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 Marcelo Rocha changed: What|Removed |Added CC||marcelo@marcelocavalcante.n ||et --- Comment #42 from Marcelo Rocha --- I can confirm the bug is still there.. I am running Arch linux with the last versions of plasma and I am with the same issue.. When logging into my system, my second screen is black and right clicking doesn't work. But after running "kquitapp plasmashell && kstart plasmashell" both my screen are reloaded and I can go back to my work.. So far I am running this "fix" everytime I log into my system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #61 from Samantha McVey --- (In reply to nicholas from comment #60) At that time I didn't see any movement in the tray, but that usually seems to be what triggers the bug, or at the very least makes it occur quicker and worse. I am using 5.7.2 btw. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #60 from nicholas --- not sure what to make of all this, im a dumb python programmer! do you actually have high cpu with spinners going? On 1 August 2016 at 15:10, Samantha McVey via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=356479 > > --- Comment #59 from Samantha McVey --- > Created attachment 100407 > --> https://bugs.kde.org/attachment.cgi?id=100407&action=edit > strace of plasmashell > > Here is an strace. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 366307] activity manager daemon crash
https://bugs.kde.org/show_bug.cgi?id=366307 Ivan Čukić changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||ivan.cu...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ivan Čukić --- Plasma 4.x (and accomp. components) are unmaintained. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 366326] OFX direct download fails when OFX UID is expected by bank
https://bugs.kde.org/show_bug.cgi?id=366326 Jeff changed: What|Removed |Added CC||jeffjl@outlook.com --- Comment #1 from Jeff --- I don't recall a patch to KMM that fixed this. AqBanking implements the and that is the workaround I remember. The problem is that libofx does not implement . I have modified my copy of libofx to implement the and hacked my copy of KMM to use it, and that works with my Chase accounts. But I also made a lot of other libofx changes to better support investment accounts. About a couple of weeks ago, I sent an email to the sourceforge libofx mailing list with my patch and got no response. Not sure what to do next. -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 366327] New: Cross-compiling QCA. Make errors
https://bugs.kde.org/show_bug.cgi?id=366327 Bug ID: 366327 Summary: Cross-compiling QCA. Make errors Product: qca Version: 2.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dr...@land.ru Reporter: zaleski.mik...@gmail.com CC: br...@frogmouth.net, jus...@affinix.com I want to build QCA for ARM Linux and Qt 4.8 I have successfully compiled OpenSSL 1.1.0 and Qt 4.8.6 for ARM platform Then I tried to build QCA with cmake. I set paths to qt, openssl and cross-compiler through the toolchain-file and interface of ccmake. But when I tried to make (verbose=1) I got an error: [ 94%] Linking CXX shared module ../../lib/qca/crypto/libqca-gnupg.so cd /home/zaleski/dev/cpp/sources/qca-2.1.1/build/plugins/qca-gnupg && /usr/bin/cmake -E cmake_link_script CMakeFiles/qca-gnupg.dir/link.txt --verbose=1 /opt/codesourcery/bin/arm-none-linux-gnueabi-g++ -fPIC -Wcast-align -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -Wformat-security -fno-check-new -fno-common -g2 -shared -o ../../lib/qca/crypto/libqca-gnupg.so CMakeFiles/qca-gnupg.dir/qca-gnupg.cpp.o CMakeFiles/qca-gnupg.dir/gpgop.cpp.o CMakeFiles/qca-gnupg.dir/utils.cpp.o CMakeFiles/qca-gnupg.dir/gpgproc/sprocess.cpp.o CMakeFiles/qca-gnupg.dir/mypgpkeycontext.cpp.o CMakeFiles/qca-gnupg.dir/mykeystoreentry.cpp.o CMakeFiles/qca-gnupg.dir/myopenpgpcontext.cpp.o CMakeFiles/qca-gnupg.dir/mykeystorelist.cpp.o CMakeFiles/qca-gnupg.dir/mymessagecontext.cpp.o CMakeFiles/qca-gnupg.dir/ringwatch.cpp.o CMakeFiles/qca-gnupg.dir/lineconverter.cpp.o CMakeFiles/qca-gnupg.dir/gpgaction.cpp.o CMakeFiles/qca-gnupg.dir/gpgproc/gpgproc.cpp.o CMakeFiles/qca-gnupg.dir/moc_gpgop.cxx.o CMakeFiles/qca-gnupg.dir/moc_gpgop_p.cxx.o CMakeFiles/qca-gnupg.dir/gpgproc/moc_gpgproc.cxx.o CMakeFiles/qca-gnupg.dir/gpgproc/moc_gpgproc_p.cxx.o CMakeFiles/qca-gnupg.dir/gpgproc/moc_sprocess.cxx.o CMakeFiles/qca-gnupg.dir/moc_ringwatch.cxx.o CMakeFiles/qca-gnupg.dir/moc_mykeystorelist.cxx.o CMakeFiles/qca-gnupg.dir/moc_mymessagecontext.cxx.o CMakeFiles/qca-gnupg.dir/moc_gpgaction.cxx.o /lib/libQtCore.so ../../lib/libqca.so.2.1.1 /lib/libQtCore.so -Wl,-rpath,/lib:/home/zaleski/dev/cpp/sources/qca-2.1.1/build/lib: make[2]: Leaving directory '/home/zaleski/dev/cpp/sources/qca-2.1.1/build' [ 94%] Built target qca-gnupg make[1]: Leaving directory '/home/zaleski/dev/cpp/sources/qca-2.1.1/build' Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 After second attempt of make I got such error: [ 98%] Linking CXX executable ../../bin/qcatool cd /home/zaleski/dev/cpp/sources/qca-2.1.1/build/tools/qcatool && /usr/bin/cmake -E cmake_link_script CMakeFiles/qcatool.dir/link.txt --verbose=1 /bin/arm-none-linux-gnueabi-g++-Wcast-align -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -Wformat-security -fno-check-new -fno-common -g2 CMakeFiles/qcatool.dir/main.cpp.o -o ../../bin/qcatool -rdynamic /lib/libQtCore.so ../../lib/libqca.so.2.1.1 /lib/libQtCore.so -Wl,-rpath,/lib:/home/zaleski/dev/cpp/sources/qca-2.1.1/build/lib: /lib/gcc/arm-none-linux-gnueabi/4.8.3/../../../../arm-none-linux-gnueabi/bin/ld: warning: libts-1.0.so.0, needed by /lib/libQtCore.so, not found (try using -rpath or -rpath-link) make[2]: Leaving directory '/home/zaleski/dev/cpp/sources/qca-2.1.1/build' [ 98%] Built target qcatool make[1]: Leaving directory '/home/zaleski/dev/cpp/sources/qca-2.1.1/build' Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 And after third and subsequent attempts of make I got such error: plugins/qca-ossl/CMakeFiles/qca-ossl.dir/build.make:67: recipe for target 'plugins/qca-ossl/CMakeFiles/qca-ossl.dir/qca-ossl.cpp.o' failed make[2]: *** [plugins/qca-ossl/CMakeFiles/qca-ossl.dir/qca-ossl.cpp.o] Error 1 make[2]: Leaving directory '/home/zaleski/dev/cpp/sources/qca-2.1.1/build' CMakeFiles/Makefile2:428: recipe for target 'plugins/qca-ossl/CMakeFiles/qca-ossl.dir/all' failed make[1]: *** [plugins/qca-ossl/CMakeFiles/qca-ossl.dir/all] Error 2 make[1]: Leaving directory '/home/zaleski/dev/cpp/sources/qca-2.1.1/build' Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 Why do I get different errors during make? What am I doing wrong? How to cross-build QCA correctly? The build of Qt uses external library Tslib. Seems that QCA can't find the path to tslib.so (see output of 2nd attempt of make). How should I specify the path to this library? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360219] Right Click opens files
https://bugs.kde.org/show_bug.cgi?id=360219 --- Comment #29 from Wolfgang Bauer --- (In reply to Eike Hein from comment #27) > My assumption is that this bug only happens after the state previously got > corrupted by using the context menu elsewhere. Well, in my case this occurs right after login, without doing anything else first. I.e. I just right-click on an icon in the folderview after logging in and it gets opened (in addition to showing the context menu). (In reply to Eike Hein from comment #28) > Here's an updated patch for Qt 5.7 if you want to test: > https://codereview.qt-project.org/#/c/166455/ I tried it and it does NOT help with this problem. Btw, Qt 5.7.0 failed to compile with this patch here, I had to remove the "0L" parameter in the call to deliverHoverEvent(). -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 363875] holidays setting in korganizer always set back to none
https://bugs.kde.org/show_bug.cgi?id=363875 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||mon...@kde.org --- Comment #3 from Laurent Montel --- Fixed in 5.3.0. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 364626] [RFE] Appropriate icon for airplane mode in network manager applet
https://bugs.kde.org/show_bug.cgi?id=364626 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||http://commits.kde.org/plas ||ma-nm/2d0150fc72981b27712ee ||80590d4b2741626e317 Version Fixed In||5.8.0 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Kai Uwe Broulik --- Git commit 2d0150fc72981b27712ee80590d4b2741626e317 by Kai Uwe Broulik. Committed on 01/08/2016 at 15:46. Pushed by broulik into branch 'master'. [Plasma-nm] Indicate flight mode in system tray icon This changes the tray icon to the airplane icon when in flight mode. Also changes the SwitchButton to use a PlasmaCore.IconItem instead of a PlasmaCore.Svg to be consisteht with the tray icon. FIXED-IN: 5.8.0 REVIEW: 128332 M +2-11 applet/contents/ui/SwitchButton.qml M +7-1applet/contents/ui/Toolbar.qml M +21 -0libs/declarative/connectionicon.cpp M +7-0libs/declarative/connectionicon.h http://commits.kde.org/plasma-nm/2d0150fc72981b27712ee80590d4b2741626e317 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it
https://bugs.kde.org/show_bug.cgi?id=364915 --- Comment #4 from Götz --- I see this issue since the past year, on an [AMD/ATI] Mullins, Radeon R3 Graphics. xf86-video-ati 7.7.0 mesa 12.0.1 linux 4.6.4 Plasma 5.7.2 Qt 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366328] New: missing option to install new languages
https://bugs.kde.org/show_bug.cgi?id=366328 Bug ID: 366328 Summary: missing option to install new languages Product: systemsettings Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcmshell Assignee: kdelibs-b...@kde.org Reporter: gandalflech...@gmail.com In systemsettings -> translations, one can select "preferred" languages from "available" languages. It would be most natural to have the option to install new languages from here. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 366277] klipper systray applet autostarts on non-plasma DE's
https://bugs.kde.org/show_bug.cgi?id=366277 Jonathan Riddell changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Jonathan Riddell --- http://commits.kde.org/plasma-workspace/7ff606de2c7bcd8d2ea2893f01390b48f8b283e3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364329] System forgets custom login screen background image
https://bugs.kde.org/show_bug.cgi?id=364329 Gandalf Lechner changed: What|Removed |Added CC||gandalflech...@gmail.com --- Comment #3 from Gandalf Lechner --- same problem using kde neon -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366233] Brush tool no longer draws but cursor is still visible and moving
https://bugs.kde.org/show_bug.cgi?id=366233 --- Comment #2 from contramuf...@gmail.com --- I'm sorry but I couldn't figure out where instant preview is. Can you tell me where to find it? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366233] Brush tool no longer draws but cursor is still visible and moving
https://bugs.kde.org/show_bug.cgi?id=366233 --- Comment #3 from contramuf...@gmail.com --- I'm sorry but I couldn't figure out where instant preview is. Can you tell me where to find it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366329] New: Crash when dragging widget to secondary monitor (dual monitor system)
https://bugs.kde.org/show_bug.cgi?id=366329 Bug ID: 366329 Summary: Crash when dragging widget to secondary monitor (dual monitor system) Product: plasmashell Version: 5.7.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: briana...@hotmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.7.1) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.6.4-301.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Dragging desktop widget to secondary monitor causes Plasma to crash. Only happens every few times when moving the widgets and seems to happen with all widget types I have tried. - Unusual behavior I noticed: Upon crash desktop reverts to a "generic" background and loses my wallpaper config. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff1a6086940 (LWP 1638))] Thread 8 (Thread 0x7ff0edb62700 (LWP 2073)): #0 0x7ff1b4a7d32d in poll () from /lib64/libc.so.6 #1 0x7ff1b01c7a46 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7ff1b01c7b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7ff1b588324b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7ff1b58325ea in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff1b5691343 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7ff0ef7392e7 in KCupsConnection::run() () from /lib64/libkcupslib.so #7 0x7ff1b569599a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7ff1b3de25ca in start_thread () from /lib64/libpthread.so.0 #9 0x7ff1b4a88ead in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7ff0ffd88700 (LWP 1850)): #0 0x7ff1b4a7d32d in poll () from /lib64/libc.so.6 #1 0x7ff1b01c7a46 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7ff1b01c7b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7ff1b588324b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7ff1b58325ea in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff1b5691343 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7ff1b92eec66 in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #7 0x7ff1b569599a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7ff1b3de25ca in start_thread () from /lib64/libpthread.so.0 #9 0x7ff1b4a88ead in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7ff18e39a700 (LWP 1802)): #0 0x7ff1b3de7bd0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7ff1bb183bc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7ff1bb183c09 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7ff1b3de25ca in start_thread () from /lib64/libpthread.so.0 #4 0x7ff1b4a88ead in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7ff18700 (LWP 1800)): #0 0x7ff1b020bb64 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7ff1b01c6f70 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7ff1b01c796b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7ff1b01c7b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7ff1b588324b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff1b58325ea in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7ff1b5691343 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7ff1b89658f5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #8 0x7ff1b569599a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7ff1b3de25ca in start_thread () from /lib64/libpthread.so.0 #10 0x7ff1b4a88ead in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7ff195be0700 (LWP 1681)): #0 0x7ff1b020bb49 in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7ff1b01c747c in g_main_context_check () from /lib64/libglib-2.0.so.0 #2 0x7ff1b01c79e4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7ff1b01c7b5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7ff1b588324b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff1b58325ea in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7ff1b5691343 in QThread::exec() () from
[kmail2] [Bug 362608] Default colours unusable on dark theme
https://bugs.kde.org/show_bug.cgi?id=362608 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #1 from Alexander Potashev --- Same problem here with KMail 5.2.3. other versions: KDE Frameworks 5.24.0, Qt 5.6.1 (собрана с версией 5.6.1), Оконную систему xcb. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366330] New: Fancy Headers have black background on paper when color scheme is Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=366330 Bug ID: 366330 Summary: Fancy Headers have black background on paper when color scheme is Breeze Dark Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: aspotas...@gmail.com see Steps to Reproduce below Reproducible: Always Steps to Reproduce: 1. Set color scheme to Breeze Dark in Plasma System Settings. 2. Set header style to Fancy Headers in KMail. 3. Print an e-mail. Actual Results: The headers are white on black which is waste of toner. Expected Results: Default color scheme (with blue fancy headers) should be used when printing. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 366326] OFX direct download fails when OFX UID is expected by bank
https://bugs.kde.org/show_bug.cgi?id=366326 Swj changed: What|Removed |Added CC||s...@pobox.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363329] git master: playback cannot be stopped after end of project with preview rendering
https://bugs.kde.org/show_bug.cgi?id=363329 --- Comment #3 from Wegwerf --- Hah! After running this regression project through my project analyzer, I finally see that the hidden "black" track #0 has a problem: both user tracks are 00:11:06 in length. Yet the black track is calculated to have a length of 02:19:00! Close inspection shows that the track #0 playlist itself is (almost?) sane: its "out" point is at 3475, or 00:02:19:00. However, the visible timeline is only 00:11:06. So the black track completely got out of sync and looks like the cause for this hickup. Is there any way to reset the hidden black track? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 363430] Plasma crashes on right click on the menu
https://bugs.kde.org/show_bug.cgi?id=363430 Phil Evans changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID --- Comment #6 from Phil Evans --- Thank you - the "What happens if you remove ~/.local/share/kactivitymanagerd (log out before deleting, and log back in)" solved the problem (indirectly). When I came to delete this file, I couldn't - it transpired that a bunch of files in my .local directory were owned by root(!) I have no idea how this happened: I had restored some of my home area from backup (this machine was rebuilt following a motherboard failure) but I always do that via rsync -a which should preserve ownership. Anyhow, it's now fixed; thanks! I guess I should change the status to INVALID since one assumes the ownership problem is an error by me sometime, rather than an installer issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 363329] git master: playback cannot be stopped after end of project with preview rendering
https://bugs.kde.org/show_bug.cgi?id=363329 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Wegwerf --- I could now properly track down the issue to some strange issue with the preview rendering regions: there was an additional region around 02:19:00. By unsetting this regions, then adding a clip to the end of the ordinary timeline, and finally removing this trailing clip, Kdenlive properly resized the black track to be only of the overall length+1 frame ... as to be expected. So I'm now closing this bug as resolved/invalid, but still for others to find. Another bug less in our backlog! -- You are receiving this mail because: You are watching all bug changes.
