[valgrind] [Bug 348909] Support OS X 10.11 (El Capitan)
https://bugs.kde.org/show_bug.cgi?id=348909 René Schwaiger changed: What|Removed |Added CC|sansseco...@me.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481720] Could not delete /home/mine/��� .
https://bugs.kde.org/show_bug.cgi?id=481720 --- Comment #2 from René --- Yes, it looks like a regression of that bug. I cannot rename nor delete the filename like I see in the various comments before the fix came out. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481720] New: Could not delete /home/mine/��� .
https://bugs.kde.org/show_bug.cgi?id=481720 Bug ID: 481720 Summary: Could not delete /home/mine/��� . Classification: Applications Product: dolphin Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: r...@comunica2.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I discovered a file of unknown origin with the weird name ��� in my home folder. When I tried to delete it (permanently) the error message was shown as in summary. STEPS TO REPRODUCE 1. Open Konsole and create the weird file name with 'touch ''$'\372\365\311\003' 2. Open Dolphin and attempt to delete the file OBSERVED RESULT Error message as in Summary and file not deleted. EXPECTED RESULT File deleted like usual SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Work around is to go to Konsole where you will discover the weird name's true spelling with 'ls' allowing you to delete it with 'rm' -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481702] Slow and high CPU when folder contain big ".desktop" file(s)
https://bugs.kde.org/show_bug.cgi?id=481702 René Paw Christensen changed: What|Removed |Added CC||r...@rpc-scandinavia.dk -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481702] New: Slow and high CPU when folder contain big ".desktop" file(s)
https://bugs.kde.org/show_bug.cgi?id=481702 Bug ID: 481702 Summary: Slow and high CPU when folder contain big ".desktop" file(s) Classification: Applications Product: dolphin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: r...@rpc-scandinavia.dk CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin tries to process ".desktop" file, even when it is not a text file, and when it is big. This results in a unresponsive window. The solution is to set a size limit, on how big ".desktop" files Dolphin should process. STEPS TO REPRODUCE 1. Create a folder and copy a big file to it (150 MB) 2. Rename the file to ".desktop" or ".Desktop" extension 3. Browse the folder in Dolphin OBSERVED RESULT The window does not respond, the CPU goes high. I expect that Dolphin tries to process the big file, because it thinks it is a text ".desktop" file. EXPECTED RESULT Dolphin ignorees (do not process) big ".desktop" files, perhaps > 1 MB. SOFTWARE/OS VERSIONS Dolphin: 24.02.0 Linux/KDE Plasma: 6.0.0 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Nothing. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 René changed: What|Removed |Added CC||r...@comunica2.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471984] New: Broken drag and drop of selectable text within konsole
https://bugs.kde.org/show_bug.cgi?id=471984 Bug ID: 471984 Summary: Broken drag and drop of selectable text within konsole Classification: Applications Product: konsole Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: r...@comunica2.net Target Milestone: --- SUMMARY Like in previous versions I try to select text then (ctrl+) drag and drop it on the command prompt, to save me typing paths or filenames. No longer works. STEPS TO REPRODUCE 1. Select text with the mouse pointer, 2. Ctrl+drag the selected text down or anywhere 3. Drop the text OBSERVED RESULT No drag nor drop takes place EXPECTED RESULT The dragged text is pasted / copied to the cursor location on command prompt. This worked in previous versions I used (functionality regression). SOFTWARE/OS VERSIONS Linux : Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: Wayland ADDITIONAL INFORMATION Work around is doing ctrl+c and ctrl+v but that unnecessarily "contaminates" the clipboard. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441384] Dolphin's UI responsiveness becomes slow while counting items inside subfolders in an NTFS partition
https://bugs.kde.org/show_bug.cgi?id=441384 --- Comment #9 from René Fritz --- (In reply to René Fritz from comment #8) > KDE neon 5.27 22.04 (x86_64) > > I have the same Problem but with ext4. > > It seems dolphin in kde neon has git functionality included - even when the > dolphin-plugins package for git support is NOT installed. > > Dolphin shows icons with git status. Directories with many git repositories > take ages to count. The gui is laggy. > > A folder without git repositories is faster, but not lightning fast. I realised Kommit (Git gui client for KDE) was installed and caused the slow down. Which means my problem was not related to the bug report. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441384] Dolphin's UI responsiveness becomes slow while counting items inside subfolders in an NTFS partition
https://bugs.kde.org/show_bug.cgi?id=441384 René Fritz changed: What|Removed |Added CC||rf-...@colorcube.de --- Comment #8 from René Fritz --- KDE neon 5.27 22.04 (x86_64) I have the same Problem but with ext4. It seems dolphin in kde neon has git functionality included - even when the dolphin-plugins package for git support is NOT installed. Dolphin shows icons with git status. Directories with many git repositories take ages to count. The gui is laggy. A folder without git repositories is faster, but not lightning fast. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #157 from René Fritz --- KDE Neon 5.27.2 The bug is fixed for me. - Login in with the monitors already connected: works - connecting monitors after login: works Many Thanks for fixing this bug! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #117 from René Fritz --- > For me the bug is not resolved in kde neon unstable. Well it has changed a little bit. There's the new widget in the taskbar. When I click in "extend to right" it doesn't work. A second click brings up the external display. In tests with kcontrol panel I can activate the monitor but not always. This didn't work for me before. It was almost impossible to activate the monitor. Still plugging in the cable doesn't work. Sometimes all screens are black and nothing happens. Unplug shows the default screen again. The layout is not restored. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11 with proprietary NVIDIA GPU drivers, external monitor disabled after reboot or wake-from-sleep
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #116 from René Fritz --- For me the bug is not resolved in kde neon unstable. I installed related packages in my kde neon user by adding deb http://archive.neon.kde.org/unstable jammy main I tried to identity the packages. There's no libkscreen package... > Plasma things to be "5.26.80", not "5.26.5". There aren't any packages with version 5.26.80 in KDE Neon unstable. So maybe I'm on the wrong track? Here are the updated packages (some unrelated) kscreen (4:5.26.5+p22.04+tunstable+git20230118.0241-0) kwin-common (4:5.26.5+p22.04+tunstable+git20230118.0014-0) kwin-data (4:5.26.5+p22.04+tunstable+git20230118.0014-0) kwin-wayland (4:5.26.5+p22.04+tunstable+git20230118.0014-0) kwin-wayland-backend-drm (4:5.26.5+p22.04+tunstable+git20230118.0014-0) kwin-wayland-backend-fbdev (4:5.26.5+p22.04+tunstable+git20230118.0014-0) kwin-wayland-backend-virtual (4:5.26.5+p22.04+tunstable+git20230118.0014-0) kwin-wayland-backend-wayland (4:5.26.5+p22.04+tunstable+git20230118.0014-0) kwin-wayland-backend-x11 (4:5.26.5+p22.04+tunstable+git20230118.0014-0) kwin-x11 (4:5.26.5+p22.04+tunstable+git20230118.0014-0) layer-shell-qt (5.26.5+p22.04+tunstable+git20230116.0525-0) libappstream4:amd64 (0.15.6-0xneon+22.04+jammy+unstable+build5) libappstreamqt2:amd64 (0.15.6-0xneon+22.04+jammy+unstable+build5) libkdecorations2-5v5:amd64 (4:5.26.5+p22.04+tunstable+git20230114.0118-0) libkdecorations2private10:amd64 (4:5.26.5+p22.04+tunstable+git20230114.0118-0) libkf5guiaddons5:amd64 (5.102.0+p22.04+tunstable+git20230116.1229-0) libkf5guiaddons-bin (5.102.0+p22.04+tunstable+git20230116.1229-0) libkf5guiaddons-data (5.102.0+p22.04+tunstable+git20230116.1229-0) libkf5plasma5:amd64 (5.102.0+p22.04+tunstable+git20230118.0218-0) libkf5plasmaquick5:amd64 (5.102.0+p22.04+tunstable+git20230118.0218-0) libkf5prison5:amd64 (5.102.0+p22.04+tunstable+git20230116.1320-0) libkf5screen7:amd64 (4:5.26.5+p22.04+tunstable+git20230117.0100-0) libkf5screen-bin (4:5.26.5+p22.04+tunstable+git20230117.0100-0) libkuserfeedbackcore1:amd64 (1.2.0+p22.04+tunstable+git20230118.0141-0) libkwineffects14 (4:5.26.5+p22.04+tunstable+git20230118.0014-0) libkwinglutils14 (4:5.26.5+p22.04+tunstable+git20230118.0014-0) liblayershellqtinterface5 (5.26.5+p22.04+tunstable+git20230116.0525-0) libpolkit-qt5-1-1:amd64 (0.114.0+p22.04+tunstable+git20220920.0916-0) libqalculate22:amd64 (4.5.1-0xneon+22.04+jammy+unstable+build10) libqt5core5a:amd64 (5.15.8+p22.04+tunstable+git20230118.0109-0) libqt5dbus5:amd64 (5.15.8+p22.04+tunstable+git20230118.0109-0) libqt5gui5:amd64 (5.15.8+p22.04+tunstable+git20230118.0109-0) libqt5network5:amd64 (5.15.8+p22.04+tunstable+git20230118.0109-0) libqt5printsupport5:amd64 (5.15.8+p22.04+tunstable+git20230118.0109-0) libqt5script5:amd64 (5.15.8+p22.04+tunstable+git20230118.0141-0) libqt5sql5:amd64 (5.15.8+p22.04+tunstable+git20230118.0109-0) libqt5widgets5:amd64 (5.15.8+p22.04+tunstable+git20230118.0109-0) libqt5xml5:amd64 (5.15.8+p22.04+tunstable+git20230118.0109-0) plasma-workspace (4:5.26.5+p22.04+tunstable+git20230118.0240-0) plasma-workspace-wayland (4:5.26.5+p22.04+tunstable+git20230118.0240-0) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464039] When entering pause screen, the mouse is reset to right handed
https://bugs.kde.org/show_bug.cgi?id=464039 René Lagoni Neukirch changed: What|Removed |Added Summary|WHen entering pause|When entering pause |screen, the mouse is reset |screen, the mouse is reset |to right handed |to right handed -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464039] WHen entering pause screen, the mouse is reset to right handed
https://bugs.kde.org/show_bug.cgi?id=464039 René Lagoni Neukirch changed: What|Removed |Added Summary|WHen entering puse screen, |WHen entering pause |the mouse is reset to right |screen, the mouse is reset |handed |to right handed -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464039] New: WHen entering puse screen, the mouse is reset to right handed
https://bugs.kde.org/show_bug.cgi?id=464039 Bug ID: 464039 Summary: WHen entering puse screen, the mouse is reset to right handed Classification: Applications Product: systemsettings Version: 5.26.4 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: r...@neukirch.dk Target Milestone: --- SUMMARY *** There is no crash, and the work around is to reset mouse to left handed after each login when puse screen has been activated (annoying, but not critical). *** STEPS TO REPRODUCE 1. Wait for the puse screen to become active 2. Re-login 3. There you are OBSERVED RESULT Mouse changed from left to right handed EXPECTED RESULT No change SOFTWARE/OS VERSIONS Operativsystem: Debian GNU/Linux KDE Plasma-version: 5.26.4 KDE Frameworks-version: 5.101.0 Qt-version: 5.15.7 Kerne-version: 6.0.0-6-amd64 (64-bit) Graphics Platform: X11 Processorer: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Hukommelse: 7,7 GiB af RAM Grafikprocessor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: Latitude E5570 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 --- Comment #66 from René Fritz --- (In reply to David Edmundson from comment #65) > >- enable the USB-C Monitor using nvidia-settings > > If nvidia-settings is also adjusting monitors that's going to lead to > unpredictable results having two daemons thinking they're in charge at once. > It is possible nvidia-settings was previously disabling the monitor after > kscreen enabled it. nvidia-settings is a user space program where I manually activate the monitor (gui). There's no daemon involved as I know. Normally I don't have nvidia-settings running. In the past I didn't had problems and nvidia-settings was installed too. nvidia proprietary driver is used -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460341] On X11, external monitor disabled, setting of external monitor is not remembered
https://bugs.kde.org/show_bug.cgi?id=460341 René Fritz changed: What|Removed |Added CC||rf-...@colorcube.de --- Comment #62 from René Fritz --- I have a laptop with Nvidia graphics and driver version 510 (tried 515 and 520). KDE Neon 22.04 I use external monitors connected with HDMI and USB-C (which is display port?) both in 4k. Hotplug worked well but not always flawless in the past. Lately only HDMI Monitor gets enabled on hotplug but not the one over USB-C. This behavior seems to be the same which many described here. I can enable the USB-C monitor using kcm_kscreen but it gets disabled immediately. Can't tell which updated caused it. It was before 22.04 was available I thin. My workaround - plug in the USB-C Monitor, it will not be enabled - enable the USB-C Monitor using nvidia-settings - plug in the HDMI Monitor - the monitor layout configured with kcm_kscreen will be restored To me it seems not the monitor layout is the problem but enabling a display port monitor - maybe specific to nvidia? I don't think the it's the nvidia driver because I'm pretty shure I used v 510 already when it still worked. Slightly different and maybe not related: I have another setup with two 4k daisy chained USB-C monitors. I had a problem there that sometimes one monitor got not enabled and enabling him manually using kcm_kscreen didn't work (nothing happens). Usually I tried plugin multiple times until it worked. This behavior got much more worse with recent update, which means it doesn't work 95% of the time. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 461808] Konqueror start
https://bugs.kde.org/show_bug.cgi?id=461808 --- Comment #2 from René Cybala --- the message is unknow error *Gesendet:* Donnerstag, 17. November 2022 um 23:23 Uhr *Von:* "Nicolas Fella" *An:* r.cyb...@gmx.de *Betreff:* [konqueror] [Bug 461808] Konqueror starthttps://bugs.kde.org/show_bug.cgi?id=461808 Nicolas Fella changed: What |Removed |Added CC| |nicolas.fe...@gmx.de Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #1 from Nicolas Fella --- What is the error message? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 461808] New: Konqueror start
https://bugs.kde.org/show_bug.cgi?id=461808 Bug ID: 461808 Summary: Konqueror start Classification: Applications Product: konqueror Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: r.cyb...@gmx.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Programmaufruf 2. konq:blank 3. Fehlermeldung OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Konqueror Version 20.12.0 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 388537] Unexpected Sidebar Ctrl or Shift Click behaviour
https://bugs.kde.org/show_bug.cgi?id=388537 René changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Version|unspecified |5.0.97 Resolution|WAITINGFORINFO |FIXED --- Comment #2 from René --- I installed the indicated newer version. There no longer is a sidebar of any kind. That is another way of bug fixing; just remove the buggy code until nothing is left. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 444192] Apps crash in QMenuBarPrivate::updateGeometries() when DisplayPort monitor is connected
https://bugs.kde.org/show_bug.cgi?id=444192 René Serral changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 René Krell changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #12 from René Krell --- (In reply to Justin Zobel from comment #11) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Sorry, I can't tell you any longer, haven't used KDE for a very long time and don't have an instance for testing the fix the next time. The issue has been probably fixed by the commit mentioned above. You may close this if you want. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 373344] Clear contact history does not clear anything instantly
https://bugs.kde.org/show_bug.cgi?id=373344 René Krell changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from René Krell --- Sorry, I can't tell you any longer, haven't used Telepathy for a very long time and don't have an instance for testing it the next time. You may close this if you want. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 373343] Open "Previous Conversations" from chat window doesn't preselected the dedicated user in log viewer
https://bugs.kde.org/show_bug.cgi?id=373343 René Krell changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from René Krell --- Sorry, I can't tell you any longer, haven't used Telepathy for a very long time and don't have an instance for testing it the next time. You may close this if you want. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 268913] Load a default session that can be saved on application closure, so session saving is automatic like a web browser
https://bugs.kde.org/show_bug.cgi?id=268913 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 459006] Investment activity type 'Remove' is replaced by 'Add' in CSV import
https://bugs.kde.org/show_bug.cgi?id=459006
--- Comment #2 from René ---
Dear Thomas,
Thank you for your rapid reply.
The KMyMoney ledger shows the wrong information: "Add" ("Ajouter des
titres" in French) instead of "Remove". The issues seems to occur in
the importer CSV file.
Best regards.
René
Le lundi 12 septembre 2022 à 06:24 +, Thomas Baumgart a écrit :
> https://bugs.kde.org/show_bug.cgi?id=459006
>
> Thomas Baumgart changed:
>
> What |Removed |Added
> -
> ---
> Resolution|--- |WAITINGFORINFO
> Status|REPORTED |RESOLVED
>
> --- Comment #1 from Thomas Baumgart ---
> Thanks for the details. One important detail is missing though: does
> the
> KMyMoney ledger show the correct or the wrong information? Depending
> on the
> answer of this we can hunt the source of the problem to be either in
> the CSV
> importer or CSV exporter.
>
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 459006] New: Investment activity type 'Remove' is replaced by 'Add' in CSV import
https://bugs.kde.org/show_bug.cgi?id=459006 Bug ID: 459006 Summary: Investment activity type 'Remove' is replaced by 'Add' in CSV import Product: kmymoney Version: 5.1.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: r.clu...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Hi everybody, I'm using KMyMoney (V 5.1.3) under Opensuse Tumbleweed (20220908 x86_64) with Gnome 42.2 (with Wayland). I created a CSV file for importing investments with different activity types (Buy, Sell, Dividend, Add and Remove). Buy, Sell, Dividend, Add activity types work well and create the corresponding records in the KMM empty created investment account. The rows containing Remove for removing securities after they have been created (with dates in the correct order) operate as Add activity type. STEPS TO REPRODUCE 1. The CSV file: Type de compte :Placement,,, ,,, Date,Titre,Action/type,Montant,Quantité,Cours,Intérêts,Commissions,Compte,Note,État,Symbole 2022-10-10,AMUNDI CRDT Euro P,Buy,"-2812,26","18,2","154,69",,,TitreTest (Courtage),,,FR0010775429 2022-10-10,AMUNDI CRDT Euro P,Buy,"-2534,94","0,3","9749,77",,,TitreTest (Courtage),,,FR0010775429 2022-10-10,BNP Paribas,Buy,"-417,67","4,3","97,36",,,TitreTest (Courtage),,,FR0011362094 2022-10-10,SG MONE PLUS P - FR0011362094,Buy,"-299,67","4,5","66,89",,,TitreTest (Courtage),,,FR131104 2022-10-11,AMUNDI CRDT Euro P,ReinvDiv,"5,45","18,2","0,3","-5,45",,TitreTest (Courtage),,,FR0010775429 2022-10-11,BNP Paribas,Sell,"223,11","3,3",67,,,TitreTest (Courtage),,,FR0011362094 2022-10-12,BNP Paribas,DivX,10,0,0,-10,,TitreTest (Courtage),,,FR0011362094 2022-10-15,SG MONE PLUS P - FR0011362094,Shrsin,0,5,0,,,TitreTest (Courtage),,,FR131104 2022-10-16,SG MONE PLUS P - FR0011362094,Remove,0,2,0,,,TitreTest (Courtage),,,FR131104 2022-10-10,AMUNDI CRDT Euro P,Remove,0,3,0,,,TitreTest (Courtage),,,FR0010775429 2. The output of the import process: Type de compte :Placement Date,Titre,Action/type,Montant,Quantité,Cours,Intérêts,Commissions,Compte,Note,État 2022-10-10,"SG MONE PLUS P - FR0011362094",Buy,"-299,67","4,50","66,89",,,"Titres_Pour_Tests (Courtage)",, 2022-10-10,"BNP Paribas",Buy,"-417,67","4,30","97,36",,,"Titres_Pour_Tests (Courtage)",, 2022-10-10,"AMUNDI CRDT Euro P",Shrsin,,"3,00",, 2022-10-10,"AMUNDI CRDT Euro P",Buy,"-2534,94","0,30","9749,77",,,"Titres_Pour_Tests (Courtage)",, 2022-10-10,"AMUNDI CRDT Euro P",Buy,"-2812,26","18,20","154,69",,,"Titres_Pour_Tests (Courtage)",, 2022-10-11,"BNP Paribas",Sell,"223,11","3,30","67,00",,,"Titres_Pour_Tests (Courtage)",, 2022-10-11,"AMUNDI CRDT Euro P",ReinvDiv,"5,45","18,20","0,30","-5,45" 2022-10-12,"BNP Paribas",DivX,"10,00",,,"-10,00",,"Titres_Pour_Tests (Courtage)",, 2022-10-15,"SG MONE PLUS P - FR0011362094",Shrsin,,"5,00",, 2022-10-16,"SG MONE PLUS P - FR0011362094",Shrsin,,"2,00",, 3. OBSERVED RESULT The two rows of the CSV file indicating to remove the corresponding securities are the two last rows: 2022-10-16,SG MONE PLUS P - FR0011362094,Remove,0,2,0,,,TitreTest (Courtage),,,FR131104 2022-10-10,AMUNDI CRDT Euro P,Remove,0,3,0,,,TitreTest (Courtage),,,FR0010775429 The corresponding rows in the output are 2022-10-10,"AMUNDI CRDT Euro P",Shrsin,,"3,00",, 2022-10-16,"SG MONE PLUS P - FR0011362094",Shrsin,,"2,00",, EXPECTED RESULT As one can note, the activity type in the output is Shrsin, which corresponds to Add ans not to Remove . Many thanks for your help René SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ... Qt5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449828] Login notification doesn't play the sound queue on login since the system was updated to KDE Plasma 5.24
https://bugs.kde.org/show_bug.cgi?id=449828 René Regensbogen changed: What|Removed |Added CC||smartpower0...@gmail.com --- Comment #7 from René Regensbogen --- Me too. In my case, I recognized that the notification sound is not muted, but at 0%. After turning it on 50%, it doesn´t help next reboot because it resets again. System: Kernel: 5.16.8-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0 parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=bbd31a1a-5acd-4143-b97f-a940c8bb5b82 rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 Desktop: KDE Plasma 5.24.0 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux Machine: Type: Laptop System: Medion product: S4216 v: 1.0 serial: Mobo: Medion model: S4216 v: 1.0 serial: UEFI: American Megatrends v: 505 date: 09/28/2012 Battery: ID-1: BAT0 charge: 30.7 Wh (95.9%) condition: 32.0/36.4 Wh (88.0%) volts: 16.4 min: 14.4 model: B34 type: Li-ion serial: N/A status: Not charging CPU: Info: model: Intel Core i5-3317U bits: 64 type: MT MCP arch: Ivy Bridge family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21 Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB Speed (MHz): avg: 2387 high: 2482 min/max: 800/2600 scaling: driver: intel_cpufreq governor: schedutil cores: 1: 2373 2: 2298 3: 2482 4: 2395 bogomips: 13569 Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Type: mds mitigation: Clear CPU buffers; SMT vulnerable Type: meltdown mitigation: PTI Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling Type: srbds status: Vulnerable: No microcode Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel 3rd Gen Core processor Graphics vendor: Pegatron driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0166 class-ID: 0300 Device-2: Microdia USB 2.0 Camera type: USB driver: uvcvideo bus-ID: 1-1.1:3 chip-ID: 0c45:6457 class-ID: 0e02 Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver: loaded: intel unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (20.0x11.2") s-diag: 582mm (22.9") Monitor-1: VGA1 res: 1920x1080 hz: 60 dpi: 92 size: 530x300mm (20.9x11.8") diag: 609mm (24") OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 21.3.5 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Pegatron driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403 Sound Server-1: ALSA v: k5.16.8-zen1-1-zen running: yes Sound Server-2: PulseAudio v: 15.0 running: no Sound Server-3: PipeWire v: 0.3.45 running: yes Network: Device-1: Intel Centrino Wireless-N 2230 driver: iwlwifi v: kernel bus-ID: 02:00.0 chip-ID: 8086:0887 class-ID: 0280 IF: wlp2s0 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Pegatron driver: r8169 v: kernel port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: enp3s0 state: down mac: IF-ID-1: docker0 state: down mac: Bluetooth: Device-1: Intel Centrino Bluetooth Wireless Transceiver type: USB driver: btusb v: 0.8 bus-ID: 1-1.4:5 chip-ID: 8087:07da class-ID: e001 Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: Drives: Local Storage: total: 223.57 GiB used: 37.71 GiB (16.9%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda maj-min: 8:0 vendor: GOODRAM model: SSDPR-CL100-240-G2 size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: rev: V4.7 scheme: GPT Partition: ID-1: / raw-size: 104.87 GiB size: 104.87 GiB (100.00%) used: 37.68 GiB (35.9%) fs: btrfs dev: /dev/sda5 maj-min: 8:5 ID-2: /boot/efi raw-size: 99 MiB size: 95 MiB (95.96%) used: 29.9 MiB (31.4%) fs: vfat dev: /dev/sda2 maj-min: 8:2 ID-3: /home raw-size: 104.87 GiB size: 104.87 GiB (100.00%) used: 37.68 GiB (35.9%) fs: btrfs dev: /dev/sda5 maj-min: 8:5 ID-4: /var/log raw-size: 104.87 GiB size: 104.87 GiB (100.00%) used: 37.68 GiB (35.9%) fs: btrfs dev: /dev/sda5 maj-min: 8:5 ID-5: /var/tmp raw-size: 104.87 GiB size: 104.87 GiB (100.00%) u
[digikam] [Bug 435695] Add image quality information on properties view from right sidebar
https://bugs.kde.org/show_bug.cgi?id=435695 René changed: What|Removed |Added CC||renel...@bluewin.ch -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 René Serral changed: What|Removed |Added CC||rser...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376061] DigiKam in KDE Neon is unable play video via QtAv (package problem)
https://bugs.kde.org/show_bug.cgi?id=376061 René Fritz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #26 from René Fritz --- (In reply to Jonathan Riddell from comment #25) > Now in user edition I confirm that video works now in kde user edition. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376061] DigiKam in KDE Neon is unable play video via QtAv (package problem)
https://bugs.kde.org/show_bug.cgi?id=376061 René Fritz changed: What|Removed |Added CC||rf-...@colorcube.de --- Comment #23 from René Fritz --- Version 7.5 is around the corner. Would be nice to have video support enabled. btw. the digikam appimage has video support but doesn't integrate very well: wrong fonts, wrong theme, ... -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 416830] Elisa crashes on start Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=416830
René Fritz changed:
What|Removed |Added
CC||rf-...@colorcube.de
--- Comment #16 from René Fritz ---
I had the same Problem (KDE neon). The last line in console was:
> org.kde.elisa.database: DatabaseInterface::initRequest QSqlError("10", "Não
> foi possível executar a expressão", "disk I/O error")
It turned out I had no phonon backend installed.
No/Wrong error message is somewhat misleading.
--
You are receiving this mail because:
You are watching all bug changes.
[KScreen] [Bug 444192] Apps crash in QMenuBarPrivate::updateGeometries() when DisplayPort monitor is connected
https://bugs.kde.org/show_bug.cgi?id=444192 --- Comment #4 from René Serral --- Thanks a lot for the prompt feedback. Just for the record I tried this with 3 different physical monitors and happens with all of them (they are from the same brand and model though). Don't hesitate to ask for more details if necessary. Thanks once again! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444192] Crash when DisplayPort monitor connected
https://bugs.kde.org/show_bug.cgi?id=444192 --- Comment #2 from René Serral --- Sorry for the delay I had to get back to the office to test. Here you have a crash report for the systemsettings app. Hope this helps: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 QWidget::hide (this=0x55f992e69294) at kernel/qwidget.cpp:7916 #5 0x7fd5be68156d in QMenuBarPrivate::updateGeometries (this=0x55fccd2a3f20) at widgets/qmenubar.cpp:256 #6 0x7fd5be6861a0 in QMenuBar::changeEvent (this=0x55fccd32cb70, e=0x7ffd6b1ab0a0) at widgets/qmenubar.cpp:1446 #7 0x7fd5be52e146 in QWidget::event (this=0x55fccd32cb70, event=0x7ffd6b1ab0a0) at kernel/qwidget.cpp:8961 #8 0x7fd5be4eb6b3 in QApplicationPrivate::notify_helper (this=, receiver=0x55fccd32cb70, e=0x7ffd6b1ab0a0) at kernel/qapplication.cpp:3632 #9 0x7fd5bd8ee16a in QCoreApplication::notifyInternal2 (receiver=0x55fccd32cb70, event=0x7ffd6b1ab0a0) at kernel/qcoreapplication.cpp:1063 #10 0x7fd5be51f305 in QWidgetPrivate::updateFont (this=this@entry=0x55fccd2a3f20, font=...) at kernel/qwidget.cpp:4654 #11 0x7fd5be52e600 in QWidget::event (this=0x55fccd32cb70, event=0x7ffd6b1ab250) at kernel/qwidget.cpp:9055 #12 0x7fd5be4eb6b3 in QApplicationPrivate::notify_helper (this=, receiver=0x55fccd32cb70, e=0x7ffd6b1ab250) at kernel/qapplication.cpp:3632 #13 0x7fd5bd8ee16a in QCoreApplication::notifyInternal2 (receiver=0x55fccd32cb70, event=0x7ffd6b1ab250) at kernel/qcoreapplication.cpp:1063 #14 0x7fd5be547596 in sendScreenChangeRecursively (widget=0x55fccd32cb70) at kernel/qwidgetwindow.cpp:752 #15 0x7fd5be5475c6 in sendScreenChangeRecursively (widget=) at kernel/qwidgetwindow.cpp:757 #16 0x7fd5be547696 in QWidgetWindow::handleScreenChange (this=0x55fccd33a130) at kernel/qwidgetwindow.cpp:764 #17 QWidgetWindow::qt_static_metacall (_c=QMetaObject::InvokeMetaMethod, _a=, _id=, _o=0x55fccd33a130) at .moc/moc_qwidgetwindow_p.cpp:77 #18 QWidgetWindow::qt_static_metacall (_o=0x55fccd33a130, _c=, _id=, _a=) at .moc/moc_qwidgetwindow_p.cpp:70 #19 0x7fd5bd925a88 in doActivate (sender=0x55fccd33a130, signal_index=3, argv=0x7ffd6b1ab3c0) at kernel/qobject.cpp:3898 #20 0x7fd5bd91ed67 in QMetaObject::activate (sender=sender@entry=0x55fccd33a130, m=m@entry=0x7fd5be365300 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd6b1ab3c0) at kernel/qobject.cpp:3946 #21 0x7fd5bdde77b3 in QWindow::screenChanged (this=this@entry=0x55fccd33a130, _t1=, _t1@entry=0x55fcccf27710) at .moc/moc_qwindow.cpp:729 #22 0x7fd5bdde8001 in QWindowPrivate::emitScreenChangedRecursion (this=, newScreen=0x55fcccf27710) at kernel/qwindow.cpp:484 #23 0x7fd5be5204d5 in QWidgetPrivate::create (this=this@entry=0x55fcccd712d0) at kernel/qwidget.cpp:1288 #24 0x7fd5be5207fe in QWidget::create (this=0x55fcccfcb710, window=, initializeWindow=, destroyOldWindow=) at kernel/qwidget.cpp:1179 #25 0x7fd5be683adf in QMenuBarPrivate::handleReparent (this=) at widgets/qmenubar.cpp:1421 #26 0x7fd5be683fa9 in QMenuBarPrivate::init (this=0x55fccd2a3f20) at widgets/qmenubar.cpp:705 #27 0x7fd5be684198 in QMenuBar::QMenuBar (this=, parent=) at widgets/qmenubar.cpp:741 #28 0x7fd5be6456c2 in QMainWindow::menuBar (this=0x55fcccfcb710) at widgets/qmainwindow.cpp:508 #29 0x7fd5beef4c3b in KXmlGuiWindow::createGUI(QString const&) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #30 0x7fd5beef55db in KXmlGuiWindow::setupGUI(QSize const&, QFlags, QString const&) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #31 0x7fd5beef5721 in KXmlGuiWindow::setupGUI(QFlags, QString const&) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #32 0x55fccb9b3288 in ?? () #33 0x55fccb9b0560 in ?? () #34 0x7fd5bd221fd0 in __libc_start_call_main (main=main@entry=0x55fccb9afae0, argc=argc@entry=1, argv=argv@entry=0x7ffd6b1aba78) at ../sysdeps/nptl/libc_start_call_main.h:58 #35 0x7fd5bd22207d in __libc_start_main_impl (main=0x55fccb9afae0, argc=1, argv=0x7ffd6b1aba78, init=, fini=, rtld_fini=, stack_end=0x7ffd6b1aba68) at ../csu/libc-start.c:409 #36 0x55fccb9b12d5 in ?? () [Inferior 1 (process 72725) detached] -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444192] New: Crash when DisplayPort monitor connected
https://bugs.kde.org/show_bug.cgi?id=444192 Bug ID: 444192 Summary: Crash when DisplayPort monitor connected Product: kde Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rser...@gmail.com Target Milestone: --- SUMMARY I just bought a Displayport Samsung monitor and when connecting it through USB-C and DisplayLink on my Ubuntu 21.04 a really weird behavior happens. The moment I connect the monitor KDE applications start to randomly crash and from then they cannot be started anymore. Looking at the logs I can repeatedly (around 3 million times!!) see the message: [warn] epoll_wait: Bad file descriptor I'm not able to see any other relevant log message. The most strange issue is that if I disconnect the monitor or if I connect it through regular HDMI the problem instantly disappears. I don't really know if it's a plasma or displaylink bug. The problem does not happen with other non plasma applications (chrome, firefox...) I filed a bug on DisplayLink already without answer yet: https://www.displaylink.org/forum/showthread.php?t=67936 Any hint what can be wrong? No STEPS TO REPRODUCE 1. Connect the monitor through displayport 2. continue working as usual 3. observe crashes kontact, dolphin, systemsettings, ... EXPECTED RESULT No crashes and regular workflow SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23 (but the behavior is the same in 5.21 and 5.22 My KUbuntu is 21.10 (but before upgrading, the problem was present in 21.04) KDE Frameworks Version: 5.87, but with 5.86 was the same Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410360] Add a "soft upair" (disconnect) option to the interface and put a warning on the permanent unpair action.
https://bugs.kde.org/show_bug.cgi?id=410360 René changed: What|Removed |Added Version|1.10|1.4 CC||r...@comunica2.net --- Comment #1 from René --- I don't want to change the title but propose you don't call it "soft unpair". I think disconnect is sufficient. I agree that this feature is needed but for other reasons. What about the use of kdeconnect in a small office or household?: 1. members want to quickly share among them a file without setting up a network share. 2. members don't want to be permanently connected to avoid clipboard paste conflicts 3. privacy issues in Android Concept of clipboard paste conflict can be described as follows. User A and B are paired and share the clipboard. Both are editing a document and do a lot of corrections using copy/cut and paste. User A copies a text and without knowing user B does the same right after. Then user A pastes not his own copy but that of user B and is confused. The privacy issue in Android I discovered while using the virtual keyboard. Just above the virtual keyboard there is an area that shows a button of recently cut/copies text from the clipbaord that allows you to paste it by tapping it. It shows a fragment of the text and it was constantly changing while I was answering a chat message. I discovered they were not the usual suggestions while you enter your text but it was copied text of my wife while she was editing on her paired device In this aspect I think that kdeconnect counts too much on individual use and it does not on use in households or small office teams. There should at least be an easy disconnect option and auto-connect should be optional per device. That way you can minimally distinguish between your own devices and that of others and maintain some respect and privacy. Like @leftcrane explains, unpair is too drastic and something like (manual) connect and disconnect would be desirable. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438987] Latte Dock randomly crashes on wayland
https://bugs.kde.org/show_bug.cgi?id=438987 René Serral changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from René Serral --- Sorry I forgot to update it. It doesn't happen with the new version. Regards -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 438987] New: Latte Dock randomly crashes on wayland
https://bugs.kde.org/show_bug.cgi?id=438987 Bug ID: 438987 Summary: Latte Dock randomly crashes on wayland Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rser...@gmail.com Target Milestone: --- Application: latte-dock (0.9.12) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.10-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.1 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - Unusual behavior I noticed: Since migrating to Fedora 34, plasma on Wayland behaves erratically. In particular latte-dock crashes frequently on random events (not sure if related): - Opening new applications - Closing running apps - changing windows The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f9f4e088eb8 in QVariant::QVariant(QVariant const&) () at /lib64/libQt5Core.so.5 #5 0x7f9f4e08b87e in QVariant::cmp(QVariant const&) const () at /lib64/libQt5Core.so.5 #6 0x55dcc022de67 in Latte::WindowSystem::Tracker::LastActiveWindow::windowChanged(QVariant const&) [clone .part.0] () #7 0x55dcc022df0b in Latte::WindowSystem::Tracker::LastActiveWindow::windowChanged(QVariant const&) [clone .part.0] () #8 0x7f9f4e07e4b0 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #9 0x55dcc023dda2 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] () #10 0x7f9f4e07e4b0 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #11 0x55dcc0225cd8 in Latte::WindowSystem::AbstractWindowInterface::considerWindowChanged(QVariant) () #12 0x55dcc0225eb3 in Latte::WindowSystem::WaylandInterface::updateWindow() () #13 0x7f9f4e07e4b0 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #14 0x7f9f5013f078 in KWayland::Client::PlasmaWindow::Private::stateChangedCallback(void*, org_kde_plasma_window*, unsigned int) () at /lib64/libKF5WaylandClient.so.5 #15 0x7f9f4c0e1c04 in ffi_call_unix64 () at /lib64/libffi.so.6 #16 0x7f9f4c0e1107 in ffi_call () at /lib64/libffi.so.6 #17 0x7f9f4d1f0d10 in wl_closure_invoke.constprop () at /lib64/libwayland-client.so.0 #18 0x7f9f4d1f142b in dispatch_event.isra () at /lib64/libwayland-client.so.0 #19 0x7f9f4d1f161c in wl_display_dispatch_queue_pending () at /lib64/libwayland-client.so.0 #20 0x7f9f4cc457a3 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib64/libQt5WaylandClient.so.5 #21 0x7f9f4e07e4fd in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #22 0x7f9f4e09a78b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #23 0x7f9f4e04c9b2 in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #24 0x7f9f4e054544 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #25 0x55dcc0193530 in main () [Inferior 1 (process 64315) detached] Possible duplicates by query: bug 437773, bug 436863, bug 435427, bug 432084, bug 431077. Reported using DrKonqi This report was filed against 'kde' because the product 'latte-dock' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437972] New: Wrong button name
https://bugs.kde.org/show_bug.cgi?id=437972 Bug ID: 437972 Summary: Wrong button name Product: systemsettings Version: 5.21.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_plasmasearch Assignee: plasma-b...@kde.org Reporter: r...@rpc-scandinavia.dk CC: alexander.loh...@gmx.de Target Milestone: --- Created attachment 138931 --> https://bugs.kde.org/attachment.cgi?id=138931=edit Screenshot SUMMARY When the file indexer is suspended, the button name is still "Pause Indexer", and not "Start Indexer" or "Resume Indexer". STEPS TO REPRODUCE 1. Goto configure file search 2. Enable file search 3. Pause the indexer OBSERVED RESULT When the file indexer is suspended, the button name is still "Pause Indexer". EXPECTED RESULT Expecting the button name to be "Start Indexer" or "Resume Indexer". SOFTWARE/OS VERSIONS Windows: NO. macOS: NO. Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Not everything is translated either, but the parts in question is in English. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Spurious XCB Events causing high CPU
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #20 from René Krell --- (In reply to Nate Graham from comment #19) > Is anyone still seeing this issue in a recent Plasma version? I haven't used KDE / KMail since 07/2017, I'm not able to update the state of the issue in current versions. From my point of view it is not interesting any longer. Maybe anybody else around? Otherwise this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430371] ALT Tab change tag does no longer work while dragging selected string
https://bugs.kde.org/show_bug.cgi?id=430371 --- Comment #6 from René --- Reported in Ubuntu ropositories https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1911140 and https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1911140 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430371] ALT Tab change tag does no longer work while dragging selected string
https://bugs.kde.org/show_bug.cgi?id=430371 René changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #5 from René --- I just noticed that also Thunderbird shows the same behaviour. If I remember well Thunderbird, Firefox are GTK applications but I could not reproduce the same behaviour (or lack thereof) in other GTK applications like gEdit. I therefore close this issue and report it elsewhere. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429453] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=429453 René changed: What|Removed |Added CC||r...@comunica2.net --- Comment #3 from René --- The question is why Bookmarks is hidden and Places has its own Panel. Apparently the team responsible is chosing simplicity over functionality. In Bookmarks you can organise in a folder hierarchy, in Places not. Bookmarks aim at what you could call power users that need losts of shortcuts that are organised according to task or location. Do you want to punish power users? In the filemanager profile of Konquerer both "Places" and bookmarks had their own Panel. I would be in favour of adding a bookmark Panel, by default hidden. -- 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 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430371] ALT Tab change tag does no longer work while dragging selected string
https://bugs.kde.org/show_bug.cgi?id=430371 --- Comment #2 from René --- (In reply to Nate Graham from comment #1) > Works for me dragging text in Firefox to Kate in Plasma 5.20. Which apps are > you using where this is broken? Does it work in Firefox and Kate for you? The dragging is not the issue here, but what it inhibits, namely to use of ALT + TAB to change task. ALT+TAB from FF to Kate does not work here, but curiously from Kate to FF does. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430371] New: ALT Tab change tag does no longer work while dragging selected string
https://bugs.kde.org/show_bug.cgi?id=430371 Bug ID: 430371 Summary: ALT Tab change tag does no longer work while dragging selected string Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: r...@comunica2.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY This seems like a functionality regression. Previously I could select a text, start dragging it, then with ALT Tab change to another applicaton window and there drop the string in that window. I don't see the point why I should always contaminate the clipboard with these routine operations. Work around is slow and needs more coordination and finding the right one, namely to drag the string to the desired task tab in the task manager which will make it change the focus there. When that still works, why not ALT Tab like before? STEPS TO REPRODUCE 1. Select text string in task A 2. Start dragging while changing to previous task using the ALT + Tab key combination. OBSERVED RESULT ALT Tab will no longer change to previous task during a drag operation. EXPECTED RESULT ALT Tab will also change task while doing a drag operation. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 LTS standard Plasma repository. (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 165732] reproducible crash on blauarbeit.de (QMetaObject::activate)
https://bugs.kde.org/show_bug.cgi?id=165732 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416080] Kmymoney: distinction between date of record and date of movement
https://bugs.kde.org/show_bug.cgi?id=416080 --- Comment #2 from René --- Thank you for your reply. Looking forward to solving this issue. Regards. René Cluzel Le vendredi 10 janvier 2020 à 12:24 +, Thomas Baumgart a écrit : > https://bugs.kde.org/show_bug.cgi?id=416080 > > Thomas Baumgart changed: > >What|Removed |Added > --- > - >Severity|normal |wishlist > > --- Comment #1 from Thomas Baumgart --- > I turned this into a wish list item because we currently do not > differentiate > between the booking date and value date even though the software > maintains a > date when the transaction has been entered into the data pool. This > field > though is not accessible to the user. > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416080] New: Kmymoney: distinction between date of record and date of movement
https://bugs.kde.org/show_bug.cgi?id=416080 Bug ID: 416080 Summary: Kmymoney: distinction between date of record and date of movement Product: kmymoney Version: 5.0.7 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: database Assignee: kmymoney-de...@kde.org Reporter: r.clu...@gmail.com Target Milestone: --- Hello everybody, I am not sure to address the correct list. I would like to a feature wish about Kmymoney and not a bug. The issue concerns the Reconciliation process. I very frequently meet a difficulty in this process when the date of a record is very close to the initial date of a a reconciliation period provided by my bank. Account records are registered with their date of emission (the date of the signature of a check, or the date when a transfer is made). My account is debited later, few days later for transfer or credit card payment, and very often two or three weeks later for checks. When I reconciliate a check payment, I have to go backward in my account to change the date and record the emission date in the record note. There is a loss of information unless printing the final listing of the reconciliation of the previous period. The reconciliation list provided by banks include two fields: * Emission Date, which the date of the check emission, the date of the credit card payment, or the date of the transfer request, and * Value Date (Date de Valeur in French), which is the date when the bank account is debited or credited. It would be interesting that such a second field is added to the account file, filled in by default with the first field and displayed in color(red for example) when the corresponding record is not yet reconciliated, and reset in a standard color when it is reconciliated. This issue is related for Kmymoney versions for both Debian 10, and Fedora 31. If this is not the right forum, please redirect me to the right one. Many thanks for your attention. René Cluzel -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 392823] Google tasks doesn't have an "All day" mark after sync
https://bugs.kde.org/show_bug.cgi?id=392823 René Fritz changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||rf-...@colorcube.de --- Comment #1 from René Fritz --- I can confirm this with KDE Neon User edition. Korganizer 5.13.0 (19.12.0) Instead of "all day" marked the time is set to 00:00. When you begin to fix this in Korganizer or Google Calendar the task moves a day back because of the time 00:00 I guess. -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 336114] systray hide keyboard layout separately
https://bugs.kde.org/show_bug.cgi?id=336114 René changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Platform|unspecified |Ubuntu Packages Resolution|WAITINGFORINFO |FIXED --- Comment #2 from René --- This is fixed in my present version of Plasma 4:5.8.9-0ubuntu1~ubuntu16.04~ppa1 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 204612] the svg files are show with errors in text positioning
https://bugs.kde.org/show_bug.cgi?id=204612 René Mérou changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from René Mérou --- Well, the map has evolute a lot since one decade ago. Nowadays, its more like this one: http://saberlibre.net/fsmap/ca/fsmap-ca.svg Which is more complex and resource demanding. The comparation with firefox makes it with a i7 of last generation to take like 3 or 4 times more seconds to run but I'm happy to say that it runs as a charm. Thank you guys to update Konqueror, it is still my proffered browser and It was a very good news to see it working in my Debian. Regards -- Jean-René Mérou -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394671] Distortion on Panasonic DMC-LX15
https://bugs.kde.org/show_bug.cgi?id=394671 René <raz...@dunkelweiss.li> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from René <raz...@dunkelweiss.li> --- Oh in this case I made a false assumption. With my DSLR I never experienced something like this, so I though DigiKam was just automatically correcting it. So I guess this is not the case at all, so I will probably go with JPEG with this camera. Thank you very much for the explanation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394671] New: Distortion on Panasonic DMC-LX15
https://bugs.kde.org/show_bug.cgi?id=394671 Bug ID: 394671 Summary: Distortion on Panasonic DMC-LX15 Product: digikam Version: 6.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Preview-RAW Assignee: digikam-bugs-n...@kde.org Reporter: raz...@dunkelweiss.li Target Milestone: --- When opening a .rw2 file from my new Panasonic DMC-LX15, the preview (if the embedded preview is disabled) looks distorted (a little bit of a fisheye effect). The JPEG files generated on the camera do not have this problem. After searching a while to understand what actually happens, it appears that the lens correction is either wrong or not applied at all. I also updated the lensfun data with lensfun-update-data, since it is only listed in the development notes of lensfun. I can see the definitions in .local/share/lensfun/updates/version_1/compact-panasonic.xml for this camera / lens. I tried with Digikam 5.9.0 and 6.0.0. What can I do to track this down further? Thank you -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 182838] Facebook tool does not work any more
https://bugs.kde.org/show_bug.cgi?id=182838 --- Comment #15 from René <raz...@dunkelweiss.li> --- It is not only about the git master. I tried version 5.9.0 just before trying with the git master. I got exactly the same message there. This was actually the reason why I tried the git branch. So a hint on the website would probably be nice already. But this solved my problem for now. Of course it is up to you when you will publish something on the website :-) Many thanks René -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 182838] Facebook tool does not work any more
https://bugs.kde.org/show_bug.cgi?id=182838 --- Comment #13 from René <raz...@dunkelweiss.li> --- Thank you for the fast response. If the uploader is not usable for a while, it might be a good idea to add this information either in the export window or on the website. Or even disable this option in the menu. I was searching for a while, but could just not figure out why it was not working. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390373] Kwin crash
https://bugs.kde.org/show_bug.cgi?id=390373 René Timmermans <rene.timmerm...@bax-shop.nl> changed: What|Removed |Added CC||rene.timmerm...@bax-shop.nl --- Comment #1 from René Timmermans <rene.timmerm...@bax-shop.nl> --- Forgot to mention: It happens only the first time i click "play" in Spotify. The rest of the session i can click whatever i want in Spotify, the crash only happens once (first time of the day). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390373] New: Kwin crash
https://bugs.kde.org/show_bug.cgi?id=390373 Bug ID: 390373 Summary: Kwin crash Product: kwin Version: 5.12.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rene.timmerm...@bax-shop.nl Target Milestone: --- Application: kwin_x11 (5.12.0) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.15.2-2-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Everytime I click "play" in Spotify, Kwin crashes. The sons starts playing, but Kwin crashes en restarts immediately. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffc9840 (LWP 871))] Thread 8 (Thread 0x7f77562de700 (LWP 28873)): #0 0x7f777091a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7774ae100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f776fae39ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f776fae3e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f7774adfb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f777091408c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f962e7f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f769a51b700 (LWP 28872)): #0 0x7f958a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f7774d24883 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f7774d2601f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f7774ccae9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f7774ada78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f776f3e5a19 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f7774adfb2d in () at /usr/lib/libQt5Core.so.5 #7 0x7f777091408c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f962e7f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f7744cc7700 (LWP 1512)): #0 0x7f777091a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7774ae100c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f776fae39ca in () at /usr/lib/libQt5Quick.so.5 #3 0x7f776fae3e54 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f7774adfb2d in () at /usr/lib/libQt5Core.so.5 #5 0x7f777091408c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f962e7f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f7747fff700 (LWP 1446)): #0 0x7f958a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f7774d24883 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f7774d2601f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f7774ccae9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f7774ada78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f776f3e5a19 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f7774adfb2d in () at /usr/lib/libQt5Core.so.5 #7 0x7f777091408c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f962e7f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f773f815700 (LWP 1049)): #0 0x7f777091a3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7773bf8f77 in () at /usr/lib/libQt5Script.so.5 #2 0x7f7773bf8fb9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f777091408c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f962e7f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f77554cd700 (LWP 1041)): #0 0x7f958a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f7774d24883 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f7774d2601f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f7774ccae9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f7774ada78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f776f3e5a19 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f7774adfb2d in () at /usr/lib/libQt5Core.so.5 #7 0x7f777091408c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f962e7f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f7757b59700 (LWP 916)): #0 0x7f958a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f7774d24883 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f7774d2601f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f7774ccae9b in QEventLoop::exec(QFlags) () at
[konqueror] [Bug 388537] New: Unexpected Sidebar Ctrl or Shift Click behaviour
https://bugs.kde.org/show_bug.cgi?id=388537 Bug ID: 388537 Summary: Unexpected Sidebar Ctrl or Shift Click behaviour Product: konqueror Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sidebar Assignee: stefano.cro...@alice.it Reporter: r...@comunica2.net Target Milestone: --- Since my upgrade to 4.14.22 (Kubuntu 16.04LTS) I see a change in sidebar click behaviour. Shift+Click does not open in a new window nor Ctrl+Click in a new tab. This is inconsistent in behaviour with Ctrl or Shift clicking in the Bookmark menu it opens in a new tab or window respectively. Not sure if this a Kubuntu specific bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372208] kwrite File -> New directory fails to follow current, defaults to $HOME
https://bugs.kde.org/show_bug.cgi?id=372208 René <r...@comunica2.net> changed: What|Removed |Added CC|r...@comunica2.net| -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372208] kwrite File -> New directory fails to follow current, defaults to $HOME
https://bugs.kde.org/show_bug.cgi?id=372208 René <r...@comunica2.net> changed: What|Removed |Added CC||r...@comunica2.net --- Comment #3 from René <r...@comunica2.net> --- likely a duplicate of bug 374913 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 168726] file open dialog does not start in the current file's directory
https://bugs.kde.org/show_bug.cgi?id=168726 René <r...@comunica2.net> changed: What|Removed |Added CC|r...@comunica2.net| -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 168726] file open dialog does not start in the current file's directory
https://bugs.kde.org/show_bug.cgi?id=168726 René <r...@comunica2.net> changed: What|Removed |Added CC||r...@comunica2.net --- Comment #5 from René <r...@comunica2.net> --- Version 16.04.03 in Kubuntu 16.04 shows the same behaviour, together with File -> Save as... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] SIGILL failure with ud2 opcode _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) (macOS)
https://bugs.kde.org/show_bug.cgi?id=383723 René Hansen <ren...@gmail.com> changed: What|Removed |Added CC||ren...@gmail.com --- Comment #16 from René Hansen <ren...@gmail.com> --- I ran into this bug today and have a small non-qt program that reproduces the same error as well. It's a simple cli tool that prints out some OpenCL information; basically just wrapping stock OpenCL functions. Tool: https://github.com/rhardih/opencl_util/blob/master/src/oclinf.c Source of interest: https://github.com/rhardih/opencl_util/blob/master/src/opencl_util.c#L554 Output with error: https://gist.github.com/rhardih/939ebfdc6b10acf732b62a805bd7ea93 -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 381349] Relative path for audio files not working
https://bugs.kde.org/show_bug.cgi?id=381349 --- Comment #6 from René Fritz <r...@colorcube.de> --- added patch to review board https://git.reviewboard.kde.org/r/130224/ -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 381349] Relative path for audio files not working
https://bugs.kde.org/show_bug.cgi?id=381349 René Fritz <r...@colorcube.de> changed: What|Removed |Added CC||r...@colorcube.de --- Comment #5 from René Fritz <r...@colorcube.de> --- Created attachment 107232 --> https://bugs.kde.org/attachment.cgi?id=107232=edit fixes relative paths handling in reader if (QUrl::fromLocalFile(currentElement.text()).isRelative()) ... did not work because the url has a scheme and a scheme means it's not relative. My knowledge of Qt is vry limited, so I hope the patch makes sense. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 381349] Relative path for audio files not working
https://bugs.kde.org/show_bug.cgi?id=381349 --- Comment #4 from René Fritz <r...@colorcube.de> --- Yes 17.04 package. From Neon user packages. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 381349] Relative path for audio files not working
https://bugs.kde.org/show_bug.cgi?id=381349 --- Comment #2 from René Fritz <r...@colorcube.de> --- The bug is already mentioned here: https://mail.kde.org/pipermail/kde-edu/2017-March/013344.html -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 381349] Relative path for audio files not working
https://bugs.kde.org/show_bug.cgi?id=381349 --- Comment #1 from René Fritz <r...@colorcube.de> --- I found this change which might be related https://git.reviewboard.kde.org/r/129992/diff/3/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381981] New: Plasma crash on startup
https://bugs.kde.org/show_bug.cgi?id=381981 Bug ID: 381981 Summary: Plasma crash on startup Product: plasmashell Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: renda.kr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.3) Qt Version: 5.9.0 Frameworks Version: 5.34.0 Operating System: Linux 4.11.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Plasma crashes each time on start without any interaction. Using native nvidia drivers 384.47. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e206758c0 (LWP 3354))] Thread 12 (Thread 0x7f1d33bfe700 (LWP 4081)): #0 0x7f1e1956c5ed in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1e1a39fa5b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f1e1e105748 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f1e1e105b7a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f1e1a39e73e in () at /usr/lib64/libQt5Core.so.5 #5 0x7f1e195664e7 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1e19caca2f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f1d40d53700 (LWP 4080)): #0 0x7f1e1956c5ed in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1e1a39fa5b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f1e1e105748 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f1e1e105b7a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f1e1a39e73e in () at /usr/lib64/libQt5Core.so.5 #5 0x7f1e195664e7 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1e19caca2f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1d41dc8700 (LWP 4079)): [KCrash Handler] #6 0x7f1e19bf3a60 in raise () at /lib64/libc.so.6 #7 0x7f1e19bf50c6 in abort () at /lib64/libc.so.6 #8 0x7f1e19c328f1 in __libc_message () at /lib64/libc.so.6 #9 0x7f1e19c38f3b in malloc_printerr () at /lib64/libc.so.6 #10 0x7f1e19c3a671 in _int_free () at /lib64/libc.so.6 #11 0x7f1e1b11415f in () at /usr/lib64/libQt5Gui.so.5 #12 0x7f1e1b11319c in () at /usr/lib64/libQt5Gui.so.5 #13 0x7f1e1b0dfc95 in () at /usr/lib64/libQt5Gui.so.5 #14 0x7f1e1b0e05d8 in QOpenGLShaderProgram::link() () at /usr/lib64/libQt5Gui.so.5 #15 0x7f1e1e0f8d90 in QSGDefaultRenderContext::compileShader(QSGMaterialShader*, QSGMaterial*, char const*, char const*) () at /usr/lib64/libQt5Quick.so.5 #16 0x7f1e1e0c70f6 in () at /usr/lib64/libQt5Quick.so.5 #17 0x7f1e1e0c7a2a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib64/libQt5Quick.so.5 #18 0x7f1e1e0c8e15 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib64/libQt5Quick.so.5 #19 0x7f1e1e0ce2bc in QSGBatchRenderer::Renderer::render() () at /usr/lib64/libQt5Quick.so.5 #20 0x7f1e1e0bf2ea in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib64/libQt5Quick.so.5 #21 0x7f1e1e0bf77b in QSGRenderer::renderScene(unsigned int) () at /usr/lib64/libQt5Quick.so.5 #22 0x7f1e1e0f81e0 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib64/libQt5Quick.so.5 #23 0x7f1e1e150f58 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib64/libQt5Quick.so.5 #24 0x7f1e1e100e19 in () at /usr/lib64/libQt5Quick.so.5 #25 0x7f1e1e105b38 in () at /usr/lib64/libQt5Quick.so.5 #26 0x7f1e1a39e73e in () at /usr/lib64/libQt5Core.so.5 #27 0x7f1e195664e7 in start_thread () at /lib64/libpthread.so.0 #28 0x7f1e19caca2f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1d4a5fc700 (LWP 4065)): #0 0x7f1e14ad120d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f1e14ad1c3b in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1e14ad1e1c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1e1a5be75b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f1e1a567d0a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f1e1a39a05a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f1d4ce93f37 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7f1e1a39e73e in () at /usr/lib64/libQt5Core.so.5 #8 0x7f1e195664e7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f1e19caca2f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1d65392700 (LWP 3885)): #0 0x7f1e1956c5ed in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1
[parley] [Bug 381349] New: Relative path for audio files not working
https://bugs.kde.org/show_bug.cgi?id=381349 Bug ID: 381349 Summary: Relative path for audio files not working Product: parley Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: parley-bugs-n...@kde.org Reporter: r...@colorcube.de Target Milestone: --- When you add an audio file in editor mode the absolute path of the file is shown and you can play the audio file. When the vocabulary file is saved the absolute path of the audio is converted to a relative which is the expected behaviour. But when the vocabulary file is loaded the relative path is not handled correctly and the audio file can't be played. When clicking the play button following error message is on the console: GStreamer; Unable to pause - "file:Assets/au02834218_ew_0001.mp3" GStreamer; Unable to pause - "file:Assets/au02834218_ew_0001.mp3" Error: "Could not open resource for reading." Parley Version 2.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #10 from René Krell <renda.kr...@gmail.com> --- (In reply to Laurent Montel from comment #9) > akonadi-calendar: > commit 12711617070bae66679d107e270c7fb5a676c154 Aha, ok, finally found it: https://github.com/KDE/akonadi-calendar/commit/12711617070bae66679d107e270c7fb5a676c154 Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #8 from René Krell <renda.kr...@gmail.com> --- (In reply to Laurent Montel from comment #7) > Thanks I tested it. > David fixed a bug in 5.5.0 > We can open this eml file and see invitation without problem now. > So I think that in new version it will work. > > I will delete your testcase Great, thank you. Do you have any reference to the fix (some Git commit or another issue)? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #5 from René Krell <renda.kr...@gmail.com> --- Just for the record, as a hint: Thunderbird 45.8.0 does show this kind of messages (TNEF) without any trouble - in header there appears: "This message contains an invitation to an event." with the Decline | Tentative | Accept buttons. Which probably means this seems not to be an authorization or other integration problem. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #4 from René Krell <renda.kr...@gmail.com> --- It also depends what do you expect as testcase. Is it enough to forward you a mail causing this problem, and how (inline, as attachment). Or should I save this mail (which format *.eml, *.txt)? What is the best way for you? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #3 from René Krell <renda.kr...@gmail.com> --- I cannot attach these mails publically, because they are confidential. But I might choose one to forward to your mail address if you promise not to make them public, ok? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #1 from René Krell <renda.kr...@gmail.com> --- Special headers of the affected message look like this: --- ... X-MS-Exchange-Organization-AuthAs: Internal X-MS-Exchange-Organization-AuthMechanism: 04 X-MS-Exchange-Organization-AuthSource: mail.a.company.com X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: multipart/alternative; boundary="_002_F263790328C47E4C80994544E26F19C2017786B9AB73mail_" MIME-Version: 1.0 --_002_F263790328C47E4C80994544E26F19C2017786B9AB73mail_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 ... --- -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] New: KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 Bug ID: 378228 Summary: KMail hangs when trying to open a MS Outlook calendar (invitation) message Product: kmail2 Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: --- Linkage info: - KDE Frameworks 5.31.0 - Qt 5.7.1 (built against 5.7.1) If I receive a calendar message (invitation) from MS Outlook via KMail/Akonadi the message window starts showing "retrieving folder contents" and hangs up infinitely. After that, even on changing to other messages in the message list the message window does not recover from that. To recover, I have to restart KMail and Akonadi (akonadictl restart), but if the first message to show after restarting KDE is the same calendar message again, the whole problem reappears of course. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 365327] Support macOS Sierra (10.12)
https://bugs.kde.org/show_bug.cgi?id=365327 René Schwaiger <sansseco...@me.com> changed: What|Removed |Added CC||sansseco...@me.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373524] Konsole crashes when closing a tab using a profile that launches autossh
https://bugs.kde.org/show_bug.cgi?id=373524 René van Buuren <kdeb...@xadamas.com> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from René van Buuren <kdeb...@xadamas.com> --- (In reply to Kurt Hindenburg from comment #1) > I'd be interested if you still have issues w/ a newer release - a number of > bugs were fixed in 16.12.x and later I'm now on 16.12.2, and this does seem to have been fixed. Konsole now gives the appropriate warning about killing autossh and no longer crashes. Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Spurious XCB Events causing high CPU
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #11 from René Krell <renda.kr...@gmail.com> --- (In reply to bjoernv from comment #9) > I see this bug every day on the same Tumbleweed version You're right, right now I got the problem again with 5.8.5, just after "heavily using" the system (many Java processes and IDE in use). So this is definitely not fixed in 5.8.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #8 from René Krell <renda.kr...@gmail.com> --- (In reply to David Edmundson from comment #7) > Rene, had a look > > Log shows we're receiving a ridiculous number of X events. 674603 in fact. > Assuming "several minutes" == 3 minutes, that's 3743 events per second, > which is a sign that something is going wrong. > > This matches something seen in one of the other generic high CPU threads. Edmund, thanks. I saw just this issue: Bug 356479. Is there the same cause? Most times this happened during sleep/hibernation mode, but not always. I'm now at 5.8.5 (OpenSUSE Tumbleweed RPMs), and the problem hasn't appeared a long time here since updating. Maybe just accidentally, or has it been already fixed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374176] Plasmashell hogs CPU while network connection is setting up
https://bugs.kde.org/show_bug.cgi?id=374176 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added CC||renda.kr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373524] Konsole crashes when closing a tab using a profile that launches autossh
https://bugs.kde.org/show_bug.cgi?id=373524 René van Buuren <kdeb...@xadamas.com> changed: What|Removed |Added CC|kdeb...@xadamas.com | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373524] Konsole crashes when closing a tab using a profile that launches autossh
https://bugs.kde.org/show_bug.cgi?id=373524 René van Buuren <kdeb...@xadamas.com> changed: What|Removed |Added CC||kdeb...@xadamas.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373524] New: Konsole crashes when closing a tab using a profile that launches autossh
https://bugs.kde.org/show_bug.cgi?id=373524 Bug ID: 373524 Summary: Konsole crashes when closing a tab using a profile that launches autossh Product: konsole Version: 16.08.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: kdeb...@xadamas.com Target Milestone: --- Application: konsole (16.08.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-53-generic x86_64 Distribution: KDE neon User Edition 5.8 -- Information about the crash: - Custom settings of the application: I use Konsole profiles that are set to launch autossh to connect to a particular server. - What I was doing when the application crashed: Whenever I try to close a tab that was launched with one of these autossh profiles, Konsole crashes in its entirety, killing the window with all tabs inside of it, including local ones that had nothing to do with autossh. (This problem does not occur when I change autossh to regular ssh in the profiles, but I depend on the measures autossh takes in the background to avoid connections getting dropped and to reopen them when they do.) The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9b4e9238c0 (LWP 31506))] Thread 3 (Thread 0x7f9b3b418700 (LWP 20906)): #0 0x7f9b4e3dab5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9b4467b861 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f9b4466ce11 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f9b4466d4ae in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f9b4466d560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f9b4467b7a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f9b3f89e078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #7 0x7f9b476476ba in start_thread (arg=0x7f9b3b418700) at pthread_create.c:333 #8 0x7f9b4e3e682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f9b3924c700 (LWP 31527)): #0 0x7f9b4e3d669d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9b45a2c740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9b459e8e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9b459e9340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9b459e94ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9b4afe221f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9b4af8ccea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9b4adb1fb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9b4e9f77a5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f9b4adb6b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9b476476ba in start_thread (arg=0x7f9b3924c700) at pthread_create.c:333 #11 0x7f9b4e3e682d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f9b4e9238c0 (LWP 31506)): [KCrash Handler] #6 0x7f9b4e026270 in ?? () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.16 #7 0x7f9b4e048fac in Konsole::Session::getDynamicTitle() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.16 #8 0x7f9b4e052ea3 in Konsole::SessionController::snapshot() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.16 #9 0x7f9b4afb9e76 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9b4afc6418 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f9b4afba9d3 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f9b4bb0e89c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f9b4bb16296 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f9b4af8ecf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f9b4afe116e in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f9b4afe16a1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f9b459e91a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f9b459e9400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Summary|Opening new message very|Plasmashell falls into high |slow and freezes KMail for |CPU load after a while, |several second each |desktop and kmail remains ||almost unresponsive ||(initial kmail issue) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Product|kmail2 |plasmashell Component|message list|general Version|Git (master)|5.8.4 CC||bhus...@gmail.com, ||plasma-b...@kde.org Target Milestone|--- |1.0 --- Comment #6 from René Krell <renda.kr...@gmail.com> --- This seems to become a plasmashell issue. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #5 from René Krell <renda.kr...@gmail.com> --- Created attachment 102662 --> https://bugs.kde.org/attachment.cgi?id=102662=edit Compressed output of valgrind --tool=callgrind --instr-atstart=no plasmashell for a few minutes after starting callgrind_control -i o Added the compressed output of 'valgrind --tool=callgrind --instr-atstart=no plasmashell' for a few minutes after starting 'callgrind_control -i o'. I started callgrind_control when kmail started to be unresponsive, including the rest of the plasmashell. I'm not able to interpret the output shown in kcachegrind. Can someone look at this, please? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #4 from René Krell <renda.kr...@gmail.com> --- I'm currently keeping plasmashell running in valgrind according to this comment: https://forum.kde.org/viewtopic.php?f=289=121533=7ab1403c4fedc79c23d4cadac1e09fd3=45#p343228 and waiting for plasmashell to fall into the high CPU load again, which is apparently the reason for the unresponsiveness of KMail. As soon as this will be the case I try to send some kcachegrind dump from it to get this issue to the right direction. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #3 from René Krell <renda.kr...@gmail.com> --- Sorry, that was to fast. Baloo isn't the cause. I run into this problem again with deactivated File Search, but now I have plasmashell at high load: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3392 rkrell20 0 0,255t 471020 187628 S 115,3 1,456 33:34.98 plasmashell There is no comparable process in this situation with such a high CPU load. Now even restarting KMail doesn't help. Navigating between messages is almost unresponsive in both accounts, IMAP and Local Folders. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #2 from René Krell <renda.kr...@gmail.com> --- The only process I saw with a high load during reproducing the problem was the baloo_file_extractor. After that I switched off Search -> File Search -> [ ] Enable File Search. Deactivating the Baloo File Extractor might be way how to avoid the issue reported here, I'll watch this several days. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #1 from René Krell <renda.kr...@gmail.com> --- Important addition: This problem doesn't happen right after system start, but some time after using KMail (after several seconds, minutes or even hours). At the moment I can't see it, but when it happens the notebook's fan is running on higher speed, probably due to a high CPU load. As soon as the problem occurs, KMail doesn't recover from it, so the high load remains instant until the next system restart. I nobody can reproduce this, please give me some hints what outputs to generate and provide, and what to do else to help analyzing. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] New: Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 Bug ID: 373368 Summary: Opening new message very slow and freezes KMail for several second each Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: --- KMail 5.3.3 (QtWebEngine), OpenSUSE Tumbleweed, Linux (x86_64) release 4.8.12-1-default: Kmail is very slow when navigating between messages in the message list. I have two accounts - an IMAP account (Activated Download all messages for offline use) and a Local Folders account. To be sure this is no migration problem from KDE 4 I stopped KMail and Akonadi and removed the following folders and files: ~/.local/share/akonadi ~/.config/akonadi ~/.kde4/share/config/akonadi* After that I restarted Akonadi and resynchronized the account again. Thus, this should be a clean state. When having synchronized all messages after the above cleanup action the problem reoccurs again: I click on several messages in the message list, marking a new message in the message list freezes KMail for several seconds before the new message is shown in the message window. This behavior happened from my point of view since the QtWebEngine has been introduced as message viewer. Because I've read about multi-threading problems of Nouveau, I tried also the native NVidia driver, no change so far. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 373344] New: Clear contact history does not clear anything instantly
https://bugs.kde.org/show_bug.cgi?id=373344 Bug ID: 373344 Summary: Clear contact history does not clear anything instantly Product: telepathy Version: git-latest Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: log-viewer Assignee: kde-telepathy-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: Future In log viewer, if I select a contact history and using the contect menu on the contact name, choosing Clear contact history I get the following: - A warning message box appears: Are you sure ->Choose button Delete - Only the contact disappears in the left upper part of the log viewer, but the messages (dates and contents) are still shown below. - If restarting the log viewer also the contact name itself is available again, along with all the contact history. At the end, nothing is deleted at all. I f deleting, I'd expect the contact and its history disappera instantly from log viewer unless there is no new message in a chat from that contact. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 373343] New: Open "Previous Conversations" from chat window doesn't preselected the dedicated user in log viewer
https://bugs.kde.org/show_bug.cgi?id=373343 Bug ID: 373343 Summary: Open "Previous Conversations" from chat window doesn't preselected the dedicated user in log viewer Product: telepathy Version: git-latest Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: log-viewer Assignee: kde-telepathy-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: Future When chatting with a contact, opening Conversation -> Previous Conversations does never pre-select the dedicated contact in the log viewer. I must always filter or find the contact from the chat window manually in the log viewer instead, after the log viewer opened from that menu. I'd expect there are immediately displayed only conversations from the contact I'm in chat with. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347041] Tooltip interaction in multi-row Task Manager suffers from not being able to reach tooltip for lower rows of delegates
https://bugs.kde.org/show_bug.cgi?id=347041 René Fürst <r...@fuerst.biz> changed: What|Removed |Added CC||r...@fuerst.biz --- Comment #3 from René Fürst <r...@fuerst.biz> --- I haven't tested it but I think the patches in bug 358930 should also fix this. -- You are receiving this mail because: You are watching all bug changes.
