[plasmashell] [Bug 370516] Adding activity pager to panel causes plasmashell to crash [plasma 5.8.1]

https://bugs.kde.org/show_bug.cgi?id=370516 --- Comment #15 from Deri James --- I am running Mageia (Cauldron) with 5.8.1, have the same problem. I ran activity pager under plasmawindowed using gdb, after installing the debug package for libqt5core5. This is the

[plasmashell] [Bug 370516] Adding activity pager to panel causes plasmashell to crash [plasma 5.8.1]

https://bugs.kde.org/show_bug.cgi?id=370516 Deri James changed: What|Removed |Added CC|

[kmail2] [Bug 317072] kmail not checking mail on startup

https://bugs.kde.org/show_bug.cgi?id=317072 --- Comment #11 from James --- (In reply to Denis Kurz from comment #10) > This bug has only been reported for versions before 4.14, which have been > unsupported for at least two years now. Can anyone tell if this bug still >

[kactivitymanagerd] [Bug 366688] Segfault when started under kwin_wayland

https://bugs.kde.org/show_bug.cgi?id=366688 --- Comment #2 from James --- This crash is no longer occurring, after explicitly selecting the Breeze window decorations, at Martin's suggestion. But there is a crash backtrace at https://bugs.kde.org/show_bug.cgi?id=366689#c2 If

[frameworks-ktexteditor] [Bug 368129] Crash when switch between input modes

https://bugs.kde.org/show_bug.cgi?id=368129 Simon St James changed: What|Removed |Added CC|

[kate] [Bug 367786] Crash when I use VI input mode with the option "Let VI commands override Kate Shortcuts" and the Key Shift in command line ":"

https://bugs.kde.org/show_bug.cgi?id=367786 --- Comment #2 from Simon St James --- Will need to see the backtrace to know for certain, but is very probably a dupe of https://bugs.kde.org/show_bug.cgi?id=364650 -- You are receiving this mail because: You are

[kwin] [Bug 366689] kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0

https://bugs.kde.org/show_bug.cgi?id=366689 --- Comment #11 from James --- Ok - hopefully something simple: While dragging a window, the dragged window is visible only on the "first" display, and is not visible on the second or third display. The window becomes visible again

[kwin] [Bug 366689] kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0

https://bugs.kde.org/show_bug.cgi?id=366689 --- Comment #9 from James --- Oh - and do you want to deal with cut and paste right now? Gnome claims to have solved the middle button paste function. With the theming, let's decide on a baseline configuration, for the purpose of

[kwin] [Bug 366689] kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0

https://bugs.kde.org/show_bug.cgi?id=366689 --- Comment #8 from James --- Ha! Ok - thanks Martin. This is going to turn into a long, one by one, set of issues, I suspect. First - tell me, do you want to deal with making non-Breeze theming work right now? The problem set

[kwin] [Bug 366689] kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0

https://bugs.kde.org/show_bug.cgi?id=366689 --- Comment #6 from James --- Success! Actually, there is no "Window Style", but instead, there are "Widget Style" and "Window Decorations" menu items. I just then changed everything I could find to "Breeze", and that worked. I 

[kwin] [Bug 366689] kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0

https://bugs.kde.org/show_bug.cgi?id=366689 --- Comment #4 from James --- I'm not sure about aurorae decorations, but I opened system settings in regular X Windows KDE, selected Workspace Theme / Look And Feel, and selected "Breeze" instead of "Oxygen". Then I logged-out of

[kwin] [Bug 366689] kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0

https://bugs.kde.org/show_bug.cgi?id=366689 --- Comment #2 from James --- Thanks. If you tell me how to get the backtrace, I'll give it a shot. Everything and the only thing that "systemd-coredump" put in the system log was that single line systemd-coredump[996]: Process

[kwin] [Bug 366689] New: kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0

