[dolphin] [Bug 447119] Summary: Dolphin/Baloo search with symlinks
https://bugs.kde.org/show_bug.cgi?id=447119 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 337578] parts of a pdf are cut off when printing pages with size ratio different from the medium in the printer
https://bugs.kde.org/show_bug.cgi?id=337578 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #5 from Geert Janssens --- I have tried this with okular 23.04.3 today. My test was to print a pdf document formatted as a single A0 page in landscape. It correctly scaled down to fit an A4 page using the options "Fit to print area" or "Fit to full page". With the latter I lost some information that was rendered beyond the margins this printer could physically print to, but that's normal and expected behaviour. So in my testing this feature works (but it's not my bug report). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 313815] Add "Print current view" option to the print dialogue
https://bugs.kde.org/show_bug.cgi?id=313815 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #3 from Geert Janssens --- I would also benefit greatly from this being implemented. I'll just add there's a similar, more recent request in bug 226321. Perhaps these can be considered the same thing and be merged into one request. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 454315] Images by copying a rectangular selection is partially blank when the selection is outside initial screen
https://bugs.kde.org/show_bug.cgi?id=454315 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #1 from Geert Janssens --- I am also having this issue on Fedora 37. For the current project we're in I regularly receive very high resolution pdfs. I want to capture parts of it into images for easier processing. However when zoomed out to fit the screen too many details are lost and the selected screen capture is no longer suitable. So it would help a lot if I could zoom in sufficiently and then capture more than just what's visible on screen. Versions: Okular 23.04.3 Linux/KDE Plasma 5.27.8 KDE Frameworks 5.108.0 Qt 5.15.9 xcb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445058] kwin interactive console does not work
https://bugs.kde.org/show_bug.cgi?id=445058 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #18 from Geert Janssens --- It took me a while to figure out that "console.info" in comment 13 was meant to be used instead of "print" in the scripts... That does indeed work. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 354920] No sound on local computer over xfeerdp session
https://bugs.kde.org/show_bug.cgi?id=354920 Geert Janssens changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 from Geert Janssens --- For me this is fixed. I'm currently running Fedora 36, which ships freerdp-2.8.0-1.fc36.x86_64. For my part this can be closed, though I don't know if that's something I should do now or leave for the maintainers. So I have set the status back to reported to be on the safe side. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 348047] Applications started on first Activity instead of where they were left
https://bugs.kde.org/show_bug.cgi?id=348047 --- Comment #7 from Geert Janssens --- I am aware this feature is not implemented yet under Wayland, so for completeness I'll add I'm seeing this under X11. I don't know about the original author though. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 348047] Applications started on first Activity instead of where they were left
https://bugs.kde.org/show_bug.cgi?id=348047 --- Comment #6 from Geert Janssens --- Furhtermore bug 351402 has a duplicate bug 437551 which mentions both symptoms have started appearing together. It really looks like it would be useful to bring all those bugs together under one. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 348047] Applications started on first Activity instead of where they were left
https://bugs.kde.org/show_bug.cgi?id=348047 --- Comment #5 from Geert Janssens --- Bug 442380 describes a similar issue, but this time across virtual desktops rather than activities. I suspect this to be the same bug, but I'll leave it to someone more experienced to make a final decision on this. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #63 from Geert Janssens --- I also found this older bug 348047 I had commented on a while back. It deals with the same issue appearing when using plasma activities. I am not completely sure it's the same as with virtual desktops, but the symptoms are very similar. So I thought it worth considering here and cross-referencing them. Perhaps someone with more knowledge can decide whether these are duplicates or not. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #62 from Geert Janssens --- I'm seeing a similar problem. However instead of virtual desktops I heavily rely on Plasma activities. Other than that the behaviour is exactly the same. After rebooting most applications are not properly restored to the Activities I had started them on initially. This is very annoying as I (use to) have 10+ Konsole windows open spread over 4 activities. Early on I went through the effort of resetting them to the proper activity after reboot, but that became way to cumbersome. I now just have 2 Konsole windows left and I close all other applications before shutting down. So in a way the crippled session restore has caused me to no longer rely on it. But that's an important step backwards in the overal user experience. I'm currently on Fedora 35, X11. But the problem started somewhere in Fedora 34 for me already. As others I have tried to remove all files in .config/session. It works for one reboot and afterwards things go wrong again. The applications I typically left open were Dolphin, Firefox, Kontact and Konsole. I never noticed Firefox restoring properly as I have taken the habit to just shut it down. I'll check this on a future reboot and report back because that could mean only some applications are affected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449574] New: Printerlist is too narrow and not resizable
https://bugs.kde.org/show_bug.cgi?id=449574 Bug ID: 449574 Summary: Printerlist is too narrow and not resizable Product: systemsettings Version: 5.23.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: i...@kobaltwit.be CC: plasma-b...@kde.org Target Milestone: --- Created attachment 146236 --> https://bugs.kde.org/attachment.cgi?id=146236=edit Screenshot of printerlist with truncated printer names SUMMARY I have several print queues with fairly long names that only differ in their suffix, like Bureau_Lade2_Duplex_Plain Bureau_Lade2_Duplex_Film These names won't fully fit in the printer list in System Settings and hence it's hard to distinguish them. I also can't widen the list to see the full names. This makes is harder than necessary to select the proper printer. Particularly as there is plenty of space on my screen to widen the full System Settings window and/or the printer list widget. STEPS TO REPRODUCE 1. Create multiple printer queues with long names 2. Open System Settings->Printers 3. Widen the System Settings window OBSERVED RESULT After step 2. the list of printers is presented, but the printer names are truncated. Attempting to widen the window as suggested in step 3. doesn't make a difference. EXPECTED RESULT When there's enough room, just display the printer names in full or allow the user to widen the list. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 35 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 432174] Certificate dialog loops when cancelled (expired certificate)
https://bugs.kde.org/show_bug.cgi?id=432174 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #3 from Geert Janssens --- I have run into this issue several times as well. The issue gets even worse if auto-checking for new mail is enabled and you're not around. Each time a mail check is triggered a new popup is added. I was called to an unattended computer today which had over 300 warning dialogs open. I think one single dialog per mail server should be presented at most. If the dialog is not dismissed by the next mail check, simply don't create another dialog and at best try to raise the existing dialog again. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 348047] Applications started on first Activity instead of where they were left
https://bugs.kde.org/show_bug.cgi?id=348047 --- Comment #4 from Geert Janssens --- For additional info Fedora 35 uses plasma-workspace-5.23.3-1.fc35.x86_64 Fedora 34 uses plasma-workspace-5.22.5-2.fc34.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 348047] Applications started on first Activity instead of where they were left
https://bugs.kde.org/show_bug.cgi?id=348047 --- Comment #3 from Geert Janssens --- I forgot I had left a comment on this bug. Since then things have worsened. A while ago I upgraded to Fedora 34 and since then all applications restore to the first workspace. This is becoming highly annoying. It's a serious chore to relocate 10+ windows each time the PC is rebooted (ie daily). Hoping a newer plasma would fix it, I upgraded to Fedora 35 yesterday but it's still failing to properly restore my session. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 445271] New: KDevelop crashes on close
https://bugs.kde.org/show_bug.cgi?id=445271 Bug ID: 445271 Summary: KDevelop crashes on close Product: kdevelop Version: 5.6.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: i...@kobaltwit.be Target Milestone: --- Application: kdevelop (5.6.2) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.16-201.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: There are two ways I can have this crash: 1. I hit the close button on kdevelop's main window. 2. I choose File->Quit The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7fb240e7e77d in KDevelop::TopDUContext::indexed() const (this=0x55b3a83d45a0) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/topducontext.cpp:534 #5 0x7fb240e7ebb3 in KDevelop::TopDUContextLocalPrivate::removeImportedContextRecursion(KDevelop::TopDUContext const*, KDevelop::TopDUContext const*, int, QSet >&) (this=this@entry=0x55b3a78b2f90, traceNext=traceNext@entry=0x55b3a6250330, imported=, distance=2, rebuild=...) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/topducontext.cpp:356 #6 0x7fb240e84f21 in KDevelop::TopDUContextLocalPrivate::removeImportedContextRecursively(KDevelop::TopDUContext*, bool) (local=true, context=0x55b3a6250330, this=0x55b3a78b2f90) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/topducontext.cpp:231 #7 KDevelop::TopDUContext::removeImportedParentContext(KDevelop::DUContext*) (this=, context=0x55b3a6250330) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/topducontext.cpp:1088 #8 0x7fb240e74033 in KDevelop::DUContext::~DUContext() (this=0x55b3a6250330, this=) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/ducontext.cpp:440 #9 0x7fb20bb28937 in Python::PythonDUContext::~PythonDUContext() (this=0x55b3a6250330, this=) at /usr/src/debug/kdevelop-python-5.6.2-1.fc34.x86_64/duchain/pythonducontext.h:37 #10 Python::PythonDUContext::~PythonDUContext() (this=0x55b3a6250330, this=) at /usr/src/debug/kdevelop-python-5.6.2-1.fc34.x86_64/duchain/pythonducontext.h:37 #11 0x7fb240e85b62 in KDevelop::TopDUContext::deleteSelf() (this=0x55b3a6250330) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/topducontext.cpp:596 #12 0x7fb240e553e5 in KDevelop::DUChainPrivate::removeDocumentChainFromMemory(KDevelop::TopDUContext*) (this=0x7fb2413d0520 <_ZZN8KDevelop12_GLOBAL__N_122Q_QGS_sdDUChainPrivate13innerFunctionEvE6holder.lto_priv.0>, context=) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/duchain.cpp:456 #13 0x7fb240e58cb3 in KDevelop::DUChain::removeDocumentChain(KDevelop::TopDUContext*) (this=this@entry=0x55b3a33c0a40, context=0x55b3a6250330) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/duchain.cpp:1312 #14 0x7fb240e5cbca in KDevelop::DUChainPrivate::cleanupTopContexts() (this=0x7fb2413d0520 <_ZZN8KDevelop12_GLOBAL__N_122Q_QGS_sdDUChainPrivate13innerFunctionEvE6holder.lto_priv.0>) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/duchain.cpp:1093 #15 KDevelop::DUChain::shutdown() (this=) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/language/duchain/duchain.cpp:1736 #16 0x7fb243d26bad in KDevelop::Core::cleanup() (this=0x55b3a1ead960) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/shell/core.cpp:405 #17 0x7fb243d272bc in KDevelop::Core::shutdown() (this=0x55b3a1ead960) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/shell/core.cpp:360 #18 0x7fb243d06e4f in KDevelop::MainWindow::~MainWindow() (this=0x55b3a1fe69f0, this=) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/shell/mainwindow.cpp:150 #19 0x7fb243d06ebd in KDevelop::MainWindow::~MainWindow() (this=0x55b3a1fe69f0, this=) at /usr/src/debug/kdevelop-5.6.2-1.fc34.x86_64/kdevplatform/shell/mainwindow.cpp:154 #20 0x7fb24248fd31 in QObject::event(QEvent*) (this=0x55b3a1fe69f0, e=0x7fb22401f260) at kernel/qobject.cpp:1301 #21 0x7fb240630d2d in KXmlGuiWindow::event(QEvent*) (this=0x55b3a1fe69f0, ev=0x7fb22401f260) at /usr/src/debug/kf5-kxmlgui-5.85.0-1.fc34.x86_64/src/kxmlguiwindow.cpp:219 #22 0x7fb24311e443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55b3a1fe69f0, e=0x7fb22401f260) at kernel/qapplication.cpp:3632 #23 0x7fb242465798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55b3a1fe69f0,
[kmail2] [Bug 431948] Unable to add new imap account using auto detection
https://bugs.kde.org/show_bug.cgi?id=431948 --- Comment #1 from Geert Janssens --- Note if I try the manual method (without automatic detection of servers) I get to the Setting up Account page without console errors. However it eventually will fail as well on that page with the following console output: org.kde.pim.accountwizard: Did not find D-Bus method: "setAccountIdentity" available methods are: org.kde.pim.accountwizard: "destroyed(QObject*)" org.kde.pim.accountwizard: "destroyed()" org.kde.pim.accountwizard: "objectNameChanged(QString)" org.kde.pim.accountwizard: "deleteLater()" org.kde.pim.accountwizard: "_q_reregisterTimers(void*)" org.kde.pim.accountwizard: "_q_serviceOwnerChanged(QString,QString,QString)" org.kde.pim.accountwizard: Impossible to convert argument : QVariant(int, 1340438214) That is not the same error though seemingly in the same area. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 431948] New: Unable to add new imap account using auto detection
https://bugs.kde.org/show_bug.cgi?id=431948 Bug ID: 431948 Summary: Unable to add new imap account using auto detection Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: i...@kobaltwit.be Target Milestone: --- Created attachment 135067 --> https://bugs.kde.org/attachment.cgi?id=135067=edit Details of the failing "Setting up Account" page SUMMARY I'm trying to set up a new imap account in kmail for a GMail account. The account wizard offers to detect the proper settings and seems to do so successfully. However when I click the "Next" button on the "Secure your communication" page, I immediately get the error "Failed to set up the account" When starting kmail from the command line to get console output, I notice the following error printed in the terminal: org.kde.pim.accountwizard: Did not find D-Bus method: "setAuthentication" available methods are: org.kde.pim.accountwizard: "destroyed(QObject*)" org.kde.pim.accountwizard: "destroyed()" org.kde.pim.accountwizard: "objectNameChanged(QString)" org.kde.pim.accountwizard: "deleteLater()" org.kde.pim.accountwizard: "_q_reregisterTimers(void*)" org.kde.pim.accountwizard: "_q_serviceOwnerChanged(QString,QString,QString)" org.kde.pim.accountwizard: Impossible to convert argument : QVariant(int, 9) STEPS TO REPRODUCE 1. Open kmail 2. Choose settings "Add Account..." 3. Enter credentials for a gmail e-mail address (may be an issue with any imap account for which the server data is in the Mozilla database, I have only tested with a gmail account) 4. Enable "Find provider settings on the internet" if not enabled 5. Click next 6. Click "Add Account" 7. Click "Next" again OBSERVED RESULT After step 5. the assistant will properly show the discovered server addresses for the provided e-mail address. After step 6. the console error messages as mentioned above are printed. The assistant will at this point be showing the "Secure your Communication" page and doesn't show any signs of failure, although the console suggests something went wrong already at this point. After step 7. the "Setting up Account" page appears and it immediately states "Failed to set up account." I'll attach a screenshot with the details on this page. Note this is with kmail 5.15.2, which is no longer in the list above, but it's what is currently comes with an up to date Fedora 32 system. EXPECTED RESULT Account gets configured successfully. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 32 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.75.0 Qt Version: 5.14.2 Kmail2 version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 226321] allow printing of selected text/selected area
https://bugs.kde.org/show_bug.cgi?id=226321 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #3 from Geert Janssens --- I do understand there is a lot of things to work on in okular and only limited time. However I do cast my vote for this request. It would save a lot of time as I regularly get large pdfs that are too dense to print on a standard A4 printer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348047] Applications started on first Activity instead of where they were left
https://bugs.kde.org/show_bug.cgi?id=348047 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #2 from Geert Janssens --- I'm seeing the same with Dolphin and it has been like that for a long time. Perhaps the other mentioned applications behave the same, but I never keep those open so I haven't tested. I'm currently on Fedora 31, with Kde Plasma 5.17.1, Frameworks 5.68.0, Qt 5.13.2. I'm not sure these version numbers matter per se. It's bee like this for a very long time. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 419298] New: Big mails fail to display body
https://bugs.kde.org/show_bug.cgi?id=419298 Bug ID: 419298 Summary: Big mails fail to display body Product: kmail2 Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: i...@kobaltwit.be Target Milestone: --- SUMMARY I receive daily log mails from our servers. These text-only mails have a large body of text (> 3Mb). These messages fail to display in KMail. That is, they appear in the list of mails, but when clicking the mail the preview window will only show the smart header (subject, from, to) but the message body remains empty. The same goes when opening the mail in a new window (by double-clicking) the mail header in the message list). I can reproduce this both on Fedora 31 and Kubuntu 18.04 with the default installations of Kmail. STEPS TO REPRODUCE 1. Find a large text-only mail in one of your mailboxes. Mine are > 3Mb of text 2. Click on the mail in the message list OBSERVED RESULT Preview window will properly show the header info (subject, date, to, from,...) as with all other mails, but the message body is not displayed. That is, the rest of the preview window is just blank. EXPECTED RESULT The message body is also properly displayed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31 and Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.17.5 (Fedora) and 5.12.9 (Kubuntu) KDE Frameworks Version: 5.66.0 (Fedora) and 5.44.0 (Kubuntu) Qt Version: 5.13.2 (Fedora) and 4.15.0-1076-oem (Kubuntu) KMail Version: 5.11.3 (Fedora) and 5.7.3 (Kubuntu) ADDITIONAL INFORMATION I can open the same messages with no issues in Thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[pimsettingexporter] [Bug 331432] pimsettingsexporter forget to setup correctly the database
https://bugs.kde.org/show_bug.cgi?id=331432 Geert Janssens changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #6 from Geert Janssens --- I ran into the same issue today while trying to restore a configuration on a new laptop. On the original PC I am using pim-data-exporter-19.04.3-2.fc31.x86_64, on the laptop where I want to import I am using 4:17.12.3-0ubuntu1 . Both are the default ones shipped on the respective systems (being Fedora 31 and Ubuntu 18.04LTS). (In reply to Laurent Montel from comment #3) > We don't use same account name id so we can't do it. > How hard would it be to fix this ? I haven't looked at the code (yet). However I think it would be sufficient to export a map of the user-visible account names to account name ids in the backup file and reuse this map to recover e-mail folder names on restore. The data is available on the PC where the backup is created. Why can't it be added to the backup so it can be reused during restore ? > 2nd point: normal if we don't have connection we don't have folder tree. I > can't fix it if you can't connect to it. The issue I see here is not really being unable to connect, but trying to restore folders before actually connecting. When I do a restore I first get a question to choose a trash folder. This trash folder originally pointed at a folder on the imap server. Only after successfully setting a dummy folder the restore process will ask me to connect to the imap server. That's backwards. I would suggest the restore first tries to make all remote connections and only then start mapping folders. Combined with backing up more details of how the accounts were named by the user at the original pc this would tremendously improve the export/import experience. Note I'm also being asked for folders related to 'IDENTITY_12345679' multiple times. The 123456789 changes for each request. I have no idea what these mean exactly. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417628] New: Exclude filter in find/replace files dialog doesn't seem to work
https://bugs.kde.org/show_bug.cgi?id=417628 Bug ID: 417628 Summary: Exclude filter in find/replace files dialog doesn't seem to work Product: kdevelop Version: 5.5.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: i...@kobaltwit.be Target Milestone: --- SUMMARY For the last couple of releases I have some trouble to use the exclude file filter in the find/replace files dialog. No matter what I enter in there files matching the expressions in the exclude filter are searched anyway. For example, in my C++ project I set the exclude filter to "*.c", kdevelop still searches all c source files and will display search results in these c source files. This has been going on for a couple of releases (say at least a year), though unfortunately I can't recollect when exactly it started STEPS TO REPRODUCE 1. Open a project in kdevelop 2. Select Edit->Find/Replace in Files... 3. Enter something to search for and that you know is present in files you plan to exclude in the next step 4. Adjust the exclude step to exclude some files, for example "*.c" to exclude all c source files. 5. Run the search OBSERVED RESULT The search results will also show files that have been excluded via the exclude filter. EXPECTED RESULT Only show results from files that had not been excluded via the exclude filter. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 399270] File copying ignores setuid bit
https://bugs.kde.org/show_bug.cgi?id=399270 --- Comment #5 from Geert Janssens --- I don't agree it's the same. Your file generated using cp is this: -rw-r--r-- 1 ahmad users 10 Sep 24 00:16 copied-file Your file generated using copy in dolphin is this: -rw-r--r-- 1 ahmad ahmad 6 Sep 24 00:26 copied-file-with-dolphin Note the difference in group id! copied-file is owned by group "users", where copied-file-with-dolphin is owned by group "ahmad". Considering the group setuid bit was set on the containing directory, the command line copy's behaviour is the proper one. Dolphin's copy ignores this group setuid bit. However as we have both established, it only does so for files, not for directories. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 399270] File copying ignores setuid bit
https://bugs.kde.org/show_bug.cgi?id=399270 --- Comment #3 from Geert Janssens --- I'll add that since I reported this I have upgraded to frameworks-kio-5.59.0 (which is current on Fedora 30). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 399270] File copying ignores setuid bit
https://bugs.kde.org/show_bug.cgi?id=399270 Geert Janssens changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Geert Janssens --- (In reply to Ahmad Samir from comment #1) > Copied the the two above items using dolphin, and the result: > [~/test-setgid]>$ ls -l copied-file-with-dolphin > -rw-r--r-- 1 ahmad ahmad 6 Sep 24 00:26 copied-file-with-dolphin > [~/test-setgid]>$ ls -ld copied-dir-from-dolphin/ > drwxr-sr-x 2 ahmad users 4096 Sep 24 00:27 copied-dir-from-dolphin/ > > So it looks like it's the same behaviour as using cp from the cli. > > Can you still reproduce this issue? The file "copied-file-with-dolphin" in your output above shows exactly the issue I'm pointing out: its primary group is still ahmad instead of users. So it seems you are equally able to reproduce this issue... And I have just tested, it still happens for me as well. Interestingly it seems to go wrong for files only. The group id is set correctly on directories. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399270] New: File copying ignores setuid bit
https://bugs.kde.org/show_bug.cgi?id=399270 Bug ID: 399270 Summary: File copying ignores setuid bit Product: dolphin Version: 17.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: i...@kobaltwit.be CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Using dolphin to copy files into a directory which has the group setuid bit set, will ignore this bit. That means the files copied will have the primary group set of the user performing the copy instead of the group of the parent directory. STEPS TO REPRODUCE 1. Create a directory "test" with following permissions: rwx rws --- myuser commongroup That is the directory is accessible and modifyable by myuser and all members of commongroup. The "s" indicates the group setuid bit is set and should enforce that each file copied into this directory should get "commongroup" as group ownership The exact set of commands to set this up are - mkdir test - chmod u+rwx,g+rwxs,o= test - chgrp commongroup test Note commongroup must be an existing group which is not the primary group of user myuser for this test. 2. Start dolphin and copy any file into this test directory 3. Check file ownership via the command line: - ls -l test OBSERVED RESULT The group of the copied file is myuser's primary group EXPECTED RESULT The group of the copied file is "commongroup" as per the setuid bit behavior. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.48.0 Qt Version: 5.9.6 ADDITIONAL INFORMATION A copy on the command line using "cp" does the right thing. This erratic behavior makes it unnecessarily hard to share files in a networked multi-user environment. In the past a similar bug was reported against gwenview: bug 149148. As that bug is closed and I'm seeing this in dolphin, I chose to create a new bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 Geert Janssens changed: What|Removed |Added Version|unspecified |5.48.0 --- Comment #8 from Geert Janssens --- Oh, I should have updated my version information: Dolphin is currently at dolphin-17.12.2-2.fc27.x86_64 KDE Frameworks at 5.48 Please let me know if you need additional details. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 Geert Janssens changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #7 from Geert Janssens --- I am reopening this bug as it happened to me again yesterday, exact same scenario as described in comment 4. It's probably a corner case, but it's a pretty annoying one that really offsets my less experienced users. The fact things work fine on the command line but not in dolphin suggests it's something in the way kde deals with network file system permissions. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 289107] Kontact crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=289107 --- Comment #13 from Geert Janssens --- I haven't seen this happening any more recently. My current version of Kontact is 5.7.3. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377150] Use real attachment's file name when opening an attachment
https://bugs.kde.org/show_bug.cgi?id=377150 --- Comment #2 from Geert Janssens --- I'm not seeing this issue any more with more recent versions of KMail (currently running 5.7.3). So as far as I'm concerned this bug is now fixed. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 307967] Plasma and Dolphin hang when changing network interfaces
https://bugs.kde.org/show_bug.cgi?id=307967 --- Comment #5 from Geert Janssens --- My Fedora system currently has KDE Frameworks 5.48 and I'm not seeing these delays any more. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 385846] Baloo file indexer crashes on login
https://bugs.kde.org/show_bug.cgi?id=385846 --- Comment #2 from Geert Janssens <i...@kobaltwit.be> --- How can I clean the db ? I have searched for this but didn't find an obvious answer. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 391605] Kaddressbook crashes when double-clicking on a name in the contacts list
https://bugs.kde.org/show_bug.cgi?id=391605 --- Comment #2 from Geert Janssens <i...@kobaltwit.be> --- Ah, that fixes it indeed. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 391605] New: Kaddressbook crashes when double-clicking on a name in the contacts list
https://bugs.kde.org/show_bug.cgi?id=391605 Bug ID: 391605 Summary: Kaddressbook crashes when double-clicking on a name in the contacts list Product: kaddressbook Version: 5.7.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: i...@kobaltwit.be CC: to...@kde.org Target Milestone: --- Application: kaddressbook (5.7.2) Qt Version: 5.9.4 Frameworks Version: 5.43.0 Operating System: Linux 4.15.6-300.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: - What I was doing when the application crashed: I opened my addressbook, then double clicked on one of the names in there. The contact's card briefly opens and then results in the segmentation fault I'm reporting here. Single clicking works ok, the preview panel nicely shows the selected contact's details. The issue happens both when opening the addressbook from within kontact or as a standalone application. The addressbook is an owncloud (webdav) remote address book, configured to connect to a selfhosted Nextcloud instance. The crash can be reproduced every time. -- Backtrace: Application: KAddressBook (kaddressbook), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 27return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7fcc8fd72e00 (LWP 9646))] Thread 5 (Thread 0x7fcc521ab700 (LWP 9651)): #0 g_mutex_unlock (mutex=0x7fcc4c000bf0) at gthread-posix.c:1348 #1 0x7fcc7f0c0399 in g_main_context_prepare (context=context@entry=0x7fcc4c000bf0, priority=priority@entry=0x7fcc521aab20) at gmain.c:3508 #2 0x7fcc7f0c0dcb in g_main_context_iterate (context=context@entry=0x7fcc4c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3848 #3 0x7fcc7f0c0fac in g_main_context_iteration (context=0x7fcc4c000bf0, may_block=may_block@entry=1) at gmain.c:3929 #4 0x7fcc89b4fc4b in QEventDispatcherGlib::processEvents (this=0x7fcc4c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fcc89afd96a in QEventLoop::exec (this=this@entry=0x7fcc521aac60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7fcc8994e8ca in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7fcc89952de2 in QThreadPrivate::start (arg=0x55f7d354b310) at thread/qthread_unix.cpp:368 #8 0x7fcc86e0361b in start_thread (arg=0x7fcc521ab700) at pthread_create.c:465 #9 0x7fcc88cefc2f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fcc5b5ef700 (LWP 9649)): #0 __tls_get_addr () at ../sysdeps/x86_64/tls_get_addr.S:46 #1 0x7fcc89951d46 in get_thread_data () at thread/qthread_unix.cpp:189 #2 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:244 #3 0x7fcc89b4fb3a in postEventSourcePrepare (s=0x7fcc540047a0, timeout=timeout@entry=0x7fcc5b5eea94) at kernel/qeventdispatcher_glib.cpp:252 #4 0x7fcc7f0c03f9 in g_main_context_prepare (context=context@entry=0x7fcc54000bf0, priority=priority@entry=0x7fcc5b5eeb20) at gmain.c:3440 #5 0x7fcc7f0c0dcb in g_main_context_iterate (context=context@entry=0x7fcc54000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3848 #6 0x7fcc7f0c0fac in g_main_context_iteration (context=0x7fcc54000bf0, may_block=may_block@entry=1) at gmain.c:3929 #7 0x7fcc89b4fc4b in QEventDispatcherGlib::processEvents (this=0x7fcc54000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7fcc89afd96a in QEventLoop::exec (this=this@entry=0x7fcc5b5eec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #9 0x7fcc8994e8ca in QThread::exec (this=) at thread/qthread.cpp:515 #10 0x7fcc89952de2 in QThreadPrivate::start (arg=0x55f7d34c30c0) at thread/qthread_unix.cpp:368 #11 0x7fcc86e0361b in start_thread (arg=0x7fcc5b5ef700) at pthread_create.c:465 #12 0x7fcc88cefc2f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fcc60ec0700 (LWP 9648)): #0 0x7fcc88cdeb28 in __GI___libc_read (fd=17, buf=buf@entry=0x7fcc60ebfa00, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fcc7f1050a0 in read (__nbytes=16, __buf=0x7fcc60ebfa00, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x55f7d3423ab0) at gwakeup.c:210 #3 0x7fcc7f0c09a8 in g_main_context_check (context=context@entry=0x7fcc5c000bf0, max_priority=2147483647, fds=fds@entry=0x7fcc5c004db0, n_fds=n_fds@entry=1) at gmain.c:3646 #4 0x7fcc7f0c0e40 in g_main_context_iterate (context=context@entry=0x7fcc5c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3865 #5 0x7fcc7f0c0fac in
[kmail2] [Bug 386023] Unable to delete multiple emails at once
https://bugs.kde.org/show_bug.cgi?id=386023 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Geert Janssens <i...@kobaltwit.be> --- Fedora has upgraded to KMail 5.7.0 and I'm happy to report this issue is now fixed. I can delete multiple mails in one go again. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 387908] New: Crash while correcting entered text
https://bugs.kde.org/show_bug.cgi?id=387908
Bug ID: 387908
Summary: Crash while correcting entered text
Product: krunner
Version: 5.10.5
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@privat.broulik.de
Reporter: i...@kobaltwit.be
Target Milestone: ---
Application: krunner (5.10.5)
Qt Version: 5.7.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.12-200.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"
-- Information about the crash:
- What I was doing when the application crashed:
I had activated krunner using the F2 key.
Then I started entering a query ("konta") in this case, which got autocompleted
to "Kontact"
Next I realized I didn't want to search for kontact, but rather for calc,
so using the backspace I removed the entered text.
I believe I also started to type "calc", but somewhere at that point krunner
crashed.
This happens occasionally and I seem to remember most of these occasions are
when I correct the text I have entered.
The crash can be reproduced sometimes.
-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
88int err = lll_futex_timed_wait (futex_word, expected, NULL, private);
[Current thread is 1 (Thread 0x7f2158da7380 (LWP 1635))]
Thread 25 (Thread 0x7f20c24e2700 (LWP 23691)):
#0 0x7f215489bd2d in poll () at ../sysdeps/unix/syscall-template.S:84
#1 0x7f214c808569 in g_main_context_poll (priority=,
n_fds=1, fds=0x7ee0a8002eb0, timeout=, context=0x7ee0a8000990)
at gmain.c:4271
#2 0x7f214c808569 in g_main_context_iterate
(context=context@entry=0x7ee0a8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3967
#3 0x7f214c80867c in g_main_context_iteration (context=0x7ee0a8000990,
may_block=1) at gmain.c:4033
#4 0x7f21556b7e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5 0x7f215566860a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6 0x7f21554c099a in QThread::exec() () at /lib64/libQt5Core.so.5
#7 0x7f21554c4c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8 0x7f21512aa36d in start_thread (arg=0x7f20c24e2700) at
pthread_create.c:456
#9 0x7f21548a7e1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97
Thread 24 (Thread 0x7f20c2ce3700 (LWP 23688)):
#0 0x7f214c84d4c4 in g_mutex_unlock (mutex=0x7ee0b4000990) at
gthread-posix.c:1348
#1 0x7f214c808686 in g_main_context_iteration (context=0x7ee0b4000990,
may_block=) at gmain.c:4034
#2 0x7f21556b7e6b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#3 0x7f215566860a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#4 0x7f21554c099a in QThread::exec() () at /lib64/libQt5Core.so.5
#5 0x7f21554c4c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#6 0x7f21512aa36d in start_thread (arg=0x7f20c2ce3700) at
pthread_create.c:456
#7 0x7f21548a7e1f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97
Thread 23 (Thread 0x7f20d67fc700 (LWP 4145)):
#0 0x7f21512b090b in futex_wait_cancelable (private=,
expected=0, futex_word=0x55f598aad1a4) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 0x7f21512b090b in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55f598aad150, cond=0x55f598aad178) at pthread_cond_wait.c:502
#2 0x7f21512b090b in __pthread_cond_wait (cond=0x55f598aad178,
mutex=0x55f598aad150) at pthread_cond_wait.c:655
#3 0x7f21554c53fb in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#4 0x7f21303df0d5 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#5 0x7f21303e3048 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#6 0x7f21303de29d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#7 0x7f21303e30a2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#8 0x7f21303de29d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#9 0x7f21303e30a2 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#10 0x7f21303de29d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#11 0x7f21303e0f8b in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#12 0x7f21554c4c9e in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#13 0x7f21512aa36d in
[frameworks-kio] [Bug 364662] Opening URLs is very slow or aborted completely
https://bugs.kde.org/show_bug.cgi?id=364662 --- Comment #8 from Geert Janssens <i...@kobaltwit.be> --- Oops, that was a typo in comment 6 indeed. I meant to refer to the bug that was actually set as a duplicate of this one. Sorry about the confusion. The core remains though, I'd very much like to see this one fixed, although the helpful workaround does reduce the urgency. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 386023] New: Unable to delete multiple emails at once
https://bugs.kde.org/show_bug.cgi?id=386023 Bug ID: 386023 Summary: Unable to delete multiple emails at once Product: kmail2 Version: 5.5.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: i...@kobaltwit.be Target Milestone: --- When I select multiple mails at once and then hit the delete key, the mails disappear for a fraction of a second and then return to the list. I suspect the mails are deleted on the server side though because 1. looking at the same mail folder with thunderbird, the messages are gone 2. restarting kontact/kmail updates the list correctly Also before restarting kontact/kmail (and after hitting the delete key), these messages do appear in the trash folder (both in kmail and thunderbird). So it seems kmail (or akonadi?) is getting confused when I try to delete multiple messages at once. It's unfortunately not happening each time. But I can easily reproduce it 99% of the time. I haven't figured out yet what's different in the 1% where it does work. It seems like it works when the program is first started and I haven't manipulated any mails yet, but that's just a first guess. I didn't see this problem with kmail 5.4.3 (the current default on Fedora 25). The issues started after upgrading my system to Fedora 26, which ships kmail 5.5.1 at present. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 385847] New: Kontact crashes on restart
https://bugs.kde.org/show_bug.cgi?id=385847 Bug ID: 385847 Summary: Kontact crashes on restart Product: kontact Version: 5.5.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: i...@kobaltwit.be Target Milestone: --- Application: kontact (5.5.1) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.13.5-200.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: As Kontact was not properly updating the message list when I delete a message, I quit the application and restarted it. While starting up again, this crash notification appears. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0aff04ff00 (LWP 4277))] Thread 39 (Thread 0x7f0ad27fc700 (LWP 6333)): #0 0x7f0b170d3acd in poll () at /lib64/libc.so.6 #1 0x7f0b08af8569 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f0b08af867c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f0b17eebe4f in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0b17e9c60a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f0b17cf499a in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f0b17cf8c9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f0b0d5ba36d in start_thread () at /lib64/libpthread.so.0 #8 0x7f0b170dfbbf in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7f0ad2ffd700 (LWP 6322)): #0 0x7f0b0d5c0e0a in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0b10ca6172 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f0b10c7c229 in base::PosixDynamicThreadPool::WaitForTask() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f0b10c7c78b in base::(anonymous namespace)::WorkerThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f0b10c7506b in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f0b0d5ba36d in start_thread () at /lib64/libpthread.so.0 #6 0x7f0b170dfbbf in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7f09e61f9700 (LWP 6320)): #0 0x7f0b170cf1cd in read () at /lib64/libc.so.6 #1 0x7f0b08b3c170 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f0b08af8078 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f0b08af8510 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f0b08af867c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f0b17eebe6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f0b17e9c60a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f0b17cf499a in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f0b17cf8c9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f0b0d5ba36d in start_thread () at /lib64/libpthread.so.0 #10 0x7f0b170dfbbf in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7f09b2f41700 (LWP 4366)): #0 0x7f0b170d3acd in poll () at /lib64/libc.so.6 #1 0x7f0b08af8569 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f0b08af867c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f0b17eebe6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0b17e9c60a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f0b17cf499a in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f0b17cf8c9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f0b0d5ba36d in start_thread () at /lib64/libpthread.so.0 #8 0x7f0b170dfbbf in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7f09ba68f700 (LWP 4344)): #0 0x7f0b0d5c090b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0b10c77725 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f0b10c77c07 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f0b10c789a1 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f0b10c7506b in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f0b0d5ba36d in start_thread () at /lib64/libpthread.so.0 #6 0x7f0b170dfbbf in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7f09d0e96700 (LWP 4334)): #0 0x7f0b170d3acd in poll () at /lib64/libc.so.6 #1 0x7f0b08af8569 in
[frameworks-baloo] [Bug 385846] New: Baloo file indexer crashes on login
https://bugs.kde.org/show_bug.cgi?id=385846 Bug ID: 385846 Summary: Baloo file indexer crashes on login Product: frameworks-baloo Version: 5.36.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: i...@kobaltwit.be Target Milestone: --- Application: baloo_file_extractor (5.36.0) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.13.5-200.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: I get this crash notification during login in my plasma session. It has happened more than once by now. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe6c9d488c0 (LWP 3591))] Thread 2 (Thread 0x7fe6ab770700 (LWP 3604)): #0 0x7fe6c6d41acd in poll () at /lib64/libc.so.6 #1 0x7fe6c28ea569 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fe6c28ea67c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fe6c7b59e6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fe6c7b0a60a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fe6c796299a in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fe6c9e6aa39 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fe6c7966c9e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fe6c628636d in start_thread () at /lib64/libpthread.so.0 #9 0x7fe6c6d4dbbf in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fe6c9d488c0 (LWP 3591)): [KCrash Handler] #6 0x7fe6c9126c7b in Baloo::IdFilenameDB::get(unsigned long long) () at /lib64/libKF5BalooEngine.so.5 #7 0x7fe6c912064a in Baloo::DocumentUrlDB::get(unsigned long long) const () at /lib64/libKF5BalooEngine.so.5 #8 0x7fe6c9130fa4 in Baloo::Transaction::documentUrl(unsigned long long) const () at /lib64/libKF5BalooEngine.so.5 #9 0x55744fc28fe8 in Baloo::App::processNextFile() () #10 0x7fe6c7b3e954 in QSingleShotTimer::timerEvent(QTimerEvent*) () at /lib64/libQt5Core.so.5 #11 0x7fe6c7b3388b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #12 0x7fe6c83565dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7fe6c835dc74 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7fe6c7b0b627 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #15 0x7fe6c7b5948b in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #16 0x7fe6c7b599d1 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #17 0x7fe6c28ea247 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #18 0x7fe6c28ea5e8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #19 0x7fe6c28ea67c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #20 0x7fe6c7b59e4f in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #21 0x7fe6c7b0a60a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7fe6c7b1227c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #23 0x55744fc2819f in main () Possible duplicates by query: bug 373006. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 364662] Opening URLs is very slow or aborted completely
https://bugs.kde.org/show_bug.cgi?id=364662 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #6 from Geert Janssens <i...@kobaltwit.be> --- While bug 354216 was marked as a duplicate of this one, it describes the root cause much better: kde-open5 is not coping well with several http(s) variants. As this bug is kept open and the bug 354216 marked as a duplicate, it may be useful to change the title of this bug to reflect this cause. I'm hitting this same issue mostly when clicking on links in mail messages in KMail, presently with kmail 17.04.1 on Fedora 26. Before stumbling on this bug I thought kde-open5 was mangling certain urls (like improperly escaping special characters such as '#', '&', '?' and similar), but now I believe it's the improper redirection handling that's causing most of it. So I'd be very happy to see some progress on this bug. Unfortunately I don't know the kde codebase at all so I'm not in a position to answer Andrea's questions in comment 5. Can someone else chime in ? Thanks. And lastly, the workaround suggested in comment 3 works for me for now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 220297] Kmail delete message no longer centers next selected message in message list
https://bugs.kde.org/show_bug.cgi?id=220297 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #11 from Geert Janssens <i...@kobaltwit.be> --- Kmail 5.4.3 and this issue is still happening for me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #6 from Geert Janssens <i...@kobaltwit.be> --- I have resolved this issue by exporting directories outside of the /home directory on the server. It seems like there is some security feature interfering with exporting directories under /home. I never was able to figure out whether this is something in nfs or selinux or whatever. So works for me now. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 356785] kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5
https://bugs.kde.org/show_bug.cgi?id=356785 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Geert Janssens <i...@kobaltwit.be> --- Now that most of the applications I use have switched to kf5, I no longer have a use case to test this. And since no other users have confirmed this, I'll just close this bug again. I'm hesitating on the resolution reason as none really fit the bill. I'll choose "Unmaintained". If that's a wrong choice, feel free to correct it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376520] KMail forget to display html mail and fetch pics set in global settings
https://bugs.kde.org/show_bug.cgi?id=376520 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #1 from Geert Janssens <i...@kobaltwit.be> --- I observe the same behaviour with kmail-16.08.3 on Fedora 25 (kmail 5.3.3). Steps to reproduce: - Open Kmail preferences, disable "Prefer Html to plain text" and re-enable it. - Hit ok -> Kmail will warn all folder specific settings will be overwritten, accept this => At this point kmail will effectively prefer html to plain text for any mail message you have like this. - quit kmail - restart kmail => At this point kmail has reverted to preferring plain text to html - Open kmail preferences => Observe the setting "Prefer Html to plain text" is still active So clearly something goes wrong during startup of kmail. Either the setting is not queried at all at startup or the per-folder preferences are configured before the global setting is loaded. Or something like that. This is highly confusing for less experienced users and a reason to hold off upgrading them to kmail 5.3.3. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377150] New: Use real attachment's file name when opening an attachment
https://bugs.kde.org/show_bug.cgi?id=377150 Bug ID: 377150 Summary: Use real attachment's file name when opening an attachment Product: kmail2 Version: 5.3.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: i...@kobaltwit.be Target Milestone: --- When opening an attachment directly from the mail, it is saved to /tmp first with a name like "messageviewer_.pdf", and so that's the name that also will be used by the application opening the attachment. This behaviour has changed recently. Before the temporary name was the actual name of the attachment, optionally with a number appended to it if the original name already existed in the tmp folder. The new behaviour is rather inconvenient because the file name often has meaning. Some examples of the issues this generic naming brings with it: - the name of the attachment you see in the e-mail has no link any more with the name of the file that is open. So it's hard to link back the open file to an e-mail. This gets more increasingly hard as you open more attachments from different e-mails. - when opening multiple attachments it is no longer evident from the taskbar which file is which because they are all named 'messageviewer_xyz.ext' Switching files from the taskbar after several are open has become a hit and miss. - when you have opened an attachment, you may decide to resave it (to a location other than tmp) directly from the application that is used to open the attachment (libreoffice or okular for example). You typically do this by using "Save as". However the proposed name in that dialog is now 'messageviewer_xyz.ext' rather than the much more descriptive name the attachment originally had in the mail. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368434] Kontact crash when filing through eMail
https://bugs.kde.org/show_bug.cgi?id=368434 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added CC||i...@kobaltwit.be -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 343996] Some parts of the document aren't printed
https://bugs.kde.org/show_bug.cgi?id=343996 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|UPSTREAM|--- --- Comment #4 from Geert Janssens <i...@kobaltwit.be> --- Hmm, upstream claims it's an okular bug, because they can't reproduce in evince which also uses poppler... (see upstream bug in previous comment). Can I ask you guys to talk to each other directly to clear this out ? I have no knowledge at all of the internals of either poppler or okular, so I can't add much more than "it doesn't work here" and run tests if you ask me to. Thanks! I have reopened this bug to indicate there is still an issue that's not cleared out and upstream doesn't agree it's their issue. If you don't agree, by all means change the state again, but please communicate with upstream to explain why you believe the bug is in poppler. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 --- Comment #5 from Geert Janssens <i...@kobaltwit.be> --- And I found a blog reporting this same issue on Arch linux: http://kdeblog.mageprojects.com/2016/06/24/plasma-5-6-clean-installation-impression/ So it doesn't appear to be distro specific. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 --- Comment #4 from Geert Janssens <i...@kobaltwit.be> --- Unfortunately a recent updated to plasma 5.6.2 and related kf5 5.21 brings back the issue in Dolphin as well (which is at version 15.12.3 on my Fedora 23 installation). I already reported this in the Fedora bug mentioned in comment 1, but forgot to update here. I was able to narrow down the poor behaviour a bit more as well: - example simple directory hierarchy: nfs-share \ subdir \ sub-subdir so the nfs share "nfs-share" has one subdirectory called "subdirectory" and in that directory there's another subdirectory called "sub-subdirectory" - current user is "janssege" - user janssege is member of "goudsmid", though it's not his primary group - nfs-share is owned by goudsmid:goudsmid and has permissions rwxrwx--- => user can view contents of the share, but not contents of subdirectories on the share in Dolphin and friends Change permissions to rwxrwx--x => user can also view contents of subdirectories on the share The permissions on subdirectory will likewise define whether I can see the contents of sub-subdirectory. If the permissions of subdirectory are rwxrwx---, the contents of sub-subdirectory is empty, of they are rwxrwx--x, I can see the contents. Navigating back up from sub-subdirectory (when I can't see it's contents) will bring me back to subdirectory, but it will no longer have sub-subdirectory listed in its contents. That is restored by hitting F5. It also still stands that I can navigate to sub-subdirectory in all circumstances above from a konsole window or in nautilus and will always see its contents. And also when explicitly typing the address in dolphin's address bar, the suggestion dropdown properly suggests all subdirectories, regardless of the permissions. So it's apparently limited to the widget that should display the contents of the directory. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 --- Comment #3 from Geert Janssens <i...@kobaltwit.be> --- It would really be great if whatever was needed to fix this for kf5 based applications to be applied to the kde4 environment as well. This is a blocker for most of my users (which are not computer-savvy at all). Some examples of where this interferes: - saving attachments from within kmail - saving a copy of a pdf document from within okular (frequently done to re-save a pdf downloaded from the internet). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 --- Comment #2 from Geert Janssens <i...@kobaltwit.be> --- Some further evolution. It looks like this bug is fixed for kf5 based applications. Current Dolphin (dolphin-15.12.1-1.fc23.x86_64) no longer has this issue. KDE 4 based applications still behave erratically. For example, current okular still won't properly show the contents of an nfs share not owned by the logged in user. Note also that even though the folder contents is not shown (or only briefly), I can still navigate deeper down the hierarchy by typing the the address bar. This still correctly autocompletes as well. So it's really something in the folder content view area that's messed up. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 334080] kdeconnect,some sent photo are uncomplete
https://bugs.kde.org/show_bug.cgi?id=334080 --- Comment #30 from Geert Janssens <i...@kobaltwit.be> --- I noticed version 0.9g got released recently, which triggered me to try again. Current versions in use are: PC: - Fedora 22 - kdeconnect 0.9g Smartphone - kdeconnect 0.9e With these versions I haven't been able to reproduce this bug. All videos I sent directly from the gallery using kdeconnect were properly transferred. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 --- Comment #1 from Geert Janssens <i...@kobaltwit.be> --- This is also reported in the Fedora bug tracker as https://bugzilla.redhat.com/show_bug.cgi?id=1269987 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] New: KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 Bug ID: 356791 Summary: KDE Applications won't show contents of nfs mount (automount) Product: frameworks-kio Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: i...@kobaltwit.be CC: kdelibs-b...@kde.org KDE gui applications such as Dolphin or kde gui componenents such as the File Open dialog fail to show the contents of some automounted nfs partitions. I have attached a screenshot to illustrate the issue. I have captured 4 different applications attempting to display the contents of /kobaltnet/goudsmid/bin /kobaltnet is the base mount point for my autofs mounted nfs shares. goudsmid is one such share. 1. In the top-left you see Konsole running a bash session. It can list the contents of the directory just fine 2. Top-right is dolphin, which just shows an empty directory 3. Bottom-left is nautilus, which shows the directory contents just fine 4. Bottom-right is the file-open dialog for okular, listing an empty directory Version-Release number of selected component (if applicable): I'm not sure I chose the right component. I don't really know which part of kde/plasma is responsible for this. Anyway, I see this with 5.4.1-3 and up (also the updates in updates-testing). There are a few remarkable details that are important: - this only happens with nfs shares I'm not the owner of (my id is janssege in the screenshot, the nfs share is owned by user goudsmid). When I access shares I do own, this behaviour doesn't show. - the behaviour starts from the second level down the mount point. In the example, I can see the contents of /kobaltnet/goudsmid, but not of any of its subdirectories. - hitting F5 on the empty contents does shortly reveal the contents (it flashes a fraction of a second) and the the window goes blank again. So this suggests the directory contents is properly written but then discarded from some reason. Reproducible: Always Steps to Reproduce: 1. Set up an nfs share which is automounted, not owned by you, but with proper group access permissions 2. Open dolphin and navigate to the mounted share. The contents will be visible. 3. Continue to navigate to a subdirectory. 4. Hit F5 Actual Results: 3. The contents of the subdirectory won't be shown 4. The actual contents briefly flashes in the window, but won't show permanently. Expected Results: Normal navigation through the share and all of it's subdirectories. The other applications (konsole/bash and nautilus) illustrate there's no access/file permission issue causing this. This change is fairly recent. I know I recently updated to plasma 5.4.1 from 5.3.x. However the KDE frameworks were also recently updated, so perhaps that's the culprit. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 356785] New: kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5
https://bugs.kde.org/show_bug.cgi?id=356785 Bug ID: 356785 Summary: kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5 Product: kwallet-pam Version: 5.4.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: i...@kobaltwit.be I have installed pam-kwallet-5.4.2-1 from updates-testing. This version should be able to open both kwallet4 and kwallet5 at login. However 9 times out of 10 I am still asked for a password for kwallet4 on login. Kwallet5 is always opened without asking for a password. Reproducible: Always Steps to Reproduce: 1. Install pam-kwallet-5.4.2-1, kde-runtime-15.08.1-2.fc22.x86_64 (for kde4's kwallet), kf5-kwallet-5.14.0-1.fc22.x86_64 (for kf5's kwallet). Optionally also install kde4's and kf5's version of kwalletmanager for easy testing. 2. Make sure you use the same password for login, and the default wallets in both versions 3. Log in to the system and verify which wallets are opened automatically Actual Results: On my system, kf5's default wallet is always opened, while kde4's default wallet isn't. I remember it worked a couple of times early on. Expected Results: Both default wallets should be opened at login. I have tested this with a recent version of sddm (0.12..0-5). I am aware old versions won't work. A couple of links that may be of interest: * https://quickgit.kde.org/?p=kwallet-pam.git=shortlog=352904c7500e44fcc6788291244882484c7b5962 is the git commit log for pam-kwallet on branch 5.4. Commits on 2015-07-28 are related to getting this functionality to work with both versions of kwallet at the same time. * http://martys.typepad.com/blog/2015/07/kwallet5-can-be-auto-unlocked-during-login-again.html?cid=6a012876e7556d970c01b7c7c640fc970b was the announcement of this feature. The comments have some discussion on initial issues with it, leading to the commits I refer to in the previous link. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 327316] KTorrent slows down my computer overall and boots me off the network
https://bugs.kde.org/show_bug.cgi?id=327316 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #1 from Geert Janssens <i...@kobaltwit.be> --- I'm seeing similar behaviour with ktorrent-4.3.1-14.fc22.x86_64 on Fedora 22, although only if I keep the ktorrent window open. When I minimize it to the systray it runs fine. A potential memory leak in the main window code perhaps ? -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 307967] Plasma and Dolphin hang when changing network interfaces
https://bugs.kde.org/show_bug.cgi?id=307967 Geert Janssens <i...@kobaltwit.be> changed: What|Removed |Added CC||i...@kobaltwit.be --- Comment #1 from Geert Janssens <i...@kobaltwit.be> --- I ran into this same problem yesterday on Fedora 23. This runs plasma 5.5.0-2.fc23.x86_64. This is probably going on for quite some time already as I'm experiencing a lot of system instabilities for a couple of months (and I'm a heavy user of nfs mounts via autofs, though not for home directories directly). -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 356785] kwallet4 still asks for password although pam-kwallet should open both kwallet4 and kwallet5
https://bugs.kde.org/show_bug.cgi?id=356785 --- Comment #1 from Geert Janssens <i...@kobaltwit.be> --- I also reported this earlier to the Fedora bug tracker as https://bugzilla.redhat.com/show_bug.cgi?id=1273773 -- You are receiving this mail because: You are watching all bug changes.
