[plasmashell] [Bug 476775] New: Plasma crashed when trying to edit size of a widget
https://bugs.kde.org/show_bug.cgi?id=476775 Bug ID: 476775 Summary: Plasma crashed when trying to edit size of a widget Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mikrod.i...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-13-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Plasma crashed when I was trying to edit size of a digital clock widget. This is a brand new install of Debian OS with KDE. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 24549 (plasmashell) UID: 1000 (mikrod) GID: 1000 (mikrod) Signal: 11 (SEGV) Timestamp: Fri 2023-11-10 00:05:22 -03 (1min 25s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (mikrod) Boot ID: 21393acba2834517b61c6fc438eed493 Machine ID: 3540669b8aa14a288273cf0be2df520c Hostname: debian Storage: /var/lib/systemd/coredump/core.plasmashell.1000.21393acba2834517b61c6fc438eed493.24549.169958552200.zst (present) Size on Disk: 27.7M Message: Process 24549 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.17-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.17-1~deb12u1.amd64 Stack trace of thread 24549: #0 0x7f6cdbaa9d3c n/a (libc.so.6 + 0x8ad3c) #1 0x7f6cdba5af32 raise (libc.so.6 + 0x3bf32) #2 0x7f6cde17eb46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f6cdba5afd0 n/a (libc.so.6 + 0x3bfd0) #4 0x7f6cdbaa9d3c n/a (libc.so.6 + 0x8ad3c) #5 0x7f6cdba5af32 raise (libc.so.6 + 0x3bf32) #6 0x7f6cdba5afd0 n/a (libc.so.6 + 0x3bfd0) #7 0x7f6cdbaa4da4 n/a (libc.so.6 + 0x85da4) #8 0x7f6cdbaa7468 pthread_cond_wait (libc.so.6 + 0x88468) #9 0x7f6cdbcd1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b) #10 0x7f6cddc0bd58 n/a (libQt5Quick.so.5 + 0x20bd58) #11 0x7f6cddc76e20 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5 + 0x276e20) #12 0x7f6cdcd62fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #13 0x7f6cdbeb16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #14 0x7f6cdc32c3e8 _ZN15QPlatformWindow20deliverUpdateRequestEv (libQt5Gui.so.5 + 0x12c3e8) #15 0x7f6cdbedd6f0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd6f0) #16 0x7f6cdcd62fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #17 0x7f6cdbeb16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #18 0x7f6cdbeb4681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b4681) #19 0x7f6cdbf0a153 n/a (libQt5Core.so.5 + 0x30a153) #20 0x7f6cda98a7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #21 0x7f6cda98aa38 n/a (libglib-2.0.so.0 + 0x54a38) #22 0x7f6cda98aacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #23 0x7f6cdbf09836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #24 0x7f6cdbeb017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #25 0x7f6cdbeb82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #26 0x55f706724dc3 n/a (plasmashell + 0x26dc3) #27 0x7f6cdba461ca n/a (libc.so.6 + 0x271ca) #28 0x7f6cdba46285 __libc_start_main (libc.so.6 + 0x27285) #29 0x55f706724ee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 24553:
[blinken] [Bug 410270] sound problems
https://bugs.kde.org/show_bug.cgi?id=410270 --- Comment #4 from Mik --- (In reply to Albert Astals Cid from comment #3) > systemsettings -> multimedia -> audio & video -> backend Strange ... On both systems I can't found any settings for "Multimedia -> audio & video -> backend". I have "systemsettings" but without "multimedia". So I ran through nearly all systemsettings on both systems but there is no hint for the audio & video backend. Is there a system file where I can look into ? -- You are receiving this mail because: You are watching all bug changes.
[blinken] [Bug 410270] sound problems
https://bugs.kde.org/show_bug.cgi?id=410270 --- Comment #2 from Mik --- (In reply to Albert Astals Cid from comment #1) > Are you using the same phonon backend on both? Can you tell me how to determine which backend is used ? -- You are receiving this mail because: You are watching all bug changes.
[blinken] [Bug 410270] New: sound problems
https://bugs.kde.org/show_bug.cgi?id=410270 Bug ID: 410270 Summary: sound problems Product: blinken Version: 0.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: dieter1...@gmx.net Target Milestone: --- Running system: Linux mint 19 Cinnamon 64 Bit, Desktop PC Intel I5, Cinnamon version 3.8.9 RAM: 7.8 GB uname -a: 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Blinken Version 0.4 "About Blinken" results KDE Frameworks 5.44.0 Qt 5.9.5 (compiled 5.9.5) xcb window system When I start the game I can hear the first two or three sounds for the corresponding color field. After that the program produces only sound clicks or chopped sound. STEPS TO REPRODUCE On my system this is always reproducible after starting the game. ADDITIONAL INFORMATION On my ubuntu 16.04 (64 bit, Intel I7, 16 GB RAM) system the game runs properly. On this system "Blinken" gives the following information: version 0.4 KDE Frameworks 5.18.0 Qt 5.5.1 (compiled 5.5.1) xcb window system -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391115] Very slow search, full text search (FTS) proposition for huge speedup.
https://bugs.kde.org/show_bug.cgi?id=391115 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392961] Layout shortcut makes all other shortcuts starting with that combination unavailable
https://bugs.kde.org/show_bug.cgi?id=392961 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392961] Layout shortcut makes all other shortcuts starting with that combination unavailable
https://bugs.kde.org/show_bug.cgi?id=392961 Michal Kec (MiK) changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Michal Kec (MiK) --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378910] System Tray forgets Dropbox hidden state after logout+login
https://bugs.kde.org/show_bug.cgi?id=378910 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 386716] akonadi apparmor error: denied access to /etc/mysql/mariadb.cnf
https://bugs.kde.org/show_bug.cgi?id=386716 --- Comment #3 from Michal Kec (MiK) --- There are two issues simultaneously. 1. Apparmor profile doesn't know MariaDB config files Workaround: Open the file /etc/apparmor.d/usr.sbin.mysqld-akonadi and add following lines "somewhere in the middle": /etc/mysql/mariadb.conf.d/ r, /etc/mysql/mariadb.conf.d/* r, /etc/mysql/mariadb.cnf r, 2. MariaDB vs. MySQL binary files incompatibility. Since you already can have database files generated by MySQL, MariaDB can't deal with them and dies. Workaround: Delete everything in ~/.local/share/akonadi/db_data and restart akonadi to let it create brand new database. It's just a metadata cache after all. Akonadi maintainers should definitely take care of the first issue. I'm not sure how to fix the second one. The DB engine should detect the incompatibility and either delete broken database, or try to migrate. Further reading: https://mariadb.com/kb/en/library/mariadb-vs-mysql-compatibility/ -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 386716] akonadi apparmor error: denied access to /etc/mysql/mariadb.cnf
https://bugs.kde.org/show_bug.cgi?id=386716 Michal Kec (MiK) changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED CC||k...@kecnet.cz --- Comment #2 from Michal Kec (MiK) --- I can confirm this behavior on recent KDE Neon (bionic) User Edition. Since I had to switch from MySQL to MariaDB due to digiKam bug #379959, I am unable to run Kaddressbook. Steps to reproduce: 1. Fresh installed KDE Neon with kaddressbook & kdepim-addons packages. 2. Start kaddressbook -> should work ok, you can see process mysqld invoked by Akonadi. 3. Replace mysql-core-server-5.7 by mariadb-server-10.1 4. Restart 5. Start kaddressbook -> Message "Akonadi not running" appears. Also no mysqld process invoked by Akonadi. 6. Error in syslog: audit: type=1400 audit(1541959236.039:31): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" name="/etc/mysql/mariadb.cnf" pid=8844 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 I believe the usr.sbin.mysqld-akonadi profile of Apparmor needs to be updated in order to take MariaDB files into consideration. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382361] Continuous net usage, server CPU and IO usage while doing nothing but keeping a collection opened [network share & mysql db]
https://bugs.kde.org/show_bug.cgi?id=382361 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398921] digikam 5.9.0 slow to start on Mac but rapid on Ubuntu with same database
https://bugs.kde.org/show_bug.cgi?id=398921 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399113] Feature request: add reverse geocoding (country, state/province, city) to database
https://bugs.kde.org/show_bug.cgi?id=399113 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378838] Initializing MySQL/MariaDB database or migrating from SQLite cancels with DB errors
https://bugs.kde.org/show_bug.cgi?id=378838 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389179] Error creating mysql db for internel server (mysql_install_db)
https://bugs.kde.org/show_bug.cgi?id=389179 Michal Kec (MiK) changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379959] Could not start database initializer
https://bugs.kde.org/show_bug.cgi?id=379959 Michal Kec (MiK) changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||k...@kecnet.cz --- Comment #9 from Michal Kec (MiK) --- I can confirm this bug affected digiKam 5.9.0 and 6.0.0 beta 2, both on KDE Neon (bionic) and MySQL server 5.7.24. Besides the issue mentioned in #c0 (mysql_install_db is deprecated), there's another issue caused by wrong parameters order. In according to MySQL docs [1] the argument --defaults-file must be the first. More info about the initializing in MySQL 5.7 on [2] The initialization command that worked for me was `mysqld --defaults-file=/home/mik/.local/share/digikam/mysql.conf --initialize --datadir=/home/mik/.local/share/digikam/db_data --server-id=1` [1] https://dev.mysql.com/doc/refman/5.7/en/option-file-options.html [2] https://mysqlserverteam.com/initialize-your-mysql-5-7-instances-with-ease/ -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 376672] KAddressbook crashes while opening contact details
https://bugs.kde.org/show_bug.cgi?id=376672 Michal Kec (MiK) <k...@kecnet.cz> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Michal Kec (MiK) <k...@kecnet.cz> --- I can see this fixed in kaddressbook 5.5.0. Thank you for your attention. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 379459] Krusader no longer minimizes to system tray.
https://bugs.kde.org/show_bug.cgi?id=379459
--- Comment #5 from Michal Kec (MiK) <k...@kecnet.cz> ---
Thank you Alex for actively taking this issue!
> If I didn't miscount, there are 4 people now who want the old behaviour back
> ("Minimize" minimizes, "close" closes to tray").
Just for the record I can describe the old behavior as I can see that with
Krusader 2.4.0 on KDE 4 (Kubuntu 14.04 LTS):
- When "Minimize to tray" checked, both minimizing and closing the window
(using both "X" or Alt-F4) just minimize the app to the systray (thus no icon
in the taskbar).
- Actually I can see the icon in the systray all the time, even if the window
is not minimized.
- The app is terminated only by selecting "Quit" in the File menu.
--
You are receiving this mail because:
You are watching all bug changes.
[krusader] [Bug 379459] Krusader no longer minimizes to system tray.
https://bugs.kde.org/show_bug.cgi?id=379459 Michal Kec (MiK) <k...@kecnet.cz> changed: What|Removed |Added CC||k...@kecnet.cz --- Comment #2 from Michal Kec (MiK) <k...@kecnet.cz> --- Thank you Alex for mentioning the relevant bug. I'm very excited with reintroduced feature "minimize to tray" in Krusader 2.6.0! However I do agree with the reporter here and with the comments in bug 350920 that the previous behavior (as in Krusader 2.4.0 on KDE 4) is more convenient. I also believe it is common behavior among apps with "minimize to tray" feature (i.e. Amarok, Clementine, various instant messaging apps). Well, maybe the correct label should be "Minimize to tray instead of quit". :-) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 350920] please revert removal of "minimize to tray"
https://bugs.kde.org/show_bug.cgi?id=350920 Michal Kec (MiK) <k...@kecnet.cz> changed: What|Removed |Added CC||k...@kecnet.cz -- You are receiving this mail because: You are watching all bug changes.