https://bugs.kde.org/show_bug.cgi?id=366689 Bug ID: 366689 Summary: kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0 Product: kwin Version: 5.7.3 Platform: Archlinux Packages OS: Linux

[kactivitymanagerd] [Bug 366688] New: Segfault when started under kwin_wayland

https://bugs.kde.org/show_bug.cgi?id=366688 Bug ID: 366688 Summary: Segfault when started under kwin_wayland Product: kactivitymanagerd Version: 5.7.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED

[kmymoney4] [Bug 365366] Can not download new Version

https://bugs.kde.org/show_bug.cgi?id=365366 --- Comment #5 from James --- So KDE Money 4.8 can not be used in Windows 10. or how do I download the new Version 4.8 then? -- You are receiving this mail because: You are watching all bug changes.

[kde] [Bug 365366] New: Can not download new Version

https://bugs.kde.org/show_bug.cgi?id=365366 Bug ID: 365366 Summary: Can not download new Version Product: kde Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 James changed: What|Removed |Added Resolution|--- |FIXED

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 James changed: What|Removed |Added Version|5.6.4 |5.7.0 -- You are receiving this

[kde] [Bug 365307] New: Download

https://bugs.kde.org/show_bug.cgi?id=365307 Bug ID: 365307 Summary: Download Product: kde Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority:

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

https://bugs.kde.org/show_bug.cgi?id=363284 --- Comment #27 from james --- is there a fix in the works for the XP-Pen products, like the XP-Pen Artist Display 22HD? It works in krita 2.9, but not 3. -- You are receiving this mail because: You are watching all bug

[kate] [Bug 353332] No long able to save with CTRL-S in VI mode

https://bugs.kde.org/show_bug.cgi?id=353332 Simon St James changed: What|Removed |Added Resolution|--- |FIXED

[konqueror] [Bug 35333] file list settings are not saved

https://bugs.kde.org/show_bug.cgi?id=35333 Simon St James changed: What|Removed |Added Ever confirmed|0 |1

[konqueror] [Bug 35333] file list settings are not saved

https://bugs.kde.org/show_bug.cgi?id=35333 Simon St James changed: What|Removed |Added Status|CLOSED |RESOLVED

[frameworks-ktexteditor] [Bug 360418] Crash using 'g' in Vi-input mode

https://bugs.kde.org/show_bug.cgi?id=360418 Simon St James changed: What|Removed |Added Latest Commit|http://commits.kde.org/ktex

[kate] [Bug 353332] No long able to save with CTRL-S in VI mode

https://bugs.kde.org/show_bug.cgi?id=353332 Simon St James changed: What|Removed |Added CC|

