[digikam] [Bug 385726] Add Support For Motion Photos - Use ExifTool to extract data
https://bugs.kde.org/show_bug.cgi?id=385726 Sammy changed: What|Removed |Added CC||sa...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 480593] Multiple axes Placement not stored
https://bugs.kde.org/show_bug.cgi?id=480593 Sammy changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #7 from Sammy --- Good morning, I installed the latest nightly flatpak, but the problem persists. I can see, that the UI differs from the nightly release before (LapPlot draws boxes around elements such as additional y-axes), but after repositioning the axes, saving and reopening all the additional y-axes are in the center again. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 480593] Multiple axes Placement not stored
https://bugs.kde.org/show_bug.cgi?id=480593 --- Comment #11 from Sammy --- Oh no! Now I see, I repositioned the axes not the right way. When I choose position from the General tab it works like a charm. I positioned the axes by clicking on them and then use the arrow keys to move them to the desired location. This placement is still not stored. Is this the desired behavior? If so, then we can happily close this bugreport and I want to say thank you for your kind help! -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 480593] Multiple axes Placement not stored
https://bugs.kde.org/show_bug.cgi?id=480593 --- Comment #14 from Sammy --- Hey, is it helpful if I test with the latest nightly if I can confirm the fix? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 480593] New: Multiple axes Placement not stored
https://bugs.kde.org/show_bug.cgi?id=480593 Bug ID: 480593 Summary: Multiple axes Placement not stored Classification: Applications Product: LabPlot2 Version: 2.10.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: sa...@posteo.de Target Milestone: --- Created attachment 165390 --> https://bugs.kde.org/attachment.cgi?id=165390&action=edit LabPlot Plot with 4 y-axes SUMMARY If you create a plot with multiple axes (https://labplot.kde.org/2021/10/27/multi-axes-made-easy/) and have custom places for them. The placement is not restored when reopening the file. STEPS TO REPRODUCE 1. Create Graph with multi axes 2. Move the axes to the left 3. save and exit 4. open the saved file OBSERVED RESULT All axes except the first one are in the middle of the graph). EXPECTED RESULT The placement of the axes from step 2 should be restored. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Leap 15.5 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 LapPlot installed from flathub ADDITIONAL INFORMATION: The plot where I had the problem is attached. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 480593] Multiple axes Placement not stored
https://bugs.kde.org/show_bug.cgi?id=480593 Sammy changed: What|Removed |Added Platform|Other |Flatpak OS|Other |Linux -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 480593] Multiple axes Placement not stored
https://bugs.kde.org/show_bug.cgi?id=480593 Sammy changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #2 from Sammy --- Hi, thanks for the fast reply. I switched to the nightly version, but unfortunately the problem seems to persist. I saved the plot once again with the correct positions of the axes and after reopening, they are in the middle again. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 480593] Multiple axes Placement not stored
https://bugs.kde.org/show_bug.cgi?id=480593 --- Comment #4 from Sammy --- (In reply to Alexander Semke from comment #3) > (In reply to Sammy from comment #2) > > Hi, > > > > thanks for the fast reply. I switched to the nightly version, but > > unfortunately the problem seems to persist. I saved the plot once again with > > the correct positions of the axes and after reopening, they are in the > > middle again. > Can you please paste the content shown in the first tab in the "About > LabPlot"-dialog? Oh course. Now I'm a bit puzzled. In the window head it says nightly, but in the about window not. Window title: LabPlot (Nightly) About Window content: LabPlot is a FREE, open-source and cross-platform Data Visualization and Analysis software accessible to everyone. Debug build 69216fe Jan 4 2024, 23:56:16 System: KDE Flatpak runtime Locale: German,Germany (Decimal point ',', Group separator '.' Number settings: Decimal point ',', Group separator '.', Exponential 'e', Zero digit '0', Percent '%', Positive/Negative sign '+'/'-' (Updated on restart) Architecture: x86_64-little_endian-lp64 Kernel: linux 5.14.21-150500.55.44-default C++ Compiler: GNU 12.2.0 C++ Compiler Flags: -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -fdiagnostics-color=always -Wall -Wextra -Wundef -Wpointer-arith -Wunreachable-code -Wunused -Wdeprecated-declarations -fno-omit-frame-pointer -fstack-protector -fexceptions -std=c++17 -O2 -Wcast-align -Wswitch-enum -fvisibility=default -pedantic -Wzero-as-null-pointer-constant (c) 2007-2023 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452253] New: No Progress bar in system tray
https://bugs.kde.org/show_bug.cgi?id=452253 Bug ID: 452253 Summary: No Progress bar in system tray Product: lattedock Version: 0.9.11 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: sa...@posteo.de Target Milestone: --- If I have the system tray in a latte panel I don't get a progress indication. For example when copying files with dolphin. The system tray is working (with progress indication) when it sits in a kde panel. For reference: https://www.reddit.com/r/kde/comments/jb83fw/dolphin_progress_bar_disappeared/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 452253] No Progress bar in system tray
https://bugs.kde.org/show_bug.cgi?id=452253 --- Comment #3 from Sammy --- Thanks for your response. I will do accordingly. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Sammy changed: What|Removed |Added CC||sa...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435177] New: Interactive reports
https://bugs.kde.org/show_bug.cgi?id=435177 Bug ID: 435177 Summary: Interactive reports Product: kmymoney Version: 5.1.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: sa...@posteo.de Target Milestone: --- Dear kmymoney-Team, I have a suggestion for the wishlist. For my usecase the reports would be much more useful, if they were interactive. For example: If I have a report diagram (amount of money over time) where I monitor my monthly expenses split up into categories, it would be awesome to be able to interactively select the categories, which are monitored in the diagram. This would make it a lot easier to investigate where expenses increased. Best wishes! Samuel -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435177] Interactive reports
https://bugs.kde.org/show_bug.cgi?id=435177 Sammy changed: What|Removed |Added CC||sa...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425455] New: Dolphin crashes, then i try to create a new link to a folder for the page entry
https://bugs.kde.org/show_bug.cgi?id=425455 Bug ID: 425455 Summary: Dolphin crashes, then i try to create a new link to a folder for the page entry Product: dolphin Version: 19.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: xx1supercoolerbo...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (19.12.3) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-42-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I tried to create a shortcut for the page entry before it crashed. After that I tried 2-3 more times without success. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fda0c02fe80 (LWP 4634))] Thread 8 (Thread 0x7fd9f5f8c700 (LWP 4642)): #0 __GI___libc_read (nbytes=16, buf=0x7fd9f5f8bb90, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=19, buf=0x7fd9f5f8bb90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fda0e6df89f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fda0e696cfe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fda0e697152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fda0e6972e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fda107a4583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fda1074b4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fda10583785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fda105849d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fda0efd8609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fda12897103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fda0117e700 (LWP 4641)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563d41df26d8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563d41df2688, cond=0x563d41df26b0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563d41df26b0, mutex=0x563d41df2688) at pthread_cond_wait.c:638 #3 0x7fda02dfe62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fda02dfe23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fda0efd8609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fda12897103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fda0197f700 (LWP 4640)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563d41df26d8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563d41df2688, cond=0x563d41df26b0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563d41df26b0, mutex=0x563d41df2688) at pthread_cond_wait.c:638 #3 0x7fda02dfe62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fda02dfe23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fda0efd8609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fda12897103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fda02180700 (LWP 4639)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563d41df26d8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563d41df2688, cond=0x563d41df26b0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563d41df26b0, mutex=0x563d41df2688) at pthread_cond_wait.c:638 #3 0x7fda02dfe62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fda02dfe23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fda0efd8609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fda12897103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fda02981700 (LWP 4638)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563d41df26d8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563d41df2688, cond=0x563d41df26b0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563d41df26b0, mutex=0x563d41df2688) at pthread_cond_wait.c:638 #3 0x7fda02dfe62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fda02dfe23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fda0efd8
[dolphin] [Bug 425455] Dolphin crashes, then i try to create a new link to a folder for the page entry
https://bugs.kde.org/show_bug.cgi?id=425455 --- Comment #2 from Sammy --- (In reply to Julian Steinmann from comment #1) > Hi, what do you mean by "page entry"? When I create a new "Link to > Location", I cannot get Dolphin to crash (using Dolphin 20.11.70). Hi, on the left side there are different links to folders like main directory, downloads etc. if i try to add another entry now it crashes. interestingly enough, it worked when i reinstalled the program. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412709] New: Libreoffice windows and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=412709 Bug ID: 412709 Summary: Libreoffice windows and virtual desktops Product: kwin Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: sa...@posteo.de Target Milestone: --- SUMMARY I have my windows arranged on six virtual desktops. However if I open a file in Libreoffice all libreoffice windows go to the current virtual desktop. This can be very annoying. STEPS TO REPRODUCE 1. distribute some libreoffice windows on different virtual desktops 2. open a file from the libreoffice open dialog OBSERVED RESULT 3. the distributed windows of libreoffice are now all on the current workspace EXPECTED RESULT the distributed windows stay on the virtual desktop as before and a new libreoffice window opens with the selected file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Stable (buster) (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION I'm actually not sure if this belongs here, because it could also be an libreoffice problem, but it seems connected to kde. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412709] Libreoffice windows and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=412709 Sammy changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412709] Libreoffice windows and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=412709 --- Comment #2 from Sammy --- If you uninstall the kde integration of LO everything seems to work as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412709] Libreoffice windows and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=412709 --- Comment #5 from Sammy --- Actually I don't understand what that means actually. Is it a problem of LO and should I report it there? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412709] Libreoffice windows and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=412709 --- Comment #9 from Sammy --- You can workaround this bug by selecting the Libreiffice Open/Save Dialogs under Extras > Options > Libreoffice > General. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412709] Libreoffice windows and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=412709 --- Comment #7 from Sammy --- I'm sorry to bother again. Are there any news on this? Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394688] New: Toolbar Crashes When Clicking on Start Icon
https://bugs.kde.org/show_bug.cgi?id=394688 Bug ID: 394688 Summary: Toolbar Crashes When Clicking on Start Icon Product: plasmashell Version: 5.12.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: samex...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.10.0 Frameworks Version: 5.46.0 Operating System: Linux 4.16.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Clicked on the start icon after starting an application - Unusual behavior I noticed: Toolbar disappeared and the desktop reset. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa98c5335c0 (LWP 6809))] Thread 20 (Thread 0x7fa8713fb700 (LWP 12769)): #0 0x7fa98515056c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa985fa5efb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x558b19da2c00) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x7fa970039118, mutex=mutex@entry=0x7fa970039110, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fa989d52ac8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7fa970039108) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7fa970039090) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:708 #5 0x7fa989d52efa in QSGRenderThread::run (this=0x7fa970039090) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:737 #6 0x7fa985fa4ba0 in QThreadPrivate::start (arg=0x7fa970039090) at thread/qthread_unix.cpp:376 #7 0x7fa98514a59b in start_thread () from /lib64/libpthread.so.0 #8 0x7fa98589da1f in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7fa873fff700 (LWP 12768)): #0 0x7fa98515056c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa985fa5efb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x558b19f963d0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x558b15c193d8, mutex=mutex@entry=0x558b15c193d0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fa989d52ac8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x558b15c193c8) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x558b15c19350) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:708 #5 0x7fa989d52efa in QSGRenderThread::run (this=0x558b15c19350) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:737 #6 0x7fa985fa4ba0 in QThreadPrivate::start (arg=0x558b15c19350) at thread/qthread_unix.cpp:376 #7 0x7fa98514a59b in start_thread () from /lib64/libpthread.so.0 #8 0x7fa98589da1f in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7fa893d70700 (LWP 12767)): #0 0x7fa98515056c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa985fa5efb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x558b1882afb0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x558b1883dbd8, mutex=mutex@entry=0x558b1883dbd0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fa989d52ac8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x558b1883dbc8) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x558b1883db50) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:708 #5 0x7fa989d52efa in QSGRenderThread::run (this=0x558b1883db50) at /usr/src/debug/libqt5-qtdeclarative-5.10.0-2.2.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:737 #6 0x7fa985fa4ba0 in QThreadPrivate::start (arg=0x558b1883db50) at thread/qthread_unix.cpp:376 #7 0x7fa98514a59b in start_thread () from /lib64/libpthread.so.0 #8 0x7fa98589da1f in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7fa895072700 (LWP 12766)): #0 0x7fa98515056c in pthread_cond_wait@@GLIBC_2.3.2 () from /
[okular] [Bug 443404] Mousewheel scroll does not work in full page size and non-continous mode for some mouses
https://bugs.kde.org/show_bug.cgi?id=443404 Sammy Bresel changed: What|Removed |Added OS|All |Linux Platform|unspecified |Ubuntu Status|ASSIGNED|CONFIRMED CC||euredudehe...@googlemail.co ||m Version|21.08.1 |21.12.3 --- Comment #16 from Sammy Bresel --- I have the same problem using a Logitech M720. - Kubuntu 22.04 KDE-Plasma-Version: 5.24.7 KDE-Frameworks-Version: 5.92.0 Qt-Version: 5.15.3 Kernel-Version: 5.15.0-58-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 385364] Timezone RRULE entry has bot UNTIL and COUNT property
https://bugs.kde.org/show_bug.cgi?id=385364 Sammy Bresel changed: What|Removed |Added CC||euredudehe...@googlemail.co ||m --- Comment #11 from Sammy Bresel --- I have the same Problem with KORganizer Version 5.7.3 on Ubuntu 18.04.2. It occours when i create events with KOrganizer and want to sync them with posteo.de which uses CalDAV. The events are synced on the Server, are synced between KDE clients, but in Outlook with CalDav Synchronizer (3.6.1.0) i get the error. -- You are receiving this mail because: You are watching all bug changes.
