[frameworks-kirigami] [Bug 383735] New: Fluttering of sliding section's content widget upon it's initial appearance in Kirigami Gallery
https://bugs.kde.org/show_bug.cgi?id=383735 Bug ID: 383735 Summary: Fluttering of sliding section's content widget upon it's initial appearance in Kirigami Gallery Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Created attachment 107388 --> https://bugs.kde.org/attachment.cgi?id=107388&action=edit fluttering-of-sliding-widget Steps to reproduce: 1. Start Kirigami Gallery and maximize its window. 2. Select any section on the left side. 3. Pay attention to the right side of the window and watch revealing animation of sliding content widget. Actual result: Section's content widget flutters upon sliding animation. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 381664] Plugin leads to the home page of Flickr and 'An error has occurred: Invalid Frob It can not be continued.'
https://bugs.kde.org/show_bug.cgi?id=381664 Robert Cabane changed: What|Removed |Added CC||rcab...@free.fr --- Comment #9 from Robert Cabane --- Just the same here. I use Flickr on a regular basis, thank you for your amazing work ! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 383681] Kscreenlocker 5.10.4 only crashes
https://bugs.kde.org/show_bug.cgi?id=383681 --- Comment #6 from Martin Flöser --- OK, so we need to figure out what is different in your distribution to all other distributions. Obvious things first: this works on other distributions. KScreenlocker saw some changes in Plasma 5.10, but no other distro reported issues with it. I sent detailed instructions to the kde distributions mailing list about the changes involved. Please verify that all (optional) build dependencies are installed. Please attach an output of the cmake run. Most importantly to verify: is the seccomp dependency found and does this work on your distribution? Are you using the default lock screen theme or a custom one? If a custom one: does the problem also happen with the default theme? If not please attach the custom theme. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 383734] New: Print job with media=Custom swaps width and height which results in shrinked printouts
https://bugs.kde.org/show_bug.cgi?id=383734 Bug ID: 383734 Summary: Print job with media=Custom swaps width and height which results in shrinked printouts Product: okular Version: 1.1.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: robert.falkenb...@tu-dortmund.de Target Milestone: --- Created attachment 107387 --> https://bugs.kde.org/attachment.cgi?id=107387&action=edit Resuling postscript from pstops due to incorrect parametrization When specifying custom media dimensions for a printout (on a physical printer), the command sent to CUPS includes the media dimensions. Unfortunately, the values are given in swapped order. According to CUPS manual https://www.cups.org/doc/options.html the correct order of the dimensions is lp -o media=Custom.WIDTHxLENGTHmm filename But the assignment is performed in reverse order, see file "fileprinter.cpp" line 539: case QPrinter::Custom: return QStringLiteral("Custom.%1x%2mm") .arg( printer.heightMM() ) .arg( printer.widthMM() ); Please swap heightMM() and widthMM(). In the current version (and for many years), printouts of A4 portraits (borderless) are being shrinked by pstops to the bottom-right corner of the portrait media. The resulting content height corresponds to the width of the media (due to swapped values). I have attached an example of the resulting shrinked postscript, which is then passed to the CUPS filter of my printer (Brother DCP585CW). Here is the relevant excerpt of /var/log/cups/erros.log in debug mode, including the incorrect dimensions in argv[5]: D [20/Aug/2017:07:42:54 +0200] [Job 477] 2 filters for job: D [20/Aug/2017:07:42:54 +0200] [Job 477] pstops (application/postscript to application/vnd.cups-postscript, cost 66) D [20/Aug/2017:07:42:54 +0200] [Job 477] brlpdwrapperdcp585cw (application/vnd.cups-postscript to printer/Brother_DCP-585CW, cost 0) D [20/Aug/2017:07:42:54 +0200] [Job 477] job-sheets=none,none D [20/Aug/2017:07:42:54 +0200] [Job 477] argv[0]="Brother_DCP-585CW" D [20/Aug/2017:07:42:54 +0200] [Job 477] argv[1]="477" D [20/Aug/2017:07:42:54 +0200] [Job 477] argv[2]="robert" D [20/Aug/2017:07:42:54 +0200] [Job 477] argv[3]="Example.pdf" D [20/Aug/2017:07:42:54 +0200] [Job 477] argv[4]="1" D [20/Aug/2017:07:42:54 +0200] [Job 477] argv[5]="Collate finishings=3 fit-to-page job-billing media=Custom.291x205mm number-up=1 number-up-layout=lrtb outputorder=reverse page-bottom=10 page-left=10 page-right=10 page-top=10 portrait sides=one-sided job-uuid=urn:uuid:7ae72161-74c7-3701-5164-eb4fab1e615f job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1503207774 time-at-processing=1503207774 document-name-supplied=okular_nS1822.ps" D [20/Aug/2017:07:42:54 +0200] [Job 477] argv[6]="/var/spool/cups/d00477-001" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[0]="CUPS_CACHEDIR=/var/cache/cups" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[1]="CUPS_DATADIR=/usr/share/cups" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[2]="CUPS_DOCROOT=/usr/share/cups/doc" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[3]="CUPS_FONTPATH=/usr/share/cups/fonts" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[4]="CUPS_REQUESTROOT=/var/spool/cups" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[5]="CUPS_SERVERBIN=/usr/lib/cups" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[6]="CUPS_SERVERROOT=/etc/cups" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[7]="CUPS_STATEDIR=/run/cups" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[8]="HOME=/var/spool/cups/tmp" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[9]="PATH=/usr/lib/cups/filter:/usr/bin:/usr/bin:/bin:/usr/bin" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[10]="SERVER_ADMIN=root@Blocko" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[11]="SOFTWARE=CUPS/2.2.4" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[12]="TMPDIR=/var/spool/cups/tmp" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[13]="USER=root" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[14]="CUPS_MAX_MESSAGE=2047" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[15]="CUPS_SERVER=/run/cups/cups.sock" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[16]="CUPS_ENCRYPTION=IfRequested" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[17]="IPP_PORT=631" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[18]="CHARSET=utf-8" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[19]="LANG=en.UTF-8" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[20]="PPD=/etc/cups/ppd/Brother_DCP-585CW.ppd" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[21]="RIP_MAX_CACHE=128m" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[22]="CONTENT_TYPE=application/postscript" D [20/Aug/2017:07:42:54 +0200] [Job 477] envp[23]="DEVIC
[frameworks-kirigami] [Bug 383733] New: Left 'Widgets gallery' and right 'Actions' widgets are incorrectly revealing upon dragging of main 'Action button' (pencil in a circle) in some sections in Kiri
https://bugs.kde.org/show_bug.cgi?id=383733 Bug ID: 383733 Summary: Left 'Widgets gallery' and right 'Actions' widgets are incorrectly revealing upon dragging of main 'Action button' (pencil in a circle) in some sections in Kirigami Gallery Product: frameworks-kirigami Version: Master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Created attachment 107386 --> https://bugs.kde.org/attachment.cgi?id=107386&action=edit left-and-right-sections-are-incorrectly-revealing 'Radio button', 'Progress Bar', 'List View' and 'Non Scrollable Page' sections have incorrect revealing of side widgets upon dragging of main 'Action button' in them. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 --- Comment #18 from Philippe ROUBACH --- kde app 17.08 also some time some contents has no date. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383730] Kirigami Gallery hangs upon changing of it's window width in 'Color' section
https://bugs.kde.org/show_bug.cgi?id=383730 Alexander Mentyu changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383731] 'Text Fields' section always use all horizontal space even if after width change - there is enough of horizontal space in Kirigami Gallery
https://bugs.kde.org/show_bug.cgi?id=383731 Alexander Mentyu changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383732] New: Part of bottom right 'Actions' menu is visible for a split of a second when increasing width of Kirigami Gallery window
https://bugs.kde.org/show_bug.cgi?id=383732 Bug ID: 383732 Summary: Part of bottom right 'Actions' menu is visible for a split of a second when increasing width of Kirigami Gallery window Product: frameworks-kirigami Version: Master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Created attachment 107385 --> https://bugs.kde.org/attachment.cgi?id=107385&action=edit part-of-actions-menu-is-visible When increasing increasing width of Kirigami Gallery window - pay attention to the bottom right corner of the window. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383731] New: 'Text Fields' section always use all horizontal space even if after width change - there is enough of horizontal space in Kirigami Gallery
https://bugs.kde.org/show_bug.cgi?id=383731 Bug ID: 383731 Summary: 'Text Fields' section always use all horizontal space even if after width change - there is enough of horizontal space in Kirigami Gallery Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Created attachment 107384 --> https://bugs.kde.org/attachment.cgi?id=107384&action=edit text-fields-takes-all-space The left sections ('Button', 'CheckBox', 'Radio Button'...) part of interface displays only for a split of second upon increasing of width of Kirigami Gallery window. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383730] Kirigami Gallery hangs upon changing of it's window width in 'Color' section
https://bugs.kde.org/show_bug.cgi?id=383730 --- Comment #1 from Alexander Mentyu --- Hanging in 'Color' section happens only when increasing width from the most narrow window size. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383730] New: Kirigami Gallery hangs upon changing of it's window width in 'Color' section
https://bugs.kde.org/show_bug.cgi?id=383730 Bug ID: 383730 Summary: Kirigami Gallery hangs upon changing of it's window width in 'Color' section Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Created attachment 107383 --> https://bugs.kde.org/attachment.cgi?id=107383&action=edit kirigami-gallery-hangs Steps to reproduce: 1. Launch Kirigami Gallery and choose 'Color' section. 2. Grab right border of Kirigami Gallery window and narrow down this window size. 3. Without releasing of mouse button - try to increase the window width. Actual result: Kirigami Gallery hangs. Hanging isn't happening in other sections. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 Pal Körössy changed: What|Removed |Added CC||p1037...@gmail.com --- Comment #17 from Pal Körössy --- Same here with Akregator 17.04.3 with OpenSUSE Tumbleweeed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383729] Vertical scrollbar is displaying too late in Kirigami Gallery
https://bugs.kde.org/show_bug.cgi?id=383729 --- Comment #1 from Alexander Mentyu --- Created attachment 107382 --> https://bugs.kde.org/attachment.cgi?id=107382&action=edit vertical scrollbar-is-displaying-too-late-2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383729] New: Vertical scrollbar is displaying too late in Kirigami Gallery
https://bugs.kde.org/show_bug.cgi?id=383729 Bug ID: 383729 Summary: Vertical scrollbar is displaying too late in Kirigami Gallery Product: frameworks-kirigami Version: Master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Created attachment 107381 --> https://bugs.kde.org/attachment.cgi?id=107381&action=edit vertical scrollbar-is-displaying-too-late There is no scrollbar when many of the section's content is already hidden after/upon vertical size change. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383728] Jittering of interface upon change of vertical size in Kirigami Gallery
https://bugs.kde.org/show_bug.cgi?id=383728 --- Comment #1 from Alexander Mentyu --- Created attachment 107380 --> https://bugs.kde.org/attachment.cgi?id=107380&action=edit jittering-of-interface-radio-section -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383728] New: Jittering of interface upon change of vertical size in Kirigami Gallery
https://bugs.kde.org/show_bug.cgi?id=383728 Bug ID: 383728 Summary: Jittering of interface upon change of vertical size in Kirigami Gallery Product: frameworks-kirigami Version: Master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Created attachment 107379 --> https://bugs.kde.org/attachment.cgi?id=107379&action=edit jittering-of-interface Steps to reproduce: 1. Launch Kirigami Gallery and try to change it's window height. Jittering also happens in any of gallery section. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370612] Artifacts when dragging maximized (wobbly) windows to different screen
https://bugs.kde.org/show_bug.cgi?id=370612 Sriram Kumar changed: What|Removed |Added CC||m.sriram1...@gmail.com --- Comment #9 from Sriram Kumar --- I can confirm that this bug also occurs when trying to snap a maximised window to one side of a screen. I can also confirm that the method @Antonio Orefice suggested (disabling maximise effect) works... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383727] Kirigami Gallery - 'Text fields' text is draggable in top navigation panel
https://bugs.kde.org/show_bug.cgi?id=383727 --- Comment #1 from Alexander Mentyu --- Created attachment 107378 --> https://bugs.kde.org/attachment.cgi?id=107378&action=edit text-fields-is-draggable -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383727] New: Kirigami Gallery - 'Text fields' text is draggable in top navigation panel
https://bugs.kde.org/show_bug.cgi?id=383727 Bug ID: 383727 Summary: Kirigami Gallery - 'Text fields' text is draggable in top navigation panel Product: frameworks-kirigami Version: Master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Steps to reproduce: 1. Launch Kirigami Gallery. 2. Increase Kirigami Gallery window width so it switched from mobile width mode or make it fullscreen. 3. Select Text Field section. 4. Grab and drag 'Text fields' text in top navigation panel. Actual result: 'Text fields' text is draggable. Expected result: 'Text fields' text isn't draggable same as others text items in top navigation panel. Also this bug prompted me to idea - what if all top navigation text in Kirigami Gallery could be draggable and used for back and forth navigation. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378897] missing cursor in timeline
https://bugs.kde.org/show_bug.cgi?id=378897 DeMus changed: What|Removed |Added CC||jan.muss...@gmail.com --- Comment #3 from DeMus --- Created attachment 107377 --> https://bugs.kde.org/attachment.cgi?id=107377&action=edit Start of timeline in Kdenlive I clicked the cursor on the timeline and between 10 and 20 seconds you see this small grey line, but below it is no cursor. In the preview screen the time does also not change to the point in time where I clicked. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383725] Not fully visible top list item after scrolling in Discover
https://bugs.kde.org/show_bug.cgi?id=383725 --- Comment #1 from Alexander Mentyu --- Created attachment 107376 --> https://bugs.kde.org/attachment.cgi?id=107376&action=edit not-fully-visible-top-list-item-2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 383725] New: Not fully visible top list item after scrolling in Discover
https://bugs.kde.org/show_bug.cgi?id=383725 Bug ID: 383725 Summary: Not fully visible top list item after scrolling in Discover Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: Not decided Created attachment 107375 --> https://bugs.kde.org/attachment.cgi?id=107375&action=edit not-fully-visible-top-list-item Sometimes top list item is not fully visible in a list after scrolling. This happens more often when there are a lot of items in a list and scrolling down (approximately to the middle) were made by mouse click on scrollbar and dragging it lower - and after that - scrolling up to the ALMOST very top were made by mouse click on scrollbar and dragging it upper - and than - scrolling to the very top were made by mouse wheel. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 383726] New: Konqueror crashed by launching it
https://bugs.kde.org/show_bug.cgi?id=383726 Bug ID: 383726 Summary: Konqueror crashed by launching it Product: konqueror Version: 5.0.97 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: gat...@grrlz.net Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.7.1 Frameworks Version: 5.37.0 Operating System: Linux 4.10.0-32-generic x86_64 Distribution: KDE neon LTS User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: I launched Konqueror from a launcher at a pannel, it popped up a window questioning me something (I don't remember what, sorry), I clicked on «no» option and then it crashed -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb91138d940 (LWP 12907))] Thread 3 (Thread 0x7fb906ae5700 (LWP 12909)): #0 0x7fb923cbe70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb918e9838c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fb93020, timeout=, context=0x7fb90990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7fb90990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7fb918e9849c in g_main_context_iteration (context=0x7fb90990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7fb91f30b75b in QEventDispatcherGlib::processEvents (this=0x7fb908c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fb91f2b60ba in QEventLoop::exec (this=this@entry=0x7fb906ae4c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7fb91f0e5f64 in QThread::exec (this=this@entry=0x7fb924498d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #7 0x7fb924424735 in QDBusConnectionManager::run (this=0x7fb924498d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7fb91f0eab48 in QThreadPrivate::start (arg=0x7fb924498d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x7fb91af886ba in start_thread (arg=0x7fb906ae5700) at pthread_create.c:333 #10 0x7fb923cca3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb90ee24700 (LWP 12908)): #0 0x7fb923cbe70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb91a906c62 in poll (__timeout=-1, __nfds=1, __fds=0x7fb90ee23b80) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x1fe0150, cond=cond@entry=0x1fe0190, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x7fb91a9088d7 in xcb_wait_for_event (c=0x1fe0150) at ../../src/xcb_in.c:693 #4 0x7fb910d54d79 in QXcbEventReader::run (this=0x1fea820) at qxcbconnection.cpp:1343 #5 0x7fb91f0eab48 in QThreadPrivate::start (arg=0x1fea820) at thread/qthread_unix.cpp:368 #6 0x7fb91af886ba in start_thread (arg=0x7fb90ee24700) at pthread_create.c:333 #7 0x7fb923cca3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb91138d940 (LWP 12907)): [KCrash Handler] #6 0x7fb923fe12d8 in QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer (this=, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qshareddata.h:165 #7 KonqRun::foundMimeType (this=0x256faa0, _type=...) at /workspace/build/src/konqrun.cpp:106 #8 0x7fb92290c362 in KRun::mimeTypeDetermined(QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #9 0x7fb922e9f668 in KParts::BrowserRun::slotBrowserMimetype(KIO::Job*, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5 #10 0x7fb91f2e31f6 in QtPrivate::QSlotObjectBase::call (a=0x7fff5c3d25f0, r=0x256faa0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #11 QMetaObject::activate (sender=sender@entry=0x25a4680, signalOffset=, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff5c3d25f0) at kernel/qobject.cpp:3723 #12 0x7fb91f2e3837 in QMetaObject::activate (sender=sender@entry=0x25a4680, m=m@entry=0x7fb922853980 , local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff5c3d25f0) at kernel/qobject.cpp:3602 #13 0x7fb9225ac1b7 in KIO::TransferJob::mimetype (this=this@entry=0x25a4680, _t1=_t1@entry=0x25a4680, _t2=...) at /workspace/build/obj-x86_64-linux-gnu/src/core/moc_transferjob.cpp:338 #14 0x7fb9225ac2df in KIO::TransferJob::slotMimetype (this=0x25a4680, type=...) at /workspace/build/src/
[frameworks-kirigami] [Bug 382191] update page gets freaky when scrolling past top
https://bugs.kde.org/show_bug.cgi?id=382191 --- Comment #9 from Alexander Mentyu --- It happens more often for me if scrolling with touchpad. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379131] Gmail authentication expires after some time
https://bugs.kde.org/show_bug.cgi?id=379131 labayla...@tuta.io changed: What|Removed |Added CC||labayla...@tuta.io --- Comment #4 from labayla...@tuta.io --- Can confirm that with single gmail account, but with various other google resource (calendar, addressbook), email always stop working/synching after this message: qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on non-plain connection org.kde.pim.kimap: Connection to server lost 0 org.kde.pim.imapresource: Session login cancelled Switching imap server to imap.googlemail.com solve the problem. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383434] Maximized window button behavior should also apply to tiled windows
https://bugs.kde.org/show_bug.cgi?id=383434 Nate Graham changed: What|Removed |Added Latest Commit||https://phabricator.kde.org ||/R31:629b0698535a7210a49ab2 ||825b44e156e1eae8a5 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Nate Graham --- Fixed in https://phabricator.kde.org/R31:629b0698535a7210a49ab2825b44e156e1eae8a5 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 383724] New: Modified Blender files don't get uploaded
https://bugs.kde.org/show_bug.cgi?id=383724 Bug ID: 383724 Summary: Modified Blender files don't get uploaded Product: kio-gdrive Version: 1.2.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: matthewtresc...@gmail.com Target Milestone: --- I opened a Blender (.blend) file from my gdrive:// in Dolphin, edited, and saved it. At no point was the modified version uploaded back to Drive, even after closing Blender. I was _very_ lucky I had backed up the cached file in ~/.cache/kioexec/krun/whatever. I imagine this is due to Blender creating backup files with the .blend1 extension in the same folder as the file currently open. I was at first going to label this as "critical" but since I found that it only affects Blender it's not _quite_ as horrible. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 382191] update page gets freaky when scrolling past top
https://bugs.kde.org/show_bug.cgi?id=382191 --- Comment #8 from Alexander Mentyu --- I still managed to reproduce flickering - but not upon updates. It's reproducing sometimes upon regular navigating for me. Three recorder videos attached. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 382191] update page gets freaky when scrolling past top
https://bugs.kde.org/show_bug.cgi?id=382191 --- Comment #7 from Alexander Mentyu --- Created attachment 107374 --> https://bugs.kde.org/attachment.cgi?id=107374&action=edit flickering-scroll-past-top-discover-3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 382191] update page gets freaky when scrolling past top
https://bugs.kde.org/show_bug.cgi?id=382191 --- Comment #5 from Alexander Mentyu --- Created attachment 107372 --> https://bugs.kde.org/attachment.cgi?id=107372&action=edit flickering-scroll-past-top-discover -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 382191] update page gets freaky when scrolling past top
https://bugs.kde.org/show_bug.cgi?id=382191 --- Comment #6 from Alexander Mentyu --- Created attachment 107373 --> https://bugs.kde.org/attachment.cgi?id=107373&action=edit flickering-scroll-past-top-discover-2 -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 340411] krfb does not save user settings
https://bugs.kde.org/show_bug.cgi?id=340411 Michael Earle changed: What|Removed |Added CC||ikit...@gmail.com --- Comment #12 from Michael Earle --- This is still a bug on: KDE Neon Latest Plasma Version: 5.10.4 KDE Frameworks Version: 5.37.0 Kernel Version 4.10.0-32-generic -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 383702] Gwenview crashed when drive got unmounted
https://bugs.kde.org/show_bug.cgi?id=383702 Christoph Feck changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383714] Dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=383714 Christoph Feck changed: What|Removed |Added Version|unspecified |16.12.3 Product|kde |dolphin CC||elvis.angelac...@kde.org Component|general |general Assignee|unassigned-b...@kde.org |dolphin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 378666] File chooser only allows files to be drag-and-dropped to the text field, not the main file view
https://bugs.kde.org/show_bug.cgi?id=378666 Nate Graham changed: What|Removed |Added Summary|No drag-and-drop support in |File chooser only allows |the file chooser|files to be ||drag-and-dropped to the ||text field, not the main ||file view -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 378666] No drag-and-drop support in the file chooser
https://bugs.kde.org/show_bug.cgi?id=378666 --- Comment #3 from Nate Graham --- Workaround: drag the file to the text box, not the file view, which pastes in the path and accomplishes the desired workflow. I still think dragging a file to the main file view should do the same, given that right now it does nothing and displays a "can't do that" cursor. Might as well have it do something useful and in the process match the behavior of the macOS and GTK file choosers. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] New: MacOS 10.12.x: UNKNOWN workq_ops option 128, and ud2 opcode
https://bugs.kde.org/show_bug.cgi?id=383723 Bug ID: 383723 Summary: MacOS 10.12.x: UNKNOWN workq_ops option 128, and ud2 opcode Product: valgrind Version: 3.14 SVN Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: imol00+...@gmail.com Target Milestone: --- I sent this to the mailing list. It was reviewed by John Reiser (thanks John!) and he asked that I file this report. Here are the details I supplied: Running callgrind on my Qt-based app on macOS 10.12.6 crashes. Running callgrind on "/bin/date" works (which is not surprising as I think workq_ops is related to threads?) - in Qt Creator, add a new project - select "Qt Console Application" - edit its qmake file to remove "CONFIG += console" (this shouldn't be added on the Mac) - build "Profile" version The .pro looks like this: QT += core QT -= gui CONFIG += c++11 TARGET = valgrind-test2 CONFIG -= app_bundle TEMPLATE = app SOURCES += main.cpp And main.cpp looks like this: #include int main(int argc, char *argv[]) { QCoreApplication a(argc, argv); return a.exec(); } Run valgrind --tool=callgrind Results: ==35785== Callgrind, a call-graph generating cache profiler ==35785== Copyright (C) 2002-2017, and GNU GPL'd, by Josef Weidendorfer et al. ==35785== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright info ==35785== Command: /Users/maloney/dev/build-valgrind-test2-Qt_5_x-Profile/valgrind-test2 ==35785== ==35785== For interactive control, run 'callgrind_control -h'. --35785-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option --35785-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2 times) --35785-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4 times) UNKNOWN workq_ops option 128 ==35785== valgrind: Unrecognised instruction at address 0x103b0fb50. ==35785==at 0x103B0FB50: _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B0D8FB: _dispatch_client_callout (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B0D8B8: dispatch_once_f (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B0FA90: _dispatch_kq_update (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B110CD: _dispatch_kevent_resume (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B1103D: _dispatch_source_kevent_resume (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B10E85: _dispatch_source_kevent_register (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B20651: _dispatch_queue_resume_finalize_activation (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103E603C0: _notify_lib_init (in /usr/lib/system/libsystem_notify.dylib) ==35785==by 0x103E609AB: notify_register_dispatch (in /usr/lib/system/libsystem_notify.dylib) ==35785==by 0x1027E8916: CFUniCharMapTo (in /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation) ==35785==by 0x103B0D8FB: _dispatch_client_callout (in /usr/lib/system/libdispatch.dylib) ==35785== Your program just tried to execute an instruction that Valgrind ==35785== did not recognise. There are two possible reasons for this. ==35785== 1. Your program has a bug and erroneously jumped to a non-code ==35785==location. If you are running Memcheck and you just saw a ==35785==warning about a bad jump, it's probably your program's fault. ==35785== 2. The instruction is legitimate but Valgrind doesn't handle it, ==35785==i.e. it's Valgrind's fault. If you think this is the case or ==35785==you are not sure, please let us know and we'll try to fix it. ==35785== Either way, Valgrind will now raise a SIGILL signal which will ==35785== probably kill your program. ==35785== ==35785== Process terminating with default action of signal 4 (SIGILL) ==35785== Illegal opcode at address 0x103B0FB50 ==35785==at 0x103B0FB50: _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B0D8FB: _dispatch_client_callout (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B0D8B8: dispatch_once_f (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B0FA90: _dispatch_kq_update (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B110CD: _dispatch_kevent_resume (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B1103D: _dispatch_source_kevent_resume (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B10E85: _dispatch_source_kevent_register (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103B20651: _dispatch_queue_resume_finalize_activation (in /usr/lib/system/libdispatch.dylib) ==35785==by 0x103E603C0: _notify_lib_init (in /usr/lib/system/libsystem_notify.dylib) ==35785==by 0x103E609AB: notify_register_dispatch (in /usr/lib/system/libsystem_notify.dylib) ==35785==by
[systemsettings] [Bug 358254] Setting the toolbar font does nothing
https://bugs.kde.org/show_bug.cgi?id=358254 --- Comment #5 from Allan Sandfeld --- Note my Qt change was in Qt's KDE platformplugin. If you have a full KDE/Plasma installation, the vanilla platform-integrations gets overriden by the Plasma's own platformplugin. So similar code might already be there in that plugin it the code might need to be duplicated. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354227] kcm_kscreen is too high
https://bugs.kde.org/show_bug.cgi?id=354227 Valeriy Malov changed: What|Removed |Added CC||jazzv...@gmail.com --- Comment #31 from Valeriy Malov --- So, if scrollbars can't be added to kscreen since systemsettings adds it's own set of scrollbars, what about adding scrollbars to KCMultiDialog same way it's done it systemsettings (via QScrollArea)? This theoretically should take care about systemsettings modules. kcm_kscreen specifically takes some time to initialize, which causes "kcmshell5 kscreen" to start in a very small window if scrollbars are added, but this seems like something that should be fixed in kcm_kscreen (perhaps through size hint?) However, KCMultiDialog is also used outside of systemsettings (e.g. kdepim), and those might have their own scrollbars? Also, bug 366299 and bug 360260 seem to be related/duplicates -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383717] Move tool won't update the image in real-time
https://bugs.kde.org/show_bug.cgi?id=383717 --- Comment #2 from Henrique --- I'm using the appimage on Linux Mint. Also, I'm not sure if it influences, but this happened with a .psd file. Then I imported an image to one layer, used filter (threshold) and tried to move said layer. But sometimes the bug doesn't come up, so I'm not entirely sure what triggers it. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 383722] New: Can't read calendar list --- too small
https://bugs.kde.org/show_bug.cgi?id=383722 Bug ID: 383722 Summary: Can't read calendar list --- too small Product: korganizer Version: unspecified Platform: Mint (Debian based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: 1840tra...@gmail.com Target Milestone: --- Created attachment 107371 --> https://bugs.kde.org/attachment.cgi?id=107371&action=edit Screenshot of the calendar (just launched for the first time)...can't read calendar selection area. Where you can select the calendars in the bottom left corner...the print is so small, can't be read. Can't even click on it without de-selecting or selecting a calendar. Have to arrow around and hit spacebar to even guess at which calendar is showing up and which isn't. I have three calendars I'm using, but even just starting the program up...the two default calendars (for the first time launch) are the same super small font and type. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383716] "Save Changes" button same as "Save As New Version" Button
https://bugs.kde.org/show_bug.cgi?id=383716 Simon changed: What|Removed |Added CC||freisi...@gmail.com --- Comment #1 from Simon --- That might not be the clearest of UI choices. I believe this is due to the how digikam is configured. In the editor configuration you can choose whether an edit should be done in place or as new version (didn't check this now though). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 383681] Kscreenlocker 5.10.4 only crashes
https://bugs.kde.org/show_bug.cgi?id=383681 --- Comment #5 from Jerrod Frost --- All we did is upgraded plasma 5.9.5 to 5.10.4 Intel is also affected. I'm part of the Sabayon Linux software testing team. We've located the issue. It's 100% with DRI3. Once we downgrade to DRI2. Everything works in both Intel and AMD graphics cards. DRI3 isn't compatible. This is bad as it disables vulkan for open source drivers. KDE+gaming is a no go at this point. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383721] New: New tab changing shortcuts conflict with Move to Top/Bottom of View commands in Kate
https://bugs.kde.org/show_bug.cgi?id=383721 Bug ID: 383721 Summary: New tab changing shortcuts conflict with Move to Top/Bottom of View commands in Kate Product: kate Version: Git Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: pointedst...@zoho.com Target Milestone: --- In https://phabricator.kde.org/R237:d85a57645f94d2d087711d7c608a0c5a46ed7ede, we changed the standard tab changing keyboard shortcuts to ctrl+pgup/pgdn. This creates a conflict in Kate, which currently uses ctrl+pgup for "Move to Top of View and ctrl+pgdn for "Move to Bottom of View". -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 369611] Dolphin cannot create links to files, only directories
https://bugs.kde.org/show_bug.cgi?id=369611 --- Comment #5 from Nate Graham --- Yes, that was my thought as well. However changing it to that approach involves a lot of work given the way this feature is currently implemented, and it also has translation implications (changing one already-translated string to two new ones). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381000] [Regression] High CPU when background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=381000 --- Comment #111 from David Edmundson --- @ Vova Mshanetskiy Only non threaded render loops are affected. Kwin's CPU is higher because plasmashell is redrawing windows like crazy. As to why Plasmashell is redrawing like crazy, I don't exactly know. See earlier comments from me. Logs won't help, someone being affected and debugging it will. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 383720] New: Konqueror crash after opening new tab
https://bugs.kde.org/show_bug.cgi?id=383720 Bug ID: 383720 Summary: Konqueror crash after opening new tab Product: konqueror Version: 5.0.97 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: opensuse.lietuviu.ka...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.79-19-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: I did Google searche, tryied to open one result in new tab. Seems result was a file. Crashed. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f793ebe1940 (LWP 12529))] Thread 9 (Thread 0x7f78c8ca1700 (LWP 12873)): #0 0x7f793400e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f790f1e77c3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f790f509421 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f7934009744 in start_thread (arg=0x7f78c8ca1700) at pthread_create.c:334 #4 0x7f793e47faad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f78c94a2700 (LWP 12872)): #0 0x7f793400e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f790f1e77c3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f790f509421 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f7934009744 in start_thread (arg=0x7f78c94a2700) at pthread_create.c:334 #4 0x7f793e47faad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f791152a700 (LWP 12871)): #0 0x7f793400e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f790f1e77c3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f790f509421 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f7934009744 in start_thread (arg=0x7f791152a700) at pthread_create.c:334 #4 0x7f793e47faad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f7911d2b700 (LWP 12870)): #0 0x7f793400e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f790f1e67ed in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f790f509421 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f7934009744 in start_thread (arg=0x7f7911d2b700) at pthread_create.c:334 #4 0x7f793e47faad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f78ca325700 (LWP 12869)): #0 0x7f793e47720d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f793326b314 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f78c4002e70, timeout=9367, context=0x7f78c4000990) at gmain.c:4135 #2 0x7f793326b314 in g_main_context_iterate (context=context@entry=0x7f78c4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f793326b42c in g_main_context_iteration (context=0x7f78c4000990, may_block=1) at gmain.c:3901 #4 0x7f7938e3c1ab in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f78c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f7938de9bfb in QEventLoop::exec(QFlags) (this=this@entry=0x7f78ca324c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #6 0x7f7938c24f5a in QThread::exec() (this=) at thread/qthread.cpp:500 #7 0x7f7938c29a29 in QThreadPrivate::start(void*) (arg=0x45a7d70) at thread/qthread_unix.cpp:365 #8 0x7f7934009744 in start_thread (arg=0x7f78ca325700) at pthread_create.c:334 #9 0x7f793e47faad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f790af39700 (LWP 12868)): #0 0x7f793400e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f790f4da953 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f790f4da979 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f7934009744 in start_thread (arg=0x7f790af39700) at pthread_create.c:334 #4 0x7f793e47faad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f7924caf700 (LWP 12534)): #0 0x7f793e47720d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f793326b314 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f791800e090, timeout=-1, context=0x7f7918000990) at gmain.c:4135 #2 0x7f793326b314 in g_main_context_iterate (context=context@entry=0x7f7918000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f793326b42c in g_main_context_iteration (context=0x7f7
[akregator] [Bug 383719] New: corrupt xml error
https://bugs.kde.org/show_bug.cgi?id=383719 Bug ID: 383719 Summary: corrupt xml error Product: akregator Version: 5.5.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: doug...@gmail.com Target Milestone: --- Application: akregator (5.5.3) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: This error occurs on reboot. Akregator complains about corrupt xml entries and discards ALL user added data, creating a default list of feeds instead. Doesn't seem to matter which feeds have been added. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2e81b85e00 (LWP 2803))] Thread 25 (Thread 0x7f2dd794a700 (LWP 3136)): #0 0x7f2e77ea05dd in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e6a7648e4 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f2e6a764929 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f2e77e9a4d7 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2e7d9e8b2f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f2ddc96a700 (LWP 3055)): #0 0x7f2e77ea05dd in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e6d550ec5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2e6d5513a7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2e6d552141 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2e6d54e80b in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f2e77e9a4d7 in start_thread () at /lib64/libpthread.so.0 #6 0x7f2e7d9e8b2f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f2e067fc700 (LWP 2958)): #0 0x7f2e7d9daefd in read () at /lib64/libc.so.6 #1 0x7f2e760a4840 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2e760607fb in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2e76060cc0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2e76060e2c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2e7e2ff6ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2e7e2a835a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f2e7e0d831a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f2e7e0dcd2e in () at /usr/lib64/libQt5Core.so.5 #9 0x7f2e77e9a4d7 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2e7d9e8b2f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f2e06ffd700 (LWP 2935)): #0 0x7f2e7d9df18d in poll () at /lib64/libc.so.6 #1 0x7f2e670bf881 in () at /usr/lib64/libpulse.so.0 #2 0x7f2e670b1240 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f2e670b18d0 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f2e670b1960 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f2e670bf7c9 in () at /usr/lib64/libpulse.so.0 #6 0x7f2e6011b478 in () at /usr/lib64/pulseaudio/libpulsecommon-10.99.so #7 0x7f2e77e9a4d7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2e7d9e8b2f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f2e077fe700 (LWP 2934)): #0 0x7f2e77ea090c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e6d57f7b2 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2e6d5468be in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2e6d52170b in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2e6d51df88 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f2e6d53ab7b in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f2e6d552706 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f2e6d54e80b in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f2e77e9a4d7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2e7d9e8b2f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f2e07fff700 (LWP 2933)): #0 0x7f2e77ea05dd in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e6ddb9fe0 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2e6d552141 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f2e6d54e80b in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f2e77e9a4d7 in start_thread () at /lib64/libpthread.so.0 #5 0x7f2e7d9e8b2f in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f2e1cff9700 (LWP 2932)): #0 0x7f2e77ea05dd in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2e6d546939 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f2e6d546967 in () at /usr/lib64/libQt5
[systemsettings] [Bug 380113] Plymouth KCM update-alternatives not able to set available themes
https://bugs.kde.org/show_bug.cgi?id=380113 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383666] KCM Plymouth - error when changing theme
https://bugs.kde.org/show_bug.cgi?id=383666 --- Comment #1 from Dr. Chapatin --- I can confirm this bug on Antergos (Arch-based), plasma 5.10.4. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 369611] Dolphin cannot create links to files, only directories
https://bugs.kde.org/show_bug.cgi?id=369611 --- Comment #4 from Guo Yunhe --- One quick idea: Have two context menu entries and dialog: 1. Link to a file --> use a file picker 2. Link to a folder --> use a folder picker This will give users the function they want before Qt support this feature. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358254] Setting the toolbar font does nothing
https://bugs.kde.org/show_bug.cgi?id=358254 Henrik (rkflx) changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||rk...@lab12.net --- Comment #4 from Henrik (rkflx) --- Allan: I'm working on a similar fix in https://phabricator.kde.org/D6697 (while I included the bug number, somehow I missed your comment until now as it only appeared shortly before I submitted my review – sorry for that). However, it seems I cannot get your fix to Qt working locally. I tried Plasma (Breeze), IceWM (Fusion) and XFCE (Adwaita), all with Qt 5.9.1 on Tumbleweed which should include your patch according to gerrit. For testing I created a MainWindow with a toolbar in Qt Designer. Only with Plasma the MainWindow picked up KDE's settings: Menubar as specified in kdeglobals, but Toolbar got general font. I also tested with Qt 5.6.2, which should not include your patch. We get the same behaviour as above (only Plasma was tested). This means your patch seems to change nothing for me. Apparently KDE's settings are picked up only in Plasma, and then the Plasma QPA takes over which is not based on the unix platformtheme. Could you share how to reproduce your fix properly? (I might have missed something). Let me know if we should continue this discussion in gerrit. Even though I might commit my patch to Plasma (which works on both 5.6.2 and 5.9.1, so not dependant on your Qt patch) shortly, I'd be interested to understand your Qt patch properly, as I'll maybe look into the "Toolbar vs Toolbutton" issue in the next weeks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 273716] transupp.cpp failing at make (2.0.0 Beta 5 under Fedora 14)
https://bugs.kde.org/show_bug.cgi?id=273716 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 127238] libkipi/interface.h: No such file or directory
https://bugs.kde.org/show_bug.cgi?id=127238 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 340295] make fails on imagedescedittab.cpp has no member named 'textEdit'
https://bugs.kde.org/show_bug.cgi?id=340295 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 341298] libkexiv2-4.14.3/libkexiv2/kexiv2exif.cpp:934: bad if test ?
https://bugs.kde.org/show_bug.cgi?id=341298 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 108458] Make gives error "digikamthumbnail.cpp:662: error: visibility arg must be one of "default", "hidden", "protected" or "internal"
https://bugs.kde.org/show_bug.cgi?id=108458 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 222490] digikam: fails to build with gcc-4.5
https://bugs.kde.org/show_bug.cgi?id=222490 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 314784] digikam 3.0 breaks during build
https://bugs.kde.org/show_bug.cgi?id=314784 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 147626] 0.9.2 fails to build
https://bugs.kde.org/show_bug.cgi?id=147626 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 142088] Build fails when libkexiv2 is in $PREFIX, but not in $KDEDIR or standard include directories
https://bugs.kde.org/show_bug.cgi?id=142088 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball-Compilation |Tarball -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 265445] digikam-1.8.0 fails to build against kde-4.6.x/gcc-4.6
https://bugs.kde.org/show_bug.cgi?id=265445 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 193348] Can't build digikam on kde 4.2.3
https://bugs.kde.org/show_bug.cgi?id=193348 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 165403] Build issues with 0.1.6-beta1
https://bugs.kde.org/show_bug.cgi?id=165403 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92929] digikam 0.7 fails to build
https://bugs.kde.org/show_bug.cgi?id=92929 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 240469] Fails to build with glib >= 2.25
https://bugs.kde.org/show_bug.cgi?id=240469 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 142088] Build fails when libkexiv2 is in $PREFIX, but not in $KDEDIR or standard include directories
https://bugs.kde.org/show_bug.cgi?id=142088 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378218] Build failure around DFontProperties
https://bugs.kde.org/show_bug.cgi?id=378218 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 287772] build failed against boost-1.48 [patch]
https://bugs.kde.org/show_bug.cgi?id=287772 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 274462] build failure in kmemoryinfo - swapctl
https://bugs.kde.org/show_bug.cgi?id=274462 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 340944] Build failed against libjpeg-turbo-1.3.90
https://bugs.kde.org/show_bug.cgi?id=340944 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 122747] Will not build with GCC 4.1
https://bugs.kde.org/show_bug.cgi?id=122747 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 292645] Build fails at imageproperties/captionedit.cpp
https://bugs.kde.org/show_bug.cgi?id=292645 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 274455] build fails in kmemoryinfo - invalid conversion from 'void*' to 'kstat_named_t*'
https://bugs.kde.org/show_bug.cgi?id=274455 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 274432] build fails due to UINT32 ...
https://bugs.kde.org/show_bug.cgi?id=274432 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 341031] LibLqr detected during build but shown as not supported in components information
https://bugs.kde.org/show_bug.cgi?id=341031 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 282099] easier installation (compare to Building Digikam for Dummies on Ubuntu and other linux based distro´s)
https://bugs.kde.org/show_bug.cgi?id=282099 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360473] Fails to build against libkipi-15.12.x
https://bugs.kde.org/show_bug.cgi?id=360473 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372362] Build error due to private function
https://bugs.kde.org/show_bug.cgi?id=372362 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366542] Build failure on i686
https://bugs.kde.org/show_bug.cgi?id=366542 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 356672] digikam 4.14.0 failed to build against lensfun 0.3.2
https://bugs.kde.org/show_bug.cgi?id=356672 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348211] digikam fails to build using >=gcc-5
https://bugs.kde.org/show_bug.cgi?id=348211 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 146312] Configure rules for digikam 0.92 Beta 2 using --prefix=/home/xav/build
https://bugs.kde.org/show_bug.cgi?id=146312 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 285240] digikam fails to build with external libpgf-6.11.42
https://bugs.kde.org/show_bug.cgi?id=285240 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 290466] MacPorts DigiKam package fails to build
https://bugs.kde.org/show_bug.cgi?id=290466 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 306136] build failed without an explicit error
https://bugs.kde.org/show_bug.cgi?id=306136 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361033] Build fails on Slackware Linux
https://bugs.kde.org/show_bug.cgi?id=361033 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 328818] 4.0.0-beta1 - Build Errors (kevix2.h)
https://bugs.kde.org/show_bug.cgi?id=328818 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 287787] Can't build on Ubuntu Oneiric x86-64
https://bugs.kde.org/show_bug.cgi?id=287787 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 279696] Building the unittests of libkgeomap fails
https://bugs.kde.org/show_bug.cgi?id=279696 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 111084] build failure, gcc-4.0.1, -fvisibility
https://bugs.kde.org/show_bug.cgi?id=111084 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 254315] Please consider attached patch for build system
https://bugs.kde.org/show_bug.cgi?id=254315 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 290496] Fails to build against libkipi from kde-4.7.95
https://bugs.kde.org/show_bug.cgi?id=290496 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278966] Building the unittests fails when using external libpgf
https://bugs.kde.org/show_bug.cgi?id=278966 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 290642] build failed with gcc-4.7.0 [patch]
https://bugs.kde.org/show_bug.cgi?id=290642 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 140279] Fails to build
https://bugs.kde.org/show_bug.cgi?id=140279 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 265197] Please specify dependencies of digikam-2.0, and make digikam-2.0/core also build with stock kde
https://bugs.kde.org/show_bug.cgi?id=265197 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 257949] Build fails on XP due to line too long
https://bugs.kde.org/show_bug.cgi?id=257949 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 294423] build error under Solaris [patch]
https://bugs.kde.org/show_bug.cgi?id=294423 caulier.gil...@gmail.com changed: What|Removed |Added Component|Tarball |Tarball-Compilation -- You are receiving this mail because: You are watching all bug changes.