[krita] [Bug 388164] Suggested functionality for Krita Warp tool - Rectangular Selection, and Movement constraint
https://bugs.kde.org/show_bug.cgi?id=388164 Boudewijn Rempt changed: What|Removed |Added Keywords||triaged Severity|normal |wishlist CC||b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388166] Photoshop Shear for Krita
https://bugs.kde.org/show_bug.cgi?id=388166 Boudewijn Rempt changed: What|Removed |Added Keywords||triaged Severity|normal |wishlist CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Do NOT enter feature requests as normal bugs! Do NOT enter feature requests in the form of "Add feature X from application Y". That is not useful and wastes our time. Do NOT enter a wish bug for every filter in Photosop. Without theses wishes, we known they exist. We're not suddenly going to add these filters because there's a wish in bugzilla... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379519] JJ: Improvement to the color adjustment curves
https://bugs.kde.org/show_bug.cgi?id=379519 --- Comment #5 from shubhamgoyal <22shub...@gmail.com> --- Created attachment 109490 --> https://bugs.kde.org/attachment.cgi?id=109490&action=edit Patch file of diff in src directory Patch file for changes in code. Patch is diff file in src directory. 1)Added a reset button to color adjustment curve. 2)Made flexible histogram layout. file changed:- kis_curve_widget.cpp kis_perchannel_filter.cpp kis_perchannel_filter.h wdg_perchannel.ui -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388163] Inkscape-Style Envelope tool or Photoshop Warp tool
https://bugs.kde.org/show_bug.cgi?id=388163 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED Severity|normal |wishlist Resolution|--- |WORKSFORME --- Comment #2 from Boudewijn Rempt --- a) this is clearly a feature request, so the priority should be "wishlist" b) a feature request that goes like "add feature from app Y" isn't helpful c) I'm not going to spend time looking at videos, but your description sounds like what you want is the cage option of the transform too. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388166] New: Photoshop Shear for Krita
https://bugs.kde.org/show_bug.cgi?id=388166 Bug ID: 388166 Summary: Photoshop Shear for Krita Product: krita Version: 4.0 pre-alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: reptilli...@live.com Target Milestone: --- There's a interesting filter which is Photoshop shear. What it does it allow one to shift pixels according to a curve from one end to another. There's a few filters in Krita that are rarely used (color transfer comes to mind), but they still are there. The only application for this filter is to enable artists to create interesting background that are less uniform than the wave filter, and glitch art. There's also fabric creation which of course, would aid in concept art creation. There's a few artistic purpose to this. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
https://bugs.kde.org/show_bug.cgi?id=345979 avlas changed: What|Removed |Added CC||jsar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378322] Kate-ctags-plugin can not passes path string which contain space character to ctags command correctory
https://bugs.kde.org/show_bug.cgi?id=378322 --- Comment #3 from Yuki --- (In reply to Vasudeo from comment #2) > (In reply to Yuki from comment #0) > > > - Setting of CTags plugin - > > Index Target: D:/Projects/tmp/src dir > > CTags database file: D:\Projects\tmp\tags dir\tags > > I have observed this bug on Linux (Mint/Kubuntu) Kate (V16.04.3) as well. > Can you please edit the field 'Platform' in the bug description to > accommodate Linux along with Windows? > > Thanks. I've changed platform to unspecified, is this ok? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378322] Kate-ctags-plugin can not passes path string which contain space character to ctags command correctory
https://bugs.kde.org/show_bug.cgi?id=378322 Yuki changed: What|Removed |Added OS|MS Windows |All Platform|MS Windows |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387618] words less than 3 letters are ignored
https://bugs.kde.org/show_bug.cgi?id=387618 --- Comment #4 from avlas --- Just saw this https://bugs.kde.org/show_bug.cgi?id=387618 Are these two bugs referring to the same thing? Is this bug then fixed too by the same commit https://cgit.kde.org/messagelib.git/commit/?id=999bac0c064c600868af35852d2fe000aab09970? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388141] Use KIO::highlightInFileManager in attachment saved confirmation
https://bugs.kde.org/show_bug.cgi?id=388141 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Version Fixed In||5.8.0 --- Comment #2 from Laurent Montel --- it's fixed in 5.8.0 I had a problem with my name in commit so it didn't change status. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 386953] Option to select background color for plugins
https://bugs.kde.org/show_bug.cgi?id=386953 --- Comment #8 from avlas --- > If some border/line size setting would solve that, we can do this with our > widget, too. If that means a line width different than 0, then I think that would solve the issue, yes. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388165] New: After updating to 17.12 kmail does not display ical invitations from Google Calendar
https://bugs.kde.org/show_bug.cgi?id=388165 Bug ID: 388165 Summary: After updating to 17.12 kmail does not display ical invitations from Google Calendar Product: kmail2 Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- The email body of ical invitations from Google Calendar is empty. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387618] words less than 3 letters are ignored
https://bugs.kde.org/show_bug.cgi?id=387618 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #3 from avlas --- (In reply to davidblunkett from comment #2) > This is nonsensical -I understand that unspecific keys are not very useful > but that is an issue for the user and shouldn't be enforced by the interface. > > I need to do a 2 letter search that will uniquely identify 3 emails out of > 1000 but this is blocked whereas there there are lots of longer strings that > will be found in every single email yet these are allowed. > > This is a poor policy and should be removed. I agree with this comment. Think for instance when looking for country codes, such as UK (also being sensitive to case would help for e.g. US) Perhaps the logi goes like this: searching 1 or 2 letters is very computationally demanding, and most of the time a user will search words of >= 3 letters anyways, so the user won't like the search process to be unresponsive after introducing the 1st or 2nd letter. If that would be the problem, could the search algorithm impose a delay to retrieve matches when only 1 or 2 letters are introduced? Would that be a good compromise solution? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384943] Automatic filters on maildirs are not applied automatically
https://bugs.kde.org/show_bug.cgi?id=384943 avlas changed: What|Removed |Added CC||jsar...@gmail.com --- Comment #2 from avlas --- I can reproduce this bug in some of my filters. Others work fine. I have no clue why some of them fail and some other just work :/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379519] JJ: Improvement to the color adjustment curves
https://bugs.kde.org/show_bug.cgi?id=379519 shubhamgoyal <22shub...@gmail.com> changed: What|Removed |Added CC||22shub...@gmail.com --- Comment #4 from shubhamgoyal <22shub...@gmail.com> --- (In reply to Boudewijn Rempt from comment #3) > Hi Isabelle, > > I see in my irc backlog that you tried to ask questions -- unfortunately, > almost all of us are in timezones where one is usually in bed when you asked > your question. > > KDE isn't that relevant -- we use some frameworks, but the most important > thing is Qt. In any case, you wrote on irc that you have already gotten > Krita built and installed, which is the biggest step. Shreyas already worked > on part of this wish: enabling the logarithmic view in the histograms, but I > he added that to the levels filter. If you check his diff, that would be a > starting point for adding the same switch to the curves filter: > https://phabricator.kde.org/D6621 > > The reset button would be simply a push button you add to the ui file. > > The relevant code is in krita/plugins/filters/colorsfilters, > > wdg_perchannel.ui > kis_perchannel_filter.cpp > kis_perchannel_filter.h > > Good luck! Hi, I fixed some issues. 1)Added a reset button in color adjustment curve. 2)Made flexible histogram layout. How should I contribute it to the project? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388164] New: Suggested functionality for Krita Warp tool - Rectangular Selection, and Movement constraint
https://bugs.kde.org/show_bug.cgi?id=388164 Bug ID: 388164 Summary: Suggested functionality for Krita Warp tool - Rectangular Selection, and Movement constraint Product: krita Version: 4.0 pre-alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: reptilli...@live.com Target Milestone: --- There are two things I would love to see in Krita warp tool. 1) Rectangular selection option for Krita Warp tool 2) Being able to constraint to vertical or horizontal movement. The first one would solve the cumbersome issue of manipulating many points to get an effect. The second one is just adding functionality to the warp tool, but not needed, but it's a idea. The first one is a must IMHO. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388163] Inkscape-Style Envelope tool or Photoshop Warp tool
https://bugs.kde.org/show_bug.cgi?id=388163 --- Comment #1 from reptilli...@live.com --- Another example - https://www.youtube.com/watch?v=ul1l3K6nVgI Note the direction vector can be manipulated with ease unlike the current warp tool. This video shows how it can benefit concept artists. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388163] New: Inkscape-Style Envelope tool or Photoshop Warp tool
https://bugs.kde.org/show_bug.cgi?id=388163 Bug ID: 388163 Summary: Inkscape-Style Envelope tool or Photoshop Warp tool Product: krita Version: 4.0 pre-alpha Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: reptilli...@live.com Target Milestone: --- These are transformation that involves a mesh with the option to set up your own direction vectors, and with ease of manipulating a large area with a highly smooth area. These tools are more efficient for placing textures in a non-destructive manner than the current liquify and warp tool. As of now, it would take a lot of stroke to do this with the current liquify tool, and especially with extremely large image where it would take a huge ton of memory to work with. These tools essentially solve these issues with the current Krita tool. For a example - https://www.youtube.com/watch?v=o_pkpBEVYZE For justification to support to add this feature, let's see this quote: - Krita is a professional FREE and open source painting program. It is made by artists that want to see affordable art tools for everyone. concept art texture and matte painters illustrations and comics - Concept art. Concept artists would highly benefit from this tool as they can use a 2D picture, and they would be able to project that texture into a perspective view of a mechanical concept. It would also benefit other area of concept art. This is the main use of Inkscape-style envelope tool or Photoshop warp tool. It would also benefit texture artists, as well as they can use this to preview how textures may look onto other surface. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387884] Scripter does not run edits unless saved
https://bugs.kde.org/show_bug.cgi?id=387884 --- Comment #2 from Brendan --- This bug is present in commit 61a84e2 (15 Dec) When you save a script it seems to uncouple the connection to setDocumentModified - undo is available (press ctrl-Z!) but the signal is not setting off setDocumentModified. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387822] Don't make the updates
https://bugs.kde.org/show_bug.cgi?id=387822 --- Comment #14 from Nate Graham --- No, that's an unrelated issue tracked by Bug 388101. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 387979] Plasmashell and latte dock crashes due abnormal behavior of kactivitymanagerd
https://bugs.kde.org/show_bug.cgi?id=387979 --- Comment #7 from Ivan Bordoni --- is it necessary to reset some SQlite databases? how can I do ? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 387979] Plasmashell and latte dock crashes due abnormal behavior of kactivitymanagerd
https://bugs.kde.org/show_bug.cgi?id=387979
--- Comment #6 from Ivan Bordoni ---
from the account with problems I ran a rm -r ~ / .config / plasma * rc
...So, at the next login, I found a default configuration with the plasma panel
instead of Latte-Dock
and here we immediately highlight the problem described above and that is
plasma shell goes into crash
so I thought to compare the output of the plasmashell command for two different
accounts, one corrupt and one valid
***
CORRUPTED ACCOUNT
***
Ivan@UltrabookSamsung:~> plasmashell
kf5.karchive: bzDecompress returned -5
org.kde.kcoreaddons: Expected JSON property "X-Plasma-ContainmentCategories" to
be a string list. Treating it as a list with a single entry: "panel"
org.opensuse.desktop.defaultPanel
kf5.karchive: bzDecompress returned -5
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
Empty filename passed to function
trying to show an empty dialog
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
kdeinit5: Shutting down running client.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
KActivities: Database can not be opened in WAL mode. Check the SQLite version
(required >3.7.0). And whether your filesystem supports shared memory
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: Application 'plasmashell' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Empty filename passed to function
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
"Message recipient disconnected from message bus without replying"
found lsb_release
Using /proc to determine executable path
Executable is: "/usr/bin/plasmashell"
Executable exists: true
[kleopatra] [Bug 388162] New: don´t recognice the key just created
https://bugs.kde.org/show_bug.cgi?id=388162 Bug ID: 388162 Summary: don´t recognice the key just created Product: kleopatra Version: 3.0.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: Assuan UI Server Assignee: aheine...@intevation.de Reporter: arturoegarciamen...@gmail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- Ocurrió un error cuando se intentaba exportar la clave secreta. El resultado de C:\Program Files (x86)\GnuPG\bin\gpg.exe fue: gpg: key D7FEDF0C83F68A7EF69FC9A7F33E1D57456748AA: error receiving key from agent: Bad passphrase - skipped gpg: AllowSetForegroundWindow(8912) failed: Acceso denegado. gpg: key 7E30A4AD584FC9435C231F36519C5594BF7A77AC: error receiving key from agent: Bad passphrase - skipped gpg: ATENCIàN: no se ha exportado nada -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 285081] Kgpg can't create key pairs
https://bugs.kde.org/show_bug.cgi?id=285081 me changed: What|Removed |Added CC||arturoegarciamendez@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387822] Don't make the updates
https://bugs.kde.org/show_bug.cgi?id=387822 --- Comment #13 from ruiamar --- I'll try Nate meanwhile, I forgot to mention, along with "cgicon:knsrc" -- all categories are missing. This helps? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388161] New: selecting onion skin lightbulb makes Krita unresponsive
https://bugs.kde.org/show_bug.cgi?id=388161 Bug ID: 388161 Summary: selecting onion skin lightbulb makes Krita unresponsive Product: krita Version: git master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: scottpetro...@gmail.com Target Milestone: --- I am on my KDE Neon box with the latest on master. Krita starts to become unresponsive (does not seg fault though) when I do the following: 1. Create a new document 2. Open the timeline docker 3. Add a new keyframe to the timeline 4. Click on the light bulb to enable onion skinning The light bulb does not turn on...and Krita goes into an unresponsive state. I moved around to different commits and it seems like the problems starts happening at this commit. b180f3c768fc3d4e Merge remote-tracking branch 'origin/master' into kazakov/lazy-brush -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388140] Frequent crashes (few per day) when using application launcher
https://bugs.kde.org/show_bug.cgi?id=388140 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Crash is in libsqlite3. Please report this issue to libsqlite3 developers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388136] Krita crashed after removing a vector layer (text)
https://bugs.kde.org/show_bug.cgi?id=388136 --- Comment #4 from Altguard --- That alone helps me out. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 388083] Error after graphics drivers upgrade
https://bugs.kde.org/show_bug.cgi?id=388083 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- If this crash persists after a reboot, please ask for help in a forum of your distribution and/or video drivers vendor. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 388066] Date & Time adjust crash
https://bugs.kde.org/show_bug.cgi?id=388066 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Christoph Feck --- Fixed in Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 183429] open externally called folder in new tab
https://bugs.kde.org/show_bug.cgi?id=183429 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=388016 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388016] Device Notifier opens a new Dolhin Window even if Dolphin already runs
https://bugs.kde.org/show_bug.cgi?id=388016 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=183429 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 367634] Copying text with ctrl+ins does not work
https://bugs.kde.org/show_bug.cgi?id=367634 --- Comment #6 from Sic Volo --- A workaround for this issue is to create a global shortcut remapping Ctrl-Ins into Ctrl+Shift+C Good enough for now, all hopes on the wayland version -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 388160] ksmtp EHLO sends server hostname as domain parameter by default
https://bugs.kde.org/show_bug.cgi?id=388160 --- Comment #1 from kzi --- My system is openSUSE Tumbleweed. kmailtransport 17.12.0-1.1-x86_64 ksmtp 17.12.0-3.1-x86_64 (How does that relate to the 'Version' dropdown above?) -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 388160] New: ksmtp EHLO sends server hostname as domain parameter by default
https://bugs.kde.org/show_bug.cgi?id=388160 Bug ID: 388160 Summary: ksmtp EHLO sends server hostname as domain parameter by default Product: kmailtransport Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@snafu.de Target Milestone: --- As Fabian Vogt pointed out elsewhere (https://bugs.kde.org/show_bug.cgi?id=387926#c30), ksmtp sends the server hostname as the EHLO domain parameter (confirmed via telnet and wireshark): EHLO mail.snafu.de 550 EHLO/HELO not allowed by local policy. In this case my Provider rejects the EHLO, which results in failure to transport the e-mail. Any other domain will be accepted: EHLO foo.bar 250-sour.ops.eusc.inter.net Hello ... Consequently, this can be worked around by specifying an explicit custom hostname in the SMTP settings e.g. in kmail2. It has been recommended somewhere that in case the client has no (meaningful) domain, the bracketed IP address should be sent, such as: EHLO [nnn.nnn.nnn.nnn] In my case, this is accepted, too. I'm not 100% sure this is a bug, but it seems sane client behavior not to tell the server it ought to talk to itself. It's understandable that the server would test for this domain and none else. This issue didn't arise until a couple of days ago. I do not know what the default EHLO parameter was before that change. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] Settings page UX overhaul
https://bugs.kde.org/show_bug.cgi?id=388153 --- Comment #7 from Nate Graham --- Feel free to ignore my mockups; I like Andreas' more. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] Settings page UX overhaul
https://bugs.kde.org/show_bug.cgi?id=388153 andreas changed: What|Removed |Added CC||kain...@gmail.com --- Comment #6 from andreas --- Created attachment 109489 --> https://bugs.kde.org/attachment.cgi?id=109489&action=edit Discover Setting Layout The idea is to have a consistent layout so also the settings section has the same layout than the app section. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388159] New: Discover should handle apt:// URLs
https://bugs.kde.org/show_bug.cgi?id=388159 Bug ID: 388159 Summary: Discover should handle apt:// URLs Product: Discover Version: 5.11.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: PackageKit Assignee: aleix...@kde.org Reporter: pointedst...@zoho.com Target Milestone: --- Discover doesn't support apt:// URLs, so you can't open various 1-click install thingies available in various corners of the web. For example, apt://arc-theme, available at http://www.omgubuntu.co.uk/2017/11/best-gtk-themes-for-ubuntu -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #9 from Éric Brunet --- Created attachment 109488 --> https://bugs.kde.org/attachment.cgi?id=109488&action=edit patch to reenable numbers, v17.08.3 This is an updated version of my patch to re-enable numbers in the tray icon for kmail. It is for kmail version 5.6.3 shipped with kde 17.08.3, as found in fedora 27. I have also a version for the kmail that shipped with fedora 26 that I forgot to post here. Contact me if anyone needs it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #13 from Petr Nehez --- (In reply to Aleksey Kontsevich from comment #12) > No effect at all! If you restarted Plasma with no effect then I am out of ideas... I am not KDE expert, just an user. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #12 from Aleksey Kontsevich --- (In reply to Petr Nehez from comment #11) > Try to put a real value for 'minimumHeight' - at least to see if it works > (e.g. 900). No effect at all! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #11 from Petr Nehez --- (In reply to Aleksey Kontsevich from comment #10) > > I think it depends also on your screen resolution, mine is 1920x1080. > Mine is same, I have 42" monitor (52 DPI). Hmm, you have quite big monitor so I guess your gridUnit is lower than mine, but this is just my guess. Try to put a real value for 'minimumHeight' - at least to see if it works (e.g. 900). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #8 from Maik Qualmann --- And digiKam-5.7.0 is not really ready for Qt >= 5.9.3. This requires the current git version of digiKam-5.8.0. I do not know if openSUSE has patched the digiKam-5.7.0 version for this. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #7 from Marcus Gama --- About the GDB, this is what I got: Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. 0x7fffee951baa in Marble::GeoSceneLayer::backend() const () from /usr/lib64/libmarblewidget-qt5.so.27 I made some tests and I figured out what happened. The problem was the other repo. According the backtrace above, the digikam was compiled with the libmarblewidget-qt5.so.27, provided by KDE Apps 17.04. The new repo provides KDE Apps 17.12, with libmarblewidget-qt5.so.28. This broke the system. I removed the new Marble and installed the old one and the problem was solved. Maik, thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #10 from Aleksey Kontsevich --- (In reply to Petr Nehez from comment #9) > I think it depends also on your screen resolution, mine is 1920x1080. Mine is same, I have 42" monitor (52 DPI). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #31 from kzi --- (In reply to Fabian Vogt from comment #30) > ksmtp sends the server's hostname instead of the local hostname by accident > with the "EHLO" command. The mail.snafu.de server rejects that immediately, > but example.com works. > > Please try this workaround to confirm: In the account configuration dialog, > in the "advanced" tab, enter "example.com" as "Send custom hostname to > server". Indeed, that works around my issue. After your hint I learned: > telnet mail.snafu.de 587 EHLO foo.bar 250-... (ok) EHLO mail.snafu.de 550 EHLO/HELO not allowed by local policy. Connection closed by foreign host. So seemingly /every/ EHLO domain parameter but the server host is accepted! Thank you so much for this offtopic help! > Please open a new bug report for that. I will, now that I have a clue. ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #6 from Maik Qualmann --- Qt-5.10.0? This is not a normal openSUSE Leap 42.3 anymore. And Qt will not be updated when installing digiKam-5.7.0. OpenSUSE Tumbleweed is still using Qt-5.9.3 here. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388128] [suggestion] KWin as a VNC server
https://bugs.kde.org/show_bug.cgi?id=388128 --- Comment #6 from RJVB --- In that case, please remember that I'm Dutch so English is a second language and I am even more direct (or can be as over 30y in international exchange have taught me a minimum of restraint). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #5 from Marcus Gama --- This is my components info (in Portuguese): digikam version 5.7.0 CPU cores: 8 Eigen: 3.2.9 Exiv2: 0.26 Exiv2 can write to Jp2: Sim Exiv2 can write to Jpeg: Sim Exiv2 can write to Pgf: Sim Exiv2 can write to Png: Sim Exiv2 can write to Tiff: Sim Exiv2 supports XMP metadata: Sim KF5: 5.32.0 LensFun: 0.3.2-0 LibCImg: 130 LibJPEG: 80 LibJasper: 1.900.14 LibLCMS: 2080 LibLqr support: Sim LibPGF: 7.15.32 LibPNG: 1.6.8 LibRaw: 0.18.2 LibTIFF: 4.0.8 Marble: 0.27.1 Parallelized demosaicing: Sim Qt: 5.10.0 Infraestrutura do banco de dados: QSQLITE LibGphoto2: 2.5.13 LibKipi: 5.2.0 LibOpenCV: 3.3.1 LibQtAV: 1.12.0 Plugins do Kipi: 5.7.0 Suporte ao AkonadiContact: Sim Suporte ao Baloo: Sim Suporte ao calendário: sim Suporte para galerias HTML: sim Suporte para leitores multimédia: Sim Suporte para o D-Bus: Sim Suporte à panorâmica: sim I'm not sure if this issue can be result of the other repository mentioned (http://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_42.3/). This repository installed the latest Kde applications (17.12). The Marble works fine (stand alone at least). I already tried to remove the digikamrc but the crash persists. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 388158] New: Using "Organize Files" drops labels
https://bugs.kde.org/show_bug.cgi?id=388158 Bug ID: 388158 Summary: Using "Organize Files" drops labels Product: amarok Version: 2.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Collections/Organize Files Dialog Assignee: amarok-bugs-d...@kde.org Reporter: m.krasilni...@yandex.ru CC: ralf-eng...@gmx.de Target Milestone: 2.9 Created attachment 109487 --> https://bugs.kde.org/attachment.cgi?id=109487&action=edit Screenshot before and after. All track labels are dropped after using "Organize Files" feature. STR: 1. Add some labels to track 2. Use Organize Files to move file to anther folder. ER: Track labels preserved. AR: All labels are gone. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] Settings page UX overhaul
https://bugs.kde.org/show_bug.cgi?id=388153 Nate Graham changed: What|Removed |Added Severity|normal |wishlist Summary|"Application Sources" menu |Settings page UX overhaul |has unclear purpose and UX | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] "Application Sources" menu has unclear purpose and UX
https://bugs.kde.org/show_bug.cgi?id=388153 --- Comment #5 from Nate Graham --- Created attachment 109486 --> https://bugs.kde.org/attachment.cgi?id=109486&action=edit Mockup (multiple sources) And here's the proposed UI when there are multiple sources--in this case, Flathub and Ubuntu 17.10 package repos. One source becomes the default (marked with "Default Source"), and all the other sources gain a "Make Default" button. A source jumps or animates to the top of the list when it's made the default. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] "Application Sources" menu has unclear purpose and UX
https://bugs.kde.org/show_bug.cgi?id=388153 Nate Graham changed: What|Removed |Added Attachment #109484|0 |1 is obsolete|| --- Comment #4 from Nate Graham --- Created attachment 109485 --> https://bugs.kde.org/attachment.cgi?id=109485&action=edit Mockup (single source) After a few rounds of design work in the Discover Design Telegram room, we came up with some new mockups. This one shows the UI when there is only a single backend (in this case my Ubuntu 17.10 package repositories). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #30 from Fabian Vogt --- (In reply to kzi from comment #28) > I can confirm the issue on Tumbleweed, KMail 5.7.0, server mail.snafu.de > port 25 or 587. Encryption 'None' or TLS results in Socket error: 2, while > SSL gives Socket error: 9. TLS/25/PLAIN is autodetected. Provider says 'SSL' > (but probably means TLS) and above ports. > > The ksmtp patch 17.12.0-3-1 rolled out today noon UTC: > - Add patch to fix sending of emails over SSL (without STARTTLS): > * 0001-Fix-duplicate-authentication.patch > * Fixes kde#388068, kde#387926 and boo#1073975 > > does ***NOT*** fix this issue for me. It is indeed a different issue, but it's fairly simple: ksmtp sends the server's hostname instead of the local hostname by accident with the "EHLO" command. The mail.snafu.de server rejects that immediately, but example.com works. Please try this workaround to confirm: In the account configuration dialog, in the "advanced" tab, enter "example.com" as "Send custom hostname to server". Please open a new bug report for that. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 388148] KSquares: Don't introduce in AppStream translations (de)
https://bugs.kde.org/show_bug.cgi?id=388148 --- Comment #2 from Unknown --- SVN commit 1506981 by lueck: remove invalid quote markup from appdata file M +3 -2 org.kde.ksquares.appdata.po WebSVN link: http://websvn.kde.org/?view=rev&revision=1506981 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 388148] KSquares: Don't introduce in AppStream translations (de)
https://bugs.kde.org/show_bug.cgi?id=388148 Unknown changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Unknown --- SVN commit 1506980 by lueck: remove invalid quote markup from appdata file M +3 -2 org.kde.ksquares.appdata.po WebSVN link: http://websvn.kde.org/?view=rev&revision=1506980 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 --- Comment #4 from Maik Qualmann --- I have openSUSE Leap 42.3 on my service laptop in the company. After updating to digiKam-5.7.0 from the KDE extra repository, I can not reproduce problems with the map. Everything works as expected from this version. Have you possibly installed other updates? Please post the help-> components info. Otherwise, the GDB backtrace would be interesting also without debugging symbols Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365105] QSystemTrayIcon with context menu does not react after second show
https://bugs.kde.org/show_bug.cgi?id=365105 Pavlo84 changed: What|Removed |Added CC||polyako...@gmail.com --- Comment #11 from Pavlo84 --- Confirmed that have the same situation with tray on Archlinux Plasma 5.11.4 Whats the status of bug? Has anybody news? Last comment was 2 month ago. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388157] New: Plasma crash when select Send To Contact from QuickShare widget
https://bugs.kde.org/show_bug.cgi?id=388157 Bug ID: 388157 Summary: Plasma crash when select Send To Contact from QuickShare widget Product: plasmashell Version: 5.11.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: codestr...@posteo.org CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.3) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.14.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Click on the QuickShare widget, click on the right arrow on "Send to Contact..." The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff96d445d80 (LWP 2325))] Thread 11 (Thread 0x7ff87edf7700 (LWP 8507)): #0 0x7ff966a79f0b in poll () at /lib64/libc.so.6 #1 0x7ff95d852831 in () at /usr/lib64/libpulse.so.0 #2 0x7ff95d8441f0 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7ff95d844880 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7ff95d844910 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7ff95d852779 in () at /usr/lib64/libpulse.so.0 #6 0x7ff95c895438 in () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7ff966333558 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff966a846bf in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7ff89090f700 (LWP 8506)): #0 0x7ff961ab9714 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff961a7406e in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff961a7425c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff9673a325b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff96734b73a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff96717b1fa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff96a2b2b05 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7ff96717fc0e in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff966333558 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff966a846bf in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7ff893eab700 (LWP 2855)): #0 0x7ff961ab9714 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff961a73ffd in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff961a7425c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff9673a325b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff96734b73a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff96717b1fa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff896767f67 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7ff96717fc0e in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff966333558 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff966a846bf in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7ff8ab0dc700 (LWP 2548)): #0 0x7ff961ab96f9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff961a74248 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff9673a325b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7ff96734b73a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff96717b1fa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7ff96ae53d22 in () at /usr/lib64/libQt5Quick.so.5 #6 0x7ff96717fc0e in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff966333558 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff966a846bf in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7ff8b87f1700 (LWP 2473)): #0 0x7ff96633982d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff9405600db in () at /usr/lib64/dri/nouveau_dri.so #2 0x7ff94055fff7 in () at /usr/lib64/dri/nouveau_dri.so #3 0x7ff966333558 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff966a846bf in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7ff9431c1700 (LWP 2439)): #0 0x7ff96633982d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff96cb2c554 in () at /usr/lib64/libQt5Script.so.5 #2 0x7ff96cb2c599 in () at /usr/lib64/libQt5Script.so.5 #3 0x7ff966333558 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff966a846bf in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7ff94d594700 (LWP 2411)): #0 0x7ff967177c7f in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5 #1 0x7ff9673a319f in () at /usr/lib64/libQt5Co
[kwin] [Bug 388128] [suggestion] KWin as a VNC server
https://bugs.kde.org/show_bug.cgi?id=388128 --- Comment #5 from Martin Flöser --- I have now been the maintainer of KWin for - I don't know - 6, 7 years. I don't remember a single case where a feature or idea was suggested which I hadn't thought about before. You can think it's a generalization or even arrogant, but that's how it is. For the specific topic on remote rendering I even blogged about it in 2015: https://blog.martin-graesslin.com/blog/2015/10/september-update-for-plasmas-wayland-porting/ Please also remember that this is a technical issue tracking, that English is not my native language and that I'm German which means I'm extremely direct. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 330088] OAuth is lost after each system reboot
https://bugs.kde.org/show_bug.cgi?id=330088 Andrea Scarpino changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED CC||scarp...@kde.org --- Comment #8 from Andrea Scarpino --- With current git we migrated to Qt's OAuth implementation, so maybe this is no more valid. Re-open if necessary. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388147] "More Tags..." Doesn't Open Captions Side Menu In Preview
https://bugs.kde.org/show_bug.cgi?id=388147 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/12cd7b1e27858883225419 ||903eb7c302ef16e378 Version Fixed In||5.8.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- Git commit 12cd7b1e27858883225419903eb7c302ef16e378 by Maik Qualmann. Committed on 22/12/2017 at 19:29. Pushed by mqualmann into branch 'master'. fix signal/slot connections from the "More Tags" action FIXED-IN: 5.8.0 M +2-2NEWS M +0-1app/items/digikamimageview.h M +3-0app/views/digikamview.cpp M +1-1app/views/stackedview.cpp M +1-0app/views/stackedview.h https://commits.kde.org/digikam/12cd7b1e27858883225419903eb7c302ef16e378 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 374670] AAC transcoding is broken due to deprecated libfaac
https://bugs.kde.org/show_bug.cgi?id=374670
--- Comment #26 from rdragonr...@gmail.com ---
I have followed the instructions in the two recent posts, the Github mock and
the mySQL liblz4 ones.
I attempted to use the Github google mock rather than the built-in one, but I
still got this error set (It seems to deal with libpthread):
Performing C++ SOURCE FILE Test COMPLEX_TAGLIB_FILENAME failed with the
following output:
Change Dir: /home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp
Run Build Command:"/usr/bin/make" "cmTC_dc03d/fast"
/usr/bin/make -f CMakeFiles/cmTC_dc03d.dir/build.make
CMakeFiles/cmTC_dc03d.dir/build
make[1]: Entering directory
'/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_dc03d.dir/src.cxx.o
/usr/bin/c++-I/usr/include/taglib -DCOMPLEX_TAGLIB_FILENAME
-I/usr/include/taglib -o CMakeFiles/cmTC_dc03d.dir/src.cxx.o -c
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/src.cxx
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/src.cxx: In function
‘int main()’:
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/src.cxx:5:38: error:
cannot convert ‘const wchar_t*’ to ‘TagLib::FileName {aka const char*}’ in
initialization
TagLib::FileName fileName2(L"wchar");
^
CMakeFiles/cmTC_dc03d.dir/build.make:65: recipe for target
'CMakeFiles/cmTC_dc03d.dir/src.cxx.o' failed
make[1]: *** [CMakeFiles/cmTC_dc03d.dir/src.cxx.o] Error 1
make[1]: Leaving directory
'/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_dc03d/fast' failed
make: *** [cmTC_dc03d/fast] Error 2
Source file was:
#include
int main()
{
TagLib::FileName fileName1("char");
TagLib::FileName fileName2(L"wchar");
return 0;
}
Determining if the Q_WS_WIN exist failed with the following output:
Change Dir: /home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp
Run Build Command:"/usr/bin/make" "cmTC_33044/fast"
/usr/bin/make -f CMakeFiles/cmTC_33044.dir/build.make
CMakeFiles/cmTC_33044.dir/build
make[1]: Entering directory
'/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_33044.dir/CheckSymbolExists.cxx.o
/usr/bin/c++-I/usr/include/taglib -I/usr/include/qt4 -fmessage-length=0
-Wl,--as-needed -I/usr/include/taglib -o
CMakeFiles/cmTC_33044.dir/CheckSymbolExists.cxx.o -c
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
In function ‘int main(int, char**)’:
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19:
error: ‘Q_WS_WIN’ was not declared in this scope
return ((int*)(&Q_WS_WIN))[argc];
^
CMakeFiles/cmTC_33044.dir/build.make:65: recipe for target
'CMakeFiles/cmTC_33044.dir/CheckSymbolExists.cxx.o' failed
make[1]: *** [CMakeFiles/cmTC_33044.dir/CheckSymbolExists.cxx.o] Error 1
make[1]: Leaving directory
'/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_33044/fast' failed
make: *** [cmTC_33044/fast] Error 2
File
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
/* */
#include
int main(int argc, char** argv)
{
(void)argv;
#ifndef Q_WS_WIN
return ((int*)(&Q_WS_WIN))[argc];
#else
(void)argc;
return 0;
#endif
}
Determining if the Q_WS_QWS exist failed with the following output:
Change Dir: /home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp
Run Build Command:"/usr/bin/make" "cmTC_55009/fast"
/usr/bin/make -f CMakeFiles/cmTC_55009.dir/build.make
CMakeFiles/cmTC_55009.dir/build
make[1]: Entering directory
'/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_55009.dir/CheckSymbolExists.cxx.o
/usr/bin/c++-I/usr/include/taglib -I/usr/include/qt4 -fmessage-length=0
-Wl,--as-needed -I/usr/include/taglib -o
CMakeFiles/cmTC_55009.dir/CheckSymbolExists.cxx.o -c
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
In function ‘int main(int, char**)’:
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19:
error: ‘Q_WS_QWS’ was not declared in this scope
return ((int*)(&Q_WS_QWS))[argc];
^
CMakeFiles/cmTC_55009.dir/build.make:65: recipe for target
'CMakeFiles/cmTC_55009.dir/CheckSymbolExists.cxx.o' failed
make[1]: *** [CMakeFiles/cmTC_55009.dir/CheckSymbolExists.cxx.o] Error 1
make[1]: Leaving directory
'/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_55009/fast' failed
make: *** [cmTC_55009/fast] Error 2
File
/home/rdragonrydr/working_amarok/build/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
/* */
#include
int main(int argc, char** ar
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 --- Comment #19 from Stephen Anthony --- Tangentially related to this issue; is it better to use SSL or TLS when a server offers both? I've changed to TLS to 'work around' this current issue, but I wonder if I should just leave it that way, even when SSL is fixed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 --- Comment #18 from Daniele --- Hi Good work! the patch works on tumbleweed. Thank you very much. cheers Daniele -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 349756] [patch] Run in terminal
https://bugs.kde.org/show_bug.cgi?id=349756 Christoph Cullmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/kat ||e/e0850455361cbe396c05647b9 ||f4d9394fbd73a4f Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Christoph Cullmann --- Git commit e0850455361cbe396c05647b9f4d9394fbd73a4f by Christoph Cullmann, on behalf of Ede Rag. Committed on 22/12/2017 at 17:12. Pushed by cullmann into branch 'master'. allow to run current document in konsole CHANGELOG: Allow to execute the current document in the terminal widget. Differential Revision: https://phabricator.kde.org/D9244 M +120 -6addons/konsole/kateconsole.cpp M +20 -5addons/konsole/kateconsole.h M +1-0addons/konsole/ui.rc https://commits.kde.org/kate/e0850455361cbe396c05647b9f4d9394fbd73a4f -- You are receiving this mail because: You are watching all bug changes.
[kmarkdownwebview] [Bug 388150] kpart appdata wrongly typed as desktop application
https://bugs.kde.org/show_bug.cgi?id=388150 Friedrich W. H. Kossebau changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kma ||rkdownwebview/979774def24dd ||b0ae81f5a16481f2819670eba47 --- Comment #1 from Friedrich W. H. Kossebau --- Git commit 979774def24ddb0ae81f5a16481f2819670eba47 by Friedrich W. H. Kossebau. Committed on 22/12/2017 at 17:10. Pushed by kossebau into branch 'master'. KParts plugin: fix component type set in appstream metadata to "addon" M +1-1src/kpart/CMakeLists.txt R +11 -1src/kpart/org.kde.kmarkdownwebviewpart.metainfo.xml [from: src/kpart/org.kde.kmarkdownwebviewpart.appdata.xml - 093% similarity] https://commits.kde.org/kmarkdownwebview/979774def24ddb0ae81f5a16481f2819670eba47 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] "Application Sources" menu has unclear purpose and UX
https://bugs.kde.org/show_bug.cgi?id=388153 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #3 from Andres Betts --- What I feel needs to happen with this view first is to define each area that it is showing. Make a selection between Flatpak, and what it is, more clear. Separate from other sources and explain the differences. Add two boxes for flatpak and traditional sources instead of one with different headers. On the left pane, I would move the "settings" line to the very bottom where most apps will have them. I can also provide a mockup on this to make the idea clear. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 388144] "Copy to" and "Move to" ignore entered filename
https://bugs.kde.org/show_bug.cgi?id=388144 Henrik Fehlauer changed: What|Removed |Added Ever confirmed|0 |1 CC||rk...@lab12.net Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Henrik Fehlauer --- Thanks for reporting, can confirm the bug. It's a regression introduced by 9056aa941e0d which was not caught during review – sorry for that. We'll fix it for 17.12.1. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 385840] LivePreview reports no existance of tex file
https://bugs.kde.org/show_bug.cgi?id=385840 Michel Ludwig changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |DOWNSTREAM --- Comment #7 from Michel Ludwig --- Actually, Kile is escaping the strings correctly. The problem seems to lie within TeXlive on Windows... Running a similar command on the command line also fails. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 --- Comment #17 from andreas.sturmlech...@gmail.com --- The correct package would be ksmtp. But you just need to sync, and 17.12.0-r1 will be available to you. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 388156] New: NumLock settings are not being applied
https://bugs.kde.org/show_bug.cgi?id=388156 Bug ID: 388156 Summary: NumLock settings are not being applied Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: unassigned-b...@kde.org Reporter: cliv...@kubuntu.org Target Milestone: --- This past week or so, I have noticed that Num Lock is off when I log into Plasma despite my having it turned on in the System Settings. https://i.imgur.com/gVwnwOv.png I am using Neon (dev edition) packages for Bionic. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 --- Comment #16 from Mark Gannon --- Can you give a little more help on applying the patch on gentoo? I tried the patch (renamed as smtpsend.patch) in /etc/portage/patches/kde-apps/kmailtransport-17.12.0/ and /etc/portage/patches/kde-apps/kmail-17.12.0 and then ran ebuild prepare and it failed in both cases. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388155] New: Kmail shows duplicate emails - detect automatically on refresh?
https://bugs.kde.org/show_bug.cgi?id=388155 Bug ID: 388155 Summary: Kmail shows duplicate emails - detect automatically on refresh? Product: kmail2 Version: 5.7.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: northivanas...@gmail.com Target Milestone: --- When using a GMail account, new emails will appear in multiple folders: Inbox, [Gmail]/All Mail, and [Gmail]/Important. It should be trivial to automatically detect when receiving duplicate emails and delete all except in Inbox. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388154] New: Backend switcher UI doesn't appear for apps also available in an Ubuntu PPA
https://bugs.kde.org/show_bug.cgi?id=388154 Bug ID: 388154 Summary: Backend switcher UI doesn't appear for apps also available in an Ubuntu PPA Product: Discover Version: 5.11.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: pointedst...@zoho.com Target Milestone: --- I use Discover on Kubuntu 17.10 with the following PPAs installed: - Kubuntu backports (provides newer versions of KDE software) - VLC nightly builds (provides a newer version of VLC) These PPAs provide versions of their software that have AppStream IDs identical to the versions provided by the regular Kubuntu 17.10 repos. I know that Discover has a backend switcher UI: https://www.youtube.com/watch?v=qzOZZvabNeg&spfreload=10 However, Discover doesn't show the backend switcher on the Application Pages of any apps that are available from both a PPA and the distro packaging. Instead, the PPA version is always shown and the distro-provided version is unavailable until you manually disable the PPA. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375483] Wrong history on images taken with Samsung S3 [patch]
https://bugs.kde.org/show_bug.cgi?id=375483
--- Comment #15 from Gernot Hillier ---
I fixed it manually now in the files as well as in the Digikam database
"digikam4.db":
0. Shutdown digikam, backup digikam4.db and photos.
1. Scan all pictures using "exiftool -ImageUniqueId" and find duplicates. A
small number of duplicates can come from edited pictures, so only filter out
those with many occurences. I used a lot of Samsung phones over the years,
so
I ended up with this list: "NULL NULL ", "LL ", "OAEL01", "S08Q0LEGC01",
"SCEE07", "T13LLIA00PM T13LLIL04SB "
2. Find all problematic images in digikam4.db:
select name from Images where id in (
select imageid from ImageHistory where uuid in ("NULL NULL ", "LL ",...)
);
Compare this list to files with problematic IDs from step 1.
3. Now I started digikam, and deleted IDs from all those files using
"exiftool -ImageUniqueId= ". This forces re-read of files in digikam.
With digikam >= 5.7, a simple touch shuold be enough, too. Shutdown digikam
again.
4. Identify tagid for Digikam's internal tag "Original Version":
select id from Tags where name="Original Version";
For me, this was "112".
5. Find all entries for tag "112" in ImageTags for problematic images:
select * from ImageTags where tagid=112 and imageid in (
select imageid from ImageHistory where uuid in ("NULL NULL ", "LL ", ...)
) ;
Store this result.
6. Verify if some of those images were edited (get file names as in 2., search
for name_v?.jpg). If yes, the originals should keep tag "112".
7. Delete all entries with tag="112" and problematic imageid in ImageTags
which are not found in 6. (For me, step 6 only returned a small number of
files, so I just deleted tag "112" for all Samsung images and added it
later again for those who shall have it.
8. Delete all entries in ImageHistory with problematic uuids.
Sorry for not sharing a full script here, but I had no time to make a polished
version which is sufficiently fool-proof... But if you have some experience
using SQL and shell scripts, the above description will hopefully be helpful...
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 388153] "Application Sources" menu has unclear purpose and UX
https://bugs.kde.org/show_bug.cgi?id=388153 --- Comment #2 from Nate Graham --- The real issue IMHO is that Discover's Settings page doesn't follow the visual or UX conventions for any other KDE application, and this odd menu is just a symptom of that broader issue. Let's start a broader discussion in the VDG or Discover Design telegram rooms. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] "Application Sources" menu has unclear purpose and UX
https://bugs.kde.org/show_bug.cgi?id=388153 --- Comment #1 from Aleix Pol --- I think the mockup is too visually intrusive. Can we maybe improve the wording? or add a tooltip that explains? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] "Application Sources" menu has unclear purpose and UX
https://bugs.kde.org/show_bug.cgi?id=388153 veeye...@gmail.com changed: What|Removed |Added CC||veeye...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 388153] New: "Application Sources" menu has unclear purpose and UX
https://bugs.kde.org/show_bug.cgi?id=388153 Bug ID: 388153 Summary: "Application Sources" menu has unclear purpose and UX Product: Discover Version: 5.11.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: pointedst...@zoho.com Target Milestone: --- Created attachment 109484 --> https://bugs.kde.org/attachment.cgi?id=109484&action=edit Mockup The Settings page's "Application Sources" menu has an unclear purpose and UI. Among the issues: - It's not clear to the user what it controls. Does it choose which application source you want to use? Or does it control the *default* application source? Or something else entirely? - Menus typically don't have radio buttons; unusual UX Assuming this is really a "choose the default backend" control, I've attached a proposed mockup of a different UI that might be a bit more familiar and user-friendly. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 388152] New: Uncorrect value for parent account
https://bugs.kde.org/show_bug.cgi?id=388152 Bug ID: 388152 Summary: Uncorrect value for parent account Product: kmymoney Version: 4.8.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: cont...@lemaire.eu.com Target Milestone: --- When creating a parent account and subaccounts in the hierarchy, the parent account does not show the total value of the subaccounts. It works as if it is hidden and thus does not show the reality. >From my perspective, subaccounts could or should be used as "subprojects" in order to quantify some projects as for instance "World tour project" In such project, it includes transportation, food, etc. With this functionality, it is possible to have a better analyse of the budgets (more powerfull as the tags). If this is not a bug, I suggest that the explanation of how parent and subaccounts are working is written in the help file. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388151] New: Moving messages to other folder corrupts threading
https://bugs.kde.org/show_bug.cgi?id=388151 Bug ID: 388151 Summary: Moving messages to other folder corrupts threading Product: kmail2 Version: 5.6.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: g...@gmx.net Target Milestone: --- When using threading strategy "Perfect and by references", moved messages are threaded randomly in the tree under the thread starter. In the same folder, the direct parent (from In-Reply-To) is also present, but the message not threaded under it. The resulting folder structure is a complete mess. Restarting kmail and/or akonadi doesn't help. Changing to threading startegy "Perfect only" shows the correct tree, but obviously creates separate trees when a message is missing. Switching back to "Perfect and by references" seems to fix the threading. I have not noticed any problems with threading of new incoming emails, only when moving messages between folders. The messages are moved within the same account, which uses online imap as its backend. The message list aggregation is set to "Threaded" with the following config: Grouping: none Group expand policy: - Threading: perfect and by references Thread leader: Topmost message Thread expand policy: Expand threads with unread or important messages Fill view strategy: Favor interactivity -- You are receiving this mail because: You are watching all bug changes.
[kmarkdownwebview] [Bug 388150] New: kpart appdata wrongly typed as desktop application
https://bugs.kde.org/show_bug.cgi?id=388150 Bug ID: 388150 Summary: kpart appdata wrongly typed as desktop application Product: kmarkdownwebview Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kpart Assignee: kosse...@kde.org Reporter: sit...@kde.org Target Milestone: --- https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Application.html > A desktop application is an application which has a graphical user interface > and is commonly used with mouse and keyboard. It also ships a Freedesktop > .desktop file to be visible in application menus. as the kpart is not an application it shouldn't be marked as desktop but addon https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Addon.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355464] Plasmoid downloaded from internet is not remembered as installed
https://bugs.kde.org/show_bug.cgi?id=355464 Anthony Fieroni changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Anthony Fieroni --- The fix introduces a regression. It is correct in https://phabricator.kde.org/R120:acd7034952bc2f72454253056c5a8581b33e22ae -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388149] New: Kmail crash 5min after start
https://bugs.kde.org/show_bug.cgi?id=388149 Bug ID: 388149 Summary: Kmail crash 5min after start Product: kmail2 Version: 5.6.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@fuckl.de Target Milestone: --- Application: kmail (5.6.3) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.14.7-300.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Kmail crashes every time 5min after I start it. In this 5min I can do what I like, everything seems to work just fine. But after 5min it crashes... The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb38cb0d340 (LWP 4237))] Thread 26 (Thread 0x7fb2435f6700 (LWP 4301)): #0 0x7fb382376c4b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb37984ee85 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fb37984f367 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fb379850101 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fb37984c7cb in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fb2c3fff700 (LWP 4300)): #0 0x7fb382376c4b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb36783b604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fb36783b649 in () at /lib64/libQt5Script.so.5 #3 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fb2ca4a3700 (LWP 4287)): #0 0x7fb38644a30b in poll () at /lib64/libc.so.6 #1 0x7fb3711d0ed9 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fb3711d0fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fb3872b535b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fb3872630ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fb3870b48ba in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fb3870b8b92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fb300ff9700 (LWP 4275)): #0 0x7fb38644a30b in poll () at /lib64/libc.so.6 #1 0x7fb365d796f1 in poll_func () at /lib64/libpulse.so.0 #2 0x7fb365d6b0b0 in pa_mainloop_poll () at /lib64/libpulse.so.0 #3 0x7fb365d6b740 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #4 0x7fb365d6b7d0 in pa_mainloop_run () at /lib64/libpulse.so.0 #5 0x7fb365d79639 in thread () at /lib64/libpulse.so.0 #6 0x7fb3637b3ac8 in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fb3017fa700 (LWP 4274)): #0 0x7fb38644592b in write () at /lib64/libc.so.6 #1 0x7fb3863c23fd in _IO_new_file_write () at /lib64/libc.so.6 #2 0x7fb3863c2d9f in __GI__IO_file_xsputn () at /lib64/libc.so.6 #3 0x7fb386395c17 in buffered_vfprintf () at /lib64/libc.so.6 #4 0x7fb386392c56 in vfprintf () at /lib64/libc.so.6 #5 0x7fb386467206 in __fprintf_chk () at /lib64/libc.so.6 #6 0x7fb36ada63e0 in _warn_helper () at /lib64/libevent-2.0.so.5 #7 0x7fb36ada65a4 in event_warn () at /lib64/libevent-2.0.so.5 #8 0x7fb36adaad40 in epoll_dispatch () at /lib64/libevent-2.0.so.5 #9 0x7fb36ad958de in event_base_loop () at /lib64/libevent-2.0.so.5 #10 0x7fb37981fcb9 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #11 0x7fb37981bf88 in base::MessageLoop::RunHandler() () at /lib64/libQt5WebEngineCore.so.5 #12 0x7fb3798389cb in base::RunLoop::Run() () at /lib64/libQt5WebEngineCore.so.5 #13 0x7fb3798506c6 in base::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #14 0x7fb37984c7cb in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #15 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #16 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7fb301ffb700 (LWP 4273)): #0 0x7fb382376c4b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #29 from Christophe Giboudeaux --- (In reply to kzi from comment #28) > I can confirm the issue on Tumbleweed, KMail 5.7.0, server mail.snafu.de > port 25 or 587. Encryption 'None' or TLS results in Socket error: 2, while > SSL gives Socket error: 9. TLS/25/PLAIN is autodetected. Provider says 'SSL' > (but probably means TLS) and above ports. > Different issue, please open a new bug report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388128] [suggestion] KWin as a VNC server
https://bugs.kde.org/show_bug.cgi?id=388128
--- Comment #4 from RJVB ---
Here's one idea you clearly never got: how to avoid spewing insulting
generalisations and other petty remarks ("I'll break it just because I can").
--
You are receiving this mail because:
You are watching all bug changes.
[i18n] [Bug 388148] New: KSquares: Don't introduce in AppStream translations (de)
https://bugs.kde.org/show_bug.cgi?id=388148 Bug ID: 388148 Summary: KSquares: Don't introduce in AppStream translations (de) Product: i18n Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: de Assignee: kde-i18n...@kde.org Reporter: aleix...@kde.org Target Milestone: --- Error loading AppData file: failed to parse /app/share/appdata/org.kde.ksquares.appdata.xml: Error on line 63 char 290: already set 'KSquares ist ein Spiel, das an das bekannte' and tried to replace with '-Spiel Käsekästchen angelehnt ist. Jeder Spieler muss der Reihe nach einen Strich zwischen zwei benachbarten Punkten zeichnen. Ziel des Spiels ist es, mehr Kästchen als der Gegner zu malen.' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381266] Icontasks identifying Chrome apps as Chrome windows
https://bugs.kde.org/show_bug.cgi?id=381266 --- Comment #12 from Kai Uwe Broulik --- I never know which of the two is which but: "crx_gaedmjdfmmahhbjefcbgaolhhanlaolb", "Google-chrome" We end up matching google-chrome (appId) first, perhaps we should check for the (xWindowsWMClassName) first? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388147] New: "More Tags..." Doesn't Open Captions Side Menu In Preview
https://bugs.kde.org/show_bug.cgi?id=388147 Bug ID: 388147 Summary: "More Tags..." Doesn't Open Captions Side Menu In Preview Product: digikam Version: 5.8.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Usability-Menus Assignee: digikam-bugs-n...@kde.org Reporter: hardy.pub...@gmail.com Target Milestone: --- In Preview, right-clicking Assign Tag -> More Tags... doesn't do anything. Expected Behaviour: The above action should open Captions -> Tags tab as per Thumbnail view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 208383] Add "Properties" to the context menu of Kickoff/Kicker items
https://bugs.kde.org/show_bug.cgi?id=208383 Kai Uwe Broulik changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||k...@privat.broulik.de --- Comment #4 from Kai Uwe Broulik --- When I search for e.g. "Dolphin" in Kickoff, I get an "Edit application" entry for that search result which among others lists the executable path -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 kzi changed: What|Removed |Added CC||k...@snafu.de --- Comment #28 from kzi --- I can confirm the issue on Tumbleweed, KMail 5.7.0, server mail.snafu.de port 25 or 587. Encryption 'None' or TLS results in Socket error: 2, while SSL gives Socket error: 9. TLS/25/PLAIN is autodetected. Provider says 'SSL' (but probably means TLS) and above ports. The ksmtp patch 17.12.0-3-1 rolled out today noon UTC: - Add patch to fix sending of emails over SSL (without STARTTLS): * 0001-Fix-duplicate-authentication.patch * Fixes kde#388068, kde#387926 and boo#1073975 does ***NOT*** fix this issue for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388146] New: Make visibility of scrollbars configurable (autohide)
https://bugs.kde.org/show_bug.cgi?id=388146 Bug ID: 388146 Summary: Make visibility of scrollbars configurable (autohide) Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: off...@mikemitterer.at CC: plasma-b...@kde.org Target Milestone: 1.0 Please make scrollbars autohide - I think thats standard for modern Desktops -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 388145] New: Chrome asks over and over for KWallet PW
https://bugs.kde.org/show_bug.cgi?id=388145 Bug ID: 388145 Summary: Chrome asks over and over for KWallet PW Product: kwalletmanager Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: off...@mikemitterer.at Target Milestone: --- Every time I open Chrome it asks me for a password. This is very annoying. My main workstation is a Mac and Password-Management works on Mac without bothering me on every Chrome start. However - I'm running a Jenkins slave on a KDE-Neon machine. The integration-tests are using Chrome. I had to disable KDE-Wallet for Chrome because of this behavior... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369303] Krita fails to build on Windows in Debug mode
https://bugs.kde.org/show_bug.cgi?id=369303 --- Comment #15 from Alvin Wong --- Weird, what's different in debug mode that can cause this error? -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 388109] After the removal of the XML, kdesrc-build downloads wrong metadata
https://bugs.kde.org/show_bug.cgi?id=388109 tcanabr...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from tcanabr...@kde.org --- Works with XS. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 388144] New: "Copy to" and "Move to" ignore entered filename
https://bugs.kde.org/show_bug.cgi?id=388144 Bug ID: 388144 Summary: "Copy to" and "Move to" ignore entered filename Product: gwenview Version: 17.12.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: k...@ashka.me Target Milestone: --- When using "Copy to" or "Move to", Gwenview displays a file picker that asks for a filename. Whatever the entered filename is, the file will be copied/moved retaining the original filename. If the target filename already exists, the file picker will prompt to confirm that the file will be overwritten, but that is not the case. Steps to reproduce: 1. Open file a.jpg 2. Copy file a.jpg to folder/b.jpg Expected: folder/ contains b.jpg Actual: folder/ contains a.jpg -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369303] Krita fails to build on Windows in Debug mode
https://bugs.kde.org/show_bug.cgi?id=369303 --- Comment #14 from Boudewijn Rempt --- It still fails: CMakeFiles\kritaui.dir/objects.a(kis_uniform_paintop_property_widget.cpp.obj): In function `KisUniformPaintOpPropertyIntSlider::KisUniformPaintOpPropertyIntSlider(QSharedPointer, QWidget*)': C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:81: undefined reference to `KisSliderBasedPaintOpProperty::max() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:81:(.text+0x496): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::max() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:81: undefined reference to `KisSliderBasedPaintOpProperty::min() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:81:(.text+0x4a4): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::min() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:82: undefined reference to `KisSliderBasedPaintOpProperty::singleStep() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:82:(.text+0x4c5): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::singleStep() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:83: undefined reference to `KisSliderBasedPaintOpProperty::pageStep() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:83:(.text+0x4e3): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::pageStep() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:85: undefined reference to `KisSliderBasedPaintOpProperty::suffix() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:85:(.text+0x51f): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::suffix() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:86: undefined reference to `KisSliderBasedPaintOpProperty::exponentRatio() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:86:(.text+0x551): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::exponentRatio() const' CMakeFiles\kritaui.dir/objects.a(kis_uniform_paintop_property_widget.cpp.obj): In function `KisUniformPaintOpPropertyDoubleSlider::KisUniformPaintOpPropertyDoubleSlider(QSharedPointer, QWidget*)': C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:121: undefined reference to `KisSliderBasedPaintOpProperty::decimals() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:121:(.text+0x9e6): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::decimals() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:121: undefined reference to `KisSliderBasedPaintOpProperty::max() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:121:(.text+0x9f4): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::max() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:121: undefined reference to `KisSliderBasedPaintOpProperty::min() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:121:(.text+0xa05): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::min() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:122: undefined reference to `KisSliderBasedPaintOpProperty::singleStep() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:122:(.text+0xa33): relocation truncated to fit: R_X86_64_PC32 against undefined symbol `KisSliderBasedPaintOpProperty::singleStep() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:124: undefined reference to `KisSliderBasedPaintOpProperty::suffix() const' C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:124:(.text+0xa77): additional relocation overflows omitted from the output C:/dev/4/64/krita/libs/ui/brushhud/kis_uniform_paintop_property_widget.cpp:125: undefined reference to `KisSliderBasedPaintOpProperty::exponentRatio() const' collect2.exe: error: ld returned 1 exit status libs\ui\CMakeFiles\kritaui.dir\build.make:10277: recipe for target 'bin/libkritaui.dll' failed mingw32-make[2]: *** [bin/libkritaui.dll] Error 1 CMakeFiles\Makefile2:16424: recipe for target 'libs/ui/CMakeFiles/kritaui.dir/all' failed mingw32-make[1]: *** [libs/ui/CMakeFiles/kritaui.dir/all] Error 2 Makefile:139: recipe for target 'all' failed mingw32-make: *** [all] Error 2 -- You ar
[plasmashell] [Bug 388143] Favorites and History disappear in launcher when I restart plasmashell
https://bugs.kde.org/show_bug.cgi?id=388143 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- I have the same on my laptop with master branch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388143] New: Favorites and History disappear in launcher when I restart plasmashell
https://bugs.kde.org/show_bug.cgi?id=388143 Bug ID: 388143 Summary: Favorites and History disappear in launcher when I restart plasmashell Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: cont...@neros.fr CC: plasma-b...@kde.org Target Milestone: 1.0 If I restart plasmashell, or my computer, favorites and history in the app launcher (kickoff or alternatives) are gone. I'm on Arch with the last updates. -- You are receiving this mail because: You are watching all bug changes.
