[okular] [Bug 442503] Scroll Page Up teleports to top of previous page if in non-continuous view and trimmed view
https://bugs.kde.org/show_bug.cgi?id=442503 Wouter M. Koolen changed: What|Removed |Added Version|21.08.1 |22.04.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442503] Scroll Page Up teleports to top of previous page if in non-continuous view and trimmed view
https://bugs.kde.org/show_bug.cgi?id=442503 --- Comment #13 from Wouter M. Koolen --- Dear David, This is to confirm that the bug occurs when trimming is used. I always use Trim Margins. I tested with 21.08.0. Without any Trimming applied, the problem is absent. With Trim Margins as well as with Trim to Selection the problem is present. Cheers, Wouter On 17/09/2021 20:11, David Hurka wrote: > https://bugs.kde.org/show_bug.cgi?id=442503 > > David Hurka changed: > > What|Removed |Added > > Summary|Scroll Page Up teleports to |Scroll Page Up teleports to > |top of previous page|top of previous page if in > ||non-continuous view and > ||trimmed view > Status|REPORTED|CONFIRMED > Ever confirmed|0 |1 > > --- Comment #12 from David Hurka --- > Wow, you are fast. Yes, this helps! > > I guess you have View -> Trim View -> Trim to Selection enabled, but you did > not select anything, or something similar. > > I can reproduce the issue when I enable Trim to Selection and select some > area. > -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442503] Scroll Page Up teleports to top of previous page
https://bugs.kde.org/show_bug.cgi?id=442503 --- Comment #11 from Wouter M. Koolen --- Dear David, Sure! 61551d2356ea5f93ba3e921a1c4ab9cca88fdbda is the first bad commit commit 61551d2356ea5f93ba3e921a1c4ab9cca88fdbda Author: Gerd Wachsmuth Date: Thu Apr 1 11:58:53 2021 +0200 Fix: Viewport coords normalized w.r.t. full page The coordinates in Viewport.rePos are normalized on the full page. In two functions within pageview.cpp, these were treated as coordinates on the cropped page. CCBUG: 198427 This partially fixes the bug 198427 in the case that the cropping of the target pages (and the pages around the target) is known at the time the link is clicked. That is, it works if - One uses 'Trim To Selection' - One uses 'Trim To Margin' and has already viewed at the target page(s). In the case that the cropping of the page at the target is unknown, we still end up at the wrong position. autotests/data/pdf_with_internal_links.pdf | Bin 0 -> 60899 bytes autotests/data/pdf_with_internal_links.tex | 9 ++ autotests/parttest.cpp | 44 + part/pageview.cpp | 18 +--- 4 files changed, 67 insertions(+), 4 deletions(-) create mode 100644 autotests/data/pdf_with_internal_links.pdf create mode 100644 autotests/data/pdf_with_internal_links.tex Here is the full log: git bisect start # good: [6f5b23290fdd2ada8e0e7f44ffada02c978d0c6a] presentation: Show better the status of the "playing" button git bisect good 6f5b23290fdd2ada8e0e7f44ffada02c978d0c6a # bad: [4afd21470147dd7b20f21e8edf20e5f350f98df3] ToggleActionMenu::createWidget(): Do not crash if parent is not a QToolBar git bisect bad 4afd21470147dd7b20f21e8edf20e5f350f98df3 # good: [67325270eca8bc5a725a4a0283537b8078d9c1a6] Fix viewport jumps when drag-scrolling beyond screen edges git bisect good 67325270eca8bc5a725a4a0283537b8078d9c1a6 # bad: [b15accd0ae51c68fbd1b1b09a3d12ffcd24a5f55] Checks whether the pdf is broken or not git bisect bad b15accd0ae51c68fbd1b1b09a3d12ffcd24a5f55 # bad: [394001017e9ddfba941fb0fc9162bbfd10c49392] Merge remote-tracking branch 'origin/release/21.04' git bisect bad 394001017e9ddfba941fb0fc9162bbfd10c49392 # good: [6b3da83f69d1d61baf5f056494d4ae809ee41825] Merge remote-tracking branch 'origin/release/21.04' git bisect good 6b3da83f69d1d61baf5f056494d4ae809ee41825 # bad: [61551d2356ea5f93ba3e921a1c4ab9cca88fdbda] Fix: Viewport coords normalized w.r.t. full page git bisect bad 61551d2356ea5f93ba3e921a1c4ab9cca88fdbda # good: [e8e4cd7c6dc28deead28682a876dd0e2e4ef643d] GIT_SILENT Upgrade release service version to 21.04.0. git bisect good e8e4cd7c6dc28deead28682a876dd0e2e4ef643d # good: [ff5f4cbc453d37f5c70e7c31a6c22105cee994fc] Open the signed document on the page with the new signature git bisect good ff5f4cbc453d37f5c70e7c31a6c22105cee994fc # good: [218c5ab64ea2865272a26f18b22c8047226ad957] GIT_SILENT made messages (after extraction) git bisect good 218c5ab64ea2865272a26f18b22c8047226ad957 # first bad commit: [61551d2356ea5f93ba3e921a1c4ab9cca88fdbda] Fix: Viewport coords normalized w.r.t. full page Hope this helps. Cheers, Wouter On 17/09/2021 13:19, David Hurka wrote: > https://bugs.kde.org/show_bug.cgi?id=442503 > > David Hurka changed: > > What|Removed |Added > > Status|NEEDSINFO |REPORTED > Resolution|WAITINGFORINFO |--- > > --- Comment #10 from David Hurka --- > Thanks. I think I recreated all preconditions correctly, but unfortunately > still can not reproduce the issue. > > I don’t know what else could be relevant. > > If you know how to do that, you may build Okular from source and do a git > bisect to find the problem. The source is located at > https://invent.kde.org/graphics/okular. The README.md contains a description > how to build from source. If you are interested, we can help you with that. :) > -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442503] Scroll Page Up teleports to top of previous page
https://bugs.kde.org/show_bug.cgi?id=442503 --- Comment #2 from Wouter M. Koolen --- Dear David, Thanks for looking at this. I checked, and smooth scrolling does not matter. Here are four screenshots using a random example PDF I found here https://juventudedesporto.cplp.org/files/sample-pdf_9359.pdf To interpret the file names: old is 20.12.3, new is 21.08.0. The four numbers are as follows: 1) after opening Okular, loading the PDF from the command line 2) after pressing Space once (now we're on the bottom of page 1) 3) after pressing Space once more (now we're on the top of page 2) 4) after pressing Shift-Space. now we're either on the top (new) or bottom (old) of page 1. I'm using Plasma on X, not wayland. The fact that you cannot reproduce it makes me think it is a dependency issue. I noticed that upgrade/downgrade of okular pulls in a matching version of libokular5core9, and changes nothing else on the system. Cheers, Wouter On 16/09/2021 22:36, David Hurka wrote: > https://bugs.kde.org/show_bug.cgi?id=442503 > > David Hurka changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from David Hurka --- > Can not reproduce with Okular 21.08.1 on KDE Neon user edition. > > Can you provide screenshots or a screencast of the whole window, so we can try > to reconstruct more precisely? > > Can you provide more information on your configuration? Do you have smooth > scrolling enabled (if that makes a difference)? > > (Besides that, this is an excellent bug report. :) ) > -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442503] New: Scroll Page Up teleports to top of previous page
https://bugs.kde.org/show_bug.cgi?id=442503 Bug ID: 442503 Summary: Scroll Page Up teleports to top of previous page Product: okular Version: 21.08.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: onkekabo...@hotmail.com Target Milestone: --- SUMMARY In non-continuous scrolling mode, scrolling backwards over a page boundary (either with scroll wheel, Shift-Space or PgUp) has the effect that the top of the previous page is shown. In earlier versions the bottom of the previous page was shown, which is the expected behaviour (so that Scroll Page Down and Scroll Page Up actions are each others' inverses). STEPS TO REPRODUCE 1. Open any pdf with more than one page in Single Page, non-continuous view mode. Size the window so that a vertical scroll bar is showing. 2. Navigate to the top of page 2 (e.g. by pressing the space bar twice) 3. Scroll up (e.g. by pressing Shift-Space or PgUp, or by mouse wheeling up) OBSERVED RESULT Okular displays the topmost part of page 1 EXPECTED RESULT Okular displays the bottommost part of page 1 SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.4 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700 CPU @ 3.60GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 ADDITIONAL INFORMATION This bug is not present in version 20.12.3, while it appears in 21.08.0 and 21.08.1. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432025] New: Find box is capturing keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=432025 Bug ID: 432025 Summary: Find box is capturing keyboard shortcuts Product: okular Version: 20.12.1 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: onkekabo...@hotmail.com Target Milestone: --- SUMMARY The okular "find" box is capturing shortcut keys and interpreting them as text. STEPS TO REPRODUCE 1. Open a PDF in okular. Hit Ctrl-F to open search box at the bottom. 2. Type a search term. 3. Hit a keyboard shortcut. Ctrl-F, Alt-n, Alt-p, Escape. OBSERVED RESULT The keyboard shortcut is not passed on to the application by the search box. In the case of 'Alt-n or Alt-p' the letter 'n' or 'p' are input in the find textbox. In case of 'Ctrl-F' the find box is not reactiated (it used to do a select-all in the find textbox). In case of 'Esc' nothing happens. These keyboard shortcuts do work when first clicking on the PDF body. EXPECTED RESULT Keyboard shortcuts should not be captured by the search box, but passed on to the encompassing application so they can be interpreted correctly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.10 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages okular depends on: ii kinit 5.78.0-2 ii kio 5.78.0-2 ii libc6 2.31-9 ii libfreetype6 2.10.4+dfsg-1 ii libjpeg62-turbo 1:2.0.5-2 ii libkf5activities5 5.78.0-2 ii libkf5archive55.78.0-2 ii libkf5bookmarks5 5.78.0-2 ii libkf5codecs5 5.78.0-2 ii libkf5completion5 5.78.0-2 ii libkf5configcore5 5.78.0-3 ii libkf5configgui5 5.78.0-3 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons5 5.78.0-2 ii libkf5crash5 5.78.0-3 ii libkf5i18n5 5.78.0-2 ii libkf5iconthemes5 5.78.0-2 ii libkf5itemviews5 5.78.0-2 ii libkf5jobwidgets5 5.78.0-2 ii libkf5kexiv2-15.0.0 20.12.0-1 ii libkf5kiocore55.78.0-2 ii libkf5kiowidgets5 5.78.0-2 ii libkf5parts5 5.78.0-2 ii libkf5pty55.78.0-2 ii libkf5purpose-bin 5.78.0-2 ii libkf5purpose55.78.0-2 ii libkf5service-bin 5.78.0-2 ii libkf5service55.78.0-2 ii libkf5textwidgets55.78.0-2 ii libkf5wallet-bin 5.78.0-2 ii libkf5wallet5 5.78.0-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5windowsystem5 5.78.0-2 ii libkf5xmlgui5 5.78.0-2 ii libokular5core9 4:20.12.1-1 ii libphonon4qt5-4 4:4.11.1-3 ii libpoppler-qt5-1 20.09.0-3.1 ii libqmobipocket2 4:20.12.0-1 ii libqt5core5a 5.15.2+dfsg-2 ii libqt5dbus5 5.15.2+dfsg-2 ii libqt5gui55.15.2+dfsg-2 ii libqt5printsupport5 5.15.2+dfsg-2 ii libqt5svg55.15.2-2 ii libqt5texttospeech5 5.15.2-2 ii libqt5widgets55.15.2+dfsg-2 ii libqt5xml55.15.2+dfsg-2 ii libspectre1 0.2.9-1 ii libstdc++610.2.1-6 ii phonon4qt54:4.11.1-3 ii zlib1g1:1.2.11.dfsg-2 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 397314] New: korganizer segfaults on exit
https://bugs.kde.org/show_bug.cgi?id=397314 Bug ID: 397314 Summary: korganizer segfaults on exit Product: korganizer Version: 5.7.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: onkekabo...@hotmail.com Target Milestone: --- Application: korganizer (5.7.3) Qt Version: 5.10.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.13 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Korganizer always segfaults on exit. - Custom settings of the application: I have setup a view filter that hides completed TODOs. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2df783e2c0 (LWP 11036))] Thread 5 (Thread 0x7f2decf00700 (LWP 11041)): #0 0x7f2e0ced7739 in __GI___poll (fds=0x7f2de4003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e04006439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2e0400654c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2e0d41a64b in QEventDispatcherGlib::processEvents (this=0x7f2de4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2e0d3c71fb in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2e0d1fc316 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2e0d200f90 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #7 0x7f2e058edf2a in start_thread (arg=0x7f2decf00700) at pthread_create.c:463 #8 0x7f2e0cee1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f2ded701700 (LWP 11039)): #0 0x7f2e0ced7739 in __GI___poll (fds=0x7f2de002b460, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e04006439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2e0400654c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2e0d41a64b in QEventDispatcherGlib::processEvents (this=0x7f2deb20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2e0d3c71fb in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2e0d1fc316 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2e0d200f90 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #7 0x7f2e058edf2a in start_thread (arg=0x7f2ded701700) at pthread_create.c:463 #8 0x7f2e0cee1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2dee912700 (LWP 11038)): #0 0x7f2e0ced7739 in __GI___poll (fds=0x7f2de8004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e04006439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2e0400654c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2e0d41a64b in QEventDispatcherGlib::processEvents (this=0x7f2de8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2e0d3c71fb in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f2e0d1fc316 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f2e0c5a4015 in QDBusConnectionManager::run (this=0x7f2e0c618d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f2e0d200f90 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #8 0x7f2e058edf2a in start_thread (arg=0x7f2dee912700) at pthread_create.c:463 #9 0x7f2e0cee1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2df51cb700 (LWP 11037)): #0 0x7f2e0ced7739 in __GI___poll (fds=0x7f2df51cac78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e03b970f7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2e03b98d1a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2df753e6e9 in QXcbEventReader::run (this=0x55ed13bac4e0) at qxcbconnection.h:408 #4 0x7f2e0d200f90 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #5 0x7f2e058edf2a in start_thread (arg=0x7f2df51cb700) at pthread_create.c:463 #6 0x7f2e0cee1edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2df783e2c0 (LWP 11036)): [KCrash Handler] #6 0x7f2e0bab8738 in QSharedPointer::data (this=0x82) at
[korganizer] [Bug 383661] enabling "hide completed todos" in a view filter causes korganizer to segfault on exit
https://bugs.kde.org/show_bug.cgi?id=383661 Wouter M. Koolen <onkekabo...@hotmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Wouter M. Koolen <onkekabo...@hotmail.com> --- Indeed, after upgrading to ii libkf5widgetsaddons5:amd64 5.37.0-2 amd64 add-on widgets and classes for applications that use the Qt Widget the crash is gone. Thanks, Wouter -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 383661] enabling "hide completed todos" in a view filter causes korganizer to segfault on exit
https://bugs.kde.org/show_bug.cgi?id=383661 --- Comment #2 from Wouter M. Koolen <onkekabo...@hotmail.com> --- Dear Christoph, I am running ii libkf5widgetsaddons5:amd64 5.28.0-3 amd64 add-on widgets and classes for applications that use the Qt Widgets module Cheers, Wouter On 07/09/17 23:31, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=383661 > > --- Comment #1 from Christoph Feck <cf...@kde.org> --- > This is probably a duplicate of bug 353380. Which kwidgetsaddons (Frameworks) > version are you using? > -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 383661] New: enabling "hide completed todos" in a view filter causes korganizer to segfault on exit
https://bugs.kde.org/show_bug.cgi?id=383661 Bug ID: 383661 Summary: enabling "hide completed todos" in a view filter causes korganizer to segfault on exit Product: korganizer Version: 5.2.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: onkekabo...@hotmail.com Target Milestone: --- Created attachment 107344 --> https://bugs.kde.org/attachment.cgi?id=107344=edit Output log with "hide completed todos" disabled and enabled Steps to reproduce: - create a new view filter - tick 'hide completed todos' - exit korganizer Result: Thread 1 "korganizer" received signal SIGSEGV, Segmentation fault. 0x7f196507b504 in QAbstractScrollArea::horizontalScrollBar() const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 (gdb) bt #0 0x7f196507b504 in QAbstractScrollArea::horizontalScrollBar() const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #1 0x7f195e3ca037 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #2 0x7f1963ed2c41 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f1964ec6bec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x7f1964ece381 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7f1963ea6850 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f1963ea8fed in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1963ef9fb3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f195989ebf7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f195989ee60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f195989ef0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f1963efa3bf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1963ea483a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1963eacedc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00018f14 in ?? () #15 0x7f19633162b1 in __libc_start_main (main=0x18ab0, argc=1, argv=0x7fffdf68, init=, fini=, rtld_fini=, stack_end=0x7fffdf58) at ../csu/libc-start.c:291 #16 0x000190aa in _start () I also noted that the debugging? output of korganizer is different with and without the view filter enabled. Both outputs attached. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 331543] New event dialog has "Calendar:" misplaced in tab order
https://bugs.kde.org/show_bug.cgi?id=331543 --- Comment #5 from Wouter M. Koolen <onkekabo...@hotmail.com> --- On 27/09/16 02:50, Denis Kurz via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=331543 > > Denis Kurz <kde...@posteo.de> changed: > > What|Removed |Added > > CC||kde...@posteo.de > > --- Comment #4 from Denis Kurz <kde...@posteo.de> --- > Wouter, that's strange. I tried to reproduce it myself, and it works for me, > in > KOrganizer 5.3.1. Double click + shift+tab, and the focus jumps to the > calendar > dropdown. Since there's been very little activity in KOrganizer lately, I > don't > think that this was fixed recently. > > Does KOrganizer itself report the version 5.2.3 for you? You can get it to > report its version by launching it standalone (not as part of Kontact), and > then via "Help -> About KOrganizer", in the Version tab. Or maybe you only > have > one calendar configured? > Dear Denis, That is wild :) There must be some crucial difference between our setups. I do not see it yet though. I am starting korganizer from bash (in kopete). I got my version number from the about dialog, as you describe. I have 5 calendards configured, so that is not it either. I tried LC_ALL=C LANGUAGE=en_US:en korganizer (since I have some of these set to a mix of GB and NL) but that did not change anything. Below is the output from reportbug korganizer, it should show the current installed version of all related packages. Maybe you can compare to yours and spot the crucial diff. Any other ideas? Cheers, Wouter Package: korganizer Version: 4:16.04.3-1 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.5+ (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages korganizer depends on: ii kdepim-runtime 4:16.04.2-2 ii kf5-kdepimlibs-kio-plugins 4:16.04.2-2 ii libc62.23-5 ii libgcc1 1:6.1.1-11 ii libkf5akonadicalendar5 16.04.2-2 ii libkf5akonadicontact54:16.04.2-2 ii libkf5akonadicore-bin4:16.04.3-2 ii libkf5akonadicore5 4:16.04.3-2 ii libkf5akonadimime5 4:16.04.2-2 ii libkf5akonadinotes5 4:16.04.2-2 ii libkf5akonadisearchpim5 16.04.2-2 ii libkf5akonadiwidgets54:16.04.3-2 ii libkf5calendarcore5 4:16.04.2-1 ii libkf5calendarsupport5 4:16.04.2-2 ii libkf5calendarutils5 16.04.3-1 ii libkf5codecs55.25.0-1 ii libkf5completion55.25.0-1 ii libkf5configcore55.25.0-1 ii libkf5configgui5 5.25.0-1 ii libkf5configwidgets5 5.25.0-1 ii libkf5contacts5 16.04.2-1 ii libkf5coreaddons55.25.0-1 ii libkf5dbusaddons55.25.0-1 ii libkf5eventviews54:16.04.2-2 ii libkf5holidays5 16.04.2-1 ii libkf5i18n5 5.25.0-1 ii libkf5iconthemes55.25.0-1 ii libkf5identitymanagement516.04.2-1 ii libkf5incidenceeditor-bin16.04.2-2 ii libkf5incidenceeditor5 16.04.2-2 ii libkf5itemmodels55.25.0-1 ii libkf5itemviews5 5.25.0-1 ii libkf5jobwidgets55.25.0-1 ii libkf5kcmutils5 5.25.0-1 ii libkf5kdelibs4support5 5.25.0-1 pn libkf5kdepimdbusinterfaces5 ii libkf5kiocore5 5.25.0-1 ii libkf5kiowidgets55.25.0-1 ii libkf5kontactinterface5 16.04.2-1 ii libkf5libkdepim-plugins 4:16.04.2-3 ii libkf5libkdepim5 4:16.04.2-3 pn libkf5mailcommon-plugins pn libkf5mailcommon5 ii libkf5mailtransport5 16.04.2-2 ii libkf5mime5 16.04.2-1 ii libkf5newstuff5 5.25.0-1 ii libkf5notifications5 5.25.0-1 ii libkf5parts5 5.25.0-1 ii libkf5pimcommon-plugins 4:16.04.2-2 ii libkf5pimcommon5 4:16.04.2-2 ii libkf5pimtextedit5 16.04.2-1 ii libkf5service-bin5.25.0-1 ii libkf5service5 5.25.0-1 ii libkf5widgetsaddons5 5.25.0-1 ii libkf5windowsystem5 5.25.0-1 ii libkf5xmlgui55.25.0-1 ii libphonon4qt5-4 4:4.9.0-4 ii libqt5core5a 5.6.1+dfsg-3+b1 ii libqt5dbus5 5.6.1+dfsg-3+b1 ii libqt5gui5 5.6.1+dfsg-3+b1 ii libqt5widgets5 5.6.1+dfsg-3+b1 ii libstdc++6
[korganizer] [Bug 331543] New event dialog has "Calendar:" misplaced in tab order
https://bugs.kde.org/show_bug.cgi?id=331543 --- Comment #3 from Wouter M. Koolen <onkekabo...@hotmail.com> --- Dear Denis, Nothing has changed regarding this bug. I can confirm it for Korganizer 5.2.3. To hit it, start creating a new event by double clicking anywhere on the calendar. The New Event dialog comes up, with the keyboard focus in a text field labelled "Title". Now press shift-tab. You expect to be in the calendar dropdown list, but the focus jump straight to the cancel button. Cheers, Wouter On 25/09/16 03:52, Denis Kurz via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=331543 > > Denis Kurz <kde...@posteo.de> changed: > > What|Removed |Added > > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Denis Kurz <kde...@posteo.de> --- > This bug has only been reported for versions before 4.14, which have been > unsupported for at least two years now. Can anyone tell if this bug still > present? > > If noone confirms this bug for a Framework-based version of korganizer > (version > 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in > about three months. > -- You are receiving this mail because: You are watching all bug changes.
