[digikam] [Bug 371648] New: not able to use in digikam cifs share with the same name under linux and windows
https://bugs.kde.org/show_bug.cgi?id=371648 Bug ID: 371648 Summary: not able to use in digikam cifs share with the same name under linux and windows Product: digikam Version: 5.2.0 Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: AlbumsView Assignee: digikam-de...@kde.org Reporter: stefan.onl...@loehr-online.de I am trying to use digikam as the one and only photo organisation tool. Unfortunatelly my wife is using windows and I am using linux. All the photos are stored on a cifs share (NAS). Digikam uses external mysql server to be able to use the same "metadatadase" on both systems. But I cannot find a way to add the cifs share with the same name so that the versions of digikam use the same folders. One problem is, that the \\ in windows world are not useable in linux. So please add a solution to map the different notations. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369512] New: Plasma Crashes after boot
https://bugs.kde.org/show_bug.cgi?id=369512 Bug ID: 369512 Summary: Plasma Crashes after boot Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ei...@gmx.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Booting the system. Yesterday I agreed to the package update (via OpenSuse) and a new version of NVIDIA drivers was installed... The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81c3b9e7c0 (LWP 2125))] Thread 7 (Thread 0x7f810afff700 (LWP 2195)): #0 0x7f81bd0a2bfd in poll () at /lib64/libc.so.6 #1 0x7f81b977fe64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f81b977ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f81bd9cfd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f81bd976d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f81bd79861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f81c1648282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f81bd79d32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f81b8bc6754 in () at /usr/X11R6/lib64/libGL.so.1 #9 0x7f81bc8ac0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f81bd0ab02d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f8191f5d700 (LWP 2194)): #0 0x7f81bc8b003f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f81c327b86b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f81c327b899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f81b8bc6754 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f81bc8ac0a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f81bd0ab02d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f819385f700 (LWP 2185)): #0 0x7f81bd0a2bfd in poll () at /lib64/libc.so.6 #1 0x7f81b977fe64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f81b977ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f81bd9cfd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f81bd976d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f81bd79861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f81c0aace18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f81bd79d32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f81b8bc6754 in () at /usr/X11R6/lib64/libGL.so.1 #9 0x7f81bc8ac0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f81bd0ab02d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f819915e700 (LWP 2136)): #0 0x7f81bd0b75ff in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7f81bd0a2bf2 in poll () at /lib64/libc.so.6 #2 0x7f81b977fe64 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f81b977ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f81bd9cfd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f81bd976d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f81bd79861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f81c0aace18 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f81bd79d32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f81b8bc6754 in () at /usr/X11R6/lib64/libGL.so.1 #10 0x7f81bc8ac0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f81bd0ab02d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f81a97ac700 (LWP 2131)): #0 0x7f81bd09eccd in read () at /lib64/libc.so.6 #1 0x7f81b8bc573c in () at /usr/X11R6/lib64/libGL.so.1 #2 0x7f81b525dbf7 in () at /usr/lib64/tls/libnvidia-tls.so.304.132 #3 0x7f81b97c0b60 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f81b977f999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #5 0x7f81b977fdf8 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7f81b977ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #7 0x7f81bd9cfd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f81bd976d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7f81bd79861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #10 0x7f81c0aace18 in () at /usr/lib64/libQt5Qml.so.5 #11 0x7f81bd79d32f in () at /usr/lib64/libQt5Core.so.5 #12 0x7f81b8bc6754 in () at /usr/X11R6/lib64/li
[kdeconnect] [Bug 367726] New: File Synchronization
https://bugs.kde.org/show_bug.cgi?id=367726 Bug ID: 367726 Summary: File Synchronization Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: stefan.bul...@gmail.com I would like to set up a file to be synchronized between my phone and my desktop, and KDE-connect seems to be the obvious place for this functionality. Specifically, I would like to setup a shared KeePass database, and keep it synchronized without depending on cloud storage. This is stored as a single file, and generally in a user-selectable location. Generally my expectation is that my phone will be present whenever I make changes to the database; I am, however, unlikely to make any changes on my phone directly. That said, my phone will travel between my home and my office, and so it may hold the authoritative copy when it connects. PS. I absolutely /love/ KDE connect. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kirigami] [Bug 365002] Consider moving the back action to top
https://bugs.kde.org/show_bug.cgi?id=365002 --- Comment #4 from Philipp Stefan --- (In reply to Thomas Pfeiffer from comment #1) > Putting it at the top would be against the one-handed-use goal. > What we could do, though, is put it always at the bottom of the screen > instead of just the last position of the list. > That way it would be easy to reach with one hand, but still keep the same > position. I am not sure I agree with you here. If it is difficult to reach at the top, how did you reach the (sub)menu in first place? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 Stefan changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||ca589ee212d2734b190383969e1 ||a9fc5d2cd720d Version Fixed In||16.08 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364844] [ASTROPAD] Canvas stuck in panning mode when selecting any tool
https://bugs.kde.org/show_bug.cgi?id=364844 --- Comment #2 from Stefan --- It does appear to be a Qt 5 related bug: https://www.mail-archive.com/interest@qt-project.org/msg20852.html I hope this can be fixed, being able to draw in Krita using the iPad (through Astropad) would have been so great, as it is with Photoshop. -- You are receiving this mail because: You are watching all bug changes.
[kirigami] [Bug 365002] New: Consider moving the back action to top
https://bugs.kde.org/show_bug.cgi?id=365002 Bug ID: 365002 Summary: Consider moving the back action to top Product: kirigami Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: neptuneca...@gmail.com I want to request to move the back action in submenus to the top of the lists. So if one accesses a submenu the back button would be at the same position. Upsides: One does not have to move ones finger to go back and it is more consistent withe the back action of the blue navigation bar on top. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kirigami] [Bug 365001] New: Improve padding in blue navigation bar
https://bugs.kde.org/show_bug.cgi?id=365001 Bug ID: 365001 Summary: Improve padding in blue navigation bar Product: kirigami Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: neptuneca...@gmail.com The blue navigation bar on top of the kirigami gallery (sorry, I don't know what it's called) can be improved by adding padding between the left screen edge and the first item. Currently there seems to be none. As a rule of thumb there should be the same amount of padding between the the left screen edge and the text as there is between the top screen edge and the text. Additionally vertically center the arrow icon in the top bar. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kirigami] [Bug 365000] New: Increase list item padding
https://bugs.kde.org/show_bug.cgi?id=365000 Bug ID: 365000 Summary: Increase list item padding Product: kirigami Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: neptuneca...@gmail.com Currently the list items are a bit small on my phone screen. About 0.6cm. I suggest to up the padding on list items (and drawer items) so they reach about 1cm in the real world. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kirigami] [Bug 364999] New: Remove separator lines between drawer items
https://bugs.kde.org/show_bug.cgi?id=364999 Bug ID: 364999 Summary: Remove separator lines between drawer items Product: kirigami Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: neptuneca...@gmail.com There is a separator line between every item in the context drawers. These lines add little meaning but much visual clutter to the drawers themselves. The separator lines should be used in list views only (and with much more tint (ligher)) and to separate groups of times. Similar to desktop contect menus. I.e. there would not be a separator line between Copy and Paste, but between say Paste and New Document. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kirigami] [Bug 364998] New: Shadow of drawer buttons obstructs its symbol
https://bugs.kde.org/show_bug.cgi?id=364998 Bug ID: 364998 Summary: Shadow of drawer buttons obstructs its symbol Product: kirigami Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: neptuneca...@gmail.com Currently the shadow for the buttons that reveal the drawers come from the middle of the button itself, making the button symbol look muddled and decreases contrast drastically. The shadow should only be shown on the outline of the button itself and only from one direction. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kirigami] [Bug 364997] New: Primary actions are hard to trigger
https://bugs.kde.org/show_bug.cgi?id=364997 Bug ID: 364997 Summary: Primary actions are hard to trigger Product: kirigami Version: unspecified Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: neptuneca...@gmail.com Trying to trigger the primary action button with the thumb is difficult right now, as lifting the thumb off the button will likely result in a slight drag motion of the action button, thereby invalidating the push action. Reproducible: Always Steps to Reproduce: 1. Hold your phone in one hand 2. Try to trigger the primary action with your thumb several times Expected Results: Triggering primary action should have a high(er) success rate -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #15 from Stefan --- Diff added to phabricator -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364844] New: Canvas stuck in panning mode when selecting any tool (using Astropad).
https://bugs.kde.org/show_bug.cgi?id=364844 Bug ID: 364844 Summary: Canvas stuck in panning mode when selecting any tool (using Astropad). Product: krita Version: 3.0 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: grave Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: stefan.gabri...@gmail.com I'm trying to draw in Krita on my iPad Pro with the Apple Pencil through Astropad which connects to my MBP where Krita (3.0) is installed. However whenever I put down the pencil on the canvas it shows the hand cursor and switches to panning mode. Nothing is drawn. Switching to another tool in the toolbar doesn't change this behavior, neither on the iPad with the pencil, nor using the mouse on the MBP. It keeps being stuck in panning mode. It is still possible to use different widgets like the brush size slider or the color wheel, just not the canvas itself. I've tried this with both the 3.0 dmg and the developer krita-eb0d266-3.0.dmg build and they have both the same problem. The current 2.9 version of Krita is working correctly, so I don't think the problem is with Astropad. Reproducible: Always Steps to Reproduce: 1. Open up Krita, create a new document. 2. Open up Astropad on MBP and on iPad Pro. 3. Try to draw something on the canvas with the pencil. Actual Results: The canvas is panning. Expected Results: The canvas should have drawn something. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #14 from Stefan --- And adding works also now :) Believe never the documentation ;) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #13 from Stefan --- Reading, deleting and modifying works now. Adding is still a problem. A reason could be the date format. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #12 from Stefan --- Today a was working on the write access. The deletion of an note works now, but the resource blocks after this operation and is then unusable. Adding and modifying don't work at the moment. The note data seems not to be available as payload. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #11 from Stefan --- The resource provides a configuration dialog now -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #10 from Stefan --- The resource provides read-only access now. The next steps are a network error handling and a configuration dialog. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #9 from Stefan --- I get now also now content and the remote revision. I think that I had not set everything correctly from the original item, so that the result wasn't recognized properly. I now doing this: resultItem = Akonadi::Item(item); The setPayload part seems to to be invalid, so the note content is not visible at the moment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364457] Don't Resize Small Avatar Pictures to Fill Avatar Bubble
https://bugs.kde.org/show_bug.cgi?id=364457 --- Comment #2 from Philipp Stefan --- Yes, I reported this bug before the reversal decision. I will comment again here and on IRC when we have updated the designs. Please hold for now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364539] Preview close button in tooltips don't fit into the container
https://bugs.kde.org/show_bug.cgi?id=364539 --- Comment #3 from Philipp Stefan --- Created attachment 99638 --> https://bugs.kde.org/attachment.cgi?id=99638&action=edit kdeglobals file -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #8 from Stefan --- A little update from yesterday: Getting all items with correct id works now. I have also now a Job class for collections for getting the global sync revision. This also seems to be working now. I'm now working on getting the notes content. On the beginning this was a little confusing because the mime type wasn't correctly, so the corresponding method wasn't called -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364545] New: Settings windows use wrong icon
https://bugs.kde.org/show_bug.cgi?id=364545 Bug ID: 364545 Summary: Settings windows use wrong icon Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: neptuneca...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Almost all applet settings windows use the wrong application icon. They use a monochrome icon. Please use preferences-other as generic application icon for settings windows instead. Reproducible: Always Steps to Reproduce: 1. Open any applets' settings window 2. See that it uses a monochrome icon in the window titlebar and task manager Expected Results: They should use a colored application icon instead Seen on neon dev unstable (git branch) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364544] "Computer" category icon not rendered correctly
https://bugs.kde.org/show_bug.cgi?id=364544 --- Comment #1 from Philipp Stefan --- Created attachment 99631 --> https://bugs.kde.org/attachment.cgi?id=99631&action=edit Icon with artifacts -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364544] New: "Computer" category icon not rendered correctly
https://bugs.kde.org/show_bug.cgi?id=364544 Bug ID: 364544 Summary: "Computer" category icon not rendered correctly Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: neptuneca...@gmail.com CC: plasma-b...@kde.org When opening Kickoff the "computer" category icon is not rendered correctly. The right side of the icon is missing for some reason Reproducible: Always Seen on Neon dev unstable (git branch) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364539] New: Preview close button in tooltips don't fit into the container
https://bugs.kde.org/show_bug.cgi?id=364539 Bug ID: 364539 Summary: Preview close button in tooltips don't fit into the container Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: neptuneca...@gmail.com CC: plasma-b...@kde.org When one hovers of the window close button in one of the task manager tooltips, the shown button outline does not fit into the container i.e. the button outline is only shown in half Reproducible: Always Steps to Reproduce: 1. Open a window 2. Go to task manager and call a tooltip 3. Hover over the close button Actual Results: button outline only shown partially Expected Results: See complete button outline Seen on Neon dev unstable (git branch) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364539] Preview close button in tooltips don't fit into the container
https://bugs.kde.org/show_bug.cgi?id=364539 --- Comment #1 from Philipp Stefan --- Created attachment 99626 --> https://bugs.kde.org/attachment.cgi?id=99626&action=edit Picture of the bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364538] System Tray Settings uses wrong icon
https://bugs.kde.org/show_bug.cgi?id=364538 --- Comment #1 from Philipp Stefan --- Created attachment 99625 --> https://bugs.kde.org/attachment.cgi?id=99625&action=edit Incriminating evidence -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364538] New: System Tray Settings uses wrong icon
https://bugs.kde.org/show_bug.cgi?id=364538 Bug ID: 364538 Summary: System Tray Settings uses wrong icon Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: neptuneca...@gmail.com The system tray settings dialogue uses a monochrome icon for the "entries" section instead of a colored one. Perhaps use preferences-desktop-notification instead. Reproducible: Always Expected Results: Use colored icon like other groups. Seen on neon unstable iso -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #7 from Stefan --- The OAuth authentication works now. Also getting access to seems to be working (no QNetwork-Reply error). So the problem now seems to be parsing the JSON data. I think I use QJsonDocument not correctly. The KJobs are now asyncron. I have now a new KJob for receiving the collections. This is needed for receiving the remote id. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364464] New: Opening the fullscreen launcher shows a task manager item for a moment
https://bugs.kde.org/show_bug.cgi?id=364464 Bug ID: 364464 Summary: Opening the fullscreen launcher shows a task manager item for a moment Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: neptuneca...@gmail.com CC: plasma-b...@kde.org Opening the fullscreen launcher (as well as the alternative plasmoid selection dialogue) shows a launcher item for a split second before vanishing again. Reproducible: Always Steps to Reproduce: 1. Look at our task manager/icons only task manager 2. Open the fullscreen launcher 3. See an item appear and vanish in the launcher within a split second Expected Results: Not show any new item in the task manager when the launcher is opened Observed in VirtualBox 5.0.20 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364461] [SDDM] Adjust Border on Avatar Pictures
https://bugs.kde.org/show_bug.cgi?id=364461 Philipp Stefan changed: What|Removed |Added Summary|[SDDM] Adjust Border on |[SDDM] Adjust Border on |Avatar icons|Avatar Pictures -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364461] [SDDM] Adjust Border on Avatar icons
https://bugs.kde.org/show_bug.cgi?id=364461 --- Comment #2 from Philipp Stefan --- Created attachment 99570 --> https://bugs.kde.org/attachment.cgi?id=99570&action=edit Graphical explanation of the double border -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364461] [SDDM] Adjust Border on Avatar icons
https://bugs.kde.org/show_bug.cgi?id=364461 --- Comment #1 from Philipp Stefan --- Created attachment 99569 --> https://bugs.kde.org/attachment.cgi?id=99569&action=edit AvatarBorder that can be used as overlay -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364461] New: [SDDM] Adjust Border on Avatar icons
https://bugs.kde.org/show_bug.cgi?id=364461 Bug ID: 364461 Summary: [SDDM] Adjust Border on Avatar icons Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: neptuneca...@gmail.com CC: plasma-b...@kde.org This https://community.kde.org/File:Blueprint.png design document we made contains an error :re the border of the Avatar icons. It makes it looks like the border around the images are supposed to be 2px thick pastel blue. That was an error on my part, I am deeply sorry. The avatar bubble with the border is supposed to be 130px by 130px, not 132px by 132px. The border is made up of two parts. A 1px thick 128px by 128px circle on top of the 128px avatar picture. This circle is supposed to to have a gradient starting in the top left, going to the bottom right (45%). Gradient start (top left) should use 100% white and 60% opacity, gradient stop should use 100% white and 0% opacity. Then there's another 1px thick 130px by 130px ring. Ideally it should be 40% darker than the average colour of the avatar picture, at 60% opacity. Alternatively, it that is not possible it should use 40% black and 40% opacity. If all this ring business is too complicated for QML one can overlay the picture found in the attachment. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364457] New: Don't Resize Small Avatar Pictures to Fill Avatar Bubble
https://bugs.kde.org/show_bug.cgi?id=364457 Bug ID: 364457 Summary: Don't Resize Small Avatar Pictures to Fill Avatar Bubble Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: neptuneca...@gmail.com CC: plasma-b...@kde.org Currently, if avatar images are too big or too small they are resized to fit into the photo bubble in the login screen. Especially smaller picture end up looking very pixelated and rough when scaled up. Instead of doing so the picture should be shown at it's true size. Reproducible: Always Steps to Reproduce: 1. Select a small image as avatar 2. Logout 3. See the upscaled picture -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 364454] New Login Screen: system-reboot.svg does not assume the text colour like everything else
https://bugs.kde.org/show_bug.cgi?id=364454 --- Comment #1 from Philipp Stefan --- Created attachment 99567 --> https://bugs.kde.org/attachment.cgi?id=99567&action=edit The icon has the wrong colour -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 364454] New: New Login Screen: system-reboot.svg does not assume the text colour like everything else
https://bugs.kde.org/show_bug.cgi?id=364454 Bug ID: 364454 Summary: New Login Screen: system-reboot.svg does not assume the text colour like everything else Product: Breeze Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: neptuneca...@gmail.com CC: kain...@gmail.com On the new login screen the system-reboot.svg icon does not assume the text colour as per the new 5.7 mechanic, but uses the default icon colour. Reproducible: Always Steps to Reproduce: 1. Load the login screen 2. Look at reboot option 3. Icon and text have a different colour Expected Results: The icon should use the text color i.e. white -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #6 from Stefan --- I hope I have the right idea now: KMime::Message::Ptr akonadiNote = KMime::Message::Ptr(new KMime::Message); akonadiNote->subject(true)->fromUnicodeString( jsonNote["title"].toString(), "utf-8" ); akonadiNote->contentType()->setMimeType("text/plain"); akonadiNote->contentType()->setCharset("utf-8"); akonadiNote->contentTransferEncoding(true)->setEncoding(KMime::Headers::CEquPr); akonadiNote->mainBodyPart()->fromUnicodeString(jsonNote["note-content"].toString().toUtf8()); akonadiNote->assemble(); resultItem.setPayload(akonadiNote); Problem is now the debugging. How can read the debug messages like qCDebug(log_tomboynotesresource) << "Resource started"; -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #5 from Stefan --- A little status update: For OAuth I use now the suggested o2. Because of cmake it was a little bit difficult getting it working. I want to use the following KJob classes: - TomboyJobBase: it should provide the full OAuth stuff using the library o2 - TomboyServerAuthenticateJob: It's needed for the configuration it should do the OAuth registration process getting the client credentials - TomboyItemsDownloadJob: It should retrieve all items - TomboyItemDownloadJob: It should get the specific item - TomboyItemUploadJob For the first 3 classes I have a rudimentary implementation now. I use o2 and KIO::AccessManager (o2 needs a QNetworkAccessManager!) for accessing the server. I parse the received data with QJsonDocument. Current question is, how I have to save the notes data in Akonadi::Item. I studied the code of KJots and I think I have to use KMime:Message, but the details are still unclear. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #4 from Stefan --- Link to the repository: https://github.com/staeglis/tomboynotes -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #3 from Stefan --- Hello, thank you for your comment. QOAuth is no option anymore because it's not working properly. Using kQOAuth could be also problematic because it support only HTTP POST and not HTTP PUT. The API description is unclear in this point. So o2 is an interesting option because it does only OAuth and the other stuff is done directly with QNetworkAccessManager. But I don't understand how I could use KIO::KJob. Some example resource would be helpful. But for this I'll write a mail soon. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 362938] Implement tomboy REST API as Akonadi resource
https://bugs.kde.org/show_bug.cgi?id=362938 --- Comment #1 from Stefan --- I need also a library that implements OAuth 1.0. For now I have two candidates: QOAuth: https://github.com/ayoy/qoauth kQOAuth: https://github.com/kypeli/kQOAuth I think the better candidate is QOAuth because it looks lesser dead than the other. But what think you? -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 363148] Deselecting Signing check box in Advanced Settings - Certificate Usage results in General Error in Kleopatra
https://bugs.kde.org/show_bug.cgi?id=363148 Stefan changed: What|Removed |Added CC||luke1...@gmx.de --- Comment #1 from Stefan --- Could confirm the issue here --- Win 10, Kleopatra 2.2.0. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 363193] New: Decryption failed when trying to import S/MIME certificate backed-up from Firefox
https://bugs.kde.org/show_bug.cgi?id=363193 Bug ID: 363193 Summary: Decryption failed when trying to import S/MIME certificate backed-up from Firefox Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: luke1...@gmx.de CC: kdepim-b...@kde.org, m...@kde.org When trying to import an S/MIME certificate backed-up from Firefox using a long passphrase, importing the p12 file in Kleopatra fails with the error: Decryption failed. This is bad in two ways: a) it should just work (using long passphrases is advertised) b) the error message doesn't point to the actual problem at all - the user might not at all get the idea that a too long passphrase is the problem The issue might be related to https://bugs.kde.org/show_bug.cgi?id=362640 but I'm not too sure, especially since this is an entire different use-case and error message. Reproducible: Always Steps to Reproduce: 1. Get an S/MIME certificate in Firefox (normal case, when creating a certificate via the webbrowser - for instance via CAcert). 2. In Firefox: Tools -> Options -> Advanced -> View Certificates 3. Select your certificate -> Backup... 4. Enter a filename where to store the p12-file 5. Enter the master password, if required 6. Use the following password to encrypt the p12-file: 0f9guf9dhgsadi90sdg0ßfd0hdgj0df 7. In Kleopatra: File -> Import certificate... 8. Select the p12-file saved earlier 9. Enter the password: 0f9guf9dhgsadi90sdg0ßfd0hdgj0df 10. Enter a random passphrase to protect the imported object - for instance test1234 and confirm it once more Actual Results: Error shows up: Title: Certificate Import Failed - Kleopatra An error occurred while trying to import the certificate [filename].p12: Decryption failed Expected Results: Import of certificate succeeds. The error doesn't occur, when using a shorter password to create the backup of the certificate from Firefox. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 363154] New: Cannot create certificate with @ in the name field.
https://bugs.kde.org/show_bug.cgi?id=363154 Bug ID: 363154 Summary: Cannot create certificate with @ in the name field. Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: luke1...@gmx.de CC: kdepim-b...@kde.org, m...@kde.org Trying to create a new certificate with the @-sign in the name field fails (unless the @ is used as the first character in the name). Using gpg directly to create a keypair, this works just fine. Note that in some cases keys are generated specifying the email address as the name and as the email address to ensure privacy where the key is used. For instance the end-to-end-encryption of posteo.de only accepts OpenPGP keys which comply to that restriction: https://posteo.de/en/help/policies-for-public-keys Reproducible: Always Steps to Reproduce: 1. File -> New Certificate -> Create a personal OpenPGP key pair 2. Try to enter the following name: f...@bar.com Actual Results: The @-sign cannot be entered. Trying to enter it results in a noop. Expected Results: The @-sign can correctly be entered. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #81 from Stefan --- As I see it, the problem is the whole locale system which assumes that all your preferences are based on a single region. This problem is beyond KDE, and affects the entire UNIX ecosystem. On Sun, May 15, 2016 at 4:37 PM, Janet via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=340982 > > --- Comment #80 from Janet --- > I'm now using an alternate clock/calendar widget for the panel > (http://kde-look.org/content/show.php/Event+Calendar?content=175591) which > allows to set the date to a format I want. It can show the short day - "Fr > 25.09." - and you can use any format for time and date you want, that's > enough > for me. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 362640] cryptic error message, when using long password to export secret key
https://bugs.kde.org/show_bug.cgi?id=362640 --- Comment #1 from Stefan --- On a related note: Regardless of the error, the output file is created (it's empty however, in the error case). It would be better, if the file would either not be created, if there was an error, or that the file is removed and not being left behind, if exporting failed. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 362640] cryptic error message, when using long password to export secret key
https://bugs.kde.org/show_bug.cgi?id=362640 Stefan changed: What|Removed |Added CC||luke1...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 362640] New: cryptic error message, when using long password to export secret key
https://bugs.kde.org/show_bug.cgi?id=362640 Bug ID: 362640 Summary: cryptic error message, when using long password to export secret key Product: kleopatra Version: 2.2.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: luke1...@gmx.de CC: kdepim-b...@kde.org, m...@kde.org Following the described steps the Kleopatra presents an error message which is not quite user friendly. In fact it should be possible to use a long password (as the one given in the repro steps). I understand that the issue is that the specified password is too long but there are several usability glitches here: 1. the input field to set a password to encrypt the keyfile does allow entering a long password and neither the displayed text hints to any limit there, nor is there a warning/error displayed when clicking OK after having entered the long password - at least there should be some mentioning on the restriction. 2. Given that very long passphrases are generally advertised in all docs related to GnuPG, IMO there should be no character limit for the password here at all. 3. The displayed error in the end is not quite user friendly. It's so cryptic and for someone not reading the whole text in detail it won't directly point to the actual issue (too long password). Such an error should be better presented to the user IMO. A simple error message would suffice: "An error occurred while trying to export the secret key. Error: password too long" Any additional details are only of interest to developers and should not be presented to users. Reproducible: Always Steps to Reproduce: 1.on an existing X.509 key right click and select: "Export Secret Keys" 2. select an output file and click ok 3. enter the key's passphrase -> press ok 4. enter the following password for the exported key: 0f9guf9dhgsadi90sdg0ßfd0hdgj0df -> press ok 5. enter the same password to confirm it -> press OK Actual Results: The following error is displayed Title: Secret Key Export Error --- Kleopatra An error occurred while trying to export the secret key. The output from E:\Program Files (x86)\GNU\GnuPG\gpgsm.exe was: gpgsm: gpg-protect-tool: AllowSetForegroundWindow(6380) failed: Access is denied. gpgsm: gpgsm: gpg-protect-tool: AllowSetForegroundWindow(3692) failed: Access is denied. gpgsm: gpgsm: gpg-protect-tool: password too long gpgsm: gpg-protect-tool: password too long gpgsm: gpg-protect-tool: password too long gpgsm: error running 'E:\Program Files (x86)\GNU\GnuPG\gpg-protect-tool.exe': exit status 2 Expected Results: Password file is generated without errors. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 361503] New: Spam filter (spamassasin) does not work
https://bugs.kde.org/show_bug.cgi?id=361503 Bug ID: 361503 Summary: Spam filter (spamassasin) does not work Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: bugtrac...@losch-spandau.de Since several months spamassasin did not work at my computer. Versions: SpamAssassin version 3.4.1 running on Perl version 5.18.2 kmail2 5.1.3 No spam was moved from "Posteingang" to "Trash" Yesterday I found the bug! The spam filter were not installed properly. First filter "Spamassasin Check" worked well. The second filter, which moves spam to trash and marks it as "read" did not. The filter rule was "X-Spam-Flag" matches regular expression "(yes)|(YES)" But spamassasin does not create a line "X-Spam-Flag". In teh current version it creates a line "X-Spam-Level". So I added a second rule to that filter: "X-Spam-Level" contains "**" Works! Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 360623] New: baloo daemon crashes every time while kontact ist started
https://bugs.kde.org/show_bug.cgi?id=360623 Bug ID: 360623 Summary: baloo daemon crashes every time while kontact ist started Product: Baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: bugtrac...@losch-spandau.de CC: pinak.ah...@gmail.com Application: baloo_file (5.19.0) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I started kontact, firefox and konsole. Guess kontact (kmail) causes baloo to crash with segmentation fault. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff2b51d1780 (LWP 1610))] Thread 2 (Thread 0x7ff16a0ce700 (LWP 2281)): #0 0x7ff2b2cc7c8d in read () at /lib64/libc.so.6 #1 0x7ff2af71bb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff2af6da999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff2af6dadf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff2af6daf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff2b3904d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff2b38abd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x004152cd in () #8 0x7ff2b36cf382 in () at /usr/lib64/libQt5Core.so.5 #9 0x7ff2b36d232f in () at /usr/lib64/libQt5Core.so.5 #10 0x7ff2b1cf70a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7ff2b2cd3fed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7ff2b51d1780 (LWP 1610)): [KCrash Handler] #6 0x7ff2b09d625c in mdb_get () at /usr/lib64/liblmdb-0.9.14.so #7 0x7ff2b3fa74cd in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5 #8 0x7ff2b3fa4dc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #9 0x7ff2b3fb6949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x0041d3e3 in () #11 0x0041d49d in () #12 0x7ff2b38dd73f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #13 0x004270d5 in () #14 0x0041b686 in () #15 0x7ff2b38dd73f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x7ff2b38eaf22 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5 #17 0x7ff2b38de8bc in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7ff2b38ae18d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x7ff2b38ade95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7ff2b390477d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #21 0x7ff2b3904ad9 in () at /usr/lib64/libQt5Core.so.5 #22 0x7ff2af6dac84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #23 0x7ff2af6daed8 in () at /usr/lib64/libglib-2.0.so.0 #24 0x7ff2af6daf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #25 0x7ff2b3904d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #26 0x7ff2b38abd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #27 0x7ff2b38b38f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #28 0x0040a832 in () #29 0x7ff2b2c10b05 in __libc_start_main () at /lib64/libc.so.6 #30 0x0040a9a8 in _start () Possible duplicates by query: bug 359672, bug 355210, bug 353223. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.