[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones

https://bugs.kde.org/show_bug.cgi?id=363284 james changed: What|Removed |Added CC||jamesonr...@gmail.com -- You

[krita] [Bug 361515] [UGEE] Brush Cursor Doesn't Follow Ugee Tablet Pen on Hover

https://bugs.kde.org/show_bug.cgi?id=361515 james changed: What|Removed |Added CC||jamesonr...@gmail.com ---

[ark] [Bug 79023] wish: support for Web Archives (.war)

https://bugs.kde.org/show_bug.cgi?id=79023 --- Comment #8 from David P James --- Sorry, how is this "INVALID"? It was an actual, real, verifiable bug at the time it was filed. It was subsequently confirmed as a bug. For something to be "invalid" it has to have never been a

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 --- Comment #5 from James --- Now plasma-workspace 5.6.3-1 Still strange. The environment does not change, before and after running startplasmacompositor. systemd does not clear the files in /tmp/, just logging out and in again, so

[systemsettings] [Bug 361943] New: systemsettings - Workspace Theme - Desktop Theme - Get New Themes > Loading ... failed

https://bugs.kde.org/show_bug.cgi?id=361943 Bug ID: 361943 Summary: systemsettings - Workspace Theme - Desktop Theme - Get New Themes > Loading ... failed Product: systemsettings Version: 5.6.2 Platform: Archlinux Packages

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 --- Comment #4 from James --- Ok - finally - yes "export $(dbus-launch)" - BUT - apparently there is a running: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation that comes up with

[kde] [Bug 361471] GNOME services fail to clean-up after KDE "logout"

https://bugs.kde.org/show_bug.cgi?id=361471 --- Comment #2 from James --- Aha! Apparently, KDE just needs to kill the still running dbus-daemon. After startkde: $ ps lU 1000 F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 4 1000 30004 1 20

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 --- Comment #3 from James --- Ok, thanks. After exiting startkde the first time, this being the context for startplasmacompositor, there is: ps lU 1000 F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 4

[kde] [Bug 361471] GNOME services fail to clean-up after KDE "logout"

https://bugs.kde.org/show_bug.cgi?id=361471 --- Comment #1 from James --- I'm curious - how, and by what, are these gnome services being started? Is this a dbus/systemd thing? And if so, how would kde get a handle on these services? Or, is kde starting these gnome services

[kde] [Bug 361471] GNOME services fail to clean-up after KDE "logout"

https://bugs.kde.org/show_bug.cgi?id=361471 James changed: What|Removed |Added Summary|GNOME services fail to |GNOME services fail to

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 James changed: What|Removed |Added Version|5.6.1 |5.6.2 -- You are receiving this

[plasmashell] [Bug 361437] startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 --- Comment #1 from James --- I've now upgraded to 5.6.2. Something I've noticed: Prior to the upgrade, and continuing after the upgrade, I have now gotten kde into some mode where, independent of startplasmacompositor,

[kde] [Bug 361471] New: KDE fails to clean-up after "logout"

https://bugs.kde.org/show_bug.cgi?id=361471 Bug ID: 361471 Summary: KDE fails to clean-up after "logout" Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED

[plasmashell] [Bug 361437] New: startkde -> startplasmacompositor -> startkde = "blackscreen"

https://bugs.kde.org/show_bug.cgi?id=361437 Bug ID: 361437 Summary: startkde -> startplasmacompositor -> startkde = "blackscreen" Product: plasmashell Version: 5.6.1 Platform: Archlinux Packages OS: Linux

[kmymoney4] [Bug 359470] New: Older Date

https://bugs.kde.org/show_bug.cgi?id=359470 Bug ID: 359470 Summary: Older Date Product: kmymoney4 Version: 4.7.2 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: grave

[krita] [Bug 358901] Black Canvas appears and remains during start up- windows 7 (Not drivers)

https://bugs.kde.org/show_bug.cgi?id=358901 --- Comment #2 from James --- I attempted the suggested reset- unfortunately Krita ignored the command, and no pop up appeared. I attempted variations of hold duration for the combo but with no results- Krita would just open,

[krita] [Bug 358901] New: Black Canvas appears and remains during start up- windows 7 (Not drivers)

https://bugs.kde.org/show_bug.cgi?id=358901 Bug ID: 358901 Summary: Black Canvas appears and remains during start up- windows 7 (Not drivers) Product: krita Version: 2.9.10 Platform: Windows CE OS: other

[kwin] [Bug 356580] startplasmacompositor - kwin_wayland - "/usr/lib/startplasma" - hangs at "start_kdeinit_wrapper"

https://bugs.kde.org/show_bug.cgi?id=356580 --- Comment #3 from James --- One additional patch is required to gain a functioning desktop. The first issue involves kdeinit5 hanging while waiting on programs in the kwin repository/package:

[frameworks-kinit] [Bug 356580] New: startplasmacompositor - kwin_wayland - "/usr/lib/startplasma" - hangs at "start_kdeinit_wrapper"

https://bugs.kde.org/show_bug.cgi?id=356580 Bug ID: 356580 Summary: startplasmacompositor - kwin_wayland - "/usr/lib/startplasma" - hangs at "start_kdeinit_wrapper" Product: frameworks-kinit Version: unspecified