[plasma-pa] [Bug 488897] Device names differ between widget and KCM
https://bugs.kde.org/show_bug.cgi?id=488897 Łukasz Plich changed: What|Removed |Added CC||skeleton0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 487688] Kleopatra crashes when opening gpg sig file
https://bugs.kde.org/show_bug.cgi?id=487688 --- Comment #1 from Łukasz Żarnowiecki --- Created attachment 169910 --> https://bugs.kde.org/attachment.cgi?id=169910=edit This specific file crashes kleopatra -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 487688] New: Kleopatra crashes when opening gpg sig file
https://bugs.kde.org/show_bug.cgi?id=487688
Bug ID: 487688
Summary: Kleopatra crashes when opening gpg sig file
Classification: Applications
Product: kleopatra
Version: unspecified
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: aheine...@gnupg.org
Reporter: luk...@zarnowiecki.pl
CC: kdepim-b...@kde.org, m...@kde.org
Target Milestone: ---
Application: kleopatra (3.2.0.240500 (24.05.0))
Qt Version: 6.7.1
Frameworks Version: 6.2.0
Operating System: Linux 6.8.9-arch1-2 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 6.0.5 [CoredumpBackend]
-- Information about the crash:
When I open sig file to import it or examine, kleopatra crashes.
The crash can be reproduced every time.
-- Backtrace:
Application: Kleopatra (kleopatra), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/kleopatra...
[New LWP 31921]
[New LWP 31923]
[New LWP 31925]
[New LWP 31922]
[New LWP 31926]
[New LWP 31924]
[New LWP 31927]
[New LWP 31928]
[New LWP 31929]
Downloading separate debug info for
/usr/lib/libKPim6MimeTreeParserWidgets.so.6...
Downloading separate debug info for
/usr/lib/libKPim6IdentityManagementCore.so.6...
Downloading separate debug info for /usr/lib/libKPim6MailTransport.so.6...
Downloading separate debug info for /usr/lib/libKPim6AkonadiMime.so.6...
Downloading separate debug info for /usr/lib/libassuan.so.0...
Downloading separate debug info for /usr/lib/libgpg-error.so.0...
Downloading separate debug info for /usr/lib/libKF6DBusAddons.so.6...
Downloading separate debug info for /usr/lib/libkleopatraclientgui.so.1...
Downloading separate debug info for /usr/lib/libkleopatraclientcore.so.1...
Downloading separate debug info for /usr/lib/libKPim6Libkleo.so.6...
Downloading separate debug info for /usr/lib/libqgpgmeqt6.so.15...
Downloading separate debug info for /usr/lib/libgpgmepp.so.6...
Downloading separate debug info for /usr/lib/libgpgme.so.11...
Downloading separate debug info for /usr/lib/libKF6WindowSystem.so.6...
Downloading separate debug info for /usr/lib/libKPim6Mime.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOCore.so.6...
Downloading separate debug info for /usr/lib/libKF6Crash.so.6...
Downloading separate debug info for /usr/lib/libKF6XmlGui.so.6...
Downloading separate debug info for /usr/lib/libQt6Network.so.6...
Downloading separate debug info for /usr/lib/libQt6PrintSupport.so.6...
Downloading separate debug info for /usr/lib/libKF6IconWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6Codecs.so.6...
Downloading separate debug info for /usr/lib/libKF6WidgetsAddons.so.6...
Downloading separate debug info for /usr/lib/libQt6Widgets.so.6...
Downloading separate debug info for /usr/lib/libKF6CoreAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6IconThemes.so.6...
Downloading separate debug info for /usr/lib/libKF6ColorScheme.so.6...
Downloading separate debug info for /usr/lib/libKF6I18n.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigGui.so.6...
Downloading separate debug info for /usr/lib/libKF6ItemModels.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigCore.so.6...
Downloading separate debug info for /usr/lib/libQt6Gui.so.6...
Downloading separate debug info for /usr/lib/libQt6DBus.so.6...
Downloading separate debug info for /usr/lib/libQt6Core.so.6...
Downloading separate debug info for /usr/lib/libc.so.6...
Downloading separate debug info for /usr/lib/libKPim6MimeTreeParserCore.so.6...
Downloading separate debug info for /usr/lib/libKF6CalendarCore.so.6...
Downloading separate debug info for /usr/lib/libqt6keychain.so.1...
Downloading separate debug info for /usr/lib/libKPim6AkonadiWidgets.so.6...
Downloading separate debug info for /usr/lib/libKPim6AkonadiCore.so.6...
Downloading separate debug info for /usr/lib/libKF6Completion.so.6...
Downloading separate debug info for /usr/lib/libKF6TextCustomEditor.so.1...
Downloading separate debug info for /lib64/ld-linux-x86-64.so.2...
Downloading separate debug info for /usr/lib/libm.so.6...
Downloading separate debug info for /usr/lib/libX11.so.6...
Downloading separate debug info for /usr/lib/libxcb.so.1...
Downloading separate debug info for /usr/lib/libxcb-res.so.0...
Downloading separate debug info for /usr/lib/libXfixes.so.3...
Downloading separate debug info for /usr/lib/libxcb-keysyms.so.1...
Downloading separate debug info for /usr/lib/libKF6Service.so.6...
Downloading separate debug info for /usr/lib/libKF6AuthCore.so.6...
Downloading separate debug info for /usr/lib/libacl.so.1...
Downloading separate debug info for /usr/lib/libmount.so.1...
Downloading
[kdenlive] [Bug 484181] Mix clips doesn't work
https://bugs.kde.org/show_bug.cgi?id=484181 --- Comment #3 from Łukasz Zając --- (In reply to Jean-Baptiste Mardelle from comment #2) > I have updated the mix to only affect active tracks. From your screenshot, > it looks like your V1 track is not active. Can you try enabling it (Click on > the "V1" tag) in the track header. Let me know if it fixes the problem aah, yes, that did the trick. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 484181] Mix clips doesn't work
https://bugs.kde.org/show_bug.cgi?id=484181 --- Comment #1 from Łukasz Zając --- I did some more tests, and it looks like, mixing only works on audio clips now. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 484181] New: Mix clips doesn't work
https://bugs.kde.org/show_bug.cgi?id=484181 Bug ID: 484181 Summary: Mix clips doesn't work Classification: Applications Product: kdenlive Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: s...@rbtv.pl Target Milestone: --- Whenever I try to mix 2 clips to spawn short transition between them, kdenlive refuses to do it. It shows message "select a clip to apply the mix". It was working fine before update. Preview: https://www.youtube.com/watch?v=OTkMSDk-6IU SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuse Tumbleweed, kernel 6.7.9-1 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 484178] New: Importing .png images begs for transcoding which doesn't occur
https://bugs.kde.org/show_bug.cgi?id=484178 Bug ID: 484178 Summary: Importing .png images begs for transcoding which doesn't occur Classification: Applications Product: kdenlive Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: s...@rbtv.pl Target Milestone: --- After updating Kdenlive to 24.02, I'm having problem importing .png images to project bin. It asks me to transcode the files but then, those files do not appear in the project bin. They are lost in limbo. It's happening everytime by dragging from dolphin, or clicking import inside kdenlive. Preview: https://youtu.be/CzVZkCAWB-Y SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuse Tumbleweed, kernel 6.7.9-1 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 --- Comment #4 from Łukasz Konieczny --- I don't know how, but now, after I have reset both file type associations, this bug is not present. Perhaps I had some old settings (I have fought with this bug earlier). I'm closing this bug report. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 --- Comment #3 from Łukasz Konieczny --- Software versions: Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-10-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 --- Comment #2 from Łukasz Konieczny --- Created attachment 162914 --> https://bugs.kde.org/attachment.cgi?id=162914=edit And example of correctly depicted library -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 --- Comment #1 from Łukasz Konieczny --- Created attachment 162913 --> https://bugs.kde.org/attachment.cgi?id=162913=edit Example of library depicted as manual page -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476638] New: If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI
https://bugs.kde.org/show_bug.cgi?id=476638 Bug ID: 476638 Summary: If the name of shared library ends with digit from 1 to 9, Plasma recognizes it as manual page, and one can't change it using GUI Classification: Applications Product: systemsettings Version: 5.27.9 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_filetypes Assignee: plasma-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: fa...@kde.org Target Milestone: --- Created attachment 162911 --> https://bugs.kde.org/attachment.cgi?id=162911=edit Many libraries are depicted as manual pages SUMMARY *** The wrong file association (and icon) of shared libraries which names end with .[1-9] is somewhat hardcoded in Plasma and it is not possible to change it, no matter what you would do in GUI. They are presented as manual pages, despite file command shows they are shared libraries. I have tried: 1. removing pattern *.[1-9] from application/x-troff-man association 2. adding pattern *.so.*.[0-9] to application/x-sharedlib association. It doesn't work. I suspect there is some fundamental problem with kcm_filetypes, which prevents an ordinary user from doing whatever they want with file associations. You can see in attached screenshots what have I done and how still wrongly Dolphin shows shared libraries for example in /usr/lib/x86_64-linux-gnu/ *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 474191] Crash when opening event in main view
https://bugs.kde.org/show_bug.cgi?id=474191 --- Comment #2 from Łukasz Żarnowiecki --- Yes, its working. I did not know I had it enabled... -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 474191] Crash when opening event in main view
https://bugs.kde.org/show_bug.cgi?id=474191 Łukasz Żarnowiecki changed: What|Removed |Added Product|kde |Merkuro Component|general |general CC||c...@carlschwan.eu Version|unspecified |23.08.0 Assignee|unassigned-b...@kde.org |claudio.cam...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 474191] New: Crash when opening event in main view
https://bugs.kde.org/show_bug.cgi?id=474191
Bug ID: 474191
Summary: Crash when opening event in main view
Classification: I don't know
Product: kde
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: luk...@zarnowiecki.pl
Target Milestone: ---
Application: merkuro-calendar (23.08.0)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.12-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
When I click on calendar event in week view application crashes.
What I did was essentialy to add a new calendar event and its location. It did
crash first when I was typing location. After that it crashes when I try to
open this event.
The crash can be reproduced every time.
-- Backtrace:
Application: Merkuro Calendar (merkuro-calendar), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7ff9c2f03dbe in QDeclarativeGeocodeModel::~QDeclarativeGeocodeModel()
(this=0x5567e4cfb490, this=) at
/usr/src/debug/qt5-location/qtlocation/src/location/declarativemaps/qdeclarativegeocodemodel.cpp:128
#7 0x7ff9c30cc94b in
QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x5567e4cfb490, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#8 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x5567e4cfb490, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#9 0x7ffa23ac73bd in QObjectPrivate::deleteChildren()
(this=this@entry=0x5567e4b995a0) at kernel/qobject.cpp:2137
#10 0x7ffa23ac7b39 in QObject::~QObject() (this=this@entry=0x5567e42b4210,
this=) at kernel/qobject.cpp:1115
#11 0x7ffa25e2c668 in QQuickItem::~QQuickItem()
(this=this@entry=0x5567e42b4210, this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:2389
#12 0x7ff9c2f16d69 in
QDeclarativeGeoMapItemGroup::~QDeclarativeGeoMapItemGroup()
(this=this@entry=0x5567e42b4210, this=) at
/usr/src/debug/qt5-location/qtlocation/src/location/declarativemaps/qdeclarativegeomapitemgroup.cpp:150
#13 0x7ff9c2f16e09 in
QDeclarativeGeoMapItemView::~QDeclarativeGeoMapItemView()
(this=this@entry=0x5567e42b4210, this=) at
/usr/src/debug/qt5-location/qtlocation/src/location/declarativemaps/qdeclarativegeomapitemview.cpp:111
#14 0x7ff9c30cca2b in
QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x5567e42b4210, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#15 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x5567e42b4210, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#16 0x7ffa23ac73bd in QObjectPrivate::deleteChildren()
(this=this@entry=0x5567e2bed620) at kernel/qobject.cpp:2137
#17 0x7ffa23ac7b39 in QObject::~QObject() (this=this@entry=0x5567e1cc5cc0,
this=) at kernel/qobject.cpp:1115
#18 0x7ffa25e2c668 in QQuickItem::~QQuickItem()
(this=this@entry=0x5567e1cc5cc0, this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:2389
#19 0x7ff9c2f12297 in QDeclarativeGeoMap::~QDeclarativeGeoMap()
(this=this@entry=0x5567e1cc5cc0, this=) at
/usr/src/debug/qt5-location/qtlocation/src/location/declarativemaps/qdeclarativegeomap.cpp:284
#20 0x7ff9c30ccbeb in
QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x5567e1cc5cc0, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#21 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x5567e1cc5cc0, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#22 0x7ffa23ac3f9e in QObject::event(QEvent*) (this=0x5567e1cc5cc0,
e=0x5567e6e80470) at kernel/qobject.cpp:1334
#23 0x7ffa2477893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5567e1cc5cc0, e=0x5567e6e80470) at
kernel/qapplication.cpp:3640
#24 0x7ffa23a9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5567e1cc5cc0, event=0x5567e6e80470) at
kernel/qcoreapplication.cpp:1064
#25 0x7ffa23aa165b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x5567e0a1ee50) at
kernel/qcoreapplication.cpp:1821
#26 0x7ffa23ae76d8 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x5567e0a3d1b0) at kernel/qeventdispatcher_glib.cpp:277
#27 0x7ffa21b10a61 in g_main_dispatch (context=0x7ffa0ee0) at
../glib/glib/gmain.c:3460
#28 g_main_context_dispatch (context=0x7ffa0ee0) at
../glib/glib/gmain.c:4200
#29 0x7ffa21b6dc29 in g_main_context_iterate.isra.0
(context=context@entry=0x7ffa0ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#30 0x7ffa21b0e112 in g_main_context_iteration (context=0x7ffa0ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#31 0x7ffa23aeb51c in
[plasma-nm] [Bug 471870] New: Sometimes the NetworkManager applet doesn't appear after resuming from suspend and is not reachable unless suspend and resume again
https://bugs.kde.org/show_bug.cgi?id=471870 Bug ID: 471870 Summary: Sometimes the NetworkManager applet doesn't appear after resuming from suspend and is not reachable unless suspend and resume again Classification: Plasma Product: plasma-nm Version: 5.27.6 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- Created attachment 160044 --> https://bugs.kde.org/attachment.cgi?id=160044=edit NM applet is not visible anywhere after resume SUMMARY There is a problem with NetworkManager applet in tray. It happens frequently (but not always), that this applet doesn't appear after resuming from suspend to RAM. I have attached a screenshot of such situation. As you can see, there is no NM applet either in tray or in the slid-up applet with other tray items. STEPS TO REPRODUCE 1. Suspend system to RAM. 2. Resume from suspend. 3. Do points 1 and 2 until NM applet dies. 4. If it dies, suspend again and resume, NM applet most likely will reappear. OBSERVED RESULT Sometimes NM applet is not reachable after resuming. EXPECTED RESULT NM applet is always visible in the system. SOFTWARE/OS VERSIONS GNU/Linux, KDE Plasma: (available in About System) Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-24-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 466106] Don't register MPRIS interface when not doing anything controllable by MPRIS
https://bugs.kde.org/show_bug.cgi?id=466106 Łukasz Konieczny changed: What|Removed |Added Version|22.12.2 |23.04.2 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 466106] Don't register MPRIS interface when not doing anything controllable by MPRIS
https://bugs.kde.org/show_bug.cgi?id=466106 Łukasz Konieczny changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Łukasz Konieczny --- The bug still exists. The situation happens when i suspend system to RAM with many Gwenview instances opened, and then resume from suspend. It also happens when Plasma shell crashes and relaunches itself while many instances of Gwenview are opened. -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 470251] New: Crash when ordering items
https://bugs.kde.org/show_bug.cgi?id=470251
Bug ID: 470251
Summary: Crash when ordering items
Classification: Applications
Product: ktimetracker
Version: 5.0.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: aspotas...@gmail.com
Reporter: luk...@zarnowiecki.pl
Target Milestone: ---
Application: ktimetracker (5.0.1)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.3-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
Sometimes when you reorder tasks, move out of sub task, put into substask
existing ones, application crashes. Happened to me three times in a row, but I
am not sure what causes it specifically, because not every move action triggers
it.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: KTimeTracker (ktimetracker), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fedb0a7934c in QSortFilterProxyModel::sibling (this=,
row=1465036853, column=0, idx=...) at itemmodels/qsortfilterproxymodel.cpp:2234
#7 0x7fedb1a50457 in QModelIndex::sibling (acolumn=0, arow=, this=) at
../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:446
#8 QTreeViewPrivate::viewIndex (this=0x56073701e100, _index=...) at
itemviews/qtreeview.cpp:3599
#9 0x7fedb1a49292 in QTreeView::visualRect
(this=this@entry=0x560737019310, index=...) at itemviews/qtreeview.cpp:1112
#10 0x7fedb19da595 in QAbstractItemViewPrivate::setHoverIndex
(this=this@entry=0x56073701e100, index=...) at
itemviews/qabstractitemview.cpp:164
#11 0x7fedb19dcb2f in QAbstractItemView::viewportEvent
(this=0x560737019310, event=0x7ffdfcd89cd0) at
itemviews/qabstractitemview.cpp:1714
#12 0x7fedb0a97b22 in
QCoreApplicationPrivate::sendThroughObjectEventFilters
(receiver=receiver@entry=0x56073700fee0, event=event@entry=0x7ffdfcd89cd0) at
kernel/qcoreapplication.cpp:1190
#13 0x7fedb177892f in QApplicationPrivate::notify_helper (this=, receiver=0x56073700fee0, e=0x7ffdfcd89cd0) at
kernel/qapplication.cpp:3634
#14 0x7fedb0a9ab18 in QCoreApplication::notifyInternal2
(receiver=0x56073700fee0, event=0x7ffdfcd89cd0) at
kernel/qcoreapplication.cpp:1064
#15 0x7fedb0a9ab83 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462
#16 0x7fedb177b669 in QApplicationPrivate::dispatchEnterLeave
(enter=0x560736cde350, leave=, globalPosF=...) at
kernel/qapplication.cpp:2251
#17 0x7fedb17d05c3 in QWidgetWindow::handleEnterLeaveEvent
(event=0x7ffdfcd89f80, this=0x560736b67ed0) at kernel/qwidgetwindow.cpp:447
#18 QWidgetWindow::event (this=0x560736b67ed0, event=0x7ffdfcd89f80) at
kernel/qwidgetwindow.cpp:264
#19 0x7fedb177893f in QApplicationPrivate::notify_helper (this=, receiver=0x560736b67ed0, e=0x7ffdfcd89f80) at
kernel/qapplication.cpp:3640
#20 0x7fedb0a9ab18 in QCoreApplication::notifyInternal2
(receiver=0x560736b67ed0, event=0x7ffdfcd89f80) at
kernel/qcoreapplication.cpp:1064
#21 0x7fedb0a9aba3 in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#22 0x7fedb0f3a65c in QGuiApplicationPrivate::processLeaveEvent
(e=0x56073705c470) at kernel/qguiapplication.cpp:2464
#23 QGuiApplicationPrivate::processLeaveEvent (e=0x56073705c470) at
kernel/qguiapplication.cpp:2452
#24 0x7fedb0f2a955 in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at kernel/qwindowsysteminterface.cpp:1169
#25 0x7fedaeb5e8d5 in userEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /usr/lib/libQt5WaylandClient.so.5
#26 0x7fedaf10f53b in g_main_dispatch (context=0x7feda4000ee0) at
../glib/glib/gmain.c:3460
#27 g_main_context_dispatch (context=0x7feda4000ee0) at
../glib/glib/gmain.c:4200
#28 0x7fedaf16c219 in g_main_context_iterate.constprop.0
(context=0x7feda4000ee0, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4276
#29 0x7fedaf10e1a2 in g_main_context_iteration (context=0x7feda4000ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#30 0x7fedb0ae9f0c in QEventDispatcherGlib::processEvents
(this=0x56073686bab0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#31 0x7fedb0a99824 in QEventLoop::exec (this=this@entry=0x56073721c840,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#32 0x7fedb0f7d9fa in QBasicDrag::drag (this=0x56073684f8e0, o=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#33 0x7fedb0f77960 in QDragManager::drag (this=0x56073732ca70,
o=o@entry=0x560736cfb450) at kernel/qdnd.cpp:117
#34 0x7fedb0f7d03f in QDrag::exec (this=this@entry=0x560736cfb450,
supportedActions=..., supportedActions@entry=...,
[kontact] [Bug 468590] Window for mail writing does not repaint properly on Wayland
https://bugs.kde.org/show_bug.cgi?id=468590 Łukasz Żarnowiecki changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||luk...@zarnowiecki.pl Ever confirmed|0 |1 --- Comment #2 from Łukasz Żarnowiecki --- Yes, it's a probably a duplicate of the bug you mentioned and xwayland workaround is working fine for me. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 Łukasz Żarnowiecki changed: What|Removed |Added CC||luk...@zarnowiecki.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469916] New: Env variables field is overwriting program and arguments fields
https://bugs.kde.org/show_bug.cgi?id=469916 Bug ID: 469916 Summary: Env variables field is overwriting program and arguments fields Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: s...@rbtv.pl Target Milestone: 1.0 Created attachment 159050 --> https://bugs.kde.org/attachment.cgi?id=159050=edit video showcasing issue STEPS TO REPRODUCE 1. right click on app to enter properties 2. In application tab, put some env variables, save, close OBSERVED RESULT App will no longer run because If You open properties again, You will notice first env variable will move to program field and the rest to arguments field. EXPECTED RESULT env variables stay in the field and not overwrite the rest of fields. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468919] Some KDE Apps don't respect KWin window rules even when "ignore requested geometry" is set to "force"
https://bugs.kde.org/show_bug.cgi?id=468919 --- Comment #2 from Łukasz Konieczny --- (In reply to Nate Graham from comment #1) > Can you test the following other KDE apps so we can try to establish a > pattern? > - Dolphin > - Ark > - Konsole > - Discover > - System Settings > - Filelight > - Elisa Dolphin - behaves correctly Ark - behaves correctly Konsole - behaves incorrectly! Discover - behaves correctly System Settings - behaves incorrectly! Filelight - behaves correctly Elisa - behaves correctly Kate - behaves correctly Plasma System Monitor - behaves correctly Gwenview - behaves correctly KGet - behaves correctly Kid3 - behaves correctly Cantor - behaves incorrectly! LabPlot - behaves correctly KDE Marble - behaves correctly Spectacle - behaves correctly KDevelop - behaves correctly KDiskFree - behaves partially incorrectly - it re-launches with proper size, but the last column is stretched and horizontal scrollbar appears! KInfoCenter - behaves correctly Uff! Perhaps it's enough. Moreover, those programs, which behaves incorrectly, often launch not centered, despite I have setting to all windows appear centered. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468919] New: Some KDE Apps don't respect KWin window rules even when "ignore requested geometry" is set to "force"
https://bugs.kde.org/show_bug.cgi?id=468919 Bug ID: 468919 Summary: Some KDE Apps don't respect KWin window rules even when "ignore requested geometry" is set to "force" Classification: I don't know Product: kde Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- SUMMARY Some KDE Apps, notably KWrite and Okular, but probably others, don't launch to their window size being set (when previously their size was manually changed) even when "ignore requested geometry" is set to "force". That means, they stubbornly remember their last window size regardless of "ignore requested geometry" set to "force" and regardless of their window size set to "apply initially". This is annoying bug, not a feature, because perfectionists like me want to set initial sizes of all their applications to some values and have freedom to dynamically change that size, and have their apps again in their initial size after re-launching. STEPS TO REPRODUCE 1. Set some window size for particular program. 2. Set "ignore requested geometry" to "force". 3. Launch program. 4. Change its size by dragging border. 5. Close app. 6. Open it again. OBSERVED RESULT App has size you changed by dragging. EXPECTED RESULT App has size NOT you changed by dragging, but its initial size set by you. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467518] KWrite doesn't respect initial window size setting set in System Settings
https://bugs.kde.org/show_bug.cgi?id=467518 Łukasz Konieczny changed: What|Removed |Added Platform|Other |Kubuntu -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467518] New: KWrite doesn't respect initial window size setting set in System Settings
https://bugs.kde.org/show_bug.cgi?id=467518 Bug ID: 467518 Summary: KWrite doesn't respect initial window size setting set in System Settings Classification: Applications Product: kate Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- SUMMARY KWrite doesn't respect initial window size setting set in System Settings, that means when I set, that KWrite should appear after launching in such way that it has for example size of 400 px x 500 px, when I resize manually KWrite window, close KWrite and then launch it, it doesn't have size of 400 px x 500 px. STEPS TO REPRODUCE 1. Set initial size of KWrite window in System Settings or by clicking KWrite's icon in top-left corner of the window, set even rejecting window geometry demanding to "yes". 2. Launch KWrite. Resize its window manually. Close KWrite. 3. Launch KWrite. Observe, that KWrite's window doesn't have size of initial size set. OBSERVED RESULT KWrite doesn't respect window rules settings. EXPECTED RESULT KWrite fully respects window rules settings. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ADDITIONAL INFORMATION Kubuntu Backports PPA enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466106] Allow to exclude some applications from registering in media player applet in preferences of this applet
https://bugs.kde.org/show_bug.cgi?id=466106 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466106] New: Allow to exclude some applications from registering in media player applet in preferences of this applet
https://bugs.kde.org/show_bug.cgi?id=466106 Bug ID: 466106 Summary: Allow to exclude some applications from registering in media player applet in preferences of this applet Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: plasma-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 156513 --> https://bugs.kde.org/attachment.cgi?id=156513=edit Screenshot of media player applet, when 36 windows of Gwenview are opened SUMMARY A problem specific to me, but perhaps somebody has the same problem. I'm listening to music, using some audio player (for example Strawberry). In the same time I have 36 windows of Gwenview opened, in every window is a photo of my friends. I love those photos, so I want them to be opened simultaneously in 36 windows, one window per photo. All of those Gwenview windows register themselves as media player and the top of media player applet is littered by Gwenview icons, which even don't fit in the space in top of the applet. If I want to stop playing music in Strawberry and play something in Firefox, and then switch back to Strawberry, I can't, because I'm even not able to point to icon of Strawberry in the top of the applet. I have attached screenshot, to show you the problem. I would like to have an option to exclude particular programs from registering themselves as media player in this applet. Then I would exclude Gwenview, because I don't need to command Gwenview from this applet. STEPS TO REPRODUCE 1. Open way more windows of, for example, Gwenview, than you think you can, for example 40 windows of Gwenview, and observe, that each Gwenview window registers itself as media player in applet. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.6 Kernel Version: 6.0.12-76060006-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: System76 Product Name: Darter Pro System Version: darp7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 464960] New: Project and clip monitor overlay is not rendering properly
https://bugs.kde.org/show_bug.cgi?id=464960 Bug ID: 464960 Summary: Project and clip monitor overlay is not rendering properly Classification: Applications Product: kdenlive Version: 22.12.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: skeleton0...@gmail.com Target Milestone: --- Created attachment 155743 --> https://bugs.kde.org/attachment.cgi?id=155743=edit Screenshot over clip monitor overlay not being rendered SUMMARY The monitor overlay on both project's and clip's is not rendering at all or is rendering very slightly. This happens on Flatpak version but I also tested it on Fedora package and there is the same problem. Bug occurs every time, even after deleting kdenlive config files. STEPS TO REPRODUCE 1. Start Kdenlive 2. Load any clip or project OBSERVED RESULT Overlay is not being rendered in monitors EXPECTED RESULT Overlay with audio waveform and buttons on side should be rendered properly SOFTWARE/OS VERSIONS OS: Fedora Linux 37 (KDE Plasma) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376202] Emails are moved to folders on read, without explanation
https://bugs.kde.org/show_bug.cgi?id=376202 Łukasz changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #14 from Łukasz --- (In reply to Bug Janitor Service from comment #13) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! Luckily I haven't noticed the problem in Kontact 5.7.3, which I currently use. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 375149] Kmail deletes emails from folder after switching to folder
https://bugs.kde.org/show_bug.cgi?id=375149 Łukasz changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #16 from Łukasz --- (In reply to Justin Zobel from comment #14) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! The issue doesn't exist with the Kontact version I currenlty use, which is 5.7.3. -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 460701] New: KTimeTracker looses data
https://bugs.kde.org/show_bug.cgi?id=460701 Bug ID: 460701 Summary: KTimeTracker looses data Classification: Applications Product: ktimetracker Version: 5.0.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: luk...@zarnowiecki.pl Target Milestone: --- Created attachment 153022 --> https://bugs.kde.org/attachment.cgi?id=153022=edit ktimetracker.ics SUMMARY Close program, open program, no data loaded. STEPS TO REPRODUCE 1. Add some tasks and their time 2. Quit program 3. Open program OBSERVED RESULT No tasks EXPECTED RESULT Tasks are still there SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION ics file included for reproducibility -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454290] Dolphin sometimes crashes when I close the window or one of the tabs
https://bugs.kde.org/show_bug.cgi?id=454290 Łukasz Żarnowiecki changed: What|Removed |Added CC||luk...@zarnowiecki.pl --- Comment #3 from Łukasz Żarnowiecki --- Happens to me as well Thread 43 (Thread 0x7fff5bfff6c0 (LWP 228689) "UpdateItemState"): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x75e95b26 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=0x77f8f308 > > const&)::globalMutex>) at thread/qfutex_p.h:116 #2 QtLinuxFutex::futexWait > (expectedValue=0x3, futex=...) at thread/qfutex_p.h:135 #3 lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:142 #4 QBasicMutex::lockInternal (this=0x77f8f308 > > const&)::globalMutex>) at thread/qmutex_linux.cpp:159 #5 0x75e95cbd in QMutex::lock (this=) at thread/qmutex.cpp:237 #6 0x77f3821f in QMutexLocker::QMutexLocker (m=, this=) at /usr/include/qt/QtCore/qmutex.h:238 #7 UpdateItemStatesThread::run (this=0x55f67870) at /usr/src/debug/dolphin-22.08.0/src/views/versioncontrol/updateitemstatesthread.cpp:33 #8 0x75e9a2ca in QThreadPrivate::start (arg=0x55f67870) at thread/qthread_unix.cpp:331 #9 0x75a1e78d in start_thread (arg=) at pthread_create.c:442 #10 0x75a9f8e4 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 Thread 42 (Thread 0x7fff70cc66c0 (LWP 228686) "Thread (pooled)"): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7fff70cc5a60, op=137, expected=0, futex_word=0x55db9744) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55db9744, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7fff70cc5a60, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x75a1b3af in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55db9744, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7fff70cc5a60, private=private@entry=0) at futex-internal.c:139 #3 0x75a1de64 in __pthread_cond_wait_common (abstime=0x7fff70cc5a60, clockid=1, mutex=0x55db96f0, cond=0x55db9718) at pthread_cond_wait.c:503 #4 ___pthread_cond_timedwait64 (cond=0x55db9718, mutex=0x55db96f0, abstime=0x7fff70cc5a60) at pthread_cond_wait.c:643 #5 0x75ea16d4 in QWaitConditionPrivate::wait_relative (deadline=..., this=0x55db96f0) at thread/qwaitcondition_unix.cpp:136 #6 QWaitConditionPrivate::wait (deadline=..., this=0x55db96f0) at thread/qwaitcondition_unix.cpp:144 #7 QWaitCondition::wait (this=, mutex=0x55ccbfb8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #8 0x75e9e537 in QThreadPoolThread::run (this=0x55bd2710) at thread/qthreadpool.cpp:140 #9 0x75e9a2ca in QThreadPrivate::start (arg=0x55bd2710) at thread/qthread_unix.cpp:331 #10 0x75a1e78d in start_thread (arg=) at pthread_create.c:442 #11 0x75a9f8e4 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 Thread 41 (Thread 0x7fff91ffb6c0 (LWP 228685) "Thread (pooled)"): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7fff91ffaa60, op=137, expected=0, futex_word=0x55be0744) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55be0744, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7fff91ffaa60, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x75a1b3af in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55be0744, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7fff91ffaa60, private=private@entry=0) at futex-internal.c:139 #3 0x75a1de64 in __pthread_cond_wait_common (abstime=0x7fff91ffaa60, clockid=1, mutex=0x55be06f0, cond=0x55be0718) at pthread_cond_wait.c:503 #4 ___pthread_cond_timedwait64 (cond=0x55be0718, mutex=0x55be06f0, abstime=0x7fff91ffaa60) at pthread_cond_wait.c:643 #5 0x75ea16d4 in QWaitConditionPrivate::wait_relative (deadline=..., this=0x55be06f0) at thread/qwaitcondition_unix.cpp:136 #6 QWaitConditionPrivate::wait (deadline=..., this=0x55be06f0) at thread/qwaitcondition_unix.cpp:144 #7 QWaitCondition::wait (this=, mutex=0x55ccbfb8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #8 0x75e9e537 in QThreadPoolThread::run (this=0x55be06c0) at thread/qthreadpool.cpp:140 #9 0x75e9a2ca in QThreadPrivate::start (arg=0x55be06c0) at thread/qthread_unix.cpp:331 #10 0x75a1e78d in start_thread (arg=) at pthread_create.c:442 #11 0x75a9f8e4 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 Thread 40
[okular] [Bug 457367] New: Okular crashing when opening a specific pdf file
https://bugs.kde.org/show_bug.cgi?id=457367 Bug ID: 457367 Summary: Okular crashing when opening a specific pdf file Product: okular Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: skeleton0...@gmail.com Target Milestone: --- Application: okular (22.04.1) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.13-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: Okular 22.04.1 is crashing only when opening a specific pdf file. I can't send the pdf file as it contains many private data, but as far as I can describe it, it's an invoice of a bought product from a shop. It contains text with different formating, picture and a table. It doesn't contain any electronic signature or any specific metadata as far as I can tell. I am sending a picture of some data collected by chromium browser of this pdf file under this link: https://imgur.com/0qaJkKi The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Aborted [KCrash Handler] #4 0x7f55df6adc4c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7f55df65d9c6 in raise () from /lib64/libc.so.6 #6 0x7f55df6477f4 in abort () from /lib64/libc.so.6 #7 0x7f55df8c3b57 in __gnu_cxx::__verbose_terminate_handler() [clone .cold] () from /lib64/libstdc++.so.6 #8 0x7f55df8cf43c in __cxxabiv1::__terminate(void (*)()) () from /lib64/libstdc++.so.6 #9 0x7f55df8cf4a7 in std::terminate() () from /lib64/libstdc++.so.6 #10 0x7f55df8cf708 in __cxa_throw () from /lib64/libstdc++.so.6 #11 0x7f55df8c63f6 in std::__throw_logic_error(char const*) () from /lib64/libstdc++.so.6 #12 0x7f55b440cadf in SignatureHandler::getSignerName[abi:cxx11]() () from /lib64/libpoppler.so.117 #13 0x7f55b42f0c87 in FormFieldSignature::validateSignature(bool, bool, long, bool, bool) () from /lib64/libpoppler.so.117 #14 0x7f55b45b2191 in Poppler::FormFieldSignature::validate(int, QDateTime const&) const () from /lib64/libpoppler-qt5.so.1 #15 0x7f55b45b2623 in Poppler::FormFieldSignature::validate(Poppler::FormFieldSignature::ValidateOptions) const () from /lib64/libpoppler-qt5.so.1 #16 0x7f55c4072a8d in PopplerFormFieldSignature::PopplerFormFieldSignature(std::unique_ptr >) () from /usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so #17 0x7f55c4077810 in PDFGenerator::getFormFields(Poppler::Page*) [clone .constprop.0] () from /usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so #18 0x7f55c4069116 in PDFGenerator::init(QVector&, QString const&) () from /usr/lib64/qt5/plugins/okular/generators/okularGenerator_poppler.so #19 0x7f55cc1e96c8 in Okular::DocumentPrivate::openDocumentInternal(KPluginMetaData const&, bool, QString const&, QByteArray const&, QString const&) () from /lib64/libOkular5Core.so.10 #20 0x7f55cc1f5c8c in Okular::Document::openDocument(QString const&, QUrl const&, QMimeType const&, QString const&) () from /lib64/libOkular5Core.so.10 #21 0x7f55cc36a152 in Okular::Part::doOpenFile(QMimeType const&, QString const&, bool*) () from /usr/lib64/qt5/plugins/okularpart.so #22 0x7f55cc36b94d in Okular::Part::openFile() () from /usr/lib64/qt5/plugins/okularpart.so #23 0x7f55e14002d5 in KParts::ReadOnlyPartPrivate::openLocalFile() () from /lib64/libKF5Parts.so.5 #24 0x7f55e1404abf in KParts::ReadOnlyPart::openUrl(QUrl const&) () from /lib64/libKF5Parts.so.5 #25 0x7f55cc36862c in Okular::Part::openUrl(QUrl const&, bool) () from /usr/lib64/qt5/plugins/okularpart.so #26 0x55b4e8bf4f7b in Shell::openUrl(QUrl const&, QString const&) () #27 0x55b4e8bf5a25 in Shell::openDocument(QUrl const&, QString const&) () #28 0x55b4e8bef087 in main () [Inferior 1 (process 33792) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 453669] Muon asks for root password on system with sudo when trying to launch software-properties-kde, so one can't launch this utility
https://bugs.kde.org/show_bug.cgi?id=453669 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 453669] New: Muon asks for root password on system with sudo when trying to launch software-properties-kde, so one can't launch this utility
https://bugs.kde.org/show_bug.cgi?id=453669 Bug ID: 453669 Summary: Muon asks for root password on system with sudo when trying to launch software-properties-kde, so one can't launch this utility Product: muon Version: 5.8.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: muon Assignee: unassigned-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: echidna...@kubuntu.org, silh...@gmail.com Target Milestone: --- SUMMARY Muon asks for root password on system with sudo when trying to launch software-properties-kde, so one can't launch this utility. It does that even when root account is locked. STEPS TO REPRODUCE 1. Launch Muon 2. Go to settings -> Configure software sources 3. Observe that Muon launches KDE su. When I try to provide my own password (because root account is locked and I have sudo configured), I can't launch software-properties-kde OBSERVED RESULT One can't launch software-properties-kde from Muon EXPECTED RESULT One can launch software-properties-kde from Muon SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.16.19-76051619-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION Kubuntu backports PPA enabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413499] The sorting method and placement of desktop icons get reset after changing sorting method to Manual from anything else
https://bugs.kde.org/show_bug.cgi?id=413499 --- Comment #8 from Łukasz Konieczny --- Unfortunately, the bug still exists in Plasma 5.24.5. Icons are moved from their positions when bottom panel appears after login. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453174] New: Dolphin crash on exit
https://bugs.kde.org/show_bug.cgi?id=453174
Bug ID: 453174
Summary: Dolphin crash on exit
Product: dolphin
Version: 22.04.0
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: luk...@zarnowiecki.pl
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (22.04.0)
(Compiled from sources)
Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.17.4-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I closed dolphin and it did crash. I had two tabs open. One tab had opened a
directory which no longer existed.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Dolphin (dolphin), signal: Bus error
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#6 QHashNode::same_key (key0=...,
h0=1158673663, this=0x7f924d5b362b) at /usr/include/qt/QtCore/qhash.h:156
#7 QHash::findNode
(this=this@entry=0x557650494c28, akey=..., h=1158673663) at
/usr/include/qt/QtCore/qhash.h:931
#8 0x7f96300cbc4a in QHash::findNode (ahp=0x0, akey=...,
this=0x557650494c28) at /usr/include/qt/QtCore/qhash.h:950
#9 QHash::contains (akey=...,
this=0x557650494c28) at /usr/include/qt/QtCore/qhash.h:920
#10 FileViewGitPlugin::beginRetrieval (this=0x7f95eccc5608, directory=...) at
/usr/src/debug/dolphin-plugins-22.04.0/git/fileviewgitplugin.cpp:242
#11 0x7f964180676a in UpdateItemStatesThread::run (this=0x557650336f60) at
/usr/src/debug/dolphin-22.04.0/src/views/versioncontrol/updateitemstatesthread.cpp:36
#12 0x7f963f7898cc in QThreadPrivate::start (arg=0x557650336f60) at
thread/qthread_unix.cpp:331
#13 0x7f963f3025c2 in start_thread () from /usr/lib/libc.so.6
#14 0x7f963f387584 in clone () from /usr/lib/libc.so.6
Thread 25 (Thread 0x7f95ef7fe640 (LWP 135344) "Thread (pooled)"):
#1 0x7f963f301c64 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libc.so.6
#2 0x7f963f790c84 in QWaitConditionPrivate::wait_relative (deadline=...,
this=0x55764fedf300) at thread/qwaitcondition_unix.cpp:136
#3 QWaitConditionPrivate::wait (deadline=..., deadline=...,
this=0x55764fedf300) at thread/qwaitcondition_unix.cpp:144
#4 QWaitCondition::wait (this=, mutex=0x55764fcca4b8,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5 0x7f963f78db47 in QThreadPoolThread::run (this=0x55764fedcd70) at
thread/qthreadpool.cpp:140
#6 0x7f963f7898cc in QThreadPrivate::start (arg=0x55764fedcd70) at
thread/qthread_unix.cpp:331
#7 0x7f963f3025c2 in start_thread () from /usr/lib/libc.so.6
#8 0x7f963f387584 in clone () from /usr/lib/libc.so.6
Thread 24 (Thread 0x7f95f4ff9640 (LWP 135343) "Thread (pooled)"):
#1 0x7f963f301c64 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libc.so.6
#2 0x7f963f790c84 in QWaitConditionPrivate::wait_relative (deadline=...,
this=0x55764fca29f0) at thread/qwaitcondition_unix.cpp:136
#3 QWaitConditionPrivate::wait (deadline=..., deadline=...,
this=0x55764fca29f0) at thread/qwaitcondition_unix.cpp:144
#4 QWaitCondition::wait (this=, mutex=0x55764fcca4b8,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5 0x7f963f78db47 in QThreadPoolThread::run (this=0x55764fecffc0) at
thread/qthreadpool.cpp:140
#6 0x7f963f7898cc in QThreadPrivate::start (arg=0x55764fecffc0) at
thread/qthread_unix.cpp:331
#7 0x7f963f3025c2 in start_thread () from /usr/lib/libc.so.6
#8 0x7f963f387584 in clone () from /usr/lib/libc.so.6
Thread 23 (Thread 0x7f95f57fa640 (LWP 135342) "Thread (pooled)"):
#1 0x7f963f301c64 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libc.so.6
#2 0x7f963f790c84 in QWaitConditionPrivate::wait_relative (deadline=...,
this=0x55764fee3e00) at thread/qwaitcondition_unix.cpp:136
#3 QWaitConditionPrivate::wait (deadline=..., deadline=...,
this=0x55764fee3e00) at thread/qwaitcondition_unix.cpp:144
#4 QWaitCondition::wait (this=, mutex=0x55764fcca4b8,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5 0x7f963f78db47 in QThreadPoolThread::run (this=0x55764ff41c20) at
thread/qthreadpool.cpp:140
#6 0x7f963f7898cc in QThreadPrivate::start (arg=0x55764ff41c20) at
thread/qthread_unix.cpp:331
#7 0x7f963f3025c2 in start_thread () from /usr/lib/libc.so.6
#8 0x7f963f387584 in clone () from /usr/lib/libc.so.6
Thread 22 (Thread 0x7f95ee7fc640 (LWP 135341) "Thread (pooled)"):
#1 0x7f963f301c64 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libc.so.6
#2 0x7f963f790c84 in QWaitConditionPrivate::wait_relative (deadline=...,
this=0x55764ff452b0) at thread/qwaitcondition_unix.cpp:136
#3
[kdeplasma-addons] [Bug 352346] Description and options for Hunyango and Haenau wallpaper types are missing
https://bugs.kde.org/show_bug.cgi?id=352346 Łukasz Żarnowiecki changed: What|Removed |Added CC|luk...@zarnowiecki.pl | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446674] In Wayland with fractional scaling fonts and images are blurry from downscaling
https://bugs.kde.org/show_bug.cgi?id=446674 Łukasz Żarnowiecki changed: What|Removed |Added CC||luk...@zarnowiecki.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #10 from Łukasz Konieczny --- It seems like this bug can be overcome by editing bottom panel, for example I have changed application launcher from Kickoff to old Kickoff variant downloaded via Get Hot New Stuff. Now I have tried to logout and login several times and sometimes icons move to the top but immediately return to their position. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444409] When you call the menu with the right button in the workrave program, Plasma consumes 100% of the CPU
https://bugs.kde.org/show_bug.cgi?id=09 Łukasz Żarnowiecki changed: What|Removed |Added CC||luk...@zarnowiecki.pl --- Comment #1 from Łukasz Żarnowiecki --- I have the same problem with plasma 5.23.2 and workrave 1.10.48. It does not happen all the time, but when you close workrave window, reopen from tray it would render plasma unusable and only sddm restart can help. It used to work fine with plasma < 5.23 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444490] "Login" column doesn't show usernames
https://bugs.kde.org/show_bug.cgi?id=90 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 444490] New: "Login" column doesn't show usernames
https://bugs.kde.org/show_bug.cgi?id=90 Bug ID: 90 Summary: "Login" column doesn't show usernames Product: plasma-systemmonitor Version: 5.23.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 142941 --> https://bugs.kde.org/attachment.cgi?id=142941=edit Screenshot of Plasma Systemmonitor SUMMARY If enabled, "login" column shows no usernames of owners of processess. STEPS TO REPRODUCE 1. Enable "login" column in Plasma Systemmonitor. 2. Observe the effect. OBSERVED RESULT No usernames on this column. EXPECTED RESULT "Login" column contains usernames corresponding to UIDs of processess. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-7619-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION Kubuntu backports PPA enabled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #8 from Łukasz Konieczny --- (In reply to Nate Graham from comment #6) > But "Manual" is supposed to be the default setting. What did you change it > from? I have also changed "place icons in rows" to "place icons in columns", because rows is default setting in Kubuntu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 Łukasz Konieczny changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Łukasz Konieczny --- (In reply to Nate Graham from comment #6) > But "Manual" is supposed to be the default setting. What did you change it > from? At least in Kubuntu sorting desktop icons by name (directories first) is default. I have just checked it on new account. So I changed that and also changed icons size from fourth position on slider to third. I have also disabled icons preview of content. I did those things after installation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 Łukasz Konieczny changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Łukasz Konieczny --- (In reply to Nate Graham from comment #4) > Is there any chance you--at any time--changed the sorting method to > something other than "Manual" and then changed it back? If so, this may have > the same root cause as Bug 413499. I have only changed to "manual" after installation of OS, when I was adjusting settings of desktop. Since then I haven't changed anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #3 from Łukasz Konieczny --- Created attachment 142836 --> https://bugs.kde.org/attachment.cgi?id=142836=edit This is what happended after login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #2 from Łukasz Konieczny --- Created attachment 142835 --> https://bugs.kde.org/attachment.cgi?id=142835=edit My desktop settings part 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345 --- Comment #1 from Łukasz Konieczny --- Created attachment 142834 --> https://bugs.kde.org/attachment.cgi?id=142834=edit My desktop settings part 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444345] New: Frequently, but not always, files on the desktop move to the top after login
https://bugs.kde.org/show_bug.cgi?id=444345
Bug ID: 444345
Summary: Frequently, but not always, files on the desktop move
to the top after login
Product: plasmashell
Version: 5.23.1
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Desktop Containment
Assignee: notm...@gmail.com
Reporter: ftefrjbhfvas...@o2.pl
CC: plasma-b...@kde.org
Target Milestone: 1.0
Created attachment 142833
--> https://bugs.kde.org/attachment.cgi?id=142833=edit
My desktop with icons placed as I want
SUMMARY
I have some files in the ~/Desktop/ (in polish version in the ~/Pulpit/)
directory. Those files are shown on my desktop. I want them to be in place
specified by me. But many times after I login into my account, they initially
are in those places, but when bottom panel appears, they move to the top. They
change their place. My bottom panel has height of 38. In desktop settings
("Icons" section) I have those options enabled (I have polish language version,
so this is my own translation to english): "place icons in columns", "align to
the left", "arrange manually", "icons size": third from the left on slider,
"width of label": medium, "number of text lines": 2. This problem has existed
for a long time (couple of years). My screen resolution is 1920x1080, I have
only bottom panel. Screenshots of my desktop are in attachments.
STEPS TO REPRODUCE
1. Login into account in system.
2. Many times you will observe that icons move to the top after login.
OBSERVED RESULT
Icons change their place. I don't want that. I want them to be in exactly this
place I have placed them.
EXPECTED RESULT
Icons on the desktop don't change their place.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-7619-generic (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
ADDITIONAL INFORMATION
Kubuntu backports PPA enabled.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 443742] Kickoff doesn't respect order of programs set in KMenuEdit
https://bugs.kde.org/show_bug.cgi?id=443742 --- Comment #6 from Łukasz Konieczny --- (In reply to Noah Davis from comment #5) > > Weirdly, only programs in Multimedia category behave as I expect. > > I have a theory for why this may be. Please confirm that you have no > subcategories in the Multimedia category with items in them. > > My theory is that Kickoff is supposed to respect the "Always sort > applications alphabetically" setting, but it falls back to alphabetical > sorting whenever a category has subcategories with items in them. If that is > the case, we'll need to change the behavior of the Kicker models, which are > used by Kickoff. Yes, I don't have any subcategories (nested folders) in Multimedia category. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] Kickoff doesn't respect order of programs set in KMenuEdit
https://bugs.kde.org/show_bug.cgi?id=443742 --- Comment #4 from Łukasz Konieczny --- (In reply to Nate Graham from comment #3) > For apps like those, maybe you could put them all in a big top-level "Junk" > folder. Yes, I could do so, but those utilities come from various categories, so, again, nested folders could be very helpful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] Kickoff doesn't respect order of programs set in KMenuEdit
https://bugs.kde.org/show_bug.cgi?id=443742 --- Comment #2 from Łukasz Konieczny --- (In reply to Nate Graham from comment #1) > Not showing the nesting is intentional; we got user complaints that showing > the nesting required unnecessarily fiddly navigation. If you're the kind of > person who likes it, then Kicker (Application Menu) may be better for you. > > Showing apps in alphabetical order is likewise intentional, though you may > have a point. We can use the bug to track that. I think there could be apropriate configuration options in Kickoff configuration window. Nesting folders is very useful, for example one user (like myself) has many "junk" applications, which aren't "big" programs, but rather small utilities, like Bluetooth assistant, KColorChooser, KRuler, vprerex, UXTerm, ImageMagick, which register their entries in menu, but user never launches them from menu. For some reasons though the user doesn't want to remove those entries of small utilities from menu, but wants to store them in folder "Others" nested in apropriate category. The user can then hide those utilities from "big" applications, like OBS Studio, Strawberry, LibreOffice Writer or Kid3. Listing applications in order specified by user instead of alphabetical order is also useful when user wants some programs to be on top. For example I like to order programs of similar purpose near each other. In Multimedia category for example my order of applications is as follows: Strawberry -> Yarock -> Elisa -> Kid3 -> VLC media player -> mpv -> Subtitle Composer -> OBS Studio -> vokoscreenNG -> Handbrake -> K3b. As you can see, this order resembles closely such groups of programs: audio players -> tag editors -> multimedia players -> subtitle editors -> recording software -> multimedia converters -> disk burning software. That's the reason the user wouldn't want their programs be listed in alphabetical order. Conclusion. Please make configuration options for various types of users instead of hard-coding particular behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] Kickoff doesn't respect order of programs set in KMenuEdit and doesn't show nested folders of programs
https://bugs.kde.org/show_bug.cgi?id=443742 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443742] New: Kickoff doesn't respect order of programs set in KMenuEdit and doesn't show nested folders of programs
https://bugs.kde.org/show_bug.cgi?id=443742 Bug ID: 443742 Summary: Kickoff doesn't respect order of programs set in KMenuEdit and doesn't show nested folders of programs Product: plasmashell Version: 5.23.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: ftefrjbhfvas...@o2.pl CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I have set order of programs in every category using KMenuEdit and Kickoff doesn't repsect that. Instead it shows programs in every category in alphabetical order. I have had unchecked showing programs in alphabetical order in kickoff settings from the beginning. Weirdly, only programs in Multimedia category behave as I expect. Changing order of programs in KMenuEdit doesn't work. Moreover, I have folders for less important programs nested in every category. Kickoff doesn't show those folders. STEPS TO REPRODUCE Update Plasma to 5.23 OBSERVED RESULT As described above EXPECTED RESULT Nested folders are shown and I can go to them. Kickoff obeys order of programs set in KMenuEdit. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-7614-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION Kubuntu Backports PPA enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442475] Plasma crashed after unplugging USB memory stick
https://bugs.kde.org/show_bug.cgi?id=442475 --- Comment #1 from Łukasz Konieczny --- Created attachment 141797 --> https://bugs.kde.org/attachment.cgi?id=141797=edit New crash information added by DrKonqi plasmashell (5.22.5) using Qt 5.15.2 - What I was doing when the application crashed: I unplugged pendrive from computer using external drives applet. -- Backtrace (Reduced): #6 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:741 #7 std::atomic::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/atomic:523 #8 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #9 QBasicAtomicPointer::loadRelaxed() const (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:248 #10 QQmlNotifierEndpoint::connect(QObject*, int, QQmlEngine*, bool) (this=this@entry=0x56544ba586e0, source=0x56544d0618e0, sourceSignal=46, engine=0x0, doNotify=doNotify@entry=true) at qml/qqmlnotifier.cpp:122 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442475] Plasma crashed after unplugging USB memory stick
https://bugs.kde.org/show_bug.cgi?id=442475 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440424] Placing icon in lower-right-most position causes it to shift down a row when plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=440424 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl --- Comment #7 from Łukasz Konieczny --- I want to extend this bug report. I have manual placement of icons on the desktop (and, because I had to choose one from two options, I have placement of icons in columns and to the left side of the screen, but they are in reality placed manually on various places on the desktop). Plasma sometimes doesn't remember my placement of icons on the desktop after i log out and log in (or reboot). Especially it always doesn't remember my manual placement of icons, when I choose to place them to the right side of the screen, Plasma then stretches workspace beyond right side of the screen and horizontal scrollbar appears. Plasma has a HUGE problem with remembering custom position of icons on the desktop. My specification: Operating System: Kubuntu 21.04 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-7620-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics My screen resolution: 1920x1080 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426906] Attempting to change Google Calendar colour crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=426906 --- Comment #4 from Łukasz Żarnowiecki --- Created attachment 137150 --> https://bugs.kde.org/attachment.cgi?id=137150=edit New crash information added by DrKonqi kontact (5.16.3 (20.12.3)) using Qt 5.15.2 - What I was doing when the application crashed: I changed color of my nextcloud calendar. At the same time I noticed that I have calendars that have same colors. This is the reason I wanted to change color, but not sure if this useful -- Backtrace (Reduced): #4 0x7f71d95be7f5 in QColor::operator=(QColor const&) (this=0x8, color=...) at painting/qcolor.cpp:2932 #5 0x7f713d3feefc in EventViews::setResourceColor(Akonadi::Collection const&, QColor const&, QSharedPointer const&) () at /usr/lib/libKF5EventViews.so.5 #6 0x7f7196733a13 in KOHelper::setResourceColor(Akonadi::Collection const&, QColor const&) () at /usr/lib/libkorganizerprivate.so.5 [...] #8 0x7f71d902ed86 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc53d5e690, r=0x5607e5647610, this=0x5607e57101e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate(QObject*, int, void**) (sender=0x5607e570fcd0, signal_index=4, argv=argv@entry=0x7ffc53d5e690) at kernel/qobject.cpp:3886 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426906] Attempting to change Google Calendar colour crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=426906 Łukasz Żarnowiecki changed: What|Removed |Added CC||luk...@zarnowiecki.pl -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 434749] KMail crash at startup after new template
https://bugs.kde.org/show_bug.cgi?id=434749 --- Comment #2 from Łukasz Żarnowiecki --- Looks like it's a nvidia driver issue. But I'm not sure if this should be handled in KDE or not... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 434749] KMail crash at startup after new template
https://bugs.kde.org/show_bug.cgi?id=434749 --- Comment #1 from Łukasz Żarnowiecki --- Also in console, I have this: Qt: Session management error: Could not open network socket Error loading text-to-speech plug-in "speechd" WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed. QGLXContext: Failed to create dummy context Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) *** KMail got signal 6 (Exiting) *** Dead letters dumped. /tmp/messageviewer_attachment_Hcijon was not removed . /tmp/messageviewer_attachment_MidIox was not removed . /tmp/messageviewer_attachment_xdNgWT was not removed . and [warn] epoll_wait: Bad file descriptor repeated 10k times -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 434749] New: KMail crash at startup after new template
https://bugs.kde.org/show_bug.cgi?id=434749 Bug ID: 434749 Summary: KMail crash at startup after new template Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: luk...@zarnowiecki.pl Target Milestone: --- Application: kmail (5.16.3 (20.12.3)) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.7-arch1-1 x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I created new email template in kmail settings and then after I closed KMail it refuses to start again and always crashes with attachted backtrace. Also, kontact won't start either The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 0x7f4cf6e3aef5 in raise () at /usr/lib/libc.so.6 #5 0x7f4cf6e24862 in abort () at /usr/lib/libc.so.6 #6 0x7f4cf723a9ac in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffc267b08b0, msg=msg@entry=0x7f4cf0480008 "%s") at global/qlogging.cpp:893 #8 0x7f4cf047ab98 in QQuickWidgetPrivate::handleContextCreationFailure(QSurfaceFormat const&) (this=this@entry=0x55a397e43110, format=...) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.2/src/quickwidgets/qquickwidget.cpp:885 #9 0x7f4cf047aec0 in QQuickWidgetPrivate::createContext() (this=0x55a397e43110) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.2/src/quickwidgets/qquickwidget.cpp:917 #10 0x7f4cf047b042 in QQuickWidget::showEvent(QShowEvent*) (this=0x55a397e2dbf0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.2/src/quickwidgets/qquickwidget.cpp:1355 #11 0x7f4cf088e815 in () at /usr/lib/libQt5WebEngineWidgets.so.5 #12 0x7f4cf7f68b0e in QWidget::event(QEvent*) (this=0x55a397e2dbf0, event=0x7ffc267b0b30) at kernel/qwidget.cpp:9019 #13 0x7f4cf7f27752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55a397e2dbf0, e=0x7ffc267b0b30) at kernel/qapplication.cpp:3632 #14 0x7f4cf745fa2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a397e2dbf0, event=0x7ffc267b0b30) at kernel/qcoreapplication.cpp:1063 #15 0x7f4cf7f65338 in QWidgetPrivate::show_helper() (this=0x55a397e43110) at kernel/qwidget.cpp:7813 #16 0x7f4cf7f650ff in QWidgetPrivate::show_recursive() (this=) at kernel/qwidget.cpp:7692 #17 0x7f4cf7f6528a in QWidgetPrivate::showChildren(bool) (this=this@entry=0x55a397b9d900, spontaneous=spontaneous@entry=false) at ../../include/QtWidgets/../../src/widgets/kernel/qwidget.h:132 #18 0x7f4cf7f65312 in QWidgetPrivate::show_helper() (this=0x55a397b9d900) at kernel/qwidget.cpp:7768 #19 0x7f4cf7f650ff in QWidgetPrivate::show_recursive() (this=) at kernel/qwidget.cpp:7692 #20 0x7f4cf7f6528a in QWidgetPrivate::showChildren(bool) (this=this@entry=0x55a397be3cb0, spontaneous=spontaneous@entry=false) at ../../include/QtWidgets/../../src/widgets/kernel/qwidget.h:132 #21 0x7f4cf7f65312 in QWidgetPrivate::show_helper() (this=this@entry=0x55a397be3cb0) at kernel/qwidget.cpp:7768 #22 0x7f4cf7f6864d in QWidgetPrivate::setVisible(bool) (this=0x55a397be3cb0, visible=) at kernel/qwidget.cpp:8111 #23 0x7f4cf7f65273 in QWidgetPrivate::showChildren(bool) (this=this@entry=0x55a397b6ab90, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8183 #24 0x7f4cf7f65312 in QWidgetPrivate::show_helper() (this=this@entry=0x55a397b6ab90) at kernel/qwidget.cpp:7768 #25 0x7f4cf7f6864d in QWidgetPrivate::setVisible(bool) (this=0x55a397b6ab90, visible=) at kernel/qwidget.cpp:8111 #26 0x7f4cf7f65273 in QWidgetPrivate::showChildren(bool) (this=this@entry=0x55a397bdb430, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8183 #27 0x7f4cf7f65312 in QWidgetPrivate::show_helper() (this=this@entry=0x55a397bdb430) at kernel/qwidget.cpp:7768 #28 0x7f4cf7f6864d in QWidgetPrivate::setVisible(bool) (this=0x55a397bdb430, visible=) at kernel/qwidget.cpp:8111 #29 0x7f4cf7f65273 in QWidgetPrivate::showChildren(bool) (this=this@entry=0x55a397b1f2b0, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8183 #30 0x7f4cf7f65312 in QWidgetPrivate::show_helper() (this=this@entry=0x55a397b1f2b0) at kernel/qwidget.cpp:7768 #31 0x7f4cf7f6864d in QWidgetPrivate::setVisible(bool) (this=0x55a397b1f2b0, visible=) at kernel/qwidget.cpp:8111 #32 0x7f4cf7f65273 in QWidgetPrivate::showChildren(bool) (this=this@entry=0x55a397af6220, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8183 #33 0x7f4cf7f65312 in QWidgetPrivate::show_helper()
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #17 from Łukasz Konieczny --- (In reply to Nate Graham from comment #15) > Can't reproduce, FWIW. In both cases, the restored window moves to the > correct place. I did find one related problem while testing, however: Bug > 434116. > > I will try to fix that soon. I have to add, that in icon view I have icons of size 80 px. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #16 from Łukasz Konieczny --- (In reply to Nate Graham from comment #15) > Can't reproduce, FWIW. In both cases, the restored window moves to the > correct place. I did find one related problem while testing, however: Bug > 434116. > > I will try to fix that soon. Perhaps the initial size of window matters? Please try to shrink your Dolphin window so that you have four columns of files/directories in icon view. I have such setup and in this case I can reproduce the problem every time. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #14 from Łukasz Konieczny --- (In reply to Nate Graham from comment #13) > That's not related to this, but if you're sure it is, you can test again by > removing the "Location Bar" item from Dolphin's toolbar. I have already tested this on new account in system (in order to eliminate other factors). When location bar is in the toolbar (default since Dolphin 20.12), Dolphin behaves correctly. When location bar is not in the toolbar, but under the toolbar (that's my setting, because I like that), Dolphin doesn't return to the desired size of window. So it must be caused by placement of location bar. Or by something connected to the placement of this element of interface. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 Łukasz Konieczny changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #12 from Łukasz Konieczny --- Finally, I have found, what is causing problem. In recent version of Dolphin you have moved URL navigator into the toolbar. Please, remove the URL navigator (breadcrumbs) from the toolbar, then it will appear under the toolbar. You will see, that Dolphin doesn't return into the window size set by you, when you return from maximize state. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #11 from Łukasz Konieczny --- Because of the remainder about bug closing due to inactivity, I have posted another video, which shows this problem. Still doesn't work for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #10 from Łukasz Konieczny --- Created attachment 136437 --> https://bugs.kde.org/attachment.cgi?id=136437=edit The second video showing this behavior of Dolphin in version 20.12.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #8 from Łukasz Konieczny --- (In reply to Nate Graham from comment #7) > FWIW if your goal is to always position all windows in the center, there's a > much easier solution than using Window Rules: > > 1. Go to System Settings > Window Management > Window Behavior > Advanced > 2. Change "Window Placement" to "Centered" > 3. Uncheck "Allow apps to remember the positions of their own windows, if > they support it > > Voila! That's what I did. I was talking about that exactly. I have separate window rules, but only the ones that control size of the windows of particular programs. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 Łukasz Konieczny changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Łukasz Konieczny --- (In reply to Nate Graham from comment #4) > Hmm, seems kind of like Bug 432661, but that was fixed in Frameworks 5.79 > and yo have that. > > If you remove your window rule entirely, does Dolphin restore to the correct > position? Position is OK. I have setting to place every window in the center of the screen. But size of the window is incorrect, regardless if I have a window rule or not. So no, if I remove this rule, Dolphin still restores to incorrect size of window. But I have noticed that if size of unmaximized Dolphin window is larger, more or less larger, this problem doesn't occur. But in my case (784x616) it occurs. > If not, does it do so if you temporarily move aside your ~/.config/dolphinrc > file, restart Dolphin, and try a maximize+restore cycle again? No, it doesn't help. It only makes Dolphin loss my settings, unless I restore that file into its place. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #3 from Łukasz Konieczny --- Perhaps this problem depends on size of window. My size of Dolphin window is 784x616. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #2 from Łukasz Konieczny --- (In reply to Nate Graham from comment #1) > You can remove that window rule because Dolphin now always remembers its > window size automatically. :) I made this window rule in case I would like to temporarily change Dolphin's window size, because I want Dolphin to have the same size every time I launch it. > If you don't want to remove the window rule, you need to make use of the > window rule setting to override the app's own window geometry by also adding > an "Ignore Requested Geometry: Yes" property to your window rule. This is > made clearer in Plasma 5.21 when you create a window rule with with Size: > property. I checked if it is true, and no. I removed the window rule and yes, Dolphin remembers its size, unless I maximize its window. When I maximize and return from maximization, Dolphin sets window size to this size, which I have shown in video. I have tried everything, also setting "Ignore Requested Geometry: Yes", and it doesn't work. Dolphin is still stubborn and after returning from maximization it sets its size to this fixed value, which I don't want. I think there is either problem with Dolphin respecting Plasma's settings, or someone hard-coded this unwanted window size into Dolphin. Or some another problem, which I don't know. And still there is problem with "Places" panel on the left side of the window, which changes width after returning from maximization. I don't want this behavior either. Older version of Dolphin (20.08) didn't have those problems. Thank you in advance for your help! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] New: Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 Bug ID: 433230 Summary: Dolphin window doesn't return to size set by user after returning from maximize state Product: dolphin Version: 20.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 135893 --> https://bugs.kde.org/attachment.cgi?id=135893=edit Video showing strange behavior of Dolphin after returning from maximization of window SUMMARY I have set size of Dolphin window in window rules in order to have Dolphin window of the same size every time I create a window of this program. But when I maximize the window of Dolphin and return from maximization, Dolphin sets window size to its own size and doesn't respect my own settings. Moreover, "places" pane on the left is shrunk. This behavior is shown in attached video made using vokoscreenNG. Other KDE programs behave correctly, only Dolphin behaves this way. STEPS TO REPRODUCE 1. Set window size of Dolphin in System Settings and set it to be applied when new window is created. 2. Launch Dolphin. 3. Maximize its window. 4. Return from maximization. OBSERVED RESULT Dolphin doesn't respect user settings. EXPECTED RESULT Dolphin window has the same size as it has before maximization. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432856] Can't reopen remote files using common "File, Open recent" menu option
https://bugs.kde.org/show_bug.cgi?id=432856 Łukasz Szeremeta changed: What|Removed |Added CC||better...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 --- Comment #33 from Łukasz Szeremeta --- (In reply to Igor from comment #31) > This is a strange bug. Once more, i have the dolphin crash after using > search. > > The dolphin also crashed at startup every time. > > Then I downloaded some file and clicked "open folder" from the browser > interface. > > And the the dolphin started working! Thanks, this works for me too :-) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 --- Comment #29 from Łukasz Szeremeta --- (In reply to Nate Graham from comment #26) > ~/.config/dolphinrc. Delete the line that starts with "State=" Thanks Nate for quick answer. I did that but something keep adding State with previous value. Before my question, I changed the name of this file to force a new, clean one and the problem continued. Now I removed this line, rename file again and the State with the previous value is also added there. I have tried to run Dolphin in different ways (including via the terminal with the given path) and it is the same problem all the time. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 --- Comment #25 from Łukasz Szeremeta --- (In reply to Igor from comment #17) > This method helped me. Try not just to call the Dolphin. Try to open > some directory, for example: > > `dolphin /home/username/Downloads`. Unfortunately it doesn't help me because I have keep session on (default for KDE Neon now). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429628] Dolphin Crashes on Start
https://bugs.kde.org/show_bug.cgi?id=429628 Łukasz Szeremeta changed: What|Removed |Added CC||better...@gmail.com --- Comment #24 from Łukasz Szeremeta --- Where does Dolphin keep session information? I would like to run Dolphin without any tabs to temporarily fix the problem while waiting for a fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430197] KWin crashed when I used hot corner to present all windows in virtual desktop
https://bugs.kde.org/show_bug.cgi?id=430197 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430197] New: KWin crashed when I used hot corner to present all windows in virtual desktop
https://bugs.kde.org/show_bug.cgi?id=430197 Bug ID: 430197 Summary: KWin crashed when I used hot corner to present all windows in virtual desktop Product: kwin Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- Application: kwin_x11 (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-31-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: I used top-right hot corner to present all 34 windows in one of my four virtual desktops, then I again used this hot corner to switch off all windows view and KWin crashed (but reopened immediately). All of those windows were Gwenview instances. Just when I was writing this bug report, I did the same thing and it happened again. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x7f16d7ee34ee in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x5607635d2970, e=0x7f16c80473f0) at /usr/include/c++/10/bits/stl_algobase.h:1975 #7 0x7f16d6b5b4ef in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=, eventType=..., message=message@entry=0x7f16c80473f0, result=result@entry=0x7ffd5ab17648) at kernel/qabstracteventdispatcher.cpp:488 #8 0x7f16d0634505 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x5607634c4770, event=event@entry=0x7f16c80473f0) at qxcbnativeinterface.h:101 #9 0x7f16d0635a46 in QXcbConnection::processXcbEvents(QFlags) (this=0x5607634c4770, flags=...) at qxcbconnection.cpp:1029 #10 0x7f16d0658740 in QXcbUnixEventDispatcher::processEvents(QFlags) (this=0x5607635143f0, flags=...) at qxcbeventdispatcher.cpp:61 #11 0x7f16d6b5ca4b in QEventLoop::exec(QFlags) (this=this@entry=0x7ffd5ab17790, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #12 0x7f16d6b64fc6 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #13 0x560762d25a6d in main(int, char**) (argc=, argv=0x7ffd5ab17a18) at ./main_x11.cpp:479 [Inferior 1 (process 1242) detached] Possible duplicates by query: bug 430180, bug 430028, bug 429938, bug 429202, bug 428975. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 --- Comment #5 from Łukasz Konieczny --- (In reply to Nikita Sirgienko from comment #4) > About crashing problem - I don't know, how to fix it, because crash appears > in Qt code, and I even don't know why it goes there in first place. > But there is a good news - crash will apears only, when Cantor can't use > Sage. So, for example, the problem don't appears with Sage 9.1, because > Cantor works with this version. > And after script fix - the problems will gone for Sage 9.2 too. > So, this problem is on low priority, and because it appears very rarely and > depends from another bug - i will set status as LATER. OK. Thank you very much for help and explanation. Regards. Łukasz Konieczny -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 428813] Not possible to open app
https://bugs.kde.org/show_bug.cgi?id=428813 --- Comment #2 from Łukasz --- (In reply to Alexander Semke from comment #1) > To unblock you now, open the file > C:\Users\\AppData\Local\labplot2rc in the text editor, > locate the line with 'geometry' (must be in the [MainWin] section) and > remove it. Save the file and start LabPlot again. > > We'll check how to fix this problem. Thank you very much, it helped! -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 428813] New: Not possible to open app
https://bugs.kde.org/show_bug.cgi?id=428813 Bug ID: 428813 Summary: Not possible to open app Product: LabPlot2 Version: 2.8.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: misiekka6...@gmail.com Target Milestone: --- SUMMARY LabPlot won't open again (only first loading window) after closing from full screen mode with alt+f4 STEPS TO REPRODUCE 1. Use full screen mode. 2. Close app with ALT+F4. 3. Try opening app. OBSERVED RESULT Not possible to open app again EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428535] Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 --- Comment #6 from Łukasz Konieczny --- Perhaps the problem is caused by tree view mode. I wrote that problem occurs no matter which view mode I choose. But I had initially tree view mode. When I set view to icon view mode and threw those files to trash, they were not duplicated. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428535] Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 --- Comment #5 from Łukasz Konieczny --- I have thrown 7.4 GiB of data into trash. Dolphin duplicates files in trash and crashes even when I go back from trash to earlier directory. @Christoph Feck [[[Duplicate entries where also seen by other reporters; might be caused by the Tree view mode. Do you use this?]]] No matter which view mode I use, Dolphin shows duplicated files in trash. I have thrown 3 files, Dolphin shows 6. @Méven Car [[[Is there double files in ~/.local/share/Trash/info/ as well compared to the trash "real" content in "~/.local/share/Trash/files" ?]]] In both directories mentioned by you I have now 3 files. There is everything OK. Dolphin only erratically shows 6 files in trash:/ Moreover, Dolphin doesn't show duplicated files every time. It only shows duplicated files every time I move to trash some large files. Now I have thrown to trash three files which are 7.4 GiB in total. Dolphin showed them duplicated, then crashed when I went back to earlier directory. When I launched Dolphin once again, those files in trash were not duplicated. I could then empty the trash successfully. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428535] Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 --- Comment #2 from Łukasz Konieczny --- I don't have any idea. Perhaps Dolphin has problems if there are too large files in trash? I had some large files then and total amount of used space in trash was around 400 MiB. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 --- Comment #2 from Łukasz Konieczny --- Looks like only Sage tabs crash on closing. I have tried Maxima and it works fine. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 Łukasz Konieczny changed: What|Removed |Added Version|unspecified |20.08 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 428611] New: Cantor crashes after closing tab with working Sage
https://bugs.kde.org/show_bug.cgi?id=428611 Bug ID: 428611 Summary: Cantor crashes after closing tab with working Sage Product: cantor Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- Application: cantor (20.08.2) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-26-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: I tried to use Sage 9.2 installed in /opt/SageMath/ and symlinked in /usr/bin/. Sage doesn't work in Cantor after all (but works in terminal), but the biggest problem is that Cantor crashes when I click to close tab with worksheet. It happens every time. - Custom settings of the application: I have manually installed Sage in /opt/ (vanilla version downloaded from Sage website). The crash can be reproduced every time. -- Backtrace: Application: Cantor (cantor), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x in ?? () #7 0x7fa3fb7732e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd9a19d250, r=0x55b9698c8db0, this=0x55b969a58f70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x55b9698e6110, signal_index=7, argv=0x7ffd9a19d250) at kernel/qobject.cpp:3870 #9 0x7fa3fb7732e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd9a19d390, r=0x55b96a0d2790, this=0x55b96a2aafb0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x55b96989d350, signal_index=8, argv=argv@entry=0x7ffd9a19d390) at kernel/qobject.cpp:3870 #11 0x7fa3fb76d068 in QMetaObject::activate (sender=sender@entry=0x55b96989d350, m=m@entry=0x7fa3fcdb42c0 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7ffd9a19d390) at kernel/qobject.cpp:3930 #12 0x7fa3fcd77cf5 in Cantor::Expression::statusChanged (this=this@entry=0x55b96989d350, _t1=, _t1@entry=Cantor::Expression::Interrupted) at ./obj-x86_64-linux-gnu/src/lib/cantorlibs_autogen/EWIEGA46WW/moc_expression.cpp:249 #13 0x7fa3fcd7db8c in Cantor::Expression::setStatus (this=0x55b96989d350, status=Cantor::Expression::Interrupted) at ./src/lib/expression.cpp:206 #14 0x7fa3f009ece5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends/cantor_sagebackend.so #15 0x7fa3f009f149 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends/cantor_sagebackend.so #16 0x7fa3deafded0 in Worksheet::~Worksheet (this=0x55b9698e6110, __in_chrg=) at ./src/worksheet.cpp:119 #17 0x7fa3deafe08d in Worksheet::~Worksheet (this=0x55b9698e6110, __in_chrg=) at ./src/worksheet.cpp:107 #18 0x7fa3fb76718e in QObjectPrivate::deleteChildren (this=this@entry=0x55b9696d4c00) at kernel/qobject.cpp:2123 #19 0x7fa3fc22fa66 in QWidget::~QWidget (this=0x55b9699460d0, __in_chrg=) at kernel/qwidget.cpp:1530 #20 0x7fa3fc22fdbd in QWidget::~QWidget (this=0x55b9699460d0, __in_chrg=) at kernel/qwidget.cpp:1408 #21 0x7fa3fcd118b7 in KParts::Part::~Part (this=0x55b9698c8db0, __vtt_parm=0x7fa3deb77638 , __in_chrg=) at /usr/include/c++/10/bits/atomic_base.h:420 #22 0x7fa3deae5a82 in CantorPart::~CantorPart (this=0x55b9698c8db0, __in_chrg=, __vtt_parm=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:53 #23 0x7fa3deae5acd in CantorPart::~CantorPart (this=0x55b9698c8db0, __in_chrg=, __vtt_parm=) at ./src/cantor_part.cpp:400 #24 0x55b967a7c6d0 in CantorShell::closeTab (this=0x55b96967cb30, index=) at ./src/cantor.cpp:483 #25 0x7fa3fb773320 in doActivate (sender=0x55b9697f0650, signal_index=8, argv=argv@entry=0x7ffd9a19d7b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #26 0x7fa3fb76d068 in QMetaObject::activate (sender=, m=m@entry=0x7fa3fc7075e0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd9a19d7b0) at kernel/qobject.cpp:3930 #27 0x7fa3fc3c23e5 in QTabWidget::tabCloseRequested (this=, _t1=) at .moc/moc_qtabwidget.cpp:333 #28 0x7fa3fb773320 in doActivate (sender=0x55b969749a30, signal_index=8, argv=argv@entry=0x7ffd9a19d8d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #29 0x7fa3fb76d068 in QMetaObject::activate (sender=, m=m@entry=0x7fa3fc706040 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd9a19d8d0) at kernel/qobject.cpp:3930 #30 0x7fa3fc3a1ff5 in QTabBar::tabCloseRequested (this=, _t1=) at .moc/moc_qtabbar.cpp:345 #31 0x7fa3fb773320 in doActivate (sender=0x55b9698d0990, signal_index=9, argv=argv@entry=0x7ffd9a19d9f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #32 0x7fa3fb76d068 in
[dolphin] [Bug 428535] Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 Łukasz Konieczny changed: What|Removed |Added CC||ftefrjbhfvas...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428535] New: Dolphin crashes when I choose to empty trash
https://bugs.kde.org/show_bug.cgi?id=428535 Bug ID: 428535 Summary: Dolphin crashes when I choose to empty trash Product: dolphin Version: 20.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ftefrjbhfvas...@o2.pl CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.2) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-26-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: I went to Trash where I had about 400 MiB of data and attempted to empty the Trash. Every item in Trash was duplicated, which I thought was strange. When I hit "Empty Trash" button, Dolphin crashed. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 QSharedDataPointer::~QSharedDataPointer (this=0x55e2e539e650, __in_chrg=) at /usr/include/c++/10/bits/atomic_base.h:333 #7 0x7fa7e91e18be in KFileItemModel::ItemData::~ItemData (this=0x55e2e539e650, __in_chrg=) at ./src/kitemviews/kfileitemmodel.h:298 #8 qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:320 #9 qDeleteAll > (c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:328 #10 KFileItemModel::slotClear (this=0x55e2e563cb90) at ./src/kitemviews/kfileitemmodel.cpp:1155 #11 0x7fa7e73e42e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffc7b51a620, r=0x55e2e563cb90, this=0x55e2e4b27040) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x55e2e55fc290, signal_index=10, argv=0x7ffc7b51a620, argv@entry=0x0) at kernel/qobject.cpp:3870 #13 0x7fa7e73de068 in QMetaObject::activate (sender=sender@entry=0x55e2e55fc290, m=m@entry=0x7fa7e8d65100 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #14 0x7fa7e8cea547 in KCoreDirLister::clear (this=this@entry=0x55e2e55fc290) at ./obj-x86_64-linux-gnu/src/core/KF5KIOCore_autogen/include/moc_kcoredirlister.cpp:460 #15 0x7fa7e8cfcb3e in KCoreDirListerCache::forgetDirs (this=this@entry=0x7fa7e8d684e0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, lister=0x55e2e55fc290) at ./src/core/kcoredirlister.cpp:490 #16 0x7fa7e8cfd31a in KCoreDirListerCache::listDir (this=0x7fa7e8d684e0 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, lister=, _u=..., _keep=, _reload=) at ./src/core/kcoredirlister.cpp:125 #17 0x7fa7e91ec382 in KFileItemModel::refreshDirectory (this=0x55e2e563cb90, url=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:118 #18 0x7fa7e9243dcf in DolphinView::reload (this=0x55e2e537d4d0) at ./src/views/dolphinview.cpp:463 #19 0x7fa7e94e68f1 in DolphinViewContainer::reload (this=0x55e2e53dfcc0) at ./src/dolphinviewcontainer.cpp:456 #20 0x7fa7e94d1662 in DolphinMainWindow::reloadView (this=0x55e2e44ccdc0) at ./src/dolphinmainwindow.cpp:805 #21 0x7fa7e73e42e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffc7b51a9f0, r=0x55e2e44ccdc0, this=0x55e2e4550b70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #22 doActivate (sender=0x55e2e453e520, signal_index=4, argv=argv@entry=0x7ffc7b51a9f0) at kernel/qobject.cpp:3870 #23 0x7fa7e73de068 in QMetaObject::activate (sender=sender@entry=0x55e2e453e520, m=m@entry=0x7fa7e8427f00 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc7b51a9f0) at kernel/qobject.cpp:3930 #24 0x7fa7e7f1f826 in QAction::triggered (this=this@entry=0x55e2e453e520, _t1=) at .moc/moc_qaction.cpp:381 #25 0x7fa7e7f22111 in QAction::activate (this=0x55e2e453e520, event=) at kernel/qaction.cpp:1161 #26 0x7fa7e8017202 in QAbstractButtonPrivate::click (this=this@entry=0x55e2e46e34f0) at widgets/qabstractbutton.cpp:909 #27 0x7fa7e8017325 in QAbstractButton::mouseReleaseEvent (this=0x55e2e470c050, e=0x7ffc7b51afc0) at widgets/qabstractbutton.cpp:1012 #28 0x7fa7e810959e in QToolButton::mouseReleaseEvent (this=, e=) at widgets/qtoolbutton.cpp:622 #29 0x7fa7e7f6730e in QWidget::event (this=0x55e2e470c050, event=0x7ffc7b51afc0) at kernel/qwidget.cpp:9033 #30 0x7fa7e7f26013 in QApplicationPrivate::notify_helper (this=, receiver=0x55e2e470c050, e=0x7ffc7b51afc0) at kernel/qapplication.cpp:3685 #31 0x7fa7e7f2b841 in QApplication::notify(QObject*, QEvent*) () at kernel/qapplication.cpp:3129 #32 0x7fa7e73ae1ca in QCoreApplication::notifyInternal2 (receiver=0x55e2e470c050, event=0x7ffc7b51afc0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #33 0x7fa7e7f2a73a in
[kcharselect] [Bug 428523] New: Make KCharSelect cover all scripts in Unicode
https://bugs.kde.org/show_bug.cgi?id=428523 Bug ID: 428523 Summary: Make KCharSelect cover all scripts in Unicode Product: kcharselect Version: 20.08 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: cf...@kde.org Reporter: ftefrjbhfvas...@o2.pl Target Milestone: --- SUMMARY KCharSelect doesn't allow to use all scripts, for example egyptian hieroglyphs or vietnamese Chu Nom and many other scripts. Please make this program covering all scripts (all signs) in Unicode. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-26-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415295] Unable to receive file from phone
https://bugs.kde.org/show_bug.cgi?id=415295 Łukasz Żarnowiecki changed: What|Removed |Added CC||luk...@zarnowiecki.pl --- Comment #1 from Łukasz Żarnowiecki --- I have similar problem in logs I have when sending file from phone to computer: kdeconnectd[873]: QMetaObject::invokeMethod: No such method KIO::StoredTransferJob::slotDataReqFromDevice() -- You are receiving this mail because: You are watching all bug changes.
