[kapptemplate] [Bug 445293] KParts template fails to find the part
https://bugs.kde.org/show_bug.cgi?id=445293 Adrien Cordonnier changed: What|Removed |Added CC||adrien.cordonn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kapptemplate] [Bug 396677] KParts template fails to find the part
https://bugs.kde.org/show_bug.cgi?id=396677 Adrien Cordonnier changed: What|Removed |Added Blocks||445293 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=445293 [Bug 445293] KParts template fails to find the part -- You are receiving this mail because: You are watching all bug changes.
[kapptemplate] [Bug 445293] New: KParts template fails to find the part
https://bugs.kde.org/show_bug.cgi?id=445293 Bug ID: 445293 Summary: KParts template fails to find the part Product: kapptemplate Version: 0.1.21083 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: an...@kde.org Reporter: adrien.cordonn...@gmail.com CC: an...@kde.org Depends on: 396677 Target Milestone: --- +++ This bug was initially created as a clone of Bug #396677 +++ SUMMARY When creating a foo application based on the KPart template, the application cannot find the KPart. It looks that Bug #396677 happened again. STEPS TO REPRODUCE 1. Open KAppTemplate 2. Create a new project called foo, using the KPart template 3. Use the instructions in the README file: create the build folder, configure, compile and install the project 4. Run the project. OBSERVED RESULT There is an error window, saying "Could not find foo part!". The window then starts but is empty. EXPECTED RESULT The window loads the KPart content. SOFTWARE/OS VERSIONS Linux: 5.11.0-40-generic KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I am using latest package from KDE Neon Developer Edition. Package: kapptemplate Version: 4:21.08.3+p20.04+tunstable+git20211109.0123-0 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=396677 [Bug 396677] KParts template fails to find the part -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 176113] multiple keyboard layouts: provide shared key-permanent shortcuts
https://bugs.kde.org/show_bug.cgi?id=176113 Adrien Cordonnier changed: What|Removed |Added CC||adrien.cordonn...@gmail.com --- Comment #13 from Adrien Cordonnier --- Unfortunately, this bug still exists. I faced the bug on KDE Neon Developer Edition, unstable branches (Plasma 5.14.80, KF5 5.54.0, Qt 5.11.2). In my case, there was no shortcuts working to go back to the default zoom after accidentally pressing 'Ctrl +'. The assigned shortcuts to zoom out (Ctrl -) and to revert to the default zoom (Ctrl 0) do not work on my French keyboard (I fixed it by setting 'InitialZoom=1' in ~/.config/kwinrc and then pressing 'Shift Alt F12' twice' - it took me quite a while to find the solution). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 399511] New: Kdevelop crashed when closing
https://bugs.kde.org/show_bug.cgi?id=399511 Bug ID: 399511 Summary: Kdevelop crashed when closing Product: kdevelop Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: adrien.cordonn...@gmail.com Target Milestone: --- Application: kdevelop (5.3.40) Qt Version: 5.11.1 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: I closed the application using the title bar close button in the top right corner. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57abefddc0 (LWP 24560))] Thread 16 (Thread 0x7f5725ffb700 (LWP 25036)): #0 0x7f57a13509f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557515ab73b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f57a13509f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x557515ab7360, cond=0x557515ab7388) at pthread_cond_wait.c:502 #2 0x7f57a13509f3 in __pthread_cond_wait (cond=0x557515ab7388, mutex=0x557515ab7360) at pthread_cond_wait.c:655 #3 0x7f57a8c5591b in QWaitConditionPrivate::wait(unsigned long) (time=18446744073709551615, this=0x557515ab7360) at thread/qwaitcondition_unix.cpp:143 #4 0x7f57a8c5591b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x557515ac1380, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7f579ef4cd5b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f579ef51f40 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f579ef4cc8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f579ef51b92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f579ef4cc8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f579ef51b92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f579ef4cc8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f579ef51b92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7f579ef4cc8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7f579ef51b92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7f579ef4cc8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7f579ef4f9fb in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x7f57a8c54aab in QThreadPrivate::start(void*) (arg=0x557516ca2d20) at thread/qthread_unix.cpp:367 #18 0x7f57a134a6db in start_thread (arg=0x7f5725ffb700) at pthread_create.c:463 #19 0x7f57a854c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f5726ffd700 (LWP 25034)): #0 0x7f57a13509f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557515ab73b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f57a13509f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x557515ab7360, cond=0x557515ab7388) at pthread_cond_wait.c:502 #2 0x7f57a13509f3 in __pthread_cond_wait (cond=0x557515ab7388, mutex=0x557515ab7360) at pthread_cond_wait.c:655 #3 0x7f57a8c5591b in QWaitConditionPrivate::wait(unsigned long) (time=18446744073709551615, this=0x557515ab7360) at thread/qwaitcondition_unix.cpp:143 #4 0x7f57a8c5591b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x557515ac1380, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7f579ef4cd5b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f579ef51f40 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f579ef4cc8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f579ef51b92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f579ef4cc8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f579ef51b92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11
[neon] [Bug 399137] New: No icons in system tray for distro-release-notifier
https://bugs.kde.org/show_bug.cgi?id=399137 Bug ID: 399137 Summary: No icons in system tray for distro-release-notifier Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Dev Edition [unstable] Assignee: neon-b...@kde.org Reporter: adrien.cordonn...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Step to reproduce: 1. Log in, a new message inform about upgrading to 18.04. There is a yellow upgrade icon in the system tray 2. Fill the root file system so that there is just a few hundred of MB: $ df -h /dev/sda217G9.6G6.0G62% / $ fallocate -l 5800M temp_fill $ df -h /dev/sda217G 16G303M99% / 3. Click on the yellow upgrade icon in the system tray. Click "upgrade" on the upgrade window. The upgrade icon disappears from the system tray. The upgrade will fail because of lack of space. 4. Free some space on the root file system: rm temp_fill 5. Notice that there is no more yellow upgrade icon in the system tray. In the notification and status section of the system tray, upgrade section show that the system is up-to-date. Hence there is no easy way to find how to upgrade at that point. `ps aux | grep distro|` shows that distro-release-notifier is still running in the background. I did not find how to access it though. It is possible to run `sudo distro-release-notifier` but it warns about a missing icon (see below). An "invisible" icon is added to the system tray, when clicking on it, it is possible to start the upgrade again. $ distro-release-notifier org.kde.distro-release-notifier: Failed to register org.kde.DistroReleaseNotifier $ sudo distro-release-notifier QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QSystemTrayIcon::setVisitble: No Icon set Expected result: The yellow upgrade icon should automatically return to the system tray after the upgrade fails. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.80 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1 distro-release-notifier Version: 0.0+p16.04+git20180924.1417-0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 399136] No icon in system tray for distro-release-notifier
https://bugs.kde.org/show_bug.cgi?id=399136 --- Comment #1 from Adrien Cordonnier --- *** Bug 399137 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 399137] No icons in system tray for distro-release-notifier
https://bugs.kde.org/show_bug.cgi?id=399137 Adrien Cordonnier changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Adrien Cordonnier --- *** This bug has been marked as a duplicate of bug 399136 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 399136] New: No icon in system tray for distro-release-notifier
https://bugs.kde.org/show_bug.cgi?id=399136 Bug ID: 399136 Summary: No icon in system tray for distro-release-notifier Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Dev Edition [unstable] Assignee: neon-b...@kde.org Reporter: adrien.cordonn...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Step to reproduce: 1. Log in, a new message inform about upgrading to 18.04. There is a yellow upgrade icon in the system tray 2. Fill the root file system so that there is just a few hundred of MB: $ df -h /dev/sda217G9.6G6.0G62% / $ fallocate -l 5800M temp_fill $ df -h /dev/sda217G 16G303M99% / 3. Click on the yellow upgrade icon in the system tray. Click "upgrade" on the upgrade window. The upgrade icon disappears from the system tray. The upgrade will fail because of lack of space. 4. Free some space on the root file system: rm temp_fill 5. Notice that there is no more yellow upgrade icon in the system tray. In the notification and status section of the system tray, upgrade section show that the system is up-to-date. Hence there is no easy way to find how to upgrade at that point. `ps aux | grep distro|` shows that distro-release-notifier is still running in the background. I did not find how to access it though. It is possible to run `sudo distro-release-notifier` but it warns about a missing icon (see below). An "invisible" icon is added to the system tray, when clicking on it, it is possible to start the upgrade again. $ distro-release-notifier org.kde.distro-release-notifier: Failed to register org.kde.DistroReleaseNotifier $ sudo distro-release-notifier QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' QSystemTrayIcon::setVisitble: No Icon set Expected result: The yellow upgrade icon should automatically return to the system tray after the upgrade fails. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.80 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1 distro-release-notifier Version: 0.0+p16.04+git20180924.1417-0 -- You are receiving this mail because: You are watching all bug changes.
[kapptemplate] [Bug 396677] KParts template fails to find the part
https://bugs.kde.org/show_bug.cgi?id=396677 Adrien Cordonnier changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Adrien Cordonnier --- It seems fixed after updating packages today. When installing in /usr, the kpart is now installed in /usr/lib/x86_64-linux-gnu/qt5/plugins/ instead of /usr/lib/x86_64-linux-gnu/plugins/. Cmake also displays "-- Installing in the same prefix as Qt, adopting their path scheme." -- You are receiving this mail because: You are watching all bug changes.
[kapptemplate] [Bug 396677] New: KParts template fails to find the part
https://bugs.kde.org/show_bug.cgi?id=396677 Bug ID: 396677 Summary: KParts template fails to find the part Product: kapptemplate Version: 0.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: an...@kde.org Reporter: adrien.cordonn...@gmail.com Target Milestone: --- I used the KParts template to create a foo application and the corresponding foopart. I built the application using the instructions in the KParts template README. I tried different installation paths (e.g. /usr/, /usr/local, /opt/kde) but every time, the application fails to load the kpart with the error message "Could not find foo part!". For example, when installing in /usr, the following files are copied: -- Installing: /usr/lib/x86_64-linux-gnu/plugins/foopart.so -- Installing: /usr/share/kservices5/foopart.desktop -- Installing: /usr/share/kxmlgui5/foopart/foopartui.rc -- Installing: /usr/bin/foo -- Installing: /usr/share/applications/foo.desktop -- Installing: /usr/share/kxmlgui5/foo/fooui.rc -- Installing: /usr/share/icons/hicolor/16x16/apps/foo.png -- Installing: /usr/share/icons/hicolor/32x32/apps/foo.png -- Installing: /usr/share/icons/hicolor/48x48/apps/foo.png I am using latest package from KDE Neon Developer Edition. Package: kapptemplate Version: 4:18.04.3+p16.04+git20180719.0510-0 -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 396613] New: DragonPlayer crashes at startup when opening MP4 from Dolphin
https://bugs.kde.org/show_bug.cgi?id=396613 Bug ID: 396613 Summary: DragonPlayer crashes at startup when opening MP4 from Dolphin Product: dragonplayer Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: adrien.cordonn...@gmail.com CC: myr...@kde.org Target Milestone: --- Application: dragon (18.11.70) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.13.0-45-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: I opened a MP4 video from a SD card by clicking it in Dolphin. It can be reproduced but it does not crash every time. The crash can be reproduced sometimes. -- Backtrace: Application: Dragon Player (dragon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5a71a7b900 (LWP 14210))] Thread 3 (Thread 0x7f5a34b52700 (LWP 14217)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5a39fc570b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #2 0x7f5a39fc5427 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #3 0x7f5a6a2b96ba in start_thread (arg=0x7f5a34b52700) at pthread_create.c:333 #4 0x7f5a6cda441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f5a55cc0700 (LWP 14212)): #0 0x7f5a6cd9874d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5a67de238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5a67de249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5a6d9b90bb in QEventDispatcherGlib::processEvents (this=0x7f5a58c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5a6d9605ba in QEventLoop::exec (this=this@entry=0x7f5a55cbfc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f5a6d7955e4 in QThread::exec (this=this@entry=0x7f5a6e079d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:525 #6 0x7f5a6de00f35 in QDBusConnectionManager::run (this=0x7f5a6e079d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f5a6d7a0727 in QThreadPrivate::start (arg=0x7f5a6e079d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #8 0x7f5a6a2b96ba in start_thread (arg=0x7f5a55cc0700) at pthread_create.c:333 #9 0x7f5a6cda441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f5a71a7b900 (LWP 14210)): [KCrash Handler] #6 QWidgetPrivate::windowHandle (this=) at ../../include/QtWidgets/5.11.1/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:1010 #7 QWidget::windowHandle (this=0xd47990) at kernel/qwidget.cpp:2627 #8 0x7f5a70f49880 in KJobWidgets::setWindow (job=0xfc9e30, widget=0xd47990) at /workspace/build/src/kjobwidgets.cpp:30 #9 0x0043032b in Dragon::MainWindow::load (this=0xd47990, url=...) at /workspace/build/src/app/mainWindow.cpp:568 #10 0x00435eb4 in Dragon::MainWindow::open (this=0xd47990, url=...) at /workspace/build/src/app/mainWindow.cpp:524 #11 0x0042d555 in Dragon::PlayerApplication::newInstance (this=0x7fff136d23f0, playDisc=, uris=...) at /workspace/build/src/app/playerApplication.cpp:81 #12 0x0042ddeb in Dragon::PlayerApplication::slotActivateRequested (this=0x7fff136d23f0, arguments=..., workingDirectory=...) at /workspace/build/src/app/playerApplication.cpp:54 #13 0x7f5a6d98f2a6 in QtPrivate::QSlotObjectBase::call (a=0x7fff136d1960, r=0x7fff136d23f0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 #14 QMetaObject::activate (sender=0x7fff136d2410, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3754 #15 0x7f5a704a5ee7 in KDBusService::activateRequested(QStringList const&, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5 #16 0x7f5a704a02b4 in KDBusService::CommandLine(QStringList const&, QString const&, QMap const&) () from /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5 #17 0x7f5a704a5d4d in ?? () from /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5 #18 0x7f5a704a5e67 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5DBusAddons.so.5 #19 0x7f5a6de0c434 in QDBusConnectionPrivate::deliverCall (this=this@entry=0x7f5a500030f0, object=object@entry=0xd34ac0, msg=..., metaTypes=..., slotIdx=) at qdbusintegrator.cpp:991 #20 0x7f5a6de10d9a in QDBusConnectionPrivate::activateCall (this=this@entry=0x7f5a500030f0, object=0xd34ac0,
[Skanlite] [Bug 299517] Skanlite should support scan to pdf.
https://bugs.kde.org/show_bug.cgi?id=299517 --- Comment #21 from Adrien Cordonnier <adrien.cordonn...@gmail.com> --- If any one is interested, Skanpage fulfils exactly what is requested in this bug report. It works great. Despite Kåre's comment, I even think that it has the best UI among Skanlite, Kooka and Skanpage. I was able to compile Skanpage on Debian 9 (stretch, current stable) after installing qtdeclarative5-dev and qt4-dev-tools (gcc and other lib being already installed). git clone https://cgit.kde.org/scratch/sars/skanpage.git/ cd skanpage/src cmake -DCMAKE_INSTALL_PREFIX=/opt/kde -DCMAKE_BUILD_TYPE=Debug . make sudo make install It runs with: /opt/kde/bin/skanpage The only missing feature in Skanpage is the ability to save in png or jpeg (or other image file formats) as you can only save as PDF. There are a few quirks: * quality profile only changes resolution (not color mode), * "Best Quality"-profile is 600 dpi even if the scanner can do better, * changes to quality profiles are not saved for the next page, * saving does not use the default "Save as" dialog, * saving dialog asks for page settings (page size and print resolution) instead of reusing the scan settings for each page. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 299517] Skanlite should support scan to pdf.
https://bugs.kde.org/show_bug.cgi?id=299517 --- Comment #19 from Adrien Cordonnier <adrien.cordonn...@gmail.com> --- Kåre, is your code available online? -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 299517] Skanlite should support scan to pdf.
https://bugs.kde.org/show_bug.cgi?id=299517 Adrien Cordonnier <adrien.cordonn...@gmail.com> changed: What|Removed |Added CC||adrien.cordonn...@gmail.com --- Comment #16 from Adrien Cordonnier <adrien.cordonn...@gmail.com> --- Interestingly, Skanlite development page [1] lists open bug with max 40 votes (=2 voters) but not this bug report with 292 votes from 18 voters. As strange as it can be, changing its status to UNCONFIRMED would actually makes it more visible. Skanlite git repo does not have a branch with Kåre Särs' changes to implement multipage scans in December 2015 [2]. Hopefully, we will be able to find it back. Once Skanlite has multi-image support, they can be saved as a multi-page PDF with QtPdfWriter [3]. [1] https://www.kde.org/applications/graphics/skanlite/development [2] https://bugs.kde.org/show_bug.cgi?id=299517#c8 [3] http://doc.qt.io/qt-5/qpdfwriter.html#details -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 392485] New: Numeric keypad as a remote input
https://bugs.kde.org/show_bug.cgi?id=392485 Bug ID: 392485 Summary: Numeric keypad as a remote input Product: kdeconnect Version: 1.8 Platform: Android OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: adrien.cordonn...@gmail.com Target Milestone: --- I would like to have a numeric keypad as a remote input. Most laptops do not have a numeric keypad. Numbers are not directly available either on the French keyboard as they require holding Shift. This make it very inconvenient to insert a lot of numbers in a spreadsheet. It is currently possible to have a soft keyboard on the remote input activity. However keys are quite small as there are many other key than numbers. I suggest to add a keypad icon (3x3 dots + 1 bottom middle dot) which trigger the soft numeric keypad. The native numeric keypad is automatically displayed for example when filling html5 form fields with a modern browser (https://www.w3schools.com/html/tryit.asp?filename=tryhtml_input_number). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372158] Allow changing metadata of multiple images at once
https://bugs.kde.org/show_bug.cgi?id=372158 Adrien Cordonnier <adrien.cordonn...@gmail.com> changed: What|Removed |Added CC||adrien.cordonn...@gmail.com --- Comment #2 from Adrien Cordonnier <adrien.cordonn...@gmail.com> --- I confirm this bug with digikam 5.3 (Debian stable). My workflow was: 1. Search tab / Advanced search / search for a specific camera model 2. Select all (Ctrl+A) 3. menu Item / Modify metadata 4. check Name and Author checkboxes and type the camera owner's name twice 5. click Next Steps 4 and 5 need to be repeated for each photo, i.e. several thousands of times in my case. The added info is displayed in the Metadata right tab when a single photo is selected. Yet no information is displayed when several photos are selected, even the information shared by all the selected photos. The information cannot be modified there (neither single nor multiple photo selection). The expected behaviour is: 1. Select several items 2. menu Item / Modify metadata 3. click checkboxes of fields to be modified with tri-state checkboxes (https://en.wikipedia.org/wiki/Checkbox#Tri-state_checkbox) 4. click Apply to all Same behaviour would also be expected from the Metadata right tab. Note: such metadata editor exists in Amarok. The dialog shows Previous / Next / By track checkbox / Save and close / Cancel. Previous and Next buttons are greyed when By track checkbox is not checked. -- You are receiving this mail because: You are watching all bug changes.
