[Books] [Bug 373445] New: builds invalid epub
https://bugs.kde.org/show_bug.cgi?id=373445 Bug ID: 373445 Summary: builds invalid epub Product: Books Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Frameworks Cookbook Assignee: kde-doc-engl...@kde.org Reporter: w...@ubuntu.com Target Milestone: --- Created attachment 102694 --> https://bugs.kde.org/attachment.cgi?id=102694=edit flightcrew-cli errors The linked ePUB on books.k.o is invalid: https://books.kde.org/frameworks5/KDE-Frameworks-Cookbook.epub Using the current git: https://cgit.kde.org/kf5book.git/commit/?id=ff4008b17f889c8e381d2ea0cb208c021572d097 I attempted a rebuild but it was still invalid. See attached output of flightcrew-cli. -- You are receiving this mail because: You are watching all bug changes.
[Books] [Bug 373446] New: build instructions are incomplete
https://bugs.kde.org/show_bug.cgi?id=373446 Bug ID: 373446 Summary: build instructions are incomplete Product: Books Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Frameworks Cookbook Assignee: kde-doc-engl...@kde.org Reporter: w...@ubuntu.com Target Milestone: --- Created attachment 102695 --> https://bugs.kde.org/attachment.cgi?id=102695=edit incomplete build instructions I have not been able to use this to build a PDF because the build instructions are not complete. I have managed to figure out a lot and have created the attached additions, which I would have just added to the repo, but they're incomplete as you can see by the TODO. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 373221] Music being played even after a level is completed or the activity is closed
https://bugs.kde.org/show_bug.cgi?id=373221 --- Comment #2 from Walter Lapchynski <w...@ubuntu.com> --- > Version : 0.61 based on Qt 5.6.1 It also might be interesting to see if you have the same experience when using the latest version: https://mail.kde.org/pipermail/gcompris-devel/2016-December/004981.html -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 373221] Music being played even after a level is completed or the activity is closed
https://bugs.kde.org/show_bug.cgi?id=373221 Walter Lapchynski <w...@ubuntu.com> changed: What|Removed |Added CC||w...@ubuntu.com --- Comment #1 from Walter Lapchynski <w...@ubuntu.com> --- Thanks for your report! > OS : Microsoft windows Which Windows version? Also, what are the general specs of your computer? > When the level or the activity is quickly changed/closed, the audio still > continues. Does the audio stop playing at some point? -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 373221] Music being played even after a level is completed or the activity is closed
https://bugs.kde.org/show_bug.cgi?id=373221 --- Comment #4 from Walter Lapchynski <w...@ubuntu.com> --- (In reply to Karmanya from comment #3) > I used window vista and a low end pc(intel core 2 duo, 2GB ram)and also a > mid budget laptop with windows 7 home premium. Is it possible that it may have to do with exhausting available resources? > The audio stops after it is completed. You mean the audio continues until the audio track has reached its end, correct? -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 373221] Music being played even after a level is completed or the activity is closed
https://bugs.kde.org/show_bug.cgi?id=373221 --- Comment #6 from Walter Lapchynski <w...@ubuntu.com> --- (In reply to Karmanya from comment #5) > Yeah it could be that the program or that activity was exhausting available > resources. If you could check to see whether or not that is the case, it would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399863] New: segfault when repeatedly sorting
https://bugs.kde.org/show_bug.cgi?id=399863 Bug ID: 399863 Summary: segfault when repeatedly sorting Product: trojita Version: git Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Core Assignee: trojita-b...@kde.org Reporter: w...@ubuntu.com Target Milestone: --- STEPS TO REPRODUCE 1. Click on a folder 2. Click a column header to sort by that column 3. Repeat #2 several times (can be a different header) EXPECTED RESULTS Every click on the column header should result in sorting, with multiple clicks on the same header alternating between ascending and descending. ACTUAL RESULTS Assuming there are more than a couple messages and the column header is clicked more than a couple times, the application quits. AFFECTED VERSIONS trojita 0.7-0ubuntu2 (also upstream git master 76151f1a9226b27da9039d8701dc91a9f5e7c056) NOTES Using the menu to change the sorting does not produce the same result, but it may be that it's impossible to change the sorting as quickly. DOWNSTREAM BUG https://bugs.launchpad.net/ubuntu/+source/trojita/+bug/1797665 EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 401090] New: feature request: create application links from drag and drop
https://bugs.kde.org/show_bug.cgi?id=401090 Bug ID: 401090 Summary: feature request: create application links from drag and drop Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: w...@ubuntu.com CC: kdelibs-b...@kde.org Target Milestone: --- Currently, if one drags and drops an executable, one can copy/move it or make a symlink, but they cannot make an application link (read: Freedesktop Desktop Entry). The only option for doing this, is to right click on the desktop to open the context menu and make a new application link and fill in the blanks. Unfortunately, if one doesn't know all the details, it's not that easy. Solution: make the dropJob smart enough to recognize an executable, and if it is one, offer to create an application link. Upon select this, the application link editor opens up. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398222] New: 100% CPU usage when trying to open a mailto link
https://bugs.kde.org/show_bug.cgi?id=398222 Bug ID: 398222 Summary: 100% CPU usage when trying to open a mailto link Product: Falkon Version: unspecified Platform: Ubuntu Packages URL: https://bugs.launchpad.net/ubuntu/+source/falkon/+bug/ 1788542 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: w...@ubuntu.com Target Milestone: --- To see the problem, simply run `falkon mailto:w...@ubuntu.com`. It will, along with other QtWebEngine browsers, lead to a blank chrome-error://chromewebdata/ page. Qutebrowser doesn't load any further. With Falkon, it seems to keep trying to access that page for whatever reason and that's likely leading to the 100% usage. Note that neither browser will load a mail client. That said, it's probably a combination of QtWebEngine not properly dealing with mailtos and Falkon not properly dealing with the chrome-error page. This is Falkon 3.0.1-0ubuntu1 on Lubuntu 18.10, FWIW. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398222] 100% CPU usage when trying to open a mailto link
https://bugs.kde.org/show_bug.cgi?id=398222 --- Comment #3 from Walter Lapchynski --- I can confirm with e0d1175dd107 that if I have an email client installed, it Just Works™, but if there's no email client installed, it produces the same results. And indeed xdg-open wants to open falkon for mailtos, so I guess that explains things. The question is now: which commit fixed the problem? Is this unknown? Or maybe approaching this from a different direction: when's the next release? I'd really love to see this fixed before 18.10 is released. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398222] 100% CPU usage when trying to open a mailto link
https://bugs.kde.org/show_bug.cgi?id=398222 --- Comment #2 from Walter Lapchynski --- While that makes sense, I think it's kind of missing the mark. Here's the results of various actions: * `xdg-open mailto:w...@ubuntu.com` → opens email client with normal CPU usage * `firefox mailto:w...@ubuntu.com` → opens firefox, then email client with normal CPU usage * `qutebrowser mailto:w...@ubuntu.com` → opens qutebrowser with normal CPU usage * `falkon mailto:w...@ubuntu.com` → opens falkon with 100% CPU usage And interestingly, mailto is not the only URI scheme that's problematic. * `xdg-open tel:towel.blinkenlights.nl` → opens falkon with 100% CPU usage * `firefox tel:towel.blinkenlights.nl` → opens firefox with a search for tel:towel.blinkenlights.nl with normal CPU usage * `qutebrowser tel:towel.blinkenlights.nl` → opens qutebrowser with normal CPU usage * `falkon tel:towel.blinkenlights.nl` → opens falkon with 100% CPU usage >From this my guess is that there are two issues: 1. Some bug in QtWebEngine that doesn't properly handle some URI schemes. 2. Falkon lacks something that qutebrowser has where if it can't handle some URI scheme, it gets stuck in a loop that qutebrowser avoids. That said, what version can you not reproduce it in? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 398222] 100% CPU usage when trying to open a mailto link
https://bugs.kde.org/show_bug.cgi?id=398222 --- Comment #5 from Walter Lapchynski --- Created attachment 114979 --> https://bugs.kde.org/attachment.cgi?id=114979=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399863] segfault when repeatedly sorting
https://bugs.kde.org/show_bug.cgi?id=399863 --- Comment #6 from Walter Lapchynski --- Discovered a new quirk today: the smaller the window size, the more likely the problem is to occur. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399863] segfault when repeatedly sorting
https://bugs.kde.org/show_bug.cgi?id=399863 --- Comment #2 from Walter Lapchynski --- One piece of information I failed to include: it seems to require at least 10 messages. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399863] segfault when repeatedly sorting
https://bugs.kde.org/show_bug.cgi?id=399863 --- Comment #4 from Walter Lapchynski --- Oh and I'm not super familiar with ASan but if I grok the docs correctly, a simple -fsanitize=address to cmake should make things work and I didn't really notice anything different. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399863] segfault when repeatedly sorting
https://bugs.kde.org/show_bug.cgi?id=399863 --- Comment #3 from Walter Lapchynski --- After some further testing that involved increasing the memory allocation on the VMs I was using, I found that there seems to be some relationship between the amount of messages required to trigger it and the amount of memory. It's probably based more on size of messages (or mailbox/folder) rather than individual numbers of messages from what I can tell. Anyways, similar backtrace with b94f4307. Thread 1 "trojita" received signal SIGSEGV, Segmentation fault. 0x73eeda82 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 (gdb) backs[Ktrace full #0 0x73eeda82 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x73eee056 in QSortFilterProxyModel::flags(QModelIndex const&) const () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74b3fc71 in QTreeView::isExpanded(QModelIndex const&) const () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #3 0x74b4ace5 in QTreeView::verticalScrollbarValueChanged(int) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x74ad9d5f in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x73f3f5c6 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x749778ae in QAbstractSlider::valueChanged(int) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x74977f14 in QAbstractSlider::setValue(int) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x73f3f703 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x74887f62 in QAction::toggled(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7488a3b0 in QAction::setChecked(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7488b79a in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7488bc81 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x73f3f5c6 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x74889a2e in QActionPrivate::sendDataChanged() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7488a397 in QAction::setChecked(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x73f3f703 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x5578451c in Imap::Mailbox::PrettyMsgListModel::sortingPreferenceChanged(int, Qt::SortOrder) (this=this@entry=0x55c80630, _t1=, _t1@entry=2, _t2=, _t2@entry=Qt::AscendingOrder) at /home/lubuntu/trojita/_build/Imap_autogen/I7YDGANZM2/moc_PrettyMsgListModel.cpp:131 _a = {0x0, 0x7fffca2c, 0x7fffca28} #18 0x55735ff3 in Imap::Mailbox::PrettyMsgListModel::sort(int, Qt::SortOrder) (this=0x55c80630, column=2, order=Qt::AscendingOrder) at /home/lubuntu/trojita/src/Imap/Model/PrettyMsgListModel.cpp:244 threadingModel = criterium = Imap::Mailbox::ThreadingMsgListModel::SORT_FROM willSort = true #19 0x73f3f5c6 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x74ae536f in QHeaderView::sortIndicatorChanged(int, Qt::SortOrder) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x74aee975 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x74aeebfa in QHeaderView::mouseReleaseEvent(QMouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x748cc748 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7496ff4e in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x74ae149b in QAbstractItemView::viewportEvent(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x74af038b in QHeaderView::viewportEvent(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x73f1618b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7488e481 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x74895d08 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x73f16479 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x74895019 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x748e7264 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x748e9dee in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7488e491 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x74895ac0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/
[ark] [Bug 408233] New: ark cannot drag and drop to pcmanfm-qt
https://bugs.kde.org/show_bug.cgi?id=408233 Bug ID: 408233 Summary: ark cannot drag and drop to pcmanfm-qt Product: ark Version: 19.04.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: w...@ubuntu.com CC: rthoms...@gmail.com Target Milestone: --- SUMMARY In LXQt's file manager, pcmanfm-qt, which can also optionally manage the desktop, it is not possible to drag and drop a file from ark to any pcmanfm-qt window, a folder therein, or the desktop. STEPS TO REPRODUCE 1. Open an archive in ark 2. Open a pcmanfm-qt window 3. Drag and drop file from the archive to the pcmanfm-qt window 4. Ensure pcmanfm-qt is in control of the desktop (has to be run with `pcmanfm-qt --desktop` 5. Drag and drop file from the archive to the desktop OBSERVED RESULT Dragging and dropping fails. A general prohibition sign badge appears over the dragged icon when mousing over the areas managed by pcmanfm-qt. EXPECTED RESULT Dragging and dropping succeeds as it does with other archivers such as: * engrampa * file-roller * xarchiver SOFTWARE/OS VERSIONS Linux: Lubuntu 19.10 (development) KDE Frameworks Version: 5.58.0 Qt Version: 5.12.2 LXQt Version: 0.14.1 pcmanfm-qt Version: 0.14.1 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 393594] Drag file from compressed archive to other applications does not work
https://bugs.kde.org/show_bug.cgi?id=393594 Walter Lapchynski changed: What|Removed |Added CC||w...@ubuntu.com -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Walter Lapchynski changed: What|Removed |Added CC||w...@ubuntu.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 408233] ark cannot drag and drop to pcmanfm-qt
https://bugs.kde.org/show_bug.cgi?id=408233 --- Comment #3 from Walter Lapchynski --- LXQt has their own archiver (or rather, will; it hasn't hit v1 yet) and they have a generalized methodology to DND to anywhere using pure Qt methods: https://github.com/lxqt/lxqt-archiver/pull/93 Might be a nice alternative to forcing every single app that wants to interact with ark to have to write code specific to it. I mean if every file manager is expected to do that, it seems a little silly, especially if all the other archivers had the same expectation. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 408233] ark cannot drag and drop to pcmanfm-qt
https://bugs.kde.org/show_bug.cgi?id=408233 --- Comment #4 from Walter Lapchynski --- And as it turns out, file-roller and engrampa use Freedesktop's Direct Save Protocol (XDS) which seems about as standard as it comes: https://www.freedesktop.org/wiki/Specifications/XDS/ -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 408233] ark cannot drag and drop to pcmanfm-qt
https://bugs.kde.org/show_bug.cgi?id=408233 --- Comment #2 from Walter Lapchynski --- I submitted a new issue: https://github.com/lxqt/pcmanfm-qt/issues/977 but also asked if they have any suggestion on how to do this in a more standard way to share it upstream. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 415665] New: trojita needs function to print a message
https://bugs.kde.org/show_bug.cgi?id=415665 Bug ID: 415665 Summary: trojita needs function to print a message Product: trojita Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Other Assignee: trojita-b...@kde.org Reporter: w...@ubuntu.com Target Milestone: --- Trojita needs a function to print a message, as really just about every email client under the sun offers. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399530] Display which backends/sources are represented in the ApplicationDelegate
https://bugs.kde.org/show_bug.cgi?id=399530 Walter Lapchynski changed: What|Removed |Added CC||w...@ubuntu.com --- Comment #6 from Walter Lapchynski --- At least in 5.16.5, it seems there is a "Source" field, so it sounds to me like this has been implemented. Were we intending some other change I'm not understanding from this conversation? I will say the multiple entries confuse users that don't understand all the different packaging options. Discover is supposed to be "intuitive and simple" (https://userbase.kde.org/Discover#What_Discover_is), so it's not like grouping all the sources under one entry is at odds with the goals of the project. If all the sources are shown with separate install buttons next to them (and perhaps a "recommended" next to the distro package), that seems to also be consistent with the idea that Discover should "try to guide users through safe choices" (https://userbase.kde.org/Discover#What_Discover_isn.27t). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399530] Display which backends/sources are represented in the ApplicationDelegate
https://bugs.kde.org/show_bug.cgi?id=399530 --- Comment #8 from Walter Lapchynski --- If you mean the source would be shown on each item on the list, rather than solely within the individual metadata when you select an item, that sounds like a great upgrade. -- You are receiving this mail because: You are watching all bug changes.