[Breeze] [Bug 368019] Resolution selection box not wide enough with scrollbars
https://bugs.kde.org/show_bug.cgi?id=368019 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org --- Comment #4 from Antonio Larrosa --- This patch fixes this issue: https://phabricator.kde.org/D3192 (Although I'm not sure that's the correct way to fix it, so a comment from someone with experience on breeze should comment on it) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 371887] .ps-files were not displayed since last update of ghostscript
https://bugs.kde.org/show_bug.cgi?id=371887 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org --- Comment #5 from Antonio Larrosa --- Albert asked me to have a look at this since it seems to be an openSUSE issue. I had a look and it seems to be a problem with a security patch introduced in that update. I created an issue in openSUSE's bugzilla at https://bugzilla.opensuse.org/show_bug.cgi?id=1007816 . Franz, if this is an urgent problem for you, I mentioned a temporary workaround in that bugzilla entry. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 371724] Screenshots are not shown when element has no width/height attribute
https://bugs.kde.org/show_bug.cgi?id=371724 Antonio Larrosa changed: What|Removed |Added Latest Commit||http://commits.kde.org/disc ||over/3297fe6026edebb8db72bb ||179289bee844c26ae3 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.8.4 --- Comment #5 from Antonio Larrosa --- Git commit 3297fe6026edebb8db72bb179289bee844c26ae3 by Antonio Larrosa. Committed on 02/11/2016 at 11:40. Pushed by antlarr into branch 'Plasma/5.8'. Make screenshots visible when there's only one screenshot too Summary: Applications with only one screenshot also deserve to have it visible. FIXED-IN: 5.8.4 Test Plan: Open any application that only has one screenshot (e.g. poedit). No screenshot is shown until this patch is applied. Reviewers: davidedmundson, apol Reviewed By: davidedmundson, apol Differential Revision: https://phabricator.kde.org/D3223 M +1-1discover/qml/ApplicationScreenshots.qml http://commits.kde.org/discover/3297fe6026edebb8db72bb179289bee844c26ae3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368019] Resolution selection box not wide enough with scrollbars
https://bugs.kde.org/show_bug.cgi?id=368019 Antonio Larrosa changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Antonio Larrosa --- Fixed in breeze 5.8.3 (by https://quickgit.kde.org/?p=breeze.git&a=commit&h=3c7fd5a87e2e176f480b9bb67b594f59a08c9551 ) -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input
https://bugs.kde.org/show_bug.cgi?id=435338 Antonio Larrosa changed: What|Removed |Added Version|21.04.1 |22.04.1 CC||larr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 435555] Crashing in QAccessible after playing the ‘Counties by Flag’ activity
https://bugs.kde.org/show_bug.cgi?id=43 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org --- Comment #10 from Antonio Larrosa --- I've tried to reproduce this on Tumbleweed 20210401 and also on another system with 20210408 (the latest version at this time). In both cases following the "steps to reproduce" worked fine and kgeography didn't crash. I also tried using kgeography with LANGUAGE=nn just in case it's related to translations but couldn't reproduce the problem either. I also tried running kgeography on wayland just in case there was a mistake in the bug report which mentions it happened in X11. Karl, can you give us the full output of running `rpm -qi libQt5Gui5 kgeography` to check if I'm using exactly the same versions that fail for you? -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 435555] Crashing in QAccessible after playing the ‘Counties by Flag’ activity
https://bugs.kde.org/show_bug.cgi?id=43 --- Comment #13 from Antonio Larrosa --- I tested with exactly the same packages here. Can you create a new user in your system, log in with it and try to run kgeography within that user's session? Just to check if using the default desktop settings as a new user makes any difference. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 416965] k3b - Application de gravure de CB/DVD pour GNOME / k3b - CB / DVD burning application for GNOME
https://bugs.kde.org/show_bug.cgi?id=416965 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Antonio Larrosa --- I submitted a fix for this in: https://l10n.opensuse.org/translate/packages-i18n/k-master/fr/?q=Application+de+gravure&search=ftx&source=1&target=1&type=all&offset=1 So it should be fixed in the next releases of Leap / Tumbleweed. I also checked that the translator who did this also submitted many other correct translations so it seems to be an honest mistake. In any case, thanks for reporting it, Olivier! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 395704] Media Codec required popup which can't be closed when can't play the unplugged notification sound.
https://bugs.kde.org/show_bug.cgi?id=395704 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org --- Comment #2 from Antonio Larrosa --- I was just hit by this problem and noticed this bug entry when I was going to report it. I got flooded with popup entries that appear continuously after restoring the system from hybernation. When I started debugging powerdevil the popup notifications stopped appearing, so it was clear this was the application showing them. This is the backtrace: (gdb) info threa Id Target Id Frame 1Thread 0x7f3dc5e96200 (LWP 2393) "org_kde_powerde" 0x7f3dc30122c9 in poll () from /lib64/libc.so.6 2Thread 0x7f3db1dc1700 (LWP 2395) "QXcbEventReader" 0x7f3dc30122c9 in poll () from /lib64/libc.so.6 3Thread 0x7f3db093d700 (LWP 2404) "QDBusConnection" 0x7f3dc30122c9 in poll () from /lib64/libc.so.6 4Thread 0x7f3daa6d3700 (LWP 2405) "gmain" 0x7f3dc30122c9 in poll () from /lib64/libc.so.6 5Thread 0x7f3da9ed2700 (LWP 2406) "gdbus" 0x7f3dc30122c9 in poll () from /lib64/libc.so.6 6Thread 0x7f3d7ef11700 (LWP 17192) "typefind:sink" 0x7f3dc3017739 in syscall () from /lib64/libc.so.6 7Thread 0x7f3d7fd72700 (LWP 17193) "oggdemux5353:si" 0x7f3dc3017739 in syscall () from /lib64/libc.so.6 8Thread 0x7f3d7e710700 (LWP 17194) "multiqueue5353:" 0x7f3dc3017739 in syscall () from /lib64/libc.so.6 9Thread 0x7f3d9df36700 (LWP 17227) "oggdemux5354:si" 0x7f3dc3017739 in syscall () from /lib64/libc.so.6 10 Thread 0x7f3d7dd01700 (LWP 17228) "typefind:sink" 0x7f3dc3017739 in syscall () from /lib64/libc.so.6 11 Thread 0x7f3d7d500700 (LWP 17229) "multiqueue5354:" 0x7f3dc3017739 in syscall () from /lib64/libc.so.6 * 12 Thread 0x7f3d5bfff700 (LWP 8290) "threaded-ml" 0x7f3dc30122c9 in poll () from /lib64/libc.so.6 (gdb) bt #0 0x7f3dc30122c9 in poll () at /lib64/libc.so.6 #1 0x7f3db95859b1 in () at /usr/lib64/libpulse.so.0 #2 0x7f3db95771e0 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f3db957782e in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f3db95778e0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f3db95858f9 in () at /usr/lib64/libpulse.so.0 #6 0x7f3db7691668 in () at /usr/lib64/pulseaudio/libpulsecommon-12.0.so #7 0x7f3dbfc69554 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3dc301cccf in clone () at /lib64/libc.so.6 (gdb) thread 6 [Switching to thread 6 (Thread 0x7f3d7ef11700 (LWP 17192))] #0 0x7f3dc3017739 in syscall () from /lib64/libc.so.6 (gdb) bt #0 0x7f3dc3017739 in syscall () at /lib64/libc.so.6 #1 0x7f3dbd693c5f in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3d9f70121b in () at /usr/lib64/libgstreamer-1.0.so.0 #3 0x7f3dbd6765e3 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3dbd675c45 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f3dbfc69554 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3dc301cccf in clone () at /lib64/libc.so.6 Threads 6, 7, 9 and 10 have a similar backtrace and -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 395704] Media Codec required popup which can't be closed when can't play the unplugged notification sound.
https://bugs.kde.org/show_bug.cgi?id=395704 --- Comment #3 from Antonio Larrosa --- (sorry, send it to early by mistake) and thread 8's backtrace is: (gdb) threa 8 [Switching to thread 8 (Thread 0x7f3d7e710700 (LWP 17194))] #0 0x7f3dc3017739 in syscall () from /lib64/libc.so.6 (gdb) bt #0 0x7f3dc3017739 in syscall () at /lib64/libc.so.6 #1 0x7f3dbd693c5f in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3d9e8d70db in () at /usr/lib64/libgstbase-1.0.so.0 #3 0x7f3d9e8d8430 in gst_data_queue_pop () at /usr/lib64/libgstbase-1.0.so.0 #4 0x7f3d9c3a8bd1 in () at /usr/lib64/gstreamer-1.0/libgstcoreelements.so #5 0x7f3d9f701021 in () at /usr/lib64/libgstreamer-1.0.so.0 #6 0x7f3dbd6765e3 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f3dbd675c45 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f3dbfc69554 in start_thread () at /lib64/libpthread.so.0 #9 0x7f3dc301cccf in clone () at /lib64/libc.so.6 I'm afraid that after quitting gdb and reinstalling the debuginfo packages, powerdevil changed its behaviour and didn't show any popup anymore so I couldn't get more specific debug info. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396912] New: Infinite notifications 'An application needs additional multimedia codecs'
https://bugs.kde.org/show_bug.cgi?id=396912 Bug ID: 396912 Summary: Infinite notifications 'An application needs additional multimedia codecs' Product: plasmashell Version: 5.13.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: larr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 I'm getting infinite notifications in plasma saying "An application needs additional multimedia codecs" and a button to install ogg vorbis decoders (which I had installed). If I open the notification applet in plasma and clear the whole notifications history, it's filled again with the same messages instantaneously (at least 10 notifications/second, but it happens so fast it's difficult to count). This notification is the same that is shown when running After some debugging, I found that this notification is run by phonon executing: /usr/lib/gst-install-plugins-helper "gstreamer|1.0|plasmashell|decodificador Vorbis|decoder-audio/x-vorbis" (this can be run manually to reproduce the message) That command is run by PluginInstaller::addPlugin in phonon-gstreamer, when calling gst_install_plugins_async . It seems gstreamer has an internal loop that at some point calls the Phonon::Gstreamer::Pipeline::cb_error callback. This calls PluginInstaller::checkInstalledPlugins [see backtrace 1 below] and at this poing, PluginInstaller's m_state is Idle, m_pluginList is empty and m_descList is a list containing one string: "gstreamer|1.0|plasmashell|decodificador Vorbis|decoder-audio/x-vorbis", so the condition (!allFound || m_descList.size() > 0) is true and so it tries to install the codec by running the above command. I set a breakpoint in Phonon::Gstreamer::PluginInstaller::pluginInstallationResult and noticed that the result is always GST_INSTALL_PLUGINS_SUCCESS. This makes sense, since I checked gst-install-plugins-helper is trying to using packagekit to install something that provides "gstreamer1(decoder-audio/x-vorbis)()(64bit)" and I have the gstreamer-plugins-base package installed, which provides that capability. I tried replacing the binary /usr/lib/gst-install-plugins-helper with a symlink to /bin/true to check if maybe each notification was somehow generating the next one (for example, because plasma tried to play a sound and this would fail, generate a new notification, which would try to play another sound...), but no. Replacing the command with 'true' stopped the notifications, but I could still see in gdb that it's executing it continuously as fast as the cpu allows. I was tempted to try to fix this by making Phonon:Gstreamer::PluginInstaller have a check that doesn't try to install the same plugin more than once per minute, or something like that, but the above test shows that this is not a valid fix. Btw, while trying to understand phonon's code I noticed that PluginInstaller's m_pluginList is always empty as PluginInstaller::addPlugin(GstMessage *gstMessage) is called in each iteration, but PluginInstaller::addPlugin(const QString &name, PluginType type) is never called (which is the only method that inserts anything into m_pluginList. I wondered if maybe filing this bug entry for phonon, but I'm not sure and since it's plasmashell the process trying to play sound I thought I'd start here, and maybe later we can move it to phonon. Any idea of what else to try? I'll leave plasmashell stopped in gdb as long as I can in order to continue testing this, as this problem happened to me other times and it's difficult to reproduce. This all happens in openSUSE Tumbleweed with plasma 5.13.3, phonon4qt5-4.10.1, phonon4qt5-backend-gstreamer 4.9.0, gstreamer 1.14.1, pulseaudio 12.0, Frameworks 5.47.0 and Qt 5.11.1, but I've seen the problem with older versions too (I can't recall the first time I had this problem, but it was many months ago). [backtrace 1] #0 0x7f9f2e956f95 in Phonon::Gstreamer::PluginInstaller::checkInstalledPlugins() (this=0x555ad29b5060) at /usr/src/debug/phonon4qt5-backend-gstreamer-4.9.0-1.8.x86_64/gstreamer/plugininstaller.cpp:253 #1 0x7f9f2e94deee in Phonon::Gstreamer::Pipeline::cb_error(_GstBus*, _GstMessage*, void*) (bus=, gstMessage=0x555b21f44310, data=0x555ad2731800) at /usr/src/debug/phonon4qt5-backend-gstreamer-4.9.0-1.8.x86_64/gstreamer/pipeline.cpp:500 #2 0x7fa0114826c5 in ffi_call_unix64 () at ../src/x86/unix64.S:101 #3 0x7fa011481bd7 in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=) at ../src/x86/ffi64.c:662 #4 0x7f9f61f78565 in g_cclosure_marshal_generic () at /usr/lib64/libgobject-2.0.so.0 #5 0x7f9f61f77aed in g_closure_invoke () at /usr/lib64/libgobject-2.0.so.0 #6 0x7f9f61f8ab13 in () at /usr/lib64/libgobject-2.0.so.0 #7 0x7f9f61f93b4a in g_signal_emit
[Discover] [Bug 392971] Discovery crashed after clicking settings
https://bugs.kde.org/show_bug.cgi?id=392971 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org --- Comment #1 from Antonio Larrosa --- Some questions in order to have more information... Can you write here the output of running "zypper lr -d" ? Just to try to reproduce your system configuration. Did you run "zypper dup" to update your system recently? I tried updating my system and can't reproduce this (nor I could reproduce it before updating) Can you reproduce the problem without yast running in the background? and after a system restart? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 389825] Does not build with Qt dev branch: "error: 'cupsOptionsList' is not a member of 'QCUPSSupport'"
https://bugs.kde.org/show_bug.cgi?id=389825 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org --- Comment #1 from Antonio Larrosa --- Proposed patch at https://phabricator.kde.org/D10345 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 389825] Does not build with Qt dev branch: "error: 'cupsOptionsList' is not a member of 'QCUPSSupport'"
https://bugs.kde.org/show_bug.cgi?id=389825 Antonio Larrosa changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Antonio Larrosa --- Patch was approved and submitted to master -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390840] New: Discover has a problem when packagekitd is stopped
https://bugs.kde.org/show_bug.cgi?id=390840 Bug ID: 390840 Summary: Discover has a problem when packagekitd is stopped Product: Discover Version: 5.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PackageKit Assignee: aleix...@kde.org Reporter: larr...@kde.org Target Milestone: --- When updating the packages, sometimes Discover shows in its output: PackageKit stopped running! and the "Checking for updates..." (Looking for updates) messages are kept on discover forever, as if the connection with packagekitd was lost. After some debugging, it seems packagekitd can be configured to end automatically after some idle time (Just set ShutdownTimeout=15 under [Daemon] in /etc/PackageKit/PackageKit.conf), and that confuses Discover. Note that openSUSE did install a default of ShutdownTimeout=15 in the past, so old systems may have that config option. This was done because of a bug in libzypp (https://bugzilla.opensuse.org/show_bug.cgi?id=899755) which was fixed in 2017. Since last August, the option is no longer used in new installations, but old ones still use it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389531] Discover won't show app icons in openSUSE
https://bugs.kde.org/show_bug.cgi?id=389531 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org --- Comment #2 from Antonio Larrosa --- This is what that command returns on openSUSE Tumbleweed with KDE 5.11.95 (the 5.12 beta): > LANG=C appstreamcli search krita --details Identifier: org.kde.krita.desktop [desktop-application] Name: Krita Summary: Digital Painting, Creative Freedom Package: krita Homepage: https://www.krita.org/ Description: Krita is the full-featured digital art studio. It is perfect for sketching and painting, and presents an end–to–end solution for creating digital painting files from scratch by masters. Krita is a great choice for creating concept art, comics, textures for rendering and matte paintings. Krita supports many colorspaces like RGB and CMYK at 8 and 16 bits integer channels, as well as 16 and 32 bits floating point channels. Have fun painting with the advanced brush engines, amazing filters and many handy features that make Krita enormously productive. Default Screenshot URL: http://files.kde.org/krita/marketing/appdata/2016-05-24_screenshot_002.png Project Group: KDE License: GPL-2.0+ and LGPL-2.1+ Categories: - Graphics - RasterGraphics Provided Items: ↓ Mimetypes: - application/x-krita - application/x-krita-paintoppreset - image/openraster Binaries: krita Looking at the /usr/share/metainfo/org.kde.krita.appdata.xml file, I see there are more screenshots (4 of them, which are shown in discover correctly even if they're not shown in the appstreamcli output), but there's no icon defined. I looked here: https://cgit.kde.org/krita.git/tree/krita/org.kde.krita.appdata.xml?h=Aniketh/T6108-Integrate-with-share.krita.org And it seems there's no icon defined by upstream neither. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389531] Discover won't show app icons in openSUSE
https://bugs.kde.org/show_bug.cgi?id=389531 --- Comment #4 from Antonio Larrosa --- I updated AppStream to 0.11.8 in openSUSE Tumbleweed (it will get to the repositories in a couple of days or so) and I checked that that update fixes this problem. Thanks Ivan for reporting this, and thanks to Aleix for his help debugging it and getting this into my attention. Teamwork! :) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 385294] New icons required for plasma-pa
https://bugs.kde.org/show_bug.cgi?id=385294 --- Comment #4 from Antonio Larrosa --- Created attachment 110310 --> https://bugs.kde.org/attachment.cgi?id=110310&action=edit Plasma volume applet screenshot I'm sorry, I just noticed today that Andreas was working on this. Thanks for the icons that were added, but I'm afraid I'm not sure if those will be useful in this case. The needed icons would be used like the headset and internal card icons in the attached screenshot. While afaik, the added icons are a monochrome version and much smaller. I wouldn't remove them now they're done, just in case they're useful for someone else, but still I think we'd need bigger color icons for those. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373633] New: konsole process crashed when closing a tab
https://bugs.kde.org/show_bug.cgi?id=373633 Bug ID: 373633 Summary: konsole process crashed when closing a tab Product: konsole Version: 16.08.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: larr...@kde.org Target Milestone: --- Application: konsole (16.08.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.9-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had many tabs open in two konsole windows, I decided to close several tabs I wasn't using anymore and when closing one of them, the konsole process crashed (closing the two windows). The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb70b6ebe00 (LWP 10511))] Thread 2 (Thread 0x7fb6efdf5700 (LWP 10513)): #0 0x7fb70b02368d in poll () from /lib64/libc.so.6 #1 0x7fb7011f7876 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb7011f798c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb70761d79b in QEventDispatcherGlib::processEvents (this=0x7fb6e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fb7075c71ea in QEventLoop::exec (this=this@entry=0x7fb6efdf4cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7fb7073f58b3 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7fb70577f3e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fb7073fa558 in QThreadPrivate::start (arg=0x7fb7059f0d20) at thread/qthread_unix.cpp:344 #8 0x7fb702ec9454 in start_thread () from /lib64/libpthread.so.0 #9 0x7fb70b02c39f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb70b6ebe00 (LWP 10511)): [KCrash Handler] #6 0x7fb70afbf814 in free () from /lib64/libc.so.6 #7 0x7fb7075f2b84 in QObjectPrivate::Connection::~Connection (this=0x4578030, __in_chrg=) at kernel/qobject.cpp:1056 #8 0x7fb7075fc71c in QObjectPrivate::Connection::deref (this=) at kernel/qobject_p.h:156 #9 QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:977 #10 0x7fb70854bea9 in QAction::~QAction (this=0x10dccf40, __in_chrg=) at kernel/qaction.cpp:570 #11 0x7fb70854bed9 in QAction::~QAction (this=0x10dccf40, __in_chrg=) at kernel/qaction.cpp:594 #12 0x7fb7075f36d1 in QObjectPrivate::deleteChildren (this=this@entry=0x248f230) at kernel/qobject.cpp:1970 #13 0x7fb7075fca4f in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1041 #14 0x7fb70854bea9 in QAction::~QAction (this=0x78a53a0, __in_chrg=) at kernel/qaction.cpp:570 #15 0x7fb70859ca8d in QWidgetAction::~QWidgetAction (this=0x78a53a0, __in_chrg=) at kernel/qwidgetaction.cpp:118 #16 0x7fb7093cf6c1 in KSelectAction::~KSelectAction (this=0x78a53a0, __in_chrg=) at /usr/src/debug/kwidgetsaddons-5.28.0/src/kselectaction.cpp:98 #17 0x7fb709d32219 in KCodecAction::~KCodecAction (this=0x78a53a0, __in_chrg=) at /usr/src/debug/kconfigwidgets-5.28.0/src/kcodecaction.cpp:85 #18 0x7fb7075f36d1 in QObjectPrivate::deleteChildren (this=this@entry=0x24b3480) at kernel/qobject.cpp:1970 #19 0x7fb7075fca4f in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1041 #20 0x7fb70acb8429 in Konsole::SessionController::~SessionController (this=0x24b3350, __in_chrg=) at /usr/src/debug/konsole-16.08.3/src/SessionController.cpp:212 #21 0x7fb70acb8469 in Konsole::SessionController::~SessionController (this=0x24b3350, __in_chrg=) at /usr/src/debug/konsole-16.08.3/src/SessionController.cpp:222 #22 0x7fb7075f5d90 in QObject::event (this=0x24b3350, e=) at kernel/qobject.cpp:1254 #23 0x7fb70855292c in QApplicationPrivate::notify_helper (this=, receiver=0x24b3350, e=0x3fe0bb0) at kernel/qapplication.cpp:3799 #24 0x7fb70855a0e1 in QApplication::notify (this=0x20ad340, receiver=0x24b3350, e=0x3fe0bb0) at kernel/qapplication.cpp:3556 #25 0x7fb7075c9200 in QCoreApplication::notifyInternal2 (receiver=0x24b3350, event=event@entry=0x3fe0bb0) at kernel/qcoreapplication.cpp:988 #26 0x7fb7075cb98d in QCoreApplication::sendEvent (event=0x3fe0bb0, receiver=) at kernel/qcoreapplication.h:231 #27 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x20ab0d0) at kernel/qcoreapplication.cpp:1649 #28 0x7fb7075cbdf8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #29 0x7fb70761d373 in postEventSourceDispatch (s=0x20f20e0) at kernel/qeventdispatcher_glib.cpp:276 #30 0x7fb7011f7677 in g_main_context_dispatch () from /usr/lib64/l
[konsole] [Bug 373633] konsole process crashed when closing a tab
https://bugs.kde.org/show_bug.cgi?id=373633
--- Comment #1 from Antonio Larrosa ---
Just in case it helps, I'll add here the source lines around each frame in the
backtrace:
(gdb) frame 7
#7 0x7fb7075f2b84 in QObjectPrivate::Connection::~Connection
(this=0x4578030, __in_chrg=) at kernel/qobject.cpp:1056
1056delete [] v;
(gdb) l
1051QObjectPrivate::Connection::~Connection()
1052{
1053if (ownArgumentTypes) {
1054const int *v = argumentTypes.load();
1055if (v != &DIRECT_CONNECTION_ONLY)
1056delete [] v;
1057}
1058if (isSlotObject)
1059slotObj->destroyIfLastRef();
1060}
(gdb) frame 8
#8 0x7fb7075fc71c in QObjectPrivate::Connection::deref (this=) at kernel/qobject_p.h:156
156 delete this;
(gdb) l
151 int method() const { Q_ASSERT(!isSlotObject); return
method_offset + method_relative; }
152 void ref() { ref_.ref(); }
153 void deref() {
154 if (!ref_.deref()) {
155 Q_ASSERT(!receiver);
156 delete this;
157 }
158 }
159 };
160 // ConnectionList is a singly-linked list
(gdb) frame 9
#9 QObject::~QObject (this=, __in_chrg=) at
kernel/qobject.cpp:977
977 c->deref();
(gdb) l
972 c->isSlotObject = false;
973 locker.unlock();
974 c->slotObj->destroyIfLastRef();
975 locker.relock();
976 }
977 c->deref();
978 }
979 }
980
981 if (!--d->connectionLists->inUse) {
(gdb) frame 10
#10 0x7fb70854bea9 in QAction::~QAction (this=0x10dccf40,
__in_chrg=) at kernel/qaction.cpp:570
570 QAction::~QAction()
(gdb) l
565
566
567 /*!
568 Destroys the object and frees allocated resources.
569 */
570 QAction::~QAction()
571 {
572 Q_D(QAction);
573 for (int i = d->widgets.size()-1; i >= 0; --i) {
574 QWidget *w = d->widgets.at(i);
(gdb) frame 11
#11 0x7fb70854bed9 in QAction::~QAction (this=0x10dccf40,
__in_chrg=) at kernel/qaction.cpp:594
594 }
(gdb) l
589 const int id = d->alternateShortcutIds.at(i);
590 qApp->d_func()->shortcutMap.removeShortcut(id, this);
591 }
592 }
593 #endif
594 }
595
596 /*!
597 Sets this action group to \a group. The action will be automatically
598 added to the group's list of actions.
(gdb) frame 12
#12 0x7fb7075f36d1 in QObjectPrivate::deleteChildren
(this=this@entry=0x248f230) at kernel/qobject.cpp:1970
1970delete currentChildBeingDeleted;
(gdb) l
1965// don't use qDeleteAll as the destructor of the child might
1966// delete siblings
1967for (int i = 0; i < children.count(); ++i) {
1968currentChildBeingDeleted = children.at(i);
1969children[i] = 0;
1970delete currentChildBeingDeleted;
1971}
1972children.clear();
1973currentChildBeingDeleted = 0;
1974isDeletingChildren = false;
(gdb) frame 13
#13 0x7fb7075fca4f in QObject::~QObject (this=,
__in_chrg=) at kernel/qobject.cpp:1041
1041d->deleteChildren();
(gdb) l
1036}
1037}
1038}
1039
1040if (!d->children.isEmpty())
1041d->deleteChildren();
1042
1043qt_removeObject(this);
1044if (Q_UNLIKELY(qtHookData[QHooks::RemoveQObject]))
1045
reinterpret_cast(qtHookData[QHooks::RemoveQObject])(this);
(gdb) frame 14
#14 0x7fb70854bea9 in QAction::~QAction (this=0x78a53a0,
__in_chrg=) at kernel/qaction.cpp:570
570 QAction::~QAction()
(gdb) l
565
566
567 /*!
568 Destroys the object and frees allocated resources.
569 */
570 QAction::~QAction()
571 {
572 Q_D(QAction);
573 for (int i = d->widgets.size()-1; i >= 0; --i) {
574 QWidget *w = d->widgets.at(i);
(gdb) frame 15
#15 0x7fb70859ca8d in QWidgetAction::~QWidgetAction (this=0x78a53a0,
__in_chrg=) at kernel/qwidgetaction.cpp:118
118 QWidgetAction::~QWidgetAction()
(gdb) l
113 }
114
115 /*!
116 Destroys the object and frees allocated resources.
117 */
118 QWidgetAction::~QWidgetAction()
119 {
120 Q_D(QWidgetAction);
121 for (int i = 0; i < d->createdWidgets.count(); ++i)
122 disconnect(d->createdWidgets.at(i),
SIGNAL(destroyed(QObject*)),
(gdb) frame 16
#16 0x7fb7093cf6c1 in KSelectAction::~KSelectAction (this=0x78a53a0,
__in_chrg=) at
/usr/src/debug/kwidgetsaddons-5.28.0/src/kselectaction.cpp:98
98 KSelectAction::~KSelectAction()
(
[Breeze] [Bug 385294] New: New icons required for plasma-pa
https://bugs.kde.org/show_bug.cgi?id=385294 Bug ID: 385294 Summary: New icons required for plasma-pa Product: Breeze Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: task Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: larr...@kde.org CC: kain...@gmail.com Target Milestone: --- With https://phabricator.kde.org/D8054 , the plasma volume applet will change to use the form factors defined by PulseAudio, so we need icons for each of those form factors: form factor -> icon name currently used "internal" -> "audio-card" "speaker" -> "audio-speakers-symbolic" "handset" -> "phone" "tv" -> "video-television" "webcam" -> "camera-web" "microphone" -> "audio-input-microphone" "headset" -> "audio-headset" "headphone" -> "audio-headphones" "hands-free" -> icon missing "car" -> icon missing "hifi" -> icon missing "computer" -> "computer" "portable" -> icon missing We would need icons for the missing form factors and also, we would need all of them to have a symbolic version for plasma, since currently, some of them are monochrome and others have colors. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] 4.x application configuration rc files are ignored [patch]
https://bugs.kde.org/show_bug.cgi?id=364258 Antonio Larrosa changed: What|Removed |Added CC||larr...@kde.org --- Comment #24 from Antonio Larrosa --- Created attachment 101393 --> https://bugs.kde.org/attachment.cgi?id=101393&action=edit Support to migrate digiKam 4 settings/database in the first run wizard I've implemented this patch that adds a new page to the FirstRun wizard that allows the user to choose if he/she wants to do a migration of the digikam4 settings (only if settings from digikam4 are detected). If the user selects to create new settings, then the usual wizard continues, and if the user selects to migrate then files are moved as explained by Caulier in #c8 and the database albumroots are updated since digiKam 5 doesn't interpret correctly values like volumeid:?path=%2Fhome%2Fantonio%2FPictures and they need to be url-decoded. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357944] wrong encoded collection paths after upgrade from digikam v4.x
https://bugs.kde.org/show_bug.cgi?id=357944 Antonio Larrosa changed: What|Removed |Added Latest Commit||http://commits.kde.org/digi ||kam/ca2983d109553c37398da3e ||afdac9010c7344a9a Version Fixed In||5.3.0 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Antonio Larrosa --- Git commit ca2983d109553c37398da3eafdac9010c7344a9a by Antonio Larrosa. Committed on 03/10/2016 at 16:55. Pushed by antlarr into branch 'master'. Modified NEWS to reference fixed bugs related to migration from digiKam 4 Related: bug 364258, bug 368968 FIXED-IN: 5.3.0 M +4-1NEWS http://commits.kde.org/digikam/ca2983d109553c37398da3eafdac9010c7344a9a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357944] wrong encoded collection paths after upgrade from digikam v4.x
https://bugs.kde.org/show_bug.cgi?id=357944 Antonio Larrosa changed: What|Removed |Added Latest Commit|http://commits.kde.org/digi |http://commits.kde.org/digi |kam/ca2983d109553c37398da3e |kam/da661e5c84ebaf8037c806a |afdac9010c7344a9a |3ac5c004bb6e56d8b --- Comment #9 from Antonio Larrosa --- Git commit da661e5c84ebaf8037c806a3ac5c004bb6e56d8b by Antonio Larrosa. Committed on 03/10/2016 at 17:05. Pushed by antlarr into branch 'master'. Modified NEWS to reference fixed bugs related to migration from digiKam 4 Related: bug 364258, bug 368968 FIXED-IN: 5.3.0 M +4-1NEWS http://commits.kde.org/digikam/da661e5c84ebaf8037c806a3ac5c004bb6e56d8b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368968] Geo bookmarks are not migrated from version 4 to version 5
https://bugs.kde.org/show_bug.cgi?id=368968 Antonio Larrosa changed: What|Removed |Added Latest Commit|http://commits.kde.org/digi |http://commits.kde.org/digi |kam/ca2983d109553c37398da3e |kam/da661e5c84ebaf8037c806a |afdac9010c7344a9a |3ac5c004bb6e56d8b --- Comment #2 from Antonio Larrosa --- Git commit da661e5c84ebaf8037c806a3ac5c004bb6e56d8b by Antonio Larrosa. Committed on 03/10/2016 at 17:05. Pushed by antlarr into branch 'master'. Modified NEWS to reference fixed bugs related to migration from digiKam 4 Related: bug 364258, bug 357944 FIXED-IN: 5.3.0 M +4-1NEWS http://commits.kde.org/digikam/da661e5c84ebaf8037c806a3ac5c004bb6e56d8b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 368968] Geo bookmarks are not migrated from version 4 to version 5
https://bugs.kde.org/show_bug.cgi?id=368968 Antonio Larrosa changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.3.0 Latest Commit||http://commits.kde.org/digi ||kam/ca2983d109553c37398da3e ||afdac9010c7344a9a --- Comment #1 from Antonio Larrosa --- Git commit ca2983d109553c37398da3eafdac9010c7344a9a by Antonio Larrosa. Committed on 03/10/2016 at 16:55. Pushed by antlarr into branch 'master'. Modified NEWS to reference fixed bugs related to migration from digiKam 4 Related: bug 364258, bug 357944 FIXED-IN: 5.3.0 M +4-1NEWS http://commits.kde.org/digikam/ca2983d109553c37398da3eafdac9010c7344a9a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] 4.x application configuration rc files are ignored [patch]
https://bugs.kde.org/show_bug.cgi?id=364258 Antonio Larrosa changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/digi ||kam/ca2983d109553c37398da3e ||afdac9010c7344a9a Version Fixed In||5.3.0 Latest Commit|http://commits.kde.org/digi |http://commits.kde.org/digi |kam/ca2983d109553c37398da3e |kam/da661e5c84ebaf8037c806a |afdac9010c7344a9a |3ac5c004bb6e56d8b --- Comment #25 from Antonio Larrosa --- Git commit ca2983d109553c37398da3eafdac9010c7344a9a by Antonio Larrosa. Committed on 03/10/2016 at 16:55. Pushed by antlarr into branch 'master'. Modified NEWS to reference fixed bugs related to migration from digiKam 4 Related: bug 357944, bug 368968 FIXED-IN: 5.3.0 M +4-1NEWS http://commits.kde.org/digikam/ca2983d109553c37398da3eafdac9010c7344a9a --- Comment #26 from Antonio Larrosa --- Git commit da661e5c84ebaf8037c806a3ac5c004bb6e56d8b by Antonio Larrosa. Committed on 03/10/2016 at 17:05. Pushed by antlarr into branch 'master'. Modified NEWS to reference fixed bugs related to migration from digiKam 4 Related: bug 357944, bug 368968 FIXED-IN: 5.3.0 M +4-1NEWS http://commits.kde.org/digikam/da661e5c84ebaf8037c806a3ac5c004bb6e56d8b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364258] 4.x application configuration rc files are ignored [patch]
https://bugs.kde.org/show_bug.cgi?id=364258 Antonio Larrosa changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/digi ||kam/ca2983d109553c37398da3e ||afdac9010c7344a9a Version Fixed In||5.3.0 Latest Commit|http://commits.kde.org/digi |http://commits.kde.org/digi |kam/ca2983d109553c37398da3e |kam/da661e5c84ebaf8037c806a |afdac9010c7344a9a |3ac5c004bb6e56d8b --- Comment #25 from Antonio Larrosa --- Git commit ca2983d109553c37398da3eafdac9010c7344a9a by Antonio Larrosa. Committed on 03/10/2016 at 16:55. Pushed by antlarr into branch 'master'. Modified NEWS to reference fixed bugs related to migration from digiKam 4 Related: bug 357944, bug 368968 FIXED-IN: 5.3.0 M +4-1NEWS http://commits.kde.org/digikam/ca2983d109553c37398da3eafdac9010c7344a9a --- Comment #26 from Antonio Larrosa --- Git commit da661e5c84ebaf8037c806a3ac5c004bb6e56d8b by Antonio Larrosa. Committed on 03/10/2016 at 17:05. Pushed by antlarr into branch 'master'. Modified NEWS to reference fixed bugs related to migration from digiKam 4 Related: bug 357944, bug 368968 FIXED-IN: 5.3.0 M +4-1NEWS http://commits.kde.org/digikam/da661e5c84ebaf8037c806a3ac5c004bb6e56d8b -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 371570] New: Duplicate entry in CollectionTable when creating database in a new installation
https://bugs.kde.org/show_bug.cgi?id=371570 Bug ID: 371570 Summary: Duplicate entry in CollectionTable when creating database in a new installation Product: Akonadi Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: larr...@kde.org On a clean openSUSE Leap 42.2 RC1 system (with kmail 5.3.0 and akonadi-server 16.08.2), I run kmail for the first time. It shows a "Starting Akonadi server" message for some seconds, then a dialog appears to "Provide personal data" (full name, email and password), and practically at the same time I get an error box from kmail that says: "The Email program encountered a fatal error and will terminate now. The error was: Could not create collection inbox, resourceId: 3" I ran kmail with full logs as dvratil suggested and got the attached output. That gave lots of information, and the directed to the real problem: log_akonadiserver: DATABASE ERROR: log_akonadiserver: Error code: 1062 log_akonadiserver: DB error: "Duplicate entry '4-inbox' for key 'CollectionTable_parentAndNameIndex'" log_akonadiserver: Error text: "Duplicate entry '4-inbox' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" log_akonadiserver: Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, cachePolicyCheckInterval, cachePolicyCacheTimeout, cachePolicySyncOnDemand, cachePolicyLocalParts, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14)" log_akonadiserver: Error during insertion into table "CollectionTable" "Duplicate entry '4-inbox' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement" log_akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Could not create collection inbox, resourceId: 3" log_mailcommon: "The Email program encountered a fatal error and will terminate now.\nThe error was:\nCould not create collection inbox, resourceId: 3" I can reproduce the problem every time, by removing the config files for the user and starting kmail again. Btw, note that if instead of starting kmail, I run akonadictl start and then kmail once akonadi is started, then there's no problem. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 371570] Duplicate entry in CollectionTable when creating database in a new installation
https://bugs.kde.org/show_bug.cgi?id=371570 --- Comment #1 from Antonio Larrosa --- Created attachment 101739 --> https://bugs.kde.org/attachment.cgi?id=101739&action=edit Logs from akonadi/kmail, showing the problem -- You are receiving this mail because: You are watching all bug changes.
