[Elisa] [Bug 468153] Changing Repeat Mode using the drop-down menu desynchronizes the toggle-button
https://bugs.kde.org/show_bug.cgi?id=468153 --- Comment #2 from Marcus Harrison --- Awesome! Thanks, and sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468153] New: Changing Repeat Mode using the drop-down menu desynchronizes the toggle-button
https://bugs.kde.org/show_bug.cgi?id=468153 Bug ID: 468153 Summary: Changing Repeat Mode using the drop-down menu desynchronizes the toggle-button Classification: Applications Product: Elisa Version: 22.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mar...@harrisonland.co.uk Target Milestone: --- SUMMARY There are two methods of changing the repeat behaviour of Elisa: you can click the button to cycle through Playlist, One and None; or you can click-and-hold to select the play mode from a drop-down menu. If you don't use the drop-down menu at all, just toggling by clicking the button, the three modes work as expected. If you choose the play mode from the drop-down menu, the play mode you selected will be active. However, after choosing from the drop-down menu, the button will no longer reflect the play mode you selected. Changing the play mode by toggling the button no longer works, and the play mode the button displays doesn't reflect the mode selected from the drop-down menu. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.4.6 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.13.0-valve36-1-neptune (64-bit) Graphics Platform: X11 Processors: 8 × AMD Custom APU 0405 Memory: 14.5 GiB of RAM Graphics Processor: AMD Custom GPU 0405 Manufacturer: Valve Product Name: Jupiter System Version: 1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 461505] Plasma Integration in Firefox - Failed to connect to the native host
https://bugs.kde.org/show_bug.cgi?id=461505 --- Comment #5 from Marcus Harrison --- Having the same issue. Confirmed the application is installed at /usr/bin/plasma-browser-integration-host, and the native application manifest exists at /usr/lib/mozilla/native-messaging-hosts/org.kde.plasma.browser_integration.json. This is with the native apt package installed. I believe it's an issue with the plugin/app itself, since when launching with a flatpak (which I expect to not be able to connect to the native host), and it has an extra line, "No such native application org.kde.plasma_browser_integration", which doesn't appear in the apt version. Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 2 × AMD A6-9220C RADEON R5, 5 COMPUTE CORES 2C+3G Memory: 3.8 GiB of RAM Graphics Processor: AMD STONEY Manufacturer: Google Product Name: Grunt System Version: rev6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 461505] Plasma Integration in Firefox - Failed to connect to the native host
https://bugs.kde.org/show_bug.cgi?id=461505 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459945] Multiple windows are force-opened in the center of the screen which shouldn't be
https://bugs.kde.org/show_bug.cgi?id=459945 --- Comment #5 from Marcus Harrison --- (In reply to Vlad Zahorodnii from comment #4) > Okay, can you check whether qtwaylandclient has been updated recently and > perhaps try to downgrade it? I suspect that qtwaylandclient had been > updated, but due to a packaging mishap, kwayland-integration was not rebuilt. I did run upgrades yesterday before experiencing this issue, not sure which version I upgraded _from_ though. Current installed version is 5.15.5+p20.04+tunstable+git20220909.1409-0. Using apt to try to downgrade to version 5.15.5+p20.04+tunstable+git20220809.0847-0 gives a resolution that attempts to remove most depending KDE software and some system-critical packages (including neon-desktop), so I'm holding fire on doing that for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459945] Multiple windows are force-opened in the center of the screen which shouldn't be
https://bugs.kde.org/show_bug.cgi?id=459945 --- Comment #3 from Marcus Harrison --- (In reply to Vlad Zahorodnii from comment #2) > Can you check whether you have kwayland-integration or any package with > similar name (the naming may differ based on distro package naming > conventions) installed? Looks like I do indeed have that package installed: Installed kwayland-integration-4:5.25.5-0xneon+20.04+focal+release+build59.amd64 (installed:user_focal-focal-main) > Also, if you change the placement policy to > zero-cornered, are those windows placed differently? Interestingly, when I set the policy to zero-cornered, KRunner begins opening in the top-left corner, but the plasma panel pop-ups continue to appear in the center, rising up from the panel, and the notifications still appear in the center of the screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459945] Multiple windows are force-opened in the center of the screen which shouldn't be
https://bugs.kde.org/show_bug.cgi?id=459945 --- Comment #1 from Marcus Harrison --- I just confirmed that this happens with a brand new user account using default settings as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459945] New: Multiple windows are force-opened in the center of the screen which shouldn't be
https://bugs.kde.org/show_bug.cgi?id=459945 Bug ID: 459945 Summary: Multiple windows are force-opened in the center of the screen which shouldn't be Classification: Plasma Product: kwin Version: 5.25.5 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- SUMMARY Various windows which shouldn't open in the center of the screen are being forced to, including KRunner with Top position set, plasma widget pop-outs and plasma notifications. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: Wayland Processors: 2 × AMD A6-9220C RADEON R5, 5 COMPUTE CORES 2C+3G Memory: 3.8 GiB of RAM Graphics Processor: AMD STONEY Manufacturer: Google Product Name: Grunt System Version: rev6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454496] Krita crash on save
https://bugs.kde.org/show_bug.cgi?id=454496 --- Comment #4 from Marcus Harrison --- Ah, looks like it's solved in the duplicated ticket. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454496] Krita crash on save
https://bugs.kde.org/show_bug.cgi?id=454496 --- Comment #3 from Marcus Harrison --- Created attachment 149732 --> https://bugs.kde.org/attachment.cgi?id=149732=edit New crash information added by DrKonqi krita (5.0.5) using Qt 5.15.4 Using the save dialogue - such as from the "Save As..." or "Export..." menu options - produces the crash. When opening an existing file and using the "Save" menu option, no crash happens. Seems to be confirmed in the backtrace in the `KisPreviewFileDialog` destructor. -- Backtrace (Reduced): #4 0x7f4fcf30ec47 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x2) at /usr/include/c++/9/bits/atomic_base.h:413 #5 QAtomicOps::loadRelaxed (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x2) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 [...] #8 QList::~QList (this=0x55849ceed240, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:873 #9 0x7f4fcf39878c in KToolBar::Private::~Private (this=0x55849ceed190, __in_chrg=) at ./libs/widgetutils/xmlgui/ktoolbar.cpp:83 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454496] Krita crash on save
https://bugs.kde.org/show_bug.cgi?id=454496 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451049] New: Web View widgets don't scroll with touchpad scrolling
https://bugs.kde.org/show_bug.cgi?id=451049 Bug ID: 451049 Summary: Web View widgets don't scroll with touchpad scrolling Product: kwin Version: 5.24.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- SUMMARY In applications that use the WebView component (e.g. KMail, Falkon), touch-pad scrolling (e.g. two-finger scrolling) doesn't work with the WebView component. In particular, in Kontact, two-finger scrolling works with every _other_ widget, just not the Mail View widget, which uses a WebView to render E-mails. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-30-generic (64-bit) Graphics Platform: Wayland Processors: 2 × AMD A6-9220C RADEON R5, 5 COMPUTE CORES 2C+3G Memory: 3.8 GiB of RAM Graphics Processor: AMD STONEY -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 438686] New: Plasma desktop launches incorrect application
https://bugs.kde.org/show_bug.cgi?id=438686 Bug ID: 438686 Summary: Plasma desktop launches incorrect application Product: plasma-simplemenu Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: mar...@harrisonland.co.uk CC: plasma-b...@kde.org Target Milestone: --- SUMMARY On Wayland, when launching an application from simple application launcher, the menu launcher or KRunner, plasma instead launches the previously-selected application. For example: On first logging in, using the Simple Menu to launch Dolphin does nothing. After attempting to launch Dolphin, using the Simple Menu to launch Kate instead launches Dolphin. Then, attempting to launch Konsole instead launches Kate. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 429842] New: Crash resizing Elisa on kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=429842 Bug ID: 429842 Summary: Crash resizing Elisa on kwin_wayland Product: elisa Version: 20.08.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: elisa (20.08.3) Qt Version: 5.15.1 Frameworks Version: 5.76.0 Operating System: Linux 5.4.0-54-generic x86_64 Windowing system: Wayland Distribution: KDE neon User Edition 5.20 -- Information about the crash: Multiple times after starting Elisa, resizing the window caused a crash. The, "Scanning music" notification was displaying; The view was on a selected song ready to play, but not playing yet; The playlist was populated with 25 tracks and overflowing the view, producing a scrollbar; There was album art correctly displayed in the central view and as the background of the "header" view. After a third attempt, waiting for the, "Scanning music" notification to finish and resizing the window did not cause another crash. The crash can be reproduced sometimes. -- Backtrace: Application: Elisa (elisa), signal: Aborted [New LWP 502974] [New LWP 502975] [New LWP 502976] [New LWP 502977] [New LWP 502978] [New LWP 502979] [New LWP 502980] [New LWP 502981] [New LWP 502982] [New LWP 502983] [New LWP 502984] [New LWP 502985] [New LWP 502990] [New LWP 502992] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x555b21e8d554) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7f3a0f315880 (LWP 502971))] Thread 15 (Thread 0x7f39ceffd700 (LWP 502992)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f3a141c9859 in __GI_abort () at abort.c:79 #6 0x7f3a1460bbe7 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7f39ceffc9b0, msg=msg@entry=0x7f3a0e7ba0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #8 0x7f3a0e6fecd5 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlogging.h:90 #9 QtWaylandClient::QWaylandDisplay::checkError (this=) at qwaylanddisplay.cpp:204 #10 0x7f3a0e70f671 in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) (this=0x555b2127a220, queue=0x555b216412d0, condition=..., timeout=timeout@entry=100) at qwaylanddisplay.cpp:260 #11 0x7f3a0e716628 in QtWaylandClient::QWaylandWindow::waitForFrameSync (this=0x555b219e7af0, timeout=100) at /usr/include/c++/9/new:174 #12 0x7f3a070fbdda in QtWaylandClient::QWaylandGLContext::swapBuffers (this=0x555b21afe290, surface=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:492 #13 0x7f3a15105a51 in QOpenGLContext::swapBuffers (this=0x555b21b96fa0, surface=) at kernel/qopenglcontext.cpp:1120 #14 0x7f3a1338ae2c in QSGRenderThread::syncAndRender (this=0x555b21e76ac0, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:870 #15 0x7f3a1338eba7 in QSGRenderThread::run (this=0x555b21e76ac0) at scenegraph/qsgthreadedrenderloop.cpp:1043 #16 0x7f3a14646b1c in QThreadPrivate::start (arg=0x555b21e76ac0) at thread/qthread_unix.cpp:329 #17 0x7f3a12c44609 in start_thread (arg=) at pthread_create.c:477 #18 0x7f3a142c6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f39cf7fe700 (LWP 502990)): #0 __GI___libc_read (nbytes=10, buf=0x7f39cf7fdb5e, fd=30) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=30, buf=0x7f39cf7fdb5e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f3a0fb78975 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f3a122bb416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f3a122bbeb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f3a122bbf70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f3a122ca11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f3a0fba772c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f3a12c44609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3a142c6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f39e27fc700 (LWP 502985)): #0 0x7f3a1233c095 in g_source_ref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3a1233c168 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3a1233daff in g_main_context_check () from
[korganizer] [Bug 426718] "Use email settings from System Settings" option sets event organizer to wrong user
https://bugs.kde.org/show_bug.cgi?id=426718 --- Comment #2 from Marcus Harrison --- I _do_ see both users in the combobox, but the default is the [develop] user. Interestingly, I see three options - two Marcus Harrison options with the two different E-mail addresses I have set up for it, and the [develop] option which is selected by default. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 426718] New: "Use email settings from System Settings" option sets event organizer to wrong user
https://bugs.kde.org/show_bug.cgi?id=426718 Bug ID: 426718 Summary: "Use email settings from System Settings" option sets event organizer to wrong user Product: korganizer Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- SUMMARY I have a system with the following two users: Marcus Harrison [mharrison] Marcus Harrison (Development) [develop] I'm logged in to the mharrison account. In System Settings --> Account Details, I have them each set up with a different E-mail address. In KMail in mharrison, I have both E-mail addresses set up with incoming/outgoing accounts and identities. In Configure KOrganizer, I have the "Use email settings from System Settings" option checked. If I create a new Event in the Agenda view, and show the Attendies tab, the, "Meeting organizer" field is set to the username and email address set for the [develop] system account, even though the current user account is [mharrison]. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-47-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426632] The Emoji Picker should raise and focus when using the shortcut if it is already open
https://bugs.kde.org/show_bug.cgi?id=426632 --- Comment #3 from Marcus Harrison --- I tested with Spectacle, a QWidgets application, and it does _not_ exhibit this behaviour. Pressing the Screenshot button when the application is out of focus will correctly raise and focus Spectacle. System information, since I forgot to add it: Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-47-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426632] The Emoji Picker should raise and focus when using the shortcut if it is already open
https://bugs.kde.org/show_bug.cgi?id=426632 --- Comment #2 from Marcus Harrison --- Alright, as I was doing more testing I found that this problem occurs with Plasma Discover as well, another QML(/Kirigami?) application. It will open packages/the updates page/etc. to requests, but not raise and focus the window. I've created a new user to test and found that this happens in a clean environment for both applications. Seems likely to be a Kirigami bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426632] New: The Emoji Picker should raise and focus when using the shortcut if it is already open
https://bugs.kde.org/show_bug.cgi?id=426632 Bug ID: 426632 Summary: The Emoji Picker should raise and focus when using the shortcut if it is already open Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Emoji picker Assignee: plasma-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: 1.0 With default Window Focus Behaviour settings on X11, using the emoji selector global shortcut when it is already open does not raise or focus the window. This makes using it annoying if the user doesn't remember to close it every time they're finished, having to search through their open windows for it. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425072] KDE Telepathy Contact List package still provided by ubuntu, throws linker error on launch
https://bugs.kde.org/show_bug.cgi?id=425072 Marcus Harrison changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Marcus Harrison --- Just did a distribution upgrade and the ktp-contactlist application launches without issues now, closing as fixed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425072] New: KDE Telepathy Contact List package still provided by ubuntu, throws linker error on launch
https://bugs.kde.org/show_bug.cgi?id=425072 Bug ID: 425072 Summary: KDE Telepathy Contact List package still provided by ubuntu, throws linker error on launch Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: mar...@harrisonland.co.uk CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY KDE Neon provides its own package builds for most of the KDE telepathy components, but does not provide a package for kde-telepathy-contact-list. This package is still provided by upstream Ubuntu, and attempting to run ktp-contactlist produces the error: ktp-contactlist: symbol lookup error: ktp-contactlist: undefined symbol: _ZN3KTp14GlobalPresence11setPresenceERKNS_8PresenceE SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 4.15.0-112-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 520 -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 345959] When an individual folder is set to prefer HTML to Plaintext, some E-mails with both HTML and plaintext parts will display the plaintext part
https://bugs.kde.org/show_bug.cgi?id=345959 --- Comment #6 from Marcus Harrison --- Sorry for the slow response. I'm not able to reproduce this any more either. If I find a failing E-mail I'll try to scrape it of personal information and attach it to the bug. -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 417635] New: Selecting Data --> Validity and applying rules freezes the application indefinitely
https://bugs.kde.org/show_bug.cgi?id=417635 Bug ID: 417635 Summary: Selecting Data --> Validity and applying rules freezes the application indefinitely Product: calligrasheets Version: 3.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: calligra-sheets-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- SUMMARY The validation function freezes Calligra Sheets until the user kills the application. This was tested with multiple types of cell selections (infinite/limited), with and without data and with both the number type and list type validations. STEPS TO REPRODUCE 1. Open Calligra. Create a new blank worksheet. 2. Go to Data --> Validity (note that on first opening the document, a single empty cell - A1 - is pre-selected). 3. Select a valid Validity (e.g. integer equal to 1, list of strings) OBSERVED RESULT The application freezes and consumes CPU until it is killed. EXPECTED RESULT Apply the validation. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 Kernel Version: 5.3.0-28-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 31,1 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414966] Akonadi crash when performing search with already-present Last Search results
https://bugs.kde.org/show_bug.cgi?id=414966 --- Comment #1 from Marcus Harrison --- Created attachment 124392 --> https://bugs.kde.org/attachment.cgi?id=124392=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414966] New: Akonadi crash when performing search with already-present Last Search results
https://bugs.kde.org/show_bug.cgi?id=414966 Bug ID: 414966 Summary: Akonadi crash when performing search with already-present Last Search results Product: Akonadi Version: 5.12.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: akonadiserver (5.12.3) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.15.0-72-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I used the search function (under Tools -> Find Messages...) to create a search folder called Last Search. The first search was successful. Consecutive attempts to use the same search function with different parameters failed, searching forever without updating the Last Search folder. Sometimes the Last Search folder would populate with all messages in the searched folders. Finally, quiting Kontact caused both Kontact and Akonadi server to crash. Performing these steps in sequence fairly reliably causes the crash in my experience. The crash can be reproduced every time. -- Backtrace (Reduced): #6 _mm_crc32_u64 (__V=, __C=) at /usr/lib/gcc/x86_64-linux-gnu/7/include/smmintrin.h:848 #7 crc32 (ptr=0xfe0600044fe0, len=, h=) at tools/qhash.cpp:112 #8 0x7f03a144e3c2 in hash (seed=, len=, p=) at tools/qhash.cpp:223 #9 qHash (key=..., seed=) at tools/qhash.cpp:239 #10 0x55ba0511201b in QHash::findNode (this=this@entry=0x55ba0609b328, akey=..., ahp=ahp@entry=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:934 Possible duplicates by query: bug 414229, bug 413844, bug 413385, bug 413205, bug 413201. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414700] New: akonadi_mailfilter_agent segmentation fault for new
https://bugs.kde.org/show_bug.cgi?id=414700 Bug ID: 414700 Summary: akonadi_mailfilter_agent segmentation fault for new Product: Akonadi Version: 5.12.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Mail Filter Agent Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: akonadi_mailfilter_agent (5.12.3) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.15.0-70-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I had just finished adding a new, custom E-mail filter and had executed it manually on an IMAP folder. - Custom settings of the application: This E-mail filter is unlike my other mail filters in two ways: 1. It filters on `From`: `is not in address book`; 2. It only filters incoming E-mails from a specific IMAP account, configured under the Advanced tab --> Apply this filter to incoming messages: --> from checked accounts only I will try to further narrow down which of these is causing the crash. The crash can be reproduced every time. -- Backtrace: Application: akonadi_mailfilter_agent (akonadi_mailfilter_agent), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3a17f24bc0 (LWP 24500))] Thread 7 (Thread 0x7f39bd671700 (LWP 26910)): #0 0x7f3a12b95bf9 in __GI___poll (fds=0x7f39b0004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3a081e95c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3a081e96dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3a13700b9b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f39bb20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3a136a106a in QEventLoop::exec(QFlags) (this=this@entry=0x7f39bd6709e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f3a134bc3aa in QThread::exec() (this=) at thread/qthread.cpp:531 #6 0x7f3a134bdb52 in QThreadPrivate::start(void*) (arg=0x558937b40500) at thread/qthread_unix.cpp:360 #7 0x7f3a16dde6db in start_thread (arg=0x7f39bd671700) at pthread_create.c:463 #8 0x7f3a12ba288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f39ce902700 (LWP 24740)): #0 0x7f3a16de8082 in __pthread_disable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:96 #1 0x7f3a16de8399 in __libc_read (fd=13, buf=0x7f39ce9017d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #2 0x7f3a0822e2d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3a081e90b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3a081e9570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3a081e96dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3a13700b9b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f39c4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f3a136a106a in QEventLoop::exec(QFlags) (this=this@entry=0x7f39ce9019e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #8 0x7f3a134bc3aa in QThread::exec() (this=) at thread/qthread.cpp:531 #9 0x7f3a134bdb52 in QThreadPrivate::start(void*) (arg=0x558937a43740) at thread/qthread_unix.cpp:360 #10 0x7f3a16dde6db in start_thread (arg=0x7f39ce902700) at pthread_create.c:463 #11 0x7f3a12ba288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f39cf103700 (LWP 24640)): #0 0x7f3a0822f664 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3a081e8b18 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3a081e94fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3a081e96dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3a13700b9b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f39cb20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f3a136a106a in QEventLoop::exec(QFlags) (this=this@entry=0x7f39cf1029e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f3a134bc3aa in QThread::exec() (this=) at thread/qthread.cpp:531 #7 0x7f3a134bdb52 in QThreadPrivate::start(void*) (arg=0x558937a1a470) at thread/qthread_unix.cpp:360 #8 0x7f3a16dde6db in start_thread (arg=0x7f39cf103700) at pthread_create.c:463 #9 0x7f3a12ba288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f39cf904700 (LWP 24633)): #0 0x7f3a16de8384 in __libc_read (fd=7, buf=0x7f39cf9037a0, nbytes=16) at
[marble] [Bug 413456] New: [Marble Maps 1.2] No map data is downloaded
https://bugs.kde.org/show_bug.cgi?id=413456 Bug ID: 413456 Summary: [Marble Maps 1.2] No map data is downloaded Product: marble Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Created attachment 123488 --> https://bugs.kde.org/attachment.cgi?id=123488=edit Screenshot displaying the issue I installed Marble maps 1.2.0 using the APK found at https://files.kde.org/marble/downloads/android/. The star map, sun and moon display correctly when zoomed out fully, but no street map data at all is displayed (even land mass/continent data) at any zoom level. I have attempted clearing the application's cache, data and reinstalling. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 413359] New: Window is slow to resize
https://bugs.kde.org/show_bug.cgi?id=413359 Bug ID: 413359 Summary: Window is slow to resize Product: elisa Version: 0.4.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mar...@harrisonland.co.uk Target Milestone: --- The Elisa main window is slow to resize and resizing results in flickering in the topmost UI element (specifically the background/album art images). Results are the same in both X and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk --- Comment #24 from Marcus Harrison --- Created attachment 123014 --> https://bugs.kde.org/attachment.cgi?id=123014=edit supportInformation output This bug appears to be the same as the one I'm experiencing but I get different symptoms. In my case, plasma shell panels/pop-ups and translucent KWin decorations are blurred correctly. However, setting translucency in Konsole does not apply the blur. Starting Konsole with `konsole -platform xcb` applies the blur correctly. Additionally, translucent KVantum themes are not blurred. Attached supportInformation output. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 411588] New: Compounded use statements not parsed correctly
https://bugs.kde.org/show_bug.cgi?id=411588
Bug ID: 411588
Summary: Compounded use statements not parsed correctly
Product: kdevelop
Version: 5.4.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language Support: PHP
Assignee: kdevelop-bugs-n...@kde.org
Reporter: mar...@harrisonland.co.uk
Target Milestone: ---
As of PHP 7, a single "use" statement can refer to multiple aliases through the
use of curly braces:
// pre PHP7
use Foo\Bar\Baz;
use Foo\Bar\Barry;
// post PHP7
use Foo\Bar\{Baz, Barry};
Documentation: https://www.php.net/manual/en/language.namespaces.importing.php
This currently is considered a syntax error by the parser.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 408999] New: Konsole crash on stopping activity
https://bugs.kde.org/show_bug.cgi?id=408999 Bug ID: 408999 Summary: Konsole crash on stopping activity Product: konsole Version: 19.04.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: konsole (19.04.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.18.0-22-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I was running tmux in a Konsole window with only one tab. I switched to another Plasma activity and stopped the activity running the Konsole window, which lead to this crash. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f08202a5800 (LWP 1714))] Thread 2 (Thread 0x7f0803330700 (LWP 1721)): #0 0x7f081fbbc0b4 in __GI___libc_read (fd=7, buf=0x7f080332fb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f0815435000 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f08153effb7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f08153f0470 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f08153f05dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f081c057dcb in QEventDispatcherGlib::processEvents (this=0x7f07fc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f081bff903a in QEventLoop::exec (this=this@entry=0x7f080332fd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f081be204ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f0819852015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f081be21c72 in QThreadPrivate::start (arg=0x7f0819ac9d80) at thread/qthread_unix.cpp:361 #10 0x7f08171366db in start_thread (arg=0x7f0803330700) at pthread_create.c:463 #11 0x7f081fbcd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f08202a5800 (LWP 1714)): [KCrash Handler] #6 QHashNode::same_key (this=0x0, this=0x0, key0=@0x7ffc74b53a5c: 48235529, h0=247331385) at ../../../../include/QtCore/../../src/corelib/tools/qhash.h:158 #7 QHash::findNode (h=247331385, akey=@0x7ffc74b53a5c: 48235529, this=0x55bc28498808) at ../../../../include/QtCore/../../src/corelib/tools/qhash.h:919 #8 QHash::findNode (this=this@entry=0x55bc28498808, akey=@0x7ffc74b53a5c: 48235529, ahp=ahp@entry=0x0) at ../../../../include/QtCore/../../src/corelib/tools/qhash.h:938 #9 0x7f080db1c358 in QHash::remove (this=0x55bc28498808, akey=@0x7ffc74b53a5c: 48235529, akey@entry=@0x7ffc74b53a5c: ) at ../../../../include/QtCore/../../src/corelib/tools/qhash.h:806 #10 0x7f080db1b459 in QXcbConnection::removeWindowEventListener (this=, id=) at qxcbconnection.cpp:178 #11 0x7f080db2c341 in QXcbWindow::destroy (this=this@entry=0x7f0804010ea0) at qxcbwindow.cpp:569 #12 0x7f080db2c431 in QXcbWindow::~QXcbWindow (this=0x7f0804010ea0, __in_chrg=) at qxcbwindow.cpp:537 #13 0x7f0801cf96ad in QXcbGlxWindow::~QXcbGlxWindow (this=0x7f0804010ea0, __in_chrg=) at qxcbglxwindow.cpp:53 #14 QXcbGlxWindow::~QXcbGlxWindow (this=0x7f0804010ea0, __in_chrg=) at qxcbglxwindow.cpp:55 #15 0x7f081c5ce611 in QWindowPrivate::destroy (this=0x55bc28a3a410) at kernel/qwindow.cpp:1908 #16 0x7f081ce25ca4 in QWidgetPrivate::deleteTLSysExtra (this=0x55bc287fd410) at kernel/qwidget.cpp:1901 #17 0x7f081ce2ab88 in QWidget::destroy (this=this@entry=0x55bc28827370, destroyWindow=destroyWindow@entry=true, destroySubWindows=destroySubWindows@entry=true) at kernel/qwidget.cpp:12494 #18 0x7f081ce322c8 in QWidget::~QWidget (this=0x55bc28827370, __in_chrg=) at kernel/qwidget.cpp:1713 #19 0x7f081cf6d179 in QMenu::~QMenu (this=0x55bc28827370, __in_chrg=) at widgets/qmenu.cpp:1724 #20 0x7f081f2d9a0a in KXMLGUIBuilder::removeContainer (this=0x55bc2852cd88, container=0x55bc28827370, parent=0x0, element=..., containerAction=0x0) at ./src/kxmlguibuilder.cpp:290 #21 0x7f081f2ef4e8 in KXMLGUI::ContainerNode::destruct (this=this@entry=0x55bc287fd990, element=..., state=...) at ./src/kxmlguifactory_p.cpp:325 #22 0x7f081f2ef613 in KXMLGUI::ContainerNode::destructChildren (this=this@entry=0x55bc285e2400, element=..., state=...) at ./src/kxmlguifactory_p.cpp:347 #23 0x7f081f2ef28c in KXMLGUI::ContainerNode::destruct (this=this@entry=0x55bc285e2400, element=..., state=...) at ./src/kxmlguifactory_p.cpp:305 #24 0x7f081f2e33cb in KXMLGUIFactory::removeClient (this=, client=) at ./src/kxmlguifactory.cpp:458 #25 0x7f081feb73d7 in
[kdevelop] [Bug 408609] New: "use function" declaration reports "Expected symbol" errors.
https://bugs.kde.org/show_bug.cgi?id=408609 Bug ID: 408609 Summary: "use function" declaration reports "Expected symbol" errors. Product: kdevelop Version: 5.3.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- The "use function path\to\namespaced\function_name" reports the following "Expected symbol" errors: useNamespace statement topStatement outerTopStatement start Instead, it should recognize the "use function" statement and allow parsing of the file to continue. KDevelop Platform version 5.3.2 KDE Frameworks 5.59.0 Qt 5.12.3 Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-21-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407717] New: Firefox Bookmarks not updated in search results
https://bugs.kde.org/show_bug.cgi?id=407717 Bug ID: 407717 Summary: Firefox Bookmarks not updated in search results Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mar...@harrisonland.co.uk CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Changes to Firefox bookmarks (such as adding, removing, editing) are not reflected in Plasma's default Application Launcher's search results. Searching KRunner produces up-to-date results, leading me to believe this is not a bug in the runner. STEPS TO REPRODUCE 1. Confirm that Plasma is searching existing bookmarks by typing the title of an existing Firefox bookmark. 2. Once bookmark search is confirmed as active and working, add a new bookmark in Firefox. 3. Type the title of the new bookmark into KRunner and Application Launcher. OBSERVED RESULT KRunner shows the new bookmark; Application Launcher doesn't. EXPECTED RESULT KRunner and Application Launcher both show up-to-date results. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-20-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,4 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 406315] New: Certain applications don't provide core dumps
https://bugs.kde.org/show_bug.cgi?id=406315 Bug ID: 406315 Summary: Certain applications don't provide core dumps Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: mar...@harrisonland.co.uk CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Certain programs, after a crash, provide no further information in KCrash than the message, "segmentation fault". Attempting to install debugging symbols from KCrash does nothing and installing debugging symbols manually doesn't produce more useful output. Since this relies on arbitrary software crashing it's difficult to reproduce correctly. This has happened most frequently to me with Akonadi-based services but has also happened with other programs (I will update this bug with these programs when I find them). SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.15 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370023] plasmashell crash when attempting to use search bar
https://bugs.kde.org/show_bug.cgi?id=370023 --- Comment #4 from Marcus Harrison --- Fine by me, tried reproducing it and can't. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 401056] akonadiserver mamory leak
https://bugs.kde.org/show_bug.cgi?id=401056 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk --- Comment #1 from Marcus Harrison --- I'm seeing the same behaviour in KDE Neon packages. Plasma: 5.14.3 Frameworks: 5.52.0 Qt: 5.11.2 Akonadi server: 5.9.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396341] The "close" tooltip for the window decoration's close button appears at random
https://bugs.kde.org/show_bug.cgi?id=396341 --- Comment #2 from Marcus Harrison --- I don't know what commands you used to get all that information but here's what I could gather: Plasma: 5.13.2 Frameworks: 5.47.0 Qt: 5.11.0 Kernel: 4.13.0-45-generic Video: Intel HD Graphics 520 Kernel driver: i915 Mesa 3D: 18.0.5 Xorg: 1.19.6 Screen: 1920x1080 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396341] New: The "close" tooltip for the window decoration's close button appears at random
https://bugs.kde.org/show_bug.cgi?id=396341 Bug ID: 396341 Summary: The "close" tooltip for the window decoration's close button appears at random Product: kwin Version: 5.13.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- The "Close" tooltip used for the window decoration's close button will appear frequently when not hovering over the close button, and when hovering over Qt application widgets which don't have their own tooltip. I can't reproduce this behaviour under X. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396282] New: Segmentation fault on loading mail in Wayland
https://bugs.kde.org/show_bug.cgi?id=396282 Bug ID: 396282 Summary: Segmentation fault on loading mail in Wayland Product: kmail2 Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- On first opening KMail on Wayland, the window and widgets load, then it crashes before the E-mail view widget loads. KDE's crash wizard won't spawn but I've run KMail from gdb to retrieve this backtrace: #0 0x7fffde284e42 in gl::GLSurfaceGLXQt::Initialize(gl::GLSurfaceFormat) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #1 0x7fffde26f0e8 in gl::init::CreateOffscreenGLSurfaceWithFormat(gfx::Size const&, gl::GLSurfaceFormat) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7fffe02b5a8d in gl::init::CreateOffscreenGLSurface(gfx::Size const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7fffe232a927 in gpu::GpuChannelManager::GetDefaultOffscreenSurface() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fffe232d8f0 in gpu::GLES2CommandBufferStub::Initialize(gpu::CommandBufferStub*, GPUCreateCommandBufferConfig const&, std::unique_ptr >) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fffe2328e16 in gpu::GpuChannel::OnCreateCommandBuffer(GPUCreateCommandBufferConfig const&, int, base::SharedMemoryHandle, gpu::ContextResult*, gpu::Capabilities*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fffe2326adf in bool IPC::MessageT, std::tuple >::Dispatch(IPC::Message const*, gpu::GpuChannel*, gpu::GpuChannel*, void*, void (gpu::GpuChannel::*)(GPUCreateCommandBufferConfig const&, int, base::SharedMemoryHandle, gpu::ContextResult*, gpu::Capabilities*)) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fffe2328022 in gpu::GpuChannel::OnControlMessageReceived(IPC::Message const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fffe2329bbd in gpu::GpuChannel::HandleMessageHelper(IPC::Message const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fffdf7f68d9 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fffdf817da0 in base::MessageLoop::RunTask(base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7fffdf8187fd in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7fffdf818ae7 in base::MessageLoop::DoWork() [clone .part.156] [clone .constprop.178] () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7fffdf814679 in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7fffdf83abcf in base::RunLoop::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7fffdf85c71f in base::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #16 0x7fffdf857d80 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #17 0x7fffea8946ba in start_thread (arg=0x7fff6d7fa700) at pthread_create.c:333 #18 0x74fe841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395388] Software Center Discover Crashed
https://bugs.kde.org/show_bug.cgi?id=395388 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395388] Software Center Discover Crashed
https://bugs.kde.org/show_bug.cgi?id=395388 --- Comment #4 from Marcus Harrison --- Created attachment 113813 --> https://bugs.kde.org/attachment.cgi?id=113813=edit New crash information added by DrKonqi plasma-discover (5.13.2) using Qt 5.11.0 - What I was doing when the application crashed: Opened Discover from having searched for and selected an application in KRunner. -- Backtrace (Reduced): #8 0x7f4d041cfcfc in qobject_cast (object=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:504 #9 QQmlDelegateModelItem::dataForObject (object=object@entry=0x5229de0) at types/qqmldelegatemodel.cpp:1986 #10 0x7f4d041d6de7 in QQmlDelegateModelPrivate::release (this=0x4ee26a0, object=0x5229de0) at types/qqmldelegatemodel.cpp:543 #11 0x7f4d041d6e6d in QQmlDelegateModel::release (this=, item=) at types/qqmldelegatemodel.cpp:567 #12 0x7f4d041caed9 in QQmlInstantiatorPrivate::clear (this=this@entry=0x4edc960) at types/qqmlinstantiator.cpp:83 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395538] (Version 5.8.1) KMail wizards are missing
https://bugs.kde.org/show_bug.cgi?id=395538 Marcus Harrison changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395538] (Version 5.8.1) KMail wizards are missing
https://bugs.kde.org/show_bug.cgi?id=395538 --- Comment #2 from Marcus Harrison --- Oh my goodness I've been trying to solve this for such a long time and never found that. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395538] New: (Version 5.8.1) KMail wizards are missing
https://bugs.kde.org/show_bug.cgi?id=395538 Bug ID: 395538 Summary: (Version 5.8.1) KMail wizards are missing Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- On KDE Neon, with kdepim-addons installed, the anti-spam/anti-virus wizards do not appear in the Tools menu of KMail. Package status: $ apt-cache policy kdepim-addons spamassassin bogofilter kdepim-addons: Installed: 18.04.1-0neon+16.04+xenial+build39 Candidate: 18.04.1-0neon+16.04+xenial+build39 Version table: *** 18.04.1-0neon+16.04+xenial+build39 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 100 /var/lib/dpkg/status 18.04.0-0neon+16.04+xenial+build38 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 17.12.3-0neon+16.04+xenial+build36 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages 17.12.2-0neon+16.04+xenial+build34 500 500 http://archive.neon.kde.org/user xenial/main amd64 Packages spamassassin: Installed: 3.4.1-3 Candidate: 3.4.1-3 Version table: *** 3.4.1-3 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu xenial/main i386 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status bogofilter: Installed: 1.2.4+dfsg1-4build1 Candidate: 1.2.4+dfsg1-4build1 Version table: *** 1.2.4+dfsg1-4build1 500 500 http://es.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387733] kdevelop crashes on deactivating the activity containing it
https://bugs.kde.org/show_bug.cgi?id=387733 --- Comment #3 from Marcus Harrison --- Created attachment 113397 --> https://bugs.kde.org/attachment.cgi?id=113397=edit New crash information added by DrKonqi kdevelop (5.2.3) using Qt 5.11.0 - What I was doing when the application crashed: Same steps, deactivated an activity that KDevelop was running on and received this crash notification. -- Backtrace (Reduced): #6 QWidget::~QWidget (this=0xf5d180, __in_chrg=) at kernel/qwidget.cpp:1611 #7 0x7fba72e23e79 in QWidget::~QWidget (this=0xf5d180, __in_chrg=) at kernel/qwidget.cpp:1727 #8 0x7fba7204dc00 in QObject::event (this=this@entry=0xf5d180, e=e@entry=0x2766db0) at kernel/qobject.cpp:1242 #9 0x7fba72e28b73 in QWidget::event (this=0xf5d180, event=0x2766db0) at kernel/qwidget.cpp:9343 #10 0x7fba72de929c in QApplicationPrivate::notify_helper (this=, receiver=0xf5d180, e=0x2766db0) at kernel/qapplication.cpp:3713 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387733] kdevelop crashes on deactivating the activity containing it
https://bugs.kde.org/show_bug.cgi?id=387733 Marcus Harrison changed: What|Removed |Added CC||mar...@harrisonland.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395305] New: Parser produces errors when keywords are used as function names
https://bugs.kde.org/show_bug.cgi?id=395305 Bug ID: 395305 Summary: Parser produces errors when keywords are used as function names Product: kdevelop Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- In the Laravel PHP framework, some classes[1] use function names that are also type keywords (e.g. public function string(...)). On these files, the parser errors, producing: Expected symbol "identifier" (current token: "string" ...) This causes other features of KDevelop to stop working, including use declarations which use the class, API autocompletion and so on. - [1] https://github.com/laravel/framework/blob/0200dc58ca805e86a366a5779870856b16f8/src/Illuminate/Database/Schema/Blueprint.php#L586 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 395044] New: Networking system settings module crash on applying new settings when switching to different settings view
https://bugs.kde.org/show_bug.cgi?id=395044 Bug ID: 395044 Summary: Networking system settings module crash on applying new settings when switching to different settings view Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: kcmshell5 (5.12.5) Qt Version: 5.10.0 Frameworks Version: 5.46.0 Operating System: Linux 4.13.0-43-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: - Opened the Networking system settings module from the Plasma widget - Made modifications to a network - Clicked to change to a different network - On the pop-up asking to save my changes, I chose to save changes The crash happened before the other network's settings panel displayed and after the dialogue window closed. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa4d0f148c0 (LWP 21891))] Thread 3 (Thread 0x7fa4ac405700 (LWP 21897)): #0 0x7fa4d08f027d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa4c86d76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4c8693e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4c8694330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa4c869449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa4cdd785db in QEventDispatcherGlib::processEvents (this=0x7fa4a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fa4cdd1f65a in QEventLoop::exec (this=this@entry=0x7fa4ac404ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fa4cdb3f554 in QThread::exec (this=this@entry=0xb83010) at thread/qthread.cpp:522 #8 0x7fa4cc648a35 in QQmlThreadPrivate::run (this=0xb83010) at qml/ftw/qqmlthread.cpp:147 #9 0x7fa4cdb446eb in QThreadPrivate::start (arg=0xb83010) at thread/qthread_unix.cpp:376 #10 0x7fa4ca5836ba in start_thread (arg=0x7fa4ac405700) at pthread_create.c:333 #11 0x7fa4d090041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fa4b48aa700 (LWP 21893)): #0 0x7fa4d08f027d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa4c86d76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa4c8693e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa4c8694330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa4c869449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa4cdd785db in QEventDispatcherGlib::processEvents (this=0x7fa4b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fa4cdd1f65a in QEventLoop::exec (this=this@entry=0x7fa4b48a9cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fa4cdb3f554 in QThread::exec (this=) at thread/qthread.cpp:522 #8 0x7fa4ce19b2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fa4cdb446eb in QThreadPrivate::start (arg=0x7fa4ce40fd60) at thread/qthread_unix.cpp:376 #10 0x7fa4ca5836ba in start_thread (arg=0x7fa4b48aa700) at pthread_create.c:333 #11 0x7fa4d090041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa4d0f148c0 (LWP 21891)): [KCrash Handler] #6 0x7fa4cdd4deb2 in QObjectPrivate::isSignalConnected (checkDeclarative=false, signal_index=35, this=) at kernel/qobject_p.h:260 #7 QMetaObject::activate (sender=0x1023c20, signalOffset=, local_signal_index=, argv=argv@entry=0x7fff9cfe4830) at kernel/qobject.cpp:3647 #8 0x7fa4cc59c705 in QQmlVMEMetaObject::activate (this=this@entry=0x106eec0, object=, index=index@entry=52, args=args@entry=0x7fff9cfe4830) at qml/qqmlvmemetaobject.cpp:1243 #9 0x7fa4cc59e9a4 in QQmlVMEMetaObject::metaCall (this=0x106eec0, o=, c=QMetaObject::InvokeMetaMethod, _id=52, a=0x7fff9cfe4830) at qml/qqmlvmemetaobject.cpp:921 #10 0x7fa4cc5fabf9 in QQmlObjectOrGadget::metacall (this=this@entry=0x7fff9cfe4ba0, type=type@entry=QMetaObject::InvokeMetaMethod, index=index@entry=52, argv=) at qml/qqmlpropertycache.cpp:1732 #11 0x7fa4cc5775bd in CallMethod (object=..., index=, returnType=, argCount=, argTypes=, engine=engine@entry=0xa5a320, callArgs=0x7fa4ab3c63b8, callType=QMetaObject::InvokeMetaMethod) at jsruntime/qv4qobjectwrapper.cpp:1158 #12 0x7fa4cc578c8d in CallPrecise (object=..., data=..., engine=engine@entry=0xa5a320, callArgs=callArgs@entry=0x7fa4ab3c63b8,
[telepathy] [Bug 368395] Error: Handler no longer available
https://bugs.kde.org/show_bug.cgi?id=368395 Marcus Harrison <mar...@harrisonland.co.uk> changed: What|Removed |Added CC||mar...@harrisonland.co.uk --- Comment #6 from Marcus Harrison <mar...@harrisonland.co.uk> --- (In reply to Mostafa from comment #5) > (In reply to Mostafa from comment #4) > > I have the same issue with ktp-text-ui 15.12.3 running on KDE Neon and the > > following: > > > > KDE Frameworks 5.37.0 > > Qt 5.9.1 (built against 5.9.1) > > The xcb windowing system > > If I open the contact from KRunner the chat window opens normally. I was about to submit exactly the same bug. KDE Frameworks 5.45.0 Qt 5.10.0 (built against 5.10.0) Chat Application version 15.12.3 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 272618] Vertical scrollbar makes horizontal scrollbar show at minimum width
https://bugs.kde.org/show_bug.cgi?id=272618 --- Comment #3 from Marcus Harrison <mar...@harrisonland.co.uk> --- Not really? The minimum width is now much smaller, so a horizontal scrollbar appears at minimum width regardless of whether there's enough songs to scroll vertically. This could also vary based on the Playlist Layout selected. Using Amarok 2.8.0. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392769] Installation of classic Snaps stops immediately
https://bugs.kde.org/show_bug.cgi?id=392769 --- Comment #3 from Marcus Harrison <mar...@harrisonland.co.uk> --- Sorry, I meant to say that obs-studio installs fine in Discover, and that this only affects classic snaps. I'll test this as soon as I can (I'll try building Discover and, failing that, I'll let you know as soon as a binary version is available for KDE Neon). Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392769] New: Installation of classic Snaps stops immediately
https://bugs.kde.org/show_bug.cgi?id=392769 Bug ID: 392769 Summary: Installation of classic Snaps stops immediately Product: Discover Version: 5.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Snap Backend Assignee: aleix...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Discover is able to install Snaps using current confinement but not Snaps using classic confinement. The snaps tested were OBS Studio (current) and Skype (classic/legacy). On the command line, `snap` installs `obs-studio` immediately, while with the `skype` snap it halts to print a warning message about legacy confinement before forcing the user to type the command again with the `--classic` flag. I believe the correct behaviour for Discover should be somewhere between showing a dialogue box that warns the user of the lack of sandboxing with classic snaps, and not showing classic snaps at all. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392707] New: Enabling Identities / [Identity settings] / Advanced / Attach my vCard to message causes errors in PGP signatures
https://bugs.kde.org/show_bug.cgi?id=392707 Bug ID: 392707 Summary: Enabling Identities / [Identity settings] / Advanced / Attach my vCard to message causes errors in PGP signatures Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- When an identity is configured to attach a vCard on sending automatically, the E-mails sent result in invalid signature errors both in KMail and in other E-mail clients (I tested K-9 Mail on Android). Steps to reproduce: 1. Ensure you already have a valid GPG key set up in Kleopatra for signing E-mails with your chosen identity. 2. Set up a vCard for your sending identity. 3. Tick the box to automatically attach that vCard to sent E-mails. 4. Compose a new message to an E-mail address you control. 5. Confirm that the E-mail will be signed and send. Expected result: The message is signed, the signature passes validation and the vCard is attached. Actual result: The message is signed and the cVard is attached but the signature fails validity checks. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390648] New: Snap packages always appear as installed
https://bugs.kde.org/show_bug.cgi?id=390648 Bug ID: 390648 Summary: Snap packages always appear as installed Product: Discover Version: 5.12.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Snap Backend Assignee: aleix...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- On KDE Neon with the Snap backend installed, packages available as Snaps always appear as installed, even when they are not installed. They show the options to Remove the package from the listing view, or from the description view, the option to Remove or Open. The Open button does nothing. The Remove button prompts for authentication, then shows the error, "snap [package-name] is not installed". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390115] On wayland, keyboard input that causes Firefox focus passes key presses to Firefox
https://bugs.kde.org/show_bug.cgi?id=390115 --- Comment #4 from Marcus Harrison <mar...@harrisonland.co.uk> --- Here's the output, hopefully it helps. Cheers. KWin-Unterstützungsinformationen: Benutzen Sie die folgenden Informationen, wenn Sie nach Unterstützung fragen, z. B. auf http://forum.kde.org. Sie enthalten Informationen über die momentan laufende Instanz, welche Optionen verwendet werden, welcher OpenGL-Treiber verwendet wird und welche Effekte laufen. Bitte geben Sie die unten stehenden Informationen bei einem Pastebin-Dienst wie http://paste.kde.org ein, anstatt sie direkt in die Hilfediskussionen zu schreiben. == Version === KWin version: 5.12.0 Qt Version: 5.9.3 Qt compile version: 5.9.3 XCB compile version: 1.11.1 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11804000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 5, 3, 4 decorationButtonsRight: borderSize: 0 gridUnit: 12 font: Oxygen-Sans,11,-1,5,50,0,0,0,0,0,Sans-Book smallSpacing: 3 largeSpacing: 12 Platform == Name: DRM Active: true Atomic Mode Setting: true Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 glSmoothScale: 0 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 0 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: MEI eDP-1-VVX13F009G10 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 60.011 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2) OpenGL version string: 4.5 (Core Profile) Mesa 17.2.4 OpenGL platform interface: EGL OpenGL shading language version string: 4.50 Driver: Intel GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 17.2.4 Linux kernel version: 4.13 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom kwin4_effect_logout kwin4_effect_windowaperture kwin4_effect_dialogparent kwin4_effect_translucency kwin4_effect_login kwin4_effect_morphingpopups kwin4_effect_frozenapp kwin4_effect_fade slidingpopups slideback slide screenshot minimizeanimation desktopgrid colorpicker presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZ
[kwin] [Bug 390115] On wayland, keyboard input that causes Firefox focus passes key presses to Firefox
https://bugs.kde.org/show_bug.cgi?id=390115 --- Comment #2 from Marcus Harrison <mar...@harrisonland.co.uk> --- Sorry, how would I go about finding the version number? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390115] New: On wayland, keyboard input that causes Firefox focus passes key presses to Firefox
https://bugs.kde.org/show_bug.cgi?id=390115 Bug ID: 390115 Summary: On wayland, keyboard input that causes Firefox focus passes key presses to Firefox Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Sorry for the poorly-worded summary. This only appears when running plasma-wayland. If a keyboard press causes a previously-focused window to become unfocused, and makes Firefox the newly-focused window, the key-press is passed to Firefox as a duplicate. To reproduce: Example 1 1. Make Firefox the selected window. Focus a textarea HTML widget. 2. Open plasma's default Application Launcher. 3. Hit "Enter" to open any selected item. Expected behaviour: No key press is passed to Firefox and the selected item is opened. Actual behaviour: The "Enter" keypress is passed to Firefox, creating a newline in the text area. If Firefox has a HTML anchor element selected, it is activated, potentially switching pages. Forms can be unintentionally submitted, etc. Example 2 1. Make Firefox the focused window. 2. Open a new application window, e.g. Kwrite or Konsole. 3. Use Alt+F4 to close the new window and make Firefox the focused window again. Expected behaviour: No key press is passed to Firefox and the previously-opened window is closed. Actual behaviour: The window is closed and the Firefox application menu (file, edit etc.) is focused. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390115] On wayland, keyboard input that causes Firefox focus passes key presses to Firefox
https://bugs.kde.org/show_bug.cgi?id=390115 Marcus Harrison <mar...@harrisonland.co.uk> changed: What|Removed |Added Platform|Other |Neon Packages Version|unspecified |5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389001] plasma-discover crashes after installing flatpak backend
https://bugs.kde.org/show_bug.cgi?id=389001 Marcus Harrison <mar...@harrisonland.co.uk> changed: What|Removed |Added CC||mar...@harrisonland.co.uk --- Comment #3 from Marcus Harrison <mar...@harrisonland.co.uk> --- Hello, I just ran into the same issue with the same solution. Is the plasma-discover upgrade path broken somehow? I've been upgrading my packages pretty blindly when they become available. Cheers. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdewebkit] [Bug 389053] New: Graphical glitches with Webkit renderers on Wayland
https://bugs.kde.org/show_bug.cgi?id=389053 Bug ID: 389053 Summary: Graphical glitches with Webkit renderers on Wayland Product: frameworks-kdewebkit Version: 5.42.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- This applies to the E-mail view in Kontact, the new System Settings layout and the Discover view. Sorry if this bug is mis-filed. When using these applications on Wayland using the KDE Slimbook, they will often distort the display outside of the application. This includes drawing the application view outside of the application's window or drawing it on top of applications that overlap them in the window manager. This does not affect Xorg sessions. When those applications listed above are closed, the distortion ends. I am using mesa on intel graphics and this happens every time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387451] KWin crash on using default window-switcher
https://bugs.kde.org/show_bug.cgi?id=387451 Marcus Harrison <mar...@harrisonland.co.uk> changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #2 from Marcus Harrison <mar...@harrisonland.co.uk> --- Thanks. Where would I go about that? Simply searching results in hits for submitting Catalyst/DirectX/Windows bugs... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387451] New: KWin crash on using default window-switcher
https://bugs.kde.org/show_bug.cgi?id=387451 Bug ID: 387451 Summary: KWin crash on using default window-switcher Product: kwin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: --- Application: kwin_x11 (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.0-17-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: Alt-tabbing through windows when compositing effects are enabled. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f37f0a02980 (LWP 10676))] Thread 15 (Thread 0x7f3705066700 (LWP 10717)): #0 0x7f37e95b0072 in futex_wait_cancelable (private=, expected=0, futex_word=0x558c4d8c13dc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f37e95b0072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x558c4d8c1388, cond=0x558c4d8c13b0) at pthread_cond_wait.c:502 #2 0x7f37e95b0072 in __pthread_cond_wait (cond=0x558c4d8c13b0, mutex=0x558c4d8c1388) at pthread_cond_wait.c:655 #3 0x7f37cca75b8b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f37cca75aa7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f37e95a97fc in start_thread (arg=0x7f3705066700) at pthread_create.c:465 #6 0x7f37f038bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f3707fff700 (LWP 10716)): #0 0x7f37f037f9fb in __GI_ppoll (fds=0x7f378800c098, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f37ed98e151 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f37ed98f86e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f37ed937e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f37ed7573ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f37ed75c29d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f37e95a97fc in start_thread (arg=0x7f3707fff700) at pthread_create.c:465 #7 0x7f37f038bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f37961a2700 (LWP 10702)): #0 0x7f37e95b0072 in futex_wait_cancelable (private=, expected=0, futex_word=0x558c4db3fab8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f37e95b0072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x558c4db3fa68, cond=0x558c4db3fa90) at pthread_cond_wait.c:502 #2 0x7f37e95b0072 in __pthread_cond_wait (cond=0x558c4db3fa90, mutex=0x558c4db3fa68) at pthread_cond_wait.c:655 #3 0x7f37cca75b8b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f37cca75aa7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f37e95a97fc in start_thread (arg=0x7f37961a2700) at pthread_create.c:465 #6 0x7f37f038bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f37959a1700 (LWP 10691)): #0 0x7f37e95b0072 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f37ecbd1fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f37e95b0072 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f37ecbd1f68, cond=0x7f37ecbd1f90) at pthread_cond_wait.c:502 #2 0x7f37e95b0072 in __pthread_cond_wait (cond=0x7f37ecbd1f90, mutex=0x7f37ecbd1f68) at pthread_cond_wait.c:655 #3 0x7f37ec8ddbd4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f37ec8ddc19 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f37e95a97fc in start_thread (arg=0x7f37959a1700) at pthread_create.c:465 #6 0x7f37f038bb0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f379f5ef700 (LWP 10687)): #0 0x7f37f037f9fb in __GI_ppoll (fds=0x7f3798000d18, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f37ed98e151 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f37ed98f86e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f37ed937e3a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f37ed7573ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f37e80b0f45 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f37ed75c29d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f37e95a97fc in
[amarok] [Bug 387309] New: Amarok fails to copy tracks to a removable drive collection
https://bugs.kde.org/show_bug.cgi?id=387309 Bug ID: 387309 Summary: Amarok fails to copy tracks to a removable drive collection Product: amarok Version: 2.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Collections/USB mass storage and MSC Assignee: amarok-bugs-d...@kde.org Reporter: mar...@harrisonland.co.uk CC: bart.cerne...@kde.org Target Milestone: 2.9 On KDE Neon, an unlabelled FAT32 USB stick is mounted in a directory formatted as /media/[user]/neon user [mmdd]-[hh]:[mm]/ where the date is shown as an 8 digit number and the time is shown as a colon-separated number. It is picked up by Amarok. Attempting to use the "Copy/Move to Collection" functions to copy music from my local collection to the removable drive collection brings up the dialogue asking if I would like to copy unmodified, or transcode. Selecting either option closes the dialogue without copying the tracks and no progress is shown in the progress meter at the bottom of the collections window. Changing the label on the fat32 partition to an alphanumerical value caused it to be mounted in /media/[username]/[alphanumerical value]/, after which using the "Copy/Move to Collection" functions worked correctly. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382453] New: Errors while processing libkf5followupreminder and libkf5libkleo5
https://bugs.kde.org/show_bug.cgi?id=382453 Bug ID: 382453 Summary: Errors while processing libkf5followupreminder and libkf5libkleo5 Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: mar...@harrisonland.co.uk CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- My system is in a state where attempting to run any apt operation results in the following output: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run ‘apt-get -f install’ to correct these. The following packages have unmet dependencies. libkf5followupreminder5 : Depends: kf5-kdepim-apps-libs-data (= 4:17.04.2-0neon+16.04+xenial+build5) but it is not installed libkf5libkleo5 : Depends: libkf5libkleo-data (= 4:17.04.2-0neon+16.04+xenial+build29) but it is not installed Depends: libqgpgme7 (>= 1.8.0) but it is not installed E: Unmet dependencies. Try using -f. Running apt install -f (with a clean cache) results in the following output: $ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies...Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following additional packages will be installed: kf5-kdepim-apps-libs-data libkf5followupreminder5 libkf5libkleo-data libkf5libkleo5 libqgpgme7 The following NEW packages will be installed kf5-kdepim-apps-libs-data libkf5libkleo-data libqgpgme7 The following packages will be upgraded: libkf5followupreminder5 libkf5libkleo5 2 to upgrade, 3 to newly install, 0 to remove and 0 not to upgrade. 89 not fully installed or removed. Need to get 668 kB of archives. After this operation, 2,239 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.neon.kde.org/user xenial/main amd64 libqgpgme7 amd64 1.8.0-neon0+16.04+xenial+build3 [198 kB] Get:2 http://archive.neon.kde.org/user xenial/main amd64 libkf5followupreminder5 amd64 4:17.04.3-0neon+16.04+xenial+build6 [12.4 kB] Get:3 http://archive.neon.kde.org/user xenial/main amd64 kf5-kdepim-apps-libs-data all 4:17.04.3-0neon+16.04+xenial+build6 [21.5 kB] Get:4 http://archive.neon.kde.org/user xenial/main amd64 libkf5libkleo5 amd64 4:17.04.3-0neon+16.04+xenial+build30 [289 kB] Get:5 http://archive.neon.kde.org/user xenial/main amd64 libkf5libkleo-data all 4:17.04.3-0neon+16.04+xenial+build30 [147 kB] Fetched 668 kB in 5s (121 kB/s) Selecting previously unselected package libqgpgme7:amd64. (Reading database ... 307646 files and directories currently installed.) Preparing to unpack .../libqgpgme7_1.8.0-neon0+16.04+xenial+build3_amd64.deb ... Unpacking libqgpgme7:amd64 (1.8.0-neon0+16.04+xenial+build3) ... Selecting previously unselected package libkf5followupreminder5:amd64. Preparing to unpack .../libkf5followupreminder5_4%3a17.04.3-0neon+16.04+xenial+build6_amd64.deb ... dpkg: error processing archive /var/cache/apt/archives/libkf5followupreminder5_4%3a17.04.3-0neon+16.04+xenial+build6_amd64.deb (--unpack): triggers ci file contains unknown directive '
[neon] [Bug 379052] New: The calligraauthor package has unsatisfied dependencies
https://bugs.kde.org/show_bug.cgi?id=379052 Bug ID: 379052 Summary: The calligraauthor package has unsatisfied dependencies Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: mar...@harrisonland.co.uk CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Output from apt install calligraauthor: Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) calligraauthor [ amd64 ] < none -> 1:2.9.7-0ubuntu12 > ( universe/kde ) Broken calligraauthor:amd64 Depends on calligra-libs [ amd64 ] < 1:3.0.0.1-0neon+16.04+build13 > ( libs ) (= 1:2.9.7-0ubuntu12) Considering calligra-libs:amd64 18 as a solution to calligraauthor:amd64 Broken calligraauthor:amd64 Depends on calligrawords-common [ amd64 ] < none -> 1:2.9.7-0ubuntu12 > ( universe/kde ) (= 1:2.9.7-0ubuntu12) Considering calligrawords-common:amd64 0 as a solution to calligraauthor:amd64 Re-Instated calligrawords-common:amd64 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. calligraauthor : Depends: calligra-libs (= 1:2.9.7-0ubuntu12) but 1:3.0.0.1-0neon+16.04+build13 is to be installed E: Unable to correct problems, you have held broken packages. --- Based on KDE Neon 5.9 on the KDE Slimbook. I'll be happy to provide additional information of my system if necessary. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 345959] When an individual folder is set to prefer HTML to Plaintext, some E-mails with both HTML and plaintext parts will display the plaintext part
https://bugs.kde.org/show_bug.cgi?id=345959 --- Comment #2 from Marcus Harrison <mar...@harrisonland.co.uk> --- Using KMail 5.3.3 from the Fedora 25 repositories, I get the same issue. Sorry guys. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373501] Animated icons in system tray consume massive CPU
https://bugs.kde.org/show_bug.cgi?id=373501 --- Comment #3 from Marcus Harrison <mar...@harrisonland.co.uk> --- Sorry for the noise, it wasn't until I searched more thoroughly that I found the duplicates. After an update today, it appears to be resolved. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373501] New: Animated icons in system tray consume massive CPU
https://bugs.kde.org/show_bug.cgi?id=373501 Bug ID: 373501 Summary: Animated icons in system tray consume massive CPU Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mar...@harrisonland.co.uk Target Milestone: 1.0 I have noticed that, under normal usage, my laptop running KDE on Fedora 24 is fast and responsive. However, when system tray notifications display animations, the CPU usage of Xorg and plasmashell rise, with Xorg reaching 20% and plasmashell reaching 30%. My laptop has 4 CPU cores and this usage appears to correspond with two cores being completely occupied, bringing my laptop's performance down considerably. The effect ends immediately after the animated system tray icons stop animating, or are removed. The two that I have found cause this the most reliably are the Network Manager plasma widget and the Skype notification icon, which leads me to believe it is consistent across plasma widgets and icons registered with libnotify or similar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370023] New: plasmashell crash when attempting to use search bar
https://bugs.kde.org/show_bug.cgi?id=370023 Bug ID: 370023 Summary: plasmashell crash when attempting to use search bar Product: plasmashell Version: 5.7.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mar...@harrisonland.co.uk CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.7.5) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.5-200.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I had opened the default application launcher menu and typed a search term into the search bar. After the list of favourite options had disappeared, and before the list of results appeared, plasmashell crashed. While the symptoms are similar to another crash report I filed in the Red Hat bugzilla at https://bugzilla.redhat.com/show_bug.cgi?id=1273609#c21, I now have Baloo enabled and plasmashell crashes are considerably less frequent. Finally, I am using a more up-to-date version of Fedora and plasmashell than I was when I reported that bug. Having checked this backtrace, it doesn't seem that the two bugs are related, but I am including that report here for completeness. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f87f31a4940 (LWP 1564))] Thread 17 (Thread 0x7f871affd700 (LWP 2549)): #0 0x7f8800f21bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f88027d801a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f87418cd8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f87418d1a68 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f87418cca3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f87418cf909 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f88027d799a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f8800f1c5ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f8801bcaf6d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f871b7fe700 (LWP 2548)): #0 0x7f8800f21bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f88027d801a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f87418cd8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f87418d1a68 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f87418cca3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f87418cf909 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f88027d799a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f8800f1c5ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f8801bcaf6d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f871bfff700 (LWP 2547)): #0 0x7f8800f21bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f88027d801a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f87418cd8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f87418d1a68 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f87418cca3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f87418cf909 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f88027d799a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f8800f1c5ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f8801bcaf6d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f8720d89700 (LWP 2546)): #0 0x7f8800f21bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f88027d801a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f87418cd8c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f87418d1a68 in
[kmail2] [Bug 304525] Auto-suggesting contacts from address book using nicknames fails for first search
https://bugs.kde.org/show_bug.cgi?id=304525 --- Comment #2 from Marcus Harrison <mar...@harrisonland.co.uk> --- I have just tested this in KMail 4.14.10 from Fedora RPM packages. Auto-completion still appears to only search the "Name" and "E-mail" fields recorded in KAddressBook, and not the "Nickname" field. I'll investigate building or otherwise installing a Frameworks-based version of KMail. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363395] Plasma shell config dialogue drop-down menus do not honour QWidget colour scheme
https://bugs.kde.org/show_bug.cgi?id=363395 --- Comment #1 from Marcus Harrison <mar...@harrisonland.co.uk> --- Created attachment 99130 --> https://bugs.kde.org/attachment.cgi?id=99130=edit Example screenshot of the bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363395] New: Plasma shell config dialogue drop-down menus do not honour QWidget colour scheme
https://bugs.kde.org/show_bug.cgi?id=363395 Bug ID: 363395 Summary: Plasma shell config dialogue drop-down menus do not honour QWidget colour scheme Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mar...@harrisonland.co.uk CC: bhus...@gmail.com, plasma-b...@kde.org When opening a configuration dialogue for a plasmashell widget, most of the configuration dialogue honours the currently selected QWidget colour scheme. However, drop-down menus in these dialogues have a white background and blue hover-over background, while keeping the colour scheme text colour. This can make certain dark colour schemes difficult to use with these menus. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
