[valgrind] [Bug 479842] [PATCH] syswrap-linux: improve initialisation checks for I2C_RDWR syscall
https://bugs.kde.org/show_bug.cgi?id=479842 Christian Schmidt changed: What|Removed |Added Summary|syswrap-linux: improve |[PATCH] syswrap-linux: |initialisation checks for |improve initialisation |I2C_RDWR syscall|checks for I2C_RDWR syscall -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 479842] New: syswrap-linux: improve initialisation checks for I2C_RDWR syscall
https://bugs.kde.org/show_bug.cgi?id=479842
Bug ID: 479842
Summary: syswrap-linux: improve initialisation checks for
I2C_RDWR syscall
Classification: Developer tools
Product: valgrind
Version: 3.23 GIT
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: schm...@digadd.de
Target Milestone: ---
Created attachment 164914
--> https://bugs.kde.org/attachment.cgi?id=164914=edit
Patch for improved initialisation checks for I2C_RDWR syscall
The argument structures for this syscall contain padding. The current code will
always fail, as the padding is not initialised.
The structures in question are from linux/i2c-dev.h:
struct i2c_rdwr_ioctl_data {
struct i2c_msg *msgs; /* pointers to i2c_msgs */
__u32 nmsgs;/* number of i2c_msgs */
// Padding here (on 64bit machines)
};
and from linux/i2c.h:
struct i2c_msg {
__u16 addr;
__u16 flags;
__u16 len;
// Padding here
__u8 *buf;
};
Patch to check the individual fields instead is attached.
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 467822] SMS messages are sent but not acknowledged and replies are not received on CalyxOS
https://bugs.kde.org/show_bug.cgi?id=467822 --- Comment #2 from Tony Schmidt --- Still haven't figured out whether this is an issue that should be fixed on the KDE Connect or Android ROM side, but just switched phones to FairPhone5/eOS on Android13 and now things are working fine. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475357] Regression in Dolphin 23.08.1 - Expandable folders in Details view mode broken
https://bugs.kde.org/show_bug.cgi?id=475357 Johannes Schmidt changed: What|Removed |Added CC||johannes-schm...@dorsai.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470926] Adopt "explicit apply" paradigm with Apply/Cancel buttons
https://bugs.kde.org/show_bug.cgi?id=470926 --- Comment #3 from Guido Schmidt --- I wouldn't call it plenty. Only 5 out of 70 dialogs in my system settings don't have an Apply button. - Two of them ask if you really want to apply the changes: Global Design and Online accounts. - Game controller asks you before you start a new calibration. I think a confirmation dialog would be appropriate for autostart, too. Good to know that the button issue has been addressed, though. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472149] New: Kmail Crashed by open some mails
https://bugs.kde.org/show_bug.cgi?id=472149 Bug ID: 472149 Summary: Kmail Crashed by open some mails Classification: Applications Product: kmail2 Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@ralfschmidthamburg.de Target Milestone: --- Application: kmail (5.23.3 (23.04.3)) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 5.14.21-150400.24.66-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.4" DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: when i open a mail then kmail crashed. Only by some mails. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 0x7fb539ad8c6b in raise () at /lib64/libc.so.6 #5 0x7fb539ada305 in abort () at /lib64/libc.so.6 #6 0x7fb539f46735 in () at /usr/lib64/libstdc++.so.6 #7 0x7fb539f51dbc in () at /usr/lib64/libstdc++.so.6 #8 0x7fb539f50e29 in () at /usr/lib64/libstdc++.so.6 #9 0x7fb539f51546 in __gxx_personality_v0 () at /usr/lib64/libstdc++.so.6 #10 0x7fb539c99654 in () at /lib64/libgcc_s.so.1 #11 0x7fb539c99d11 in _Unwind_RaiseException () at /lib64/libgcc_s.so.1 #12 0x7fb539f5207b in __cxa_throw () at /usr/lib64/libstdc++.so.6 #13 0x7fb539f48fef in std::__throw_length_error(char const*) () at /usr/lib64/libstdc++.so.6 #14 0x7fb52547b546 in std::__cxx11::basic_string, std::allocator >::_M_create(unsigned long&, unsigned long) (__old_capacity=0, this=0x55a0ab17f3e0, __capacity=: ) at /usr/include/c++/7/bits/basic_string.tcc:138 #15 std::__cxx11::basic_string, std::allocator >::_M_construct(char*, char*, std::forward_iterator_tag) (__end=0xcac30d002081 , __beg=0x2081 , this=0x55a0ab17f3e0) at /usr/include/c++/7/bits/basic_string.tcc:219 #16 std::__cxx11::basic_string, std::allocator >::_M_construct_aux(char*, char*, std::__false_type) (__end=0xcac30d002081 , __beg=, this=0x55a0ab17f3e0) at /usr/include/c++/7/bits/basic_string.h:236 #17 std::__cxx11::basic_string, std::allocator >::_M_construct(char*, char*) (__end=0xcac30d002081 , __beg=, this=0x55a0ab17f3e0) at /usr/include/c++/7/bits/basic_string.h:255 #18 std::__cxx11::basic_string, std::allocator >::basic_string(std::__cxx11::basic_string, std::allocator > const&) (__str=, this=0x55a0ab17f3e0) at /usr/include/c++/7/bits/basic_string.h:440 #19 ZXing::DecodeHints::characterSet[abi:cxx11]() const (this=) at /usr/src/debug/zxing-cpp-1.2.0-9.7.1.x86_64/core/src/DecodeHints.h:92 #20 ZXing::QRCode::Reader::Reader(ZXing::DecodeHints const&) (this=0x55a0ab17f3d0, hints=) at /usr/src/debug/zxing-cpp-1.2.0-9.7.1.x86_64/core/src/qrcode/QRReader.cpp:36 #21 0x7fb525406a99 in ZXing::MultiFormatReader::MultiFormatReader(ZXing::DecodeHints const&) (this=0x7ffda06c62b0, hints=...) at /usr/src/debug/zxing-cpp-1.2.0-9.7.1.x86_64/core/src/MultiFormatReader.cpp:44 #22 0x7fb525408d27 in ZXing::ReadBarcode(ZXing::GenericLuminanceSource&&, ZXing::DecodeHints const&) (source=..., hints=...) at /usr/src/debug/zxing-cpp-1.2.0-9.7.1.x86_64/core/src/ReadBarcode.cpp:35 #23 0x7fb5254090d9 in ZXing::ReadBarcode(ZXing::ImageView const&, ZXing::DecodeHints const&) (iv=..., hints=...) at /usr/src/debug/zxing-cpp-1.2.0-9.7.1.x86_64/core/src/ReadBarcode.cpp:64 #24 0x7fb4a589eb05 in zxingReadBarcode(QImage const&, ZXing::DecodeHints const&) (img=..., hints=...) at /usr/src/debug/kitinerary-23.04.3-lp154.177.1.x86_64/src/lib/barcodedecoder.cpp:211 #25 0x7fb4a589ee8e in KItinerary::BarcodeDecoder::decodeZxing(QImage const&, QFlags, KItinerary::BarcodeDecoder::Result&) const (this=, img=..., format=..., result=...) at /usr/src/debug/kitinerary-23.04.3-lp154.177.1.x86_64/src/lib/barcodedecoder.cpp:230 #26 0x7fb4a589f4fe in KItinerary::BarcodeDecoder::decodeBinary(QImage const&, QFlags) const (this=0x55a0ab1720e0, img=..., hint=...) at /usr/src/debug/kitinerary-23.04.3-lp154.177.1.x86_64/src/lib/barcodedecoder.cpp:54 #27 0x7fb4a586c306 in KItinerary::BarcodeDocumentProcessorHelper::expandNode(QImage const&, QFlags, KItinerary::ExtractorDocumentNode&, KItinerary::ExtractorEngine const*) (img=..., barcodeHints=..., parent=..., engine=0x7ffda06c6a30) at /usr/src/debug/kitinerary-23.04.3-lp154.177.1.x86_64/src/lib/processors/barcodedocumentprocessorhelper.cpp:20 #28 0x7fb4a5873bc0 in KItinerary::ImageDocumentProcessor::expandNode(KItinerary::ExtractorDocumentNode&, KItinerary::ExtractorEngine const*) const (this=, engine=0x7ffda06c6a30, node=...) at /usr/src/debug/kitinerary-23.04.3-lp154.177.1.x86_64/src/lib/processors/imagedocumentprocessor.cpp:46 #29 KItinerary::ImageDocumentProcessor::expandNode(KItinerary::ExtractorDocumentNode&, KItinerary::ExtractorEngine const*)
[systemsettings] [Bug 470926] New: Autostart has no apply/cancel buttons / changes take effect immediately
https://bugs.kde.org/show_bug.cgi?id=470926 Bug ID: 470926 Summary: Autostart has no apply/cancel buttons / changes take effect immediately Classification: Applications Product: systemsettings Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: plasma-b...@kde.org Reporter: gu...@sanguepreto.de CC: nicolas.fe...@gmx.de Target Milestone: --- SUMMARY I wanted to inspect an autostart entry in my list that didn't have a name. Not sure what that horizontal line at the end meant, I clicked it, only to discover I just had removed the entry. (BTW: Who thinks it's a good idea to hide the button until you hover it?) Well, I didn't press the apply button yet, so nothing to worry, right? Wrong. Entry gone. STEPS TO REPRODUCE 1. Click the minus button of an entry. OBSERVED RESULT 2. See the entry disappear. 3. Find out there are no apply/cancel buttons. EXPECTED RESULT Find apply and cancel button like in the other settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleweed KDE Plasma Version: 5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469682] New: Digikam crashes randomly
https://bugs.kde.org/show_bug.cgi?id=469682 Bug ID: 469682 Summary: Digikam crashes randomly Classification: Applications Product: digikam Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: hernan.hy...@gmail.com Target Milestone: --- Application: digikam (8.0.0-beta1) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-20-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Digikam is randomly crashing, I've tried to find a pattern to know what's causing it, but it seems to occur randomly. First time it crashed after I click on "Accept" after disabling the showing of the date in icon view. After that it worked ok. Later it crashed for no apparent reason, when I clicked on a file then, after restarting, it worked as intended after clicking that same file. And then crashed again when clicking the caption field of another picture. I'm sorry I can't be more specific, but I honestly have no idea what's causing this behavior. It just seems to crash randomly throughout the day. The crash can be reproduced sometimes. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 0x7f89f4ef093e in QObject::removeEventFilter(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f89f350b29a in Sonnet::SpellCheckDecorator::~SpellCheckDecorator() () from /lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 #6 0x7f89f350b2cd in Sonnet::SpellCheckDecorator::~SpellCheckDecorator() () from /lib/x86_64-linux-gnu/libKF5SonnetUi.so.5 #7 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f89f6ac92cd in Digikam::DTextEdit::~DTextEdit() () from /usr/lib/digikam/libdigikamcore.so.8.0.0 #10 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f89f5baa8cd in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f89f5baa8cd in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f89f7a2b4fb in ?? () from /usr/lib/digikam/libdigikamgui.so.8.0.0 #19 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f89f5d266bd in QStackedWidget::~QStackedWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f89f5d49f7d in QTabWidget::~QTabWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f89f5baa8cd in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f89f7a25f2b in ?? () from /usr/lib/digikam/libdigikamgui.so.8.0.0 #31 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7f89f6af2631 in ?? () from /usr/lib/digikam/libdigikamcore.so.8.0.0 #34 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f89f5baa586 in QWidget::~QWidget() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x7f89f6b1312d in Digikam::DConfigDlgWdg::~DConfigDlgWdg() () from /usr/lib/digikam/libdigikamcore.so.8.0.0 #37 0x7f89f4ee58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7f89f5baa586 in QWidget::~QWidget() () from
[umbrello] [Bug 468728] ERD lost foreign keys when loaded again
https://bugs.kde.org/show_bug.cgi?id=468728 rolf Schmidt changed: What|Removed |Added CC||rattenko...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 468728] New: ERD lost foreign keys when loaded again
https://bugs.kde.org/show_bug.cgi?id=468728 Bug ID: 468728 Summary: ERD lost foreign keys when loaded again Classification: Applications Product: umbrello Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: rattenko...@gmx.net Target Milestone: --- SUMMARY Lost of foreign keys in ERdiagrams when safed and reloaded. STEPS TO REPRODUCE 1. Build a ERdiagram with 2 entities (A and B) each with an autoincrment id-field 2. Add a second record in in Entity for example as "link" as long, unsigned integer 3. Safe the diagram f.e. as "withoutFk.xmi" 4. Now link entity A as a foreign constaint into B and save as f.e. "withFk.xmi" 5. Build a diff of both xmi files to see, that the foreigen key was written in "withFK.xmi" OBSERVED RESULT When reload the "withFK.xmi" file all foreign key information is gone. When safe the file again no info about the foreign key is written - look again at a diff. EXPECTED RESULT No lost of foreign key information SOFTWARE/OS VERSIONS Linux (Debian testing) with Trinity : ADDITIONAL INFORMATION BTW. export to SQL (only) didn't work so it should not shown. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 --- Comment #14 from Johannes Schmidt --- (In reply to Andrey from comment #12) > As said above, XKB custom configuration should get applied having you put it > in proper place in HOME, and other mentioned conditions met. Even on Wayland. "and other mentioned conditions" is doing a lot of work here, but yes, putting in these environment variables to load custom keymaps/options from $XDG_CONFIG_HOME indeed works. I wasn't aware of these variables and that plasma supported them. For my use-case this is already good enough, but I'd still rather see proper config discovery being implemented. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 --- Comment #11 from Johannes Schmidt --- To further clarify: (In reply to Andrey from comment #9) > Does your custom config get applied at least? No, it doesn't get applied, since it doesn't show up in settings and thus there is no way to apply it, unless I'm completely mistaken. XKB gives me a way to add layouts and options, but no way to set them (on wayland). Something else is needed to set them. On X11 that could be manually via setxkbmap/xkbcomp or globally via xorg.conf. On Wayland that job necessarily goes to the compositor. And the compositor can't know which layout to pick on its own so it needs a way to discover user settings and allow to pick between them. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 --- Comment #10 from Johannes Schmidt --- I'm not 100% solid on this, but as far as I'm aware, even if you uncheck layout settings and options in the KCM, the only way to apply xkb settings (user or system) manually is using xkbcomp/setxkbmap in .xinitrc/.bashrc or globally via xorg.conf, which all have downsides and all require X11 to work. On Wayland, as far as I know, all xkb stuff requires the compositor (kwin) to do the work and thus discoverability to present the choices added by the user in the settings. And for that, KDE needs to either add support for libxkbregistry or otherwise parse the ~/.config/xkb/rules/evdev.xml file to discover what settings are available. And even if Wayland isn't a priority yet (which surely can't be true, but fine), can "just disable the GUI setting and do it manually somewhere outside KDE" really be the answer for a project that strives for user-friendliness, convenience and standard conformity? Correct me if I'm entirely wrong on this or missing something, But I don't see what I, as a user am supposed to do when I want to add a modified layout or options on Plasma Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467822] SMS messages are sent but not acknowledged and replies are not received on CalyxOS
https://bugs.kde.org/show_bug.cgi?id=467822 --- Comment #1 from Tony Schmidt --- Sorry, I guess I can't grok how to edit a ticket description in Bugzilla, so adding as a comment: Desktop KDEConnect Version: GSConnect 50 (Also tried with latest KDE-Connect version) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467822] New: SMS messages are sent but not acknowledged and replies are not received on CalyxOS
https://bugs.kde.org/show_bug.cgi?id=467822
Bug ID: 467822
Summary: SMS messages are sent but not acknowledged and replies
are not received on CalyxOS
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Android
OS: Unspecified
Status: REPORTED
Severity: normal
Priority: NOR
Component: android-application
Assignee: albertv...@gmail.com
Reporter: t...@opensourceit.org
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
SUMMARY
SMS messages are sent but not acknowledged and replies are not received on
Pixel 4a5g running CalyxOS 4.7.5.
STEPS TO REPRODUCE
1. Pair phone with computer.
2. Send an SMS to a contact from the computer.
OBSERVED RESULT
Messages are sent to contact but the message appears gray (unacknowledged?) in
desktop UI and replies from the contact are only received on the phone and not
the computer.
EXPECTED RESULT
Sent messages should turn black and replies from contact should be received
(tested and works on Pixel 6 running stock Android).
SOFTWARE/OS VERSIONS
Desktop OS: PopOS 22.04
Mobile OS: CalyxOS 4.7.5
Android KDE Connect 1.23.2
ADDITIONAL INFORMATION
Several warnings are posted in the attached Android logs, but I'm unsure which
warning is the primary issue or what configuration the CalyxOS system may be
missing to support the SMS message acknowledgement and receiving functions.
Some of the suspect warnings and logs include:
* W ContextImpl: Calling a method in the system process without a qualified
user: android.app.ContextImpl.sendBroadcastMultiplePermissions:1222
com.android.server.TelephonyRegistry.broadcastServiceStateChanged:3085
com.android.server.TelephonyRegistry.notifyServiceStateForPhoneId:1616
com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact:492
android.os.Binder.execTransactInternal:1285
* W BroadcastQueue: Permission Denial: receiving Intent {
act=android.intent.action.SERVICE_STATE flg=0x110 (has extras) } to
ProcessRecord{df2db07 2591:com.android.systemui/u0a171} (pid=2591, uid=10171)
requires android.permission.ACCESS_FINE_LOCATION due to sender android (uid
1001)
* I QImsService: ImsSmsImpl : onSendSmsResult:: token:6 smsResponse:{
mMessageRef = 6, mSendSmsResult = 1, mSendSmsReason = 0, mNetworkErrorCode =
-1}
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 Johannes Schmidt changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Johannes Schmidt --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 Johannes Schmidt changed: What|Removed |Added CC||johannes-schm...@dorsai.eu --- Comment #6 from Johannes Schmidt --- Is there any progress on this? I just tried to add my own layout as per the official documentation (https://xkbcommon.org/doc/current/md_doc_user_configuration.html) and it doesn't show up in systemsettings. This seams somewhat important for wayland support because the old X11 way of using .xmodmap is no longer available to use for user configuration. Libxkbcommon is now the only way to modify/define layouts and libxkbregistry is the only way to dynamically add user configuration. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 467501] New: missing variables after import of python file
https://bugs.kde.org/show_bug.cgi?id=467501 Bug ID: 467501 Summary: missing variables after import of python file Classification: Applications Product: umbrello Version: 2.33.2 (KDE releases 20.12.2) Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: umbrello-de...@kde.org Reporter: rattenko...@gmx.net Target Milestone: --- Created attachment 157367 --> https://bugs.kde.org/attachment.cgi?id=157367=edit files for reproduce the bug SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. import the py-file from the attachment in umbrello. 2. You will see the the class view as shown in the image in the attachment. OBSERVED RESULT In the class view is one of the self.-variable from the program file missing. Exporting the source code from the class view shows the correct list of variables. EXPECTED RESULT find all variable in the class view. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Trinity 14x: (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.
[Discover] [Bug 466702] Discover crashes at start after failed offline-update
https://bugs.kde.org/show_bug.cgi?id=466702 --- Comment #1 from Olaf Jan Schmidt --- When the next updates were available, Discover was able to launch normally. After performing this next offline update, everything is back to normal again. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466702] New: Discover crashes at start after failed offline-update
https://bugs.kde.org/show_bug.cgi?id=466702 Bug ID: 466702 Summary: Discover crashes at start after failed offline-update Classification: Applications Product: Discover Version: 5.27.2 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ojschm...@kde.org CC: aleix...@kde.org Target Milestone: --- Discover crashes during launch after installing an offline-update was interrupted because of an empty battery. The system was installing a kernel update, which I then repaired by calling `sudo dpkg --configure -a`. Qt Version: 5.15.8 Frameworks Version: 5.103.0 The crash might be related to bug 463768 (or not). It is certainly related to a broken pkcon status: > pkcon repair [=] Testing changes [=] Finished [=] [=] Waiting for authentication[=] Loading cache [=] Running [=] Finished [=] > pkcon offline-status Status: Failed ErrorCode:failed-initialization ErrorDetails:The transaction did not complete > sudo pkcon offline-trigger Command failed: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code1: Prepared update not found: /var/lib/PackageKit/prepared-update > pkcon refresh Refreshing cache [=] Loading cache [=] Downloading packages [=] Running [=] Finished [=] > pkcon get-updates Getting updates [=] Loading cache [=] Finished [=] There are no updates available at this time. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f21e4073ddc in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #5 0x7f21e4074390 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #6 0x7f21e4077d3f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #7 0x7f21e407c11d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #8 0x7f22006e9ade in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f220216c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f22006bc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f22006bf167 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2200716487 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f21ff051d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f21ff0a66c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f21ff04f3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f2200715ad8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f22006ba99b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f22006c2f34 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x55d03c6d5c63 in ?? () #20 0x7f21ffc29d90 in __libc_start_call_main (main=main@entry=0x55d03c6d5340, argc=argc@entry=1, argv=argv@entry=0x7ffce96c0418) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7f21ffc29e40 in __libc_start_main_impl (main=0x55d03c6d5340, argc=1, argv=0x7ffce96c0418, init=, fini=, rtld_fini=, stack_end=0x7ffce96c0408) at ../csu/libc-start.c:392 #22 0x55d03c6d66a5 in ?? () [Inferior 1 (process 5037) detached] -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466699] New: Dolphin crashes at start after failed offline-update
https://bugs.kde.org/show_bug.cgi?id=466699 Bug ID: 466699 Summary: Dolphin crashes at start after failed offline-update Classification: Applications Product: Discover Version: 5.27.2 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ojschm...@kde.org CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.19.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: Discover crashes during launch after installing an offline-update was interrupted because of an empty battery. The system was installing a kernel update, which I could complete by calling `sudo dpkg --configure -a`. The crash might be related to a broken pkcon status. > pkcon repair [=] Testing changes [=] Finished [=] [=] Waiting for authentication[=] Loading cache [=] Running [=] Finished [=] > pkcon offline-status Status: Failed ErrorCode:failed-initialization ErrorDetails:The transaction did not complete > sudo pkcon offline-trigger Command failed: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code1: Prepared update not found: /var/lib/PackageKit/prepared-update > pkcon refresh Refreshing cache [=] Loading cache [=] Downloading packages [=] Running [=] Finished [=] > pkcon get-updates Getting updates [=] Loading cache [=] Finished [=] There are no updates available at this time. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f21e4073ddc in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #5 0x7f21e4074390 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #6 0x7f21e4077d3f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #7 0x7f21e407c11d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #8 0x7f22006e9ade in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f220216c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f22006bc07a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f22006bf167 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2200716487 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f21ff051d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f21ff0a66c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f21ff04f3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f2200715ad8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f22006ba99b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f22006c2f34 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x55d03c6d5c63 in ?? () #20 0x7f21ffc29d90 in __libc_start_call_main (main=main@entry=0x55d03c6d5340, argc=argc@entry=1, argv=argv@entry=0x7ffce96c0418) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7f21ffc29e40 in __libc_start_main_impl (main=0x55d03c6d5340, argc=1, argv=0x7ffce96c0418, init=, fini=, rtld_fini=, stack_end=0x7ffce96c0408) at ../csu/libc-start.c:392 #22 0x55d03c6d66a5 in ?? () [Inferior 1 (process 5037) detached] The reporter indicates this bug may be a duplicate of or related to bug 463768. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466528] Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore
https://bugs.kde.org/show_bug.cgi?id=466528 --- Comment #2 from Guido Schmidt --- Thanks, that was it! I actullay saw this setting. But the German translation is so misleading that I didn't even try it: "Automatisch zur Gegenseite navigieren" which more or less translates to "Automatically navigate to the opposite side". I have to admit that I have a hard time finding a good and concise German wording. So can this be changed into a translation bug? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466528] New: Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore
https://bugs.kde.org/show_bug.cgi?id=466528 Bug ID: 466528 Summary: Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore Classification: Applications Product: systemsettings Version: 5.27.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: gu...@sanguepreto.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY Some time in fall 2022 (maybe when 5.26 landed) the shortcut that allowed me to cycle between virtual desktops does not bring me from the last to first one anymore. Imagine having three Desktops A, B and C. I used to be able to go from C to A. STEPS TO REPRODUCE 1. Configure a shortcut for "Switch to next desktop", for instance Meta+Tab. 2. Configure 3 desktops A B C. 3. Go to desktop C. 4. Hit Meta+Tab OBSERVED RESULT Nothing happens. EXPECTED RESULT Switch to desktop A. SOFTWARE/OS VERSIONS Linux: Opensuse Tumbleweed KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION "Switch to next desktop" may not be the literal name, I translated it from the German localization: "Zur nächsten Arbeitsfläche umschalten". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 384032] Get new hot stuff sorting not applied when selecting option 'most downloads'
https://bugs.kde.org/show_bug.cgi?id=384032 --- Comment #14 from Alexander Schmidt <2f5ed...@opayq.com> --- I hope what takes a long time will finally be good. I just worked on the API for another reason and tried to solve the problem described here at the same time. We have sorted by the downloads of the last 24h, but the total sum of downloads is shown in the list. This is of course confusing for the user and not helpful. We are now sorting by the total sum of downloads and I hope the result now matches what the user's expected. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 361974] Power saving settings for monitor have no effect
https://bugs.kde.org/show_bug.cgi?id=361974 Guido Schmidt changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Guido Schmidt --- Barely remember this one. No, it's working now. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453198] Switching to a pane in Details view mode results in a file opening
https://bugs.kde.org/show_bug.cgi?id=453198 --- Comment #5 from Johannes Schmidt --- (In reply to Felix Ernst from comment #4) > Can you explain why you want to switch the active pane but don't want to > click on an item or make a selection in the pane you are clicking? Just to clarify: The most relevant use-case to me is quickly changing the directory of the terminal widget to the other pane to do run a command in the directory opened in that pane. Or more generally, basically any toolbar action that only acts on a single pane, like searching, setting view mode, toggling previews, or closing the selected pane. For me personally, the solution of adding the "Leading Column Padding" was sufficient. I'm not the reporter of this duplicate issue, but for me personally all issues have been resolved with that. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #14 from Johannes Schmidt --- The biggest issue is that it's very unintuitive to have no empty space in the view that doesn't cause an action on drop or click. For example, I used to click into the empty space to select the view (in split mode) for toolbar commands or to sync the terminal directory. Now, after some adjustment period I found that I can click the scroll bar if the directory list is full. Similarly drag works same as before by dropping on the column headers instead of directly into the pane. It works and I'm starting to get used to it, but it sure as hell isn't intuitive. It took me a few seconds of trial and error to find some surface I can use to get my file where it should. Adding to the unintuitiveness of these weird usage patterns that this behavior encourages, there is also the inconsistency. For example, when clicking to the left of a file, an unfolded directory tree, or exactly between the arrows, that space still seems to have the old behavior where a click doesn't select the line. I've caught myself a few times unfolding a directory just to have a reliable space to click into. So while I would much prefer the old behavior back, I would also happily settle for a consistent, less unintuitive compromise. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 Johannes Schmidt changed: What|Removed |Added CC||johannes-schm...@dorsai.eu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453198] Switching to a pane in Details view mode results in a file opening
https://bugs.kde.org/show_bug.cgi?id=453198 --- Comment #2 from Johannes Schmidt --- (In reply to Johannes Schmidt from comment #1) > [...] and no place to right-click to create new folders or files. Sorry, I just realized that this is false, right-clicking and creating files/folder works as expected. Which in my eyes makes this even more inconsistent. Why does left-clicking and drag-dropping into empty space select/open a file/folder and right-clicking empty space does not? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453198] Switching to a pane in Details view mode results in a file opening
https://bugs.kde.org/show_bug.cgi?id=453198 --- Comment #1 from Johannes Schmidt --- This has been bothering me too. It's very counter intuitive behavior considering that in all other modes as in details mode mode, clicking the empty space just selects the pane. A related problem is that if you have a directory containing a long list of directories you have no place to drag and drop files/folders into, and no place to right-click to create new folders or files. It will always drop into or create the file inside the directory whose row is under the cursor instead of the directory displayed. In my opinion, clicking (or dragging onto) anything but the file/directory name and icon should not open the file or directory. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453198] Switching to a pane in Details view mode results in a file opening
https://bugs.kde.org/show_bug.cgi?id=453198 Johannes Schmidt changed: What|Removed |Added CC||johannes-schm...@dorsai.eu -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 452684] Please reduce the vertical space which the the color bar occupies.
https://bugs.kde.org/show_bug.cgi?id=452684 Schmidt Bay changed: What|Removed |Added CC||fuchsiaho...@disroot.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452660] Random Plasma crashes
https://bugs.kde.org/show_bug.cgi?id=452660 Stefan Schmidt changed: What|Removed |Added CC||thrimbor+kdeb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 452702] New: Curly brackets disappear on python import
https://bugs.kde.org/show_bug.cgi?id=452702
Bug ID: 452702
Summary: Curly brackets disappear on python import
Product: umbrello
Version: 2.33.2 (KDE releases 20.12.2)
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: importer
Assignee: umbrello-de...@kde.org
Reporter: rattenko...@gmx.net
Target Milestone: ---
SUMMARY
***
If python code is imported all curly brackets disappear in the attribute text.
***
STEPS TO REPRODUCE
1.
# python code
#!/usr/bin/python3
class test(object):
def abc():
xyz={'aaa':1, 'bbb':'John'}
2.
import sourcecode
3.
OBSERVED RESULT
xyz=:
'aaa':1,'bbb':'John'
EXPECTED RESULT
xyz={ 'aaa':1,'bbb':'John'}
SOFTWARE/OS VERSIONS
Devuan Chimera (i.e. debian bullseys)
GUI: Trinity
--
You are receiving this mail because:
You are watching all bug changes.
[kolourpaint] [Bug 452684] New: Please reduce the vertical space which the the color bar occupies.
https://bugs.kde.org/show_bug.cgi?id=452684 Bug ID: 452684 Summary: Please reduce the vertical space which the the color bar occupies. Product: kolourpaint Version: 22.03.80 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: fuchsiaho...@disroot.org Target Milestone: --- Created attachment 148194 --> https://bugs.kde.org/attachment.cgi?id=148194=edit A screenshot which demonstrates the amount of empty space in the color bar. SUMMARY The color bar in Koloupaint occupies an overly large amount of vertical screen real estate, including a label which tells the user the color bar is a color bar. The individual color boxes are larger than necessary and there is generally a lot of empty space. There is no way to change this in the settings. When compared to the color bar in MS paint, before and after Windows 7, it is substantially larger. EXPECTED RESULT Please include a setting that reduces how much vertical screen real-estate the color bar occupies. Smaller icons are perfectly fine for devices which have mouse support. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu Probably every other platform -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452660] New: Random Plasma crashes
https://bugs.kde.org/show_bug.cgi?id=452660 Bug ID: 452660 Summary: Random Plasma crashes Product: plasmashell Version: 5.24.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: thrimbor+kdeb...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.4) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.3-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: I'm experiencing Plasma crashes, but so far couldn't narrow it down to some specific action or situation. Today it crashed when I clicked on the icon of an open dolphin instance in the task bar, two days ago it crashed when I opened Firefox (which opens a lot of windows). These actions do not reliably reproduce the crash, and I've had crashes where I didn't even actively do anything. I've tried to install all debug symbols, but the debug dialog mentioned that the symbols for /usr/bin/plasmashell are still not there. I will try to have debuginfod ready the next time. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x70006f006f0070, this=, __m=) at /usr/include/c++/11.2.0/bits/atomic_base.h:479 #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=..., _q_value=) at /usr/include/qt/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed() const (this=0x70006f006f0070, this=) at /usr/include/qt/QtCore/qbasicatomic.h:107 #7 QWeakPointer::internalData() const (this=0x5630186a0e48) at /usr/include/qt/QtCore/qsharedpointer_impl.h:698 #8 QPointer::data() const (this=0x5630186a0e48, this=) at /usr/include/qt/QtCore/qpointer.h:77 #9 QPointer::operator QObject*() const (this=0x5630186a0e48, this=) at /usr/include/qt/QtCore/qpointer.h:83 #10 QQmlDelegateModelPrivate::destroyCacheItem(QQmlDelegateModelItem*) (this=0x563014e01b10, cacheItem=0x5630186a0e20) at /usr/src/debug/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:643 #11 0x7f86f5be1bb2 in std::function::operator()(QQmlDelegateModelItem*) const (__args#0=0x5630186a0e20, this=0x7ffefb8e8220) at /usr/include/c++/11.2.0/bits/std_function.h:560 #12 QQmlReusableDelegateModelItemsPool::drain(int, std::function) (this=0x563014e01d08, maxPoolTime=0, releaseItem=...) at /usr/src/debug/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:3821 #13 0x7f86f5bd1c6b in QQmlDelegateModelPrivate::drainReusableItemsPool(int) (maxPoolTime=, this=) at /usr/src/debug/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1118 #14 QQmlDelegateModel::drainReusableItemsPool(int) (this=, maxPoolTime=) at /usr/src/debug/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1123 #15 0x7f86f86d0f15 in QQuickListView::geometryChanged(QRectF const&, QRectF const&) (this=0x5630172220b0, newGeometry=..., oldGeometry=...) at /usr/src/debug/qtdeclarative/src/quick/items/qquicklistview.cpp:3418 #16 0x7f86f85fd530 in QQuickItem::setSize(QSizeF const&) (this=this@entry=0x5630172220b0, size=...) at /usr/src/debug/qtdeclarative/src/quick/items/qquickitem.cpp:7045 #17 0x7f86f0efd2fb in QQuickControlPrivate::resizeContent() (this=) at /usr/src/debug/qtquickcontrols2/src/quicktemplates2/qquickcontrol.cpp:402 #18 0x7f86f0efff6b in QQuickControl::geometryChanged(QRectF const&, QRectF const&) (this=0x56301619e5c0, newGeometry=..., oldGeometry=...) at /usr/src/debug/qtquickcontrols2/src/quicktemplates2/qquickcontrol.cpp: #19 0x7f86f85fd3ec in QQuickItem::setImplicitHeight(double) (this=0x56301619e5c0, h=) at /usr/src/debug/qtdeclarative/src/quick/items/qquickitem.cpp:6944 #20 0x7f86f8149b11 in QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (this=, target=, value=, flags=...) at ../../include/QtQml/5.15.3/QtQml/private/../../../../../../qtdeclarative/src/qml/qml/qqmlpropertydata_p.h:375 #21 0x7f86f819f73b in GenericBinding<6>::doStore(double, QQmlPropertyData const*, QFlags) const (flags=..., pd=, value=, this=0x563014c4e090) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:342 #22 GenericBinding<6>::write(QV4::Value const&, bool, QFlags) (this=0x563014c4e090, result=..., isUndefined=, flags=...) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:315 #23 0x7f86f81a82e6 in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x563014c4e090, watcher=..., flags=..., scope=) at /usr/src/debug/qtdeclarative/src/qml/qml/qqmlbinding.cpp:258 #24 0x7f86f81a91cc in QQmlBinding::update(QFlags) (this=0x563014c4e090, flags=...) at
[valgrind] [Bug 451827] [ppc64le] VEX temporary storage exhausted with several vbpermq instructions
https://bugs.kde.org/show_bug.cgi?id=451827 Will Schmidt changed: What|Removed |Added CC||jsew...@acm.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447995] Valgrind segfault on power10 due to hwcap checking code
https://bugs.kde.org/show_bug.cgi?id=447995 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447995] New: Valgrind segfault on power10 due to hwcap checking code
https://bugs.kde.org/show_bug.cgi?id=447995
Bug ID: 447995
Summary: Valgrind segfault on power10 due to hwcap checking
code
Product: valgrind
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: will_schm...@vnet.ibm.com
Target Milestone: ---
Created attachment 145143
--> https://bugs.kde.org/attachment.cgi?id=145143=edit
proposed patch to add clobber masks to inline asm statements
SUMMARY
***
On a Power10-based server, valgrind segfaults during initialization.
(Problem found by Tulio, investigated by Tulio and Will).
After some debug we found out that r20 is being clobbered at
coregrind/m_machine.c:1417:
__asm__ __volatile__(".long 0x7f1401b6"); /* brh RA, RS */
Preliminary patch to add clobber options to the asm stanzas is attached.
***
STEPS TO REPRODUCE
1. Run valgrind on a power10
2. observe segfault early in valgrind startup
3.
OBSERVED RESULT
segfault
EXPECTED RESULT
no segfault
SOFTWARE/OS VERSIONS
Linux on Powerpc / power10
ADDITIONAL INFORMATION
This problem has only been seen on power10, and occurs due to an instruction
only exercised on power10. But, there is potential for some of the other
inline asm to have similar side affects. Patch should address these.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 275786] disInstr(ppc): unhandled instruction: 0x10E40301
https://bugs.kde.org/show_bug.cgi?id=275786 Will Schmidt changed: What|Removed |Added CC||will_schm...@vnet.ibm.com --- Comment #3 from Will Schmidt --- disInstr(ppc): unhandled instruction: 0x10E40301 primary 4(0x4), secondary 769(0x301) This appears to map to the evldd instruction. There are references to the instruction in Power ISA version 2.07 documents (2013) under the SPE (Signal Processing Engine) category. There are no references in Power ISA version 3.0 or newer. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441534] Update test results for test_isa_3_1_VRT to match changed inputs
https://bugs.kde.org/show_bug.cgi?id=441534 --- Comment #1 from Will Schmidt --- Per some additional investigation, the changed inputs to the vinsd* tests are a side affect of changes made as part of bug 440906, which affected a modulo operation occurring on hard registers. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #99 from Guido Schmidt --- No Michael, this bug is not about kickoff only, it's about the plasmoids in general that are attached to the startmenu. For instance the folder view: It is ridiculously small, therefore shows only a few files, and only the first part of their names. And it cannot be resized. Guido 04.09.2021 23:25:22 Michael Hamilton : > https://bugs.kde.org/show_bug.cgi?id=332512 > > Michael Hamilton changed: > > What |Removed |Added > > CC| |mich...@actrix.gen.nz > > --- Comment #98 from Michael Hamilton --- > This seems to be an intractable issue (arguably showing an appalling lack of > sensibility to real-world usability in the age of 4K monitors). There is an > alternative which works quite well and the author appears focused on usability: > cupnoodle's Kickoff/Grid: https://store.kde.org/p/1317546 - I would suggest > those seeking a resizable kickoff vote with their feet, which was somewhat > officially suggested here https://forum.kde.org/viewtopic.php?f=83=170175 > > -- > You are receiving this mail because: > You voted for the bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441534] Update test results for test_isa_3_1_VRT to match changed inputs
https://bugs.kde.org/show_bug.cgi?id=441534 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||jsew...@acm.org, ||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441534] New: Update test results for test_isa_3_1_VRT to match changed inputs
https://bugs.kde.org/show_bug.cgi?id=441534 Bug ID: 441534 Summary: Update test results for test_isa_3_1_VRT to match changed inputs Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: will_schm...@vnet.ibm.com Target Milestone: --- Created attachment 141038 --> https://bugs.kde.org/attachment.cgi?id=141038=edit Proposed patch to update the vinsd* instruction test results test_isa_3_1_VRT.stdout.exp SUMMARY The inputs into the vinsdlx,vinsdrx instructions changed, and the test results were not updated to match. This addresses the issue. STEPS TO REPRODUCE 1. Run none/tests/ppc64/test_isa_3_1_VRT test case 2. See failure in expected output. 3. OBSERVED RESULT ... > -vinsdlx 4 0 => , > -vinsdlx 4 2 => ,0002 ... > +vinsdlx 6 0 => , > +vinsdlx 6 2 => ,0002 ... EXPECTED RESULT Success. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Proposed patch attached. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441512] remove troublesome block of code from guest_ppc_toIR code for pstxvp instruction
https://bugs.kde.org/show_bug.cgi?id=441512 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||jsew...@acm.org, ||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441512] New: remove troublesome block of code from guest_ppc_toIR code for pstxvp instruction
https://bugs.kde.org/show_bug.cgi?id=441512 Bug ID: 441512 Summary: remove troublesome block of code from guest_ppc_toIR code for pstxvp instruction Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: will_schm...@vnet.ibm.com Target Milestone: --- Created attachment 141023 --> https://bugs.kde.org/attachment.cgi?id=141023=edit proposed patch to remove improper R=1 check and return. SUMMARY A chunk of code was committed that should have been removed during initial development of support for the pstxvp instruction. This chunk of code prevents the emulation of the pstxvp instruction, which is showing up in current builds targeting the power10 platform. STEPS TO REPRODUCE 1. Build valgrind on/for a Power10 system. 2. Run testsuite (test_isa_3_1_XT) or other tests utilizing the pstxvp instruction. 3. OBSERVED RESULT failure. EXPECTED RESULT success. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Proposed patch attached. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441506] powerpc: Instruct the assembler to generate POWER9 instructions
https://bugs.kde.org/show_bug.cgi?id=441506 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||jsew...@acm.org, ||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440906] powerpc valgrind testsuite; update test_isa_3_1_common.c to avoid modulo against hard regs
https://bugs.kde.org/show_bug.cgi?id=440906 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||jsew...@acm.org, ||will_schm...@vnet.ibm.com Assignee|jsew...@acm.org |c...@us.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440906] powerpc valgrind testsuite; update test_isa_3_1_common.c to avoid modulo against hard regs
https://bugs.kde.org/show_bug.cgi?id=440906 --- Comment #1 from Will Schmidt --- Created attachment 140674 --> https://bugs.kde.org/attachment.cgi?id=140674=edit proposed patch to rework modulo operation -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440906] New: powerpc valgrind testsuite; update test_isa_3_1_common.c to avoid modulo against hard regs
https://bugs.kde.org/show_bug.cgi?id=440906
Bug ID: 440906
Summary: powerpc valgrind testsuite; update
test_isa_3_1_common.c to avoid modulo against hard
regs
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: will_schm...@vnet.ibm.com
Target Milestone: ---
SUMMARY
Due to a GCC issue (PR101882) seen against recent GCC builds, we
want to rework our code to avoid attempting a modulo operation
with both the input and output defined as a hard register.
ra is earlier defined as
register uint64_t ra __asm__ ("r20");
and current code attempts a
ra = ra % 9;
In this case, we can apply the modulo operation to the args[] array
value that was previously used to initialize the ra value.
ra = args[vrai] % 9;
Patch attached.
STEPS TO REPRODUCE
1. Build valgrind for power9 or power10 using a recent (~ Aug 2021) GCC.
2. See "impossible constraint" error emitted from GCC.
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.
[valgrind] [Bug 440793] Valgrind ppc64/tests/Makefile.am fixups
https://bugs.kde.org/show_bug.cgi?id=440793 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||jsew...@acm.org, ||will_schm...@vnet.ibm.com Assignee|jsew...@acm.org |c...@us.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440793] New: Valgrind ppc64/tests/Makefile.am fixups
https://bugs.kde.org/show_bug.cgi?id=440793 Bug ID: 440793 Summary: Valgrind ppc64/tests/Makefile.am fixups Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: will_schm...@vnet.ibm.com Target Milestone: --- Created attachment 140611 --> https://bugs.kde.org/attachment.cgi?id=140611=edit proposed patch for none/tests/ppc64/Makefile.am SUMMARY Correct some issues as reported with none/tests/ppc64/Makefile.am. In particular, -The wrong mcpu string is used for BUILD_FLAGS_ISA_3_00 -Indentation (tab/whitespace) glitch in EXTRA_DIST definition. -Move jm_insn_CFLAGS definition to be near other CFLAGS defines. proposed patch attached. STEPS TO REPRODUCE 1. build and run valgrind tests on a power9 target 2. observe tests being built with a mcpu=power9 cflags. 3. OBSERVED RESULT EXPECTED RESULT victory. 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.
[plasmashell] [Bug 439851] klipper removes clipboard content on mouse-click when memory size is set to 1
https://bugs.kde.org/show_bug.cgi?id=439851 --- Comment #5 from Hayo Schmidt --- (In reply to David Edmundson from comment #2) > Please can you confirm all the other settings in klipper? Please see my attachment with klipper settings. When testing that this setting really shows the effect, I saw that Copy sometimes works also with this setting. In lets say one of five cases. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439851] klipper removes clipboard content on mouse-click when memory size is set to 1
https://bugs.kde.org/show_bug.cgi?id=439851 --- Comment #4 from Hayo Schmidt --- Created attachment 140061 --> https://bugs.kde.org/attachment.cgi?id=140061=edit Screenshot of my klipper settings This attachment shows my configuration. I checked that exactly this configuration shows the error. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439851] klipper removes clipboard content on mouse-click when memory size is set to 1
https://bugs.kde.org/show_bug.cgi?id=439851 --- Comment #3 from Hayo Schmidt --- (In reply to David Edmundson from comment #1) > You can disable klipper just remove the applet. Also being overly dramatic > won't help your case. Well, I cannot remove the applet. I can just "deactivate" it. If it helps, it is OK for my personal needs. An no, I am not overly dramatic. I am sensible for other people running into the same problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439851] New: klipper removes clipboard content on mouse-click when memory size is set to 1
https://bugs.kde.org/show_bug.cgi?id=439851 Bug ID: 439851 Summary: klipper removes clipboard content on mouse-click when memory size is set to 1 Product: plasmashell Version: 5.18.6 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: bugzi...@hayo.de Target Milestone: 1.0 SUMMARY klipper does not provide the content of the clipboard after Ctrl-C, Mouse click, Ctrl-V. The trigger is that I have set the clipboard memory size (Größe des Verlaufsspeichers) to 1. If set to two, it works. STEPS TO REPRODUCE 1. Configure clipboard memory size (Größe des Verlaufsspeichers) to 1. 2. Open (for instance) in LibreOffice Calc a spreadsheet. 3. Mark one line with content. 4. Ctrl-C. (Now the LibreOffice menu provides the option to Insert). 5. Click with mouse into one of the next rows (Now the LibreOffice menu does not provide the option to Insert). OBSERVED RESULT 6. Ctrl-V. Nothing is inserted. The content is nonetheless available in klipper. If you select it there, it may be pasted again. EXPECTED RESULT The copied content must (not just should) be inserted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.2 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION Let me state that I do not need and do not want any of the features that klipper provides, and never did! In fact this peace of software, which I apparently cannot remove or disable, is a constant annoyance. In general it is a security flaw: I do not want any clipboard content other than the current one available in the system. Old copies of possibly sensitive content are a major security hole. This is why I had set the size of memory to 1 some months ago, in order to get the original behaviour of Copy which I am using for more than 35 years. klipper managed to kill one of the most basic functionalities of any OS GUI. Congratulations. You may imagine that this had an big negative impact on my work for those months, because I did not identify the root cause of this effect. BTW: If I copy the source about five times very quickly, the paste sometimes works again. It's kind of bad magic. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434840] PPC64 darn instruction not supported
https://bugs.kde.org/show_bug.cgi?id=434840 Will Schmidt changed: What|Removed |Added CC||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 Ingo Schmidt-Hammer changed: What|Removed |Added CC||ingo.schmidt-ham...@gmx.de --- Comment #54 from Ingo Schmidt-Hammer --- The bug's still turning up which means the machine consumes ernergy for nothing. May by I'm a bit naive with my workaround: Simply chosing "change user" and the load drops. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434849] The vdso is not available when running on ppc64*
https://bugs.kde.org/show_bug.cgi?id=434849 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 411189] Valgrind does not support POWER9 "DARN" RNG instructions
https://bugs.kde.org/show_bug.cgi?id=411189 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 411189] Valgrind does not support POWER9 "DARN" RNG instructions
https://bugs.kde.org/show_bug.cgi?id=411189 Will Schmidt changed: What|Removed |Added CC||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 431157] PPC_FEATURE2_SCV needs to be masked in AT_HWCAP2
https://bugs.kde.org/show_bug.cgi?id=431157 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346895] Keboard repeat settings not applied at startup time
https://bugs.kde.org/show_bug.cgi?id=346895 Guido Schmidt changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Guido Schmidt --- Now on opensuse tumbleweed: I updated to the latest packages and tried to change the settings again: The behavior is now different, but still erroneous: 1. The preview field does not reflect any changes, neither rate nor delay. 2. When hitting the aoply button the settings do not get applied. 3. Only after a relogin do the new settings become active. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411061] Tree view expanding under incorrect parent folder when sorting by last access date
https://bugs.kde.org/show_bug.cgi?id=411061 Hernan Schmidt changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |hernan.hy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411061] Tree view expanding under incorrect parent folder when sorting by last access date
https://bugs.kde.org/show_bug.cgi?id=411061 Hernan Schmidt changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Hernan Schmidt --- In the end, I figured out that the problem was that, on update, newly accessed files were being shown at the end of the file list when showing expandable folders, instead of being sorted by Access Date inside their parent folder branch. Anyway, as of Plasma 5.20.3 and Dolphin 20.08.3, the bug seems to have been fixed. Closing as RESOLVED. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 427870] lmw, lswi and related PowerPC insns aren't allowed on ppc64le
https://bugs.kde.org/show_bug.cgi?id=427870 --- Comment #2 from Will Schmidt --- The change looks reasonable to me. +# lsw compiles (and runs) only on big endian. +if VGCONF_PLATFORMS_INCLUDE_PPC64BE_LINUX +check_PROGRAMS += lsw ldst_multiple +endif The comment there could be updated since this change includes more than just lsw, but thats not a big deal. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 258418] kcm session settings: excluded applications not recognized
https://bugs.kde.org/show_bug.cgi?id=258418 Guido Schmidt changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED --- Comment #6 from Guido Schmidt --- Using Plasma 5.19.5 (OpenSUSE Tumbleweed) it is still broken. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427493] Kwin crashes after login with symbol lookup error
https://bugs.kde.org/show_bug.cgi?id=427493 Hernan Schmidt changed: What|Removed |Added CC||hernan.hy...@gmail.com --- Comment #2 from Hernan Schmidt --- I can confirm the reported bug and the solution proposed. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460 --- Comment #3 from Philipp Schmidt --- (In reply to Markus from comment #2) Yes, it's as you said, doesn't match. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 426123] PPC ISA 3.1 support is missing, part 3
https://bugs.kde.org/show_bug.cgi?id=426123 Will Schmidt changed: What|Removed |Added CC||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460 --- Comment #1 from Philipp Schmidt --- I also just verified this with the current Neon User Edition in a VM. Same behaviour as under my main system. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] New: ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460
Bug ID: 425460
Summary: ical Calendar resource cannot be created
Product: Akonadi
Version: 5.15.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: ICal file resource
Assignee: kdepim-b...@kde.org
Reporter: philschm...@gmx.net
Target Milestone: ---
Created attachment 130934
--> https://bugs.kde.org/attachment.cgi?id=130934=edit
ics with single event on aug. 17, 14:00 UTC+2
SUMMARY
ical Calendar resource cannot be created from various sources, including file:/
and https:/.
STEPS TO REPRODUCE
1. create minimal ical file and save it to disk (e.g. the attached
testevent.ics)
2. Use Akonadi Console or KOrganizer to add a ical resource
3. select the prepared ics file and save
OBSERVED RESULT
Resource is created but events do not show up (details below)
EXPECTED RESULT
Events should show
SOFTWARE/OS VERSIONS
KDE Applications: 20.08
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15
ADDITIONAL INFORMATION
Apparently the file (or url in case of https) can't be loaded ('No file
selected'). Output from terminal after activating ical debugging and issuing
"akonadictl restart":
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f7f98087750) )
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7f7f98087750) identified as
"AgentBaseChangeRecorder - 94152844984432"
"No file selected."
kf.kio.widgets.kdirmodel: protocol mismatch: "" vs "file"
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2602, resource
id: 14883497, major code: 40 (TranslateCoords), minor code: 0
"No file selected."
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 425232] PPC ISA 3.1 support is missing, part 2
https://bugs.kde.org/show_bug.cgi?id=425232 Will Schmidt changed: What|Removed |Added CC||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 423195] PPC ISA 3.1 support is missing.
https://bugs.kde.org/show_bug.cgi?id=423195 --- Comment #12 from Will Schmidt --- (In reply to Julian Seward from comment #11) > (In reply to Carl Love from comment #5) > > Created attachment 130176 [details] > > Initial load and store instruction tests > > > > 0004-Initial-ISA-3.1-instruction-tests.patch > > > > Testsuite for new instructions > > diff --git a/none/tests/ppc64/isa_3_1_helpers.h > b/none/tests/ppc64/isa_3_1_helpers.h > new file mode 100644 > index 0..d6f2f9878 > --- /dev/null > +++ b/none/tests/ppc64/isa_3_1_helpers.h > > This seems like a lot of code (functions) to put in a .h file. Should this > stuff be in a .c > file instead? Probably yes. I'm prettu sure we have a similar scenario with the existing ppc64_helpers.h ; i'll do a lookover and see if that can be fixed up too. > > > > new files: > none/tests/ppc64/test_isa_3_1_RT.c > none/tests/ppc64/test_isa_3_1_XT.c > none/tests/ppc64/test_isa_3_1_RT.c > none/tests/ppc64/test_isa_3_1_XT.c > > These are GPL 2-only licensed. I'd prefer that they are licensed "2 or any > later version" since > that is what the project requests. See the top level README file. That shouldn't be a problem. I believe I started with one of the existing tests for those, so we probably have something else existing with the GPL 2 license. I'll poke around a bit and see if I can confirm the origins of that one too. Thanks for the review. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 420895] Files view rooted at $HOME; cannot be used to browse alternative locations
https://bugs.kde.org/show_bug.cgi?id=420895 --- Comment #9 from Sigurd Schmidt --- Hi,I am using Kubuntu 19.10. I got Elisa via the Kubuntu repository (version 0.4.2). If you can send me a debian package of Elisa with the fixed bug, I can try it. Kind regardsSigurd F. Schmidt On Mo, 2020-05-11 at 16:23 +, Matthieu Gallien wrote: > https://bugs.kde.org/show_bug.cgi?id=420895 > > --- Comment #8 from Matthieu Gallien ---(In reply > to Nate Graham from comment #7) > > Thanks, that's very helpful. I can reproduce now. Marking as high > > prioritysince this makes the files view largely useless for the typical > > purpose ofbrowsing to find music *not* in the location > > where you've configured yourlibrary (e.g. a flash drive, > > intermittently-available network share, etc). > > I had planned to fix that as part > ofhttps://invent.kde.org/kde/elisa/-/merge_requests/121 but I do not know > what todo UI wise. > Do you have suggestions ? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 420895] Wrong path for music files
https://bugs.kde.org/show_bug.cgi?id=420895 --- Comment #4 from Sigurd Schmidt --- Dear Mr. Graham, Please find attached two screenshots. I am usin three hard drives. One is only for the Os and all software, One is for my files and the third is the backup drive. Screenshot Elisa 1 shows the configuration for the hard drive of my files with the place of my music. But on screenshot Elisa 2 you can see the preinstalled path for music. No music is recognized at all because there is no music. Even the folder does not exist. The new path in the configuration does not change anything. Kind regards,Dipl.-Ing. Sigurd F. Schmidt On Fri, 2020-05-08 at 17:40 +, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=420895 > > --- Comment #3 from Nate Graham ---Hm, that's not what I see. > Can you attach a screenshot (or better yet, a screenrecording) that > illustrates the problem? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 420895] Wrong path for music files
https://bugs.kde.org/show_bug.cgi?id=420895 --- Comment #5 from Sigurd Schmidt --- Created attachment 128275 --> https://bugs.kde.org/attachment.cgi?id=128275=edit Elisa 1.png --- Comment #6 from Sigurd Schmidt --- Created attachment 128276 --> https://bugs.kde.org/attachment.cgi?id=128276=edit Elisa 2.png -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 420895] Wrong path for music files
https://bugs.kde.org/show_bug.cgi?id=420895 --- Comment #2 from Sigurd Schmidt --- Dear Sir or Madam, Of course you can change the path in the configuration. But click afterwards on "Files" in the left column. You will now in the middle see the word "Files" and below still the wrong path. The change in the configuration has no influence on this. I still cannot change the path for the files. Forwarded Message From: Nate Graham Reply-To: bug-cont...@kde.org To: sigurdfschm...@web.de Subject: [elisa] [Bug 420895] Wrong path for music files Date: Thu, 07 May 2020 14:14:25 + https://bugs.kde.org/show_bug.cgi?id=420895 Nate Graham changed: What|Removed |Added-- -- Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC| |n...@kde.org --- Comment #1 from Nate Graham ---Click on The hamburger/three bars menu in the top-right corner area of thewindow , choose "Configure Elisa..." and then add the desired additional paths. -- You are receiving this mail because:You reported the bug. Kind regards Dipl.-Ing. Sigurd F. Schmidt -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 420895] New: Wrong path for music files
https://bugs.kde.org/show_bug.cgi?id=420895 Bug ID: 420895 Summary: Wrong path for music files Product: elisa Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: sigurdfschm...@web.de Target Milestone: --- I cannot change the path of the music files when I would like to choose a song by the file of it. STEPS TO REPRODUCE 1. Go to file on the main window and click on it 2. You can see now the path of the files. 3. You cannot edit this path at all. OBSERVED RESULT EXPECTED RESULT I can change the path to the folder where I have my music stored. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.18.4 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 419139] Process runs at 99-100% of core until shutdown and reoccurs again later
https://bugs.kde.org/show_bug.cgi?id=419139 Sebastian Schmidt changed: What|Removed |Added CC||schro...@gmail.com --- Comment #6 from Sebastian Schmidt --- I had the same issue with chromium for quite some while, but never had the time to investigate. The plasma-browser-integration-host process would always run at 100% usage of one core as soon as a video starts playing and the media widget didn't detect the video. However, this never happened with firefox. For me this issue was caused by DBUS_SESSION_BUS_ADDRESS not being set. I changed the session to "Exec=dbus-run-session /usr/bin/startplasma-x11" instead of "Exec=/usr/bin/startplasma-x11". I'm not sure if this has any negative consequences, but the wayland session also uses dbus-run-session -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 394775] Annotations in the separated XML files
https://bugs.kde.org/show_bug.cgi?id=394775 --- Comment #8 from Jonathan Schmidt-Dominé --- To summarise my situation: Actually I am still using Okular 1.3. I am reading and annotating a lot of PDFs for my work, any newer version of Okular would completely break my workflow. I need the original PDFs to share them with others without my annotations, many of them are very large (books etc.), always being asked whether I want to save my annotations sounds like madness to me, I am often searching for something within the XML files. Best regards, Jonathan -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403640] Wrong positioning of launchers and windows during startup for icon-only taskmanager
https://bugs.kde.org/show_bug.cgi?id=403640 --- Comment #7 from Philipp Schmidt --- I am on 5.18.1, but I still get this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413677] New: Icons of started apps reorder randomly from pinned to other position
https://bugs.kde.org/show_bug.cgi?id=413677 Bug ID: 413677 Summary: Icons of started apps reorder randomly from pinned to other position Product: plasmashell Version: 5.17.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: philschm...@gmx.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Application icons that are pinned to a certain position on the icon only task bar change their position when the app is opened. When the application is closed they reorder again. STEPS TO REPRODUCE 1. Pin multiple application to taskbar 2. Open application not on the right edge 3. Close application again OBSERVED RESULT Application icon moves to other location on the task bar EXPECTED RESULT Application icon stays in the same position it was pinned at SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 412482] New: Patch to fix crashes involving piece holders
https://bugs.kde.org/show_bug.cgi?id=412482 Bug ID: 412482 Summary: Patch to fix crashes involving piece holders Product: palapeli Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: majew...@gmx.net Reporter: bernds_...@t-online.de CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 122949 --> https://bugs.kde.org/attachment.cgi?id=122949=edit A patch to fix the problem Palapeli sometimes crashes when using piece holders. What seems to happen is that two pieces in different scenes/views are merged, and the code trying to update the piece list for one of these scenes fails to remove the piece because it's not on the list. The piece then gets deleted (through a deleteLater call), but it's still in the list for another scene, and we get a use-after-free scenario. I'm attaching a patch which seems to fix it - I've been unable to reproduce crashes after this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411061] Tree view expanding under incorrect parent folder when sorting by last access date
https://bugs.kde.org/show_bug.cgi?id=411061 Hernan Schmidt changed: What|Removed |Added CC||hernan.hy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411061] Tree view expanding under incorrect parent folder when sorting by last access date
https://bugs.kde.org/show_bug.cgi?id=411061 Hernan Schmidt changed: What|Removed |Added Platform|Other |Neon Packages Keywords||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411061] Tree view expanding under incorrect parent folder when sorting by last access date
https://bugs.kde.org/show_bug.cgi?id=411061 Hernan Schmidt changed: What|Removed |Added Summary|Tree view expanding under |Tree view expanding under |incorrect parent folder |incorrect parent folder ||when sorting by last access ||date -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411061] Tree view expanding under incorrect parent folder
https://bugs.kde.org/show_bug.cgi?id=411061 --- Comment #1 from Hernan Schmidt --- On further inverstigation, i have found that it seems to be a problem related to sorting. The bug presents itself When sorting by Last Accesed, and goes back to normal when reverting to Name Sorting. STEPS TO REPRODUCE 1. Select details view with expandable folders turned on. 2. Sort by Last Accessed 3. From Home folder, expand a folder by clicking on its tree arrow. OBSERVED RESULT The folder contents tree are shown at the bottom of the list under the wrong folder. EXPECTED RESULT The contents should expand immediately under the clicked element, and be sorted by date of last access. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411061] New: Tree view expanding under incorrect parent folder
https://bugs.kde.org/show_bug.cgi?id=411061 Bug ID: 411061 Summary: Tree view expanding under incorrect parent folder Product: dolphin Version: 19.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: hernan.hy...@gmail.com Target Milestone: --- Created attachment 122243 --> https://bugs.kde.org/attachment.cgi?id=122243=edit Tree view expanding under incorrect parent folder SUMMARY When expanding a folder in details view, instead of showing the tree immediately below the clicked element, the tree expands at the end of the file list, as seen in the attached screen show. This poses an obvious risk since one is unable to accurately determine the actual folder structure in a visual way. This bug only happens with certain folders, and so far I have been unable to identify a pattern or reproduce the problem on other folders. Unfortunately I cannot outline any steps to reproduce the problem, so it boils down to expanding random folder trees until the bug shows up. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon User 5.16 (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 408559] New: Baloo crash after reboot Object::getRef at ./poppler/Object.h:240
https://bugs.kde.org/show_bug.cgi?id=408559 Bug ID: 408559 Summary: Baloo crash after reboot Object::getRef at ./poppler/Object.h:240 Product: frameworks-baloo Version: 5.59.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: ojschm...@kde.org Target Milestone: --- Created attachment 120776 --> https://bugs.kde.org/attachment.cgi?id=120776=edit Crash trace SUMMARY Baloo crashes whenever after every restart of my computer. poppler-utils: 0.62.0-2ubuntu2.8 poppler-data: 0.4.8-2 SOFTWARE/OS VERSIONS (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #12 from Axel Schmidt --- Log files for the error -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #11 from Axel Schmidt --- Gilles, i tried both version for linux now under (K)Ubuntu 18.04: digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage both doesn't work. Both couldn't connect to mysql and than stops or exiting with error. The original digikam 5.6.0 from system start, can connect to mysql and work as expected and now under (K)Ubuntu 18.04 the error is gone... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #8 from Axel Schmidt --- Created attachment 120513 --> https://bugs.kde.org/attachment.cgi?id=120513=edit ErrorLog digikam-6.2.0-git-20190503T152230-qtwebengine-x86-64.appimage.log start with error can't connect to mysql and then exit with error -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389355] digikam crash during metadata refresh if you at same time create an new album
https://bugs.kde.org/show_bug.cgi?id=389355 --- Comment #7 from Axel Schmidt --- Created attachment 120512 --> https://bugs.kde.org/attachment.cgi?id=120512=edit Errorlog digikam-6.2.0-git-20190529T102951-qtwebkit-x86-64.appimage Start with error can't connect to mysql, but mysql is working and than hang on icc profile on start screen with no more response. klick on startscreen than it disappear but no program window showed. digikam hang in tasklist without any cpu time... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #2 from Will Schmidt --- I have no input into a different better spot for getRRegUniverse_PPC changes. A few other patch comments: +++ b/Makefile.all.am the "-mvsx -maltivec" combo can be shrunk to just "-mvsx" . (mvsx is a superset that includes maltivec). + /* LE API requires NJ be set to 0. */ A few spots.. that API reference should prob be ABI. + vrm[0] = ~(1 << (127 - 111)) & vrm[0]; // Clear NJ bit LE case + vrm[1] = ~(1 << (127 - 111)) & vrm[1]; // Clear NJ bit BE case Preferably wrap this in some logic so we are not writing to reserved bits of the vscr in the non-LE or non-BE cases. +static IRExpr* dnorm_adj ( IRExpr* value ) just wondering, should this be instead named dnorm_adj_int or some variation to avoid conflict if we need to do anything similar with Longs or Shorts in the future. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406198] none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output
https://bugs.kde.org/show_bug.cgi?id=406198 --- Comment #2 from Will Schmidt --- Created attachment 119234 --> https://bugs.kde.org/attachment.cgi?id=119234=edit proposed patch to suppress CA bit display first-blush proposed patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406198] none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output
https://bugs.kde.org/show_bug.cgi?id=406198 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com, ||will_schm...@vnet.ibm.com --- Comment #1 from Will Schmidt --- This is actually a valgrind testcase issue, not a problem with valgrind itself. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406198] New: none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output
https://bugs.kde.org/show_bug.cgi?id=406198 Bug ID: 406198 Summary: none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: will_schm...@vnet.ibm.com Target Milestone: --- SUMMARY It was pointed out to me that valgrind attempts to display ALL bits of the XER, but our tests only set or clear a few of the bits. In particular, we sometimes (not always) are seeing the CA bit show up in the test results. This is noticed with the addex test, as illustrated below. --- test_isa_3_0_other.stdout.exp-LE2019-03-25 15:44:12.283983772 -0500 +++ test_isa_3_0_other.stdout.out 2019-04-03 14:18:47.072441960 -0500 @@ -40,15 +40,15 @@ modud , 001cbe991def => 00043eb0c0b2 () modud , => () -addex , => () -addex , 001cbe991def => 001cbe991def () -addex , => () -addex 001cbe991def, => 001cbe991def () -addex 001cbe991def, 001cbe991def => 00397d323bde () OV32 -addex 001cbe991def, => 001cbe991dee () OV OV32 -addex , => () OV OV32 -addex , 001cbe991def => 001cbe991def () OV OV32 -addex , => () OV OV32 +addex , => () CA +addex , 001cbe991def => 001cbe991def () CA +addex , => () CA +addex 001cbe991def, => 001cbe991def () CA +addex 001cbe991def, 001cbe991def => 00397d323bde () CA OV32 +addex 001cbe991def, => 001cbe991dee () OV CA OV32 +addex , => () OV CA OV32 +addex , 001cbe991def => 001cbe991def () OV CA OV32 +addex , => () OV CA OV32 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.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 --- Comment #16 from Will Schmidt --- Created attachment 119233 --> https://bugs.kde.org/attachment.cgi?id=119233=edit proposed patch (v4) Updated per feedback received. tested OK on P7,P8LE,P8BE,P9 (LE). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828
--- Comment #12 from Will Schmidt ---
Created attachment 119219
--> https://bugs.kde.org/attachment.cgi?id=119219=edit
vex : sanityCheckFail: exiting due to bad IR
I got this error when regression testing this patch on a P8 BE system.
Probably obvious, but I don't immediately understand what this is telling me.
(I'll look more tomorrow)
+IN STATEMENT:
+
+t13 =
ReinterpF64asI64(RoundF64toF32(Xor32(t11,And32(Shl32(t11,0x:I8),0x:I32)),DivF64(Xor32(t11,And32(Shl32(t11,0x:I8),0x:I32)),F64i{0x},t9)))
+
+ERROR = IRStmt.Put.Tmp: tmp and expr do not match
--
You are receiving this mail because:
You are watching all bug changes.
