[kde] [Bug 485686] Doxyqml: restore handling of array-typed attributes
https://bugs.kde.org/show_bug.cgi?id=485686 Olaf Mandel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Olaf Mandel --- https://invent.kde.org/sdk/doxyqml/-/merge_requests/22 was merged -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485686] New: Doxyqml: restore handling of array-typed attributes
https://bugs.kde.org/show_bug.cgi?id=485686
Bug ID: 485686
Summary: Doxyqml: restore handling of array-typed attributes
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: o.man...@menlosystems.com
Target Milestone: ---
This is about the Doxyqml tool (https://invent.kde.org/sdk/doxyqml).
SUMMARY
Since commit 5328ede, parsing stops at array-typed class attributes, e.g.:
```qml
Item {
transitions: [ ]
/**
* This is missing from the output
*/
property int after
}
```
STEPS TO REPRODUCE
1. Run doxyqml over a file that assigns an array to one of the base-classes
properties
2. Note that the output is missing everything from this attribute till the end
of the class
OBSERVED RESULT
```c++
class NameOfInputFile : public QtQuick.Item {
var transitions;
};
```
EXPECTED RESULT
```c++
class NameOfInputFile : public QtQuick.Item {
var transitions;
public:
/**
* This is missing from the output
*/
Q_PROPERTY(int after READ dummyGetter_after_ignore)
};
```
SOFTWARE/OS VERSIONS
Linux, Python 3.10
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.
[kde] [Bug 463558] New: Delete my account
https://bugs.kde.org/show_bug.cgi?id=463558 Bug ID: 463558 Summary: Delete my account Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@oflebbe.de Target Milestone: --- Please delete my account. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] apply included fixes for Xen 4.6/4.7/4.8/4.9/4.10/4.11/4.12
https://bugs.kde.org/show_bug.cgi?id=390553 Olaf Hering changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REOPENED|RESOLVED --- Comment #8 from Olaf Hering --- Good luck. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] apply included fixes for Xen 4.6/4.7/4.8/4.9/4.10/4.11/4.12
https://bugs.kde.org/show_bug.cgi?id=390553 --- Comment #7 from Olaf Hering --- Created attachment 126481 --> https://bugs.kde.org/attachment.cgi?id=126481=edit patches-for-bug390553.3a2711c65.tar.xz refresh of the patch queue, based on 3a2711c65 for i in */*.patch ; do git am < $i ; done -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 415474] Crash while closing the "Energy Information" window
https://bugs.kde.org/show_bug.cgi?id=415474 --- Comment #9 from Olaf Dreyer --- I can confirm, that the new version is not crashing anymore. Operating System: Gentoo Linux KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.4.20-gentoo-x86_64 OS Type: 64-bit Processors: 12 × Intel® Core™ i9-8950HK CPU @ 2.90GHz Memory: 31,2 GiB -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] apply included fixes for Xen 4.6/4.7/4.8/4.9/4.10/4.11/4.12
https://bugs.kde.org/show_bug.cgi?id=390553 Olaf Hering changed: What|Removed |Added URL|https://github.com/olafheri |https://github.com/olafheri |ng/valgrind/compare/master. |ng/valgrind/compare/olh-bas |..xen |e-master...olh-fixes-master -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] apply included fixes for Xen 4.6/4.7/4.8/4.9/4.10/4.11/4.12
https://bugs.kde.org/show_bug.cgi?id=390553 Olaf Hering changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #6 from Olaf Hering --- Browsing the suggested changes attached to this bug would have revealed the other bug can not possibly fix this bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 415474] Crash while closing the "Energy Information" window
https://bugs.kde.org/show_bug.cgi?id=415474 Olaf Dreyer changed: What|Removed |Added CC||o...@dreyero.de --- Comment #2 from Olaf Dreyer --- I can reproduce this bug also on Gentoo: Operating System: Gentoo Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Kernel Version: 5.4.10-gentoo-x86_64 OS Type: 64-bit Processors: 12 × Intel® Core™ i9-8950HK CPU @ 2.90GHz Memory: 31,2 GiB The stack trace is identical to Comment 1 -- 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.
[valgrind] [Bug 390553] apply included fixes for Xen 4.6/4.7/4.8/4.9/4.10/4.11/4.12
https://bugs.kde.org/show_bug.cgi?id=390553 --- Comment #4 from Olaf Hering --- Pull request sent to valgrind-develop...@lists.sourceforge.net for https://github.com/olafhering/valgrind/commits/bug390553-20181125-ddfc274b2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] apply included fixes for Xen 4.6/4.7/4.8/4.9/4.10/4.11/4.12
https://bugs.kde.org/show_bug.cgi?id=390553 Olaf Hering changed: What|Removed |Added Summary|update xen support to Xen |apply included fixes for |4.10|Xen ||4.6/4.7/4.8/4.9/4.10/4.11/4 ||.12 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] update xen support to Xen 4.10
https://bugs.kde.org/show_bug.cgi?id=390553 --- Comment #3 from Olaf Hering --- Changes moved: https://github.com/olafhering/valgrind/compare/olh-base-master...olh-fixes-master -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 398775] Various keybindings are gone, like copy, find, "jump words in console"
https://bugs.kde.org/show_bug.cgi?id=398775 --- Comment #1 from Sven Olaf Oostenbrink --- Is there any update or news on a fix for this? I currently am in the situation where I have to use up to three different COPY operations, CTRL-INS, CTRL-C, CTRL-SHIFT-C depending on which program is being used. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397962] Digikam 6.0 does not start after install..
https://bugs.kde.org/show_bug.cgi?id=397962 Olaf Lenz changed: What|Removed |Added CC||o...@lenz.name --- Comment #3 from Olaf Lenz --- I can confirm the crash when starting Digikam 6.0.0 on Windows 7 (64bit) with the older installer. With the new installer (from Oct 2nd), it now starts, so I guess this bug can be closed. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 398775] Various keybindings are gone, like copy, find, "jump words in console"
https://bugs.kde.org/show_bug.cgi?id=398775 Sven Olaf Oostenbrink changed: What|Removed |Added CC||s...@capmega.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 398776] New: Pressing the "Close window" closes yakuake without asking if I'm really sure
https://bugs.kde.org/show_bug.cgi?id=398776 Bug ID: 398776 Summary: Pressing the "Close window" closes yakuake without asking if I'm really sure Product: yakuake Version: 3.0.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: s...@capmega.com Target Milestone: --- In Menu > Configure Yakuake > Behaviour > Dialogs, I have selected "Confirm quit when more than one session is open" and I have multiple tabs with each multiple sections open. If I accidentally press the "close" button though, yakuake quits without asking anything.. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 398775] Various keybindings are gone, like copy, find, "jump words in console"
https://bugs.kde.org/show_bug.cgi?id=398775 Sven Olaf Oostenbrink changed: What|Removed |Added Version|unspecified |3.0.5 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 398775] New: Various keybindings are gone, like copy, find, "jump words in console"
https://bugs.kde.org/show_bug.cgi?id=398775 Bug ID: 398775 Summary: Various keybindings are gone, like copy, find, "jump words in console" Product: yakuake Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: s...@capmega.com Target Milestone: --- On Kubuntu 18.04 CTRL-INS always copied to clipboard. This no longer works (even though SHIFT-INS does still work) and after using that for the past 20 something years, I have no idea how to work without it. I also use it on average 10 times per hour, so that is frustrating.. I have checked shortcut key configuration, and "copy" is not there, even though it is there on Konsole. Also, CTRL-LEFT and CTRL-RIGHT are no longer working. I could use these to jump left or right over words, which made working with the console so much faster. Also, CTRL-F would be nice as an addition to get the "Find" console, instead of having to use the right mouse button, and select "Find" from the menu.. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 --- Comment #22 from Olaf Jan Schmidt --- I now saw another update. This fixed the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 --- Comment #7 from Olaf Jan Schmidt --- Created attachment 114043 --> https://bugs.kde.org/attachment.cgi?id=114043=edit New crash information added by DrKonqi kmail (5.8.2) using Qt 5.11.1 I have the same propblem since upgrading KDE Neon an hour ago. No further updates are offered – so if “todays updates” mentioned by tomas nackaerts in https://bugs.kde.org/show_bug.cgi?id=396694#c6 are already generally available, then they do NOT solve the problem for everyone. -- Backtrace (Reduced): #7 0x7f15de4fad3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x004035fc in main (argc=1, argv=0x7ffd70150678) at /workspace/build/src/main.cpp:128 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 Olaf Jan Schmidt changed: What|Removed |Added CC||ojschm...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] update xen support to Xen 4.10
https://bugs.kde.org/show_bug.cgi?id=390553 Olaf Hering <o...@aepfle.de> changed: What|Removed |Added URL||https://github.com/olafheri ||ng/valgrind/compare/master. ||..xen --- Comment #1 from Olaf Hering <o...@aepfle.de> --- Preview the changes over there, please: https://github.com/olafhering/valgrind/compare/master...xen -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390553] New: update xen support to Xen 4.10
https://bugs.kde.org/show_bug.cgi?id=390553 Bug ID: 390553 Summary: update xen support to Xen 4.10 Product: valgrind Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: o...@aepfle.de Target Milestone: --- I'm preparing changes to add changed interfaces up to Xen-4.10. The amount of patches will be huge. How are the patches supposed to be delivered? Attach here, pull request, send to mailing list, all of it? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 374706] starting a bash-script as "root" by clicking desktop-file fails
https://bugs.kde.org/show_bug.cgi?id=374706 --- Comment #3 from Olaf Meltzer <olaf.melt...@gmx.de> --- After latest Updates of KDE-related packages with Plasma now in version 5.8.6 the Problem disappeared. openSUSE Leap 42.2 - Kernel: 4.4.49-16-default Qt: 5.6.1 - KDE Frameworks: 5.26.0 - Plasma: 5.8.6 Olaf -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362140] Discover don't find anything on search
https://bugs.kde.org/show_bug.cgi?id=362140 --- Comment #16 from Olaf <olaf...@web.de> --- Hi! I have the same problem with my 16.04.1, Discover can't searching for software. I've installed from console muon: apt-get install moun Discover also can't display a list of the installed tools/packages, with muon not a problem. - - Now I have tested "appstreamcli search chromium" - not possible search. Now I don't know more. must waiting for updates. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362140] Discover don't find anything on search
https://bugs.kde.org/show_bug.cgi?id=362140 Olaf <olaf...@web.de> changed: What|Removed |Added CC| |olaf...@web.de --- Comment #15 from Olaf <olaf...@web.de> --- Hi! I have the same problem with my 16.04.1, Discover can't searching for software. I've installed from console muon: apt-get install moun Discover also can't display a list of the installed tools/packages, with muon not a problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 374706] starting a bash-script as "root" by clicking desktop-file fails
https://bugs.kde.org/show_bug.cgi?id=374706 --- Comment #2 from Olaf Meltzer <olaf.melt...@gmx.de> --- Erroniously I wrote, the bug appears under KDE: 4.14.25. This is wrong. Actually I use KDE: 5.26.0 Plasma 5.8.3 Sorry for my mistake -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 374706] starting a bash-script as "root" by clicking desktop-file fails
https://bugs.kde.org/show_bug.cgi?id=374706 Olaf Meltzer <olaf.melt...@gmx.de> changed: What|Removed |Added CC||olaf.melt...@gmx.de --- Comment #1 from Olaf Meltzer <olaf.melt...@gmx.de> --- I confirm this bug. This bug is not related tu su root alone, but to any change of the executing user. Testcase is openSUSE 42.2 (x86_64), Kernel 4.4.36-8-default, KDE: 4.14.25. This Bug is not present in openSUSE 42.1. Olaf Meltzer, 2017-01-15 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354232] Lens information is always "unavailable" for Pentax K-S1 images
https://bugs.kde.org/show_bug.cgi?id=354232 --- Comment #11 from Olaf <schlusenb...@web.de> --- It worked with the Win64.exe with Windows 10 in a virtual box- the lens ist shown. It did not work with the x86-64.appimage with clean install of Kubuntu 16.04 in a virtual box. Digikam 5.4.0 starts, but the lens type is "not available". Olaf -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354232] Lens information is always "unavailable" for Pentax K-S1 images
https://bugs.kde.org/show_bug.cgi?id=354232 --- Comment #9 from Olaf <schlusenb...@web.de> --- Hello Gilles, I tried to start digikam-5.4.0-01-x86-64.appimage, but it shows only the splashscreen and terminates with this message: D/tmp/.mount_RzL9Xq/AppRun: Zeile 37: 2288 Speicherzugriffsfehler (Speicherabzug geschrieben) digikam.wrapper $@ olaf@olaf-iMac:~/Downloads$ Seicherzugriffsfehler "memory access fault"? Sorry, German error message... I keep on trying. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354232] Lens information is always "unavailable" for Pentax K-S1 images
https://bugs.kde.org/show_bug.cgi?id=354232 Olaf <schlusenb...@web.de> changed: What|Removed |Added CC||schlusenb...@web.de --- Comment #5 from Olaf <schlusenb...@web.de> --- I also have this problem. My camera is a Pentax K-30. The lens information is "not available". Hovever, the lens type is shown in the Manufacturer Notes. But since the Lens Auto-correction module does not use this information and I can´t search or filter according this information, it has no great use for me. Is it possible to copy the information from the the Manufacturer Notes to a perhaps more standard-conform EXIF field in the database? -- You are receiving this mail because: You are watching all bug changes.
[knode] [Bug 312391] Reference line is too long in deeply nested threads
https://bugs.kde.org/show_bug.cgi?id=312391 --- Comment #2 from Olaf Meltzer <olaf.melt...@gmx.de> --- Created attachment 99887 --> https://bugs.kde.org/attachment.cgi?id=99887=edit Truncate too long Reference-Lines If you answer a message which already contains a very long References line, your message could generate a References line exceeding the Limit of 998 characters. This patch will truncate your References according to RFC 5537. The RefTrim patch was designed by Michael Baeuerle and I testet on openSUSE 13.2 and knode 4.14.10. Olaf Meltzer -- You are receiving this mail because: You are watching all bug changes.
[knode] [Bug 312391] Reference line is too long in deeply nested threads
https://bugs.kde.org/show_bug.cgi?id=312391 Olaf Meltzer <olaf.melt...@gmx.de> changed: What|Removed |Added CC||olaf.melt...@gmx.de --- Comment #1 from Olaf Meltzer <olaf.melt...@gmx.de> --- I Stumbled upon this same bug. News server was news.Individual.net. We disputated this bug in de.comp.os.unix.apps.kde starting with <news:dtpkkof3e2...@mid.individual.net> referring the post I was not able to answer with knode directly: <news:3072571.iibc2ph...@pointedears.de> HTH -- Olaf Meltzer -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 --- Comment #9 from Olaf Titz <o...@bigred.inka.de> --- There is a recurring issue in support fora related to owncloud and iOS/Android CalDAV sync apps. I still don't understand it completely, but it seems to be related to two or three potential reasons. All of them have to do with the fact that PROPFIND is treated differently from GET (at least by Apache). 1. Sure: a number of misconfigurations of Apache can cause Apache and/or Owncloud to misunderstand the initial PROPFIND request. There is plenty of documentation about that. (Everything here applies not to owncloud exclusively but to all Apache/PHP-based DAV services.) 2. Confirmed: When the requested resource is not known (wrong URL), Apache responds 405 instead of 404 to PROPFIND, so the end user gets a misleading technical error message instead of a plain "URL not found". 3. Speculative: it looks like Apache responds 405 instead of 401 too in certain circumstances, but I'm not exactly sure what causes this. This is what really can cause breakage to the authorization protocol. The DAVdroid app has an option to always send an Authorization header with the first request to work around these kind of problems (at least the #3 one) and the recommendation could be that Akonadi get such an option too. (Now I don't have the problem any more since I fixed my setup on all three sides (owncloud, android, akonadi) but getting it right everywhere was much harder than it should be...) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 Olaf Titz <o...@bigred.inka.de> changed: What|Removed |Added CC||o...@bigred.inka.de --- Comment #7 from Olaf Titz <o...@bigred.inka.de> --- Broken for me too. I have a password consisting only of ASCII letters and digits. Akonadi always sends the first PROPFIND request without authorization headers, as gets logged by Apache. this is the version: akonadi (1.12.1-0ubuntu1.1) trusty -- You are receiving this mail because: You are watching all bug changes.
